08-03-2022, 04:17 PM
Good day, I am sending a description of the problem with tinycontrol, the unit dies after 10 minutes.
Bootloader SW=1.3
LK HW=3.8
HW version 3.8
SW version 1.52
set ip address
ip 172.16.32.124
mask 255.255.224.0
gw 172.16.32.254
dns 172.16.32.254
after approx. 10 minutes after switching on, the following state will occur
tinycontrol is taking a long time to respond to ping
from 200ms to 3900ms and then the unit stops responding to ping completely.
the http or https interface is not available at this time.
after reboot everything works normally.
When the ping starts to get longer, the putty console starts to be written out:
http_poll: too many retries, close
When i was changed the default ip address 192.168.1.100,
after the changing the result is the same.
When i was enabled HTTPS /same result
When i was changed fw from 1.49 to 1.52 / result same unit is unavailable.
ping responses:
Reply from 172.16.32.124: bytes=32 time<1ms TTL=255
and the next ping not respond, there is no increase in delay.
the length of the run is 4-10 min.
disconnecting the eth cable and re-connecting it has no effect on the status.
I am attaching the log from the putty console.
Please help to solve the problem.
Thank you in advance for your reply Tomas Hofman
xfd
Bootloader SW=1.3
LK HW=3.8
HW version 3.8
SW version 1.52
set ip address
ip 172.16.32.124
mask 255.255.224.0
gw 172.16.32.254
dns 172.16.32.254
after approx. 10 minutes after switching on, the following state will occur
tinycontrol is taking a long time to respond to ping
from 200ms to 3900ms and then the unit stops responding to ping completely.
the http or https interface is not available at this time.
after reboot everything works normally.
When the ping starts to get longer, the putty console starts to be written out:
http_poll: too many retries, close
When i was changed the default ip address 192.168.1.100,
after the changing the result is the same.
When i was enabled HTTPS /same result
When i was changed fw from 1.49 to 1.52 / result same unit is unavailable.
ping responses:
Reply from 172.16.32.124: bytes=32 time<1ms TTL=255
and the next ping not respond, there is no increase in delay.
the length of the run is 4-10 min.
disconnecting the eth cable and re-connecting it has no effect on the status.
I am attaching the log from the putty console.
Please help to solve the problem.
Thank you in advance for your reply Tomas Hofman
xfd
Greetings Tom