A JSON object describing an Modbus TCP device has the following syntax:

{
  "@Skill.Modbus.TCPDevice": {
    "name": "Device 1",
    "UUID": "58ed1445-1dc6-4c2f-84f2-8a0901183a4a",
    "ACL": { ... },
    "address": "device-1.local",
    "serverID": 1,
    "children": [
      ...
    ]
  }
}

Object Members

name	A string value containing the name of the device. The name is used to construct the device’s primary key.
UUID	A string value containing the unique UUID of the device.
ACL	An optional JSON object containing the element ACL of the device. The format of the object is described under JSON Format for ACLs in the Xentara user manual.
address	A string value containing the network address of the device. This can be a host name or an IP address, with or without a port number. If the address does not contain a port number, then the standard Modbus port (502) will be used. The format of the string is described under JSON Format for Network Addresses in the Xentara user manual.
serverID	An optional integer value containing the Modbus server ID (formerly slave ID) of the device. TCP devices generally do not use the server ID, and it is rarely necessary to specify a server ID. Some devices may require a server ID to be specified, however.
children	A JSON array containing the channels and polls of the device. The individual child elements are each represented by a double nested JSON object, as described in Element Blocks under Structure of the Model File in the Xentara user manual. The outer object has a single member whose name is the type of element, and whose value is another JSON object that contains the actual properties of the element.