Changes

Template:Networking rut manual modbus (view source)

Revision as of 13:45, 23 July 2019

9,950 bytes added , 13:45, 23 July 2019

no edit summary

Line 1: Line 1:

==Summary==

−

~~'''~~Modbus~~'''~~ is a serial communications protocol. Simple and robust, it has since become a de facto standard communication protocol and is now a commonly available means of connecting industrial electronic devices. This chapter is an overview of the Modbus TCP functionality.

+

Modbus is a serial communications protocol. Simple and robust, it has since become a de facto standard communication protocol and is now a commonly available means of connecting industrial electronic devices. This chapter is an overview of the Modbus TCP functionality.

+

{{Template: Networking_rutxxx_manual_fw_disclosure

+

| fw_version = {{{fw_version}}}

+

}}

==Modbus TCP==

−

~~'''~~Modbus TCP~~'''~~ provides users with the possibility to set or get system parameters. The Modbus daemon acts as slave device. That means it accepts connections from a master (client) and sends out a response or sets some system related parameter in accordance with the given query.

+

Modbus TCP provides users with the possibility to set or get system parameters. The Modbus daemon acts as slave device. That means it accepts connections from a master (client) and sends out a response or sets some system related parameter in accordance with the given query.

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

Line 18: Line 22:

===Get Parameters===

----

−

Modbus parameters are held within ~~'''~~registers~~'''~~. Each register contains 2 bytes of information. For simplification, the number of registers for storing numbers is 2 (4 bytes), while the number of registers for storing text information is 16 (32 bytes). The register numbers and corresponding system values are described in the table below:

+

Modbus parameters are held within registers. Each register contains 2 bytes of information. For simplification, the number of registers for storing numbers is 2 (4 bytes), while the number of registers for storing text information is 16 (32 bytes). The register numbers and corresponding system values are described in the table below:

{{#ifeq: {{{series}}} | RUT2xx

Line 37: Line 41:

}}

−

* All ON/OFF commands only accept ~~'''~~0~~'''~~ and ~~'''~~1~~'''~~ values, which represent the following:

+

* All ON/OFF commands only accept 0 and 1 values, which represent the following:

<ul>

Line 81: Line 85:

<tr>

−

<th>Field ~~name~~</th>

+

<th>Field</th>

<th>Value</th>

<th>Description</th>

Line 87: Line 91:

<tr>

<td>Enabled</td>

−

<td>yes | no; ~~Default~~: no</td>

+

<td>yes | no; default: no</td>

−

<td>Turns communication with the slave device ON or ~~OFF~~</td>

+

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

</tr>

<tr>

−

<td>string; ~~Default~~: none</td>

+

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

−

<td>Slave device ~~custom~~ name, used for easier management purposes</td>

+

<td>Slave device's name, used for easier management purposes.</td>

</tr>

<tr>

<td>Slave ID</td>

−

<td>integer [1..255]; ~~Default~~: none</td>

+

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

−

<td>Slave ID. Each slave in a network is assigned a unique identifier ~~randging~~ from 1 to 255. When the master requests data from a slave, the first byte it sends is the Slave ID</td>

+

<td>Slave ID. Each slave in a network is assigned a unique identifier ranging from 1 to 255. When the master requests data from a slave, the first byte it sends is the Slave ID. When set to 0, the slave will respond to requests addressed to any ID.</td>

</tr>

<tr>

<td>IP address</td>

−

<td>ip; ~~Default~~: none</td>

+

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

−

<td>Slave device IP address</td>

+

<td>Slave device's IP address.</td>

</tr>

<tr>

−

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

+

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

−

<td>Slave device Modbus TCP port</td>

+

<td>Slave device's Modbus TCP port.</td>

</tr>

<tr>

<td>Period</td>

−

<td>integer [1..6400]; ~~Default~~: none</td>

+

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

−

<td>Interval at which requests are sent to the slave device</td>

+

<td>Interval at which requests are sent to the slave device.</td>

</tr>

<tr>

<td>Timeout</td>

−

<td>integer [1..30]; ~~Default~~: none</td>

+

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

−

<td>Maximum response wait time</td>

+

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

</tr>

</table>

Line 202: Line 206:

<tr>

−

<th>Field ~~name~~</th>

+

<th>Field</th>

<th>Value</th>

<th>Description</th>

Line 208: Line 212:

<tr>

<td>Enabled</td>

−

<td>yes | no; ~~Default~~: no</td>

+

<td>yes | no; default: no</td>

−

<td>Turns the alarm ON or ~~OFF~~</td>

+

<td>Turns the alarm on or off</td>

</tr>

<tr>

