Basics – Sender-Receiver and NVData Interfaces
Sender-receiver communication involves the transmission and reception of signals consisting of atomic data elements sent by one AUTOSAR SWC
and received by one or more SWC.
An SWC type can have multiple sender-receiver ports. Each sender-receiver port can contain multiple data elements, each of which can be sent and received independently. Data elements within the interface can be simple (integer, float, ...) or complex (array, matrix, record) types.
In ASCET, the SenderReceiver interface component is used to specify sender-receiver communication. Such a component can contain scalar variables, enumerations, arrays, matrices, and records. In addition, SenderReceiver interface components can be used to specify mode-switch interfaces; see also Modes and Mode Groups.
In AUTOSAR R4.*, a SenderReceiver interface must contain either data elements or one mode group. If a SenderReceiver interface contains both data elements and a mode group, an error of type MMdl281 is issued during code generation. If a SenderReceiver interface contains more than one mode group, an error MMdl286 is issued.
The SenderReceiver interface editor is used to specify the content of SenderReceiver interfaces.
NVData interface components work the same way as SenderReceiver interfaces, with two exceptions:
- The elements of an NVData interface are always placed in the non-volatile memory of the ECU.
- NVData interfaces cannot contain mode groups.
The NVData interface editor is used to specify the content of NVData interfaces.
You can
Set up a SenderReceiver or NVData Interface
Implement SenderReceiver or NVData Interface Elements
See also
Specifying a SenderReceiver or NVData Interface Prototype
Sending to a Port – Block Diagram Editor for SWC
Sending to a Port – ESDL Editor for SWC
Receiving from a Port – Block Diagram Editor for SWC