DNP3 Data Object Mapping Page and Table

Data Object Mapping Page

This figure shows the dialog box for configuring the data object mapping for an item with the example data type Binary_Input for DNP3 slave/server:

This figure shows the dialog box for configuring the Binary_Input data object mapping with DNP3 NET Server:

This figure shows the dialog box for configuring the Binary_Input data object mapping with DNP3 NET Client:

Mapping Table

Depending on the data object type and the selected protocol profile, different configuration fields are required to define a data object mapping item. This table describes the parameters:

Title	Value scope	Default value	Description
Point Number	0...16777215	0	indicates the start number of the point (1).
Point Count	1...65535	1	indicates the number of points.
CPU Register Type	%M/%MW/%S/%SW/ Unlocated	%MW	indicates the register type in CPU to map points (2).
CPU Register Address	0...30000	0	indicates start address of the register in CPU. This field only taken into account for located variables. With %S, the range is from 0 to 127.
Variable Name	–	–	indicates the variable name of the located or unlocated register.
Event Class Mask (0/1/2/3/Unsolicited)	check box	0	defines the event class of points. Unsolicited is not allowed with class 0 only. In client, Channel must be at 0.
Store To CPU (Client) OR CPU Reg Mapping (Server)	Value only Value with time Value with flag Value with flag and time	Value only	Event time stamp source: Value only: module time Value with time: time in CPU registers Value with flag: flag info on the point is taken from CPU registers Value with flag and time: flag and time are taken from CPU registers
(Default) Static Variation	g1v1 Binary In/ g1v2 Binary In Flag	g1v1 Binary In	indicates the default static variation for data point
Event routing (Client only)
Channel	None/0	None	indicates the channel number to route
Session	0	0	indicates the session number to route (Channel at 0)
Point number	0...16777215	0	indicates the point number to route (Channel at 0)

Default Event Variation	g2v1 Binary Input No Time g2v1 Binary Input With Time g2v1 Binary Input Relative Time	g2v1 Binary Input No Time	indicates the default event variation for data point
1: The DNP3 point number must start from 0 and be contiguous in slave/server mode. If this is not applied, the nonconsecutive points cannot work normally. 2: DNP3 Server: %S applies only to binary inputs and %SW only to analog inputs, 32-bit analog inputs; the CPU mapping does not apply array due to the limits of Control Expert.

Configuring Unsolicited Response

The RTU module supports unsolicited messages to be sent out immediately once events are recorded.

Configuration of Unsolicited:

To check the Unsolicited parameter, you must have another Even Class Mask parameter (other than class 0) selected. The Unsolicited parameter can be configured for Binary Input, Double Input, Double Input, Binary Countand Analog Input in the Server.

Unsolicited with routing points (Client):

In events generation, Unsolicitedmessages are sent when one of the following conditions are met:

Unsolicited messages are enabled and the number of events in the buffer exceeds the minimum amount.
Unsolicited messages are enabled and the delay (timeout) to report expires.
Events are generated for the point that is set for immediate Unsolicited message reporting, regardless if the two conditions above are met or not.
Events are generated for a point that is set for immediate Unsolicited message reporting, then all events in the buffer are immediately reported.

Quality Bit/Flag Mapping

The configuration applies quality bit/flag mapping to the CPU register for monitoring datapoints for the DNP3 master/DNP3 slave.

NOTE: Use this feature for Binary_Input, Double_Input, Binary_Counter, Analog_Input, Binary_Output, and Analog_Output.

This figure shows the flag configuration:

The configuration reuses Timestamp Source in the slave and Store To CPU in the master, and expands two choices based on RTU V1.0. The DNP3 master and DNP3 slave have similar configuration pages for quality bits and flags.

Behavior:

Input and output point types apply this feature.
If the end user configures the flag in the CPU register in the slave, the module no longer manages the flags internally. The RTU module generates events following in the CPU register, otherwise, the RTU module generates them automatically.
In the DNP3 Net server/DNP3 slave, the change of flags in CPU can trigger the generation of events just like value changes.
The length of the flag is 1 byte no matter how many bytes are mapped in the CPU register, the least byte is valid. Refer to memory allocation.

This table shows the flag definition:

