ESP8266 Developer Zone The Official ESP8266 Forum 2015-08-05T13:41:51+08:00 https://bbs.espressif.com:443/feed.php?f=66&t=904 2015-08-05T13:41:51+08:00 2015-08-05T13:41:51+08:00 https://bbs.espressif.com:443/viewtopic.php?t=904&p=3051#p3051 <![CDATA[Re: SOFTAP+STA Issues]]>
Sorry that we can not duplicate your problem.

Could you provide your test code and UART output logs for debugging ?

Could you provide the captured 802.11 packets ?

Statistics: Posted by ESP_Faye — Wed Aug 05, 2015 1:41 pm

]]> 2015-08-05T06:09:18+08:00 2015-08-05T06:09:18+08:00 https://bbs.espressif.com:443/viewtopic.php?t=904&p=3043#p3043 <![CDATA[SOFTAP+STA Issues]]> 1. ESP-01 module
2. SDK v1.2.0
3. iPhone 6 and MacbookPro as wifi clients

We make the firmware to run in SOFTAP+STA mode, where the SOFTAP is used by wifi clients to configure the STA login (ssid/pwd) to an external AP (which connects to internet). We found strange behaviors in the SOFTAP after the STA is successfully connected to the external AP.

Here is the list of observed:

  1. wifi clients (7 out of 10 time) are not enable to connect to the SOFTAP anymore after the STA is connected.
  2. for those time when wifi client can connect to the SOFTAP, abnormally frequent TCP reconnects are observed.
  3. after disconnecting (initiated from wifi client side), the SOFTAP is NOT able to detect the client left - i.e. callback set with wifi_set_event_handler_cb() never calls.
  4. if wait long enough (10s of minutes), sometime the SOFTAP could recover (detected the client left), but sometime it will stuck forever.
  5. even after it recovers, the SOFTAP can never accept wifi client again.

Few more data points:

  • it seems happening when the ssid channel of SOFTAP and STA are mismatched. If we hardcode the SOFTAP channels the same as the external AP, the result is much more stable. We are aware of the single channel hardware limitation for SOFTAP and STA, and SOFTAP will release its station clients right before STA starts to connect to the external AP if the external AP doesn't share the same channel when the SOFTAP was started. But that shouldn't cause the above misbehaviors after the SOFTAP is switched to use the matched channel.
  • no matter what we do there is no way to recover (or detect) the error state. We tried disable-then-enable SOFTAP mode or reissue wifi_softap_set_config(), and none will help.
  • system_restart or hardware reset doesn't really solve the problem. wifi clients can connect the 1st time. But if we issue a disconnect on STA and restart the steps, the same result would be found.

Do you see anything like that?

../ming

Statistics: Posted by ming — Wed Aug 05, 2015 6:09 am

]]>