Disabling Modes. ETAS ASCET V6.3, AUTOSAR

ETAS Modes

Tip

When more than one runnable entity is triggered by the same mode entry (or exit), the order of execution of runnable entities is not defined. For portability, therefore, a system should not rely on a particular execution order.

9.3.3

Disabling Modes

A <MODE-DEPENDENCY> 1 / <DISABLED-MODE-IREFS> 2 element permits the behavior of an event to be different in different modes. This allows such use cases as the activation of a runnable entity to be suppressed/permitted when a certain mode is active.

To disable the activation of a runnable:

 In the software component editor, go to the "Event Specification " tab.

 In the "Events" pane, select the event ModeEvent .

 Disable the mode off .

Figure 62 : Mode off disabled in ModeEvent

The

<MODE-DEPENDENCY>

1 / <DISABLED-MODE-IREFS>

modes:

2 element specifies the disabled

1 AUTOSAR R3.1.5 or lower

2 AUTOSAR R4.0.*

ASCET V6.3 AUTOSAR User’s Guide 141

ETAS Modes

Listing 98: ARXML code – definition of a Mode-Switch event with disabled mode (AUTOSAR

R3.1.2)

ASCET V6.3 AUTOSAR User’s Guide 142

ETAS Modes

Listing 99: ARXML code – definition of a Mode-Switch event with disabled mode (AUTOSAR

R4.0.2)

When the mode specified within the <MODE-DEPENDENCY> 1 / <DISABLED-MODE-IREFS> element is active, the RTE will not activate the runnable (the activation is discarded).

2

For more information about the implementation of mode instances, please refer to the RTA-

RTE User Guide.

1 AUTOSAR R3.1.5 or lower

2 AUTOSAR R4.0.*

ASCET V6.3 AUTOSAR User’s Guide 143