Is anyone here using this ESP8266 IOT module?



I have finally gotten it to work, but it was non-trivial. It is supposed to communicate via UART at 115200 baud. It eventually does, but on startup it puts out a bunch of status info at 74600 baud (determined by using my scope) before switching to 115200 for the UI. It really does this, I have verified by sending it to a terminal emulator and if I set the baud at 74600, the status info comes out correct, but the ready message is garbled. If it set it to 115200, it is reversed. Only the ready message comes out non-garbled. I now have it working controlled by a micro by setting the speed to 115200 and ignoring everything until I see "ready<cr><lf>". The status info shows the date of Jan 8 2013, which I presume is the firmware version, so quite old.

Is this normal , or did it get a batch with a bogus version of the firmware installed? If others have used this and do not see this anomaly, I might try to re-program one of them with a newer version of the firmware, but I would like to know if that will change anything before I waste my time trying it.

Bob

 

it’s been awhile, but isn’t that the default boot vector until you load your code. I don’t recall it being a problem.

 

I an not planning on adding code to it, I intend to use the AT commands to talk to it from a PIC.

Bob

 

That is an old build. I don't know what the current version is, but I have seen at least 2015 builds.

Did you try AT+CIOBAUD=115200? It's supposed to make a permanent change to the default data rate though I have no idea if it will change the boot rate.

EDIT: I always load new firmware, so aside from a very brief investigation of the AT command set, I haven't really used it.

 

It is normal. They boot at 74600 then switch to 115200 after boot.

 

It is normal. They boot at 74600 then switch to 115200 after boot.

Thanks, I guess for now, I will just skip over the garbage and not update.

Bob