Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
📖HomeBack There are a number of ways of determining the status of a control action to the outstation.
Confirmation Events
Whenever a user initiates a control, an event will be logged in the event list to log the request. In the default course of events, a second event will be logged to indicate the successful completion of the control. The notification event is controlled through the use of the severity fields in the control aggregate for the output point. If the severity is set to None, then no event will be logged when the control is completed. Other severities will result in an event of that severity being logged when either the control was successful, or the control failed for some reason. If the control failed, the event will indicate the reason for failure.
Color Indication
When a control is initiated on a point in the database, ClearSCADA will change the foreground property of that point to indicate that it is in the control pending state. By default, this means that points with controls pending will indicate this state through flashing blue text. If the control is successful, then the color will return to the normal black state. If the control fails, an alarm will be raised in the alarm list, and the foreground colors will indicate the alarm states.
Note that these colors assume that they have not been changed from the defaults in the color palette.