Difference between revisions of "Modbus TCP Client Read Maps"

From Control Solutions IoTServer Documentation
Jump to navigation Jump to search
(Created page with "File:Modbus TCP client read maps page.jpg <hr> Modbus TCP Client Read Maps are where you configure this device to read Modbus registers from other Modbus TCP devices, and...")
 
Line 2: Line 2:
 
<hr>
 
<hr>
 
Modbus TCP Client Read Maps are where you configure this device to read Modbus registers from other Modbus TCP devices, and store that data in local data objects. This page shows a list of currently configured read maps.
 
Modbus TCP Client Read Maps are where you configure this device to read Modbus registers from other Modbus TCP devices, and store that data in local data objects. This page shows a list of currently configured read maps.
 +
 +
When Modbus display setting "Number" is selected under User Settings, Modbus registers will be displayed as type (e.g. holding register) and register number.
 +
 +
[[File:Modbus display setting number.jpg]]
  
 
[[File:Modbus TCP client read maps lines number.jpg]]
 
[[File:Modbus TCP client read maps lines number.jpg]]

Revision as of 13:55, 1 May 2019

Modbus TCP client read maps page.jpg


Modbus TCP Client Read Maps are where you configure this device to read Modbus registers from other Modbus TCP devices, and store that data in local data objects. This page shows a list of currently configured read maps.

When Modbus display setting "Number" is selected under User Settings, Modbus registers will be displayed as type (e.g. holding register) and register number.

Modbus display setting number.jpg

Modbus TCP client read maps lines number.jpg