Point	Flag definition	Options	Comments
Binary Input Flags	on-line	bit 0: 0 (off-line)/ 1 (on-line)	–
	restart	bit 1: 0 (normal/ 1 (restart)
	communication lost	bit 2: 0 (normal/ 1 (lost)
	remote forced data	bit 3: 0 (normal)/ 1 (forced)
	local forced data	bit 4: 0 (normal)/ 1 (forced)
	chatter filtered	bit 5: 0 (normal)/ 1 (filter on)	Events are generated when the CHATTER_FILTER flag is set and cleared, but not when CHATTER_FILTER is set.
	reserved	bit 6: 0	Not used
	state	bit 7: 0 /1	Not used
Binary Output Status Flags	on-line	bit 0: 0 (off-line)/1 (on-line)	–
	restart	bit 1: 0 (normal/1 (restart)
	communication lost	bit 2: 0 (normal/1 (lost)
	remote forced data	bit 3: 0 (normal)/1 (forced)
	local forced data	bit 4: 0 (normal)/1 (forced)
	chatter filtered	bit 5: 0	Not used –
	reserved	bit 6: 0
	state	bit 7: 0 /1
Double Input Flags	on-line	bit 0: 0 (off-line)/1 (on-line)	–
	restart	bit 1: 0 (normal/1 (restart)
	communication lost	bit 2: 0 (normal/1 (lost)
	remote forced data	bit 3: 0 (normal)/1 (forced)
	local forced data	bit 4: 0 (normal)/1 (forced)
	chatter filtered	bit 5: 0 (normal)/1 (filter on)	Events are generated when CHATTER_FILTER flag is set and cleared, but not when it is set.
	state	bit 6: 0/1	Not used
	state	bit 7: 0/1	Not used
Analog Input Flags	on-line	bit 0: 0 (off-line)/1 (on-line)	–
	restart	bit 1: 0 (normal/1 (restart)
	communication lost	bit 2: 0 (normal/1 (lost)
	remote forced data	bit 3: 0 (normal)/1 (forced)
	local forced data	bit 4: 0 (normal)/1 (forced)
	over range	bit 5: 0 (normal)/1 (over range)
	reference error	bit 6: 0 (normal)/1 (error)
	reserved	bit 7: 0	Not used
Analog Output Status Flags	on-line	bit 0: 0 (off-line)/1 (on-line)	–
	restart	bit 1: 0 (normal/1 (restart)
	communication lost	bit 2: 0 (normal/1 (lost)
	remote forced data	bit 3: 0 (normal)/1 (forced)
	local forced data	bit 4: 0 (normal)/1 (forced)
	over range	bit 5: 0 (normal)/1 (over range)
	reference error	bit 6: 0 (normal)/1 (error)
	reserved	bit 7: 0	Not used
Counter Flags	on-line	bit 0: 0 (off-line)/1 (on-line)	–
	restart	bit 1: 0 (normal/1 (restart)
	communication lost	bit 2: 0 (normal/1 (lost)
	remote forced data	bit 3: 0 (normal)/1 (forced)
	local forced data	bit 4: 0 (normal)/1 (forced)
	roll over	bit 5: 0	Not used
	discontinuity	bit 6: 0 (normal)/1 (discontinuity)	–
	reserved	bit 7: 0	Not used

Binary Output Status and Analog Output Status

The Binary_Output_Status and Analog_Output_Status are applied in the master, which are used to save the latest value, state (flag), and timestamp.

This figure shows the binary output status:

This figure shows the analog output status:

NOTE: Floating point values (scientific notation) can be entered for the deadband.

Behavior of a Binary Output

The configuration applies latch on/off, pulse on, and close/trip pulse on:

TCC (Trip-Close Code)	Operation type field	Control code	Point model in outstation
None	pulse on	01 hex	activation
	latch on	03 hex	latch complement
	latch off	04 hex	latch complement
Close	pulse on	41 hex	two’s complement
Trip	pulse on	81 hex	two’s complement

This figure shows the selection of control code type:

The DNP3 master only provides on-time configuration, but does not provide configured off-time and count. The DNP3 slave also only applies pulse on which the count is 1 and the off-time value is 0.
Two’s complement trip and close are provided for a single index in the DNP3 master, but two separately physical outputs in the DNP3 slave. For example, a close/pulse on request for a specific DNP3 index is mapped to a specific relay output, whereas a trip/pulse on request for the same DNP3 index is mapped to another different relay output which follows the specific relay output (close) in the RTU module.

CROB sent in DNP3 master	Point number in DNP3 master	Point number in DNP3 slave
Pulse on	0	0
Trip/Pulse on	0	1
Close/Pulse on	2	2
Trip/Pulse on	2	3
Close/Pulse on	n+2	n+2
Trip/Pulse on	n+2	n+2+1

In the DNP3 slave, it is decided by configuration whether the point index applies trip/close request. As the trip/close need to bind a couple of points, the point count is even in the configuration.

The following figure shows the selection of TCC:

TCC parameter: The usage of Trip_Close mode depends on the Trip-Close Mode parameter setting (Channel → Session → Advanced Parameter).

When Trip-Close Mode is in Even Mode, the behavior is as follows: the close command controls the even point and the trip command controls the odd point.

When Trip-Close Mode is in Consecutive Mode, the behavior is as follows: the binary output occupies two registers in the CPU memory (%MWs or %Ms). The low register is for the close command and the high register is for the trip command.

CROB usage in master

Op type field	Trigger mechanism	Description
Close/Pulse_on	any value change (0...65535)	pulse on if value change
Latch_on	0 to 1	latch on
Latch off	1 to 0	latch off
Close/Pulse_on	0 to 1	pulse on for close output
Trip/Pulse_on	1 to 0	pulse on for trip output

Binary output in DNP3 slave is only updated in CPU register only after receiving command from DNP3 master, but not synchronized cyclically. Keep the corresponding CPU register not written any more.

Long and Short Pulses of Binary Outputs

This figure shows the pulse duration setting of the master:

This figure shows the pre-configured pulse duration of the slave:

NOTE: The outstation uses the entered pulse duration. The value 0 indicates that the device uses a pre-configured value.

Set Measured Value

Apply analog input deadband (obj34) to set deadband of measured value. The parameters of the measured points are activated immediately after the DNP3 slave receives the request from the DNP3 master.

For DNP3 obj34, there is no qualifier to set as it only applies the parameter deadband. Set the static variation and point number at the same setting of the analog input. Analog input deadband is applied both on the DNP3 master and the DNP3 slave. DNP3 master uses it to store the current value which is reported in the response of read requests, the DNP3 slave uses it to display the current deadband value which can be controlled by the master through the analog input deadband control block.

This figure shows the parameter point setting of deadband:

This figure shows the parameter point setting of deadband control block:

Generating Events on Demand

This feature generates events on demand regardless of value and state. Data is pushed to the event queue even if the tag value has not changed. It generates events for any specified point type.

Gen_Events can be created only for DNP3 Slave/Server; select Data Mapping:

Parameter	Value Scope	Default Value	Definition
Object Group	Binary Input Double Input Binary Counter Analog Input Binary Output Analog Output	Binary Input	specifies the object group whose event must be generated on demand
Start Point Number	0..16777215	0	specifies the start point number of the specified object group
Point Count	1...5000	5000	specifies the point number to generate events 5000: the actual count depends on the point number of the object group’s configuration)
CPU Register Type	%MW	%MW	indicates the register type in the CPU to map points to; only the %MW type is supported
CPU Register Address	0...32464	0	indicates the start address of the register in the CPU. Effective for the located variables only
Variable Name	–	–	indicates the name of the located register

Analog input supports events in either Class1, Class2, or Class3 options. If the value of Gen_Events register has changes, the advanced RTU module records the events for the Analog Input specified in the configuration although its value has no change.

It is possible to control Gen_Events in SCADA after mapping the CPU register with Binary Output.

Clearing Events on Demand

Clear_Events supports a new point type which clears the event buffer in the DNP3 Server/Slave. It enables the user to clear the events buffer in a local or remote SCADA through mapping memory.

Clear_Events can be created only for DNP3 Slave/Server; select Data Mapping.

When the value of Clear_Events register has changes, the advanced RTU module clears the events of the object group in configuration.

Parameter	Value Scope	Default Value	Definition
Object Group	All Objects Binary Input Double Input Binary Counter Analog Input Binary Output Analog Output	All Objects	specifies the object group whose event must be cleared on demand
Channel Number	0..255	255 (all the channels)	specifies the channel number to clear (it depends on channel configuration)
CPU Register Type	%MW	%MW	indicates the register type in the CPU to map points to; only the %MW type is supported
CPU Register Address	0...32464	0	indicates the start address of the register in the CPU. Effective for the located variables only
Variable Name	–	–	indicates the name of the located register