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.

CC3135MOD: Software Roaming

Part Number: CC3135MOD
Other Parts Discussed in Thread: CC3135

Hi,

My customer wants to use software roaming in CC3135MOD.
Customer understood the feature is available in CC3x35, but it is not clear how to use it in details.
They checked below document section 4.3.5 and 4.3.6, but the example shown seems CC3235 code example.

Customer expects something like an external host sends AT command to enable the roaming, and the device automatically handles it.
Is there good document which explains how to use software roaming in CC3135?

And it is not clear how software roaming is handled inside the device and how long does it take to switch AP.
Do you have any documents which tell about that?

Thanks and regards,
Koichiro Tashiro

  • Not all the simplelink commands are supported over AT command.

    Currently only SL_WLAN_ROAMING_TRIGGERING_ENABLE is enabled by the ATCMD library.

    The customer can use this as a reference to add other commands such as the  enabling of the soft roaming.

    Check the ATCmdWlan_setParse code in atcmd_wlan.c which identify the SL_WLAN_ROAMING_TRIGGERING_ENABLE and parses the received params (a new define will be needed for SL_WLAN_SOFT_ROAMING_ENABLE and its parameters to initiate the SlWlanRegisterLinkQualityEvents_t structure).

    He can also use the sl_WlanSet command to enable the soft roaming as hard coded in the ATCMD library or the at_commands application and avoid the external configuration.

    Br,

    Kobi

  • Hi Kobi,

    Could you reply below question as well?

    And it is not clear how software roaming is handled inside the device and how long does it take to switch AP.
    Do you have any documents which tell about that?

    Thanks and regards,
    Koichiro Tashiro

  • The NWP programmer's guide is all we got on this.

    Basically a scan will be triggered based on the low RSSI event. If we find an AP with better RSSI (see differences in the AP selection when using Sotf-Roaming or Triggered-Roaming) we will disconnect from current AP and initiate the connection to the better candidate (the time it takes is the connection setup time).