This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3220MODA: Provisioning network not visible (sometimes!!)

Part Number: CC3220MODA

Hello,

I've created a device that starts the provisioning process (AP mode) using a custom SSID and WPA password, which is displayed to the user on a small screen.  The user then opens up their smartphone wifi settings and connects to the device by selecting the network name on their phone that's shown on the device screen.   They open up their browser and browse to the provisioning web page hosted on the device to browse their home network and enter their network password.  The device then completes the provisioning process and all is good.

The problem is when I send the devices to our client, they don't see the device provisioning network on their phone to connect to the device.

What could cause provisioning to work in my office but not theirs?

Thank you!

Joe K.

  • Hi Joseph,

    Assuming the units are tested for functionality before they go out, I can only think that the signal level they are getting from the device is too low to appear in the phone network list sometimes. Talk to them about proximity and placement of the unit. Perhaps revisit your RF layout/ impedance matching for potential signal optimization.

    -Aaron
  • Hi Aaron,

    If I may related question. How you can set impedance matching at CC3220MODA (module with integrated antenna)?

    There is no way how tune antenna by Pi filter, etc. In case of RF performance (resonance frequency) of antenna is affected by material of cover (dielectric of cover at near field of antenna).

    Jan
  • Hi Aaron,

    Thanks for the reply.  I thought that might be case, but I tried it in different locations as did they, and proximity to a router (interference) and phone didn't make a difference.  

    I did resolve the issue, and here's what I found out:

    • Flash new firmware onto the device, which clears out any provisioning profiles.
    • After provisioning the device during testing, the profile gets saved in the NWP.
    • Send the device to client office, or bring to home network.  Attempt to provision on different network.
    • When I start the network processor (sl_Start) in order to start provisioning, the NWP by default gravitates toward trying to connect to the already provisioned network. 
      I'm using the provisioning example as a base, with some modifications.  I was trying to go into Provisioning mode, but it was stuck in the state where it was trying to connect to the previously provisioned network, which didn’t let it get into provisioning. 
    • I can re-provision it at my office because the execution path where it is able to connect to the existing network has code that clears out the existing network profile.
    • I’ve updated the SimpleLinkInitCallback code to put it into the AP mode before it starts trying to reconnect to the previous network.  It is then able to wipe the old profile and get ready to receive the new one.

    This was a tricky one!

    Joe K.