JSON Format for Output Bits

See also

Skill Element Blocks in the Xentara user manual

A JSON object describing a output bit has the following syntax:

{
  "@Skill.PILPXI.PrecisionResistor": {
    "name": "Voltage Bit +12 V",
    "UUID": "d4c0c2c8-1609-4e08-8626-e8d063718bae",
    "ACL": { ... },
    "subUnit": 7,
    "bitNumber": 1,
    "initialState": false,
    "handler": "Card 1.Voltage Bit Handler"
  }
}

Object Members

name	A string value containing the name of the bit. The name is used to construct the bit’s primary key.
UUID	A string value containing the unique UUID of the bit.
ACL	An optional JSON object containing the element ACL of the bit. The format of the object is described under JSON Format for ACLs in the Xentara user manual.
subUnit	An integer value containing the 1-based sub-unit number of the bit. Sub-unit numbers are shared with other output sub-units, specifically output bits.
bitNumber	An integer value containing the 1-based sub-unit number of the bit. Sub-unit numbers are shared with other output sub-units, specifically output bits.
initialValue	This optional JSON Boolean value ("true" or "false") that determines how the bit is initialized. The initialization is performed at the beginning of the pre-operational stage, when Xentara is started or resumed from a suspended state. If this value is "true", then the bit is initialized by switching it on. If it is "false", the bit is initialized by switching it off. If you do not specify an initial value at all, the bit will not be initialized at all, and will retain whatever state it was in before.
handler	An optional string value describing the handler that should read and write the bit’s value. The string value must contain the primary key of the handler. If you do not specify a handler, the bit’s value will be unavailable, and the bit cannot be operated by writing the data point.