Template:Networking rutos manual dnp3: Difference between revisions

From Teltonika Networks Wiki
No edit summary
Line 8: Line 8:
==Summary==
==Summary==


<b>Distributed Network Protocol 3 (DNP3)</b> is a set of communications protocols used between components in process automation systems. It is primarily used for communications between a master station and Remote Terminal Units (RTUs) or Intelligent Electronic Devices (IEDs).
<b>Distributed Network Protocol 3 (DNP3)</b> is a set of communications protocols used between components in process automation systems. It is primarily used for communications between a client station and Remote Terminal Units (RTUs) or Intelligent Electronic Devices (IEDs).


This manual page provides an overview of the DNP3 functionality in {{{name}}} devices.
This manual page provides an overview of the DNP3 functionality in {{{name}}} devices.
Line 493: Line 493:
}}
}}


==TCP Master==
==TCP Client==


A master in DNP3 is a component that communicates (requests data) with a single outstation via a communication channel. By default, the master list is empty. To add a new master, click the 'Add' button.
A client in DNP3 is a component that communicates (requests data) with a single outstation via a communication channel. By default, the client list is empty. To add a new client, click the 'Add' button.


[[File:Networking_rutos_manual_dnp3_tcp_master_add_button.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_dnp3_tcp_master_add_button_v2.eps|border|class=tlt-border]]


After clicking 'Add' you will be redirected to the newly added master's configuration page.
After clicking 'Add' you will be redirected to the newly added client's configuration page.


===TCP Master Configuration===
===TCP Client Configuration===
----
----
The <b>TCP Master Configuration</b> section is used to configure the parameters of a DNP3 Outstation that the Master (this {{{name}}} device) will be querying with requests. The figure below is an example of the TCP Master Configuration and the table below provides information on the fields contained in that section:
The <b>TCP Client Configuration</b> section is used to configure the parameters of a DNP3 Outstation that the Client (this {{{name}}} device) will be querying with requests. The figure below is an example of the TCP Client Configuration and the table below provides information on the fields contained in that section:


