Connecting to DNP3 Devices

The DNP3 module allows the Ignition OPC-UA server to communicate with other devices that support the DNP3 protocol (DNP3 outstations).

To connect Ignition to a DNP3 device

  1. Go to the Configure section of the Gateway webpage.

  2. Scroll down and select OPC-UA > Devices.

  3. On the Devices page, find the orange arrow and click on Create new Device.

  4. On the Add Device Step 1: Choose Type page, select DNP3 Driver, and click Next.

  5. On the New Device page, leave all the default values and type in the following fields:

    Name: DNP3
    Hostname: type the IP address, for example 10.20.8.51

  6. You can check the box for Show advanced properties? to see the additional settings, but you can keep all the defaults.

  7. Click Create New Device.
    The Devices page is displayed showing the DNP3 device is successfully created and added to Ignition. The Status will show as Disconnected and then Connected or Idle, depending on the status of the device.

On this page...

Connection Settings

General
Name

The name of this DNP3 device connection.

Description

Device connection description (optional). Can be used to provide any useful information / comments about this connection.

Enabled

If True (checked), the connection is enabled; if False ( unchecked), the connection is disabled.

Main
Hostname

The IP Address of the Modbus device.

Port

The port to use when connecting to a DNP3 device. The default port is 20000.

Source Address

The address of the master station, default is 3.

Destination Address

The address of the outstation, default is 4.

Integrity Poll Interval

The interval at which to perform an integrity poll, in millis, default is 3,600,000.

Direct Operate Enabled

When true, the Direct-Operate function code is used on a write, otherwise Select-Operate is used, default is true.

Unsolicited Messages Enabled

When true, the outstation may send unsolicited messages for Class 1, 2, and 3 data, default is false.

Advanced

 

Message Fragment Size

The maximum size of a message fragment in the application layer, default is 249.

Message Timeout

The amount of time to wait for a message response from the outstation, default is 5,000.

Retries

The number of retries on a message timeout, default is 0.

Link Layer Confirmation

When true, a link layer confirmation will be required from the outstation when sending messages, default is false

Notes

  • Source Address and Destination Address: These addresses are assigned to the computers and should be the same across all settings, because of this the settings in Ignition and the settings in the device are the opposite of each other. For example, if the device is configured with an address of 4 and Ignition has an address of 3:

    • the settings in Ignition should have the Source Address set to 3 and the Destination Address set to 4.

    • the settings in the Device should have the Source Address set to 4 and the Destination Address set to 3.

  • Unsolicited messages enabled property: setting this property to True (checking the box) allows the outstation to send unsolicited messages to Ignition. This means that Ignition will connect to the outstation, but not request any data from it. Ignition waits for the outstation to send data. Not all devices support this option; those that do need to be configured to use it. Please refer to your device's documentation for more information.

Internal Indicators

Each response received from a connected outstation will contain an Internal Indication (IIN) bit field. This field indicates certain states or error conditions in the outstation. IINs are mapped to read-only points, indicating the following:

  • Broadcast message received (Broadcast)

  • Additional Class 1, 2, or 3 event data is available (Class 1 Events, Class 2 Events, Class 3 Events)

  • Time synchronization required in the outstation (Need Time)

  • Some output points are in local mode (Local Control)

  • An abnormal condition exists (Device Trouble)

  • The outstation device has restarted (Device Restart)

  • Function code not implemented (No Func Code Support)

  • Object Unknown (Object Unknown)

  • Request parameter error (Parameter Error)

  • Outstation event buffer overflow (Event Buffer Overflow)

  • An operation is already executing (Already Executing)

  • Configuration corrupt (Config Corrupt)

Terminology

  • unsolicited response: An Application Layer message from an outstation to a master for which no explicit request was received. The request is implied by the act of a master enabling unsolicited reporting of various points within an outstation.

  • integrity poll: Requests all event data, followed by the static data of all points assigned to one of the four classes (static Class 0 or event Class 1, 2, or 3).

  • DNP3TIME: Univeral Coordinated Time (UTC) time expressed as the number of milliseconds since the start of January 1, 1970. The effective date for using the UTC time base is January 1, 2008. Prior to this, DNP3 did not require a specific time reference.