W5100 Gateway hangs /freezes after some time.
-
Thank for the hint, I was able to invested the issue more. Here the result:
Sketch uses 19560 bytes (60%) of program storage space. Maximum is 32256 bytes. Global variables use 981 bytes (47%) of dynamic memory, leaving 1067 bytes for local variables. Maximum is 2048 bytes.@webstor No it's pingable but their some timeout.
Request timeout for icmp_seq 115 Request timeout for icmp_seq 116 64 bytes from 1.1.0.130: icmp_seq=117 ttl=128 time=0.693 ms 64 bytes from 1.1.0.130: icmp_seq=118 ttl=128 time=0.694 ms 64 bytes from 1.1.0.130: icmp_seq=119 ttl=128 time=0.656 ms 64 bytes from 1.1.0.130: icmp_seq=120 ttl=128 time=3.135 ms 64 bytes from 1.1.0.130: icmp_seq=121 ttl=128 time=0.641 ms 64 bytes from 1.1.0.130: icmp_seq=122 ttl=128 time=0.618 ms 64 bytes from 1.1.0.130: icmp_seq=123 ttl=128 time=0.861 ms 64 bytes from 1.1.0.130: icmp_seq=124 ttl=128 time=3.536 ms Request timeout for icmp_seq 125 Request timeout for icmp_seq 126 Request timeout for icmp_seq 127 Request timeout for icmp_seq 128 64 bytes from 1.1.0.130: icmp_seq=129 ttl=128 time=0.494 ms 64 bytes from 1.1.0.130: icmp_seq=130 ttl=128 time=0.563 ms 64 bytes from 1.1.0.130: icmp_seq=131 ttl=128 time=0.622 ms 64 bytes from 1.1.0.130: icmp_seq=132 ttl=128 time=0.643 ms Request timeout for icmp_seq 133 Request timeout for icmp_seq 134 Request timeout for icmp_seq 135 Request timeout for icmp_seq 136 Request timeout for icmp_seq 137 64 bytes from 1.1.0.130: icmp_seq=138 ttl=128 time=0.828 ms 64 bytes from 1.1.0.130: icmp_seq=139 ttl=128 time=0.570 ms 64 bytes from 1.1.0.130: icmp_seq=140 ttl=128 time=0.766 ms 64 bytes from 1.1.0.130: icmp_seq=141 ttl=128 time=0.673 ms 64 bytes from 1.1.0.130: icmp_seq=142 ttl=128 time=3.274 ms 64 bytes from 1.1.0.130: icmp_seq=143 ttl=128 time=0.662 ms 64 bytes from 1.1.0.130: icmp_seq=144 ttl=128 time=0.714 ms Request timeout for icmp_seq 145 Request timeout for icmp_seq 146 64 bytes from 1.1.0.130: icmp_seq=147 ttl=128 time=0.663 ms 64 bytes from 1.1.0.130: icmp_seq=148 ttl=128 time=3.395 ms 64 bytes from 1.1.0.130: icmp_seq=149 ttl=128 time=0.660 ms 64 bytes from 1.1.0.130: icmp_seq=150 ttl=128 time=3.527 ms 64 bytes from 1.1.0.130: icmp_seq=151 ttl=128 time=0.650 ms 64 bytes from 1.1.0.130: icmp_seq=152 ttl=128 time=0.629 ms 64 bytes from 1.1.0.130: icmp_seq=153 ttl=128 time=0.565 ms 64 bytes from 1.1.0.130: icmp_seq=154 ttl=128 time=0.639 msSame test after reset, GW keep dropping but this time with max of 2 drop per ten ping. Other devices (phone, bridge etc...) can be pinged without timeout and I'm on the same network.
For the communication testing, I'm sending payload to my tv sensor, and I made a video showing the GW status led when he doesn't work:
and
After resetLook like it's a reset on the first video?
Next test, new sketch with debug on, sending same payload, GW always receive something like:
0;255;3;0;9;Eth: 2;3;1;0;32;10 0;255;3;0;9;TSF:MSG:SEND,0-0-2-2,s=3,c=1,t=32,pt=0,l=2,sg=0,ft=0,st=OK:10Some time even when payload is received, TV doesn't turn on, also tested with a simple light sensor. GW and TV are in the same room.
So look like GW is dropping some message, I'll try tomorrow to get back to previous AVR, if their no hint.
-
Hi guys, I may found the issue.
GW was powered from the NAS (for month) and I switched for a wall adapter. Now I'm able to ping GW without timeout...sorry (I see you guys coming....obviously it's a power issue :D !). GW has been running for one days now.
Note: I'm using AVR 1.6.16 now, but i'm pretty sure, power was the real issue.
