Callback (Network)
Associated with: WITS Outstations (with network connections)
Security permission required to access this pick action: Diagnostics
ClearSCADA has a Callback (Network) action that you can use to test a WITS Field Device's ability to initiate a network connection with ClearSCADA.
NOTE: For details on testing a WITS Field Device's ability to initiate a PSTN connection, see Callback (PSTN)
You can use the Callback (Network) action if:
- Your WITS Field Device supports Callback (see Display a WITS Device Profile)
- Callback is enabled on the Network tab of the Outstation Form (see Callback for WITS Network Connections)
- Your ClearSCADA user account has permission to access the Callback (Network) action (Diagnostic permission).
To instruct a WITS Field Device to initiate a connection with ClearSCADA (for testing purposes):
- Log on to ViewX via a User Account that has the Diagnostic permission.
- In the Database Bar, right-click on the WITS Outstation item that represents the Field Device you want to test.
- Select Callback (Network).
-
Enter the parameters for the connection you want to test. These are:
- Device Port—The port on the Field Device that is used for the connection to ClearSCADA.Typically, the Device Port is used to determine which network is used (when the Field Device is connected to multiple networks).
- Host Address—The IP address of the ClearSCADA server that is currently Main (unless the ClearSCADA servers are behind a router, in which case, the Host Address is the address of the router that forwards the connection to the Main server). The domain name of the ClearSCADA server may be used instead of the IP address (if supported by the Field Device).
-
Port—The TCP/IP port on which the ClearSCADA server 'listens' for a connection (unless the ClearSCADA servers are behind a router, in which case, the Port is the TCP/IP port of the router that forwards the connection). This should match the port that is specified in the configuration of the DNP3 Channel that is used by the Field Device:
- For Direct Outstation Sets, there is one channel.
- For Switched Outstation Sets, there are two channels. You need to choose the TCP/IP port for the channel currently being used by Outstation Set.
- For Shared Outstation Sets (independent), there are two channels. The TCP/IP port you need to select is dependent on the Inbound Connection setting (see Specify the Network-Connected Channels on Which the Driver Accepts Inbound Connections in the ClearSCADA Guide to Advanced Drivers). This will limit you to either one channel (the channel currently being used) or either channel.
- For Shared Outstation Sets (group slave), there are two channels. You need to select the TCP/IP port for the channel currently being used by the group master.
- For Shared Outstation Sets (fixed A or fixed B), there are two channels. You need to select the TCP/IP port of the appropriate fixed channel.
NOTE: If the Shared Listen Port feature is enabled (see Define whether a Listen Port can be Shared in the ClearSCADA Guide to Server Administration), connections can be transferred automatically to the 'correct' channel.
-
TCP/IP Type—The protocol used by the Field Device for the connection to ClearSCADA. The connection can only be initiated if both ClearSCADA and the Field Device are set to use the same TCP/IP Type.
NOTE: If the ClearSCADA server is connected to multiple networks, it may have more than one IP address or domain name. Therefore, you will need to select the correct combination of Device Port and Host Address.
- Select OK.
If the parameters are correct, a Callback request is sent to the Field Device. In response, the Field Device terminates communications with ClearSCADA, and then attempts to initiate a connection using the specified connection for the Callback.
If the Callback succeeds, an event is logged. The message of the event indicates that the Callback succeeded. You can view the event in the Events List (see Display the Events List for an Item or Group in the ClearSCADA Guide to Lists).
ClearSCADA will wait for a specified amount of time for a Callback to take place (see Define the WITS Callback Time Period). If the Callback does not occur during this time, ClearSCADA deems the Callback to have failed and generates an alarm.
NOTE: ClearSCADA will also generate an alarm for a failed Callback if a Callback is made via a different connection or if there are unexpected Callbacks.
You can view any Callback-related alarms in the Alarm Banner, Alarms List, and on other alarms displays. For details on how to access these displays, see: