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.

LAUNCHCC3235MOD: Device is connected to the deleted WiFi profile

Part Number: LAUNCHCC3235MOD
Other Parts Discussed in Thread: CC3235SF

Hi,

I have executed the sample program in the SDK "power_measurement_CC3235SF_LAUNCHXL_tirtos_ccs" in intermittent connected mode.

When it wakes up from hibernation mode, it connects to WIFI very fast. The below settings help to make a fast connection.

sl_WlanPolicySet(SL_WLAN_POLICY_CONNECTION,
SL_WLAN_CONNECTION_POLICY(1, 1, 0,
0), NULL, 0);

I have added provisioning code on top of it.

After that, if I update the new SSID, when the device wakes up from hibernate, it connects with the old WIFI network using the old IP address.

New profile not reflect when I execute Sl_Start(0,0,0)

Is there any way to reset the network settings after adding a new profile?

Regards,

Sundar

  • Hi,

    If you have a few profiles, it follows some rules. These include the priority, RSSI level and security level.

    In your case, if fast connection is defined, it would prefer to use this profile first if the AP is available since it is the fastest (no scan needed).

    What you can do in your case is either not use fast connection method (if you plan to have more than one network and you want a dynamic mechanism to move from one network to another) or to keep it but delete the profile you don't want to use.

    Regards,

    Shlomi

  • Hi Shlomi,

    Thanks for the quick response.

    If I remove the fast mode, everything works fine, but every time it takes an extra 3–4 seconds to make a WIFI connection. I want to reduce the connection time, so I am trying to make a simple link to use the new profile for a WIFI connection with Fast mode. Is it possible to or not. If I delete all the profiles, it still uses the old IP and successfully sends the data to the cloud. Please give some input to resolve this issue

    Regards,

    Sundar

  • Hi,

    If fast is defined, and the AP is in the air, it would always prefer the fast first and only if it is not there, other profiles would be invoked. There is no way to bypass it. The fast profile would get updated based on the last connected profile so if the original fast profile cannot be reached and you connect with a new profile, then it would get updated to be the fast for next times.

    Regards,

    Shlomi