31,703
edits
Template:Networking rut manual modbus: Difference between revisions
Template:Networking rut manual modbus (view source)
Revision as of 07:50, 2 April 2019
, 2 April 2019no edit summary
No edit summary |
No edit summary |
||
| Line 73: | Line 73: | ||
<tr> | <tr> | ||
<td>Slave ID</td> | <td>Slave ID</td> | ||
<td>integer [1.. | <td>integer [1..255]; Default: <b>none</b></td> | ||
<td>Slave ID. Each slave in a network is assigned a unique identifier randging from 1 to | <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> | ||
<tr> | <tr> | ||
| Line 96: | Line 96: | ||
<td>Maximum response wait time</td> | <td>Maximum response wait time</td> | ||
</tr> | </tr> | ||
</table> | |||
===Requests configuration=== | |||
---- | |||
A Modbus <b>request</b> is | |||
[[File:{{{file_requests}}}]] | |||
<table class="nd-mantable"> | |||
<tr> | |||
<th>Field name</th> | |||
<th>Value</th> | |||
<th>Description</th> | |||
</tr> | |||
<tr> | |||
<td>Name</td> | |||
<td>string; Default: <b>Unnamed Parameter</b></td> | |||
<td>Request name. Used for easier management purposes</td> | |||
</tr> | |||
<tr> | |||
<td>Data type</td> | |||
<td>8bit INT | 8bit UINT | 16bit INT, high byte first | 16bit INT, low byte first | 16bit UINT, high byte first | 16bit UINT, low byte first | 32bit float, Byte order 1,2,3,4 | 32bit float, Byte order 4,3,2,1 | 32bit float, Byte order 2,1,4,3 | 32bit float, Byte order 3,4,1,2; Default: <b>16bit INT, high byte first</b></td> | |||
<td>Type of data contained in Modbus registers</td> | |||
</tr> | |||
<tr> | |||
<td>Function</td> | |||
<td>1 | 2 | 3 | 4 | 5 | 15 | 16; Default: <b>3</b></td> | |||
<td></td> | |||
</tr> | |||
<tr> | |||
<td>First Register</td> | |||
<td>integer [0..65535]; Default: <b>1</b></td> | |||
<td>First Modbus register from which data will be read</td> | |||
</tr> | |||
<tr> | |||
<td>Number of Registers</td> | |||
<td>integer [1..2000]; Default: <b>none</b></td> | |||
<td>Number of Modbus registers that will be read during the request</td> | |||
</tr> | |||
<tr> | |||
<td>Enabled</td> | |||
<td>yes | no; Default: <b>no</b></td> | |||
<td>Turns the request ON or OFF</td> | |||
</tr> | |||
<tr> | |||
<td>Test</td> | |||
<td>- (interactive button)</td> | |||
<td>Generates a Modbus request according to given parameters in order to test the request configuration. You must first save the configuration before you can use the Test button</td> | |||
</tr> | |||
<tr> | |||
<td>Delete</td> | |||
<td>- (interactive button)</td> | |||
<td>Deletes the request</td> | |||
</tr> | |||
<tr> | |||
<td>Add</td> | |||
<td>- (interactive button)</td> | |||
<td>Adds a new request request</td> | |||
</tr> | |||
</table> | </table> | ||
==Modbus Data to Server== | ==Modbus Data to Server== | ||
A Modbus <b>master</b> device can request data from Modbus slaves. The Modbus TCP Master section is used to configure Modbus TCP slaves. To add a new slave, enter a custom name, slave's ID, IP address and port and click the "Add" button: | |||
[[File:{{{file_add_new_sender}}}]] | [[File:{{{file_add_new_sender}}}]] | ||