31,703
edits
Template:Networking rut manual modbus: Difference between revisions
Template:Networking rut manual modbus (view source)
Revision as of 08:28, 3 April 2019
, 3 April 2019no edit summary
No edit summary |
|||
| Line 46: | Line 46: | ||
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: | 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_slave}}}]] | [[File:{{{file_add_new_slave}}}]] | ||
| Line 71: | Line 70: | ||
</tr> | </tr> | ||
</table> | </table> | ||
You can create a maximum of 10 slave configurations. | |||
===Slave device configuration=== | ===Slave device configuration=== | ||
| Line 123: | Line 124: | ||
===Requests configuration=== | ===Requests configuration=== | ||
---- | ---- | ||
A Modbus <b>request</b> is way of obtaining data from Modbus slaves. The master a sends a request to a slave specifying which Modbus registers should be read. The slave then sends the requested data back to the Modbus master. | A Modbus <b>request</b> is way of obtaining data from Modbus slaves. The master a sends a request to a slave specifying which Modbus registers should be read. The slave then sends the requested data back to the Modbus master. You can create a maximum of 64 request configurations for each slave device. | ||
The figure below is an example of the Requests configuration section and the table below provides information contained in the fields of that section: | The figure below is an example of the Requests configuration section and the table below provides information contained in the fields of that section: | ||
| Line 143: | Line 144: | ||
<td>Data type</td> | <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>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> | <td>How read data will be stored</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 339: | Line 340: | ||
<td>URL</td> | <td>URL</td> | ||
<td>host | ip; Default: <b>none</b></td> | <td>host | ip; Default: <b>none</b></td> | ||
<td>Address of the server to which the data will be sent</td> | <td>Address of the server to which the data will be sent. .<br><b>Important note</b>: when using HTTPS, remember to add the <b><i>https://</i></b> prefix before the URL</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||