JSON Format for Entry

A JSON object describing a EtherCAT Entry has the following syntax:

{
  "@Skill.CoE.Entry": {
    "id": "Channel Data 1",
    "uuid": "eb3e24b6-01ff-4928-bbd7-d75a40d125bf",
    "syncManager": 2,
    "bufferAddress": "0x0000.0",
    "index": "0x7000",
    "subIndex": 1,
    "dataType": "BOOLEAN",
    "direction": "output"
  }
}

Object Members

id	A string value containing the ID of the EtherCAT Entry Data. The ID is used to construct the entry’s primary key.
UUID	A string value containing the unique UUID of the EtherCAT Entry.
ACL	An optional JSON object containing the element ACL of the entry. The format of the block is described here.
syncManager	An integer value containing the entry's sync manager in the EtherCAT Device. Outputs have a sync manager value of 2 and inputs have a sync manager value of 3. However, it is not necessary. More details about sync manager can be found on EtherCAT Sync Manager.
bufferAddress	A string value containing the buffer address inside the IOmap of the EtherCAT network. More details about the IO mapping can be found on EtherCAT IO Map.
index	A string value containing the index's of the entry data in the device. The index list for CoE EtherCat communication can be found on Index.
subIndex	An integer value containing the sub index's of the entry data in the device. The index of each entry can have up to 255 subindexes.
dataType	A string value containing the data type of the entry data in the device. The list of supported data type is mentioned in the Data Types. Use the same name that appears in the table.
direction	An optional string value indicating the direction of the entry object. This value can be either "input" or "output". Usually, the direction is automatically determined through sync managers and indexes. However, in cases where certain devices deviate from the standard, a manual direction definition becomes necessary.

To obtain all this information about an active EtherCAT network, use the Device Information Application and for offline EtherCAT network, use the ESI and ENI Files.

Please remember that each element block requires two layers of {} due to the syntax restrictions of the JSON format.