<HardwareAction> elements define specifiers within a BEADL protocol that link directly to the physical output entities of the task controlling system. Therefore, a corresponding
<ConnectionMapping> has to be defined, to which this physical output can be linked to. By introducing this layered structure, the process of describing actions becomes more organized in case the physical hardware connection has multiple grouped individual outputs that need to be referred to, and simplifies compatibility between different hardware platforms.
... <BeadlActions> <HardwareAction actionName="Action1" connection="ConnectionName.Sink" type="" comment="" /> </BeadlActions> ...
actionNamedefines a unique name of the action to be used within the BEADL task description.
connectiondefines which physical output resource of the specified hardware should be linked to this action.
typedefines the type of the specified action. This attribute is meant to be used in future releases and is currently not not required.
commentdefines an additional documentation of the element that could be populated also in the code generation process for automatically generating the behavior task for the defined target platform of the task controlling system. This attribute is optional.
<Dependency>element: Definition under which condition the current
<HardwareAction>element is defined in a trial. See here for a detailed description of the