DNP3 Channel Configuration Over UDP
Original instructions
About us
Introduction
Select which communication needs to be configured via the Web site before configuring the ports of the RTU module. The RTU module supports UDP in two ways: UDP-IP and TCP-UDP. When it is TCP-UDP, the RTU module supports the sending/receiving of broadcast requests.
You can add a DNP3 net master (client) in the communication when you select the DNP3 protocol, the Ethernet network type, and the Master mode. Then you can configure the session parameters for the DNP3 slave device in Control Expert.
Access the parameters by selecting CONFIGURATION → CHANNELS and pressing the CHANNEL PARAMETERS tab.
Communication Setup
Set DNP3 NET client/DNP3 NET server over UDP:
Configuration
For UDP-IP and TCP-UDP, it is necessary to set special ports and IP address according to DNP3 specifications:
UDP-IP
Client
Server
Name
Description
Name
Description
Dest port
Destination port for UDP
Local port
Local port for UDP; it must be unique.
Local Port
Local port for UDP-IP; it must be unique in current channel. Exception: 0 means that the local port is generated automatically by the system
Destination port
Destination port for UDP. 0 is allowed, which means that the server uses the port from which the master sent the request.
Unsol destination port
Port that the server uses to send initial unsolicited responses in UDP-IP
TCP-UDP
Client
Server
Name
Description
Name
Description
TCP destination port
Destination port for TCP
TCP local port
Local port for TCP
UDP broadcast port
Port that sends broadcasts in TCP-UDP
UDP local port
Port that receives broadcasts (available for TCP-UDP)
Only one IP is allowed.
IP and port configuration of DNP3 Net client UDP-IP:
IP and port configuration of DNP3 Net client TCP-UDP:
When the RTU module works as client in TCP-UDP, it can send command requests in broadcasts. Beside broadcast address configuration, it is necessary to specify the destination address. Here are the options of broadcast confirmation, which are used to specify the destination address for sending broadcast requests.
Options
Definition address
Special use
Optional
FFFF hex
All-call, application layer confirmation to clear IIN1.0 is optional.
Mandatory
FFFE hex
All-call, application layer confirmation to clear IIN1.0 is mandatory.
Never
FFFD hex
All-call, application layer confirmation must not be required to clear IIN1.0.
Destination address configuration of broadcasts:
In TCP-UDP, it depends on whether this command is broadcast or not to the client. So it is necessary to enable it explicitly in data mapping setting:
NOTE:
  • Not all commands are supported in broadcast; the RTU module client supports:
    • Restart
    • Time_Sync
    • Unsolicited_Class
    • Freeze_Counter
    • Binary_Output
    • Analog_Output
  • Freeze_Counter, Binary_Output, and Analog_Output support broadcast only when operation mode (function code) is without acknowledgment.