Post Page Advertisement [Top]

21.Rte_IInvalidateInvalidate a VariableDataPrototype referenced by a VariableAccess
in the dataWriteAccess role.

Syntax: void Rte_IInvalidate_<re>_<p>_<o>(Rte_Instance <instance>)
Where <re> is the runnable entity name, <p> the port name and <o> the VariableDataPrototype name.

invalidation is used to indicate whether a data item is invalid on transmission. The  RTE API call can be used by the sender to set a signal value as invalid

22.Rte_IStatusProvide the error status of a VariableDataPrototype referenced
by a VariableAccess in the dataReadAccess role.

Syntax: Std_ReturnType Rte_IStatus_<re>_<p>_<o>(Rte_Instance)
Where <re> is the runnable entity name, <p> the port name and <o> the VariableDataPrototype name.

23.Rte_IrvIReadProvide read access to the InterRunnableVariables with implicit behavior of an AUTOSAR SW-C.

Syntax: <return> Rte_IrvIRead_<re>_<o>(RTE_Instance <instance>)
Where <re> is the name of the runnable entity the API might be used in, <o> is the name of the VariableDataPrototype in role implicitInterRunnableVariable

Runnable entities in software components that use inter-runnable variables access the variable through this API call.  Since the API calls are generated in the software component's header file each API call must include the name of the runnable itself.

24.Rte_IrvIWriteProvide write access to the InterRunnableVariables with implicit behavior of an AUTOSAR SW-C

Syntax: void Rte_IrvIWrite_<re>_<o>(RTE_Instance <instance>, <data>)
Where <re> is the name of the RunnableEntity the API might be used in, <o> is the name of the VariableDataPrototype in the role implicitInterRunnableVariable to access and <data>
is the placeholder for the data the InterRunnableVariable shall be set to.

Usecase is similar to Rte_IrvIRead but this API is used to send data instead of receiving.

25.Rte_IrvIWriteRef: Provide a reference to the VariableDataPrototype defined with the implicitInterRunnableVariable role referenced by a VariableAccess in the writtenLocalVariable role.

Syntax: Rte_IrvIWriteRef_<re>_<o>( RTE_Instance )
Where is the name of the RunnableEntity the API might be used in, is the name of the VariableDataPrototype in the role implicitInterRunnableVariable to access. [Byps_] is an optional infix used when component wrapper method for bypass support is enabled for the related software component type

26.Rte_IrvReadProvide read access to the InterRunnableVariables with explicit behavior
of an AUTOSAR SW-C

Syntax: <return> Rte_IrvRead_<re>_<o>(RTE_Instance <instance>)
Where <re> is the name of the runnable entity the API might be used in, <o> is the name of the InterRunnableVariables

Usecase is similar to Rte_IrvIRead but this API is used for explicit access

27.Rte_IrvWriteProvide write access to the InterRunnableVariables with explicit behavior of an AUTOSAR SW-C.

Syntax: void Rte_IrvWrite_<re>_<o>(RTE_Instance <instance>, <data>)
Where <re> is the name of the runnable entity the API might be used in, <o> is the name of the InterRunnableVariable to access and <data> is the placeholder for the data the InterRunnableVariable shall be set to

Usecase is similar to Rte_IrvIWrite but this API is used for explicit access

28.Rte_Enter: Enter an exclusive area

Syntax: void Rte_Enter_<name>(Rte_Instance <instance>)
Where <name> is the exclusive area name

29.Rte_Exit: Leave an exclusive area.

Syntax: void Rte_Exit_<name>(Rte_Instance <instance>)
Where <name> is the exclusive area name

30.Rte_ModeProvides the currently active mode of a mode switch port.

Syntax: <return> Rte_Mode_<p>_<o>(Rte_Instance <instance>)
Where <p> is the port name, and <o> the ModeDeclarationGroup-Prototype name within the ModeSwitchInterface categorizing the port.

31.EnhancedRte_ModeProvides the currently active mode of a mode switch port. If the mode machine instance is in transition additionally the values of the previous and the next mode are provided

Syntax: 
<return> Rte_Mode_<p>_<o>( Rte_Instance <instance>, <previousmode>,<nextmode>)
Where <p> is the port name, and <o> the ModeDeclarationGroup-Prototype name within the ModeSwitchInterface categorizing the port

32.Rte_Trigger: Raise a external trigger of a trigger port.

Syntax: void Rte_Trigger_<p>_<o>(Rte_Instance <instance>)
Where <p> is the port name and <o> the Trigger within the trigger interface categorizing the port

External Trigger Occurred Event is used by entities external to an SW-C instance to activate runnables. An external trigger requires a port categorized by a trigger port Interface to be declared within the SW-C. 

33.Rte_IrTriggerRaise an internal trigger to activate Runnable entities of the same software component instance.

Syntax: void Rte_IrTrigger_<re>_<o>(Rte_Instance <instance>)

34.Rte_IFeedbackProvide access to acknowledgment notifications for implicit sender
receiver communication and to pass error notification to senders.

Syntax: Std_ReturnType Rte_IFeedback_<re>_<p>_<o> (RTE_Instance <instance>)
Where <re> is the runnable entity name, <p> the port name and <o> the VariableDataPrototype within the sender-receiver interface categorizing the port

When a software component sends data over a port and acknowledgment requests are defined then your application code can request transmission acknowledgment. This is done by requesting feedback from the RTE with this API call

35.Rte_IsUpdated: Provide access to the update flag for an explicit receiver.

Syntax: boolean Rte_IsUpdated_<p>_<o> (RTE_Instance <instance>)
Where <p> is the port name and <o> the VariableDataPrototype within the sender-receiver interface categorizing the port

36.Rte_PBCon: Provide access to the individual post-build artifacts of a VariationPointProxy for SWCs of a system containing different variants

Syntax: <return> Rte_PBCon_<vpp> ()
Where is the shortName of the VariationPointProxy

1 comment:

  1. awwsome explanation!! but it would be really helpful for us to visualize all the RTE APis if a demo sample code (with all the RTE apis) is explained.

    ReplyDelete

Bottom Ad [Post Page]