[Solved] MySensors 2.0 Ethernet gateway (ENC28J60) restart / IP issue
-
May have spoken to soon....
Although the gateway now runs, after a few mins it seems to die. LAN leds keep blinking everything seems in order, but it's not pingable anymore and Domoticz starts logging messages that the gateway is unreachable. Is this somehow related? Or is this a whole different issue?
@tekka probably knows what to do, right? :D
-
@intellium can you add a serial print in loop() to see if the GW or the lan module freezes?
@tekka Sorry it took a while.
I gave it a try, but ever since adding print statements to the gateway loop(), the sensor nodes stopped communicating with it given FPAR failures. Even when I remove the print statements and return to the previous state, it keeps on giving FPAR failures on all sensor nodes... What would cause this ?
-
@tekka Sorry it took a while.
I gave it a try, but ever since adding print statements to the gateway loop(), the sensor nodes stopped communicating with it given FPAR failures. Even when I remove the print statements and return to the previous state, it keeps on giving FPAR failures on all sensor nodes... What would cause this ?
-
@intellium hmm, hard to diagnose without additional information - could be power-related. Can you add a better/stronger power-supply?
@tekka Before I go the route of messing with the power supply, I did some fiddling...
I added the following statements to both the gateway and the sensor sketches:
//LOW POWER MODE RADIO #define MY_RF24_PA_LEVEL RF24_PA_LOW //DEBUG FOR RADIO #define MY_DEBUG_VERBOSE_RF24 //RADIO THROUGHPUT #define MY_RF24_DATARATE RF24_1MBPSNext I put them a little bit closer together (around 80cm apart). The FPAR:FAIL message are gone now. I see in the output on the Sensor node that it communicates with the gateway. Currently, the gateway is running with this setup and the controller (Domoticz) gets values. So this seems to be working OK.
However, on the sensor node, the log sometimes indicates an error. Something like this :
RF24:write register, reg=0, value=14 RF24:open writing pipe, recipient=0 RF24:write register, reg=10, value=0 RF24:write register, reg=16, value=0 RF24:send message to 0, len=12 RF24:flushTX RF24:write register, reg=7, value=48 RF24:MAX_RT RF24:flushTX RF24:start listening RF24:write register, reg=0, value=15 RF24:write register, reg=10, value=1 !TSP:MSG:SEND 1-1-0-0 s=1,c=1,t=0,pt=7,l=5,sg=0,ft=4,st=fail:29.0 T: 29.00 RF24:write register, reg=0, value=12 RF24:power down RF24:write register, reg=0, value=12 RF24:power down RF24:stop listening RF24:write register, reg=0, value=14 RF24:open writing pipe, recipient=0 RF24:write register, reg=10, value=0 RF24:write register, reg=16, value=0 RF24:send message to 0, len=12 RF24:flushTX RF24:write register, reg=7, value=48 RF24:start listening RF24:write register, reg=0, value=15 RF24:write register, reg=10, value=1 TSP:MSG:SEND 1-1-0-0 s=0,c=1,t=1,pt=7,l=5,sg=0,ft=5,st=ok:36.0 H: 36.00 RF24:write register, reg=0, value=12 RF24:power downFrom what I've read, the st:fail means there was an error transmitting the value. Could this still be power related ? It seems so intermittent to me that my gut tells me power isn't the issue.
-
@tekka Next I tried is adding a capacitor to both the gateway and node RF module. I added a 10uF capacitor to both of them. This seems to have stabilized RF communication. I'm not seeing any failures anymore and data is flowing...
Back to the original issue... The gateway that seems to die...
I've added some debug statements to the loop() to see if this would keep on running when the gateway seemingly dies.
After 2 hours of operation, the gateway stopped responding to pings, and the controller also noticed the gateway was not alive anymore. When this happens, the output of the serial console is :New loop iteration: 21734 New loop iteration: 21735 New loop iteration: 21736 New loop iteration: 21737 New loop iteration: 21738 New loop iteration: 21739 New loop iteration: 21740 New loop iteration: 21741 New loop iteration: 21742 New loop iteration: 21743 New loop iteration: 21744As you can see, my loop code keeps on running at this point, suggesting it's just the ENC interface thats no longer reachable or has an issue. When I close and re-open the serial port monitor from the Arduino IDE, the gateway springs back to life and everything starts working again.
-
@intellium Issues with ENC: https://forum.arduino.cc/index.php?topic=398258.0
sounds pretty much the same...
-
@intellium Issues with ENC: https://forum.arduino.cc/index.php?topic=398258.0
sounds pretty much the same...
-
Just a little update:
I build a serial gateway and attached it to Domoticz. Been working ever since, even during the night. Guess this is the way to go for now.
@intellium Sounds good - fyi, I'm using both, W5100 and ESP8266-based GWs, w/o issues.
-
@intellium Sounds good - fyi, I'm using both, W5100 and ESP8266-based GWs, w/o issues.
@tekka I've got a bunch of esp8266 modules laying around. Maybe I'll just search how to wire those up to my nano's and find some code to run it as a dedicated gateway / sensor node. I've noticed the site uses a NodeMCU board for this instead of an Arduino (Nano) ?
-
Having the exact issue as the OP, but then with a W5100 shield and a NRF24.
Reverting back to MySensors 1.5.4 solves the problem.
Now i was on a beta of 2.0 that i uploaded to the gateway quite some time ago, and this worked without issues
Something has changed in the final 2.0 release... and i want to revert that change ;) -
Having the exact issue as the OP, but then with a W5100 shield and a NRF24.
Reverting back to MySensors 1.5.4 solves the problem.
Now i was on a beta of 2.0 that i uploaded to the gateway quite some time ago, and this worked without issues
Something has changed in the final 2.0 release... and i want to revert that change ;) -
No, the Node is resetting itself with the messages in the first post.
If i disable debug, it is logging the IP Address over and over again (each second), connection is reset at that moment -
The sketch is 99,999% the same as 'GatewayW5100' except i changed:
#define MY_IP_ADDRESS 192,168,0,50The default Arduino ethernet server examples work perfectly
Thanks in advance !
-
@tekka said:
@GizMoCuz did you uncomment
#define MY_DEBUGas suggested above?
Yep, see three posts up (If i disable debug, it is logging the IP Address over and over again (each second), connection is reset at that moment)
And unfortunately does not explain why version 1.5 is running (but missing important features/fixes)
-
@tekka said:
@GizMoCuz did you uncomment
#define MY_DEBUGas suggested above?
Yep, see three posts up (If i disable debug, it is logging the IP Address over and over again (each second), connection is reset at that moment)
And unfortunately does not explain why version 1.5 is running (but missing important features/fixes)
