Changes

==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.

}}

}}

==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">

         <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>

         <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>

===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: