- Mon Oct 06, 2014 9:30 am
#1308
When the module loses AP connection while TCP transfer is active it will always return "busy" string to all AT commands (incliding AT+RST) and re-joining AP is impossible. If there is internal timeout or something it is set way too long as half an hour later the device was still "busy". The only way out of this is using the RESET pin or power cycle. Bottom line is you'd better make sure you have a spare GPIO for the RESET pin as AT+RST can't be considered reliable.
- Tue Oct 07, 2014 12:19 am
#1354
I have posted a new firmware to handle such cases. It has the AT+XRST command which restarts the module. It works even when other commands return "busy...".
https://www.dropbox.com/s/838yu9k08ajpr ... T.zip?dl=0
https://www.dropbox.com/s/838yu9k08ajpr ... T.zip?dl=0
- Tue Oct 07, 2014 5:14 am
#1362
Thanks for the modified version 
I will still use the RESET pin tho as there may be more bugs in the SDK we have not discovered and hardware reset will work 100%.
I will still use the RESET pin tho as there may be more bugs in the SDK we have not discovered and hardware reset will work 100%.
- Tue Oct 07, 2014 10:24 pm
#1403
Spacejunkie - is your firmware based on the latest version i.e. 0018000902 (which is actuallly 922 but reports 902) with baud rate control) or an earlier one - if based on the latter this would be wonderful as that "busy" is a pain...
Peter Scargill - http://tech.scargill.net
