`<VirtualAction>` element

<VirtualAction> elements define specifiers within a BEADL protocol that link to virtual entities defined by the BEADL framework that can specific actions.

The XML definition of a <VirtualAction> element inside the XML structure resembles the definition of <HardwareAction> elements with the exception of how the connection attribute is being defined (see details below).

...
<BeadlActions>
  <VirtualAction actionName="Action2" connection="ConnectionName.expression" type="" comment="" />
</BeadlActions>
...

Attributes

actionName defines a unique name of the action to be used within the BEADL task description.
connection defines which virtual resource the action should be linked to. See the definitions of virtual resources below.
type defines the type of the specified action. This attribute is meant to be used in future releases and is currently not not required.
comment defines 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.

Child Elements

<Dependency> element: Definition under which condition the current <VirtualAction> element is defined in a trial. See here for a detailed description of the <Dependency> element.

Defined virtual resources

In the current version of BEADL, the following virtual actions are defined. Please note that such virtual resources have only one component expression specified that need to be used for the linked <ConnectionMapping> element.

CallbackAction

A virtual action that calls a specific software function through the task controlling environment. Such kind of implementations might violate certain real-time requirements and highly depends on the implementation of the hole system in general.

SetVariableAction

A virtual action that stores a value in a variable that can be accessed in subsequent states via the virtual event VariableEvent.

<VirtualAction> element