Line 642: |
Line 642: |
| This section is used to create server instances that the Client (this {{{name}}} device) will be querying with requests. | | This section is used to create server instances that the Client (this {{{name}}} device) will be querying with requests. |
| | | |
− | [[File:Networking_rutos_manual_modbus_modbus_serial_master_modbus_slave_device_configuration_v1.png|border|class=tlt-border]] | + | [[File:Networking_rutos_manual_modbus_modbus_serial_client_modbus_server_device_configuration.png|border|class=tlt-border]] |
| | | |
| By default there are no instances created. To add a new server configuration, enter an instance name, select a serial device instance and click the 'Add' button. | | By default there are no instances created. To add a new server configuration, enter an instance name, select a serial device instance and click the 'Add' button. |
| | | |
− | [[File:Networking_rutos_manual_modbus_modbus_serial_master_modbus_slave_device_configuration_add_button_v1.png|border|class=tlt-border]] | + | [[File:Networking_rutos_manual_modbus_modbus_serial_client_modbus_server_device_configuration_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 654: |
Line 654: |
| The <b>Server Device Configuration</b> section is used to configure the parameters of Modbus RTU 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 RTU 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:Networking_rutos_manual_modbus_modbus_serial_master_slave_device_configuration_v1.png|border|class=tlt-border]] | + | [[File:Networking_rutos_manual_modbus_modbus_serial_client_server_device_configuration.png|border|class=tlt-border]] |
| | | |
| <table class="nd-mantable"> | | <table class="nd-mantable"> |
Line 679: |
Line 679: |
| <tr> | | <tr> |
| <td>Server ID</td> | | <td>Server ID</td> |
− | <td>integer [0..255]; default: <b>none</b></td> | + | <td>integer [0..255]; default: <b>1</b></td> |
| <td>Server ID. Each server in a network is assigned a unique identifier ranging from 1 to 255. When the client requests data from a server, the first byte it sends is the Server ID. When set to 0, the server will respond to requests addressed to any ID.</td> | | <td>Server ID. Each server in a network is assigned a unique identifier ranging from 1 to 255. When the client requests data from a server, the first byte it sends is the Server ID. When set to 0, the server will respond to requests addressed to any ID.</td> |
− | </tr>
| |
− | <tr>
| |
− | <td>Always reconnect</td>
| |
− | <td>off {{!}} on; default: <b>off</b></td>
| |
− | <td>Create new connection after every Modbus request.</td>
| |
| </tr> | | </tr> |
| <tr> | | <tr> |
| <td>Number of timeouts</td> | | <td>Number of timeouts</td> |
− | <td>integer [0..10]; default: <b>1</b></td> | + | <td>integer [0..10]; default: <b>0</b></td> |
| <td>Skip pending request and reset connection after number of request failures.</td> | | <td>Skip pending request and reset connection after number of request failures.</td> |
| </tr> | | </tr> |
Line 696: |
Line 691: |
| <td>Period {{!}} Schedule; default: <b>Period</b></td> | | <td>Period {{!}} Schedule; default: <b>Period</b></td> |
| <td></td> | | <td></td> |
− | </tr>
| |
− | <tr>
| |
− | <td>Delay</td>
| |
− | <td>integer [0..999]; default: <b>0</b></td>
| |
− | <td>Wait in milliseconds after connection initialization.</td>
| |
| </tr> | | </tr> |
| <tr> | | <tr> |
Line 722: |
Line 712: |
| 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:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_add_new_instance.png|border|class=tlt-border]] | + | [[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 779: |
Line 769: |
| <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:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_on_off_slider.png|border|class=tlt-border]] | + | [[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_Serial_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 791: |
Line 781: |
| The figure below is an example of the Modbus Client Alarms list. To create a new Alarm, click the 'Add' button. | | The figure below is an example of the Modbus Client Alarms list. To create a new Alarm, click the 'Add' button. |
| | | |
− | [[File:Networking_rutos_manual_modbus_modbus_serial_master_modbus_master_alarms_add_button.png|border|class=tlt-border]] | + | [[File:Networking_rutos_manual_modbus_modbus_tcp_client_alarms_configuration_add_button.png|border|class=tlt-border]] |
| | | |
| After this you should be redirected to that Alarm's configuration page which should look similar to this: | | After this you should be redirected to that Alarm's configuration page which should look similar to this: |