31.12.2019, 08:21
Hi,
I saw on LM3 V2 and LM4 that it in some circumstances can freeze and to solve this issue it must be restarted.
I remember such example:
https://openrb.com/automatic-monitoring-...processes/
I remember also that it was contained in firmware so there is no need to do it by user.
But probably it is not working properly, because e.g. I have LM3 V2 with not so old firmware and from time to time I have such issue. When it is freezed I cannot reach it in network and modbus isn't working.
I've tried to solve the reason of this problem in below post:
https://forum.logicmachine.net/showthrea...hlight=cpu
This post is from other perpective. LM should autoreboot when it detects too high load. Probably such reaction should be parametrized e.g. for one user CPU load > 1.00 for 1 minute would be good for other permanent 3.00 is ok.
I saw on LM3 V2 and LM4 that it in some circumstances can freeze and to solve this issue it must be restarted.
I remember such example:
https://openrb.com/automatic-monitoring-...processes/
I remember also that it was contained in firmware so there is no need to do it by user.
But probably it is not working properly, because e.g. I have LM3 V2 with not so old firmware and from time to time I have such issue. When it is freezed I cannot reach it in network and modbus isn't working.
I've tried to solve the reason of this problem in below post:
https://forum.logicmachine.net/showthrea...hlight=cpu
This post is from other perpective. LM should autoreboot when it detects too high load. Probably such reaction should be parametrized e.g. for one user CPU load > 1.00 for 1 minute would be good for other permanent 3.00 is ok.
Done is better than perfect