[[File:Networking_rutos_manual_dnp3_tcp_master_tcp_master_configuration_v2.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_dnp3_tcp_client_tcp_client_configuration.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 521: Line 521:
         <td>Name</td>
         <td>Name</td>
         <td>string; default: <b>none</b></td>
         <td>string; default: <b>none</b></td>
         <td>Name of the TCP master, used for easier management purposes.</td>
         <td>Name of the TCP client, used for easier management purposes.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 536: Line 536:
         <td>Local Address</td>
         <td>Local Address</td>
         <td>integer [0..65535]; default: <b>none</b></td>
         <td>integer [0..65535]; default: <b>none</b></td>
         <td>Master Link-Layer address.</td>
         <td>Clients Link-Layer address.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 562: Line 562:
===Requests Configuration===
===Requests Configuration===
----
----
A DNP3 <b>request</b> is a way of obtaining data from DNP3 Outstations. The master sends a request to an outstation specifying the function codes to be performed. The outstation then sends the requested data back to the DNP3 master.
A DNP3 <b>request</b> is a way of obtaining data from DNP3 Outstations. The client sends a request to an outstation specifying the function codes to be performed. The outstation then sends the requested data back to the DNP3 client.


The Request Configuration list is empty by default. To add a new Request Configuration look to the Add New Instance section. Enter a custom name into the 'New Configuration Name' field and click the 'Add' button:
The Request Configuration list is empty by default. To add a new Request Configuration look to the Add New Instance section. Enter a custom name into the 'New Configuration Name' field and click the 'Add' button:

Revision as of 10:36, 25 September 2023

Template:Networking rutos manual fw disclosure

Summary

Distributed Network Protocol 3 (DNP3) is a set of communications protocols used between components in process automation systems. It is primarily used for communications between a client station and Remote Terminal Units (RTUs) or Intelligent Electronic Devices (IEDs).

This manual page provides an overview of the DNP3 functionality in {{{name}}} devices.

Note: DNP3 is additional software that can be installed from the Services → [[{{{name}}} Package Manager|Package Manager]] page.

DNP3 Parameters

DNP3 parameters are held within indexes. The index numbers and corresponding system values are described in the table below:

required value index group type
Uptime 0 Counter
Hostname 3 Octet String
Router Serial Number 5 Octet String
LAN MAC Address 6 Octet String
Router name 7 Octet String


TCP Client

A client in DNP3 is a component that communicates (requests data) with a single outstation via a communication channel. By default, the client list is empty. To add a new client, click the 'Add' button.

File:Networking rutos manual dnp3 tcp master add button v2.eps

After clicking 'Add' you will be redirected to the newly added client's configuration page.

TCP Client Configuration


The TCP Client Configuration section is used to configure the parameters of a DNP3 Outstation that the Client (this {{{name}}} device) will be querying with requests. The figure below is an example of the TCP Client Configuration and the table below provides information on the fields contained in that section:

Field Value Description
Enable off | on; default: off Turns communication with the outstation device on or off.
Name string; default: none Name of the TCP client, used for easier management purposes.
IP address ip; default: none DNP3 Outstation IP address.
Port integer [0..65535]; default: none DNP3 Outstation Port.
Local Address integer [0..65535]; default: none Clients Link-Layer address.
Remote Address integer [0..65535]; default: none Outstation Link-Layer address.
Period integer [1..60]; default: none Interval at which requests are sent to the outstation device.
Timeout integer [1..60]; default: none Maximum response wait time.
Save to flash off | on; default: off When enabled, stores request information in device flash.

Requests Configuration


A DNP3 request is a way of obtaining data from DNP3 Outstations. The client sends a request to an outstation specifying the function codes to be performed. The outstation then sends the requested data back to the DNP3 client.

The Request Configuration list is empty by default. To add a new Request Configuration look to the Add New Instance section. Enter a custom name into the 'New Configuration Name' field and click the 'Add' button:

The new Request Configuration should become visible in the list:

Field Value Description
Name string; default: Unnamed Name of this Request Configuration. Used for easier management purposes.
Start Index integer [0..65535]; default: none Start index of the data subarray.
End Index integer [0..65535]; default: none End index of the data subarray.
Data Type Binary | Double Binary | Counter | Frozen Counter | Analog | Octet String | Analog Output Status | Binary Output Status; default: Binary Data object group of the requested index(-es).
off/on slider off | on; default: off Turns the request on or off.

Request Configuration Testing


This section is used to check whether the configuration works correctly. Simply click the 'Test' button and a response should appear in the box below. The last value represents the configured request data. A successful response to a test may look something like this:


DNP3 Outstation

An outstation in DNP3 is a component that communicates with a single master via a communication channel. It makes measurements of the physical world and then sends them to a master upon request (solicited) or on its own accord (unsolicited). Occasionally a master requests that it do something by sending it a control. This provides the user with the possibility to get system parameters.

The figure below is an example of the DNP3 Outstation window section and the table below provides information on the fields contained in that window:

Field Value Description
Enable off | on; default: off Turns DNP3 Outstation on or off.
Local Address integer [0..65535]; default: none Outstation Link-Layer address.
Remote Address integer [0..65535]; default: none Master Link-Layer address.
Unsolicited enabled off | on; default: none Enables the transmission of unsolicited messages.
Protocol TCP | UDP; default: TCP Protocol used for DNP3 communications.
Port integer [0..65535]; default: none Port used for DNP3 communications.
UDP response address ipv4; default: none UDP response address.
UDP response port integer [0..65535]; default: none UDP response port.
Allow Remote Access off | on; default: off Allows remote DNP3 connections by adding an exception to the device's firewall on the port specified in the field above.


[[Category:{{{name}}} Services section]]