tagging @Fan_Du and @maurice,
I made tests this week-end. Before going with my battery bank, I just downgraded the firmware from 51.0 (and 51.3) to 49.0 and left all the parameters (I even did not touch the wiring and my network) as before.
The result: no more reboot (fingers crossed) since 17 hours. Previously, I had multiple reboots along the day. I’ll let my T3-TB running with this config for more days and will let you know the story.
Look yourself below
Mike
note: at 00:00, it’s NOT a reboot but a reset of this variable at 0, through programming
So, I understand that the T3-XX reboot itself (latest firmwares) when there is a network problem (ping). But we can’t manage it (like: IF TIME = 00:00:00 AND PING=0 THEN reboot). And the variables are reset to 0, whatever their previous values .
Is it possible to avoid this ? Because loosing variables values is also difficult (running time, states, etc) and not predictable with spontaneous reboot. Variables that hold values even after a reboot ?
After 1 day and 3 hours with Firmware 49.0 (no spontaneous reboot):
Why this new firmware (51.0 / 51.3) leads to reboot in my case ?
Thank you