[SOLVED] ESP8266 WDT reset
-
@Yveaux Thanks.. Good to know what I'm doing SHOULD work.. :-)
I have been storing everything in what I think is the default directory, which under my \users\sjones\Documents\Arduino\libraries. This is what the Arduino IDE is pointing to.
Under that directory, I removed the MySensors directory and extracted the new 2.0 one.. BUT, I do see that there are more modules than just those under MySensors, so even though I think those are supposed to NOT conflict with the default ones, I missed one?
Also, I dont understand why, but I see SOME arduino extension stuff under \program Files (x86)\arduino although I didn't see any MySensors information..
And, the only other thing I saw which I didn't know how it got there was the one referred to in the error: "C:\Users\sjones\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.2.0\libraries\ESP8266WiFi" Since that specifically was referred to in the error, I thought maybe I had an old version there, so I renamed the ESP8266Wifi directory to "old", figuring that whatever put it there in the first place would replace it with the current version if needed, but it didn't happen - it just failed to compile, complaining that it was missing, so I put it back..
I'm not near my home computer now, but maybe when I get home I'll try with a completely new windows profile (create a new user) and reinstall Arduino from scratch
Thanks for your help and patience!
-SteveHi @172pilot
I'm fairly certain from what you have described that you have NOT done this, but just in case I will mention it. Remember, simply renaming a folder within libraries (eg. 'MySensors' to 'MySensorsOLD') can cause grief as the old and new will both be compiled / seen by the linker.
I think your 'new user' idea will work.
FWIW: Some time ago I had a similar issue with a different library, I can't remember the details, but I found/fixed it by doing a global search of "C:" for various keywords (e.g. "ESP8" and "MySen" in your case). I ended up finding files I didn't realise were there.
Good luck!
Paul
-
Hi @172pilot
I'm fairly certain from what you have described that you have NOT done this, but just in case I will mention it. Remember, simply renaming a folder within libraries (eg. 'MySensors' to 'MySensorsOLD') can cause grief as the old and new will both be compiled / seen by the linker.
I think your 'new user' idea will work.
FWIW: Some time ago I had a similar issue with a different library, I can't remember the details, but I found/fixed it by doing a global search of "C:" for various keywords (e.g. "ESP8" and "MySen" in your case). I ended up finding files I didn't realise were there.
Good luck!
Paul
@AffordableTech @Yveaux
Thanks!I uninstalled Arduino completely, deleted everything I could find, and reinstalled from scratch, and after a bit of patience and rebooting the vera, I now have a functioning Wifi gateway using a Sparkfun 8266 Thing Dev board, and an NRF radio.. Then I was able to build a quick "Arduino switch" with an Uno and an NRF just to test, and it works great!!
Now it's time to get creative and build some stuff!
Thanks again!!
-Steve
-
Have had the GW running for a day now, as long as the client (Vera Edge) don't sent
0;255;3;0;9;Client 0: 2;1;1;0;24;Or I start up an new sensor it's stable and works well.
Problem now to figure out is how to connect a new sensor, as it restarts as soon as it's powered on.
Any ideas?Note. Noticed that it only restarts upon new sensor startup if the client is connected.
connected with Skoda, channel 6 dhcp client start... .ip:192.168.1.5,mask:255.255.255.0,gw:192.168.1.1 .IP: 192.168.1.5 0;255;3;0;9;Init complete, id=0, parent=0, distance=0 0;255;3;0;9;read: 1-1-0 s=0,c=1,t=1,pt=7,l=5,sg=0:39.8 0;255;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0: 0;255;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0: 0;255;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0:NO restart as the client is not connected
0;255;3;0;9;Client 0 connected 0;255;3;0;9;Client 0: 0;0;3;0;2;Get Version 0;255;3;0;9;Client 0: 0;255;3;0;9;Client 0: 0;0;3;0;5;1 0;255;3;0;9;Client 0: 0;255;3;0;9;read: 1-1-0 s=1,c=1,t=0,pt=7,l=5,sg=0:24.2 0;255;3;0;9;read: 1-1-0 s=0,c=1,t=1,pt=7,l=5,sg=0:39.7 0;255;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0: 0;255;3;0;9;Client 0: 255;255;3;0;4;3 Soft WDT resetHere is restarted, inclusion mode or not does not matter
@Kosika said:
Problem now to figure out is how to connect a new sensor, as it restarts as soon as it's powered on.
Any ideas?I have the same problem. I'm using the Esp8266Gateway sketch in the Lib v1.5 and have a NRF24 radio as described in the instructions.
Every time that I connect a new sensor, the MCU is restarting as you described. This is only happening when the Gateway is connected to a controller (Homeassistant or MYSController). If the gateway is not connected to any controller then it receive the data without any problem.@Kosika, How did you solved the problem?
-
@Kosika said:
Problem now to figure out is how to connect a new sensor, as it restarts as soon as it's powered on.
Any ideas?I have the same problem. I'm using the Esp8266Gateway sketch in the Lib v1.5 and have a NRF24 radio as described in the instructions.
Every time that I connect a new sensor, the MCU is restarting as you described. This is only happening when the Gateway is connected to a controller (Homeassistant or MYSController). If the gateway is not connected to any controller then it receive the data without any problem.@Kosika, How did you solved the problem?
-
@Kosika said:
Problem now to figure out is how to connect a new sensor, as it restarts as soon as it's powered on.
Any ideas?I have the same problem. I'm using the Esp8266Gateway sketch in the Lib v1.5 and have a NRF24 radio as described in the instructions.
Every time that I connect a new sensor, the MCU is restarting as you described. This is only happening when the Gateway is connected to a controller (Homeassistant or MYSController). If the gateway is not connected to any controller then it receive the data without any problem.@Kosika, How did you solved the problem?
-
-
@Yveaux said:
please switch to the new 2.0.0 library, for your gateway, repeaters and sensors.
Esp support has been improved in there, and developer support will be faster.Hello,
I switched to the new 2.0.0 and I still have the same problem:connected with AFENO_DD, channel 6 dhcp client start... 0;255;3;0;9;TSM:READY f r-40, scandone .....ip:192.168.1.82,mask:255.255.255.0,gw:192.168.1.1 .IP: 192.168.1.82 0;255;3;0;9;No registration required 0;255;3;0;9;Init complete, id=0, parent=0, distance=0, registration=1 0;255;3;0;9;TSP:MSG:READ 6-6-255 s=255,c=3,t=7,pt=0,l=0,sg=0: 0;255;3;0;9;TSP:MSG:BC 0;255;3;0;9;TSP:MSG:FPAR REQ (sender=6) 0;255;3;0;9;TSP:CHKUPL:OK (FLDCTRL) 0;255;3;0;9;TSP:MSG:GWL OK pm open,type:2 0 Soft WDT reset ctx: cont sp: 3ffef6b0 end: 3ffefa30 offset: 01b0 >>>stack>>> 3ffef860: 00000000 3ffefd08 3ffefd08 402048bb 3ffef870: 40107050 00000000 3ffefd08 402048bb 3ffef880: 00000000 3ffefd08 00000000 4020230f 3ffef890: 001e8480 3ffe0001 3ffefa8f 40202376 3ffef8a0: 00000000 0000000e 00000000 00000006 3ffef8b0: 00000000 00000000 00000006 00000006 ...What could be the reason for the reset?
Is it OK to power the NodeMCU from the microUSB?Thank you!
-
@Yveaux said:
please switch to the new 2.0.0 library, for your gateway, repeaters and sensors.
Esp support has been improved in there, and developer support will be faster.Hello,
I switched to the new 2.0.0 and I still have the same problem:connected with AFENO_DD, channel 6 dhcp client start... 0;255;3;0;9;TSM:READY f r-40, scandone .....ip:192.168.1.82,mask:255.255.255.0,gw:192.168.1.1 .IP: 192.168.1.82 0;255;3;0;9;No registration required 0;255;3;0;9;Init complete, id=0, parent=0, distance=0, registration=1 0;255;3;0;9;TSP:MSG:READ 6-6-255 s=255,c=3,t=7,pt=0,l=0,sg=0: 0;255;3;0;9;TSP:MSG:BC 0;255;3;0;9;TSP:MSG:FPAR REQ (sender=6) 0;255;3;0;9;TSP:CHKUPL:OK (FLDCTRL) 0;255;3;0;9;TSP:MSG:GWL OK pm open,type:2 0 Soft WDT reset ctx: cont sp: 3ffef6b0 end: 3ffefa30 offset: 01b0 >>>stack>>> 3ffef860: 00000000 3ffefd08 3ffefd08 402048bb 3ffef870: 40107050 00000000 3ffefd08 402048bb 3ffef880: 00000000 3ffefd08 00000000 4020230f 3ffef890: 001e8480 3ffe0001 3ffefa8f 40202376 3ffef8a0: 00000000 0000000e 00000000 00000006 3ffef8b0: 00000000 00000000 00000006 00000006 ...What could be the reason for the reset?
Is it OK to power the NodeMCU from the microUSB?Thank you!
@afeno what esp arduino core are you using? Try updating to the latest version.
I have an esp gateway running (2.0.0, fixed ip, mqtt client, powered through micro USB) without any issues. Power could be insufficiently stable though, so you could also try switching the power supply. -
@afeno what esp arduino core are you using? Try updating to the latest version.
I have an esp gateway running (2.0.0, fixed ip, mqtt client, powered through micro USB) without any issues. Power could be insufficiently stable though, so you could also try switching the power supply.@Yveaux ,
I tried with the esp mqtt client and I have similar issues. The node is reseting when receiving the radio signal.This is the log:
ž ¡9 C~0;255;3;0;9;Starting gateway (RNNGE-, 2.0.0) 0;255;3;0;9;TSM:INIT 0;255;3;0;9;TSM:RADIO:OK 0;255;3;0;9;TSM:GW MODE scandone state: 0 -> 2 (b0) state: 2 -> 3 (0) state: 3 -> 5 (10) add 0 aid 4 cnt chg_B1:-40 0;255;3;0;9;TSM:READY f r-40, scandone . connected with AFENO_DD, channel 6 dhcp client start... ..ip:192.168.1.82,mask:255.255.255.0,gw:192.168.1.1 .IP: 192.168.1.82 0;255;3;0;9;No registration required 0;255;3;0;9;Init complete, id=0, parent=0, distance=0, registration=1 IP: 192.168.1.82 0;255;3;0;9;Attempting MQTT connection... 0;255;3;0;9;MQTT connected 0;255;3;0;9;TSP:MSG:READ 6-6-255 s=255,c=3,t=7,pt=0,l=0,sg=0: 0;255;3;0;9;TSP:MSG:BC 0;255;3;0;9;TSP:MSG:FPAR REQ (sender=6) 0;255;3;0;9;TSP:CHKUPL:OK (FLDCTRL) 0;255;3;0;9;TSP:MSG:GWL OK Soft WDT reset ctx: cont sp: 3ffef6d0 end: 3ffefa50 offset: 01b0 >>>stack>>> 3ffef880: 00000000 3ffefc24 3ffefc24 40204d27 3ffef890: 40107050 00000000 3ffefc24 40204d27 3ffef8a0: 00000000 3ffefc24 00000000 40202336 3ffef8b0: 001e8480 3ffe0001 3ffefaaf 40202336 3ffef8c0: 00000000 0000000e 00000001 00000006 3ffef8d0: 00000000 00000000 00000006 00000006 3ffef8e0: 00000030 0000000e 00001928 402023d1 3ffef8f0: 00000001 3ffefaa8 00000006 402024ce 3ffef900: 00000008 00000006 3fff129c 00000027 3ffef910: 00000001 00000006 3ffefaa8 402035bc 3ffef920: 40107050 3ffef981 3ffefc24 00000061 3ffef930: 3ffef980 3ffefc24 3ffef980 40202336 3ffef940: 401054b2 000e937d 3ffefc24 3ffefc68 3ffef950: 4010556e 3ffee428 000e937d 00000000 3ffef960: 40105740 000e937d 3ffefc68 00000006 3ffef970: 000000ff 3ffefaa8 00000006 402026dd 3ffef980: 3ffefa06 00000006 40203bc8 00000006 3ffef990: 000000ff 3ffefaa8 00000006 402036fd ...:(
-
I didn't give up (yet...) I tried today to power the NRF from an external power supply. Same result. The esp8266 is rebooting after receiving some data as shown above. My conclusion is that the problem is on the esp8266 itself or in the power supply that I am using.
My last try will be to power the esp8266 from something different than the microUSB.
Just in case, this is the setup. Maybe I'm missing something very basic:
Regaards,
Alfredo. -
I didn't give up (yet...) I tried today to power the NRF from an external power supply. Same result. The esp8266 is rebooting after receiving some data as shown above. My conclusion is that the problem is on the esp8266 itself or in the power supply that I am using.
My last try will be to power the esp8266 from something different than the microUSB.
Just in case, this is the setup. Maybe I'm missing something very basic:
Regaards,
Alfredo. -
@afeno hard to tell from the picture, but it looks like CE is connected to D1, instead of D2.
Please refer to the connection diagram here: https://www.mysensors.org/build/esp8266_gateway -
@Yveaux , did you know that you are awesome?
There is an error on Pin labels!!! The print on the pcb is wrong. You are right!
I have two D2 and of course that I used the wrong one
Thank you so much!!!!
