• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 40 subscribers
  • Views 399 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

CC3100: What is the best way to handle disconnect events such as SL_WLAN_DISCONNECT_ROAMING_TRIGGER_BSS_LOSS, SL_WLAN_DISCONNECT_ROAMING_TRIGGER_AP_DISCONNECT...

CC3100: Sporadic disconnects

Wilmer Suarez
Intellectual 310 points
Part Number: CC3100

On an active and stable connection, occasionally, the device displays this Disconnect event:

SL_WLAN_DISCONNECT_ROAMING_TRIGGER_BSS_LOSS (109)
and this general error event:

[GENERAL EVENT] - Fatal Error!
Status: -109 (SL_GENERAL_ERROR_CON_MGMT_STATUS_DISCONNECT_DURING_CONNECT)
Sender: 5

I have a device that successfully reconnects to the AP after this happens but sometimes this error is constant, and the device never reconnects.

I've noticed that this seems to happen every 30ish minutes before reconnecting.

Other devices on the same firmware are never able to initially connect because of the same error.

I've searched through the forums a bit but have not found a solution.

Our device is on the latest SDK version for the CC3100 and the RSSI from the device ranges from -17 to -30 (The device is right now to the router).

Our device is rated to work on the 2.4 GHz range only with 802.11 b/g/n. i've made sure the router is operating with those parameters only and disabled any roaming functionality and signal strength is set to high. This is the router I'm working with for reference: AX1800 Wi-Fi 6 Router. I've tried multiple APs/routers with similar issues.

I'm going to try and capture the NWP logs with a few of these disconnects. Will reply with the logs soon.

Anything else I can try? 

Thank you

  • 0
    TI__Guru 63006 points

    We are not familiar with this specific model. is it a Linksys router?

    We will need to see logs (NWP & air sniffer) to understand the issue.

    BSS loss is typically reported when we loss track of the AP's beacon. It can happen if the AP stop transmitting (we show this happens in the past) or if it is transmitting out of the expected window, Can you test with the power-save disabled (always-on policy)?

  • 0 in reply to Kobi Leibovitch
    Intellectual 310 points

    it is a TP-link router.

    Here is the NWP Logs (disconnect a few times):

    NWP_Logs.txt

    I have sniffed traffic using tcpdump (disconnect occurred about 3 times). How can I send this to you privately?

    Note: The logs are not in sync, they reference different instances/captures of the same issue.

    By the way, the NWP logs seem to be very useful since I see it being asked for a lot. Is there a public tool available to decode that myself?

  • 0 in reply to Wilmer Suarez
    TI__Guru 63006 points

    the NWP log can't be decoded by our customers yet. We may enable this in the future.

    You can use dropbox / google drive provide the sniffer logs.

    I'll send you a "friendship" request so you can provide the link privately.

  • 0 in reply to Kobi Leibovitch
    TI__Guru 63006 points

    Again the NWP logs shows that we disconnects after we couldn't hear the AP's beacons.

    The Sniffer log provided is missing the connection details (either it is filtered out or you sniffed the wrong channel).

    Have you tried the always-on configuration?

  • 0 in reply to Kobi Leibovitch
    Intellectual 310 points

    I have configured the SL_POLICY_PM policy to be always on, yes.

    I was sniffing the wrong channel, correct, sorry. Something odd is happening though. I configured my 2.4GHz connection on my router to use a specific channel (6) (Transmit power still 'High') and now the disconnects are no longer happening. I've left it running for many hours and it didn't disconnect once. It would happen multiple time an hour previously.

    I'll start capturing again once I see the disconnects occur and put a useful log capture here when I do.

  • +1 in reply to Wilmer Suarez
    TI__Guru 63006 points

    maybe you had some interference on the other channel that caused the beacon loss. 

  • 0 in reply to Kobi Leibovitch
    Intellectual 310 points

    That seems to be it. My current config for 2.4GHz is:

    • Max transmit power
    • Channel width @ 20MHz
    • Channel 11
    • Fixed 802.11 b/g/n

    Haven't had a disconnect all day.