• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 40 subscribers
  • Views 369 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.

CC3100: AP drops and do not get disconnect event on CC3100

Bryan Valletta
Prodigy 210 points
Part Number: CC3100

Hi, I am working in STA mode and can connect to an AP with no issue. But if I just unplug the AP, I do not receive any disconnect event on the CC3100 and from my applications perspective I am still connected with no issue. Is this a known problem? Or do I need to configure something or is there a way to query periodically to see if the AP is still up?

Thanks!

Bryan

  • 0
    Prodigy 210 points
    My mistake. I am actually receiving the event, I was not handling it correctly!
  • 0
    TI__Mastermind 40965 points
    Hi Bryan,

    Whenever the connection to the AP is lost, the CC3100 should definitely be getting an async event in the wlan event handler indicating that the connection has been lost.

    Do you get async events when the CC3100 is first connected to the AP? You should be getting a connected to AP event as well as an IP address acquired event. If you don't get any async events at all, then you will need to look into your program flow and check to see if you call sl_task() regularly to process async events.

    If you do get async events but just not the disconnect event, then that will require some different debug. If you connect to a different AP, do you still see the same behavior?

    Regards,
    Michael
  • 0 in reply to Michael Reymond
    TI__Mastermind 40965 points
    Hi Bryan,

    Glad to hear that you resolved your issue. Let me know if you have other questions or need more help.

    Regards,
    Michael
  • 0 in reply to Michael Reymond
    Prodigy 210 points
    Thanks for your quick response Michael. It is working, I made a mistake. The had some processing in the callback that was causing the device to hang (before some debug output I had) so it seemed like it wasn't getting the event when it really was.