Template:Networking rutos manual modbus: Difference between revisions
Template:Networking rutos manual modbus (view source)
Revision as of 13:15, 22 September 2023
, 22 September 2023no edit summary
No edit summary |
No edit summary |
||
| Line 32: | Line 32: | ||
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: | 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: | ||
[[File: | [[File:Networking_rutos_manual_modbus_modbus_tcp_server.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
| Line 105: | Line 105: | ||
The <b>Modbus Serial Server Configuration</b> section is used to configure serial servers. By default, the list is empty. To add a new server instance, enter the instance name, select serial interface and click the 'Add' button. | The <b>Modbus Serial Server Configuration</b> section is used to configure serial servers. By default, the list is empty. To add a new server instance, enter the instance name, select serial interface and click the 'Add' button. | ||
[[File: | [[File:Networking_rutos_manual_modbus_modbus_serial_server_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 server instance configuration page. | After clicking 'Add' you will be redirected to the newly added server instance configuration page. | ||
[[File: | [[File:Networking_rutos_manual_modbus_modbus_serial_server_configuration_rs232_{{#ifeq:{{#expr: {{{rs232}}} or {{{usb}}}}} |1|1|0}}_v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
| Line 223: | Line 223: | ||
==Modbus TCP Client== | ==Modbus TCP Client== | ||
A <b>Modbus Client</b> device can request data from Modbus servers. The Modbus TCP Client section is used to configure Modbus TCP servers. By default, the server list is empty. To add a new server, click the 'Add' button | A <b>Modbus Client</b> device can request data from Modbus servers. The Modbus TCP Client section is used to configure Modbus TCP servers and enable Client. By default, the server list is empty and client is disabled. To add a new server, click the 'Add' button | ||
[[File: | [[File:Networking_rutos_manual_modbus_modbus_tcp_client_modbus_tcp_server_devices_add_button.png|border|class=tlt-border]] | ||
After clicking 'Add' you will be redirected to the newly added server's configuration page. | After clicking 'Add' you will be redirected to the newly added server's configuration page. | ||
| Line 233: | Line 233: | ||
The <b>Server Device Configuration</b> section is used to configure the parameters of Modbus TCP servers that the Client (this {{{name}}} device) will be querying with requests. The figure below is an example of the Server Device Configuration and the table below provides information on the fields contained in that section: | The <b>Server Device Configuration</b> section is used to configure the parameters of Modbus TCP servers that the Client (this {{{name}}} device) will be querying with requests. The figure below is an example of the Server Device Configuration and the table below provides information on the fields contained in that section: | ||
[[File: | [[File:Networking_rutos_manual_modbus_modbus_tcp_client_server_device_configuration.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
| Line 311: | Line 311: | ||
The Request Configuration list is empty by default. To add a new Request Configuration loon to the Add New Instance section. Enter a custom name into the 'Name' field and click the 'Add' button: | The Request Configuration list is empty by default. To add a new Request Configuration loon to the Add New Instance section. Enter a custom name into the 'Name' field and click the 'Add' button: | ||
[[File: | [[File:Networking_rutos_manual_modbus_modbus_tcp_client_requests_configuration_add_new_instance.png|border|class=tlt-border]] | ||
The new Request Configuration should become visible in the list: | The new Request Configuration should become visible in the list: | ||
| Line 368: | Line 368: | ||
<b>Additional note:</b> by default the newly added Request Configurations are turned off. You can use the on/off slider to the right of the Request Configuration to turn it on: | <b>Additional note:</b> by default the newly added Request Configurations are turned off. You can use the on/off slider to the right of the Request Configuration to turn it on: | ||
[[File: | [[File:Networking_rutos_manual_modbus_modbus_tcp_client_requests_configuration_on_off_slider.png|border|class=tlt-border]] | ||
---- | ---- | ||
After having configured a request, you should see a new 'Request Configuration Testing' section appear. It is used to check whether the configuration works correctly. Simply click the 'Test' button and a response should appear in the box below. A successful response to a test may look something like this: | After having configured a request, you should see a new 'Request Configuration Testing' section appear. It is used to check whether the configuration works correctly. Simply click the 'Test' button and a response should appear in the box below. <b>Note:</b> to use test buttons, you need to enable [[#Modbus_TCP_Client|Client section]]. A successful response to a test may look something like this: | ||
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_testing.png|border|class=tlt-border]] | [[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_testing.png|border|class=tlt-border]] | ||
| Line 380: | Line 380: | ||
The figure below is an example of the Alarms Configuration list. To create a new Alarm, click the 'Add' button. | The figure below is an example of the Alarms Configuration list. To create a new Alarm, click the 'Add' button. | ||
[[File: | [[File:Networking_rutos_manual_modbus_modbus_tcp_client_alarms_configuration_add_button.png|border|class=tlt-border]] | ||
After adding the Alarm you should be redirected to its configuration page which should look similar to this: | After adding the Alarm you should be redirected to its configuration page which should look similar to this: | ||
| Line 400: | Line 400: | ||
<td>Function code</td> | <td>Function code</td> | ||
<td>Read Coil Status (1) | Read Input Status (2) | Read Holding Registers (3) | Read Input Registers (4); default: <b>Read Coil Status (1)</b></td> | <td>Read Coil Status (1) | Read Input Status (2) | Read Holding Registers (3) | Read Input Registers (4); default: <b>Read Coil Status (1)</b></td> | ||
<td>Modbus function used for this alarm's Modbus request. The Modbus TCP Client (this {{{name}}} device) perform this request as often as specified in the 'Period' field in [[# | <td>Modbus function used for this alarm's Modbus request. The Modbus TCP Client (this {{{name}}} device) perform this request as often as specified in the 'Period' field in [[#Server_Device_Configuration|Server Device Configuration]].</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||