Difference between revisions of "Template:Networking rutos manual dnp3"
Gytispieze (talk | contribs) |
|||
(29 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
− | {{Template: | + | {{Template: Networking_rutos_manual_fw_disclosure |
− | | | + | | fw_version = {{{series}}}_R_00.07.00 |
− | + | | series = {{{series}}} | |
− | |||
− | |||
− | |||
− | |||
}} | }} | ||
==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 | + | <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). |
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. | ||
− | <b>Note:</b> DNP3 is additional software that can be installed from the <b> | + | <b>Note:</b> DNP3 is additional software that can be installed from the <b>Services → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u> |
==DNP3 Parameters== | ==DNP3 Parameters== | ||
Line 42: | Line 38: | ||
<td>Octet String</td> | <td>Octet String</td> | ||
</tr> | </tr> | ||
− | + | }} | |
<tr> | <tr> | ||
<td>Hostname</td> | <td>Hostname</td> | ||
Line 54: | Line 50: | ||
<td>Octet String</td> | <td>Octet String</td> | ||
</tr> | </tr> | ||
− | + | }} | |
<tr> | <tr> | ||
<td>Router Serial Number</td> | <td>Router Serial Number</td> | ||
Line 64: | Line 60: | ||
|TRB142= | |TRB142= | ||
|TRB145= | |TRB145= | ||
− | | | + | | |
<tr> | <tr> | ||
<td>LAN MAC Address</td> | <td>LAN MAC Address</td> | ||
Line 83: | Line 79: | ||
<td>Octet String</td> | <td>Octet String</td> | ||
</tr> | </tr> | ||
− | + | }} | |
<tr> | <tr> | ||
<td>Network state</td> | <td>Network state</td> | ||
Line 215: | Line 211: | ||
<td>Counter</td> | <td>Counter</td> | ||
</tr> | </tr> | ||
− | + | | | |
<tr> | <tr> | ||
<td>Mobile data received today</td> | <td>Mobile data received today</td> | ||
Line 271: | Line 267: | ||
<td>Counter</td> | <td>Counter</td> | ||
</tr> | </tr> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
}} | }} | ||
{{#ifeq:{{{gps}}}| 1 | | {{#ifeq:{{{gps}}}| 1 | | ||
Line 319: | Line 309: | ||
<td>Octet String</td> | <td>Octet String</td> | ||
</tr> | </tr> | ||
− | + | }} | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</table> | </table> | ||
Line 559: | Line 474: | ||
</tr> | </tr> | ||
</table> | </table> | ||
+ | |||
{{#switch:{{{name}}} | {{#switch:{{{name}}} | ||
|RUTX12= | |RUTX12= | ||
− | The <b>modem_number</b> of the secondary (internal) modem on a RUTX12 is <b> | + | The <b>modem_number</b> of the secondary (internal) modem on a RUTX12 is <b>1</b> (primary modem is skipped). modem_number for the external modem is <b>2</b>. |
| | | | ||
− | The <b>modem_number</b> of the external modem is <b> | + | The <b>modem_number</b> of the external modem is <b>1</b> (internal modem is skipped). |
}} | }} | ||
− | To get the exact index of a parameter, use the formula in the table above. For example, the index of an external modem operator is {{#ifeq:{{{name}}} | RUTX12 | | + | To get the exact index of a parameter, use the formula in the table above. For example, the index of an external modem operator is {{#ifeq:{{{name}}} | RUTX12 | 226. Formula is: 126 + 50 * 2. | 176. Formula is: 126 + 50 * 1. }} |
}} | }} | ||
− | ==TCP | + | ==TCP Master== |
− | A | + | 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. |
− | [[File: | + | [[File:Networking_rutos_manual_dnp3_tcp_master_add_button.png|border|class=tlt-border]] |
− | After clicking 'Add' you will be redirected to the newly added | + | After clicking 'Add' you will be redirected to the newly added master's configuration page. |
− | ===TCP | + | ===TCP Master Configuration=== |
---- | ---- | ||
− | The <b>TCP | + | 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: |
− | [[File: | + | [[File:Networking_rutos_manual_dnp3_tcp_master_tcp_master_configuration.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 591: | Line 507: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off | on; default: <b>off</b></td> |
<td>Turns communication with the outstation device on or off.</td> | <td>Turns communication with the outstation device on or off.</td> | ||
</tr> | </tr> | ||
Line 597: | Line 513: | ||
<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 | + | <td>Name of the TCP master, used for easier management purposes.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 612: | Line 528: | ||
<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> | + | <td>Master Link-Layer address.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 628: | Line 544: | ||
<td>integer [1..60]; default: <b>none</b></td> | <td>integer [1..60]; default: <b>none</b></td> | ||
<td>Maximum response wait time.</td> | <td>Maximum response wait time.</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
Line 638: | Line 549: | ||
===Requests Configuration=== | ===Requests Configuration=== | ||
---- | ---- | ||
− | A DNP3 <b>request</b> is a way of obtaining data from DNP3 Outstations. The | + | 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. |
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: | ||
− | [[File: | + | [[File:Networking_rutos_manual_dnp3_tcp_master_tcp_master_configuration_requests_configuration_add_new_instance_v2.png|border|class=tlt-border]] |
The new Request Configuration should become visible in the list: | The new Request Configuration should become visible in the list: | ||
− | [[File: | + | [[File:Networking_rutos_manual_dnp3_tcp_master_requests_configuration.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 671: | Line 582: | ||
<tr> | <tr> | ||
<td>Data Type</td> | <td>Data Type</td> | ||
− | <td>Binary | + | <td>Binary | Double Binary | Counter | Frozen Counter | Analog | Octet String | Analog Output Status | Binary Output Status; default: <b>Binary</b></td> |
<td>Data object group of the requested index(-es).</td> | <td>Data object group of the requested index(-es).</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>off/on slider</td> |
− | <td>off | + | <td>off | on; default: <b>off</b></td> |
<td>Turns the request on or off.</td> | <td>Turns the request on or off.</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
{{#ifeq:{{{serial}}} | 1 | | {{#ifeq:{{{serial}}} | 1 | | ||
− | ==Serial | + | ==Serial Master== |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | The <b>Serial Master</b> page is used to configure the device as a DNP3 RTU Master. DNP3 RTU (remote terminal unit) is a serial communication protocol mainly used in communication via serial interfaces. | |
− | ===Serial | + | ===Serial Master Configuration=== |
---- | ---- | ||
− | The <b>Serial | + | The <b>Serial 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 Serial Master Configuration and the table below provides information on the fields contained in that section: |
− | [[File: | + | [[File:Networking_rutos_manual_dnp3_serial_master_serial_master_configuration.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 717: | Line 611: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
<td>Turns communication with the outstation device on or off.</td> | <td>Turns communication with the outstation device on or off.</td> | ||
</tr> | </tr> | ||
Line 723: | Line 617: | ||
<td>Name</td> | <td>Name</td> | ||
<td>string; default: <b>none</b></td> | <td>string; default: <b>none</b></td> | ||
− | <td>Name of the Serial | + | <td>Name of the Serial master, used for easier management purposes.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Serial port</td> | <td>Serial port</td> | ||
− | <td>{{ | + | <td>{{#ifeq:{{{rs232}}} | 1 | RS232 |}} {{#ifeq:{{{rs232}}} | 1 | {{#ifeq:{{{rs485}}} | 1 | <nowiki>| </nowiki> |}} |}}{{#ifeq:{{{rs485}}} | 1 | RS485 |}}; default: <b>{{#ifeq:{{{rs232}}} | 1 | RS232 | RS485}}</b></td> |
<td>Selects which serial port to use for communication.</td> | <td>Selects which serial port to use for communication.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Baud rate</td> | <td>Baud rate</td> | ||
− | <td>300 | + | <td>300 <nowiki>|</nowiki> 1200 <nowiki>|</nowiki> 2400 <nowiki>|</nowiki> 4800 <nowiki>|</nowiki> 9600 <nowiki>|</nowiki> 19200 <nowiki>|</nowiki> 38400 <nowiki>|</nowiki> 57600 <nowiki>|</nowiki> 115200; default: <b>115200</b></td> |
<td>Serial data transmission rate (in bits per second).</td> | <td>Serial data transmission rate (in bits per second).</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Data bits</td> | <td>Data bits</td> | ||
− | <td> | + | <td>5 <nowiki>|</nowiki> 6 <nowiki>|</nowiki> 7 <nowiki>|</nowiki> 8; default: <b>8</b></td> |
<td>Number of data bits for each character.</td> | <td>Number of data bits for each character.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Stop bits</td> | <td>Stop bits</td> | ||
− | <td>1 | + | <td>None <nowiki>|</nowiki> 1 <nowiki>|</nowiki> 1.5 <nowiki>|</nowiki> 2; default: <b>1</b></td> |
<td>Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Electronic devices usually use one stop bit. Two stop bits are required if slow electromechanical devices are used.</td> | <td>Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Electronic devices usually use one stop bit. Two stop bits are required if slow electromechanical devices are used.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Parity</td> | <td>Parity</td> | ||
− | <td>Even | + | <td>None <nowiki>|</nowiki> Even <nowiki>|</nowiki> Odd; default: <b>None</b></td> |
<td>In serial transmission, parity is a method of detecting errors. An extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check. | <td>In serial transmission, parity is a method of detecting errors. An extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check. | ||
<ul> | <ul> | ||
<li><b>None</b> (<b>N</b>) - no parity method is used.</li> | <li><b>None</b> (<b>N</b>) - no parity method is used.</li> | ||
<li><b>Odd</b> (<b>O</b>) - the parity bit is set so that the number of "logical ones (1s)" has to be odd.</li> | <li><b>Odd</b> (<b>O</b>) - the parity bit is set so that the number of "logical ones (1s)" has to be odd.</li> | ||
− | <li><b>Even</b> (<b>E</b>) - the parity bit is set so that the number of "logical ones (1s)" has to be even.</li> | + | <li><b>Even</b> (<b>E</b>) - the parity bit is set so that the number of "logical ones (1s)" has to be even.</li> |
− | |||
</ul> | </ul> | ||
</td> | </td> | ||
Line 759: | Line 652: | ||
<tr> | <tr> | ||
<td>Flow control</td> | <td>Flow control</td> | ||
− | <td>None | + | <td>None <nowiki>|</nowiki> Hardware <nowiki>|</nowiki> Xon/Xoff; default: <b>None</b></td> |
<td>In many circumstances a transmitter might be able to send data faster than the receiver is able to process it. To cope with this, serial lines often incorporate a "handshaking" method, usually distinguished between hardware and software handshaking. | <td>In many circumstances a transmitter might be able to send data faster than the receiver is able to process it. To cope with this, serial lines often incorporate a "handshaking" method, usually distinguished between hardware and software handshaking. | ||
− | + | <ul> | |
− | <li><b> | + | <li><b>Hardware</b> - hardware handshaking. RTS and CTS are turned OFF and ON from alternate ends to control data flow, for instance when a buffer is almost full.</li> |
<li><b>Xon/Xoff</b> - software handshaking. The Xon and Xoff characters are sent by the receiver to the sender to control when the sender will send data, i.e., these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the Xoff character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an Xon character to tell the sender to resume transmission.</li> | <li><b>Xon/Xoff</b> - software handshaking. The Xon and Xoff characters are sent by the receiver to the sender to control when the sender will send data, i.e., these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the Xoff character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an Xon character to tell the sender to resume transmission.</li> | ||
− | </ul> | + | </ul> |
</td> | </td> | ||
− | </tr> | + | </tr> |
− | |||
− | |||
− | |||
− | |||
− | |||
<tr> | <tr> | ||
<td>Open delay</td> | <td>Open delay</td> | ||
Line 780: | Line 668: | ||
<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> | + | <td>Master Link-Layer address.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 796: | Line 684: | ||
<td>integer [1..60]; default: <b>none</b></td> | <td>integer [1..60]; default: <b>none</b></td> | ||
<td>Maximum response wait time.</td> | <td>Maximum response wait time.</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
Line 806: | Line 689: | ||
===Requests Configuration=== | ===Requests Configuration=== | ||
---- | ---- | ||
− | A DNP3 <b>request</b> is a way of obtaining data from DNP3 Outstations. The | + | 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. |
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: | ||
Line 814: | Line 697: | ||
The new Request Configuration should become visible in the list: | The new Request Configuration should become visible in the list: | ||
− | [[File: | + | [[File:Networking_rutos_manual_dnp3_tcp_master_requests_configuration.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 839: | Line 722: | ||
<tr> | <tr> | ||
<td>Data Type</td> | <td>Data Type</td> | ||
− | <td>Binary | + | <td>Binary <nowiki>|</nowiki> Double Binary <nowiki>|</nowiki> Counter <nowiki>|</nowiki> Frozen Counter <nowiki>|</nowiki> Analog <nowiki>|</nowiki> Octet String <nowiki>|</nowiki> Analog Output Status <nowiki>|</nowiki> Binary Output Status; default: <b>Binary</b></td> |
<td>Data object group of the requested index(-es).</td> | <td>Data object group of the requested index(-es).</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>off/on slider</td> |
− | <td>off | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
<td>Turns the request on or off.</td> | <td>Turns the request on or off.</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|}} | |}} | ||
==DNP3 Outstation== | ==DNP3 Outstation== | ||
− | An outstation in DNP3 is a component that communicates with a single | + | 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: | 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: | ||
− | [[File: | + | [[File:Networking_rutos_manual_dnp3_dnp3_outstation.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 877: | Line 749: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off | on; default: <b>off</b></td> |
<td>Turns DNP3 Outstation on or off.</td> | <td>Turns DNP3 Outstation on or off.</td> | ||
</tr> | </tr> | ||
Line 888: | Line 760: | ||
<td>Remote Address</td> | <td>Remote Address</td> | ||
<td>integer [0..65535]; default: <b>none</b></td> | <td>integer [0..65535]; default: <b>none</b></td> | ||
− | <td> | + | <td>Master Link-Layer address.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Unsolicited enabled</td> | <td>Unsolicited enabled</td> | ||
− | <td>off | + | <td>off | on; default: <b>none</b></td> |
<td>Enables the transmission of unsolicited messages.</td> | <td>Enables the transmission of unsolicited messages.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Protocol</td> | <td>Protocol</td> | ||
− | <td>TCP | + | <td>TCP | <span style="color:red">UDP</span>; default: <b>TCP</b></td> |
<td>Protocol used for DNP3 communications.</td> | <td>Protocol used for DNP3 communications.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Port</td> | <td>Port</td> | ||
− | <td>integer [0..65535]; default: <b> | + | <td>integer [0..65535]; default: <b>502</b></td> |
<td>Port used for DNP3 communications.</td> | <td>Port used for DNP3 communications.</td> | ||
</tr> | </tr> | ||
Line 917: | Line 789: | ||
<tr> | <tr> | ||
<td>Allow Remote Access</td> | <td>Allow Remote Access</td> | ||
− | <td>off | + | <td>off | on; default: <b>off</b></td> |
<td>Allows remote DNP3 connections by adding an exception to the device's firewall on the port specified in the field above.</td> | <td>Allows remote DNP3 connections by adding an exception to the device's firewall on the port specified in the field above.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
[[Category:{{{name}}} Services section]] | [[Category:{{{name}}} Services section]] |
Revision as of 12:14, 10 August 2021
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 master 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 |
Network state | 9 | Octet String |
Connection state | 10 | Octet String |
Mobile data received today | 20 | Counter |
Mobile data sent today | 21 | Counter |
Mobile data received this week | 22 | Counter |
Mobile data sent this week | 23 | Counter |
Mobile data received this month | 24 | Counter |
Mobile data sent this month | 25 | Counter |
Mobile data received last 24h | 26 | Counter |
Mobile data sent last 24h | 27 | Counter |
Mobile data received last week | 28 | Counter |
Mobile data sent last week | 29 | Counter |
Mobile data received last month | 30 | Counter |
TCP Master
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.
After clicking 'Add' you will be redirected to the newly added master's configuration page.
TCP Master Configuration
The TCP Master Configuration 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:
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 master, 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 | Master 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. |
Requests Configuration
A DNP3 request 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.
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. |
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: 502 | 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]]