watchdog restart limit

[kkontak]

Hi,
we are using a many LAN Controller tinycontrol units in our systems, mainly for the 6 remote ON/OFF Control Outputs feature and the IP Ping Watchdog feature.
We have v2.0 LAN Controller units as well as v3.0.
In the v2.0 units, the watchdog works forever, but in v3.0 it stops restarting after a defined limit up to 255 times in the settings field [Max Restarts] or [Limit of Restarts] in the newest v1.56a firmware.

Is there any way to make it work forever, without Restart limits, as in v2.0 ?

Thanks

[wilkxt]

Hi,
we are using a many LAN Controller tinycontrol units in our systems, mainly for the 6 remote ON/OFF Control Outputs feature and the IP Ping Watchdog feature.
We have v2.0 LAN Controller units as well as v3.0.
In the v2.0 units, the watchdog works forever, but in v3.0 it stops restarting after a defined limit up to 255 times in the settings field [Max Restarts] or [Limit of Restarts] in the newest v1.56a firmware.

Is there any way to make it work forever, without Restart limits, as in v2.0 ?

Thanks

If you set limit restart to 0?

[kkontak]

Hi,
we are using a many LAN Controller tinycontrol units in our systems, mainly for the 6 remote ON/OFF Control Outputs feature and the IP Ping Watchdog feature.
We have v2.0 LAN Controller units as well as v3.0.
In the v2.0 units, the watchdog works forever, but in v3.0 it stops restarting after a defined limit up to 255 times in the settings field [Max Restarts] or [Limit of Restarts] in the newest v1.56a firmware.

Is there any way to make it work forever, without Restart limits, as in v2.0 ?

Thanks

If you set limit restart to 0?

That would be the most logical way to implement the "forever" feature I seek.
I'm using this trick myself, when I write my own firmware for projects.

But I have tried that and: 
- in LK3 with Firmware Version 1.49b6, zero(0) value reacts as value 1. Meaning that it performs one restart cycle and stops the wathcdog.
- in LK3 with latest Firmware Version 1.56a, zero(0) value is not accepted at all. When pressing SAVE button, it replies with this error message "All fields are required".

Anything from 256 and above is treated as 8 bit value and it is truncated.
For example, 256 becomes 0, 257 becomes 1, 258 becomes 2, ...
For some reason, it accepts negative values but they are truncated as well.
-1 becomes 255 and so forth.

It should be a simple fix in the firmware.

[wilkxt]

Hi,
we are using a many LAN Controller tinycontrol units in our systems, mainly for the 6 remote ON/OFF Control Outputs feature and the IP Ping Watchdog feature.
We have v2.0 LAN Controller units as well as v3.0.
In the v2.0 units, the watchdog works forever, but in v3.0 it stops restarting after a defined limit up to 255 times in the settings field [Max Restarts] or [Limit of Restarts] in the newest v1.56a firmware.

Is there any way to make it work forever, without Restart limits, as in v2.0 ?

Thanks

If you set limit restart to 0?

That would be the most logical way to implement the "forever" feature I seek.
I'm using this trick myself, when I write my own firmware for projects.

But I have tried that and: 
- in LK3 with Firmware Version 1.49b6, zero(0) value reacts as value 1. Meaning that it performs one restart cycle and stops the wathcdog.
- in LK3 with latest Firmware Version 1.56a, zero(0) value is not accepted at all. When pressing SAVE button, it replies with this error message "All fields are required".

Anything from 256 and above is treated as 8 bit value and it is truncated.
For example, 256 becomes 0, 257 becomes 1, 258 becomes 2, ...
For some reason, it accepts negative values but they are truncated as well.
-1 becomes 255 and so forth.

It should be a simple fix in the firmware.

try this soft
  lk3_firmware_1_57a.zip (Rozmiar: 360.49 KB / Pobrań: 383)
for set 255 watchdoog should run forever

[kkontak]

Hi,
we are using a many LAN Controller tinycontrol units in our systems, mainly for the 6 remote ON/OFF Control Outputs feature and the IP Ping Watchdog feature.
We have v2.0 LAN Controller units as well as v3.0.
In the v2.0 units, the watchdog works forever, but in v3.0 it stops restarting after a defined limit up to 255 times in the settings field [Max Restarts] or [Limit of Restarts] in the newest v1.56a firmware.

Is there any way to make it work forever, without Restart limits, as in v2.0 ?

Thanks

If you set limit restart to 0?

That would be the most logical way to implement the "forever" feature I seek.
I'm using this trick myself, when I write my own firmware for projects.

But I have tried that and: 
- in LK3 with Firmware Version 1.49b6, zero(0) value reacts as value 1. Meaning that it performs one restart cycle and stops the wathcdog.
- in LK3 with latest Firmware Version 1.56a, zero(0) value is not accepted at all. When pressing SAVE button, it replies with this error message "All fields are required".

Anything from 256 and above is treated as 8 bit value and it is truncated.
For example, 256 becomes 0, 257 becomes 1, 258 becomes 2, ...
For some reason, it accepts negative values but they are truncated as well.
-1 becomes 255 and so forth.

It should be a simple fix in the firmware.

try this soft
for set 255 watchdoog should run forever

Thank you very much.
I'm testing the firmware a few days now and it seems to perform well.
The watchdog does not stop when it reaches 255 restarts, it loops to 0 and goes up again and again...

It would be good for other users, to add a note on the instruction manual and upload the firmware on the LK3 page.

We are planning to buy more LK in the future. Since the LK3 is not available anymore, I hope LK3.5 firmware will also add support for the 255(=forever) in watchdog.

Thanks again.

[wilkxt]

yes, now  in lk3.8 this futher it will be from soft v 1.34, but when put 0 then is unlimited restart

[kkontak]

Great, thanks