<VirtualEvent> elements define specifiers within a BEADL protocol that link to virtual entities defined by the BEADL framework that could generate state transitions.
The XML definition of a
<VirtualEvent> element inside the XML structure resembles the definition of
<HardwareEvent> elements with the exception of how the
connection attribute is being defined (see details below).
... <BeadlEvents> <VirtualEvent eventName="Event2" connection="ConnectionName.expression" type="" comment="" /> </BeadlEvents> ...
eventNamedefines a unique name of the event to be used within the BEADL task description.
connectiondefines which virtual resource the event should be linked to. See the definitions of virtual resources below.
typedefines the type of the specified event. 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
<VirtualEvent>element is defined in a trial. See here for a detailed description of the
Defined virtual resources
In the current version of BEADL, the following virtual events are defined. Please note that such virtual resources have only one component
expression specified that need to be used for the linked
A virtual event that occurs if a [BeadlArgument](/BEADL_XML/04_01_BEADL_BeadlArgument.html has a specific value.
A virtual event that occurs if a variable that was set in a preceding state (see VirtualAction has a specific value.
A virtual event that occurs if the duration between the start times of two states has a specific value.