Changes

=Summary=

==Summary==

Modbus TCP Master section is used for configuring your router as a master device and other routers configured in this section as slave devices. A Modbus TCP master device can then request data from these Modbus TCP slaves. Firstly, let's configure our second router which will be acting as a slave device.

Modbus TCP Master section is used for configuring your router as a master device and other routers configured in this section as slave devices. A Modbus TCP master device can then request data from these Modbus TCP slaves. Here is the scheme to make things easier to understand:

 

 

 

Firstly, let's configure our second router which will be acting as a slave device.

==Configuring Modbus TCP slave device==

==Configuring Modbus TCP slave device==

[[File:ModbusTCPMasterSlaveEnableTCP.png]]

[[File:ModbusTCPMasterSlaveEnableTCP.png]]

==Adding new slave device==

 

===Adding new slave device===

On '''master device''' (in this example master device has 192.168.1.1 internal IP address) open '''Services->Modbus->Modbus TCP Master'''.

On '''master device''' (in this example master device has 192.168.1.1 internal IP address) open '''Services->Modbus->Modbus TCP Master'''.

Now the slave device is added to the Modbus TCP Master section but we need to test if it is working.

Now the slave device is added to the Modbus TCP Master section but we need to test if it is working.

==Testing==

===Testing===

[[File:AddedSlaveDevice.png]]

[[File:AddedSlaveDevice.png]]

     </tr>

     </tr>

</table>

</table>

'''Note''': During the time this article is written, we need to 'Save' the configuration first before clicking the 'Test' button. This will redirect you to the Modbus TCP Master page and you will need to click 'Edit' button again to try and test the functionality of this request.

'''Note''': During the time this article is written, we need to 'Save' the configuration first before clicking the 'Test' button. This will redirect you to the Modbus TCP Master page and you will need to click 'Edit' button again to try and test the functionality of this request.

We can see that the slave device returns the registers master device has asked for. More information about how to understand the information we are getting from registers: '''[[Monitoring via Modbus]]'''

We can see that the slave device returns the registers master device has asked for. More information about how to understand the information we are getting from registers: '''[[Monitoring via Modbus]]'''

==Alarms==

===Alarms===

Alarms are a way of setting up automated actions when some Modbus values meet user specified conditions. To configure these alarms we click on ''''Alarms'''' button:

Alarms are a way of setting up automated actions when some Modbus values meet user specified conditions. To configure these alarms we click on ''''Alarms'''' button:

</table>

</table>

==Clone Slave Configuration==

===Clone Slave Configuration===