REDAC Blocks and Configurations
This page describes all available hardware entities and their possible configurations.
The firmware on the hybrid controller accepts various JSON message structures
as part of the pyanabrid.redac.protocol.messages.SetConfigRequest
message, which are documented below.
Alternatively, you can find the full JSON schema for the configuration parameters
here
.
Base Elements and Computations
All function blocks in the REDAC are made up of elements, with each implementing one computation from the following list. The list of elements contained on a function block together with the attributes of the computation define which configuration parameters need to be sent to configure a function block (see below).
Please remember that in the REDAC, all summation is done implicitly by the pyanabrid.redac.blocks.IBlock
.
Function Blocks
The following function blocks are available.
The configuration can be set with a pyanabrid.redac.protocol.messages.SetConfigRequest
message
with pyanabrid.redac.protocol.messages.SetConfigRequest.config
(or the respective sub-dictionary)
confirming to the following JSON schema.
type |
object |
||
properties |
|||
|
oneOf |
type |
array |
items |
#integrator_config |
||
maxItems |
8 |
||
minItems |
8 |
||
type |
object |
||
patternProperties |
|||
|
#integrator_config |
||
additionalProperties |
False |
||
maxProperties |
8 |
||
minProperties |
0 |
||
additionalProperties |
False |
||
definitions |
|||
|
type |
object |
|
properties |
|||
|
type |
number |
|
maximum |
1.0 |
||
minimum |
-1.0 |
||
|
enum |
100, 10000 |
|
additionalProperties |
False |
The configuration can be set with a pyanabrid.redac.protocol.messages.SetConfigRequest
message
with pyanabrid.redac.protocol.messages.SetConfigRequest.config
(or the respective sub-dictionary)
confirming to the following JSON schema.
type |
object |
||
properties |
|||
|
oneOf |
type |
array |
items |
#input_spec |
||
maxItems |
32 |
||
minItems |
32 |
||
type |
object |
||
patternProperties |
|||
|
#input_spec |
||
additionalProperties |
False |
||
maxProperties |
31 |
||
minProperties |
0 |
||
|
type |
array |
|
items |
type |
integer |
|
maximum |
8 |
||
minimum |
0 |
||
additionalProperties |
False |
||
definitions |
|||
|
type |
integer |
|
maximum |
15 |
||
minimum |
0 |
||
|
oneOf |
#input |
|
type |
null |
The configuration can be set with a pyanabrid.redac.protocol.messages.SetConfigRequest
message
with pyanabrid.redac.protocol.messages.SetConfigRequest.config
(or the respective sub-dictionary)
confirming to the following JSON schema.
type |
object |
||
properties |
|||
|
oneOf |
type |
array |
items |
#factor |
||
maxItems |
32 |
||
minItems |
32 |
||
type |
object |
||
patternProperties |
|||
|
#factor |
||
additionalProperties |
False |
||
maxProperties |
31 |
||
minProperties |
0 |
||
additionalProperties |
False |
||
definitions |
|||
|
type |
number |
|
maximum |
20.0 |
||
minimum |
-20.0 |
The configuration can be set with a pyanabrid.redac.protocol.messages.SetConfigRequest
message
with pyanabrid.redac.protocol.messages.SetConfigRequest.config
(or the respective sub-dictionary)
confirming to the following JSON schema.
type |
object |
||
properties |
|||
|
oneOf |
type |
array |
items |
#input_spec |
||
maxItems |
16 |
||
minItems |
0 |
||
type |
object |
||
patternProperties |
|||
|
#input_spec |
||
additionalProperties |
False |
||
maxProperties |
15 |
||
minProperties |
0 |
||
additionalProperties |
False |
||
definitions |
|||
|
type |
integer |
|
maximum |
31 |
||
minimum |
0 |
||
|
oneOf |
type |
array |
items |
#input |
||
maxItems |
32 |
||
minItems |
32 |
||
#input |
|||
type |
null |