<td>Function code</td>

−

<td>Read Coil Status (1) | Read Input Status (2) | Read Holding Registers (3) | Read Input Registers (4); ~~Default~~: Read Coil Status (1)</td>

+

<td>Read Coil Status (1) | Read Input Status (2) | Read Holding Registers (3) | Read Input Registers (4); default: Read Coil Status (1)</td>

−

<td>Modbus function used in Modbus request</td>

+

<td>Modbus function used in Modbus request.</td>

</tr>

<tr>

<td>Register</td>

−

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

+

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

−

<td>Number of the ~~modbus~~ coil/input/holding register/input register that will be read</td>

+

<td>Number of the Modbus coil/input/holding register/input register that will be read.</td>

</tr>

<tr>

<td>Condition</td>

−

<td>More than | Less than | Equal to | Not Equal to; ~~Default~~: Equal to</td>

+

<td>More than | Less than | Equal to | Not Equal to; default: Equal to</td>

−

<td>When a value is obtained it will be compared against the value specified in the following field. The ~~comparisson~~ will be made in ~~acordance~~ with the condition specified in this field</td>

+

<td>When a value is obtained it will be compared against the value specified in the following field. The comparison will be made in accordance with the condition specified in this field.</td>

</tr>

<tr>

<td>Value</td>

−

<td>various; ~~Default~~: none</td>

+

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

−

<td>The value against which the read data will be compared</td>

+

<td>The value against which the read data will be compared.</td>

</tr>

<tr>

<td>Action</td>

−

<td>SMS | Trigger output | Modbus Request; ~~Default~~: SMS</td>

+

<td>SMS | Trigger output | Modbus Request; default: SMS</td>

<td>Action that will be taken if the condition is met. Possible actions:

<ul>

−

<li>SMS - sends and SMS message to a specified recipient(s)</li>

+

<li>SMS - sends and SMS message to a specified recipient(s).</li>

−

<li>Trigger output - changes the state of a specified output(s)</li>

+

<li>Trigger output - changes the state of a specified output(s).</li>

−

<li>Modbus Request - sends a Modbus request to a specified slave</li>

+

<li>Modbus Request - sends a Modbus request to a specified slave.</li>

</ul>

</td>

Line 244: Line 248:

<tr>

<td>SMS: Message</td>

−

<td>string; ~~Default~~: none</td>

+

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

−

<td>SMS message text</td>

+

<td>SMS message text.</td>

</tr>

<tr>

<td>SMS: Phone number</td>

−

<td>phone number; ~~Default~~: none</td>

+

<td>phone number; default: none</td>

−

<td>Recipient's phone number</td>

+

<td>Recipient's phone number.</td>

</tr>

<tr>

<td>Trigger output: Output</td>

−

<td>Open collector output | Relay output | Both; ~~Default~~: Open collector output</td>

+

<td>Open collector output | Relay output | Both; default: Open collector output</td>

−

<td>Which output(s) will be triggered</td>

+

<td>Which output(s) will be triggered.</td>

</tr>

<tr>

<td>Trigger output: I/O Action</td>

−

<td>Turn On | Turn Off | Invert; ~~Default~~: Turn On</td>

+

<td>Turn On | Turn Off | Invert; default: Turn On</td>

−

<td>Action that will taken on the specified output</td>

+

<td>Action that will taken on the specified output.</td>

</tr>

<tr>

<td>Modbus Request: IP address</td>

−

<td>ip | host; ~~Default~~: none</td>

+

<td>ip | host; default: none</td>

−

<td>Modbus slave's IP address</td>

+

<td>Modbus slave's IP address.</td>

</tr>

<tr>

<td>Modbus Request: Port</td>

−

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

+

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

−

<td>Modbus slave's port</td>

+

<td>Modbus slave's port.</td>

</tr>

<tr>

<td>Modbus Request: Timeout</td>

−

<td>integer [1..30]; ~~Default~~: 5</td>

+

<td>integer [1..30]; default: 5</td>

−

<td>Maximum time to wait for a response</td>

+

<td>Maximum time to wait for a response.</td>

</tr>

<tr>

<td>Modbus Request: ID</td>

−

<td>integer [1..255]; ~~Default~~: none</td>

+

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

−

<td>Modbus slave ID</td>

+

<td>Modbus slave ID.</td>

</tr>

<tr>

<td>Modbus Request: Modbus function</td>

−

+

−

<td>A function code specifies the type of register being addressed by a Modbus request</td>

+

<td>A function code specifies the type of register being addressed by a Modbus request.</td>

</tr>

<tr>

<td>Modbus Request: First register</td>

−

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

