Adding active operations to a Rhapsody implementation block (RIMB)

You can add any number of active operations to a RIMB. Active operations, which are central to implementation blocks, are translated to AUTOSAR runnables and are called directly by the Runtime Environment (RTE). Active operations drive the execution of the implementation.

About this task

For each active operation, an AUTOSAR runnable is generated whose function is the implementation of the operation. An active operation calls any behavior inside the implementation block (RIMB), including statechart execution.

Procedure

  1. Right-click a RIMB implementation block and select Add New > AR3x_BMT > ActiveOperation.
  2. Specify the activation policy for the active operation. Just as when you defined a RIMBimplementation block, you must specify the activation for the active operation. On the General tab for the active operation, in the Policy field, select either Asynchronous or Periodic.
    • If you select Asynchronous, define the actual activation policy on the Access & Activation tab.
    • If you select Periodic, specify the period, offset, and duration in the Activation section of the General tab.
  3. If needed, select Guarded. When this check box is selected, this field specifies that all guarded active operations are to be mutually exclusive. This action is implemented in a dedicated AUTOSAR-exclusive area that all runnables that are generated for guarded operations are specified to “runs within.”

What to do next

While an active operation might be implemented by any code, Rational Rhapsody generates several help functions to facilitate the execution of statecharts.


Feedback