Call AUTOSAR Diagnostic Event Manager (Dem) service interface
AUTOSAR Blockset / Classic Platform / Basic Software / Diagnostic Event Manager (Dem)
The AUTOSAR standard defines a Diagnostic Event Manager (Dem) service as a
part of Basic Software (BSW) that runs in the AUTOSAR Runtime Environment
(RTE). AUTOSAR software components access Dem services through client-server
calls. The DiagnosticMonitorCaller block calls the Dem service interface
DiagnosticMonitor to initiate a specified
Client port name — Name of client port AUTOSAR component uses to call Dem
DiagnosticMonitor (default) | character vector
Enter the name of the client port the AUTOSAR software
component uses to call the Dem service interface
Operation — Specify operation defined in Dem service interface
SetEventStatus (default) |
Select the operation that the AUTOSAR software
component calls from the Dem service interface
operations are defined by the AUTOSAR standard.
After the operation is selected, the inports and
outports for the block are generated to support the
The Operation parameter must be set to an operation supported by the schema currently specified by the model. The list of operations on the block parameters dialog reflects the operations supported by the current schema.
Data type for EventStatus — Specify a data type to represent a Dem event type
Specify an enumerated data type to represent a Dem event type required for some operations. For more information, see the AUTOSAR standard Specification of Diagnostic Event Manager.
Specify this parameter when
Operation is set to
Sample time — Block sample time
-1 (default) | scalar
Block sample time. The default sets the block to inherit its sample time from the model.
C/C++ Code Generation
Generate C and C++ code using Simulink® Coder™.
Version HistoryIntroduced in R2016b
R2023a: Basic Software caller blocks support all AUTOSAR schema versions
Starting in 23a, Basic Software caller (BSW) blocks support all AUTOSAR schema versions supported by AUTOSAR Blockset. The BSW blocks inherit the same schema version specified by the model. Code and ARXML generated from the component reflect the schema version specified on the model. When you change the schema version specified by the model, the software automatically replaces software calls to the correct operation. In some cases, the software may prompt you to confirm a change when moving between schema versions.