Xentara v1.2.1
User Manual
Loading...
Searching...
No Matches
JSON Format for Register Blocks and Registers

Register Blocks

A JSON object describing a register_block has the following syntax:

{
"@IOComponent.SignalFlow.RegisterBlock": {
"id": "Register Block",
"uuid": "7c963d3a-025c-4abf-a38f-9f8de9bd0b66",
"children": [
...
]
}
}

Object Members
idA string value containing the ID of the register block. The ID is used to construct the register block’s primary key.
uuidA string value containing the unique UUID of the register block.
children

A JSON array containing the registers contained within the register block.

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

Registers

A JSON object describing a register has the following syntax:

{
"@IO.SignalFlow.Register": {
"id": "Register 1",
"uuid": "68462001-920e-46cb-8676-15f35aac68fc",
"defaultValue": [ "uint16", 0 ]
}
}

Object Members
idA string value containing the ID of the register. The ID is used to construct the register’s primary key.
uuidA string value containing the unique UUID of the register.
defaultValue

A JSON array containing the data type and the initial value.

The following data types are supported:

Keyword Data Type
"int8"
8 bit signed integer
"int16"
16 bit signed integer
"int32"
32 bit signed integer
"int64"
64 bit signed integer
"uint8"
8 bit usigned integer
"uint16"
16 bit usigned integer
"uint32"
32 bit unsigned integer
"uint64"
64 bit unsigned integer
"float32"
single precision floating point number
"float64"
double precision floating point number
"bool"
Boolean value

The initial value must be a number within the range of the given data type, except for the data type “bool”, for which it must be a Boolean value (true or false, without quotes).