Template:Networking rutos manual dnp3: Difference between revisions
Gytispieze (talk | contribs) m (Text replacement - "\{\{Template: Networking_rutos_manual_fw_disclosure (.*) (.*) (.*) (.*) \}\}" to "{{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Networking_device_manual_latest_fw | series = {{{series}}} | name = {{{name}}} }} }}") Tags: Mobile edit Mobile web edit |
No edit summary |
||
| Line 499: | Line 499: | ||
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. | 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: | [[File:Networking_rutos_manual_dnp3_tcp_master_add_button_v3.png|border|class=tlt-border]] | ||
After clicking 'Add' you will be redirected to the newly added client's configuration page. | After clicking 'Add' you will be redirected to the newly added client's configuration page. | ||
| Line 507: | Line 507: | ||
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: | 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: | [[File:Networking_rutos_manual_dnp3_tcp_client_tcp_client_configuration_v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
| Line 517: | Line 517: | ||
<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 557: | Line 557: | ||
<tr> | <tr> | ||
<td>Save to flash</td> | <td>Save to flash</td> | ||
<td>off | <td>off {{!}} on; default: <b>off</b></td> | ||
<td>When enabled, stores request information in device flash.</td> | <td>When enabled, stores request information in device flash.</td> | ||
</tr> | </tr> | ||
| Line 568: | Line 568: | ||
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_v3.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_client_requests_configuration_v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
| Line 597: | Line 597: | ||
<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>Enabled</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> | |||
<td>Actions</td> | |||
<td> - interactive button</td> | |||
<td>Deletes request configuration.</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 735: | Line 740: | ||
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_v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
| Line 764: | Line 769: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Enabled</td> | ||
<td>off {{!}} on; default: <b>off</b></td> | <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> | |||
<td>Actions</td> | |||
<td> - interactive button</td> | |||
<td>Deletes request configuration.</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 783: | Line 793: | ||
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_v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
| Line 793: | Line 803: | ||
<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 808: | Line 818: | ||
<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> | ||
| Line 833: | Line 843: | ||
<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> | ||
Revision as of 12:15, 17 April 2024
The information in this page is updated in accordance with firmware version .
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 System → [[{{{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.
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). |
| Enabled | off | on; default: off | Turns the request on or off. |
| Actions | - interactive button | Deletes request configuration. |
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 client via a communication channel. It makes measurements of the physical world and then sends them to a client upon request (solicited) or on its own accord (unsolicited). Occasionally a client 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 | Client 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]]