Chat freely about anything...

User avatar
By scargill
#2522 Busy has little to do with routers - if you check elsewhere there is a condition which I've never seen satisfactorily explained OR resolved where the board goes into some kind of "busy" mode and returns the message "busy s". I only wish my Linux skills were a little better as I'd go in there and fix it myself. It is just about the only thing now that's deterring me from shoving these boards into a variety of projects.
User avatar
By ardhuru
#2533 Did you start having this 'busy now' issue since trying to attempt to connect to your router?

That is how my problem began, and the reason was that I had defined a wrong password to connect to the router. So the chip continuosly keeps trying, unsucessfully, to log in. The solution is to disengage the attempts by AT+CWQAP, followed immediately by a re-assignation of the SSID and the password. Also, remember, your password and SSID are case sensitive. (this is where I had messed up)

Hope this helps!