What is “having stopped itself” ? Are you talking about modbus TCP/RTU, which variant? Is this an working instance with new issue or an fresh new setup ?
PS: There is option named Poll only on command in LineOptions>DevicePolling make sure it not ticked.
This reply was modified 4 months, 3 weeks ago by zzz.
The ‘Line Log’ for the Modbus TCP Communication Line has the following as its latest entry: “2024-04-11 15:02:50 Communication line [2] Modbus_TCP is stopped”
This was a previously working instance set up by the previous tech that I’m now trying to get back up and running.
DevicePolling is not ticked for any of the devices, but its not a device issue, it’s the entire Line.
Hello,
When the Communicator service starts, it starts all lines. If some line is not started, the info is written in ScadaComm.log
Try restarting the Communicator service and check ScadaComm.log for errors.
Thank you for the assistance, managed to resolve this issue.
One of the devices in the line was set up to use a module that wasn’t installed for some reason. Removed the device and the line is polling fine again.