Forum Replies Created
-
Posts
-
There was an error in my description. The actual situation is as follows: my device cannot access the internet, and it supports the Modbus RTU protocol. I have installed another networked device on this equipment, which is custom-developed. It can connect to my cloud platform and is also connected to the non-internet-enabled device via 485. When the networked device connects to the cloud platform, it sends a hello packet.
I noticed that TcpServerChannelLogic has implemented hello packet handling, but it might not be able to collect a complete hello packet.
I have sent the faulty event file to your email address info@rapidscada.org with the subject “Event marker not found.” This issue not only causes the event file to become corrupted but also affects the files in the min, hour, and cur directories.
This scenario is easy to reproduce. The reproduction conditions are as follows:
1、You have a large amount of data that needs to be read and recorded.
2、You configure alarms for these data channels.
3、Frequent power outages and restarts occur.
This issue is quite serious as it has caused the data files and event files to become unreadable. Is there a timeline for the fix?
It is installed on an Ubuntu system. Personally, I find event loss acceptable, but I cannot accept file corruption. The problem now is that after corruption occurs, no more events are generated, and there is no automatic recovery mechanism.
