You can use the Server Configuration Tool’s Channel settings to define the Maximum Number of Consecutive Read Timeouts and the Maximum Number of Write Timeouts. These settings provide a limit for consecutive timeouts or late replies from a remote outstation. If the limit is reached, ClearSCADA deems the channel to have failed (but it will not fail the channel until that limit has been reached).
To set appropriate Maximum Number of Consecutive Read Timeouts and Maximum Number of Write Timeouts for your system, you need to have an understanding of:
- How ClearSCADA Uses the Consecutive Read and Write Timeouts
- Considerations when Setting the Maximum Consecutive Read/Write Timeouts.
You need to have a good understanding of your overall system, because the Maximum Number of Consecutive Read Timeouts and Maximum Number of Write Timeouts apply to each of the channels on your system. This means that you may need to compromise when applying your limits, as you will need to consider the overall effects of the limits, not just how they affect one particular driver or channel.
When you understand how the consecutive timeouts are used and are aware of the considerations you need to make, you can proceed to: