Handling Communication Errors in Reports
You can handle errors in communication with I/O
Devices (for example, an I/O Device does not initialize properly at
startup or goes offline while CitectSCADA is running) in two ways:
- You can write communication
errors and invalid data to the report as error codes.
- You can disable the running of
reports that are triggered from an I/O Device, if communication
with the I/O device has been lost.