• State TI Thinks Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 188 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.

CC3100MOD: Distinguishing Connection Errors with CC3100 Using sl_WlanConnect API

Rahul TT
Prodigy 40 points
Part Number: CC3100MOD
Other Parts Discussed in Thread: CC3100

Tool/software:

I am writing to seek your expertise regarding an issue we are encountering with the CC3100 Wi-Fi chip, specifically during the use of the sl_WlanConnect sl_WlanConnect API.

We are currently facing challenges in identifying and distinguishing between two specific connection errors:

  1. A mismatch between the SSID or Password.
  2. A scenario where both the SSID and Password match, but the SSID is not found because router is turned off.

While attempting to connect using the sl_WlanConnect API, it is crucial for us to differentiate between these two situations to enhance our error logging process. Could you please provide guidance or recommend any specific methods or diagnostics within the CC3100 framework that could help us accurately identify these errors when using the sl_WlanConnect API? Your assistance in this matter would be greatly appreciated. Please let me know if you need any further information from our side.

  • 0
    TI__Genius 14601 points

    Hi Rahul,

    For connection issue

    1. Rahul TT said:
      A mismatch between the SSID or Password.

    The error code -2058 will be returned. 

    https://www.ti.com/lit/ug/swru455m/swru455m.pdf 

    However for scenario 2

    Rahul TT said:
    A scenario where both the SSID and Password match, but the SSID is not found because router is turned off.

    This scenario does not make sense to have an error. As you are specifically asking to connect to an ssid there is no way to know if we are just missing the beacon or maybe the environment is crowded. It would be upto the customer to put a timeout they seem appropriate when the controller will fail to find a specified SSID or else it will keep scanning and trying to connect.

    Best,

    Rogelio