Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Geo SCADA Knowledge Base
Access vast amounts of technical know-how and pro tips from our community of Geo SCADA experts.
Link copied. Please paste this link to share this article on your social media post.
Originally published on Geo SCADA Knowledge Base by Anonymous user | June 09, 2021 05:36 PM
Section | Name | Description | |
Scan Parameters | Transaction Attempts | The number of AL attempts before failing the communications to this outstation. This is independent of the Application Fragment Attempts and allows ClearSCADA to maintain communications as healthy even if one message to the outstation was unsuccessful. | |
| Inter Message Delay | The delay between messages to the same outstation. So if a message is received by ClearSCADA and the delay is 10ms, ClearSCADA will wait 10ms before sending the response. Useful for throttling network utilization. | |
| Reestablishment Interval | Once an outstation has failed, this time determines how often ClearSCADA tries to reestablish communications to the outstation. Between each failure, this time period will elapse before the next attempt. | |
Communications Parameters | Enabled | Determines whether DNP3 timeout settings are used or the generic Advanced Driver timing behavior. This should ALWAYS be set to true. | |
| Request Data Link Confirmation | This setting controls whether ClearSCADA requires a LL confirmation when sending messages. The LL confirm allows the failed link layer frame (which is much smaller) to be retried, rather than failing the whole AL message and retransmitting all data. There are three settings: Never, Sometimes and Always. Never means never request a confirmation from the outstation to each link layer frame, Always means always request one. Sometimes means only request a LL confirm message from the outstation if ClearSCADA will be sending more than one LL frame. | |
| Data Link Retries | Determines how many retries ClearSCADA will perform on a single LL frame. | |
| Data Link Timeout | Determines how long ClearSCADA should wait after sending a LL frame for the confirm from the outstation. | |
| Application Fragment Attempts | Determines how may AL message attempts ClearSCADA should perform. Each AL message could contain multiple LL failures, with the message being successfully retried at the LL level. This does not impact the AL message as long as all data is received successfully by the AL. | |
| Application Fragment Timeout | Determines how long ClearSCADA should wait for a valid AL response before timing out the AL message and retrying. | |
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.