LM disconnects suddenly

[Hadeel]

Hi!

In our projects, LM sometimes stop responding. We cannot reach LM from browser and with scada API. However it reacts to ping command.
Sometimes it is possible to reach the page http://LM IP/apps/, but then when we try to go http://LM IP/scada-main we see a white blank page and then LM stops accepting any requests for a while. After a while it recovers but this happens often and often after the project started.

In our project we have, for example, :
1440 objects in total
500 event scripts
6 resident scripts

Does this issue sound familiar to you?

In the error log we get the temperature warning as below image sometimes so it has to do something with it?

Thank you so much!

[Daniel]

It sound like LM keeps rebooting for some reason. Look on the LEDs when this is happening. The errors you have is usually generated by high traffic. It can be simple script which sends many telegrams at once.
What CPU/IO and memory says?

[PassivPluss]

Install the prosesses app and watch the bus communication. Maybe some group adresses updates very often. What does all the event scripts do? Do you use checkwrite so they dont write the same value over and over?

[Hadeel]

Hi Daniel and PassivPluss!!

Thank you for your reply!
We checked the system up time but it's 106d 17h 23m so it seems that it did not reboot...
About the CPU/IO and memory, it has ups and downs...currently it shows the numbers below but I didn't get to check the number when it actually happens.

But as you said my event scripts are causing too much load because everytime there's a update in a status group address I notify that to a third party cloud server.

>>Do you use checkwrite so they dont write the same value over and over?

I really think I should use that "checkwrite"! I really wanted that function but I didn't know how. Could you tell me how can I use "checkwrite"?

[admin]

Post what you have in System config > Status > System log.
Why do you need 500 event scripts?

For grp.checkwrite see this: https://openrb.com/docs/lua.htm#grp.checkwrite
It is advised to use it instead of grp.write where applicable. Also consider using either virtual group address range or grp.checkupdate for values that should not be sent to KNX/TP bus.