+

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

−

<td>Begins reading from the register specified in this field</td>

+

<td>Begins reading from the register specified in this field.</td>

</tr>

<tr>

<td>Modbus Request: Number of registers</td>

−

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

+

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

−

<td>The number of registers that will be read from the first register</td>

+

<td>The number of registers that will be read from the first register.</td>

+

</tr>

+

</table>

+

==Modbus Serial Master==

+

===RS232===

+

----

+

[[File:{{{file_rs232}}}]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Enabled</td>

+

<td>yes | no; default: no</td>

+

<td>Turns the Modbus RTU via RS232 on or off.</td>

+

</tr>

+

<tr>

+

+

<td>300 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 57600 | 115200; default: 19200</td>

+

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

+

</tr>

+

<tr>

+

+

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

+

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

+

</tr>

+

<tr>

+

<td>Parity</td>

+

<td>None | Even | Odd; default: Even</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>

+

</ul>

+

</td>

+

</tr>

+

<tr>

+

+

<td>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>Flow control</td>

+

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

+

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

+

</table>

+

===RS485===

+

----

+

[[File:{{{file_rs485}}}]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Enabled</td>

+

<td>yes | no; default: no</td>

+

<td>Turns the Modbus RTU via RS485 on or off.</td>

+

</tr>

+

<tr>

+

+

<td>300 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 57600 | 115200; default: 19200</td>

+

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

+

</tr>

+

<tr>

+

+

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

+

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

+

</tr>

+

<tr>

+

<td>Parity</td>

+

<td>None | Even | Odd; default: Even</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>

+

</ul>

+

</td>

+

</tr>

+

<tr>

+

+

<td>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>Flow control</td>

+

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

+

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

+

</table>

+

===Slaves===

+

----

+

[[File:{{{file_slave_settings}}}]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Enabled</td>

+

<td>yes | no; default: no</td>

+

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

+

</tr>

+

<tr>

+

<td>Slave ID</td>

+

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

+

<td>Slave ID. Each slave in a network is assigned a unique identifier randging from 1 to 255. When the master requests data from a slave, the first byte it sends is the Slave ID.</td>

+

</tr>

+

<tr>

+

<td>Period</td>

+

<td>integer [1..9999]; default: 10</td>

+

<td>Interval (in minutes) at which requests are sent to the slave device.</td>

+

</tr>

+

</table>

+

====Slave requests====

+

----

+

[[File:{{{file_slave_request}}}]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Enabled</td>

+

<td>yes | no; default: no</td>

+

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

+

</tr>

+

<tr>

+

<td>Function</td>

+

<td>Read Coil | Read Discrete Input | Read Holding Registers | Read Input Registers; default: Read Holding Registers</td>

+

<td>Modbus function used in Modbus request.</td>

+

</tr>

+

<tr>

+

<td>First Register</td>

+

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

+

<td>First Modbus register from which data will be read.</td>

+

</tr>

+

<tr>

+

<td>Number of Registers</td>

+

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

+

<td>Number of Modbus registers that will be read during the request/</td>

+

</tr>

+

</table>

+

====Slave alarms====

+

----

+

[[File:{{{file_slave_alarm}}}]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Enabled</td>

+

<td>yes | no; default: no</td>

+

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

+

</tr>

+

<tr>

+

<td>Function</td>

+

<td>Read Coil | Read Discrete Input | Read Holding Registers | Read Input Registers; default: Read Holding Registers</td>

+

<td>Modbus function used in Modbus request.</td>

+

</tr>

+

<tr>

+

<td>Register</td>

+

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

+

<td>Number of the Modbus coil/input/holding register/input register that will be read.</td>

+

</tr>

+

<tr>

+

<td>Condition</td>

+

<td>More than | Less than | Equal to | Not equal to; default: More than</td>

+

<td>When a value is obtained it will be compared against the value specified in the following field. The comparison will be made in accordance with the condition specified in this field.</td>

+

</tr>

+

<tr>

+

<td>Value</td>

+

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

+

<td>The value against which the read data will be compared.</td>

+

</tr>

+

<tr>

+

<td>Action</td>

+

<td>SMS | Trigger output | Modbus request; default: SMS</td>

+

<td>Action that will be taken if the condition is met. Possible actions:

+

<ul>

+

<li>SMS - sends and SMS message to a specified recipient(s).</li>

+

<li>Trigger output - changes the state of a specified output(s).</li>

+

<li>Modbus Request - sends a Modbus request to a specified slave.</li>

+

</ul>

+

</td>

</tr>

</table>

Dziugas

Bureaucrats, Interface administrators, Administrators

31,703

edits