Changes

Template:Networking rutos manual dnp3 (view source)

Revision as of 11:20, 23 November 2022

7,635 bytes added , 11:20, 23 November 2022

no edit summary

Line 556: Line 556:

<td>Save to flash</td>

<td>off | on; default: off</td>

−

<td>When enabled, stores ~~device~~ in device flash.</td>

+

<td>When enabled, stores request information in device flash.</td>

</tr>

</table>

Line 615: Line 615:

The Serial Master 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.

+

By default, the list is empty. To add a new master instance, enter the instance name, select serial interface and click the 'Add' button.

+

[[File:Networking_rutos_manual_generic_serial_instance_add_button_rs232_{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|1|0}}_v1.png|border|class=tlt-border]]

+

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

===Serial Master Configuration===

Line 620: Line 626:

The Serial 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 Serial Master Configuration and the table below provides information on the fields contained in that section:

−

[[File:~~Networking_rutos_manual_dnp3_serial_master_serial_master_configuration~~.png|border|class=tlt-border]]

+

[[File:Networking_rutos_manual_dnp3_serial_master_configuration_rs232_{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|1|0}}_v1.png|border|class=tlt-border]]

Line 630: Line 636:

<tr>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns communication with the outstation device on or off.</td>

</tr>

Line 640: Line 646:

<tr>

<td>Serial port</td>

−

