Configuring DNP3 SCADAPack E Outstations
The DNP3 SCADAPack E driver can communicate with SCADAPack E outstations using permanent (‘direct’) communications or PSTN. The driver can also communicate with SCADAPack or other DNP3 devices that are connected to Geo SCADA Expert remotely, via other SCADAPack E outstations (see SCADAPack E Data Concentrators and Remote Outstations).
For each SCADAPack E outstation with which you want Geo SCADA Expert to communicate, you need to configure an appropriate type of DNP3 SCADAPack E Outstation item in the Geo SCADA Expert database.
The DNP3 SCADAPack E driver supports these types of DNP3 SCADAPack E Outstation:
For communicating with a SCADAPack E outstation using a permanent connection (for example, direct serial, radio, or network).
Depending on the system set-up, a DNP3 SCADAPack E Direct Outstation can belong to a DNP3 Direct Outstation Set, or a DNP3 Switched Outstation Set (see Configuring a DNP3 Outstation Set in the Geo SCADA Expert Guide to the DNP3 Driver).
A DNP3 SCADAPack E Direct Outstation can be a parent outstation for a DNP3 SCADAPack Remote E Outstation or a DNP3 SCADAPack Remote DNP3 Device.
A DNP3 SCADAPack E Direct Outstation can optionally be configured with PSTN fallback, so that the outstation can still communicate with the server if Geo SCADA Expert deems the direct channel to have failed.
For communicating with a SCADAPack E outstation using a dial-up modem. Each DNP3 SCADAPack E PSTN Outstation has to belong to a DNP3 PSTN Outstation Set.
A DNP3 SCADAPack E PSTN Outstation can be a parent outstation for a DNP3 SCADAPack Remote E Outstation or a DNP3 SCADAPack Remote DNP3 Device.
For communication with a SCADAPack E outstation that can use either of two channels. The outstation has to be associated with a DNP3 Shared Outstation Set (each outstation in a Shared Set can communicate with the server via either channel).
A DNP3 SCADAPack E Shared Outstation can be a parent outstation for a DNP3 SCADAPack Remote E Outstation or a DNP3 SCADAPack Remote DNP3 Device.
If the system set-up allows, a DNP3 SCADAPack E Shared outstation can optionally be configured with PSTN fallback so that the outstation can still communicate with the server if Geo SCADA Expert deems both direct channels to have failed.
UNEXPECTED BEHAVIOR OF APPLICATION
‘Heartbeating’ is not supported by SCADAPack E outstations. Attempts to use Heartbeating on such outstations may cause erroneous behavior.
For communicating remotely with devices other than SCADAPack E outstations, using the DNP3 protocol.
Geo SCADA Expert communicates with each Remote DNP3 Device via that device’s parent outstation. Depending on the system setup, the parent outstation can be either a DNP3 SCADAPack E Direct, PSTN, or Shared outstation.
The actual outstation with which you associate the points on a Remote DNP3 Device varies, depending on the device that scans the remote for point data (see With Which Database Item do I Associate each DNP3 SCADAPack Point?).
For communicating remotely with SCADAPack E outstations, using the DNP3 protocol.
Geo SCADA Expert communicates with each Remote E outstation via that outstation’s parent outstation. Depending on the system setup, the parent outstation can be either a DNP3 SCADAPack E Direct, PSTN, or Shared outstation.
The actual outstation with which you associate the points on a Remote E Outstation varies, depending on the device that scans the remote outstation for point data (see With Which Database Item do I Associate each DNP3 SCADAPack Point?).
If your database structure is ‘modular’ and Group Templates are used to store ‘model’ DNP3 SCADAPack E configuration, in addition to the above types of outstation, you can add this driver-specific ‘abstract’ outstation item to your Group Templates:
A DNP3 SCADAPack Remote DNP3 Device represents a generic (rather than E) DNP3 outstation. If you require an abstract item that can convert to a DNP3 SCADAPack Remote DNP3 Device, use an Abstract DNP3 Outstation, rather than an Abstract SCADAPack E Outstation.
You can only add Abstract Items to Group Templates. The abstract items appear as additional driver-specific entries when you display the context sensitive menu from a Group Template. As with other abstract items, in order to represent a ‘real’ outstation, you need to convert the abstract items into the required type of outstation within the Group Instances that reference the Group Template. For more information, see Add an Abstract Item to a Group Template in the Geo SCADA Expert Guide to Core Configuration.
This section covers configuration of SCADAPack E specific properties on the outstations mentioned above. The properties are displayed on various tabs on the outstations’ configuration Forms. The properties are used to specify properties that are downloaded to the SCADAPack E outstation—they do not provide any additional functionality in Geo SCADA Expert. For information on these SCADAPack E properties, see the references listed below.
Before you start using Geo SCADA Expert to configure DNP3 SCADAPack E outstations, ensure that you are aware of the information detailed in Notes on Configuring SCADAPack E Outstations, also see Scanning DNP3 SCADAPack E Outstations.
Use the DNP3 tab to:
- Specify the DNP3 properties that are common to many DNP3 outstations (see Configuring a DNP3 Outstation in the Geo SCADA Expert Guide to the DNP3 Driver).
If a Remote E Outstation or Remote DNP3 Device is Polled By a Data Concentrator, the only field that applies on the remote’s DNP3 tab is the Address field. Geo SCADA Expert ignores the configuration in the other fields on the tab. For such a setup, we suggest that you use the Remote DNP3 Device tab to Specify Which Devices Scan a Remote Outstation before configuring any properties on the DNP3 tab—most of the fields on the DNP3 tab become ‘grayed out’ once the configuration indicates that the remote is being polled by its Data Concentrator, rather than Geo SCADA Expert.
If a Remote E Outstation or Remote DNP3 Device is Polled By either the Master Station (Geo SCADA Expert) or both the Data Concentrator and Master Station, use the fields on the remote’s DNP3 tab to specify the settings that apply when Geo SCADA Expert polls (scans) the remote for data ‘transparently’ via that remote’s parent outstation.
Use the Security tab to:
- Specify the DNP3 Secure Authentication properties that are common to many DNP3 outstations (see Configure the Security Properties in the Geo SCADA Expert Guide to the DNP3 Driver).
For information on the additional Security Configuration properties supported by the DNP3 SCADAPack E driver, see Configure the Security Configuration Properties. (The Security Configuration properties are on the outstation’s SCADAPack tab.)
Use the SCADAPack tab to:
Use the Outstation Type tab to:
Use the Multiple Masters tab to:
Use the SCADAPack TCP/IP tab to:
Use the X.29/TC Comms tab to:
The configuration Forms for DNP3 SCADAPack Remote DNP3 Devices and DNP3 SCADAPack Remote E Outstations include a Remote DNP3 Device tab.
Use the Remote DNP3 Device tab to:
NOTE: When configuring a SCADAPack Remote DNP3 Device, or Remote E Outstation, Geo SCADA Expert automatically specifies the Outstation Set on the Outstation tab, once you specify the Parent Outstation on the Remote DNP3 Device tab, and save the configuration.
The DNP3 SCADAPack Remote DNP3 Device Form only includes one SCADAPack-specific tab—the Remote DNP3 Device tab. The other tabs on the Form are common to many DNP3 outstations (see Configuring a DNP3 Outstation in the Geo SCADA Expert Guide to the DNP3 Driver).
For information on configuring properties on the Direct, and PSTN tabs, see Configuring a DNP3 Outstation in the Geo SCADA Expert Guide to the DNP3 Driver.
Properties on the other tabs of each Outstation Form are common to outstations on many advanced drivers. For information, see Tabs on Outstation Forms in the Geo SCADA Expert Guide to Advanced Drivers.