AUTOSAR Communication
The communication interface of an AUTOSAR software-component consists of well-defined ports. An AUTOSAR component communicates through its ports with other AUTOSAR software components or Basic Software (BSW) services. A port provides information to, or requires information from, its communication partners. Each port owned by the component maps to a communication interface, based on the component functional requirements. Communication interfaces include:
Sender-receiver (S-R) interface, for message passing
Client-server (C-S) interface, for function invocation
Mode-switch (M-S) interface, for managing mode-based execution
Nonvolatile (NV) data interface, for port-based access to NV data
Parameter interface, for port-based access to parameter data
Trigger interface, for managing trigger-based execution
To configure AUTOSAR communication for a component port, you create an AUTOSAR interface, map the port to the interface, and map Simulink® elements, such as a root inport or outport, to the AUTOSAR port as required by the type of interface. Use the AUTOSAR Dictionary and the Code Mappings editor or equivalent AUTOSAR property and map functions.
Blocks
| Signal Invalidation | Control AUTOSAR root outport data element invalidation |
Functions
getDataDefaults | Get default end-to-end (E2E) protection method for AUTOSAR component model (Since R2022b) |
setDataDefaults | Set default end-to-end (E2E) protection method for AUTOSAR component model (Since R2022b) |
getDataTransfer | Get AUTOSAR mapping information for Simulink data transfer |
mapDataTransfer | Map Simulink data transfer to AUTOSAR inter-runnable variable |
getInternalDataPackaging | Get default internal data packaging for AUTOSAR component model (Since R2021a) |
setInternalDataPackaging | Set default internal data packaging for AUTOSAR component model (Since R2021a) |
getFunctionCaller | Get AUTOSAR mapping information for Simulink function-caller block |
mapFunctionCaller | Map Simulink function-caller block to AUTOSAR client port and operation |
overflowed | Determine when message queue overflows |
Objects
autosar.api.getAUTOSARProperties | Configure AUTOSAR software component elements and properties programmatically |
autosar.api.getSimulinkMapping | Map Simulink elements to AUTOSAR elements |
Topics
Sender-Receiver Communication
- Configure AUTOSAR Sender-Receiver Communication
Read and write AUTOSAR data by using port-based sender-receiver communication. - Configure AUTOSAR Queued Sender-Receiver Communication
Read and write queued AUTOSAR data by using port-based sender-receiver communication. - Configure AUTOSAR Sender-Receiver Interface Ports for End-to-End Protection
Provide end-to-end (E2E) protection for AUTOSAR sender-receiver data transmission. - Programmatically Configure AUTOSAR Sender-Receiver Communication
Configure sender-receiver communication using AUTOSAR property and map functions.
Client-Server Communication
- Configure AUTOSAR Client-Server Communication
Implement AUTOSAR client and server runnables with Simulink Function and Function Caller blocks. - Configure Client-Server Communication in AUTOSAR Architectures Using Service Interfaces
Configure client-server communication by using client server ports and service interfaces in AUTOSAR architectures. - Programmatically Configure AUTOSAR Client-Server Communication
Configure client-server communication using AUTOSAR property and map functions.
Mode-Switch Communication
- Configure AUTOSAR Mode-Switch Communication
Define AUTOSAR modes and mode elements to activate runnables in response to system mode changes. - Programmatically Configure AUTOSAR Mode-Switch Communication
Configure mode-switch communication using AUTOSAR property and map functions.
Nonvolatile Communication
- Configure AUTOSAR Nonvolatile Data Communication
Read and write AUTOSAR nonvolatile (NV) data by using port-based NV data communication. - Programmatically Configure AUTOSAR Nonvolatile Communication
This example shows how to programmatically read and write AUTOSAR nonvolatile (NV) data using port-based NV data communication.
Ports
- Configure AUTOSAR Port Parameters for Communication with Parameter Software Component
Configure AUTOSAR parameter receiver component for port-based access to parameter data. Generate ARXML descriptions of parameter software components and ports. - Configure AUTOSAR Ports By Using Simulink Bus Ports
Model AUTOSAR ports by using Simulink In Bus Element and Out Bus Element blocks.
Runnables and Events
- Configure Receiver for AUTOSAR External Trigger Event Communication
Define trigger interface that activates AUTOSAR runnables in response to external trigger events. - Programmatically Configure AUTOSAR Runnables and Events
This example shows how to programmatically configure AUTOSAR runnables and events.
