Changes

[[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]]

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===

[[File:AddedSlaveDevice.png]]

[[File:AddedSlaveDevice.png]]