<td>{{~~#ifeq~~:~~{{{~~rs232~~}}} | 1 | RS232 |}} {{#ifeq:~~{{{rs232}}} | ~~1 | {{#ifeq:{{{~~rs485~~}}} | 1 | <nowiki>| </nowiki> |}} |}}{{#ifeq:~~{{{rs485}}} | ~~1 | RS485 |}} {{#ifeq:~~{{{usb}}} ~~| 1 | USB serial port|~~}}; default: {{Template: Networking rutos manual default serial port| rs232={{{rs232}}}| rs485={{{rs485}}}| usb = {{{usb}}}}}</td>

+

<td>{{Template: Networking rutos manual serial ports| rs232={{{rs232}}}| rs485={{{rs485}}}| usb = {{{usb}}}}}; default: {{Template: Networking rutos manual default serial port| rs232={{{rs232}}}| rs485={{{rs485}}}| usb = {{{usb}}}}}</td>

<td>Selects which serial port to use for communication.</td>

</tr>

<tr>

−

+

<td>300 {{!}} 1200 {{!}} 2400 {{!}} 4800 {{!}} 9600 {{!}} 19200 {{!}} 38400 {{!}} 57600 {{!}} 115200{{#ifeq: {{{rs485}}} | 1 | {{!}} 230400 {{!}} 460800 {{!}} 921600 {{!}} 1000000 {{!}} 3000000|}}; default: 115200</td>

<td>Serial data transmission rate (in bits per second).</td>

</tr>

<tr>

−

<td>5 ~~<nowiki>|</nowiki>~~ 6 ~~<nowiki>|</nowiki>~~ 7 ~~<nowiki>~~|~~</nowiki>~~ 8; default: 8</td>

+

<td>{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|{{#ifeq:{{{series}}}|TRB2||5 {{!}} 6 {{!}}}} 7 {{!}} |}}8; default: 8</td>

<td>Number of data bits for each character.</td>

</tr>

<tr>

−

<td~~>None <nowiki>|</nowiki~~> 1 ~~<nowiki>~~|~~</nowiki>~~ 1~~.5 <nowiki>~~|~~</nowiki>~~ 2; default: 1</td>

+

<td>1{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1| {{!}} 2|}}; default: 1</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>

<td>Parity</td>

−

<td>~~None <nowiki>~~|~~</nowiki> Even <nowiki>~~|~~</nowiki> Odd~~; default: None</td>

+

<td>Even {{!}} Odd{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1| {{!}} Mark {{!}} Space|}} {{!}} None; default: None</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.

<ul>

<li>None (N) - no parity method is used.</li>

<li>Odd (O) - the parity bit is set so that the number of "logical ones (1s)" has to be odd.</li>

−

<li>Even (E) - the parity bit is set so that the number of "logical ones (1s)" has to be even.</li>

+

<li>Even (E) - the parity bit is set so that the number of "logical ones (1s)" has to be even.</li>{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|<li>Space (s) - the parity bit will always be a binary 0.</li>

+

<li>Mark (M) - the parity bit will always be a binary 1.</li>|}}

</ul>

</td>

Line 671: Line 678:

<tr>

<td>Flow control</td>

−

<td>None ~~<nowiki>~~|~~</nowiki> Hardware <nowiki>~~|</~~nowiki>~~ Xon/Xoff; default: None</td>

+

<td>None {{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1| {{!}} RTS/CTS {{!}} Xon/Xoff|}}; default: None</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.

−

<ul>

+

{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|<ul>

−

<li>~~Hardware~~ - 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>RTS/CTS - 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>Xon/Xoff - 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>

−

</tr>

+

</tr>{{#ifeq: {{{rs485}}} | 1 |

+

<tr>

+

<td>RS485: Full Duplex</td>

+

<td>off {{!}} on; default: off</td>

+

<td>Enables RS485 full duplex.</td>

+

</tr>|}}

<tr>

<td>Open delay</td>

Line 703: Line 715:

<td>integer [1..60]; default: none</td>

<td>Maximum response wait time.</td>

+

</tr>

+

<tr>

+

<td>Save to flash</td>

+

<td>off {{!}} on; default: off</td>

+

<td>When enabled, stores request information in device flash.</td>

</tr>

</table>

Line 741: Line 758:

<tr>

−

+

<td>Binary {{!}} Double Binary {{!}} Counter {{!}} Frozen Counter {{!}} Analog {{!}} Octet String {{!}} Analog Output Status {{!}} Binary Output Status; default: Binary</td>

<td>Data object group of the requested index(-es).</td>

</tr>

<tr>

<td>off/on slider</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns the request on or off.</td>

</tr>

Line 818: Line 835:

</tr>

</table>

+

{{#ifeq:{{{serial}}} | 1 |

+

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

+

===DNP3 Serial Outstation Configuration===

+

----

+

The DNP3 Serial Outstation Configuration page is used to configure the device as a DNP3 RTU Outstation. DNP3 RTU (remote terminal unit) is a serial communication protocol mainly used in communication via serial interfaces.

+

By default, the list is empty. To add a new outstation instance, enter the instance name, select serial interface and click the 'Add' button.

+

[[File:Networking_rutos_manual_generic_serial_instance_add_button_rs232_{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|1|0}}_v1.png|border|class=tlt-border]]

+

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

+

===RS Device DNP3 Outstation Configuration===

+

----

+

The RS Device DNP3 Outstation Configuration section is used to configure the parameters of a Serial DNP3 Outstation that will be queried by other Master devices. 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:Networking_rutos_manual_dnp3_serial_outstation_configuration_rs232_{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|1|0}}_v1.png|border|class=tlt-border]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Enable</td>

+

<td>off {{!}} on; default: off</td>

+

<td>Turns communication with the outstation device on or off.</td>

+

</tr>

+

<tr>

+

+

<td>string; default: none</td>

+

<td>Name of the Serial master, used for easier management purposes.</td>

+

</tr>

+

<tr>

+

<td>Serial port</td>

+

<td>{{Template: Networking rutos manual serial ports| rs232={{{rs232}}}| rs485={{{rs485}}}| usb = {{{usb}}}}}; default: {{Template: Networking rutos manual default serial port| rs232={{{rs232}}}| rs485={{{rs485}}}| usb = {{{usb}}}}}</td>

+

<td>Selects which serial port to use for communication.</td>

+

</tr>

+

<tr>

+

+

<td>300 {{!}} 1200 {{!}} 2400 {{!}} 4800 {{!}} 9600 {{!}} 19200 {{!}} 38400 {{!}} 57600 {{!}} 115200{{#ifeq: {{{rs485}}} | 1 | {{!}} 230400 {{!}} 460800 {{!}} 921600 {{!}} 1000000 {{!}} 3000000|}}; default: 115200</td>

+

<td>Serial data transmission rate (in bits per second).</td>

+

</tr>

+

<tr>

+

+

<td>{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|{{#ifeq:{{{series}}}|TRB2||5 {{!}} 6 {{!}}}} 7 {{!}} |}}8; default: 8</td>

+

<td>Number of data bits for each character.</td>

+

</tr>

+

<tr>

+

+

<td>1{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1| {{!}} 2|}}; default: 1</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>

+

<td>Parity</td>

+

<td>Even {{!}} Odd{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1| {{!}} Mark {{!}} Space|}} {{!}} None; default: None</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.

+

<ul>

+

<li>None (N) - no parity method is used.</li>

+

<li>Odd (O) - the parity bit is set so that the number of "logical ones (1s)" has to be odd.</li>

+

<li>Even (E) - the parity bit is set so that the number of "logical ones (1s)" has to be even.</li>{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|<li>Space (s) - the parity bit will always be a binary 0.</li>

+

<li>Mark (M) - the parity bit will always be a binary 1.</li>|}}

+

</ul>

+

</td>

+

</tr>

+

<tr>

+

<td>Flow control</td>

+

<td>None {{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1| {{!}} RTS/CTS {{!}} Xon/Xoff|}}; default: None</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.

+

{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|<ul>

+

<li>RTS/CTS - 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>Xon/Xoff - 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>|}}

+

</td>

+

</tr>

+

<tr>

+

<td>Local Address</td>

+

<td>integer [0..65535]; default: none</td>

+

<td>Outstation Link-Layer address.</td>

+

</tr>

+

<tr>

+

<td>Remote Address</td>

+

<td>integer [0..65535]; default: none</td>

+

<td>Master Link-Layer address.</td>

+

</tr>

+

<tr>

+

<td>Unsolicited enabled</td>

+

<td>off {{!}} on; default: none</td>

+

<td>Enables the transmission of unsolicited messages.</td>

+

</tr>{{#ifeq: {{{rs485}}} | 1 |

+

<tr>

+

<td>RS485: Full Duplex</td>

+

<td>off {{!}} on; default: off</td>

+

<td>Enables RS485 full duplex.</td>

+

</tr>|}}

+

</table>

+

|}}

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

TomasG

Administrators

1,223

edits