• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 40 subscribers
  • Views 226 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC3235MODSF: Fast connect and moving devices

Cedric Gerber
Expert 2240 points
Part Number: CC3235MODSF

Hi,

I'm currently using auto+fast connect on our product which works fine in 99% of cases as our products are stationary.

However when a device is configured initially close to an access point, and then moved to the limit of this same access point's range, the device will still connect to it as long as it is detected (even when a much better AP is available)

Is there a recommended strategy to handle this?

If there is not, I'm thinking of periodically doing a scan and doing a manual connection to the best AP.  The easiest would be to delete/reset the fast connect stored profile (as the auto profile does just that), is there a way to do this? (Even in a hackish way by deleting the fast connect file?)

Thanks,

Cédric

  • 0
    TI__Guru 61446 points

    Hi Cedric,

    Fast connect is mainly for stationary scenarios.

    However, for your use case - you can enable the soft roaming feature, through the WLAN_GENERAL_PARAM_REGISTER_LINK_QUALITY_EVENT param (see Sl_WlanSet and chapter 4.3.6 in the http://www.ti.com/lit/ug/swru455h/swru455h.pdf).

    Br,

    Kobi

  • 0 in reply to Kobi Leibovitch
    Expert 2240 points

    Hi Kobi,

    Thanks for your feedback!

    In the doc it is also written: "Soft roaming is enabled only if FAST connection policy is disabled". If I understand this correctly it won't do for my use case.

    Is there no way to reset the fast connect saved profile?

    Cédric

  • 0 in reply to Cedric Gerber
    TI__Guru 61446 points

    Hi Cedric,

    You are right. I was not aware of this limitation. 

    As mentioned the fast connect was mainly designed for stationary use cases.

    The fast connect is a global policy and is not linked to a specific profile. It is NOT recommended to change the policy too frequent (since each change will write to the flash). You may decide to disable the FAST-Connect, in response to low RSSI trigger. 

    Br,

    Kobi

  • 0 in reply to Kobi Leibovitch
    Expert 2240 points

    Hi Kobi,

    I understand the stationary case, it's actually what we have in 99% of the cases. However for the other 1% (changing infrastructure, exchanged devices, changing AP locations, ...)  it would be helpful to have a function which would erase the currently saved fast connect profile.

    I'll try to do a manual scan and manual connect to force the next fast connects to use the best AP.

    Best regards,

    Cédric

  • 0 in reply to Cedric Gerber
    TI__Guru 61446 points

    Hi Cedric,

    You can delete the profile (sl_WlanProfileDel) whenever you get the RSSI (roaming) trigger.

    Br,

    Kobi

  • 0 in reply to Kobi Leibovitch
    Expert 2240 points

    Hi Kobi,

    Correct me if I'm wrong, but my understanding is that the profile erased by sl_WlanProfileDel is among the list of profile it can possibly connect to. It does not contain the bssid of the last connection. I suppose there is another setting containing the fast connect details.

    Anyway, I've managed to do what I want with a manual scan and manual connection, afterwards the fast connect reuse the AP set in the manual scan.

    Best regards,

    Cédric