I also sent AT+CWMODE?, and received back CWMODE=2. When I returned, 3 or so hours later, I went straight to the project and checked AT, again, and it worked. I also tried AT+CWLAP, and got the word, error. Before I left I sent AT, several times, and got OK back every time. Yesterday afternoon I went out for several hours. So the answer is, no, there are no sleep settings on this laptop causing that.
Since that time, I have not changed my sleep settings. So I turned off all of the sleep settings and was able to save the data for as long as I had my laptop there and Cool Term running. When I later reviewed the text data file, I saw that it only saved data for as long as it took to match my sleep settings.
Later when I went back to check on the running of the project and the data being saved, I found that the computer screen was black. I had Cool Term put a time stamp on each row of data as it was being received and saved into the text file. On another project that I was working on a while back, I was using Cool Term, terminal program to to save some data to a text file. What is going on here? It seems that I can't count on it to continue working over time. I went through the same routine of switching baud to 74880, doing a reset, returning the baud to 115200, sending AT and got OK back. I went to gather my thoughts about the next thing that I wanted to do, and when I returned an hour later, when I entered AT, I got nothing back. And when I change the baud rate to 115200 baud, I finally did get an OK response from my AT sent.
COOLTERM CANT SEE NODEMCU SERIAL
I switch to using the Arduino IDE Serial Monitor set it to the 74880 baud rate and was very surprised to see what came up upon reset. I was using the Cool Term terminal program and was surprised to find that it doesn't have a 74880 baud rate setting. My setup differs from his though, in that, I am using a buck converter that I have adjusted to 3.4 volts, that seems to be supplying the voltage just fine. I would sure like to know if michaelb33 found resolution to his problem, since I am having a very similar issue going on. I have been following this thread in earnest since I have my own thread with a similar problem. Now to see if I'm pushing my luck with some other AT commands. I noticed also something else that I thought curious, that what gets placed on the serial monitor when pressing Reset is different from what I see by removing and returning power to CH-PD. I tried my AT and to my pleasant surprise, got OK back. I've never heard of "startup prints of AT firmware, but I was surprised to see that although it still returned gibberish, the gibberish was different. Then setting the baud to 115200 and again resetting by removing power from CH-PD would return the startup prints of the AT firmware. I had never read that disconnecting and reconnecting the CH-PD pin of the ESP8266-01 was another way of resetting the ESP8266-01, and would return the bootlog at 74880 baud. you should see the startup prints of the AT firmware" you should see the bootlog of the esp8266. "open Serial Monitor on COM port of the Uno/esp8266, set the baud rate to 74880 and reset the esp8266 by disconnecting the CH-PD and connecting it back. In reply #20, this morning at 3:07 AM he said,
He said to try something that I had never read about before. I just found something interesting that I read on another Arduino forum post from Juraj.
0 kommentar(er)
