9,305
edits
Changes
Template:Networking rutos manual modbus (view source)
Revision as of 11:54, 19 May 2022
, 11:54, 19 May 2022no edit summary
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
| series = {{{series}}}
| name = {{{name}}}
}}
}}
}}
}}
The <b>Slave Device Configuration</b> section is used to configure the parameters of Modbus TCP slaves that the Master (this {{{name}}} device) will be querying with requests. The figure below is an example of the Slave Device Configuration and the table below provides information on the fields contained in that section:
The <b>Slave Device Configuration</b> section is used to configure the parameters of Modbus TCP slaves that the Master (this {{{name}}} device) will be querying with requests. The figure below is an example of the Slave Device Configuration and the table below provides information on the fields contained in that section:
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_slave_device_configuration_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_slave_device_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>Slave ID</td>
<td>Slave ID</td>
<td>integer [0..255]; default: <b>1</b></td>
<td>integer [0..255]; default: <b>none</b></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>
<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>
<tr>
<tr>
<td>Port</td>
<td>Port</td>
<td>integer [0..65535]; default: <b>502</b></td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>Slave device's Modbus TCP port.</td>
<td>Slave device's Modbus TCP port.</td>
</tr>
</tr>
<tr>
<tr>
<td>Period</td>
<td>Period</td>
<td>integer [1..86400]; default: <b>10</b></td>
<td>integer [1..86400]; default: <b>60</b></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>
<tr>
<tr>
<td>Action</td>
<td>Action</td>
<td>{{#ifeq:{{{mobile}}}|1|<span style="color: #0054a6;">SMS</span> {{!}}|}} <span style="color: purple;">MODBUS Write Request</span>{{#switch:{{{series}}}|TCR1=|TRB2=|#default= {{!}} <span style="color: green;">Trigger output</span>}}; default: <b>MODBUS Write Request</b></td>
<td>{{#ifeq:{{{mobile}}}|1|SMS {{!}}|}} MODBUS Write Request{{#switch:{{{series}}}|TCR1=|TRB2=|#default= {{!}} Trigger output}}; default: <b>MODBUS Write Request</b></td>
<td>Action that will be taken if the condition is met. Possible actions:
<td>Action that will be taken if the condition is met. Possible actions:
<ul>{{#ifeq: {{{mobile}}} | 1 |
<ul>{{#ifeq: {{{mobile}}} | 1 |
</tr>{{#ifeq: {{{mobile}}} | 1 |
</tr>{{#ifeq: {{{mobile}}} | 1 |
<tr>
<tr>
<td><span style="color: #0054a6;">SMS</span>: Message</td>
<td><span style="color: #0054a6;">SMS: Message</span></td>
<td>string; default: <b>none</b></td>
<td>string; default: <b>none</b></td>
<td>SMS message text.</td>
<td>SMS message text.</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: #0054a6;">SMS</span>: Phone number</td>
<td><span style="color: #0054a6;">SMS: Phone number</span></td>
<td>phone number; default: <b>none</b></td>
<td>phone number; default: <b>none</b></td>
<td>Recipient's phone number.</td>
<td>Recipient's phone number.</td>
</tr>|}}
</tr>|}}
<tr>
<tr>
<td><span style="color: purple;">MODBUS Write Request</span>: IP address</td>
<td><span style="color: purple;">MODBUS Write Request: IP address</span></td>
<td>ip | host; default: <b>none</b></td>
<td>ip | host; default: <b>none</b></td>
<td>Modbus slave's IP address.</td>
<td>Modbus slave's IP address.</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: purple;">MODBUS Write Request</span>: Port</td>
<td><span style="color: purple;">MODBUS Write Request: Port</span></td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>Modbus slave's port.</td>
<td>Modbus slave's port.</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: purple;">MODBUS Write Request</span>: Timeout</td>
<td><span style="color: purple;">MODBUS Write Request: Timeout</span></td>
<td>integer [1..30]; default: <b>5</b></td>
<td>integer [1..30]; default: <b>5</b></td>
<td>Maximum time to wait for a response.</td>
<td>Maximum time to wait for a response.</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: purple;">MODBUS Write Request</span>: ID</td>
<td><span style="color: purple;">MODBUS Write Request: ID</span></td>
<td>integer [1..255]; default: <b>none</b></td>
<td>integer [1..255]; default: <b>none</b></td>
<td>Modbus slave ID.</td>
<td>Modbus slave ID.</td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: purple;">MODBUS Write Request</span>: Modbus function</td>
<td><span style="color: purple;">MODBUS Write Request: Modbus function</span></td>
<td>Read Force Single Coil (5) | Preset Single Register (6) | Force Multiple Coils (15) | Force Multiple Registers (16); default: <b>Force Single Coil (5)</b></td>
<td>Read Force Single Coil (5) | Preset Single Register (6) | Force Multiple Coils (15) | Force Multiple Registers (16); default: <b>Force Single Coil (5)</b></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>
<tr>
<tr>
<td><span style="color: purple;">MODBUS Write Request</span>: First register</td>
<td><span style="color: purple;">MODBUS Write Request: First register</span></td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>integer [0..65535]; default: <b>none</b></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>
<tr>
<tr>
<td><span style="color: purple;">MODBUS Write Request</span>: Values</td>
<td><span style="color: purple;">MODBUS Write Request: Values</span></td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>Register/Coil values to be written (multiple values must be separated by space character).</td>
<td>Register/Coil values to be written (multiple values must be separated by space character).</td>
</tr>{{#switch:{{{series}}}|TCR1=|TRB2=|#default=
</tr>{{#switch:{{{series}}}|TCR1=|TRB2=|#default=
<tr>
<tr>
<td><span style="color: green;">Trigger output</span>: Output</td>{{#switch:{{{series}}}
<td><span style="color: green;">Trigger output: Output</span></td>{{#switch:{{{series}}}
| RUTX|RUT2 =<td>4PIN output; default: <b>4PIN output</b></td>
| RUTX|RUT2 =<td>4PIN output; default: <b>4PIN output</b></td>
| TRB1|RUT3 =<td>Configurable Input/Output (3) {{!}} Configurable Input/Output (4); default: <b>Configurable Input/Output (3)</b></td>
| TRB1|RUT3 =<td>Configurable Input/Output (3) {{!}} Configurable Input/Output (4); default: <b>Configurable Input/Output (3)</b></td>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: green;">Trigger output</span>: I/O Action</td>
<td><span style="color: green;">Trigger output: I/O Action</span></td>
<td>Turn On {{!}} Turn Off {{!}} Invert; default: <b>Turn On</b></td>
<td>Turn On {{!}} Turn Off {{!}} Invert; default: <b>Turn On</b></td>
<td>Selects the action performed on the output.</td>
<td>Selects the action performed on the output.</td>
The <b>RS232 Slave Device Configuration</b> section is used to configure the parameters of Modbus RTU slaves that the Master (this {{{name}}} device) will be querying with requests. The figure below is an example of the RS232 Slave Device Configuration and the table below provides information on the fields contained in that section:
The <b>RS232 Slave Device Configuration</b> section is used to configure the parameters of Modbus RTU slaves that the Master (this {{{name}}} device) will be querying with requests. The figure below is an example of the RS232 Slave Device Configuration and the table below provides information on the fields contained in that section:
[[File:Networking_rutos_manual_modbus_modbus_serial_master_rs232_slave_device_configuration_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_modbus_modbus_serial_master_rs232_slave_device_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>Slave ID</td>
<td>Slave ID</td>
<td>integer [0..255]; default: <b>1</b></td>
<td>integer [0..255]; default: <b>none</b></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>
<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>
<tr>
<tr>
<td>Period</td>
<td>Period</td>
<td>integer [1..86400]; default: <b>10</b></td>
<td>integer [1..86400]; default: <b>60</b></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>
This section is used to configure the Modbus Serial Master's <b>RS485</b> serial interface settings. Refer to the figure and table below for information on RS485 configuration.
This section is used to configure the Modbus Serial Master's <b>RS485</b> serial interface settings. Refer to the figure and table below for information on RS485 configuration.
[[File:Networking_rutos_manual_modbus_modbus_serial_master_rs485_configuration_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_modbus_modbus_serial_master_rs485_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
The <b>RS485 Slave Device Configuration</b> section is used to configure the parameters of Modbus RTU slaves that the Master (this {{{name}}} device) will be querying with requests. The figure below is an example of the RS485 Slave Device Configuration and the table below provides information on the fields contained in that section:
The <b>RS485 Slave Device Configuration</b> section is used to configure the parameters of Modbus RTU slaves that the Master (this {{{name}}} device) will be querying with requests. The figure below is an example of the RS485 Slave Device Configuration and the table below provides information on the fields contained in that section:
[[File:Networking_rutos_manual_modbus_modbus_serial_master_rs485_slave_device_configuration_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_modbus_modbus_serial_master_rs485_slave_device_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>Slave ID</td>
<td>Slave ID</td>
<td>integer [0..255]; default: <b>1</b></td>
<td>integer [0..255]; default: <b>none</b></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>
<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>
<tr>
<tr>
<td>Period</td>
<td>Period</td>
<td>integer [1..86400]; default: <b>10</b></td>
<td>integer [1..86400]; default: <b>60</b></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>
