Operation-Invoked Events. ETAS ASCET V6.3, AUTOSAR

ETAS Internal Behavior

Figure 40 : Definition of the timing event Cyclic_10ms

Note that ASCET enables the user to specify the modes in which this timing event shall be

activated. For the use of application modes refer to chapter 9,

Modes

, on page 136.

When the timing event is mapped to a runnable entity (see section 8.2,

Runnable Entities

, on page 108), then ASCET generates the

<TIMING-EVENT> element in the configuration language:

Listing 60: ARXML code – definition of a timing event (all AUTOSAR versions)

A timing event must be named using the <SHORT-NAME> element. The name is used within other elements to reference the timing event. The short-name of a timing event does not need to be a valid C identifier.

The <START-ON-EVENT-REF DEST="RUNNABLE-ENTITY"> element defines the runnable entity that is to be activated when the event occurs. The <PERIOD> element specifies the time raster in seconds to be used by the RTE generator.

8.1.2

Operation-Invoked Events

Operation-Invoked events are automatically inserted in an ASCET software component when

you create a server port (see section 7.1.1,

server port).

Provided Ports

, on page 88 for how to create a

ASCET V6.3 AUTOSAR User’s Guide 104

ETAS Internal Behavior

Figure 41 : Operation-Invoked event for the server operations MaximumVal and

Notification

An Operation-Invoked event is defined using the <OPERATION-INVOKED-EVENT> element.

Each <OPERATION-INVOKED-EVENT> element must specify:

 the <SHORT-NAME> to refer to the event, which can be edited manually in ASCET by the user

 a <START-ON-EVENT-REF DEST="RUNNABLE-ENTITY"> reference to the runnable entity

 an <OPERATION-IREF> reference to the operation prototype and server port

The Operation-Invoked event for the operation MaximumValue is defined in the configuration language as follows:

Listing 61: ARXML code – definition of an Operation-Invoked event (AUTOSAR R3.1.2)

ASCET V6.3 AUTOSAR User’s Guide 105