AUTOSAR SWS DiagnosticEventManager

Specification of Diagnostic Event Manager
AUTOSAR CP R20-11
Document Title Specification of Diagnostic Event

Manager
Document Owner AUTOSAR
Document Responsibility AUTOSAR
Document Identification No 19
Document Status published

Part of AUTOSAR Standard Classic Platform
Part of Standard Release R20-11
Document Change History

Date Release Changed by Description
• Referenced DemEventFailureCycle-
CounterThreshold
removed
AUTOSAR • Remove Dem_J1939DcmClearDTC
2020-11-30 R20-11 Release from SWS_Dem_01101
Management • Add Dem_GetDTCSelectionResult-
ForClearDTC to the list of API’s in
SWS_Dem_01253
• Minor corrections / clarifications /
editorial changes
• Diagnostic SRS renamed from
SRS_DIAG_xxxx to RS_DIAG_xxxx
• DataType of size parameter
increased for FF and ED APIs
AUTOSAR • Inconsistencies and contradictions
2019-11-28 R19-11 Release within the AR4.3.1 specifications of
Management Dem and Dcm has been removed
• Minor corrections / clarifications /
editorial changes , For details please
refer to the Change Documentation
• Changed Document Status from
Final to published
1 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

AUTOSAR CP R20-11
• Clarified asynchronous API behavior

• IUMPR denominators are locked at
AUTOSAR operation cycle start
2018-10-31 4.4.0 Release • Support of typed C/S interfaces
Management • minor corrections / clarifications /
editorial changes; For details please
refer to the ChangeDocumentation
• Update and optimized interaction
between Dcm and Dem
• Made many functions asynchronous
AUTOSAR • Shifted constraint handling to explicit
2017-12-08 4.3.1 Release requirements instead of informative
Management text in ECUC tables
• minor corrections / clarifications /
• Removal of context workarounds and
reworked callback behaviour.
Introduced monitor status and
updated point in time of callback
processing.
• Introduced client concept for multiple
access to the Dem. Optimized APIs
AUTOSAR for better runtime performance and
2016-11-30 4.3.0 Release aligned return values to allow the
Management Dcm mapping to return values
according to ISO 14229-1 [1].
• Supporting event memories for
multiple diagnostic servers
• Clarified thresholds and operation
cycle handling

AUTOSAR CP R20-11
• New APIs
Dem_GetEventFreezeFrameDataEx
and Dem_GetEventExtendedData
RecordEx with buffersize as
parameter and corrected return value
defintions.
AUTOSAR • Providing OBD FreezFrame for UDS
2015-07-31 4.2.2 Release service 0x19 0x05
Management • ISO 14229-1:2013[2] NRC handling
for service 0x14
• Refined service interfaces for
DataElements
• Support of ISO 27145 (WWH-OBD /
AUTOSAR Euro VI)[3]
2014-10-31 4.2.1 Release • Update to support ISO
Management 14229-1:2013[1]
• Introduction of event dependencies
• Refined DTC/Event suppression
AUTOSAR • Further clarification of event

2014-03-31 4.1.3 Release combination
Management • Clarification of DTC groups
• Editorial changes
• Added API table for service
AUTOSAR interfaces
2013-10-31 4.1.2 Release • Clarification of event combination
Management • Editorial changes
• Removed chapter(s) on change
documentation

AUTOSAR CP R20-11
• Incorporated new and reporting of

several Dem internal data elements
• Supported J1939
• Supported OBD
• Reworked Dem/Dcm interface
• Introduced new debouncing
AUTOSAR behaviour and debounce counter
2013-03-15 4.1.1 storage
Administration
• Extended clear DTC functionality
• Supported event suppression
• Extended DTC storage behavior
• Incorporation of user-controlled
warning indicator requestet bit
• Incorporation of autostart behaviour
for operation cycles
• Introduced multiple formats per DTC
• Reworked Dem_ResetEventStatus
behavior
AUTOSAR • Reworked Dlt interaction
2011-12-22 4.0.3
Administration • Reworked Dem/Dcm interface
• Corrected include-structure and RTE
interfaces
• Refined several aspects on features
• Reworked Dem/Dcm interface
• Extended definition of ”Diagnostic
Monitor”
• Introduced "Event significance" and
AUTOSAR "DTC suppression"
2009-12-18 4.0.1
Administration • Reworked OBD (esp. interface for
service $02, readiness, and
permanent memory)
• Reworked file-structure
• Finalization of issues on Revision 1

AUTOSAR CP R20-11
• Improved and extended of Dem

functional description (especially:
status bit handling, event
displacement, debouncing, fault
confirmation and indicator handling,
event combination, enable- & storage
AUTOSAR conditions, event related data,
2009-12-04 3.1.4 operation cycle management)
Administration
• Introduced the approach for
functional diagnostics of SW-Cs
• Added Dlt interaction and debugging
interface
• Document structure reworked and
extended
• Legal disclaimer revised
• Document structure reworked and
extended
AUTOSAR • Add APIs and configuration
2008-08-13 3.1.1 parameters for OBD support
Administration
• Improve interaction between DCM
and software components
• Improvement of RTE compliance
• Improvement of configuration part
• Improvement of document structure
AUTOSAR • Rework and tightening of data type
2007-12-21 3.0.1 useage
Administration
• New API added
• Document meta information
extended
• Small layout adaptations made
AUTOSAR • “Advice for users” revised
2007-01-24 2.1.115
Administration • “Revision Information” added

AUTOSAR CP R20-11
• Complete rework and extension of

debouncing part
• Dem_ClearGroupOfDTC and
Dem_ClearSingleDTC replaced by
Dem_SingleDTC
• Dem_GetNextFilteredDTCAndFDC,
Dem_SetDTCFilterForRecords,
Dem_GetSizeOfFreezeFrame,
Dem_SetValueByOemId,
Dem_SetEnableCondition,
AUTOSAR Xxx_DemGetFaultDetectionCounter
2006-11-28 2.1
Administration added
• DTCTranslationType replaced by
DTCKind in several APIs
• Chapter "Service DEM" added
• Function IDs reworked
• File Structure reworked and
extended
• Configuration chapter reworked and
extended
• Dem_GetNextFilteredDTC reworked
AUTOSAR
2006-05-16 2.0 • Layout Adaptations
Administration

AUTOSAR CP R20-11
Disclaimer
This work (specification and/or software implementation) and the material contained in
it, as released by AUTOSAR, is for the purpose of information only. AUTOSAR and the
companies that have contributed to it shall not be liable for any use of the work.
The material contained in this work is protected by copyright and other types of intel-
lectual property rights. The commercial exploitation of the material contained in this
work requires a license to such intellectual property rights.
This work may be utilized or reproduced without any modification, in any form or by
any means, for informational purposes only. For any other purpose, no part of the work
may be utilized or reproduced, in any form or by any means, without permission in
writing from the publisher.
The work has been developed for automotive applications only. It has neither been
developed, nor tested for non-automotive applications.
The word AUTOSAR and the AUTOSAR logo are registered trademarks.

AUTOSAR CP R20-11
Table of Contents
1 Introduction and functional overview 20
2 Acronyms and Abbreviations 21

2.1 Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3 Related documentation 26
3.1 Input documents & related standards and norms . . . . . . . . . . . . 26
3.2 Related specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4 Constraints and assumptions 28
4.1 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2 Applicability to car domains . . . . . . . . . . . . . . . . . . . . . . . . 29
5 Dependencies to other modules 30
5.1 File structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.1.1 Code file structure . . . . . . . . . . . . . . . . . . . . . . . . 31
5.1.2 Header file structure . . . . . . . . . . . . . . . . . . . . . . . 31
5.2 Integration Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6 Requirements traceability 33
7 Functional specification 44
7.1 Startup behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
7.2 Monitor re-initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
7.3 Diagnostic event definition . . . . . . . . . . . . . . . . . . . . . . . . . 47
7.3.1 Event priority . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7.3.2 Event occurrence . . . . . . . . . . . . . . . . . . . . . . . . 50
7.3.3 Event kind . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7.3.4 Event destination . . . . . . . . . . . . . . . . . . . . . . . . 51
7.3.5 Diagnostic monitor definition . . . . . . . . . . . . . . . . . . 51
7.3.6 Event dependencies . . . . . . . . . . . . . . . . . . . . . . . 52
7.3.7 Component availability . . . . . . . . . . . . . . . . . . . . . 54
7.4 Diagnostic trouble code definition . . . . . . . . . . . . . . . . . . . . . 54
7.4.1 DTC kind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.4.2 DTC format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.4.3 DTC groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
7.4.4 DTC severity . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
7.4.5 Functional unit . . . . . . . . . . . . . . . . . . . . . . . . . . 59
7.4.6 DTC significance . . . . . . . . . . . . . . . . . . . . . . . . . 59
7.4.7 Suppress DTC output . . . . . . . . . . . . . . . . . . . . . . 60
7.4.8 Availability of events (visibility and computation) . . . . . . . 62
7.5 Monitored Component Definition . . . . . . . . . . . . . . . . . . . . . 65
7.5.1 Definition of components and dependencies . . . . . . . . . 66
7.6 Operation cycle management . . . . . . . . . . . . . . . . . . . . . . . 67

AUTOSAR CP R20-11
7.6.1 Operation Cycle Counters . . . . . . . . . . . . . . . . . . . . 69

7.6.1.1 Cycles since last failed . . . . . . . . . . . . . . . . . 69
7.6.1.2 Cyles since first failed . . . . . . . . . . . . . . . . . 70
7.6.1.3 Failed cycles . . . . . . . . . . . . . . . . . . . . . . 71
7.7 Event memory description . . . . . . . . . . . . . . . . . . . . . . . . . 71
7.7.1 Event status management . . . . . . . . . . . . . . . . . . . 73
7.7.1.1 Status bit support . . . . . . . . . . . . . . . . . . . . 77
7.7.1.2 Monitor status and UDS status update . . . . . . . . 77
7.7.1.3 Status bit transitions . . . . . . . . . . . . . . . . . . 80
7.7.1.4 Active/Passive status . . . . . . . . . . . . . . . . . . 83
7.7.1.5 Notification of status bit changes . . . . . . . . . . . 84
7.7.2 Event memory management . . . . . . . . . . . . . . . . . . 85
7.7.2.1 Event retention . . . . . . . . . . . . . . . . . . . . . 87
7.7.2.2 Clearing event memory entries . . . . . . . . . . . . 89
7.7.2.3 Event memory overflow indication . . . . . . . . . . . 93
7.7.2.4 Event displacement . . . . . . . . . . . . . . . . . . . 93
7.7.2.5 Reporting order of event memory entries . . . . . . . 96
7.7.3 Debouncing of diagnostic events . . . . . . . . . . . . . . . . 97
7.7.3.1 Counter based debounce algorithm . . . . . . . . . . 98
7.7.3.2 Time based debounce algorithm . . . . . . . . . . . 102
7.7.3.3 Monitor internal debounce algorithm . . . . . . . . . 107
7.7.3.4 Debounce algorithm initialization and reset conditions 107
7.7.3.5 Fault detection counter retrieval . . . . . . . . . . . . 108
7.7.3.6 Fault detection counter reporting . . . . . . . . . . . 109
7.7.4 Fault confirmation . . . . . . . . . . . . . . . . . . . . . . . . 109
7.7.4.1 Method for grouping of association of events for OBD
purpose . . . . . . . . . . . . . . . . . . . . . . . . . 111
7.7.5 Event Combination . . . . . . . . . . . . . . . . . . . . . . . 111
7.7.5.1 Combination On Storage . . . . . . . . . . . . . . . . 113
7.7.5.2 Combination On Retrieval . . . . . . . . . . . . . . . 114
7.7.6 Enable and storage conditions of diagnostic events . . . . . 114
7.7.7 Event related data . . . . . . . . . . . . . . . . . . . . . . . . 118
7.7.7.1 Storage of freeze frame data . . . . . . . . . . . . . 119
7.7.7.2 Pre-storage of freeze frame data . . . . . . . . . . . 124
7.7.7.3 Storage of extended data . . . . . . . . . . . . . . . 126
7.7.7.4 Configuration of Event related data . . . . . . . . . . 128
7.7.7.5 Notification of data changes . . . . . . . . . . . . . . 135
7.7.8 Aging of diagnostic events . . . . . . . . . . . . . . . . . . . 136
7.7.9 Healing of diagnostic events . . . . . . . . . . . . . . . . . . 140
7.7.9.1 Warning indicator handling . . . . . . . . . . . . . . 140
7.7.9.2 User controlled WarningIndicatorRequested-bit . . . 142
7.7.9.3 Handling of the warning indicator lamp (MIL) . . . . 144
7.7.9.4 Notification and Set of the warning indicator status . 144
7.8 BSW Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
7.9 OBD-specific functionality . . . . . . . . . . . . . . . . . . . . . . . . . 146
7.9.1 General overview and restrictions . . . . . . . . . . . . . . . 146

AUTOSAR CP R20-11
7.9.2 PIDs provided by Dem . . . . . . . . . . . . . . . . . . . . . . 149

7.9.2.1 Centralized PID $21 / $31 / $4D / $4E handling . . . 150
7.9.3 Readiness status . . . . . . . . . . . . . . . . . . . . . . . . 152
7.9.4 In-Use-Monitor Performance Ratio (IUMPR) Support . . . . . 153
7.9.5 OBD for light duty (OBD2) . . . . . . . . . . . . . . . . . . . 158
7.9.5.1 Service $01 Read Current Powertrain Diagnostic Data158
7.9.5.2 Service $02 Read Powertrain Freeze Frame Data . 159
7.9.5.3 Service $03 - Read Emission-Related Powertrain Di-
agnostic Trouble Codes . . . . . . . . . . . . . . . . 160
7.9.5.4 Service $04 - Clear Reset Emission-Related Diag-
nostic Information . . . . . . . . . . . . . . . . . . . . 160
7.9.5.5 Service $06 - Support of central DTR handling . . . 161
7.9.5.6 Service $07 - Read emission-related diagnostic trou-
ble codes detected during during current or last com-
pleted driving cycle . . . . . . . . . . . . . . . . . . . 165
7.9.5.7 Service $0A - Read Emission-Related Diagnostic
Trouble Codes with Permanent Status . . . . . . . . 165
7.9.5.8 MIL Handling . . . . . . . . . . . . . . . . . . . . . . 166
7.9.6 WWH-OBD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
7.9.6.1 DTC WWHOBD class . . . . . . . . . . . . . . . . . 166
7.9.6.2 Continuous-MI counter . . . . . . . . . . . . . . . . . 167
7.9.6.3 Cumulative Continuous-MI counter (Master ECU) . . 167
7.9.6.4 Class B1 counter . . . . . . . . . . . . . . . . . . . . 168
7.9.6.5 Activation Mode . . . . . . . . . . . . . . . . . . . . . 168
7.9.6.6 Freeze Frame 0x00 . . . . . . . . . . . . . . . . . . . 169
7.9.6.7 Extended Data Record 0x90 . . . . . . . . . . . . . . 170
7.9.6.8 Aging . . . . . . . . . . . . . . . . . . . . . . . . . . 170
7.9.6.9 Service $19 42 - Read WWH-OBD DTC By Mask
Record . . . . . . . . . . . . . . . . . . . . . . . . . . 170
7.9.6.10 Service $14 FFFF33 - Clear Emission Related DTCs 171
7.10 J1939 specific functionality . . . . . . . . . . . . . . . . . . . . . . . . . 171
7.10.1 Read DTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
7.10.1.1 Composite Malfunction Indicator Lamp Status . . . . 172
7.10.1.2 Composite Red Stop Lamp Status . . . . . . . . . . 173
7.10.1.3 Composite Amber Warning Lamp Status . . . . . . . 173
7.10.1.4 Composite Protect Lamp Status . . . . . . . . . . . . 174
7.10.1.5 DTC data acqusition . . . . . . . . . . . . . . . . . . 174
7.10.2 Clear DTCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
7.10.3 DM31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
7.10.3.1 Malfunction Indicator Lamp . . . . . . . . . . . . . . 176
7.10.3.2 Red Stop Lamp . . . . . . . . . . . . . . . . . . . . . 176
7.10.3.3 Amber Warning Lamp . . . . . . . . . . . . . . . . . 177
7.10.3.4 Protect Lamp . . . . . . . . . . . . . . . . . . . . . . 177
7.10.3.5 J1939 lamp status . . . . . . . . . . . . . . . . . . . 178
7.10.4 FreezeFrame . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
7.10.4.1 SPNs in ExpandedFreezeFrame . . . . . . . . . . . 179

AUTOSAR CP R20-11
7.10.5 Diagnostic Readiness . . . . . . . . . . . . . . . . . . . . . . 180

7.10.6 Monitor Performance Ratio . . . . . . . . . . . . . . . . . . . 182
7.11 Interaction with other Software Modules . . . . . . . . . . . . . . . . . 182
7.11.1 Interaction with Software Components (SW-C) . . . . . . . . 182
7.11.2 Interaction with Diagnostic Clients . . . . . . . . . . . . . . . 184
7.11.2.1 Parallel event memory access . . . . . . . . . . . . . 184
7.11.2.2 Accessing diagnostic fault memory . . . . . . . . . . 185
7.11.2.3 Access DTCs and Status Information . . . . . . . . . 187
7.11.2.4 Access event related data . . . . . . . . . . . . . . . 192
7.11.2.5 Clear diagnostic information . . . . . . . . . . . . . . 196
7.11.2.6 Control DTC setting . . . . . . . . . . . . . . . . . . 196
7.11.2.7 Asynchronous Dcm operations . . . . . . . . . . . . 197
7.11.3 Interaction with J1939 Diagnostic Manager (J1939) . . . . . 197
7.11.4 Interaction with Function Inhibition Manager (FIM) . . . . . . 197
7.11.5 Interaction with NVRAM Manager (NvM) . . . . . . . . . . . 198
7.11.6 Interaction with Default Error Tracer (Det) . . . . . . . . . . . 199
7.11.7 Required data by the Dem module . . . . . . . . . . . . . . . 199
7.11.8 Scaling information on Service Interfaces . . . . . . . . . . . 200
7.12 Version check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
7.13 Error classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
7.13.1 Development Errors . . . . . . . . . . . . . . . . . . . . . . . 203
7.13.2 Runtime Errors . . . . . . . . . . . . . . . . . . . . . . . . . . 204
7.13.3 Transient Faults . . . . . . . . . . . . . . . . . . . . . . . . . 204
7.13.4 Production Errors . . . . . . . . . . . . . . . . . . . . . . . . 204
7.13.5 Extended Production Errors . . . . . . . . . . . . . . . . . . . 205
8 API specification 206
8.1 Imported Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
8.2 Type definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
8.2.1 Dem data types . . . . . . . . . . . . . . . . . . . . . . . . . 209
8.2.1.1 Dem_ComponentIdType . . . . . . . . . . . . . . . . 209
8.2.1.2 Dem_ConfigType . . . . . . . . . . . . . . . . . . . . 209
8.2.1.3 Dem_EventIdType . . . . . . . . . . . . . . . . . . . 210
8.2.1.4 Dem_EventStatusType . . . . . . . . . . . . . . . . . 210
8.2.1.5 Dem_DebouncingStateType . . . . . . . . . . . . . . 210
8.2.1.6 Dem_DebounceResetStatusType . . . . . . . . . . . 210
8.2.1.7 Dem_UdsStatusByteType . . . . . . . . . . . . . . . 210
8.2.1.8 Dem_IndicatorStatusType . . . . . . . . . . . . . . . 210
8.2.1.9 Dem_MonitorDataType . . . . . . . . . . . . . . . . . 211
8.2.1.10 Dem_MonitorStatusType . . . . . . . . . . . . . . . . 211
8.2.1.11 Dem_DTCKindType . . . . . . . . . . . . . . . . . . 211
8.2.1.12 Dem_DTCFormatType . . . . . . . . . . . . . . . . . 211
8.2.1.13 Dem_DTCOriginType . . . . . . . . . . . . . . . . . 211
8.2.1.14 Dem_DTCRequestType . . . . . . . . . . . . . . . . 211
8.2.1.15 Dem_DTCTranslationFormatType . . . . . . . . . . . 212
8.2.1.16 Dem_DTCSeverityType . . . . . . . . . . . . . . . . 212

AUTOSAR CP R20-11
8.2.1.17 Dem_RatioIdType . . . . . . . . . . . . . . . . . . . 213

8.2.1.18 Dem_DTRControlType . . . . . . . . . . . . . . . . . 213
8.2.1.19 Dem_InitMonitorReasonType . . . . . . . . . . . . . 213
8.2.1.20 Dem_IumprDenomCondIdType . . . . . . . . . . . . 214
8.2.1.21 Dem_IumprDenomCondStatusType . . . . . . . . . 214
8.2.1.22 Dem_J1939DcmDTCStatusFilterType . . . . . . . . 214
8.2.1.23 Dem_J1939DcmSetClearFilterType . . . . . . . . . . 214
8.2.1.24 Dem_J1939DcmSetFreezeFrameFilterType . . . . . 215
8.2.1.25 Dem_J1939DcmLampStatusType . . . . . . . . . . . 215
8.2.1.26 Dem_J1939DcmDiagnosticReadiness1Type . . . . . 216
8.3 Function definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
8.3.1 Dem_GetVersionInfo . . . . . . . . . . . . . . . . . . . . . . 218
8.3.2 Interface ECU State Manager <=> Dem . . . . . . . . . . . . 219
8.3.2.1 Dem_PreInit . . . . . . . . . . . . . . . . . . . . . . . 219
8.3.2.2 Dem_Init . . . . . . . . . . . . . . . . . . . . . . . . . 219
8.3.2.3 Dem_Shutdown . . . . . . . . . . . . . . . . . . . . . 219
8.3.3 Interface BSW modules / SW-Components <=> Dem . . . . 220
8.3.3.1 Dem_ClearDTC . . . . . . . . . . . . . . . . . . . . . 220
8.3.3.2 Dem_ClearPrestoredFreezeFrame . . . . . . . . . . 221
8.3.3.3 Dem_GetComponentFailed . . . . . . . . . . . . . . 221
8.3.3.4 Dem_GetDTCSelectionResult . . . . . . . . . . . . . 222
8.3.3.5 Dem_GetDTCSelectionResultForClearDTC . . . . . 223
8.3.3.6 Dem_GetEventUdsStatus . . . . . . . . . . . . . . . 223
8.3.3.7 Dem_GetMonitorStatus . . . . . . . . . . . . . . . . 224
8.3.3.8 Dem_GetDebouncingOfEvent . . . . . . . . . . . . . 224
8.3.3.9 Dem_GetDTCOfEvent . . . . . . . . . . . . . . . . . 225
8.3.3.10 Dem_GetDTCSuppression . . . . . . . . . . . . . . 226
8.3.3.11 Dem_GetEventAvailable . . . . . . . . . . . . . . . . 226
8.3.3.12 Dem_GetFaultDetectionCounter . . . . . . . . . . . 227
8.3.3.13 Dem_GetIndicatorStatus . . . . . . . . . . . . . . . . 227
8.3.3.14 Dem_GetEventFreezeFrameDataEx . . . . . . . . . 228
8.3.3.15 Dem_GetEventExtendedDataRecordEx . . . . . . . 229
8.3.3.16 Dem_GetEventMemoryOverflow . . . . . . . . . . . 230
8.3.3.17 Dem_GetNumberOfEventMemoryEntries . . . . . . 230
8.3.3.18 Dem_ResetEventDebounceStatus . . . . . . . . . . 231
8.3.3.19 Dem_ResetEventStatus . . . . . . . . . . . . . . . . 231
8.3.3.20 Dem_RestartOperationCycle . . . . . . . . . . . . . 232
8.3.3.21 Dem_PrestoreFreezeFrame . . . . . . . . . . . . . . 233
8.3.3.22 Dem_SelectDTC . . . . . . . . . . . . . . . . . . . . 233
8.3.3.23 Dem_SetComponentAvailable . . . . . . . . . . . . . 234
8.3.3.24 Dem_SetDTCSuppression . . . . . . . . . . . . . . . 234
8.3.3.25 Dem_SetEnableCondition . . . . . . . . . . . . . . . 235
8.3.3.26 Dem_SetEventAvailable . . . . . . . . . . . . . . . . 236
8.3.3.27 Dem_SetEventConfirmationThresholdCounter . . . 236

AUTOSAR CP R20-11
8.3.3.28 Dem_SetEventStatus . . . . . . . . . . . . . . . . . 237

8.3.3.29 Dem_SetEventStatusWithMonitorData . . . . . . . . 237
8.3.3.30 Dem_SetStorageCondition . . . . . . . . . . . . . . 238
8.3.3.31 Dem_SetWIRStatus . . . . . . . . . . . . . . . . . . 239
8.3.3.32 Dem_SetEventFailedWithSyncFreezeFrame . . . . . 239
8.3.4 Interface Dcm <=> Dem . . . . . . . . . . . . . . . . . . . . . 240
8.3.4.1.1 Dem_GetTranslationType . . . . . . . . . . . . 240
8.3.4.1.2 Dem_GetDTCStatusAvailabilityMask . . . . . 241
8.3.4.1.3 Dem_GetStatusOfDTC . . . . . . . . . . . . . 241
8.3.4.1.4 Dem_GetSeverityOfDTC . . . . . . . . . . . . 242
8.3.4.1.5 Dem_GetFunctionalUnitOfDTC . . . . . . . . . 243
8.3.4.1.6 Dem_SetDTCFilter . . . . . . . . . . . . . . . 243
8.3.4.1.7 Dem_GetNumberOfFilteredDTC . . . . . . . . 244
8.3.4.1.8 Dem_GetNextFilteredDTC . . . . . . . . . . . 245
8.3.4.1.9 Dem_GetNextFilteredDTCAndFDC . . . . . . 246
8.3.4.1.10 Dem_GetNextFilteredDTCAndSeverity . . . . 247
8.3.4.1.11 Dem_SetFreezeFrameRecordFilter . . . . . . 247
8.3.4.1.12 Dem_GetNextFilteredRecord . . . . . . . . . . 248
8.3.4.1.13 Dem_GetDTCByOccurrenceTime . . . . . . . 249
8.3.4.2 Access extended data records and FreezeFrame data 249
8.3.4.2.1 Dem_DisableDTCRecordUpdate . . . . . . . . 249
8.3.4.2.2 Dem_EnableDTCRecordUpdate . . . . . . . . 250
8.3.4.2.3 Dem_GetSizeOfExtendedDataRecordSelection 251
8.3.4.2.4 Dem_GetSizeOfFreezeFrameSelection . . . . 251
8.3.4.2.5 Dem_GetNextExtendedDataRecord . . . . . . 252
8.3.4.2.6 Dem_GetNextFreezeFrameData . . . . . . . . 253
8.3.4.2.7 Dem_SelectExtendedDataRecord . . . . . . . 254
8.3.4.2.8 Dem_SelectFreezeFrameData . . . . . . . . . 254
8.3.4.2.9 Dem_GetNumberOfFreezeFrameRecords . . 255
8.3.4.3 DTC storage . . . . . . . . . . . . . . . . . . . . . . 256
8.3.4.3.1 Dem_DisableDTCSetting . . . . . . . . . . . . 256
8.3.4.3.2 Dem_EnableDTCSetting . . . . . . . . . . . . 256
8.3.5 OBD-specific Dcm <=> Dem Interfaces . . . . . . . . . . . . 257
8.3.5.1 Dem_DcmGetInfoTypeValue08 . . . . . . . . . . . . 257
8.3.5.2 Dem_DcmGetInfoTypeValue0B . . . . . . . . . . . . 257
8.3.5.3 Dem_DcmReadDataOfPID01 . . . . . . . . . . . . . 258
8.3.5.4 Dem_DcmReadDataOfPID1C . . . . . . . . . . . . . 258
8.3.5.9 Dem_DcmReadDataOfPID4D . . . . . . . . . . . . . 261
8.3.5.10 Dem_DcmReadDataOfPID4E . . . . . . . . . . . . . 262
8.3.5.12 Dem_DcmReadDataOfOBDFreezeFrame . . . . . . 263

AUTOSAR CP R20-11
8.3.5.13 Dem_DcmGetDTCOfOBDFreezeFrame . . . . . . . 264

8.3.5.14 Dem_DcmGetAvailableOBDMIDs . . . . . . . . . . . 265
8.3.5.15 Dem_DcmGetNumTIDsOfOBDMID . . . . . . . . . . 265
8.3.5.16 Dem_DcmGetDTRData . . . . . . . . . . . . . . . . 266
8.3.6 Interface J1939Dcm <=> Dem . . . . . . . . . . . . . . . . . 267
8.3.6.1.1 Dem_J1939DcmSetDTCFilter . . . . . . . . . 267
8.3.6.1.2 Dem_J1939DcmGetNumberOfFilteredDTC . . 267
8.3.6.1.3 Dem_J1939DcmGetNextFilteredDTC . . . . . 268
8.3.6.1.4 Dem_J1939DcmFirstDTCwithLampStatus . . 269
8.3.6.1.5 Dem_J1939DcmGetNextDTCwithLampStatus 269
8.3.6.2 DTC storage . . . . . . . . . . . . . . . . . . . . . . 270
8.3.6.2.1 Dem_J1939DcmClearDTC . . . . . . . . . . . 270
8.3.6.2.2 Dem_J1939DcmSetFreezeFrameFilter . . . . 271
8.3.6.2.3 Dem_J1939DcmGetNextFreezeFrame . . . . 271
8.3.6.2.4 Dem_J1939DcmGetNextSPNInFreezeFrame . 272
8.3.6.3 Reporting . . . . . . . . . . . . . . . . . . . . . . . . 273
8.3.6.3.1 Dem_J1939DcmSetRatioFilter . . . . . . . . . 273
8.3.6.3.2 Dem_J1939DcmGetNextFilteredRatio . . . . . 273
8.3.6.3.3 Dem_J1939DcmReadDiagnosticReadiness1 . 274
8.3.7 OBD-specific Interfaces . . . . . . . . . . . . . . . . . . . . . 276
8.3.7.1 Dem_SetEventDisabled . . . . . . . . . . . . . . . . 276
8.3.7.2 Dem_RepIUMPRFaultDetect . . . . . . . . . . . . . 276
8.3.7.3 Dem_SetIUMPRDenCondition . . . . . . . . . . . . 277
8.3.7.4 Dem_GetIUMPRDenCondition . . . . . . . . . . . . 278
8.3.7.5 Dem_RepIUMPRDenRelease . . . . . . . . . . . . . 278
8.3.7.6 Dem_SetPtoStatus . . . . . . . . . . . . . . . . . . . 279
8.3.7.7 Dem_ReadDataOfPID01 . . . . . . . . . . . . . . . . 279
8.3.7.8 Dem_GetDataOfPID21 . . . . . . . . . . . . . . . . . 280
8.3.7.9 Dem_SetDataOfPID21 . . . . . . . . . . . . . . . . . 280
8.3.7.10 Dem_SetDataOfPID31 . . . . . . . . . . . . . . . . . 281
8.3.7.11 Dem_SetDataOfPID4D . . . . . . . . . . . . . . . . 282
8.3.7.12 Dem_SetDataOfPID4E . . . . . . . . . . . . . . . . . 282
8.3.7.13 Dem_GetCycleQualified . . . . . . . . . . . . . . . . 283
8.3.7.14 Dem_SetCycleQualified . . . . . . . . . . . . . . . . 283
8.3.7.15 Dem_GetDTCSeverityAvailabilityMask . . . . . . . . 284
8.3.7.16 Dem_GetB1Counter . . . . . . . . . . . . . . . . . . 284
8.3.7.17 Dem_SetDTR . . . . . . . . . . . . . . . . . . . . . . 285
8.4 Expected Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
8.4.1 Mandatory Interfaces . . . . . . . . . . . . . . . . . . . . . . 286
8.4.2 Optional Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 286
8.4.3 Configurable interfaces . . . . . . . . . . . . . . . . . . . . . 287
8.4.3.1 Interface BSW modules / SW-Components <=> Dem 288
8.4.3.1.1 InitMonitorForEvent . . . . . . . . . . . . . . . 288

AUTOSAR CP R20-11
8.4.3.1.2 DemTriggerOnComponentStatus . . . . . . . . 289

8.4.3.2 ClearDtcNotification . . . . . . . . . . . . . . . . . . 289
8.4.3.3 DemGeneralTriggerOnMonitorStatus . . . . . . . . . 290
8.4.3.4 DemGeneralTriggerOnEventUdsStatus . . . . . . . . 290
8.4.3.5 DemTriggerOnEventUdsStatus . . . . . . . . . . . . 291
8.4.3.6 DemTriggerOnDTCStatus . . . . . . . . . . . . . . . 292
8.4.3.7 DemTriggerOnMonitorStatus . . . . . . . . . . . . . 292
8.4.3.8 EventDataChanged . . . . . . . . . . . . . . . . . . . 293
8.4.3.9 ClearEventAllowed . . . . . . . . . . . . . . . . . . . 293
8.4.3.10 ReadDataElement . . . . . . . . . . . . . . . . . . . 293
8.4.3.11 GetFaultDetectionCounter . . . . . . . . . . . . . . . 294
8.4.3.12 Dem_CallbackEventSyncStorageProcessed . . . . . 295
8.5 Scheduled functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
8.5.1 Dem_MainFunction . . . . . . . . . . . . . . . . . . . . . . . 295
8.5.2 Runnable Entity MainFunction . . . . . . . . . . . . . . . . . 296
8.6 Service Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
8.6.1 Implementation Data Types . . . . . . . . . . . . . . . . . . . 296
8.6.1.1 Dem_DataType . . . . . . . . . . . . . . . . . . . . . 296
8.6.1.2 Dem_DataPrimitiveType . . . . . . . . . . . . . . . . 297
8.6.1.3 Dem_DataArrayType . . . . . . . . . . . . . . . . . . 298
8.6.1.4 Dem_DTCOriginType . . . . . . . . . . . . . . . . . 298
8.6.1.5 Dem_DebouncingStateType . . . . . . . . . . . . . . 299
8.6.1.6 Dem_DebounceResetStatusType . . . . . . . . . . . 300
8.6.1.7 Dem_DTRControlType . . . . . . . . . . . . . . . . . 300
8.6.1.8 Dem_EventIdType . . . . . . . . . . . . . . . . . . . 301
8.6.1.9 Dem_EventStatusType . . . . . . . . . . . . . . . . . 301
8.6.1.10 Dem_DTCFormatType . . . . . . . . . . . . . . . . . 302
8.6.1.11 Dem_InitMonitorReasonType . . . . . . . . . . . . . 302
8.6.1.12 Dem_IumprDenomCondIdType . . . . . . . . . . . . 303
8.6.1.13 Dem_IumprDenomCondStatusType . . . . . . . . . 303
8.6.1.14 Dem_MaxDataValueType . . . . . . . . . . . . . . . 304
8.6.1.15 Dem_MonitorDataType . . . . . . . . . . . . . . . . . 304
8.6.1.16 Dem_MonitorStatusType . . . . . . . . . . . . . . . . 305
8.6.1.17 Dem_IndicatorStatusType . . . . . . . . . . . . . . . 305
8.6.1.18 Dem_PID21valueType . . . . . . . . . . . . . . . . . 305
8.6.1.19 Dem_PID31valueType . . . . . . . . . . . . . . . . . 306
8.6.1.20 Dem_RatioIdType . . . . . . . . . . . . . . . . . . . 306
8.6.1.21 Dem_UdsStatusByteType . . . . . . . . . . . . . . . 307
8.6.1.22 Dem_PID4DvalueType . . . . . . . . . . . . . . . . . 307
8.6.1.23 Dem_PID4EvalueType . . . . . . . . . . . . . . . . . 307
8.6.2 Sender-Receiver-Interfaces . . . . . . . . . . . . . . . . . . . 308
8.6.2.1 DataServices_{Data} . . . . . . . . . . . . . . . . . . 308
8.6.3 Client-Server-Interfaces . . . . . . . . . . . . . . . . . . . . . 308
8.6.3.1 CallbackClearEventAllowed . . . . . . . . . . . . . . 308
8.6.3.2 CallbackComponentStatusChanged . . . . . . . . . 309
8.6.3.3 CallbackDTCStatusChange . . . . . . . . . . . . . . 309

AUTOSAR CP R20-11
8.6.3.4 CallbackEventDataChanged . . . . . . . . . . . . . . 310

8.6.3.5 CallbackEventUdsStatusChanged . . . . . . . . . . 311
8.6.3.6 CallbackGetFaultDetectCounter . . . . . . . . . . . . 311
8.6.3.7 CallbackInitMonitorForEvent . . . . . . . . . . . . . . 312
8.6.3.8 CallbackMonitorStatusChange . . . . . . . . . . . . 313
8.6.3.10 ClearDTC . . . . . . . . . . . . . . . . . . . . . . . . 314
8.6.3.11 DTCSuppression . . . . . . . . . . . . . . . . . . . . 315
8.6.3.13 DTRCentralReport . . . . . . . . . . . . . . . . . . . 317
8.6.3.14 DiagnosticInfo . . . . . . . . . . . . . . . . . . . . . . 319
8.6.3.15 DiagnosticMonitor . . . . . . . . . . . . . . . . . . . 322
8.6.3.16 DiagnosticMonitor_MonitorData . . . . . . . . . . . . 324
8.6.3.17 EnableCondition . . . . . . . . . . . . . . . . . . . . 324
8.6.3.18 EventAvailable . . . . . . . . . . . . . . . . . . . . . 325
8.6.3.19 EventFailureCycleCounterThreshold . . . . . . . . . 326
8.6.3.20 EvMemOverflowIndication . . . . . . . . . . . . . . . 326
8.6.3.21 EventStatus . . . . . . . . . . . . . . . . . . . . . . . 327
8.6.3.22 GeneralCallbackEventDataChanged . . . . . . . . . 328
8.6.3.23 GeneralCallbackEventUdsStatusChanged . . . . . . 328
8.6.3.24 GeneralCallbackMonitorStatusChanged . . . . . . . 329
8.6.3.25 GeneralDiagnosticInfo . . . . . . . . . . . . . . . . . 329
8.6.3.26 GetDataOfPID21 . . . . . . . . . . . . . . . . . . . . 333
8.6.3.27 IndicatorStatus . . . . . . . . . . . . . . . . . . . . . 334
8.6.3.28 IUMPRDenominator . . . . . . . . . . . . . . . . . . 335
8.6.3.29 IUMPRDenominatorCondition . . . . . . . . . . . . . 335
8.6.3.30 IUMPRNumerator . . . . . . . . . . . . . . . . . . . 336
8.6.3.31 OperationCycle . . . . . . . . . . . . . . . . . . . . . 336
8.6.3.32 PowerTakeOff . . . . . . . . . . . . . . . . . . . . . . 337
8.6.3.33 SetDataOfPID21 . . . . . . . . . . . . . . . . . . . . 338
8.6.3.34 SetDataOfPID31 . . . . . . . . . . . . . . . . . . . . 338
8.6.3.35 SetDataOfPID4D . . . . . . . . . . . . . . . . . . . . 339
8.6.3.36 SetDataOfPID4E . . . . . . . . . . . . . . . . . . . . 340
8.6.3.37 StorageCondition . . . . . . . . . . . . . . . . . . . . 340
8.6.4 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
8.6.4.1 CBClrEvt . . . . . . . . . . . . . . . . . . . . . . . . 341
8.6.4.2 CBDataEvt . . . . . . . . . . . . . . . . . . . . . . . 341
8.6.4.3 CBFaultDetectCtr . . . . . . . . . . . . . . . . . . . . 341
8.6.4.4 CBInitEvt . . . . . . . . . . . . . . . . . . . . . . . . 342
8.6.4.5 CBStatusDTC . . . . . . . . . . . . . . . . . . . . . . 342
8.6.4.6 CBEventUdsStatusChanged . . . . . . . . . . . . . . 342
8.6.4.7 CBMonitorStatusChanged . . . . . . . . . . . . . . . 343
8.6.4.8 CBStatusComp . . . . . . . . . . . . . . . . . . . . . 343
8.6.4.9 ClearDTC . . . . . . . . . . . . . . . . . . . . . . . . 343
8.6.4.11 ControlDTCSuppression . . . . . . . . . . . . . . . . 344

AUTOSAR CP R20-11
8.6.4.12 ControlEventAvailable . . . . . . . . . . . . . . . . . 344

8.6.4.13 ControlEventFailureCycleCounterThreshold . . . . . 345
8.6.4.15 DTR . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
8.6.4.16 EnableCond . . . . . . . . . . . . . . . . . . . . . . . 346
8.6.4.17 Event . . . . . . . . . . . . . . . . . . . . . . . . . . 346
8.6.4.18 DiagnosticMonitor_MonitorData . . . . . . . . . . . . 346
8.6.4.19 EventStatus . . . . . . . . . . . . . . . . . . . . . . . 347
8.6.4.20 EventInfo . . . . . . . . . . . . . . . . . . . . . . . . 347
8.6.4.21 GeneralCBDataEvt . . . . . . . . . . . . . . . . . . . 347
8.6.4.22 GeneralCBMonitorStatusChanged . . . . . . . . . . 348
8.6.4.23 GeneralCBStatusEvt . . . . . . . . . . . . . . . . . . 348
8.6.4.24 GeneralEvtInfo . . . . . . . . . . . . . . . . . . . . . 348
8.6.4.25 IndStatus . . . . . . . . . . . . . . . . . . . . . . . . 349
8.6.4.26 IUMPRDenominator . . . . . . . . . . . . . . . . . . 349
8.6.4.27 IUMPRDenominatorCondition . . . . . . . . . . . . . 349
8.6.4.28 IUMPRNumerator . . . . . . . . . . . . . . . . . . . 350
8.6.4.29 OpCycle . . . . . . . . . . . . . . . . . . . . . . . . . 350
8.6.4.30 OverflowIndMirrorMemory . . . . . . . . . . . . . . . 350
8.6.4.31 OverflowIndPermanentMemory . . . . . . . . . . . . 351
8.6.4.32 OverflowIndPrimaryMemory . . . . . . . . . . . . . . 351
8.6.4.33 OverflowIndUserDefinedMemory . . . . . . . . . . . 351
8.6.4.34 PowerTakeOffStatus . . . . . . . . . . . . . . . . . . 352
8.6.4.35 GetDataOfPID21 . . . . . . . . . . . . . . . . . . . . 352
8.6.4.36 SetDataOfPID21 . . . . . . . . . . . . . . . . . . . . 352
8.6.4.37 SetDataOfPID31 . . . . . . . . . . . . . . . . . . . . 353
8.6.4.38 SetDataOfPID4D . . . . . . . . . . . . . . . . . . . . 353
8.6.4.39 SetDataOfPID4E . . . . . . . . . . . . . . . . . . . . 353
8.6.4.40 StorageCond . . . . . . . . . . . . . . . . . . . . . . 353
9 Sequence Diagrams 355
9.1 ControlDTCSetting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
9.2 Dem_ClearDTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
9.3 Dem_GetDTCByOccurrenceTime . . . . . . . . . . . . . . . . . . . . . 357
9.4 Dem_GetNextExtendedDataRecord . . . . . . . . . . . . . . . . . . . 357
9.5 Dem_DcmGetStatusOfDTC . . . . . . . . . . . . . . . . . . . . . . . . 358
9.6 Retrieving freeze frames . . . . . . . . . . . . . . . . . . . . . . . . . . 358
9.7 GetOBDFaultInformation . . . . . . . . . . . . . . . . . . . . . . . . . . 359
9.8 ReportDTCByStatusMask . . . . . . . . . . . . . . . . . . . . . . . . . 360
9.9 FiM_DemTriggerOnEventStatus . . . . . . . . . . . . . . . . . . . . . . 360
9.10 ProcessEvent (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . 361
10 Configuration specification 362
10.1 How to read this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . 362
10.2 Containers and configuration parameters . . . . . . . . . . . . . . . . . 362
10.2.1 Dem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
10.2.2 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

AUTOSAR CP R20-11
10.2.2.1 DemGeneral . . . . . . . . . . . . . . . . . . . . . . 362

10.2.2.2 DemConfigSet . . . . . . . . . . . . . . . . . . . . . 377
10.2.2.3 DemClient . . . . . . . . . . . . . . . . . . . . . . . . 379
10.2.2.4 DemDTCAttributes . . . . . . . . . . . . . . . . . . . 383
10.2.2.5 DemEventParameter . . . . . . . . . . . . . . . . . . 391
10.2.2.6 DemMultiEventTriggering . . . . . . . . . . . . . . . 403
10.2.2.7 DemComponent . . . . . . . . . . . . . . . . . . . . 405
10.2.2.8 DemDTC . . . . . . . . . . . . . . . . . . . . . . . . 407
10.2.2.9 DemGroupOfDTC . . . . . . . . . . . . . . . . . . . 413
10.2.2.10 DemOperationCycle . . . . . . . . . . . . . . . . . . 413
10.2.2.11 DemIndicator . . . . . . . . . . . . . . . . . . . . . . 415
10.2.2.12 DemIndicatorAttribute . . . . . . . . . . . . . . . . . 416
10.2.2.13 DemNvRamBlockId . . . . . . . . . . . . . . . . . . . 419
10.2.3 OBD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
10.2.3.1 DemGeneralOBD . . . . . . . . . . . . . . . . . . . . 420
10.2.3.2 DemObdDTC . . . . . . . . . . . . . . . . . . . . . . 430
10.2.3.3 DemRatio . . . . . . . . . . . . . . . . . . . . . . . . 433
10.2.3.4 DemDtrs . . . . . . . . . . . . . . . . . . . . . . . . . 439
10.2.3.5 DemDtr . . . . . . . . . . . . . . . . . . . . . . . . . 439
10.2.3.6 DemPidClass . . . . . . . . . . . . . . . . . . . . . . 445
10.2.3.7 DemPidDataElement . . . . . . . . . . . . . . . . . . 446
10.2.4 J1939 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
10.2.4.1 DemGeneralJ19139 . . . . . . . . . . . . . . . . . . 447
10.2.4.2 DemJ1939FreezeFrameClass . . . . . . . . . . . . . 453
10.2.4.3 DemSPNClass . . . . . . . . . . . . . . . . . . . . . 454
10.2.5 Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
10.2.5.1 DemEnableCondition . . . . . . . . . . . . . . . . . . 456
10.2.5.2 DemEnableConditionGroup . . . . . . . . . . . . . . 457
10.2.5.3 DemStorageCondition . . . . . . . . . . . . . . . . . 458
10.2.5.4 DemStorageConditionGroup . . . . . . . . . . . . . 460
10.2.6 Event Memory . . . . . . . . . . . . . . . . . . . . . . . . . . 461
10.2.6.1 DemEventMemorySet . . . . . . . . . . . . . . . . . 461
10.2.6.2 DemPrimaryMemory . . . . . . . . . . . . . . . . . . 466
10.2.6.3 DemMirrorMemory . . . . . . . . . . . . . . . . . . . 471
10.2.6.4 DemUserDefinedMemory . . . . . . . . . . . . . . . 472
10.2.7 Debouncing . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
10.2.7.1 DemDebounceAlgorithmClass . . . . . . . . . . . . 477
10.2.7.2 DemDebounceCounterBased . . . . . . . . . . . . . 478
10.2.7.3 DemDebounceCounterBasedClass . . . . . . . . . . 479
10.2.7.4 DemDebounceTimeBase . . . . . . . . . . . . . . . 486
10.2.7.5 DemDebounceTimeBaseClass . . . . . . . . . . . . 486
10.2.7.6 DemDebounceMonitorInternal . . . . . . . . . . . . . 489
10.2.8 Callbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
10.2.8.1 DemCallbackClearEventAllowed . . . . . . . . . . . 490
10.2.8.2 DemCallbackDTCStatusChanged . . . . . . . . . . . 491
10.2.8.3 DemCallbackJ1939DTCStatusChanged . . . . . . . 492

AUTOSAR CP R20-11
10.2.8.4 DemCallbackOBDDTCStatusChanged . . . . . . . . 493

10.2.8.5 DemCallbackGetFDC . . . . . . . . . . . . . . . . . 494
10.2.8.6 DemCallbackEventDataChanged . . . . . . . . . . . 495
10.2.8.7 DemCallbackEventUdsStatusChanged . . . . . . . . 496
10.2.8.8 DemCallbackMonitorStatusChanged . . . . . . . . . 497
10.2.8.9 DemCallbackInitMForE . . . . . . . . . . . . . . . . . 498
10.2.8.10 DemClearDTCNotification . . . . . . . . . . . . . . . 499
10.2.8.11 DemCallbackEventSyncStorageProcessed . . . . . 500
10.2.9 Event related data . . . . . . . . . . . . . . . . . . . . . . . . 502
10.2.9.1 DemFreezeFrameClass . . . . . . . . . . . . . . . . 502
10.2.9.2 DemFreezeFrameRecordClass . . . . . . . . . . . . 505
10.2.9.3 DemFreezeFrameRecNumClass . . . . . . . . . . . 507
10.2.9.4 DemExtendedDataClass . . . . . . . . . . . . . . . . 508
10.2.9.5 DemExtendedDataRecordClass . . . . . . . . . . . 510
10.2.10 Data elements . . . . . . . . . . . . . . . . . . . . . . . . . . 512
10.2.10.1 DemDataElementClass . . . . . . . . . . . . . . . . 512
10.2.10.2 DemDataElementInstance . . . . . . . . . . . . . . . 514
10.2.10.3 DemDidClass . . . . . . . . . . . . . . . . . . . . . . 515
10.2.10.4 DemInternalDataElementClass . . . . . . . . . . . . 516
10.2.10.5 DemExternalCSDataElementClass . . . . . . . . . . 519
10.2.10.6 DemExternalSRDataElementClass . . . . . . . . . . 522
10.2.10.7 DemSRDataElementClass . . . . . . . . . . . . . . . 525
10.2.10.8 DemSubElementInDataElementInstance . . . . . . . 526
10.2.10.9 DemSubElementInImplDataElementInstance . . . . 527
10.2.10.10 DemDiagnosisScaling . . . . . . . . . . . . . . . . . 528
10.2.10.11 DemAlternativeDataInterface . . . . . . . . . . . . . 529
10.2.10.12 DemAlternativeDiagnosticDataElement . . . . . . . 530
10.2.10.13 DemAlternativeDataType . . . . . . . . . . . . . . . 531
10.2.10.14 DemTextTableMapping . . . . . . . . . . . . . . . . . 532
10.3 Published information . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
11 Not Applicable Requirements 535

AUTOSAR CP R20-11
1 Introduction and functional overview

The service component Diagnostic Event Manager (Dem) is responsible for processing
and storing diagnostic events (errors) and associated data. Further, the Dem provides
fault information to the Dcm (e.g. read all stored DTCs from the event memory). The
Dem offers interfaces to the application layer and to other BSW modules.
The basic target of the Dem specification document is to define the ability for a common
approach of a "diagnostic fault memory" for automotive manufacturers and component
suppliers
This specification defines the functionality, API and the configuration of the AUTOSAR
basic software module Diagnostic Event Manager (Dem). Parts of the internal behavior
are manufacturer specific and described in the Limitations chapter.

AUTOSAR CP R20-11
2 Acronyms and Abbreviations

The glossary below includes acronyms and abbreviations relevant to the Dem module
that are not included in the [4, AUTOSAR glossary].
2.1 Acronyms
Acronym Description
Activation Mode 1 Absence of malfunction - The MIL shall blink for one flash.
"on-demand-MI" - The MIL shall show blink for two flashes if the
Activation Mode 2 OBD system would command an on-demand-MI according to the
discriminatory display strategy.
"short-MI" - The MIL shall blink for three flashes if the OBD sys-
Activation Mode 3 tem would command a short-MI according to the discriminatory
display strategy.
"continuous-MI" - The MIL shall remain continuously ON
Activation Mode 4 ("continuous-MI") if the OBD system would command a
continuous-MI according to the discriminatory display strategy.
Unlearning/deleting of a no longer failed event/DTC after a de-
Aging
fined number of operation cycles from event memory.
The "Aging Counter" or "Aging Cycle Counter" or "DTC Aging
Counter" specifies the counter which is used to perform Aging.
Aging Counter
It counts the number of operation cycles until an event/DTC is
removed from event memory.
Number of engine hours during which a Class B1 malfunction has
Class B1 counter
been Confirmed and TestFailed.
Normal DTC, but referenced by multiple events reported by sev-
Combined DTC eral monitors (e.g. ECU Defect, consisting of different HW de-
fects).
Continuous-MI counter Hours run by the engine while a continuous MI is commanded.
Cumulative Continuous-MI Number of engine hours during which MI has been continuously
counter commanded to be on during its lifetime.
Debounce counter Internal counter for counter-based debouncing algorithm(s).
A monitored component is a part of the system, which is checked
DemComponent / Monitored
for proper operation by one or several monitorings. (see chapter
Component
7.5)
Some data values (e.g. the occurrence counter) are calculated
Dem-internal data value
by the Dem module itself internally.
The denominator of a specific monitor m (Denominatorm) is a
Denominator counter indicating the number of vehicle driving events, taking
into account conditions specific to that specific monitor.
Dependent / Secondary (or dep. / sec. ) ECUs are always related
Dependent / Secondary ECUs
to a Master or a Primary ECU.
Directed acyclic graph Dependency graph without circular dependencies.
Replacing the the most insignificant event memory entry by
Displacement a more significant event memory entry which needs to be
stored.

AUTOSAR CP R20-11
Acronym Description
Uniquely identifies an set of DTCs. A DTC group is mapped into
the range of valid DTCs. By providing a group of DTCs it is ex-
DTC group pressed that a certain operation is requested on all DTCs of that
group. The DTC group definition is provided by ISO 14229-1[2]
and OEM/supplier specific.
DtcGroupAllDtcs Grouping of all configured DTCS (representation is 0xFFFFFF).
Event combination is a method to merge several events to one
specific combined DTC. It is used to adapt different monitor re-
Event combination
sults to one significant fault, which is clearly evaluable in a service
station.
Debouncing is a specific mechanism (e.g. counter-based) to
evaluate, if the diagnostic event gets qualified. This works on
Event debouncing
top of potential signal debouncing and can be done within the
SW-C or inside the Dem.
A diagnostic event is confirmed in case of repeated detection of
qualified events over cycles or time evaluated by means of fault
Event confirmation
confirmation counters. Therefore, also the UDS status bit 3 (Con-
firmedDTC) is set.
An event memory (e.g. Primary memory) consists of several
Event memory
event memory entries.
The event memory entry is a single storage container for an event
Event memory entry and its event related data. The event memory entry is dynami-
cally assigned to specific events.
The event memory overflow indication indicates, if this specific
Event memory overflow indica-
event memory is full and the next event occurs to be stored in
tion
this event memory.
A diagnostic event is qualified in case of a passed or a failed
Event qualification result is set (Dem-internal or reported from another BSW module
or SW-C).
Event related data is additional data, e.g. sensor values or time
stamp/mileage, which is stored with an event in an event mem-
Event related data
ory. ISO defines two types of event related data: freeze frames
(snapshot records) and extended data.
Event status byte Status byte as defined in ISO 14229-1 [1], based on event level.
An extended data record is a record to store specific information
Extended data record
assigned to a fault.
The Failure counter represents the Trip Counter according to
ISO14229-1 [2]. The Trip Counter counts the number of oper-
Failure counter ation cycles (driving cycles) where a malfunction occurred. If the
counter reaches the threshold (e.g., 2 driving cycles) the con-
firmed bit changes from 0 to 1.
Fault Detection Counter sint8 value as used in ISO and FDC-APIs.
Freeze frame is defined as a record of data (DIDs/PIDs). Freeze
Freeze frame
frames are the same as SnapShotRecords in ISO-14229-1[2].
The general denominator is a counter indicating the number of
General Denominator times a vehicle has been operated, taking into account general
conditions.
Switching off the warning indicator including the handling of re-
Healing ported passed results over a period of time / several operation
cycles
The in-use performance ratio (IUPR) of a specific monitor m of
In-Use performance ratio
the OBD system is: IUPRm = Numeratorm / Denominatorm

AUTOSAR CP R20-11
Acronym Description
As a primary ECU a Master ECU stores “it’s own” and “reported
errors” of related dep. / sec ECUs in it’s event memory. Beside
Master ECU
this a Master has to fulfill special Master tasks as MIL Master or
provision of “general nominator” information.
A diagnostic monitor is a routine entity determining the proper
Monitor functionality of a component. Alternatively the term “diagnostic
function” can be used.
The numerator of a specific monitor m (Numeratorm) is a counter
indicating the number of times a vehicle has been operated such
Numerator
that all monitoring conditions necessary for that specific monitor
to detect a malfunction have been encountered.
The Dem has called NvM_SetRamBlockStatus() to set the ac-
NvM is marked for NvM_WriteAll
cording NvM Block to be written by NvM_WriteAll()
An ‘operation cycle’ is the base of the event qualifying and also
Operating cycle Dem scheduling (e.g. ignition key off-on cycles, driving cycles,
etc.)
On-Board Diagnostics, or OBD is a generic term referring to a
vehicle’s self-diagnostic and reporting capability. OBD systems
OBD
give the vehicle owner or a repair technician access to state of
health information for various vehicle sub-systems.
"In a vehicle there can be 3 different types of OBD ECUs:
• Master ECU (one per vehicle)
OBD ECUs • Primary ECUprimary ECUs (several per vehicle)
• Dependent / Secondary ECUs (several per vehicle)
P-Code Power train code

PFC cycle Permanent fault code - driving cycle (OBD Term)
The Dem module shall use the APIs NvM_WriteBlock and
NvM_GetErrorStatus of the NVRAMManager [5], if there is the
Positive Callback from NvM necessity to store data between Dem_Init and Dem_Shutdown.
Furthermore the API NvM_GetErrorStatus shall wait for positive
response if writing of block completed successfully.
PossibleErrors means the ApplicationErrors as defined in meta
PossibleErrors
model
A primary ECU stores “it’s own” and "reported errors" of related
Primary ECU
dep. / sec ECUs in it’s event memory
OBD Term: General Nominator / Rate-based monitoring - driving
RBM cycle
cycle (OBD Term)
The readiness refers to the tested bits TestNotCompletedSince-
Readiness LastClear (bit 4) and TestNotCompleteThisOperationCycle (bit 6)
of the UDS status byte.
The Dem module shall use the API NvM_WriteBlock of the
NVRAMManager [5], if there is the necessity to trigger the stor-
Triggered to NvM age of data between Dem_Init and Dem_Shutdown. Fur-
thermore the Dem module shall wait for positive response of
NvM_WriteBlock if request has been accepted.
testFailed bit of the UDS status byte. Indicates the result of the
UDS status bit 0
most recently performed test.
testFailedThisOperationCycle bit of the UDS status byte. Indi-
UDS status bit 1 cates whether or not a diagnostic test has reported a testFailed
result at any time during the current operation cycle.

AUTOSAR CP R20-11
Acronym Description
pendingDTC bit of the UDS status byte. Indicates whether or
UDS status bit 2 not a diagnostic test has reported a testFailed result at any time
during the current or last completed operation cycle.
confirmedDTC bit of the UDS status byte. Indicates whether a
UDS status bit 3 malfunction was detected enough times to warrant that the DTC
is desired to be stored in long-term memory.
testNotCompletedSinceLastClear bit of the UDS status byte. In-
UDS status bit 4 dicates whether a DTC test has ever run and completed since
the last time a call was made to ClearDiagnosticInformation.
testFailedSinceLastClear bit of the UDS status byte. Indicates
UDS status bit 5 whether a DTC test has completed with a failed result since the
last time a call was made to ClearDiagnosticInformation.
testNotCompletedThisOperationCycle bit of the UDS status byte.
UDS status bit 6 Indicates whether a DTC test has ever run and completed during
the current operation cycle.
warningIndicatorRequested bit of the UDS status byte. Report
UDS status bit 7 the status of any warning indicators associated with a particular
DTC.
UDS status byte Status byte as defined in ISO 14229-1 [1], based on DTC level.
2.2 Abbreviations
Abbreviation Description
API Application Programming Interface
BSW Basic Software
CDD Complex Device Driver
CRC Cyclic Redundancy Check
Dcm Diagnostic Communication Manager
Dem Diagnostic Event Manager
Det Default Error Tracer
DID Data Identifier
DTC Diagnostic Trouble Code
DTR Diagnostic Test Result
DYC OBD Term: Driving Cycle (OBD Term)
ECU Electronic Control Unit
EcuM Electronic Control Unit Manager
FDC Fault Detection Counter
Fim Function Inhibition Manager
FMI Failure Mode Indicator (SAE J1939)
FTB Failure Type Byte
HW Hardware
ID Identification/Identifier
ISO International Standardization Organization
IUMPR In Use Monitoring Performance Ratio (OBD Term)
J1939Dcm SAEJ1939 Diagnostic Communication Manager
MIL Malfunction Indicator Light (SAE J1979) or Lamp (SAE J1939)
NVRAM Non volatile RAM
OBD On-Board-Diagnostics

AUTOSAR CP R20-11
Abbreviation Description
OC Occurrence Count (SAE J1939)
OEM Original Equipment Manufacturer (Automotive Manufacturer)
OS Operating System
PID Parameter Identification (SAE J1587 or SAE J1979)
PTO Power Take Off
RAM Random Access Memory
ROM Read-only Memory
RTE Runtime Environment
SPN Suspect Parameter Number (SAE J1939)
SSCP synchronous server call point
SW Software
SW-C Software Component
UDS Unified Diagnostic Services
VOBD Vehicle On-Board-Diagnostic
WUC OBD Term: Warm up cycle (OBD Term)
WIR Warning Indicator Request
WWH-OBD World Wide Harmonized On-Board-Diagnostic

AUTOSAR CP R20-11
3 Related documentation
3.1 Input documents & related standards and norms
References
[1] Unified diagnostic services (UDS) – Part 1: Specification and requirements (Re-
lease 2006-12)
http://www.iso.org
[2] Unified diagnostic services (UDS) – Part 1: Specification and requirements (Re-
lease 2013-03)
http://www.iso.org
[3] Road vehicles – Implementation of World-Wide Harmonized On-Board Diagnos-
tics (WWH-OBD) communication requirements – Part 1: General information and
use case definition
http://www.iso.org
[4] Glossary
AUTOSAR_TR_Glossary
[5] Specification of NVRAM Manager
AUTOSAR_SWS_NVRAMManager
[6] General Specification of Basic Software Modules
AUTOSAR_SWS_BSWGeneral
[7] Specification of a Diagnostic Communication Manager for SAE J1939
AUTOSAR_SWS_SAEJ1939DiagnosticCommunicationManager
[8] Requirements on Function Inhibition Manager
AUTOSAR_SRS_FunctionInhibitionManager
[9] Specification of Diagnostic Communication Manager
AUTOSAR_SWS_DiagnosticCommunicationManager
[10] Requirements on Diagnostics
AUTOSAR_RS_Diagnostics
[11] General Requirements on Basic Software Modules
AUTOSAR_SRS_BSWGeneral
[12] Road vehicles – Communication between vehicle and external equipment for
emission-related diagnostic – Part 5: Emission-related diagnostic services.
http://www.iso.org
[13] SAE J2012-DA Digital
[14] SAE J1939-73 Application Layer – Diagnostics

AUTOSAR CP R20-11
[15] Road vehicles – Interchange of digital information on electrical connections be-

tween towing and towed vehicles – Part 4: Diagnostic communication
http://www.iso.org
[16] ISO 17356-3: Road vehicles – Open interface for embedded automotive applica-
tions – Part 3: OSEK/VDX Operating System (OS)
[17] SAE J1979
[18] SAE J1979-DA Digital Annex of E/E Diagnostic Test Modes
[19] Title 13, California Code Regulations, Section 1971.1, On-Board Diagnostic Sys-
tem Requirements for 2013 and Subsequent Model-Year Heavy-Duty Engines
(HD OBD)
[20] Title 13, California Code Regulations, Section 1968.2, Malfunction and Diagnos-
tic System Requirements for 2004 and Subsequent Model-Year Passenger Cars,
Light-Duty Trucks, and Medium-Duty Vehicles and Engines (OBD II) (Biennial Re-
view MY08-11)
http://www.arb.ca.gov/regact/obdii06/19682clean.pdf
[21] Road vehicles – Implementation of World-Wide Harmonized On-Board Diagnos-
tics (WWH-OBD) communication requirements – Part 3: Common message dic-
tionary
http://www.iso.org
[22] Software Component Template
AUTOSAR_TPS_SoftwareComponentTemplate
[23] Diagnostic Extract Template
AUTOSAR_TPS_DiagnosticExtractTemplate
3.2 Related specification

AUTOSAR provides a General Specification on Basic Software modules [6, SWS BSW
General], which is also valid for Diagnostic Event Manager.
Thus, the specification SWS BSW General shall be considered as additional and re-
quired specification for Diagnostic Event Manager.

AUTOSAR CP R20-11
4 Constraints and assumptions

Some of the synchronous API calls defined within the Dem might take variable time to
complete. Thus, this variable time must be considered in the system configuration.
[SWS_Dem_00126] dThere shall only be one Dem module available per ECU.c(RS_-
Diag_04002)
The Dem can have multiple different sections of event memory. The mapping of a
DTC to the respective section is done with the parameter DTC Origin. A specific ECU’s
Dem is only accessible by software components located inside the same ECU.
4.1 Limitations
Timing constrains have to be considered for the whole ECU. If there are explicit needs
for faster responses from the Dem than the Dem basic cycle time, special measures
have to be implemented, that are not specified in this AUTOSAR document. This is
especially the case in ECUs with many events.
Callbacks for Event and DTCStatusChange are not deterministic in rare cases, where-
fore it shall not be used for safety-relevant use-cases. Consider the general statement
in ISO-14229-1[2] that it is not recommended to link the DTC status with failsafe strate-
gies.
The handling of infrastructure errors reported by the RTE during Dem <=> SW-C in-
teractions is missing from the SWS and might have to be taken into account by imple-
menters if they need it.
The Dem is able to support additional event memories (permanent memory, mirror
memory and used defined memory), but the specific event memory processing is
not defined in detail.
Some details on the interaction between Dem and specific emission-related SW-C are
not specified in this specification, since they are dependent on the SW-C implementa-
tion. The following functionality is not defined:
• Malfunction Indicator Lamp (MIL)-activation (MIL handler interaction to Dem, MIL-
bulb check, readiness blinking, blinking in case of catalyst damaging misfire, etc.)
• misfire fault handling (debouncing over all cylinders, filtering single / multiple mis-
fire faults)
• support of similar conditions for the specific healing of misfire and fuel system
faults
Note: For OBD2, it is required that misfire and fuel system fault shall only be healed
(yielding leaving Service $07) under the similar conditions as they have been detected.
The "similarity" is derived from a "window" spanned by ranges on engine speed, engine
load and temperature conditions being present at the time of fault detection.

AUTOSAR CP R20-11
For the handling of similar conditions it is assumed that the SW-C modules of misfire
detection / fuelsystem diagnostics carry out the necessary computations themselves.
That is, it is not globally solved within the Dem.
However, based on specific interface requirements of the respective misfire detection
/ fuelsystem diagnostics this may result in an extension of the Dem. Any further im-
plementations on that need to be defined for a particular engine control unit project
depending on the diagnostics and the Dem implementation.
The DTCStoredDataRecordNumber (absolute freeze frame record addressing func-
tionality) is limited to 0x00 (OBD freeze frame, refer to subsubsection 7.11.2.4).
The structure of a specific extended data record identified by its record number is
unique per ECU.
The Dcm may lock the event memory update (refer to [SWS_Dem_00270]) while
processing the “read diagnostic data” service, due to architectural design.
This specification covers a subset of SAE J1939 related diagnostic requirements (see
Table 1: Supported DMx messages in [7, SWS J1939 Dcm]). The SPN Conversion
Method is limited to Version 4 (CM = 0).
AUTOSAR only supports user defined memories with IDs from 0x10 to 0xFF as pro-
posed to ISO 14229:1[2] by AUTOSAR.
Indicators are DemEventMemorySet local only. The Dem does not support configura-
tions where indicators are used on more than one DemEventMemorySet.
4.2 Applicability to car domains

The Dem is designed to fulfill the design demands for ECUs with OBD requirements as
well as for ECUs without OBD requirements. The immediate domains of applicability
are currently body, chassis and powertrain ECUs. However, there is no reason why the
Dem cannot be used to implement ECUs for other car domains like infotainment.

AUTOSAR CP R20-11
5 Dependencies to other modules

The AUTOSAR Diagnostic Event Manager (Dem) has interfaces and dependencies
to the following Basic software modules and Software Components:
SW-C SW-C SW-C

providing data controlling indicator
(used for event memory (e.g. lamps, text message,
Filter entries) etc.)
Services Monitor
(optional)
AUTOSAR
Software
AUTOSAR Runtime Environment (RTE)
BSW
Filter Services
Monitor
(optional)
System Services Communication Memory Services

Services
ECU State Manager
Dcm
NVRAM
FiM Dem Manager
J1939Dcm
Dlt
Basic Software
Figure 5.1: Dependencies of the Dem to other software modules
• The Function Inhibition Manager (FiM) (refer to [8, SWS FiM]) stands for the
evaluation and assignment of events to the required actions for Software Compo-
nents (e.g. inhibition of specific “Monitors”). The Dem informs and updates the
Function Inhibition Manager (FiM) upon changes of the monitor status in order to
stop or release function entities according to assigned dependencies.
• The Diagnostic Communication Manager (Dcm) (refer to [9, SWS Dcm]) is in
charge of the UDS and SAE J1979 communication path and execution of diag-
nostic service resulting in the processing of diagnostic requests from an external
tester or onboard test system. It forwards requests coming from an external di-
agnostic scan tool and is further responsible for assembly of response messages
(DTC, status information, etc.) which will be transferred to the external diagnostic
scan tool afterwards.

AUTOSAR CP R20-11
• The Diagnostic Communication Manager for J1939 (J1939Dcm) (refer to [7,

SWS J1939 Dcm]) is in charge of the SAE J1939-73 diagnostics communication
protocol.
• Software-Components (SW-C) and Basic Software (BSW) modules can ac-
cess the Dem to update and/or retrieve current monitor status and UDS status
information. SW-Cs and BSW modules can retrieve data from the Dem e.g. to
turn the indicator lamps on or off. The monitor is a sub-component of a SW-C /
BSW module.
• Data Provider SW-Cs and/or BSW modules will provide data (i.e. event related
data) required by the Dem, for example, to be able to create event memory
entries.
• The NVRAM Manager (NvM) (refer to [5]) provides mechanisms to store data
blocks in NVRAM. NVRAM blocks (maximum size is a matter of configuration)
are assigned to the Dem and used by the Dem to achieve permanent storage of
UDS status information and associated data (e.g. over power-on reset).
• The ECU State Manager (EcuM) is responsible for the basic initialization and
de-initialization of basic software components including Dem.
• The RTE implements scheduling mechanisms for BSW, e.g. assigns priority and
memory protection to each BSW module used in an ECU.
5.1 File structure
5.1.1 Code file structure
For details refer to the chapter 5.1.6 “Code File Structure” in SWS_BSWGeneral
[6] (sub chapters “Link time configuration source” and “Post-build time configuration
source”).
5.1.2 Header file structure
The symbolic names (refer to TPS_ECUC_02108) are generated for configuration con-
tainers containing an identifier parameter, like event Id symbols, operation cycles, indi-
cators, enable/storage conditions, etc.
Note, that also SW-C event Ids are published especially for complex device drivers,
which may access on the status of specific SW-C events. SW-Cs use different ports to
distinguish between different events.

AUTOSAR CP R20-11
5.2 Integration Hints

Due to cross-module communication it is recommend to map the Dem and J1939Dcm
to the same Task to have for the RTE the correct call-context configured. There might
be other BSW vendor-specific solutions possible allowing a more flexible mapping (e.g.
by describing this cross-module communication in the BSW internal-behavior or by a
similar mechanism with the Dcm <-> Dem interaction).

AUTOSAR CP R20-11
6 Requirements traceability
The following table references the requirements specified in [10] as well as [11] and
links to the fulfillment of these.
Requirement Description Satisfied by
[Non volatile storage No description [SWS_Dem_01320]
of pre-stored data]
[RS_Diag_04002] The Diagnostic event (fault) [SWS_Dem_00126]
management shall be
established as Basic SW
Module
[RS_Diag_04005] Manage Security Access [SWS_Dem_00999]
level handling
[RS_Diag_04006] Manage session handling [SWS_Dem_00999]
[RS_Diag_04007] Provide a diagnostic [SWS_Dem_00999]
service handling for the
applications involved in
diagnostic functionality
[RS_Diag_04015] Timing handling according [SWS_Dem_00999]
to ISO14229-2
[RS_Diag_04016] Support ”Busy handling” by [SWS_Dem_00999]
sending a negative
response 0x78
[RS_Diag_04019] Provide confirmation after [SWS_Dem_00999]
transmit diagnostic
responses to the
application
[RS_Diag_04020] Suppress responses to [SWS_Dem_00999]
diagnostic tool requests
[RS_Diag_04021] Handling of different [SWS_Dem_00999]
diagnostic sessions in
parallel
[RS_Diag_04024] Access and handle specific [SWS_Dem_00479] [SWS_Dem_01194]
data elements and data
element groups if
requested by an external
scan tool
[RS_Diag_04031] Notify the Function [SWS_Dem_00029] [SWS_Dem_01189]
Inhibition Manager (FIM) [SWS_Dem_01325] [SWS_Dem_01326]
upon changes of the event
status in order to process
them according to the SW
components dependencies
[RS_Diag_04032] Different diagnostic [SWS_Dem_00999]
addresses shall be
supported by multiple
(physical) channels

AUTOSAR CP R20-11

[RS_Diag_04033] Support the upload/ [SWS_Dem_00999]
download services for
reading/writing data in an
ECU in an extended and
manufacturer specific
diagnostic session
[RS_Diag_04057] Classification of events for [SWS_Dem_00057] [SWS_Dem_00518]
series production, OBD [SWS_Dem_00649] [SWS_Dem_00906]
and expert usage [SWS_Dem_01066]
[RS_Diag_04058] Ability to access different [SWS_Dem_00171]
event memories
[RS_Diag_04059] Configuration of timing [SWS_Dem_00999]
parameters
[RS_Diag_04063] Process a dedicated event [SWS_Dem_00153] [SWS_Dem_00154]
identifier for each [SWS_Dem_00942] [SWS_Dem_01034]
monitoring path to support [SWS_Dem_01037]
an autonomous handling of
different events/faults
[RS_Diag_04064] Provide configurable buffer [SWS_Dem_00999]
sizes for storage of the
events, status information
and environmental data
[RS_Diag_04067] Provide the diagnostic [SWS_Dem_00006] [SWS_Dem_00011]
status information [SWS_Dem_00016] [SWS_Dem_00051]
according to ISO 14229-1 [SWS_Dem_00059] [SWS_Dem_00060]
[SWS_Dem_00187] [SWS_Dem_00212]
[SWS_Dem_00213] [SWS_Dem_00330]
[SWS_Dem_00385] [SWS_Dem_00386]
[SWS_Dem_00387] [SWS_Dem_00388]
[SWS_Dem_00389] [SWS_Dem_00390]
[SWS_Dem_00391] [SWS_Dem_00392]
[SWS_Dem_00393] [SWS_Dem_00394]
[SWS_Dem_00395] [SWS_Dem_00409]
[SWS_Dem_00421] [SWS_Dem_00431]
[SWS_Dem_00523] [SWS_Dem_00524]
[SWS_Dem_00525] [SWS_Dem_00529]
[SWS_Dem_00539] [SWS_Dem_00566]
[SWS_Dem_00638] [SWS_Dem_00823]
[SWS_Dem_00936] [SWS_Dem_01186]
[SWS_Dem_01276] [SWS_Dem_01277]
[SWS_Dem_01278] [SWS_Dem_01280]
[SWS_Dem_01281] [SWS_Dem_01282]
[SWS_Dem_01283] [SWS_Dem_01284]
[SWS_Dem_01285] [SWS_Dem_01286]
[SWS_Dem_01287] [SWS_Dem_01342]
[SWS_Dem_91008]

AUTOSAR CP R20-11

[RS_Diag_04068] The diagnostic in [SWS_Dem_00019] [SWS_Dem_00204]
AUTOSAR shall support [SWS_Dem_00264] [SWS_Dem_00343]
event specific debounce [SWS_Dem_00344] [SWS_Dem_00413]
counters to improve signal [SWS_Dem_00414] [SWS_Dem_00416]
quality internally (According [SWS_Dem_00417] [SWS_Dem_00418]
to ISO 14229-1 Appendix [SWS_Dem_00419] [SWS_Dem_00420]
D) [SWS_Dem_00421] [SWS_Dem_00422]
[SWS_Dem_00423] [SWS_Dem_00424]
[SWS_Dem_00425] [SWS_Dem_00426]
[SWS_Dem_00427] [SWS_Dem_00428]
[SWS_Dem_00429] [SWS_Dem_00431]
[SWS_Dem_00432] [SWS_Dem_00433]
[SWS_Dem_00434] [SWS_Dem_00435]
[SWS_Dem_00437] [SWS_Dem_00438]
[SWS_Dem_00439] [SWS_Dem_00526]
[SWS_Dem_00527] [SWS_Dem_00643]
[SWS_Dem_00684] [SWS_Dem_00685]
[SWS_Dem_00730] [SWS_Dem_00772]
[SWS_Dem_00774] [SWS_Dem_00778]
[SWS_Dem_00779] [SWS_Dem_00818]
[SWS_Dem_00844] [SWS_Dem_00985]
[SWS_Dem_01213] [SWS_Dem_01279]
[RS_Diag_04071] Process events according [SWS_Dem_00232] [SWS_Dem_00382]
to their defined importance [SWS_Dem_00383] [SWS_Dem_00692]
like priority and/or severity [SWS_Dem_01291] [SWS_Dem_01292]
[SWS_Dem_01293] [SWS_Dem_01294]
[RS_Diag_04077] Uses standard [SWS_Dem_00164] [SWS_Dem_00329]
mechanisms provided by [SWS_Dem_00551] [SWS_Dem_01237]
persistency modules [SWS_Dem_01238]
[RS_Diag_04085] No description [SWS_Dem_00463]
[RS_Diag_04091] Notification about valid [SWS_Dem_00999]
freeze frame data to
applications
[RS_Diag_04093] Memory overflow indication [SWS_Dem_00397] [SWS_Dem_00398]
[SWS_Dem_00399] [SWS_Dem_00559]
[SWS_Dem_01023]
[RS_Diag_04097] Decentralized and modular [SWS_Dem_00999]
diagnostic configuration in
applications
[RS_Diag_04098] Interact with standard [SWS_Dem_00999]
bootloader
[RS_Diag_04105] Event memory [SWS_Dem_00580] [SWS_Dem_00607]
management [SWS_Dem_00683] [SWS_Dem_00780]
[SWS_Dem_00781] [SWS_Dem_00783]
[SWS_Dem_00784] [SWS_Dem_00785]
[SWS_Dem_00786] [SWS_Dem_00922]
[SWS_Dem_00923] [SWS_Dem_01000]

AUTOSAR CP R20-11

[RS_Diag_04107] Provide defensive behavior [SWS_Dem_00339]
[RS_Diag_04109] Provide an interface to [SWS_Dem_00651] [SWS_Dem_00652]
retrieve the number of
event memory entries
[RS_Diag_04110] SAE J1939 lamp status [SWS_Dem_00546] [SWS_Dem_00858]
[SWS_Dem_00859] [SWS_Dem_00860]
[SWS_Dem_00861] [SWS_Dem_00862]
[SWS_Dem_00863] [SWS_Dem_00866]
[SWS_Dem_00867] [SWS_Dem_00868]
[SWS_Dem_00869] [SWS_Dem_00870]
[SWS_Dem_00872] [SWS_Dem_00873]
[SWS_Dem_00883] [SWS_Dem_00884]
[SWS_Dem_00885] [SWS_Dem_00887]
[SWS_Dem_00888] [SWS_Dem_00889]
[SWS_Dem_00891] [SWS_Dem_00892]
[SWS_Dem_00893] [SWS_Dem_00894]
[SWS_Dem_00895] [SWS_Dem_00897]
[SWS_Dem_00898] [SWS_Dem_00948]
[SWS_Dem_00974]
[RS_Diag_04111] SAE J1939 [SWS_Dem_00877] [SWS_Dem_00899]
Expanded-FreezeFrame [SWS_Dem_00900] [SWS_Dem_00901]
[SWS_Dem_00902] [SWS_Dem_00903]
[SWS_Dem_00904] [SWS_Dem_00905]
[SWS_Dem_00906] [SWS_Dem_00907]
[RS_Diag_04112] The DEM module shall [SWS_Dem_00645] [SWS_Dem_00845]
support DTCs according to [SWS_Dem_00855] [SWS_Dem_00856]
SAE J1939 [SWS_Dem_00864] [SWS_Dem_00874]
[SWS_Dem_00875] [SWS_Dem_00910]
[SWS_Dem_00911] [SWS_Dem_00912]
[SWS_Dem_00933] [SWS_Dem_00945]
[SWS_Dem_00946] [SWS_Dem_00970]
[SWS_Dem_00971] [SWS_Dem_00976]
[SWS_Dem_00977] [SWS_Dem_00978]
[SWS_Dem_00979] [SWS_Dem_00981]
[RS_Diag_04113] Support a set of SAE [SWS_Dem_00770] [SWS_Dem_00880]
J1939 DM-messages [SWS_Dem_00881] [SWS_Dem_00882]
[SWS_Dem_00908] [SWS_Dem_00909]
[SWS_Dem_00913] [SWS_Dem_00949]
[SWS_Dem_00950] [SWS_Dem_00951]
[SWS_Dem_00982] [SWS_Dem_00983]
[SWS_Dem_01180]
[RS_Diag_04115] The optional parameter [SWS_Dem_00080] [SWS_Dem_00626]
DTCSettingControlOption
Record as part of UDS
service ControlDTCSetting
shall be limited to GroupOf
DTC
[RS_Diag_04117] Configurable behavior for [SWS_Dem_00343] [SWS_Dem_00620]
DTC deletion [SWS_Dem_00670] [SWS_Dem_00679]
[SWS_Dem_00680] [SWS_Dem_00879]

AUTOSAR CP R20-11

[RS_Diag_04118] Optionally support event [SWS_Dem_00382] [SWS_Dem_00383]
displacement [SWS_Dem_00400] [SWS_Dem_00401]
[SWS_Dem_00402] [SWS_Dem_00403]
[SWS_Dem_00404] [SWS_Dem_00405]
[SWS_Dem_00406] [SWS_Dem_00407]
[SWS_Dem_00408] [SWS_Dem_00409]
[SWS_Dem_00443] [SWS_Dem_00692]
[SWS_Dem_01186]
[RS_Diag_04119] Handle the execution of [SWS_Dem_00999]
diagnostic services
according to the assigned
diagnostic session
[RS_Diag_04120] Support a predefined [SWS_Dem_00999]
AddressAndLengthFormat
Identifier
[RS_Diag_04121] Provide the handling of [SWS_Dem_00999]
service DynamicallyDefine
DataIdentifier according to
ISO 14229-1
[RS_Diag_04124] Store the current debounce [SWS_Dem_00674] [SWS_Dem_00675]
counter value non-volatile [SWS_Dem_00676] [SWS_Dem_00782]
to over a power-down cycle
[RS_Diag_04125] Event debounce counter [SWS_Dem_00625] [SWS_Dem_00654]
shall be configurable [SWS_Dem_00655] [SWS_Dem_00656]
[SWS_Dem_00677] [SWS_Dem_00678]
[SWS_Dem_00681] [SWS_Dem_00682]
[SWS_Dem_00776] [SWS_Dem_00788]
[SWS_Dem_00789] [SWS_Dem_00790]
[SWS_Dem_00791] [SWS_Dem_00792]
[SWS_Dem_00793] [SWS_Dem_00794]
[SWS_Dem_00795] [SWS_Dem_01004]
[RS_Diag_04126] Configurable suppression [SWS_Dem_00687] [SWS_Dem_01080]
of events [SWS_Dem_01103] [SWS_Dem_01104]
[SWS_Dem_01106] [SWS_Dem_01108]
[SWS_Dem_01109] [SWS_Dem_01110]
[SWS_Dem_01111] [SWS_Dem_01302]
[SWS_Dem_01335] [SWS_Dem_01336]
[RS_Diag_04127] Configurable record [SWS_Dem_00002] [SWS_Dem_00261]
numbers and trigger [SWS_Dem_00334] [SWS_Dem_00337]
options for DTCSnapshot [SWS_Dem_00461] [SWS_Dem_00468]
Records and DTCExtended [SWS_Dem_00471] [SWS_Dem_00581]
DataRecords [SWS_Dem_00797] [SWS_Dem_00798]
[SWS_Dem_00799] [SWS_Dem_00800]
[SWS_Dem_00801] [SWS_Dem_00802]
[SWS_Dem_00803] [SWS_Dem_00804]
[SWS_Dem_00805] [SWS_Dem_00808]
[SWS_Dem_00809] [SWS_Dem_00810]
[SWS_Dem_00811] [SWS_Dem_00812]
[SWS_Dem_00813] [SWS_Dem_00814]

AUTOSAR CP R20-11

[SWS_Dem_00815] [SWS_Dem_00816]
[SWS_Dem_00817] [SWS_Dem_00819]
[SWS_Dem_00820] [SWS_Dem_00991]
[SWS_Dem_01068] [SWS_Dem_01069]
[SWS_Dem_01070] [SWS_Dem_01071]
[SWS_Dem_01081] [SWS_Dem_01082]
[SWS_Dem_01083] [SWS_Dem_01308]
[SWS_Dem_01351]
[SWS_Dem_CONSTR_06166]
[RS_Diag_04129] Provide OBD-specific [SWS_Dem_00752] [SWS_Dem_00932]
configuration capabilities [SWS_Dem_01220] [SWS_Dem_01221]
[SWS_Dem_01222] [SWS_Dem_01234]
[SWS_Dem_01235]
[RS_Diag_04131] Consistent event [SWS_Dem_01063] [SWS_Dem_01064]
management mechanisms
[RS_Diag_04133] Aging for event memory [SWS_Dem_00019] [SWS_Dem_00442]
entries [SWS_Dem_00489] [SWS_Dem_00490]
[SWS_Dem_00492] [SWS_Dem_00493]
[SWS_Dem_00498] [SWS_Dem_00698]
[SWS_Dem_00824] [SWS_Dem_00985]
[SWS_Dem_01054] [SWS_Dem_01185]
[SWS_Dem_01214] [SWS_Dem_01215]
[SWS_Dem_01219] [SWS_Dem_01221]
[RS_Diag_04134] No description [SWS_Dem_01310] [SWS_Dem_01311]
[SWS_Dem_01391]
[RS_Diag_04135] Support UDS service $38 [SWS_Dem_00999]
(RequestFileTransfer)
[RS_Diag_04136] Configurable ”confirmed” [SWS_Dem_00999]
threshold
[RS_Diag_04137] Definition of replacement [SWS_Dem_01086] [SWS_Dem_01089]
failure [SWS_Dem_CONSTR_06167]
[RS_Diag_04139] Support subfunction 0x42 [SWS_Dem_00999]
of UDS service 0x19
[RS_Diag_04148] Provide capabilities to [SWS_Dem_00259]
inform applications about
diagnostic data changes
[RS_Diag_04150] Support the primary fault [SWS_Dem_00242] [SWS_Dem_00243]
memory defined by ISO [SWS_Dem_01202] [SWS_Dem_01203]
14229-1 [SWS_Dem_01206]
[RS_Diag_04151] Event status handling [SWS_Dem_01208] [SWS_Dem_01209]
[RS_Diag_04155] Notify applications and [SWS_Dem_00475] [SWS_Dem_00618]
BSW modules about [SWS_Dem_00619] [SWS_Dem_01003]
updates of event related
data
[RS_Diag_04156] Support DTCFunctional [SWS_Dem_00594]
Unit
[RS_Diag_04159] Control of DTC storage [SWS_Dem_00243]

AUTOSAR CP R20-11

[RS_Diag_04160] ResponseOnEvent [SWS_Dem_00562]
according to ISO 14229-1
[RS_Diag_04161] Provide support for the [SWS_Dem_01242] [SWS_Dem_01243]
ASMIP algorithm [SWS_Dem_01244] [SWS_Dem_01245]
[SWS_Dem_01246]
[RS_Diag_04162] Parallel fault memory [SWS_Dem_01251] [SWS_Dem_01252]
access [SWS_Dem_01263]
[RS_Diag_04164] Independent event [SWS_Dem_01247]
memories for multiple
diagnostic server instances
(virtual ECUs)
[RS_Diag_04165] Triggering of multiple [SWS_Dem_01250] [SWS_Dem_01339]
events upon a master event
is reported
[RS_Diag_04178] Support operation cycles [SWS_Dem_00019] [SWS_Dem_00673]
according to ISO 14229-1 [SWS_Dem_00693] [SWS_Dem_00698]
[SWS_Dem_00773] [SWS_Dem_00826]
[SWS_Dem_00968] [SWS_Dem_00985]
[SWS_Dem_01224] [SWS_Dem_01225]
[SWS_Dem_01316] [SWS_Dem_01317]
[SWS_Dem_01318]
[RS_Diag_04179] Provide interfaces for [SWS_Dem_00331] [SWS_Dem_00756]
monitoring application. [SWS_Dem_00759]
[RS_Diag_04185] Notify applications about [SWS_Dem_01240] [SWS_Dem_01241]
the clearing of an event
[RS_Diag_04189] Support a fine grained [SWS_Dem_00469] [SWS_Dem_00779]
configuration for Snapshot [SWS_Dem_00821] [SWS_Dem_00995]
Records and Extended [SWS_Dem_01216]
DataRecords
[RS_Diag_04190] Usage of internal data [SWS_Dem_00469] [SWS_Dem_00470]
elements in Snapshot [SWS_Dem_00471] [SWS_Dem_00472]
Records and Extended [SWS_Dem_00473] [SWS_Dem_00592]
DataRecords [SWS_Dem_00643] [SWS_Dem_00673]
[SWS_Dem_00775] [SWS_Dem_00779]
[SWS_Dem_00817] [SWS_Dem_00818]
[SWS_Dem_00819] [SWS_Dem_00820]
[SWS_Dem_00821] [SWS_Dem_00822]
[SWS_Dem_00984] [SWS_Dem_01043]
[SWS_Dem_01044] [SWS_Dem_01045]
[SWS_Dem_01084] [SWS_Dem_01310]
[SWS_Dem_01311] [SWS_Dem_01350]
[RS_Diag_04192] Provide the ability to handle [SWS_Dem_00201] [SWS_Dem_00233]
event specific enable [SWS_Dem_00243] [SWS_Dem_00447]
conditions [SWS_Dem_00449] [SWS_Dem_00450]
[SWS_Dem_00604] [SWS_Dem_00733]
[SWS_Dem_01038]
[RS_Diag_04194] ClearDTC shall be [SWS_Dem_00515] [SWS_Dem_00516]
accessible for applications [SWS_Dem_00570] [SWS_Dem_00571]
[SWS_Dem_00572] [SWS_Dem_00573]
[SWS_Dem_00661] [SWS_Dem_00667]
[SWS_Dem_00668] [SWS_Dem_00669]
[SWS_Dem_01295] [SWS_Dem_01332]

AUTOSAR CP R20-11

[RS_Diag_04195] Chronological reporting [SWS_Dem_00161] [SWS_Dem_00219]
order of the DTCs located [SWS_Dem_00221] [SWS_Dem_00410]
in the configured event [SWS_Dem_00411] [SWS_Dem_00412]
memory [SWS_Dem_00412] [SWS_Dem_00477]
[SWS_Dem_00695] [SWS_Dem_00696]
[SWS_Dem_00787] [SWS_Dem_00935]
[RS_Diag_04201] Support a configuration to [SWS_Dem_00198] [SWS_Dem_00231]
assign specific events to a [SWS_Dem_00269]
customer specific DTC
[RS_Diag_04204] Provide the current status [SWS_Dem_00074] [SWS_Dem_00650]
of each warning indicator.
[RS_Diag_04205] Support of Snapshot [SWS_Dem_00208] [SWS_Dem_01190]
Records [SWS_Dem_01312]
[RS_Diag_04213] Support the mirror fault [SWS_Dem_01205] [SWS_Dem_01206]
memory defined by ISO
14229-1
[RS_Diag_04214] Support the user defined [SWS_Dem_01202] [SWS_Dem_01203]
fault memories defined by [SWS_Dem_01217]
ISO 14229-1
[RS_Diag_04219] Provide the ability to handle [SWS_Dem_00455] [SWS_Dem_00459]
event specific storage [SWS_Dem_00556] [SWS_Dem_00605]
conditions [SWS_Dem_01015] [SWS_Dem_01113]
[SWS_Dem_01309]
[RS_Diag_04220] Support DTCs suppression [SWS_Dem_00915] [SWS_Dem_01100]
[SWS_Dem_01101] [SWS_Dem_01102]
[SWS_Dem_01307] [SWS_Dem_01315]
[RS_Diag_04244] Support sub-function 0x04 [SWS_Dem_01348]
of UDS service 0x19.
[RS_Diag_04245] Support sub-function 0x06 [SWS_Dem_01349]
of UDS service 0x19.
[RS_Ids_00400] Persist QSEv records [SWS_Dem_01352] [SWS_Dem_01353]
[SWS_Dem_01354] [SWS_Dem_01355]
[SWS_Dem_01356]
[SRS_BSW_00005] Modules of the µC [SWS_Dem_00999]
Abstraction Layer (MCAL)
may not have hard coded
horizontal interfaces
[SRS_BSW_00101] The Basic Software Module [SWS_Dem_00180] [SWS_Dem_00181]
shall be able to initialize [SWS_Dem_00256] [SWS_Dem_00340]
variables and hardware in a
separate initialization
function
[SRS_BSW_00161] The AUTOSAR Basic [SWS_Dem_00999]
Software shall provide a
microcontroller abstraction
layer which provides a
standardized interface to
higher software layers
[SRS_BSW_00162] The AUTOSAR Basic [SWS_Dem_00999]
Software shall provide a
hardware abstraction layer

AUTOSAR CP R20-11

[SRS_BSW_00164] The Implementation of [SWS_Dem_00999]
interrupt service routines
shall be done by the
Operating System, complex
drivers or modules
[SRS_BSW_00168] SW components shall be [SWS_Dem_00999]
tested by a function defined
in a common API in the
Basis-SW
[SRS_BSW_00170] The AUTOSAR SW [SWS_Dem_00999]
Components shall provide
information about their
dependency from faults,
signal qualities, driver
demands
[SRS_BSW_00171] Optional functionality of a [SWS_Dem_00255] [SWS_Dem_00579]
Basic-SW component that
is not required in the ECU
shall be configurable at
pre-compile-time
[SRS_BSW_00300] All AUTOSAR Basic [SWS_Dem_00512]
Software Modules shall be
identified by an
unambiguous name
Software Modules shall
only import the necessary
information
[SRS_BSW_00310] API naming convention [SWS_Dem_00256]
[SRS_BSW_00327] Error values naming [SWS_Dem_00999]
convention
[SRS_BSW_00331] All Basic Software Modules [SWS_Dem_00999]
shall strictly separate error
and status information
[SRS_BSW_00336] Basic SW module shall be [SWS_Dem_00102] [SWS_Dem_00182]
able to shutdown [SWS_Dem_00341]
[SRS_BSW_00337] Classification of [SWS_Dem_00368]
development errors
[SRS_BSW_00339] Reporting of production [SWS_Dem_00167] [SWS_Dem_00207]
relevant error status [SWS_Dem_01079] [SWS_Dem_01212]
[SWS_Dem_01289]
[SRS_BSW_00341] Module documentation [SWS_Dem_00999]
shall contains all needed
informations
[SRS_BSW_00347] A Naming seperation of [SWS_Dem_00999]
different instances of BSW
drivers shall be in place
[SRS_BSW_00348] All AUTOSAR standard [SWS_Dem_00999]
types and constants shall
be placed and organized in
a standard type header file

AUTOSAR CP R20-11

Software Modules shall
allow the enabling/disabling
of detection and reporting
of development errors.
[SRS_BSW_00353] All integer type definitions [SWS_Dem_00999]
of target and compiler
specific scope shall be
placed and organized in a
single type header
[SRS_BSW_00357] For success/failure of an [SWS_Dem_00999]
API call a standard return
type shall be defined
Software Modules callback
functions shall avoid return
types other than void if
possible
[SRS_BSW_00360] AUTOSAR Basic Software [SWS_Dem_00999]
Modules callback functions
are allowed to have
parameters
[SRS_BSW_00361] All mappings of not [SWS_Dem_00999]
standardized keywords of
compiler specific scope
shall be placed and
organized in a compiler
specific type and keyword
header
[SRS_BSW_00369] All AUTOSAR Basic [SWS_Dem_01261] [SWS_Dem_01270]
Software Modules shall not [SWS_Dem_01271] [SWS_Dem_01274]
return specific development [SWS_Dem_01299] [SWS_Dem_01300]
error codes via the API [SWS_Dem_01313]
[SRS_BSW_00373] The main processing [SWS_Dem_00125]
function of each AUTOSAR
Basic Software Module
shall be named according
the defined convention
[SRS_BSW_00374] All Basic Software Modules [SWS_Dem_00999]
shall provide a readable
module vendor
identification
[SRS_BSW_00375] Basic Software Modules [SWS_Dem_00999]
shall report wake-up
reasons
[SRS_BSW_00379] All software modules shall [SWS_Dem_00999]
provide a module identifier
in the header file and in the
module XML description
file.
[SRS_BSW_00402] Each module shall provide [SWS_Dem_00177]
version information

AUTOSAR CP R20-11

[SRS_BSW_00406] A static status variable [SWS_Dem_00124] [SWS_Dem_00169]
denoting if a BSW module [SWS_Dem_00364]
is initialized shall be
initialized with value 0
before any APIs of the
BSW module is called
[SRS_BSW_00407] Each BSW module shall [SWS_Dem_00177]
provide a function to read
out the version information
of a dedicated module
implementation
[SRS_BSW_00433] Main processing functions [SWS_Dem_00999]
are only allowed to be
called from task bodies
provided by the BSW
Scheduler
[SRS_BSW_00457] Callback functions of [SWS_Dem_00003] [SWS_Dem_00284]
Application software [SWS_Dem_00613] [SWS_Dem_00986]
components shall be [SWS_Dem_00987] [SWS_Dem_01005]
invoked by the Basis SW
[SRS_Com_02041] The AUTOSAR module [SWS_Dem_00918] [SWS_Dem_00919]
shall handle complex data [SWS_Dem_00920]
types as a consistent set of
data
[SRS_Diag_04126] No description [SWS_Dem_01343] [SWS_Dem_01344]
[SRS_Mem_08549] The NVRAM manager shall [SWS_Dem_00578]
provide functionality to
automatically initialize RAM
data blocks after a software
update
[SWS_BSW_00050] Check parameters passed [SWS_Dem_00173]
to Initialization functions
[SWS_BSW_00212] NULL pointer checking [SWS_Dem_00173]

AUTOSAR CP R20-11
7 Functional specification
The Diagnostic Event Manager (Dem) handles and stores the events detected by di-
agnostic monitors in both Software Components (SW-Cs) and Basic software (BSW)
modules. The stored event information is available via an interface to other BSW mod-
ules or SW-Cs.
DemGeneral contains the global part of the configuration and DemConfigSet contains
the multiple configuration part.
7.1 Startup behavior

[SWS_Dem_00169] dThe Dem module shall distinguish between a pre-initialization
mode and a full-initialized mode (operation mode).c(SRS_BSW_00406)
[SWS_Dem_00180] dThe function Dem_PreInit shall initialize the internal states of
the Dem module necessary to process events and reset debounce counters reported
by SW-C or BSW modules by using Dem_SetEventStatus and Dem_ResetEvent-
DebounceStatus.c(SRS_BSW_00101)
The function Dem_PreInit is called by the ECU State Manager during the startup
phase of the ECU before the NVRAM Manager is initialized. The BSW mod-
ules can start reporting of related events via Dem_SetEventStatus (refer to
[SWS_Dem_00167]).
The function Dem_Init (refer also to [SWS_Dem_00340]) is called during the startup
phase of the ECU, after the NVRAM Manager has finished the restore of NVRAM data.
SW-Components including monitors are initialized afterwards. The function Dem_Init
is also used to reinitialize the Dem module after the Dem_Shutdown was called.
Caveats of Dem_Init: The Dem module is not functional until the Dem module’s en-
vironment has called the function Dem_Init.
7.2 Monitor re-initialization

The primary initialization of the monitors in the application is done via Rte_Start. The
initialization of the event-specific part of the monitor can be triggered by the Dem.
[SWS_Dem_00003] dThe Dem module shall provide the interface InitMoni-
torForEvent to trigger the initalization of a diagnostic monitor (refer also to
[SWS_Dem_00573]).c(SRS_BSW_00457)
For details see also chapter 7.7.3.
The function parameter InitMonitorReason indicates the reason / trigger of initial-
ization.

AUTOSAR CP R20-11
Note: The Dem module does not evaluate the return value (e.g. if other than E_OK) of
this callback function.
Note: The configuration container DemCallbackInitMForE is used to specify the
related port or c-callback per event.
[SWS_Dem_00679] dA call to Dem_RestartOperationCycle shall re-initialize the
diagnostic monitors of all related events by calling their respective callbacks Init-
MonitorForEvent with parameter InitMonitorReason set to DEM_INIT_MONI-
TOR_RESTART.c(RS_Diag_04117)
[SWS_Dem_00680] dThe Dem_ClearDTC API shall trigger the callback function
InitMonitorForEvent of the related event(s) in case of clearing the event(s). The
InitMonitorReason parameter shall be set to DEM_INIT_MONITOR_CLEAR.c(RS_-
Diag_04117)
[SWS_Dem_00681] dThe API Dem_SetEnableCondition shall trigger the callback
function InitMonitorForEvent of the related event(s) in case an enable condition
of the event(s) is changed to fulfilled and thus all enable conditions of the event(s) are
fulfilled. The InitMonitorReason parameter shall be set to DEM_INIT_MONITOR_-
REENABLED.c(RS_Diag_04125)
[SWS_Dem_00682] dThe API Dem_EnableDTCSetting shall trigger the callback
function InitMonitorForEvent of the related event(s) in case ControlDTCSetting
of the event(s) is re-enabled. The InitMonitorReason parameter shall be set to
DEM_INIT_MONITOR_REENABLED.c(RS_Diag_04125)
[SWS_Dem_01113] dThe API Dem_SetStorageCondition shall trigger the call-
back function InitMonitorForEvent of the related event(s) in case a storage con-
dition of the event(s) is changed to fulfilled and thus all storage conditions of the
event(s) are fulfilled. Furthermore the callback shall only be called, if the event did
report FAILED or PASSED while the storage condition was disabled. The Init-
MonitorReason parameter shall be set to DEM_INIT_MONITOR_REENABLED.c(RS_-
Diag_04219)
The following figures show two examples:

AUTOSAR CP R20-11
Figure 7.1: Use-case of the interface InitMonitorForEvent for a specific event
Figure 7.2: Use-case of the interface InitMonitorForEvent for a specific event
The initialization of any function (which may relate to the monitor) can also be triggered
by the Dem.
Example: Adaptations may be initialized in case of clearing the Dem module (on ser-
vice 04/ISO 15031-5[12] request).

AUTOSAR CP R20-11
[SWS_Dem_01046] dIn case multiple triggers for InitMonitorForEvent occur si-

multaneously, the InitMforE shall only be called once. The reason shall be selected
by following priority: DEM_INIT_MONITOR_CLEAR (highest priority), DEM_INIT_MON-
ITOR_RESTART, DEM_INIT_MONITOR_REENABLED (lowest priority) (refer to Dem_-
InitMonitorReasonType).c()
7.3 Diagnostic event definition

A ‘Diagnostic Event’ defines the atomic unit that can be handled by the Dem module.
The status of a ‘Diagnostic Event’ represents the result of a monitor (refer to chapter
7.3.5). The Dem receives the result of a monitor from SW-C via the RTE or other BSW
modules.
The Dem module uses the EventId to manage the status of the ‘Diagnostic Event’ of
a system and performs the required actions for individual test results, e.g. stores the
freeze frame.
[SWS_Dem_00153] dThe Dem module shall represent each Diagnostic Event by an
EventId and the related EventName.c(RS_Diag_04063)
All monitors and BSW modules use the EventId as a symbolic EventName. The Dem
configuration tool replaces the symbolic names by numbers.
[SWS_Dem_00154] dThe EventId and the related EventName shall be unique per Dem
module represented by the ECU configuration (refer to [SWS_Dem_00126]).c(RS_-
Diag_04063)
The Dem is not designed to be able to handle the case where more than one monitor
shares a single EventId.
The Dem module uses an internal monitor status to store the status of reported events.
To the Dcm the UDS status is reported
The Dem module supports several event-specific configuration parameters as shown
in the following figures. For a detailed description, refer to chapter 10 Configuration
specification.

AUTOSAR CP R20-11
DemEventParameter:
+parameter DemEventId: EcucIntegerParamDef
EcucParamConfContainerDef
max = 65535
upperMultiplicity = 65535 min = 1
lowerMultiplicity = 1 symbolicNameValue = true
DemCallbackInitMForEFnc:
EcucFunctionNameDef
DemCallbackInitMForE: +parameter lowerMultiplicity = 0

+subContainer EcucParamConfContainerDef upperMultiplicity = 1
lowerMultiplicity = 0
upperMultiplicity = 1
DEM_EVENT_KIND_SWC:
+literal
EcucEnumerationLiteralDef
DemEventKind:
+parameter EcucEnumerationParamDef
+literal DEM_EVENT_KIND_BSW:
upperMultiplicity = 1 EcucEnumerationLiteralDef
DemCallbackEventUdsStatusChangedFnc:
EcucFunctionNameDef
DemCallbackEventUdsStatusChanged:+parameter lowerMultiplicity = 0
upperMultiplicity = * A
DemCallbackClearEventAllowedFnc:
EcucFunctionNameDef
+parameter lowerMultiplicity = 0
DemCallbackClearEventAllowed:
EcucParamConfContainerDef upperMultiplicity = 1
+subContainer
DemClearEventAllowedBehavior:
EcucEnumerationParamDef
+parameter
defaultValue = DEM_NO_STATUS_BYTE_CHANGE
+literal
DemEventAvailable:
+parameter EcucBooleanParamDef
DEM_NO_STATUS_BYTE_CHANGE:
lowerMultiplicity = 1 +literal
DEM_ONLY_THIS_CYCLE_AND_READINESS:
DemOperationCycleRef:
+reference EcucReferenceDef
+destination DemOperationCycle:
DemEventConfirmationThreshold:
EcucIntegerParamDef
+parameter min = 1
max = 255
defaultValue = 1
DemEventAssociatedIdentification:
EcucIntegerParamDef
+parameter
min = 0
max = 65535
DemEventAvailableInVariant: lowerMultiplicity = 0
EcucBooleanParamDef upperMultiplicity = 1
+parameter
defaultValue = true
DemEnableConditionGroupRef: DemEnableConditionGroup:
+reference EcucReferenceDef +destination EcucParamConfContainerDef
lowerMultiplicity = 0 upperMultiplicity = 255

upperMultiplicity = 1 lowerMultiplicity = 0
Figure 7.3: Event parameter configuration (part 1)

AUTOSAR CP R20-11
DemEventParameter: DemDebounceAlgorithmClass:
EcucParamConfContainerDef +subContainer EcucChoiceContainerDef
lowerMultiplicity = 1 DemEventConfirmationThresholdCounterAdaptable:
upperMultiplicity = 1 EcucBooleanParamDef
+parameter
defaultValue = false
DemFFPrestorageSupported:
EcucBooleanParamDef
DemStorageConditionGroupRef: DemStorageConditionGroup:

DemIndicatorAttribute: DemIndicator:
+destination
EcucParamConfContainerDef +reference DemIndicatorRef: EcucParamConfContainerDef
EcucReferenceDef
+subContainer upperMultiplicity = 255 upperMultiplicity = 255
lowerMultiplicity = 0 lowerMultiplicity = 0
+parameter DemIndicatorBehaviour:
DemDTCRef: EcucReferenceDef DemDTC: EcucParamConfContainerDef

+reference +destination
upperMultiplicity = 1 upperMultiplicity = 65535
DemCallbackEventDataChanged: DemCallbackEventDataChangedFnc:
+subContainer EcucParamConfContainerDef +parameter EcucFunctionNameDef
+reference DemOBDGroupingAssociativeEventsRef:
EcucReferenceDef DemFFPrestorageInNvm: EcucBooleanParamDef
+destination lowerMultiplicity = 0 lowerMultiplicity = 0

+parameter
+literal
DemReportBehavior: REPORT_BEFORE_INIT: EcucEnumerationLiteralDef
+parameter
defaultValue = REPORT_BEFORE_INIT +literal REPORT_AFTER_INIT: EcucEnumerationLiteralDef
DemComponentClassRef: DemComponent: EcucParamConfContainerDef

+reference EcucReferenceDef +destination
lowerMultiplicity = 0 upperMultiplicity = *
DemEventRecoverableInSameOperationCycle:
EcucBooleanParamDef
+parameter
defaultValue = true DemCausalityDelayTime: EcucFloatParamDef
+parameter max = 2.5
DemComponentPriority: EcucIntegerParamDef upperMultiplicity = 1
defaultValue = 0
+parameter min = 0
max = 255
Figure 7.4: Event parameter configuration (part 2)

AUTOSAR CP R20-11
7.3.1 Event priority
Event priority is defined as a ranking of events based upon level of importance. It is

used to determine which fault entries may be removed from the event memory in
case the number of stored events exceeds the maximum number of memory entries
(event memory is full).
[SWS_Dem_00382] dEach supported event shall have a priority assigned to it (re-
fer to parameter DemDTCPriority in DemDTCAttributes).c(RS_Diag_04118, RS_-
Diag_04071)
[SWS_Dem_00383] dA priority value of 1 shall be the highest priority. Larger priority
value shall define lower importance.c(RS_Diag_04118, RS_Diag_04071)
7.3.2 Event occurrence
[SWS_Dem_00011] dThe Dem module shall provide an occurrence counter per event
memory entry.c(RS_Diag_04067)
[SWS_Dem_00523] dThe Dem module shall initialize the occurrence counter with the
value one if the related event is entered in the respective event memory.c(RS_Diag_-
04067)
[SWS_Dem_00524] dIf the configuration parameter DemOccurrenceCounterPro-
cessing is set to DEM_PROCESS_OCCCTR_TF (refer to DemPrimaryMemory or De-
mUserDefinedMemory), the Dem module shall increment the occurrence counter by
one, triggered by each UDS status bit 0 (TestFailed) transition from 0 to 1, if the
related event is already stored in the event memory.c(RS_Diag_04067)
[SWS_Dem_00580] dIf the configuration parameter DemOccurrenceCounterPro-
cessing is set to DEM_PROCESS_OCCCTR_CDTC (refer to DemPrimaryMemory or
DemUserDefinedMemory), the Dem module shall increment the occurrence counter
by one, triggered by each UDS status bit 0 transition from 0 to 1, if the related
event is already stored in the event memory and the UDS status bit 3 is equal
to 1 (refer to chapter 0).c(RS_Diag_04105)
[SWS_Dem_00625] dThe Dem module shall not increment the event-specific oc-
currence counter anymore, if it has reached its maximum value (255, refer to
[SWS_Dem_00471]).c(RS_Diag_04125)
7.3.3 Event kind
There are two different types of events:

• BSW-related events (reported via C-API - Dem_SetEventStatus)
• SW-C-related events (reported via RTE operation - SetEventStatus)

AUTOSAR CP R20-11
This kind is configurable per event (refer to DemEventKind in DemEventParameter).

This is necessary because BSW-events may be reported prior to full Dem initialization
and need to be buffered (refer to chapter 7.8).
7.3.4 Event destination
The configuration parameter DemMemoryDestinationRef (refer to DemDTCAt-

tributes) defines the dedicated storage location(s) of the event and its related data
(refer to chapter 7.7.7).
The “permanent event memory” assignment is implicitly derived from the related DTC
kind (refer to chapter 7.4.1). Emission-related events are automatically assigned to
the permanent event memory, since the storage of an event as “permanent DTC” is
dynamically derived from its current status (handling is described in chapter 7.9.5.8).
In this context the term “permanent” relates to an attribute of emission-related events
and does not relate only to persistent storage via NvM, which is done for each event
memory type anyway.
The definition and use of the different memory types is OEM specific.
For the Dcm-Dem interface the parameter DTCOrigin is used to distinguish between
the different memory areas. The intention is to allow specific operations on the different
memory areas (primary, user defined, permanent and mirror memory).
[SWS_Dem_CONSTR_6104] Limitations on DemMemoryDestinationRef dIf
DemMirrorMemory is configured as DemMemoryDestinationRef, another Dem-
MemoryDestinationRef on the same event of either DemPrimaryMemory or De-
mUserDefinedMemory shall be configured as a prerequisite. The same event shall
not be configured two destinations if one is not DemMirrorMemory.c()
[SWS_Dem_CONSTR_6114] Limitations on DemMemoryDestinationRef dA DTC
can only reference the event memories via DemMemoryDestinationRef to the
event memories of the same DemEventMemorySet. The scenario that a DTC refer-
ences event memories via DemMemoryDestinationRef on different DemEvent-
MemorySet is not supported.c()
7.3.5 Diagnostic monitor definition
A diagnostic monitor is a routine entity determining the proper functionality of a compo-

nent. This monitoring function identifies a specific fault type (e.g. short to ground, open
load, etc.) for a monitoring path. A monitoring path represents the physical system or a
circuit, that is being monitored (e.g. sensor input). Each monitoring path is associated
with exactly one diagnostic event.

AUTOSAR CP R20-11
Runnable Entity
(p) 
(t)  triggered (e . g. on operation invoked event )
R 1 ( p)
R 2 ( t)
R3 (t)
Diagnostic Monitor
R 4 ( p)
R6 ( p )
R 5 (t )
SW-C
... ... ...
Figure 7.5: Example for a monitor embedded within a SW-C
If the monitor debounces on its own, the reporting API is called only after a qualified
result (passed or failed) is available. A report is necessary at least if the result changes.
However, usually it is computationally more efficient for the monitor to always call the
Dem and should therefore be preferred. Hence, it is implementation specific for the
Dem to deal with reports of unchanged results.
If the monitor uses the Dem-internal debouncing mechanism (refer to chapter 7.7.3),
the reporting API is called whenever the code with the functional check is executed.
7.3.6 Event dependencies
The priority of events within the assigned DemComponent and furthermore the depen-
dency relation between the DemComponents is used for filtering the storage of error
reports to the failure memory.
[SWS_Dem_01126] dWhenever an event reports FAILED, it shall be considered as
CONSECUTIVE FAULT, if any other event with higher priority at the same DemCompo-
nent already is FAILED.c()
[SWS_Dem_01127] dWhenever an event reports FAILED, it shall be considered as
CONSECUTIVE FAULT, if any parent DemComponent is FAILED.c()

AUTOSAR CP R20-11
[SWS_Dem_01128] dThe Dem shall allow to ignore the priority of events of a Dem-
ComponentIgnoresPriority). In this case, the event shall only be considered as
CONSECUTIVE FAULT if any parent component is FAILED (other events FAILED sta-
tus at the same component shall be ignored).]c()
[SWS_Dem_01129] dIf a reported failure is not considered as consecutive fault, it shall
be considered as CAUSAL FAULT. Causal faults shall be handled normally.c()
[SWS_Dem_01218] dIf a reported failure is not considered as consecutive fault
and it has configured a DemCausalityDelayTime, it shall be considered as
PRELIMINARY-CAUSAL FAULT. Starting from the point in time where the report of
the event occurs, until the DemCausalityDelayTime is elapsed, the event can be
reconsidered as being a consecutive fault. If another failure is reported during this time
which has higher priority at the same DemComponent or at any parent DemCompo-
nent, the event shall be reconsidered as consecutive fault. After the time is elapsed,
the failure will not be reconsidered.c()
[SWS_Dem_01130] dA failure which is considered as consecutive fault shall not be
stored to the failure memory. (The handling shall be analogous to storage condition
not fulfilled).c()
[SWS_Dem_01211] dA report of DEM_EVENT_STATUS_FDC_THRESHOLD_REACHED
(e.g. either via interface call or when reaching the configured threshold in debounce
algorithm) which is considered as consecutive report of a Failed event shall not be
stored to the failure memory. The handling shall be analogous to storage condition not
fulfilled.c()
Note: Other reports of DEM_EVENT_STATUS_FDC_THRESHOLD_REACHED shall not be
considered as causal.
[SWS_Dem_01131] dThe Dem shall provide the interface Dem_GetComponent-
Failed, which allows querying a DemComponents FAILED status.c()
[SWS_Dem_01132] dIf DemTriggerFiMReports (refer to DemGeneral) is enabled,
the Dem shall notify the FiM module [8] on each change of DemComponent failed status
by calling the function DemTriggerOnComponentStatus.c()
[SWS_Dem_01133] dIf the component status is changing and DemComponent-
FailedCallbackFnc is configured or DemComponentFailedCallbackUsePort
is set to TRUE, the Dem shall trigger the callback DemTriggerOnComponentSta-
tus.c()
[SWS_Dem_CONSTR_06157] dSetting DemComponentFailedCallbackUsePort
to TRUE is only allowed, if DemComponentFailedCallbackFnc is not configured.c
()

AUTOSAR CP R20-11
7.3.7 Component availability
[SWS_Dem_01134] dThe Dem shall support the availability of DemComponent. Com-

ponents which are not available shall be treated as if they are not included in the system
(e.g. Dem_GetComponentFailed will return E_NOT_OK).c()
[SWS_Dem_01135] dThe interface Dem_SetComponentAvailable shall be avail-
able to set the availability state of a component.c()
[SWS_Dem_01136] dWith setting a DemComponent to not available, all assigned
events shall also be set as not available.c()
[SWS_Dem_01239] dAfter startup all DemComponents shall be available.c()
[SWS_Dem_01226] dIf a DemComponent is set to ‘not available’ via Dem_SetCompo-
nentAvailable, the Dem shall treat all the dependent components (children) as if
they are set as ‘not available’.c()
[SWS_Dem_01227] dIf a DemComponent is set to ‘not available’ via Dem_SetCom-
ponentAvailable, the Dem shall set all assigned events to ‘not available’, including
the events of all child nodes. The behavior for the events will be analogous to setting
each event individually to ‘not available’ (e.g. setting the event status).c()
[SWS_Dem_01228] dIf a DemComponent is set to ‘not available’ via Dem_SetCom-
ponentAvailable and any individual event assigned to it (see [SWS_Dem_01227])
is already failed, the individual event will be kept as ‘available’. Dem_SetComponen-
tAvailable still shall return E_OK.c()
[SWS_Dem_01229] dIf a DemComponent is set to available via Dem_SetComponen-
tAvailable, all assigned events are also set to ‘available’, including the events of all
child nodes (if those nodes are not still set to ‘not available’). The behavior for the indi-
vidual events will be analogous to setting them individually to ‘available’ (e.g. triggering
InitMonitorForEvent).c()
[SWS_Dem_01231] dIf the function Dem_SetEventAvailable is called for an event
to set the event to ‘available’, the function shall return E_NOT_OK, in case its related
node is current ‘not available’.c()
[SWS_Dem_01232] dIf an event is set to available using Dem_SetEventAvail-
able and its component is ‘not available’, Dem_SetEventAvailable shall return
E_NOT_OK.()c()
7.4 Diagnostic trouble code definition

A ‘Diagnostic trouble code’ defines a unique identifier (shown to the diagnostic tester)
mapped to a ‘Diagnostic event’ of the Dem module. The Dem provides the status of
‘Diagnostic trouble codes’ to the Dcm module (refer to chapter 7.11.2).

AUTOSAR CP R20-11
DemConfigSet:
DemEventParameter:
+subContainer EcucParamConfContainerDef
+reference
DemDTCRef:
+subContainer DemDtcValue: EcucIntegerParamDef
EcucReferenceDef
max = 16777214
DemDTC: +destination upperMultiplicity = 1
min = 1
EcucParamConfContainerDef lowerMultiplicity = 0
lowerMultiplicity = 0 +parameter
+subContainer
DemDTCAttributes:
DemDTCAttributesRef: EcucReferenceDef EcucParamConfContainerDef
+destination
+reference
+subContainer
DemObdDTC:
DemObdDTCRef: EcucReferenceDef
+reference +destination EcucParamConfContainerDef
+literal DEM_SEVERITY_NO_SEVERITY:
DemDTCSeverity: EcucEnumerationParamDef
+literal
defaultValue = DEM_SEVERITY_NO_SEVERITY DEM_SEVERITY_MAINTENANCE_ONLY:
+parameter
+literal
DEM_SEVERITY_CHECK_AT_NEXT_HALT:
+literal
DEM_SEVERITY_CHECK_IMMEDIATELY:
DemDTCFunctionalUnit: EcucIntegerParamDef
+parameter max = 255
min = 0
lowerMultiplicity = 0 DEM_DTC_WWHOBD_CLASS_NOCLASS:
+literal EcucEnumerationLiteralDef
DemWWHOBDDTCClass: +literal
EcucEnumerationParamDef DEM_DTC_WWHOBD_CLASS_A:
+literal
DEM_DTC_WWHOBD_CLASS_B1:
+parameter EcucEnumerationLiteralDef
+literal
+literal
DEM_DTC_WWHOBD_CLASS_C:
+literal DURING_SHUTDOWN:
DemNvStorageStrategy: EcucEnumerationLiteralDef
defaultValue = DURING_SHUTDOWN +literal

upperMultiplicity = 1 IMMEDIATE_AT_FIRST_OCCURRENCE:
lowerMultiplicity = 0 EcucEnumerationLiteralDef
Figure 7.6: DTC configuration

AUTOSAR CP R20-11
DemConfigSet: DemDTC:
EcucParamConfContainerDef +subContainer EcucParamConfContainerDef
+subContainer +reference
DemObdDTC: EcucParamConfContainerDef DemObdDTCRef:

upperMultiplicity = 65535 +destination EcucReferenceDef
DemDtcValue: EcucIntegerParamDef
+parameter min = 1
max = 65535
DemConsiderPtoStatus: EcucBooleanParamDef
+parameter
DemEventOBDReadinessGroup:
+parameter
DemJ1939DTCValue: EcucIntegerParamDef

min = 1
Figure 7.7: OBD-DTC configuration
7.4.1 DTC kind
7.4.2 DTC format
[SWS_Dem_00013] dThe Dem module shall support DTC formats for DemDTC accord-
ing to:
• ISO-14229-1[2]
• SAE J2012 OBD DTC (aka 2-byte DTC) [13]
• SAE J1939-73[14]
• ISO 11992-4[15]
• SAE J2012 WWH-OBD DTC (aka 3-byte DTC) [13]
c()

AUTOSAR CP R20-11
The configuration parameter DemTypeOfDTCSupported is used to specify one of the

supported DTC formats defined in [SWS_Dem_00013] of the ECU (refer to Dem_-
GetTranslationType). This is required to determine the DTC format value to be
reported for ISO-14229-1[2] service Read DTC Information (0x19).
[SWS_Dem_00645] dThe Dem module shall support different DTC numbers for UDS,
OBD, and J1939 DTCs based on separate configuration parameters (refer to parame-
ters DemDTC and DemObdDTC in DemConfigSet).c(RS_Diag_04112)
A DTC can have any combination of the three formats (UDS, OBD, and J1939), i.e.
one, two, or three formats at the same time. The Dem will therefore handle three DTC
value lists internally. The reported format depends on the Dem_DTCFormatType or is
defined by the context of the related API.
[SWS_Dem_00277] dThe Dem shall report DTC values as a uint32 with byte 0 = Low-
Byte, byte 1 = MiddleByte, byte 2 = HighByte and byte 3 is unused. For OBD DTC
format there are only two bytes (HighByte, LowByte) used. The Dem services shall
report these DTCs as a uint32 with byte 1 = LowByte, byte 2 = HighByte, byte 3 is
unused and byte 0 = 0x00.c()
non OBD unused DTC HighByte DTC MiddleByte DTC LowByte
OBD unused DTC HighByte DTC LowByte 0x00
Byte 3 Byte 2 Byte 1 Byte 0

Figure 7.8: DTC Byte Order
Note: The Dem expects the SPN and FMI values of the J1939DTC to be configured
according to the J1939 standard. The Dem will not do any encoding/transcoding. Refer
chapter 5.7.1.11 SPN Conversion Method in [15] for details.
[SWS_Dem_01180] dThe Dem shall report DTC values as a uint32 with byte 0 = Low-
Byte, byte 1 = MiddleByte, byte 2 = HighByte and byte 3 is unused. For WWH-OBD
DTC format there are only three bytes (HighByte, MiddleByte and LowByte) used. The
Dem services shall report these DTCs as a uint32 with byte 1 = LowByte, byte 2 =
HighByte, byte 0 is used as FTB (as of SAE J2012-DA) [13].c(RS_Diag_04113)
[SWS_Dem_CONSTR_06146] Dependency for DemDtcValue dThe OBD DTC
DemDtcValue shall only be present if DemOBDSupport is set to DEM_OBD_MASTER_-
ECU or DEM_OBD_PRIMARY_ECU.c()
[SWS_Dem_00269] dThe function Dem_GetDTCOfEvent shall get the DTC which is
mapped to EventId by the Dem configuration.c(RS_Diag_04201)

AUTOSAR CP R20-11
7.4.3 DTC groups
In addition to single DTC values, groups of DTCs can be configured (refer to Dem-
GroupOfDTC), as defined by ISO 14229-1 [2] - Annex D.1. Each DTC group has its
own DTC group value assigned (which must be unique to any other DTC and DTC
group value). When requesting operations on DTC groups (like ClearDTC and Dis-
able/Enable DTC), the DTCGroup is selected by the DTC value.
[SWS_Dem_01059] dThe DemGroupOfDTC shall represent the values of the DTC
Group boundaries.c() Note: A group with the global boundaries 0x000100 and 0xfffe00
does not need to be configured, as the group ALL is automatically defined.
[SWS_Dem_01061] dAll the DTCs in the range between the dtc-code of the requested
group and the next higher dtcgroup-code shall be treated as belonging to the group.c()
Note: DTC groups are relevant for the diagnostic service ClearDiagnosticInformation
(0x14, refer to Dem_ClearDTC).
[SWS_Dem_01337] dThe Dem shall support the predefined DTC group GroupO-
fAllDTCs (0xFFFFFF) within the parameter DTC of Dem_SelectDTC.c()
[SWS_Dem_01338] dThe Dem shall support the predefined DTC group emission re-
lated DTCs for WWH-OBD (0xFFFF33) within the parameter DTC of Dem_SelectDTC
if WWH-OBD is supported.c()
Note, the DTC group ’all DTCs’ will not be configured in DemGroupOfDTC, because it
has always to be provided by the Dem module
DemGroupOfDTC: DemGroupDTCs:
EcucParamConfContainerDef EcucIntegerParamDef
+parameter
lowerMultiplicity = 0 min = 256
upperMultiplicity = 65535 max = 16776959
Figure 7.9: DTC group configuration
Taking into consideration that 0xFFFFFF is an unconfigurable value meaning “all DTCs
group”, each of the DTCs configured for a group “X” let’s say, shall have their ids in the
open interval (ID_of_group_X, ID_of_next_configured_group) e.g.:
powertrain DTC group –> 0x3FFF00 DTC1 –> 0x3FFF04

DTC2 –> 0x3FFF06
.
.
.
DTCn –> 0x3FFF0E
body DTC group –> 0x7FFF0F ...
DTCs in the body DTC group
...

AUTOSAR CP R20-11
As a configuration constraint of the above mentioned approach on DTC groups, if there

is one or more DTC groups configured, there is no way to configure group independent
DTCs.
7.4.4 DTC severity
The DTC severity is used to provide information regarding the importance of the spe-
cific events according to ISO-14229-1[2], Annex D.3 “DTC severity and class definition”.
The DemDTCSeverity is only available for UDS DTCs.
[SWS_Dem_01291] dIf the API Dem_GetSeverityOfDTC or Dem_GetNextFil-
teredDTCAndSeverity is called and for the selected DTC a severity value in
DemDTCSeverity is configured, the Dem shall set the value configured in DemDTC-
Severity as DTCSeverity.c(RS_Diag_04071)
[SWS_Dem_01292] dIf the API Dem_GetSeverityOfDTC or Dem_GetNextFil-
teredDTCAndSeverity is called and for the selected DTC no severity value in
DemDTCSeverity is configured, the Dem shall set DEM_SEVERITY_NO_SEVERITY
as DTCSeverity.c(RS_Diag_04071)
7.4.5 Functional unit
[SWS_Dem_01293] dIf the API Dem_GetFunctionalUnitOfDTC is called and for

the selected DTC a functional unit value in DemDTCFunctionalUnit is configured,
the Dem shall set the value configured in DemDTCFunctionalUnit in the out param-
eter DTCFunctionalUnit.c(RS_Diag_04071)
[SWS_Dem_01294] dIf the API Dem_GetFunctionalUnitOfDTC is called and for
the selected DTC no functional unit in DemDTCFunctionalUnit is configured, the
Dem shall set a value of 0x00 in the out parameter DTCFunctionalUnit.c(RS_Diag_-
04071)
7.4.6 DTC significance
There are two different significance levels of DTCs:

• fault: classifies a failure, which relates to the component/ECU itself (and requires
for example a repair action)
• occurrence: classifies an issue, which indicates additional information concerning
insufficient system behavior (and relates for example to a condition out of the
ECU’s control)

AUTOSAR CP R20-11
This significance level is configurable per event (refer to DemDTCSignificance in

DemDTCAttributes) and can be mapped as a data element (refer to DEM_SIGNIF-
ICANCE).
7.4.7 Suppress DTC output
This chapter describes the dynamic suppression of events/ DTCs during runtime via
API call. A suppressed DTC behaves in a way that it is not visible for the tester but can
be processed continuously by the diagnostic monitor.
An exemplary use-case could be that the decision to hide a DTC in a certain market is
done by the SW-C at runtime.
The configuration parameter DemSuppressionSupport (refer to DemGeneral) con-
trols the availability of the DTC suppression functionality
[SWS_Dem_00915] dThe Dem shall suppress a DTC if all related events of this DTC are
not available.c(RS_Diag_04220)
For details see chapter 7.4.8.
If there is a one to one relationship between DTC and event, the DTC is suppressed if the
related event is not available. If the DTC is a combined DTC, the DTC is suppressed if
all combined events are not available.
Concerning output and query functions, suppressed DTCs are treated as if they are
not configured in the system.
[SWS_Dem_01100] Behavior of DTC query functions for suppressed DTCs dIn
case any of the following APIs is called
• Dem_GetStatusOfDTC
• Dem_GetSeverityOfDTC
• Dem_GetFunctionalUnitOfDTC
• Dem_ClearDTC
on a single selected DTC which is suppressed, the Dem shall return
DEM_WRONG_DTC.c(RS_Diag_04220)
[SWS_Dem_01101] dA suppressed DTC shall not be visible for the following Dcm
query-functions; therefore the following functions shall treat the DTC as if filter is not
matching:
• Dem_DcmGetDTCOfOBDFreezeFrame
• Dem_DcmReadDataOfOBDFreezeFrame
• Dem_DcmGetInfoTypeValue08
• Dem_DcmGetInfoTypeValue0B

AUTOSAR CP R20-11
• Dem_DcmReadDataOfPID01
• Dem_GetDTCByOccurrenceTime
• Dem_GetNextFilteredDTC
• Dem_GetNextFilteredDTCAndFDC
• Dem_GetNextFilteredDTCAndSeverity
• Dem_GetNextFilteredRecord
• Dem_J1939DcmFirstDTCwithLampStatus
• Dem_J1939DcmGetNextDTCwithLampStatus
• Dem_J1939DcmGetNextFreezeFrame
• Dem_J1939DcmSetDTCFilter
• Dem_J1939DcmGetNumberOfFilteredDTC
• Dem_J1939DcmGetNextFilteredDTC
• Dem_J1939DcmSetRatioFilter
• Dem_J1939DcmGetNextFilteredRatio
• Dem_J1939DcmReadDiagnosticReadiness1
• Dem_SelectFreezeFrameData
• Dem_SetDTCFilter
• Dem_SelectExtendedDataRecord
c(RS_Diag_04220)
Note: This means, the (external) reporting (e.g. DTC number, UDS status, DTC ex-
tended data records, DTC statistical data, IUMPR, ...) of the DTC is suppressed.
[SWS_Dem_01102] dDTC suppression shall not stop event processing of the corre-
sponding DTC.c(RS_Diag_04220)
Note: This means that e.g. event qualification, update of environmental data
and functional degradation is still processed within the Dem.
Note: If DTC/freeze frame should not be stored in the fault memory storage condi-
tions should be used in addition.
[SWS_Dem_01307] Functionality of Dem_GetDTCSuppression dIf Dem_GetDTC-
Suppression is called, the Dem shall return the DTC suppression status in the output

AUTOSAR CP R20-11
parameter SuppressionStatus. A value of TRUE means that the DTC was sup-
pressed by a call of Dem_SetDTCSuppression with SuppressionStatus = TRUE,
a value of FALSE means, that the DTC is currently not suppressed.c(RS_Diag_04220)
[SWS_Dem_01315] dIf Dem_SetDTCSuppression is called the Dem shall set the
suppression status of the selected DTC to value of the parameter Suppression-
Status.c(RS_Diag_04220)
Also there are various reasons, why a DTC is not processed and thus is not visible for
diagnostics, the suppression state itself is only changed by Dem_SetDTCSuppres-
sion. Dem_GetDTCSuppression only evaluates this suppression state.
7.4.8 Availability of events (visibility and computation)
This chapter describes a method to mark events as not available without removing
them from the actual configuration. An event which is not available is treated as if it
was not included in the Dem configuration.
An exemplary use-case could be that a control unit and its software support differ-
ent kind of hardware to be controlled. Hardware variants vary in certain parts being
available or not available. Still the same control unit and software shall be applied.
1. One calibration set is generated per hardware variant. The application engineers
set up a post-build configuration to make sure the software behaves correctly for
the hardware. For certain parts not included in a hardware variant, this means
that related Events need to be shut down, suppressed. These events shall be-
have completely neutral, never set their LastFailed, not cause limp-home modes,
not be visible to garage services.
=> ECUC parameter DemEventAvailableInVariant set to TRUE (enabled)
or FALSE (disabled)
2. One calibration covers multiple hardware variants. During production, or even
at run-time when hardware is changed (by the garage) some coding bits are
written to the control unit, or some network message is received, to change the
behaviour of the software in accordance with the changes in hardware. As in 1,
certain Events need to be suppressed.
=> ECUC parameter DemEventAvailableInVariant set to TRUE (enabled)
=> ECUC parameter DemEventAvailable defines the initial availability of an
event
=> Interface Dem_SetEventAvailable is used to change the availability de-
fined by DemEventAvailable during runtime
[SWS_Dem_01343] Enable/disable Events by configuration dThe configuration pa-
rameter DemEventAvailableInVariant shall be used as master to consider an

AUTOSAR CP R20-11
Event as enabled or disabled. If the configuration parameter DemEventAvail-

ableInVariant is set to FALSE, the Dem shall treat the Event as if it is not config-
ured as DemEventParameter. If DemEventAvailableInVariant is not set or set
to TRUE, the Dem shall consider the Event as enabled depending on other sources.c
(SRS_Diag_04126)
Note: DemEventAvailableInVariant allows to disable an Event that is not
needed, but included in the software release; even the related SW-C is prevented from
making it available through Dem_SetEventAvailable.
[SWS_Dem_01344] Dealing with availability of Events dThe Dem shall treat an
event as unavailable if:
• DemEventAvailableInVariant == FALSE or
• DemEventAvailable == FALSE or
• DemEventAvailable is overwritten by Dem_SetEventAvailable(FALSE) or
• The component referenced by DemComponentClassRef is not available
c(SRS_Diag_04126)
[SWS_Dem_00687] dThe Dem shall provide functionality during runtime to treat events
as if they were not configured as DemEventParameter. The configuration parameter
DemAvailabilitySupport is used to enable the functionality provided by Dem_-
SetEventAvailable().c(RS_Diag_04126)
[SWS_Dem_01103] dUnavailable events shall not be considered for computation of
service $01 PID $41.c(RS_Diag_04126)
[SWS_Dem_01104] dIUMPR ratios referring to an unavailable event shall neither be
computed nor reported.c(RS_Diag_04126)
[SWS_Dem_01106] dThe Dem shall not provide the function Dem_SetEventAvail-
able in VARIANT-POST-BUILD. Rational: In VARIANT-POST-BUILD the initial values
are not valid before Dem_Init (postbuild initialization time).c(RS_Diag_04126)
[SWS_Dem_01108] dIf an event is set to unavailable, the corresponding event shall
be treated as if it is not configured in the system (e.g. Dem_SetEventStatus and
Dem_GetEventUdsStatus shall return E_NOT_OK). The following APIs are affected:
• Dem_SetEventStatus
• Dem_GetEventUdsStatus
• Dem_ResetEventDebounceStatus
• Dem_ResetEventStatus
• Dem_PrestoreFreezeFrame
• Dem_ClearPrestoredFreezeFrame
• Dem_GetDebouncingOfEvent

AUTOSAR CP R20-11
• Dem_GetDTCOfEvent
• Dem_GetFaultDetectionCounter
• Dem_GetEventFreezeFrameDataEx
• Dem_GetEventExtendedDataRecordEx
• Dem_ClearDTC
• Dem_DcmGetDTRData
• Dem_RepIUMPRFaultDetect
• Dem_RepIUMPRDenRelease
• Dem_SetWIRStatus
• Dem_SetEventFailedWithSyncFreezeFrame
c(RS_Diag_04126)
Note: The availability of an event may also impact the suppression of a DTC (see
[SWS_Dem_00915]).
[SWS_Dem_01109] dWhen the API Dem_SetEventAvailable is called with
AvailableStatus = FALSE, the Dem shall return E_NOT_OK if:
• for the event an event memory entry already exists, or
• any of the event status flags ’testFailed’, ’pending’, ’confirmed’ or ’warningIndica-
torRequested’ is set
c(RS_Diag_04126)
[SWS_Dem_01302] Asynchronous behavior of Dem_SetEventAvailable dThe Dem
shall process a call of the Dem_SetEventAvailable asynchronously. This means
that the final result is available at a later point in time.c(RS_Diag_04126)
A later point in time is meant to be implementation specific, it could be the next main
function and after Dem_SetEventAvailable has returned.
[SWS_Dem_01110] dIf Dem_SetEventAvailable is called with AvailableSta-
tus == ‘false’, the Dem shall set the UDS status shall be set to 0x00 for this event.c
(RS_Diag_04126)
Note: If the UDS status changes, the corresponding callbacks are called to properly
provide the information about a changed status to the users.
[SWS_Dem_01111] dIf Dem_SetEventAvailable is called with AvailableSta-
tus == ‘true’, the Dem shall set the UDS status shall be set to 0x50 for this event.c
(RS_Diag_04126)

AUTOSAR CP R20-11
[SWS_Dem_01345] Reaction on calls related to disabled events dIf an Event is

configured with DemEventAvailableInVariant set to FALSE and the API Dem_-
SetEventAvailable is called with AvailableStatus = TRUE for this EventId,
the API Dem_SetEventAvailable shall return E_NOT_OK.c()
[SWS_Dem_01230] dIf the function Dem_SetEventAvailable is called to set an
event to ‘available’, the Dem shall trigger the event initialization using DEM_INIT_-
MONITOR_REENABLED as InitMonitorReason.c()
[SWS_Dem_01346] dIf Dem_GetEventAvailable is called with a valid EventId,
it shall set the output value AvailableStatus to the Event’s availability and return
E_OK.
The availability is determined by the configuration parameter DemEventAvail-
able (modifiable through Dem_SetEventAvailable) and DemEventAvailableCnf
([SWS_Dem_01344] ("Dem shall treat an Event as unavailable...").c()
[SWS_Dem_01347] dIf Dem_GetEventAvailable is called with an invalid EventId,
the Dem shall return E_NOT_OK.c()
7.5 Monitored Component Definition

A monitored component is a part of the system, which is relevant for being checked
for proper operation. Malfunctions of the component need to be reported and docu-
mented. For this, usually one or multiple monitorings are defined and assigned to the
component.
Furthermore the status of such components is relevant and used for influencing the
system behavior (status of components may be used in Fim) and error documentation
(filtering of consecutive failure entries).
The Dem allows to explicitly define the monitored components as DemComponent,
defining the relation between events and components and finally allows to define the
relation in-between the components.

AUTOSAR CP R20-11
ECU CAN Signal1

RAM BusOff Gradient
ROM MSGFailure Range
Plaus
Signal2
Gradient
Range
Plaus
HWC1 HWC2 HWC3
Gradient
Range
Gradient
Range
Gradient
Range
Signal3
Plaus Plaus Plaus
S3_Gradient
S3_Range
S3_Plaus
Figure 7.10: Event dependencies
7.5.1 Definition of components and dependencies
[SWS_Dem_01118] dThe Dem shall represent monitored components as DemCompo-

nent with a unique identifier, which is used in interfaces to identify the component.c
()
[SWS_Dem_01119] dEach DemComponent shall have a boolean status FAILED,
which represents the information whether the component has errors or not.c()
[SWS_Dem_01120] dThe Dem shall allow defining relations between DemComponent.
The relations are directed, which means one component is depending on another com-
ponent (DemImmediateChildComponentRef). Any component which has a directed
relation (also over multiple components) is considered as parent component.c()
Example: a -> b -> c -> d
a and b are parents of c
c and d are depending on b
[SWS_Dem_CONSTR_6106] dOnly directed acyclic graph structures are sup-

ported for the dependencies of DemComponent.c()
[SWS_Dem_01121] dThe Dem shall allow to assign events to DemComponents.c()

AUTOSAR CP R20-11
[SWS_Dem_CONSTR_6107] dEvents may be assigned to exactly one DemCompo-

nent for which the monitoring is testing the error conditions. Multiple events may be
assigned to the same component.c()
[SWS_Dem_01122] dThe Dem shall allow sorting the events assigned to a DemCom-
ponent by priority. The priority is defined per event as DemComponentPriority.c
()
[SWS_Dem_01123] dOn reporting an error (DEM_MONITOR_STATUS_TF) for an
event, the assigned DemComponent shall be set as FAILED in the context of the event
report.c()
[SWS_Dem_01124] dOn setting a DemComponent to FAILED, all dependent compo-
nents shall be set as FAILED.c()
[SWS_Dem_01125] dA DemComponent shall be set to NOT FAILED, when allassigned
events are NOT FAILED (DEM_MONITOR_STATUS_TF) and all parent components
are NOT FAILED.c()
7.6 Operation cycle management

The Dem module provides the possibility to define different operation cycles (ref. to
ISO-14229-1[2]).
Examples of operation cycles are:
• ignition on/off cycle
• power up/power down cycle
• OBD driving cycle
• engine warm up cycle
• operation active/passive cycle
• accumulated operating time
The various operation cycles serve as the basis for calculating cycle-dependent
status information such as testCompleteThisOperationCycle. In addition, the oper-
ation cycles are the basis for certain functionalities such as the confirmation of
failures and the aging of failures. The restart or switch to the next operation cycle
via Dem_RestartOperationCycle serves as the trigger for the calculation of these
functionalities.

AUTOSAR CP R20-11
DemGeneral: EcucParamConfContainerDef
+subContainer
DemOperationCycle: DemOperationCycleId:

lowerMultiplicity = 1 +parameter upperMultiplicity = 1
symbolicNameValue = true
min = 0
max = 255
+reference DemLeadingCycleRef:
EcucReferenceDef
+destination lowerMultiplicity = 0
requiresSymbolicNameValue = true
Figure 7.11: Operation cycle configuration
DemDTCAttributes: DemAgingCycleRef: DemOperationCycle:

EcucParamConfContainerDef EcucReferenceDef EcucParamConfContainerDef
upperMultiplicity = 65535 lowerMultiplicity = 0 upperMultiplicity = 256

lowerMultiplicity = 0 upperMultiplicity = 1 lowerMultiplicity = 1
+destination
+reference
DemEventParameter: DemOperationCycleRef:
EcucParamConfContainerDef EcucReferenceDef
DemGeneralOBD: DemOBDPFCCycleRef:
EcucParamConfContainerDef +reference EcucReferenceDef +destination
DemLeadingCycleRef: +reference
EcucReferenceDef
upperMultiplicity = 1 +destination
Figure 7.12: Operation and aging cycle assignment
[SWS_Dem_01318] Operation Cycle restart dCalling the function Dem_Restart-

OperationCycle shall be allowed only after Dem_PreInit. In case an operation
cycle is restarted before Dem_Init, the processing of the restart shall be done after
Dem_Init.c(RS_Diag_04178)
[SWS_Dem_01316] Operation Cycle restart dThe Dem shall only restart operation
cycles after the previous restart has been fully processed. In other words this means
that there is no Operation Cycle restart queue.c(RS_Diag_04178)

AUTOSAR CP R20-11
[SWS_Dem_01221] dThe Dem allows definition of dependent operation cycles

using DemLeadingCycleRef parameter. Whenever the parameter is set, the op-
eration cycle is considered as a dependent operation cycle. Whenever the
parameter is not set, the operation cycle is considered as "normal" operation
cycle.c(RS_Diag_04129, RS_Diag_04133)
[SWS_Dem_01222] dIf the operation cycle passed to Dem_SetCycleQuali-
fied is not configured at all, the Det error DEM_E_WRONG_CONFIGURATION shall
be reported.c(RS_Diag_04129)
[SWS_Dem_01317] dThe Dem shall store the qualification state of the dependent
operation cycles over power cycles.c(RS_Diag_04178)
[SWS_Dem_01224] Operation Cycle restart dWhenever an operation cycle is
requested to be restarted via Dem_RestartOperationCycle, all operation cy-
cles which are depending on the selected operation cycle shall also be restarted,
but only if they are qualifiedc(RS_Diag_04178)
Note: Setting a dependent operation cycle as qualified will not start the opera-
tion cycle, even if the leading operation cycle has been started before.
[SWS_Dem_01225] Operation Cycle restart dWhen restarting a dependent oper-
ation cycle, its operation cycle qualification shall be reset.c(RS_Diag_04178)
[SWS_Dem_01234] dThe API Dem_GetCycleQualified shall provide the qualifica-
tion state of the requested operation cycle in the out parameter "isQualified".c(RS_-
Diag_04129)
[SWS_Dem_01235] dIf the operation cycle passed to Dem_GetCycleQualified
is not configured at all, the Det error DEM_E_WRONG_CONFIGURATION shall be re-
ported.c(RS_Diag_04129)
[SWS_Dem_01220] dIf DemOBDDelayedDCYConfirmedAndMIL is set to TRUE, the
behavior of events linked to the OBD driving cycle (DemOBDDrivingCycleRef) shall
be changed:
If the operation cycle is not qualified, status reports shall be processed, except update
of the confirmed status. At the moment the OBD driving cycle is set to qualified, the Dem
shall execute computations required to reach the confirmed states of events collected
during the "not qualified" phase of the cycle.c(RS_Diag_04129)
OBD legislation requires specific implementation of operation cycles. For emission
related ECUs it is mandatory to implement these accordingly.
7.6.1 Operation Cycle Counters
7.6.1.1 Cycles since last failed
The counter Cycles since last failed is representing the number of operation cycles
since the DTC fault detection counter last reached its maximum value +127 (since

AUTOSAR CP R20-11
DTC information was last cleared). All operation cycles, including those during which
the test was not completed shall be included.
[SWS_Dem_00984] dIf the counter ‘Cycles since last failed’ is mapped to an ex-
tended data record (DemInternalDataElement set to DEM_CYCLES_SINCE_-
LAST_FAILED), it shall be available per ‘event related data’ record.c(RS_Diag_04190)
[SWS_Dem_00771] dIf internal debounce counter reach DemDebounceCoun-
terFailedThreshold (latest UDS status bit 0 changes from 0 to 1) and this
counter is not stored in event memory and there are available event memory en-
try, new entry shall be allocated and the counter shall be started and initialized to
zero.c()
counter is stored in event memory the counter shall initialized to zero.c(RS_Diag_-
04068)
[SWS_Dem_00773] dIn case the counter is available and started, it shall be incre-
mented at the end of the referenced operation cycle (refer to DemOperationCy-
cleRef).c(RS_Diag_04178)
[SWS_Dem_00774] dThe counter shall be implemented as one byte. If any count
operation occurs which would cause a counter to roll over past 0xFF then the count
value shall instead be maintained at 0xFF.c(RS_Diag_04068)
7.6.1.2 Cyles since first failed
The counter Cycles since first failed is representing the number of operation cycles
since the DTC fault detection counter first reached its maximum value of +127 (since
DTC information was last cleared). All operation cycles, including those in which the
test has not been completed shall be included.
[SWS_Dem_00775] dIf the counter ‘Cycles since first failed’ is mapped to an ex-
tended data record (DemInternalDataElement set to DEM_CYCLES_SINCE_-
FIRST_FAILED), it shall be available per ‘event related data’ record.c(RS_Diag_-
04190)
zero.c(RS_Diag_04125)
cleRef).c()

AUTOSAR CP R20-11

7.6.1.3 Failed cycles
The counter Failed cycles is representing the number of operation cycles during which
the DTC fault detection counter reached its maximum value of +127 (since DTC infor-
mation was last cleared)
[SWS_Dem_00779] dIf the counter ‘Failed cycles’ is mapped to an extended data
record (DemInternalDataElement set to DEM_FAILED_CYCLES), it shall be avail-
able per ‘event related data’ record.c(RS_Diag_04068, RS_Diag_04189, RS_Diag_-
04190)
zero.c(RS_Diag_04105)
cleRef) in case the UDS status bit 1 is set to 1.c(RS_Diag_04105)
7.7 Event memory description

The ‘event memory’ is defined as a set of event records located in a dedicated mem-
ory block. The event record includes at least the UDS status and the event related
data.
[SWS_Dem_00010] dThe Dem module shall support the primary event memory.c()
[SWS_Dem_00548] dIf configured (refer to [SWS_Dem_00162]) the Dem module
shall support the additional event memories (user defined, mirror, permanent).c()
[SWS_Dem_01247] dConfigured via the container DemEventMemorySet, the Dem
supports multiple independent event memories. Each API call with DemClient as
parameter, shall be applicable only on the configured event memory (primary, mirror
or user defined) for this client.c(RS_Diag_04164)

AUTOSAR CP R20-11
[SWS_Dem_CONSTR_06118] Unique DTC values within a single event memory

dThe DemDtcValue shall be unique within all DTCs referencing the same event mem-
ory.c()
[SWS_Dem_CONSTR_06119] Unique OBD DTC values within an ECU dThe
DemDtcValue shall be unique within all DTCs referencing the same event memory.c()
The Dem can be configured to support more than one DemEventMemorySet. This
allows the Dem to store DTCs and event related data of more than one diagnostic
server. Each DemEventMemorySet is treated as independent entity. Changes in one
DemEventMemorySet affect only the local addressed DemEventMemorySet and are
not visible in another DemEventMemorySet.
As a result of this, operations such as ClearDTC on one event memory only effects
the addressed DemEventMemorySet. In other words, a ClearDTC operation has no
impact on DTCs or event related data in a different DemEventMemorySet.
[SWS_Dem_01217] dIn order to calculate the user defined memory ID from Dem_-
DTCOriginType, the Dem shall substract a value of 0x0100 from the obtained value
if the value is in the range of [0x0100, 0x01FF].c(RS_Diag_04214)
The size of the different event memories is configurable in the Dem configuration.
[SWS_Dem_00162] dThe Dem shall provide configuration parameters to adapt the
fault memory size to the ECU memory space available (refer to configuration parame-
ters DemMaxNumberEventEntryPrimary, DemMaxNumberEventEntryMirror or
DemMaxNumberEventEntryUserDefined).c()
[SWS_Dem_00329] dFor storing to non-volatile memory the Dem shall use the
NVRAM Manager.c(RS_Diag_04077)
The following figure shows an example of a logical Dem event memory layout.

AUTOSAR CP R20-11
Event Memory
primary mirror ...
Event Memory Layout
event counter
Example
st
1 entry 2nd entry ... nth entry
1st entry EventId 2nd entry nth entry
Freeze Frame 1 Freeze Frame 2* Extended Data

milage milage condition byte
abs. time abs. time frequency counter 1 Refer to 1st Refer to 1st
FF Data 1 FF Data 1 : entry entry
:
FF Data 2 FF Data 2 but: ... but:
: : ev. rel. data o ev. rel. data p
: :
FF Data m FF Data m
* only at the second appearance, up to the maximal number of freeze frames

1 frequency (occurrence) counter only increments
Figure 7.13: Example of a logical Dem event memory layout
If there are limitations of the memory size, it is necessary to provide overflow indication
of the event memory and a displacement strategy (refer to chapter 7.7.2).
7.7.1 Event status management
The ‘Event Status Management’ is the Dem’s ability to record and retain events, event
status and associated data.
[SWS_Dem_00330] dThe Dem module shall provide the capability to report the status
of an event allowing a diagnostic monitor to inform the Dem about the result of the
internal diagnostic test (refer to Dem_SetEventStatus).c(RS_Diag_04067)
[SWS_Dem_01333] dThe API Dem_SetEventStatusWithMonitorData shall have
the same functionality as Dem_SetEventStatus with the only difference that it pro-
vides further parameters with data to store in an event related data.c()
The monitors, which are located in the application, should call the function (Dem_-
SetEventStatus) to report an event status as soon as a new test result is available.
This will be done independently of the current state of the Dem module (refer to Figure
7.14).

AUTOSAR CP R20-11
Figure 7.14: Example for using Dem_SetEventStatus
[SWS_Dem_01352] Setting event failed with synchronous freeze frame process-

ing dIf Dem_SetEventFailedWithSyncFreezeFrame is called, the Dem shall pro-
cess the event status in the same way a call of Dem_SetEventStatus with DEM_-
EVENT_STATUS_FAILED.c(RS_Ids_00400)
Note: An event reported with Dem_SetEventFailedWithSyncFreezeFrame is not
debounced and the TestFailed Bit will be set to 1 if other conditions such as enabled
conditions are not blocking the event status from being updated.
[SWS_Dem_01353] Synchronous snapshot record processing dIf Dem_-
SetEventFailedWithSyncFreezeFrame is called, the Dem shall capture the UDS
snapshot record data synchronous within the call of this function.c(RS_Ids_00400)
Legislated freezeframes or J1939 freeze frames are not affected by SWS_Dem_01353.
[SWS_Dem_01354] Only C-Callout data capturing for synchronous snapshot
record processing dFor each DemEventParameter with DemEventReporting-
Type set to IMMEDIATE_FAIL_AND_SYNCHRONOUS_PROCESSING, the DemFreeze-
FrameClass referenced from the event DTC, shall have only DemDidClass with
DemDataElementClass referencing a DemExternalCSDataElementClass that
has DemDataElementUsePort set to false.c(RS_Ids_00400)
[SWS_Dem_01355]{DRAFT} Optional callback after synchronous snapshot
record processing dIf DemEventReportingType is set to IMMEDIATE_FAIL_-
AND_SYNCHRONOUS_PROCESSING, the Dem shall call the configured callback Dem_-
CallbackEventSyncStorageProcessed when the Dem has processed the Dem_-
SetEventFailedWithSyncFreezeFrame call and is ready to receive the next call
of Dem_SetEventFailedWithSyncFreezeFrame for that event.c(RS_Ids_00400)
[SWS_Dem_01356]{DRAFT} CallbackEventSyncStorageProcessed only for syn-
chronous reporting event dThe Dem_CallbackEventSyncStorageProcessed
shall be only configured for events that have DemEventReportingType set to IM-
MEDIATE_FAIL_AND_SYNCHRONOUS_PROCESSING.c(RS_Ids_00400)

AUTOSAR CP R20-11
[SWS_Dem_00331] dThe Dem module shall provide the capability to reset the failed
status of an event without reporting a passed result (refer to Dem_ResetEventSta-
tus).c(RS_Diag_04179)
Note: Dem_ResetEventStatus does not mean an event status report (like done by
Dem_SetEventStatus). After the call, the monitor status is not qualified or tested.
Monitors will use the function Dem_ResetEventStatus in order to deactivate limp
home and switch back to normal operation. At this point in time, the monitor has
typically not been OK-tested and therefore Dem_SetEventStatus with tested and
passed cannot be used.
[SWS_Dem_00187] Behavior of Dem_ResetEventStatus dThe function Dem_Re-
setEventStatus shall set the event status bit 0 (TestFailed) to 0 and reset the
Dem-internal debounce algorithm to initial values if configured. The Dem shall execute
this action asynchronously at a later point in time.c(RS_Diag_04067)
A later point in time means that the exact moment is implementation specific. This
could be the next main function and after Dem_ResetEventStatus has returned.
Also a possible call of the status change callback is triggered asynchronously.
Note: The function Dem_ResetEventStatus does not change the monitor status and
UDS status bit 6 and does not clear the pre-stored freeze frame.
[SWS_Dem_00638] dThe function Dem_ResetEventStatus shall return
E_NOT_OK, if the event was already tested this operation cycle (UDS status
bit 6 is set to 0).c(RS_Diag_04067)
[SWS_Dem_00051] dIf the API Dem_GetEventUdsStatus is called, the Dem shall
provide the current event status byte of a specific event.c(RS_Diag_04067)
Note: The function Dem_GetEventUdsStatus is provided to be used by SW-Cs or
other BSW modules (e.g. FiM) on event-level. The Dcm uses the function Dem_-
GetStatusOfDTC on DTC-level instead.
[SWS_Dem_00844] dThe Dem shall provide a function Dem_GetDebouncin-
gOfEvent () that reports the debounce status of an event. The outparameter ‘De-
bouncingState’ returns the debouncing incl. intermediate states. One particular OBD
specific bit shall support the DTR update trigger if test is complete and debouncing is
at its limit while the enable and storage conditions are met.c(RS_Diag_04068)
The Dem supports a configuration per event to forbid to reset the event in the same
operation cycle.
[SWS_Dem_01208] dIf the configuration parameter DemEventRecoverableIn-
SameOperationCycle is set to FALSE, a report of PASSED (directly via Dem_-
SetEventStatus or indirectly after Debouncing) will be ignored if the event status
byte has the “TestFailedThisOperationCycle” flag is set to 1.c(RS_Diag_04151)
Note: Debouncing is done independently from the value DemEventRecoverableIn-
SameOperationCycle. The FDC can reach -128 independently from the setting of
DemEventRecoverableInSameOperationCycle.

AUTOSAR CP R20-11
[SWS_Dem_01209] dThe Dem shall perform the configured debouncing independently

from the setting of the configuration parameter DemEventRecoverableInSameOp-
erationCycle. I.e. if DemEventRecoverableInSameOperationCycle is set to
FALSE and the monitor for this event reports PREPASSED the Dem shall still process
the debouncing (e.g. decrement the counter).c(RS_Diag_04151)
[SWS_Dem_01250] dIf DemMultiEventTriggering is configured and any of the
APIs:
is called with an EventId that is referenced by DemMultiEventTriggeringMas-
terEventRef of a DemMultiEventTriggering, for each DemMultiEventTrig-
geringSlaveEventRef of this DemMultiEventTriggering the Dem shall trigger
the same API calls with identical parameters only the EventId parameter shall be
replaced with the event referenced from DemMultiEventTriggeringSlaveEven-
tRef.c(RS_Diag_04165)
[SWS_Dem_01339] dThe Dem shall not support calls of
with an EventId that is referenced by any of the DemMultiEventTrigger-
ingSlaveEventRef in container DemMultiEventTriggering or by DemStor-
ageConditionReplacementEventRef. These events are exclusively used for in-
ternal triggering. The behavior of the Dem is undefined if any of those APIs are called
in this situation.c(RS_Diag_04165)

AUTOSAR CP R20-11
7.7.1.1 Status bit support
[SWS_Dem_00006] dThe Dem module shall by default implement the current set of
all UDS status bits according to the definition in ISO-14229-1[2] for each diagnostic
event.c(RS_Diag_04067)
Note: For this specification, the UDS status byte of ISO-14229-1[2] for events is
represented by the Dem data type Dem_UdsStatusByteType (defined in chapter
8.6.1.21). If particular UDS status bits do not need to be supported (refer also to
[SWS_Dem_00060]), such optimizations or limitations may be implemented vendor-
specific.
[SWS_Dem_01276] dIf the API Dem_GetEventUdsStatus is called, the event from
the parameter EventId exists and is available, the Dem shall copy the UDS status
byte into the out parameter UdsStatusByte and return E_OK.c(RS_Diag_04067)
[SWS_Dem_01277] dIf the API Dem_GetEventUdsStatus is called, the event from
the parameter EventId does not exists or is unavailable, the Dem shall return
E_NOT_OK.c(RS_Diag_04067)
7.7.1.2 Monitor status and UDS status update
Status bit processing is an essential part of the Dem functionality. SWCs or BSW mod-
ules frequently report monitor results via the API Dem_SetEventStatus. A call of
these functions will trigger the status bit processing of the Dem.
[SWS_Dem_01278] dThe Dem shall provide a monitor status per event to store current
monitor state information. The monitor status contains the information as defined in
Dem_MonitorStatusType.c(RS_Diag_04067)
[SWS_Dem_01279] dThe Dem shall perform the counter based event debouncing syn-
chronously within the context of the calling Dem_SetEventStatus function.c(RS_-
Diag_04068)
[SWS_Dem_01280] dUpon call of Dem_SetEventStatus and after debouncing, the
Dem shall process the monitor status in the same manner as the UDS status:
• Bit0 (TestFailed) according to [SWS_Dem_00386]
• Bit1 (TestNotCompleteThisOperationCycle) according to [SWS_Dem_00394].
The monitor status byte processing shall be done synchronously within the context of
the calling Dem_SetEventStatus function.c(RS_Diag_04067)

AUTOSAR CP R20-11
[SWS_Dem_01281] dIf the parameter DemGeneralCallbackMonitorSta-

tusChangedFnc is configured, the Dem shall call this configured C function with the
signature of <Module>_DemTriggerOnMonitorStatus.c(RS_Diag_04067)
[SWS_Dem_01282] dUpon processing the monitor status, the Dem shall call the mon-
itor status changed callback functions:
• <Module>_DemTriggerOnMonitorStatus
whenever the monitor status has changed.c(RS_Diag_04067)
[SWS_Dem_01283] dUpon processing the monitor status for reported event with De-
mEventKind = DEM_EVENT_KIND_SWC, the Dem shall call the monitor status changed
callback C/S Interface CallbackMonitorStatusChange whenever the monitor sta-
tus has changed and a C/S interface is configured for this event.c(RS_Diag_04067)
[SWS_Dem_CONSTR_06120] Dependency for DemGeneralCallbackMonitorSta-
tusChangedFnc dThe DemGeneralCallbackMonitorStatusChangedFnc shall
only be present if DemGeneralInterfaceSupport is set to TRUE."c()
Limitation: The usage of monitorStatusChange via RTE is limited to SWC-monitorings.
All basic software monitorings cannot be covered with this callback via RTE. To get com-
plete statusChange information of all monitorings in a SW-C, the eventStatusChange
callbacks should be used.
The CallbackMonitorStatusChange and GeneralCallbackMonitorSta-
tusChanged via RTE is furthermore limited to monitorings, which are exclusively
changing its status in known contexts. E.g. if a monitor status is changed from CDD
(e.g. Dem_SetEventAvailable via C-function call), the monitor status change call-
back via RTE must not be used.
Rational: AUTOSAR RTE requires that calls from a BSW to a SW-C via RTE are done
in a known call context. For the synchronous monitor status changed callbacks, this
is only possible for events reported from a SW-C. For events reported from a BSW
module it is not possible to provide the calling context to the RTE. As a result of this, the
Dem provides the C/S interface CallbackMonitorStatusChange only for events that are
reported from a SW-C. For events reported from BSW modules, no such C/S interface
is provided. Furthermore, the interface GeneralCallbackMonitorStatusChanged is not
provided as C/S via RTE, as this callback could only be called for events reported from
a SW-C and not for events reported from BSW modules. This would obviously lead to
confusion.
If it is required to have a general synchronous reaction in a SW-C on monitor status
changed callbacks, the synchronous reaction could be handled within the scope of
a CDD using <Module>_DemGeneralTriggerOnMonitorStatus or <Module>_-
DemTriggerOnMonitorStatus.
[SWS_Dem_CONSTR_6116] Limited use of monitor status change callbacks to
events reported from SW-Cs only dIf Dem_SetEventAvailable is called from a
Cdd or BSW module, the corresponding monitor status changed callback can only be
used as C-function, but not via RTE interface.c()

AUTOSAR CP R20-11
[SWS_Dem_01284] dWhen processing a clear DTC command (e.g. via Dem_-

ClearDTC), the Dem shall set the monitor status assigned to the cleared DTCs to
0x02.c(RS_Diag_04067)
[SWS_Dem_01285] dThe Dem shall process the UDS status asynchronously. This
means it is calculated outside the context of the calling Dem_SetEventStatus func-
tion.c(RS_Diag_04067)
[SWS_Dem_01286] dIf the API Dem_SetEventStatus is called and the Dem has
synchronously processed the reported monitor status according to [SWS_Dem_01280]
and the corresponding UDS status (see [SWS_Dem_01285]) cannot be processed, the
Dem shall report the runtime error DEM_E_UDS_STATUS_PROCESSING_FAILED.c
(RS_Diag_04067)
SW-C or BSW «module» Dem processing
Dem
SW-C or BSW Task Dem main function
Dem_SetEventStatus()

Ask for queued events()
Process UDS status()
Figure 7.15: Synchronous and asynchronous event processing
Note: Refer to chapter 7.7.2 for a detailed description about the event memory man-
agement.
[SWS_Dem_01064] dThe mirror memory is not relevant for calculation of the UDS
status.c(RS_Diag_04131)
[SWS_Dem_01287] dIf the API Dem_GetMonitorStatus is called, the Dem shall
copy the current monitor status into the out parameter MonitorStatus and return E_OK.c
(RS_Diag_04067)
[SWS_Dem_01288] dIf the API Dem_GetMonitorStatus is called with an invalid
EventId the Dem shall return E_NOT_OK.c()
[SWS_Dem_01326] dThe monitor status shall be initialized within Dem_Init. Any call
to Dem_GetMonitorStatus shall return E_NOT_OK if the monitor status is uninitial-
ized.c(RS_Diag_04031)

AUTOSAR CP R20-11
7.7.1.3 Status bit transitions
This section describes the behavior of the individual status bits of the UDS status
byte (refer to ISO-14229-1[2], UDS status byte - bit transitions).
[SWS_Dem_00385] dAfter a clear command has been applied to a specific DTC the
Dem module shall set the UDS status byte to 0x50 (readiness bits 4 and 6 set to 1,
and all others are set to zero).c(RS_Diag_04067)
For details see chapter 7.7.2.2.
Note: The value of the UDS status byte after a clear command has been applied
represents the delivery status (initial state) of this byte as well.
[SWS_Dem_00386] dThe Dem module shall implement the status bit transitions for
UDS status bit 0.c(RS_Diag_04067)
For details see figure 7.16.
[SWS_Dem_00387] dThe Dem module shall support the configuration parameter
DemStatusBitStorageTestFailed (refer to DemGeneral) to determine whether
the information for UDS status bit 0 is stored volatile or non-volatile.c(RS_Diag_-
04067)
[SWS_Dem_00388] dIf the configuration parameter DemStatusBitStorageTest-
Failed is set to False, the Dem module shall not retain the information for UDS sta-
tus bit 0 over power cycles (volatile)c(RS_Diag_04067)
[SWS_Dem_CONSTR_6113] Configuration of the test failed status bit storage
dFor WWH-OBD ECU the DemStatusBitStorageTestFailed shall be set to True.c()
[SWS_Dem_00525] dIf the configuration parameter DemStatusBitStorageTest-
Failed is set to True, the Dem module shall retain the information for UDS status
bit 0 over power cycles (non-volatile).c(RS_Diag_04067)
Dem_SetEventStatus
Dem_SetEventStatus [EventStatus =
[EventStatus = DEM_EVENT_STATUS_FAILED]
DEM_EVENT_STATUS_PASSED] Dem_SetEventStatus[EventStatus = DEM_EVENT_STATUS_PASSED] OR
Dem_ResetEventStatus[(OperationCycleId == DemOperationCycleRef)] OR
Dem_ClearDTC
Initial Bit 0 TestFailed = TestFailed =

state FALSE TRUE
Dem_SetEventStatus[EventStatus = DEM_EVENT_STATUS_FAILED]
Figure 7.16: UDS status bit 0 TestFailed logic
[SWS_Dem_00389] dThe Dem module shall implement the status bit transition for UDS
status bit 1.c(RS_Diag_04067)
Note: The information for event status bit 1 (TestFailedThisOperationCycle) is non-
volatile, if the PendingDTC bit is used (refer to [SWS_Dem_00006]) or if the Dem mod-
ule supports operation cycles over power cycles (refer to DemOperationCycleSta-
tusStorage).

AUTOSAR CP R20-11
Dem_SetEventStatus Dem_SetEventStatus
[EventStatus = [EventStatus =
DEM_EVENT_STATUS_PASSED] DEM_EVENT_STATUS_{FAILED|PASSED}]
Dem_RestartOperationCycle [(OperationCycleId == DemOperationCycleRef)] OR
Dem_ClearDTC
Initial Bit 1 TestFailed TestFailed

state ThisOperationCycle = ThisOperationCycle =
FALSE TRUE
Figure 7.17: UDS status bit 1 TestFailedThisOperationCycle logic
[SWS_Dem_01183] dThe information for UDS status bit 2 needs to be stored
non-volatilec()
Dem_SetEventStatus
[EventStatus =
Dem_SetEventStatus DEM_EVENT_STATUS_FAILED]
[EventStatus = Dem_RestartOperationCycle[(OperationCycleId == DemOperationCycleRef) &&
DEM_EVENT_STATUS_PASSED] (TestFailedThisOperationCycle == 0) AND
(TestNotCompletedThisOperationCycle == 0)] OR
Dem_ClearDTC OR
{FaultRecordOverwritten}
Initial Bit 2 PendingDTC = PendingDTC =
state FALSE TRUE
Dem_SetEventStatus[EventSatus = DEM_EVENT_STATUS_FAILED]
Figure 7.18: UDS status bit 2 PendingDTC logic
Note: The information for event status bit 3 (ConfirmedDTC) is non-volatile (but it is
also calculable based on the respective event memory entry).
Dem_SetOperationCycleState
[(OperationCycleId == DemOperationCycleRef) &&
(testFailedThisOperationCycle == 1) &&
(failure counter+1 < DemEventConfirmationThreshold)]
/failure counter++
Dem_RestartOperationCycle[(OperationCycleId == DemOperationCycleRef) && {AgingCriteriaFulfilled}] OR

{FaultRecordOverwritten} OR
Dem_ClearDTC
Initial Bit 3 ConfirmedDTC = ConfirmedDTC =

state FALSE TRUE
/failure counter=0
Dem_SetEventStatus[(EventStatus = DEM_EVENT_STATUS_FAILED) &&

(testFailedThisOperationCycle == 0) && ((failure counter+1) >= DemEventConfirmationThreshold)]
/failure counter = 0
Dem_RestartOperationCycle
[(OperationCycleId == DemOperationCycleRef) &&
(testFailedThisOperationCycle == 0) &&
(testNotCompleteThisOperationCycle == 0)]
/failure counter = 0
Figure 7.19: UDS status bit 3 ConfirmedDTC logic
Note: The “AgingCriteriaFulfilled” condition is specified by [SWS_Dem_00498]. The

“FaultRecordOverwritten” condition is specified by [SWS_Dem_00409].

AUTOSAR CP R20-11
Note: The information for event status bit 4 (TestNotCompletedSinceLastClear) is non-
volatile.
Dem_SetEventStatus
[EventStatus =
DEM_EVENT_STATUS_{FAILED|PASSED}]
Dem_ClearDTC
Initial Bit 4 TestNotCompleted TestNotCompleted

state SinceLastClear = SinceLastClear =
TRUE FALSE
Dem_SetEventStatus[EventStatus = DEM_EVENT_STATUS_{FAILED|PASSED}]
Figure 7.20: UDS status bit 4 TestNotCompletedSinceLastClear logic
Note: The information for UDS status bit 5 (TestFailedSinceLastClear) is non-volatile.
Dem_SetEventStatus Dem_SetEventStatus
[EventStatus = [EventStatus =
DEM_EVENT_STATUS_PASSED] DEM_EVENT_STATUS_{FAILED|PASSED}]
{AgingCriteriaFulfilled} (optional) OR
{FaultRecordOverwritten} (optional) OR
Dem_ClearDTC
Initial Bit 5 TestFailed TestFailed

state SinceLastClear = SinceLastClear =
FALSE TRUE
Figure 7.21: UDS status bit 5 TestFailedSinceLastClear logic
Note: The relevance of “AgingCriteriaFulfilled” condition (specified by

[SWS_Dem_00498]) and “FaultRecordOverwritten” condition (specified by
[SWS_Dem_00409]) depends on the configuration parameter DemStatus-
BitHandlingTestFailedSinceLastClear (refer to DemGeneral).
Note: The information for UDS status bit 6 (TestNotCompleteThisOperationCy-
cle) needs to be stored non-volatile, if the PendingDTC bit is used (refer to
[SWS_Dem_00006]), or if the Dem module supports operation cycles over power cy-
cles (refer to DemOperationCycleStatusStorage).

AUTOSAR CP R20-11
Dem_SetEventStatus
[EventStatus =
DEM_EVENT_STATUS_{FAILED|PASSED}]
Dem_RestartOperationCycle[(OperationCycleId == DemOperationCycleRef)] OR
Dem_ClearDTC
Initial Bit 6 TestNotCompleted TestNotCompleted

state ThisOperationCycle = ThisOperationCycle =
TRUE FALSE
Dem_SetEventStatus[EventStatus = DEM_EVENT_STATUS_{FAILED|PASSED}]
Figure 7.22: UDS status bit 6 TestNotCompleteThisOperationCycle logic
[SWS_Dem_00395] dThe Dem module shall implement the status bit transition for
UDS status bit 7 (WarningIndicatorRequested).c(RS_Diag_04067)
Note: The information for UDS status bit 7 (WarningIndicatorRequested) may be
volatile (because it is calculated based on the assigned warning indicator states).
(Dem_ClearDTC OR
{WarningIndicatorOffCriteriaFulfilled} )
AND {warning indicator not requested on due to Latched failsafe for particular DTC}
WarningIndicator WarningIndicator
Initial Bit 7
Requested = Requested =
state
FALSE TRUE
Dem_SetEventStatus[EventStatus = DEM_EVENT_STATUS_FAILED] AND

{WarningIndicatorOnCriteriaFulfilled}
Figure 7.23: UDS status bit 7 WarningIndicatorRequested logic
Note: The “WarningIndicatorOffCriteriaFulfilled” and the “WarningIndicatorOnCriteri-

aFulfilled” condition are specified in chapter 7.7.9.
Note: ISO-14229-1[2] additionally specifies “warning indicator not requested on due to
latched failsafe for particular DTC” as condition. This has to be ensured by the monitor.
7.7.1.4 Active/Passive status
If an event gets qualified as failed, it becomes active. If the event gets qualified as
passed, it becomes passive. This status can be derived from the event status byte.
As the UDS status bit 0 is configurable in persistent storage ability (refer to con-
figuration parameter DemStatusBitStorageTestFailed), also the meaning of ac-
tive/passive is influenced:
• If the TestFailed bit is stored non-volatile, “event active” equals to TestFailed = 1
and “event passive” equals to TestFailed = 0.
• If the TestFailed bit is only stored volatile, additionally the information, if the event
was already tested/reported this power cycle, is required. As long, as this infor-
mation is not present, the active/passive status is undefined.
Note: There are also ECUs, where all monitors run during startup phase. In this case,
it is also sufficient, to map the active/passive status directly to the TestFailed bit.

AUTOSAR CP R20-11
7.7.1.5 Notification of status bit changes
The Dem module can inform the monitor and/or other components about the status
change of the event or DTC.
Note: For asynchronous event processing, the Dem module will trigger the respective
notification functions twice per event/DTC qualification.
[SWS_Dem_00016] dThe Dem module shall trigger the event-specific callback-function
EventUdsStatusChanged on each UDS status change.c(RS_Diag_04067)
Note: The configuration container DemCallbackEventUdsStatusChanged (in De-
mEventParameter) is used to specify one or more ports/c-callbacks per event.
Note: The respective callback-functions for FiM are specified in chapter 7.10.
DemEventParameter:
EcucParamConfContainerDef DemCallbackEventUdsStatusChanged: DemCallbackEventUdsStatusChangedFnc:
lowerMultiplicity = 1 lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = * A upperMultiplicity = 1
DemCallbackMonitorStatusChanged: DemCallbackMonitorStatusChangedFnc:
Figure 7.24: EventStatusChanged callback configuration
[SWS_Dem_00284] dThe Dem module shall trigger the callback function configured in
DemCallbackDTCStatusChanged on every DemDTC status change.c(SRS_BSW_-
00457)
[SWS_Dem_00986] dThe Dem module shall trigger the callback function configured in
DemCallbackOBDDTCStatusChanged on every DemObdDTC status change.c(SRS_-
BSW_00457)
[SWS_Dem_00987] dThe Dem module shall trigger the callback function configured
in DemCallbackJ1939DTCStatusChanged on every J1939 DTC status change.c
(SRS_BSW_00457)
Note: The result of EventUdsStatusChanged may only be different to the result of
DTCStatusChanged in case of event combination (refer to chapter 7.7.5).
Note: The configuration containers DemCallbackDTCStatusChanged,DemCall-
backOBDDTCStatusChanged and DemCallbackJ1939DTCStatusChanged are
used to specify one or more ports/c-callbacks for the Dem module globally.ly.

AUTOSAR CP R20-11
DemCallbackDTCStatusChanged: DemCallbackDTCStatusChangedFnc:
upperMultiplicity = 1 +parameter EcucFunctionNameDef
upperMultiplicity = * upperMultiplicity = 1
+subContainer
DemGeneralOBD: DemCallbackOBDDTCStatusChanged: DemCallbackDTCStatusChangedFnc:

EcucParamConfContainerDef +subContainer EcucParamConfContainerDef +parameter EcucFunctionNameDef
upperMultiplicity = 1 lowerMultiplicity = 0 lowerMultiplicity = 0

lowerMultiplicity = 0 upperMultiplicity = * upperMultiplicity = 1
+subContainer
DemGeneralJ1939: DemCallbackJ1939DTCStatusChanged: DemCallbackDTCStatusChangedFnc:


Figure 7.25: DTCStatusChanged callback configuration
7.7.2 Event memory management
The event memory management defines as the process of adding, updating and
removing event memory entries in and out of the Dem module. The Dem mod-
ule determines if the event memory entry is new or currently exists in the event
memory.
Note: The requirements in this section do not determine the software implementation
but describe the behavior of the ECU towards requests from the test tool.
[SWS_Dem_01199] dThe Dem module shall support the configuration parameter Dem-
MemoryDestinationRef to define the destination memory/memories for individual
DTCs.c()
When using the Dem interfaces, Dem_DTCOriginType selects the destination memo-
ries by evaluating the possible DemMemoryDestinationRef.
Note: OBD relevant DTCs can be stored in primary or user defined event memory.
[SWS_Dem_01063] dThe user defined memory shall have the same behavior as the
primary memory(event retention, event prioritization, aging, displacement).c(RS_-
Diag_04131)
Note: The mirror memory may have a different behaviour which is project specific and
is not described in this document.

AUTOSAR CP R20-11
[Dem_SetEventStatus( PREFAILED | PREPASSED | FAILED | PASSED ) or

Dem_SetEventStatus( PREFAILED | PREPASSED | FAILED | PASSED ) ]
[not fulfilled]
Check enable conditions
[fulfilled]
[PREFAILED or PREPASSED]
Process event debouncing

[FAILED] [PASSED]
Check for
[qualified as FAILED] event [qualified as PASSED]
qualification
TestFailed bit = 0,
TestFailed bit = 1,
TestNotCompleteThisOpCycle = 0;
TestFailedThisOpCycle = 1,
TestNotCompleteSince LastClear = 0,
TestNotCompleteThisOpCycle = 0;
TestNotCompleteSinceLastClear = 0, [not qualified]
TestFailedSinceLastClear = 1
Check validity
of storage
conditions
[fulfilled]
[not fulfilled]
Pending = 1
[Yes]
Confirmed Level
Confirmed = 1
Reached?
[No]
[DEM_TRIGGER_ON_CONFIRMED] DemEventMemory [DEM_TRIGGER_ON_PENDING]

EntryStorageTrigger?
[No] [No]
ConfirmedDTC changed PendingDTC changed
from 0 to 1? from 0 to 1?
[Yes]
[Yes]
Process event retention
[Not Fullfilled AND

DemResetConfirmedBitOnOverflow == True]
Check retention
result
[Fullfilled OR DemResetConfirmedBitOnOverflow == False]
[TRUE] Check [FALSE]

WarningIndicatorRequest bit = 1 WarningIndicatorOnCondition
Figure 7.26: General diagnostic event storage processing

AUTOSAR CP R20-11
7.7.2.1 Event retention
Event retention defines the ability of the Dem module to record and handle events
(DTCs), UDS status information and event related data (e.g. freeze frames, extended
data).
Check
Check if
event
event is
memory
already
[not stored] for free
stored
entry [memory full]
Process event
displacement
[memory entry available]
[stored]
Check
displacement
[old event memory entry removed] result
Event memory entry

storage
[new event memory entry not possible]
fullfilled not
fullfilled
Figure 7.27: General diagnostic event retention processing
There are several different strategies in the market when to allocate an event memory
entry. Therefore, the Dem module has the capability to configure the primary trigger
to allocate an event memory entry. Beside the primary trigger there might be sec-
ondary triggers (refer DemFreezeFrameRecordTrigger) mainly to update content
of event event memory (e.g. to have most recent update FreezeFrames).
[SWS_Dem_00783] dIf an event
1. gets qualified as failed (UDS status bit 0 changes from 0 to 1) and
2. the configuration parameter DemEventMemoryEntryStorageTrigger is set
to DEM_TRIGGER_ON_TEST_FAILED or DEM_TRIGGER_ON_FDC_THRESHOLD
(refer to DemPrimaryMemory or DemUserDefinedMemory) and
3. no event memory entry exist,
the Dem module shall try to allocate an event memory entry in its configured
event memory (refer to DemMemoryDestinationRef).c(RS_Diag_04105)

AUTOSAR CP R20-11

1. gets pending (UDS status bit 2 changes from 0 to 1) and
3. no event event memory is existing,
1. is pending (UDS status bit 2 is set to 1) and gets re-qualified as failed (UDS
status bit 0 changes from 0 to 1) and
3. no event memory entry is existing,
1. gets confirmed (UDS status bit 3 changes from 0 to 1) and
to DEM_TRIGGER_ON_CONFIRMED or DEM_TRIGGER_ON_TEST_FAILED or
DEM_TRIGGER_ON_FDC_THRESHOLD (refer to DemPrimaryMemory or De-
mUserDefinedMemory) and
1. is confirmed (UDS status bit 3 is set to 1) and gets re-qualified as failed (
UDS status bit 0 changes from 0 to 1) and
to DEM_TRIGGER_ON_CONFIRMED or DEM_TRIGGER_ON_TEST_FAILED or

AUTOSAR CP R20-11
DEM_TRIGGER_ON_FDC_THRESHOLD (refer to DemPrimaryMemory or De-

4. if DemResetConfirmedBitOnOverflow is set to false,
the Dem module shall try to allocate an event memory entry in its configured event
memory (refer to DemMemoryDestinationRef).c(RS_Diag_04105)
1. uses Dem-internal debouncing (either counterbased or timebased) and
2. the Dem-internal debounce counter is incremented and reaches DemCounter-
BasedFdcThresholdStorageValue or DemTimeBasedFdcThreshold-
StorageValue and
to DEM_TRIGGER_ON_FDC_THRESHOLD (refer to DemPrimaryMemory or De-
4. no event event memory exists,
Note: In case the event memory entry already exists, there might be other triggers
to update content of event memory entry(refer chapter 7.7.7 “Event related data”).
[SWS_Dem_CONSTR_06155] Dependency on DemTimeBasedFdcThreshold-
StorageValue dDemTimeBasedFdcThresholdStorageValue shall only be present
if DemFreezeFrameRecordTrigger is set to DEM_TRIGGER_ON_FDC_THRESHOLD
or DemExtendedDataRecordTrigger is set to DEM_TRIGGER_ON_FDC_THRESH-
OLD or DemEventMemoryEntryStorageTrigger is set to DEM_TRIGGER_ON_-
FDC_THRESHOLD (refer to DemPrimaryMemory or DemUserDefinedMemory).c()
7.7.2.2 Clearing event memory entries
The event memory entries of the Dem module can be cleared DTC-based via
various diagnostic services (e.g. service 0x14 ClearDiagnosticInformation or service
$04 Clear/Reset emission-related diagnostic information). Therefore, the Dem offers
separate APIs for different users:
• Dem_ClearDTC

AUTOSAR CP R20-11
• Dem_J1939DcmClearDTC (for J1939 to the J1939Dcm [7], refer to chapter

7.10.2).
[SWS_Dem_01203] dIf the Dem module is requested to clear diagnostic
information and the selected DTC is set to DTC group ‘all DTCs’ and
the selected DTCOrigin is set to DEM_DTC_ORIGIN_PRIMARY_MEMORY or
DEM_DTC_ORIGIN_USERDEFINED_MEMORY_<NAME>, the Dem shall reset all
event and DTC status bytes and clear event related data assigned to the requested
DTCOrigin.c(RS_Diag_04150, RS_Diag_04214)
[SWS_Dem_01205] dIf the Dem module is requested to clear diagnostic information
and the selected DTC is set to DTC group ‘all DTCs’ and the selected DTCOrigin is
set to DEM_DTC_ORIGIN_MIRROR_MEMORY, the Dem shall clear only the event entries
assigned to the mirror event memory. It does not affect UDS status.c(RS_Diag_04213)
[SWS_Dem_01206] dThe Dem shall call the callback DemClearEventAllowed only
if the selected DTCOrigin for the clear operation is the primary or user defined event
memory.c(RS_Diag_04150, RS_Diag_04213)
The clearing process can be started by different clients. Whenever one of these inter-
faces starts the clearing process, the Dem-internal clearing mechanism is locked until
the clear request is finished and the result is returned to the requesting user.
[SWS_Dem_01240] dIf DemClearDtcNotificationTime is configured to START,
the Dem shall inform the application about the start of a clear DTC operation. If the
DemClearDtcNotificationFnc is configured, the Dem shall shall call this config-
ured function otherwise the Dem shall call the R-Port ClearDtcNotification.c(RS_Diag_-
04185)
[SWS_Dem_01241] dIf DemClearDtcNotificationTime is configured to FINISH,
the Dem shall inform the application about the end of a clear DTC operation. The Dem
shall consider the configuration parameter DemClearDTCBehavior which defines the
clearing process of diagnostic information including clearing completion. If the Dem-
ClearDtcNotificationFnc is configured, the Dem shall call this configured function
otherwise the Dem shall call the R-Port ClearDtcNotification.c(RS_Diag_04185)
[SWS_Dem_00661] dIn case of multiple clients are requesting Dem_ClearDTC in par-
allel, the Dem shall internally process the different requests.c(RS_Diag_04194)
[SWS_Dem_00664] dIf the clear DTC process is started by one client and still
ongoing, then in case another client calls Dem_ClearDTC, the Dem shall return
DEM_PENDINGc()
[SWS_Dem_00670] dIf the configuration parameter DemClearDTCLimitation is
set to DEM_ONLY_CLEAR_ALL_DTCS, the APIs Dem_ClearDTC are called with a se-
lected DTC group different to DEM_DTC_GROUP_ALL_DTCS the Dem shall return DEM_-
WRONG_DTC.c(RS_Diag_04117)

AUTOSAR CP R20-11

and the configuration parameter DemClearDTCBehavior is set to DEM_CLRRESP_-
VOLATILE, the Dem module shall return E_OK after the volatile memory is cleared.c
(RS_Diag_04194)
NONVOLATILE_TRIGGER, the Dem module shall return E_OK after the volatile mem-
ory is cleared and clearing of the non-volatile memory is triggered.c(RS_Diag_04194)
NONVOLATILE_FINISH, the Dem module shall return E_OK after the volatile memory
and the non-volatile memory is cleared.c(RS_Diag_04194)
Note: The Dem implementation is responsible for consistency of the persistant data.
(See SWS_NvM_00698: Contents of RAM buffer passed to NvM_WriteBlock may not
change while the NvM processes the job). How to ensure data consistency (UDS sta-
tus byte, freeze frame data and all other related information) is implementation spe-
cific (depends on the implemented NvM strategy). Options include, but are not re-
stricted to, additional RAM mirrors and queuing of changes until the RAM area can be
modified again.
Note: If the Dcm module receives the return type DEM_CLEAR_OK of the API Dem_-
ClearDTC, the Dcm module sends the positive response (refer to [9]).
[SWS_Dem_01057] dIf the Dem module is requested to clear diagnostic in-
formation and the configuration parameter DemClearDTCBehavior is set
to DEM_CLRRESP_NONVOLATILE_FINISH, the Dem module shall return
DEM_CLEAR_MEMORY_ERROR if the clearing of the non-volatile memory fails.c()
[SWS_Dem_01202] Defintion of a failed clear DTC operation dIf the Dem module is
requested to clear diagnostic information, the Dem shall return DEM_CLEAR_FAILED:
• in case of clearing a single DTC at least one DemClearEventAllowed callback
assigned to the event of the DTC returns FALSE.
• in case of clearing a DTC group or all DTCs, the individual DTCs shall
be cleared like described in clearing single DTC. The resulting return value
shall be DEM_CLEAR_FAILED if the clearing of all individual DTCs returned
DEM_CLEAR_FAILED.
c(RS_Diag_04150, RS_Diag_04214)
[SWS_Dem_00573] dIf DemTriggerMonitorInitBeforeClearOk is set to TRUE,
the Dem_ClearDTC shall not return E_OK until the events intialization is triggered (call-
back function InitMonitorForEvent is called). If DemTriggerMonitorInitBe-
foreClearOk is set to FALSE, DEM_CLEAR_OK is not considering Event initialization
(InitMonitorForEvent).c(RS_Diag_04194)

AUTOSAR CP R20-11
This functionality is intended for some special events, which must never be cleared
from event memory within specific states, like for example special operation modes
of the ECU (e.g. assembly-, transport-, or flash-mode) or Dcm sessions (which can be
determined, using API Dcm_GetSesCtrType).
It is configurable per event (refer to DemCallbackClearEventAllowed), whether a
SW-C / BSW module shall be requested about the event-deletion allowance from this
callback function. One callback (representing a specific condition) can be assigned
per event. If multiple conditions apply, they need to be summarized by one callback
individually.
[SWS_Dem_00515] dThe Dem module shall call the callback DemClearEventAl-
lowed for each event it is configured for, before clearing this event.c(RS_Diag_04194)
[SWS_Dem_00667] dIf the DTC is not configured to use event combination, the out-
parameter Allowed of the callback DemClearEventAllowed returns “false” and the
return value is equal to E_OK, the Dem shall not clear the respective event memory
entry and Dem-internal data values.c(RS_Diag_04194)
[SWS_Dem_01295] dIf the DTC is configured to use event combination, if only one
DemClearEventAllowed callback has the out-parameter Allowed set to FALSE and
returns E_OK, the Dem shall not clear the event status, respective event memory
entry and Dem-internal data values.c(RS_Diag_04194)
[SWS_Dem_00668] dIf the out-parameter ‘Allowed’ of the callback DemClearEven-
tAllowed returns “false” and the configuration parameter DemClearEventAl-
lowedBehavior is set to DEM_NO_STATUS_BYTE_CHANGE, the related UDS status
byte shall not be modified.c(RS_Diag_04194)
[SWS_Dem_00669] dIf the out-parameter Allowed of the callback DemClearEven-
tAllowed returns “false” and the configuration parameter DemClearEventAl-
lowedBehavior is set to DEM_ONLY_THIS_CYCLE_AND_READINESS, the related
UDS status bits 1 (TestFailedThisOperationCycle), 4 (TestNotCompletedSinceLast-
Clear), 5 (TestFailedSinceLastClear), and 6 (TestNotCompletedThisOperationCycle)
shall be reset.c(RS_Diag_04194)
[SWS_Dem_01332] dIn case an event is partially cleared according to
[SWS_Dem_00669], the dependent functionality shall be handled as if the event
is not cleared at all. This means the callback function InitMonitorForEvent will
not be called and the FDC will remain unchanged in this situation.c(RS_Diag_04194)
[SWS_Dem_00516] dIf the return value of the callback DemClearEventAllowed is
equal to E_NOT_OK, the return value shall not be changed and event-deletion is al-
lowed.c(RS_Diag_04194)
The Dem supports events that are not assigned to any event memory. This is the
case, if the optional parameter DemDTCRef is not configured in DemEventParame-
ter. Events are cleared, when the event memory assigned to them is cleared. In
case there is no assigned event memory, these events would never be cleared. For

AUTOSAR CP R20-11
this case the Dem provides the configuration parameter DemClearEventsWithout-

DTCEventMemoryRef.
[SWS_Dem_01249] dIf the event memory referenced by DemClearEventsWith-
outDTCEventMemoryRef is cleared via any of the Dem_ClearDTC APIs, the Dem
shall clear also all the events that are not assigned to any event memory.c()
Note: Event displacement (mainly controlled by the event priority) and aging are not
influenced by this callback.
7.7.2.3 Event memory overflow indication
[SWS_Dem_00397] dThe Dem module shall indicate for each event memory if the
event memory is full and there was an attempt to store an additional event in this
event memory.c(RS_Diag_04093)
This overflow indication can be used to trigger further internal behavior of the Dem
module (e.g. displacement strategy). Furthermore, it can be used for additional fault
analysis in workshops.
[SWS_Dem_00398] dThe Dem module shall provide the API Dem_GetEventMemo-
ryOverflow to provide access to the event memory overflow indication status of
the respective event memory.c(RS_Diag_04093)
Note: This API can be used for vendor-specific Diagnostic Services or other vendor-
specific handling, and is provided to SW-Cs, as well as complex device drivers.
[SWS_Dem_00651] dThe Dem module shall provide the API Dem_GetNumberO-
fEventMemoryEntries to return the number of event memory entries currently
stored in the event memory.c(RS_Diag_04109)
Note: For the reported number all events are considered independently of the fault
confirmation.
[SWS_Dem_00399] dThe event memory overflow indication of the respective event
memory shall be reset, if all DTCs of this memory are deleted by Dem_ClearDTC.c
(RS_Diag_04093)
Note: In case of aging and deleting single DTCs, the overflow indication of the event
memory is not reset to keep this status information until the ECU receives an explicit
clear command of this specific event memory. The ECU itself should not change this
status information during normal operation (because it is used in workshops).
7.7.2.4 Event displacement
Event displacement means, that the most insignificant, already existing event mem-
ory entry is replaced by a new event memory entry, which needs to be stored.
During displacement, the most insignificant entry gets lost.

AUTOSAR CP R20-11
[SWS_Dem_00400] dIf the event retention want to allocate a new event memory
entry and there is no free event memory entry available, the Dem module shall
check according [SWS_Dem_00406] for allocated event memory entries to be
displaced by the new event memory entry.c(RS_Diag_04118)
Note: If the event memory size is configured to cover all possible events, no displace-
ment will occur.
[SWS_Dem_00401] dThe Dem module provides the configuration parameter De-
mEventDisplacementStrategy (refer to DemPrimaryMemory or DemUserDe-
finedMemory) defining whether the existing event memory entry can be dis-
placed or not.c(RS_Diag_04118)
[SWS_Dem_00402] dIf event displacement is disabled (DemEventDisplace-
mentStrategy in DemPrimaryMemory or DemUserDefinedMemory selects DEM_-
DISPLACEMENT_NONE), the Dem module shall not displace existing event memory
entries if the event memory is full.c(RS_Diag_04118)
[SWS_Dem_00406] dIf event displacement is enabled (DemEventDisplace-
mentStrategy selects DEM_DISPLACEMENT_FULL in DemPrimaryMemory or De-
mUserDefinedMemory or DEM_DISPLACEMENT_PRIO_OCC), the Dem module shall
perform the following sequence by combination of the different displacement criteria:
1. Priority (refer [SWS_Dem_00403])
2. Active/Passive status (configurable, only for DEM_DISPLACEMENT_FULL in Dem-
PrimaryMemory or DemUserDefinedMemory) (refer [SWS_Dem_00404])
3. Occurrence (refer [SWS_Dem_00405])
c(RS_Diag_04118)
Note: Priority needs to have Fuel system/Misfire over the rest (US/EU5) and Class A
before B1,B2, C (Euro VI).
[SWS_Dem_00403] dIf displacement strategy is DEM_DISPLACEMENT_FULL or
DEM_DISPLACEMENT_PRIO_OCC (refer to DemPrimaryMemory or DemUserDe-
finedMemory), the Dem module shall displace lower prioritized events by higher pri-
oritized events.c(RS_Diag_04118)
[SWS_Dem_00404] dIf displacement strategy is DEM_DISPLACEMENT_FULL(refer to
DemPrimaryMemory or DemUserDefinedMemory), the Dem module shall displace
passive events preferably.c(RS_Diag_04118)
[SWS_Dem_00405] dIf displacement strategy is DEM_DISPLACEMENT_FULL or
DEM_DISPLACEMENT_PRIO_OCC (refer to DemPrimaryMemory or DemUserDe-
finedMemory), the Dem module shall displace older stored events in the

AUTOSAR CP R20-11
chronological order prior to newer stored events (refer [SWS_Dem_00412] and

[SWS_Dem_00787]).c(RS_Diag_04118)
Search entries with lowest

priority
Priority of reported
event > priority of
Yes found entries?
( 12 3

'.1'' 0 ** (45
NO

! "#"
$ %&
'()**+ %&
,- ./
Found entries with

lowest priority left?
Yes
Priority of reported event

>= pririty of found entries
Yes
Search passive entries of

found entries
Priority of reported No
Passive memory No
/.(
event > priority of
entries found? )0
found entries?
No
Yes
Displace oldest found entry Yes

with reported event
Displace no entry
New event memory

Old event memory entry entry not possible
removed
Figure 7.28: Combined displacement criteria processing
[SWS_Dem_00407] dIf no event memory entry for displacement was identified,

the Dem module shall discard the storage request.c(RS_Diag_04118)

AUTOSAR CP R20-11
[SWS_Dem_00692] dIf an event is reported and an event memory entry with the
same priority exists and the existing event is not tested in this operation cycle
(TestNotCompletedThisOperationCycle bit == 1), the Dem shall displace the existing
event with the reported event.c(RS_Diag_04118, RS_Diag_04071)
[SWS_Dem_00693] dIf an event is reported and an event memory entry with the
same priority exists and the existing event is tested in this operation cycle (Test-
NotCompletedThisOperationCycle bit == 0), the Dem shall discard the reported event.c
(RS_Diag_04178)
[SWS_Dem_00695] dIf the configuration parameter DemOBDEventDisplacement is
set to TRUE all emission related events with the following conditions shall not be con-
sidered during the displacement mechanism and shall not displaced from error mem-
ory:
Eventold is emission related
AND
(Eventold triggers MIL indicator
OR (Eventold holds legislative Freeze Frame AND has equal or higher priority)
OR Pending-DTC==1)c(RS_Diag_04195)
[SWS_Dem_00696] dIf the configuration parameter DemOBDEventDisplacement
is set to FALSE the Dem module shall process the displacement without the OBD-
behavior.c(RS_Diag_04195)
[SWS_Dem_00408] dIf the event memory entry for displacement was identified,
the Dem module shall remove this event memory entry from the event memory.c
(RS_Diag_04118)
Note: This removed event memory entry should now used for the pending storage
trigger.
[SWS_Dem_00409] dIf an event memory entry was removed during displace-
ment, the Dem module shall reset the UDS status bit 2 and UDS status bit
3 to 0 if the configuration parameter DemResetConfirmedBitOnOverflow (refer to
DemGeneral) is set to true.c(RS_Diag_04067, RS_Diag_04118)
[SWS_Dem_01186] dIf an event memory entry was removed during displace-
ment, the UDS status bit 5 shall be reset to 0 in case of DemStatus-
BitHandlingTestFailedSinceLastClear is set to DEM_STATUS_BIT_AG-
ING_AND_DISPLACEMENT and DemResetConfirmedBitOnOverflow is set to
true.c(RS_Diag_04067, RS_Diag_04118)
7.7.2.5 Reporting order of event memory entries
[SWS_Dem_00410] dThe Dem module shall report DTCs in the chronological order of
the event storage (refer to API Dem_GetNextFilteredDTC), if:

AUTOSAR CP R20-11
• the DTCStatus parameter has the“pending DTC” or “confirmed DTC” bit or both
bits set
• all other bits of the DTCStatus parameter are set to false
• DemResetConfirmedBitOnOverflow is set to true
c(RS_Diag_04195)
Note: The chronological order is for reporting purposes only and does not imply explicit
memory structure, which is implementation specific.
Note: The reporting order may vary with the customer specific attributes used by the al-
gorithm for sorting the DTC records in case of not confirmed or pending. If the chrono-
logical order is required for further UDS status mask parameters, additional resources
may be necessary.
[SWS_Dem_00787] dIf an ‘stored event’ gets re-qualified as failed (UDS status bit
0 changes from 0 to 1) and a respective event memory entry exists, the Dem mod-
ule shall update the chronological order of the event storage by setting the particular
event as most recent event memory entry.c(RS_Diag_04195)
[SWS_Dem_00411] dIf the Dem module is requested to report in chronological order,
the most recent event memory entry shall be reported at first.c(RS_Diag_04195)
[SWS_Dem_00412] dIf a new event get stored in the event memory, the Dem shall
update the chronological order by setting the new event as most recent event mem-
ory entry.c(RS_Diag_04195, RS_Diag_04195)
Note: If there are multiple event memory entries stored at the same point in time
the chronological reporting order of these elements is undefined. It depends on the
implementation which of these entries is reported or displaced first..
7.7.3 Debouncing of diagnostic events
In general, an ECU may implement several types of debouncing improving signal qual-
ity. This section describes methods, how the Dem module shall implement basic algo-
rithms used for fault maturation (diagnostic event debouncing).
If the Dem module is configured to implement the debounce algorithm for a specific
event, one of the following debounce algorithms are to be performed Dem-internally.
Otherwise, the respective monitor implemented in a SW-C or BSW will report the sta-
tus of a certain event, after diagnostic event debouncing has been completed. For
interaction between the Dem and SW-C or BSW please refer to the API InitMonitor-
ForEvent (refer to chapter 7.2).
If there are any requirements to get the passed or failed status within a certain amount
of time, the diagnostic monitor is responsible.

AUTOSAR CP R20-11
[SWS_Dem_00413] dThe Dem module shall support the event-specific configuration

of debounce algorithms by using the configuration container DemDebounceAlgorithm-
Class.c(RS_Diag_04068)
Note: That means for each individual event a specific algorithm can be specified.
7.7.3.1 Counter based debounce algorithm
[SWS_Dem_00526] dThe Dem module shall provide a configuration parameter

DemDebounceCounterBasedSupport (refer to DemGeneral) to enable or disable
the Dem-internal counter based debouncing.c(RS_Diag_04068)
[SWS_Dem_00414] dIf the configuration container DemDebounceAlgorithmClass
is set to DemDebounceCounterBased, the Dem module shall provide an internal
debounce counter for each individual event, to qualify the reported event.c(RS_-
Diag_04068)
For huge debounce ranges, the maximal range of the internal debounce counter is
defined as sint16. This does not imply any explicit implementation.
DemDebounceAlgorithmClass:
EcucChoiceContainerDef
+choice
DemDebounceCounterBased:
EcucParamConfContainerDef DemDebounceCounterBasedClassRef: DemDebounceCounterBasedClass:
lowerMultiplicity = 0 upperMultiplicity = 1 upperMultiplicity = 65535
Figure 7.29: Counter based debounce algorithm
[SWS_Dem_00415] dThe Dem module shall calculate the fault detection counter (-
128 ... +127 according to UDS) based on the value and range of the internal debounce
counter to map the internal counter values linearly to the external values.c()
[SWS_Dem_00416] dThe Dem module shall provide the configuration parameter
DemDebounceCounterFailedThreshold used to define the event-specific limit in-
dicating the failed status (active).c(RS_Diag_04068)
DemDebounceCounterPassedThreshold used to define the event-specific limit in-
dicating the passed status (passive).c(RS_Diag_04068)
[SWS_Dem_00418] dThe Dem module shall increment the internal debounce
counter with its configured step-size (refer to DemDebounceCounterIncre-
mentStepSize), when the monitor reports DEM_EVENT_STATUS_PREFAILED.c
(RS_Diag_04068)

AUTOSAR CP R20-11
[SWS_Dem_00419] dThe Dem module shall decrement the internal debounce

counter with its configured step-size (refer to DemDebounceCounterDecre-
mentStepSize), when the monitor reports DEM_EVENT_STATUS_PREPASSED.c
(RS_Diag_04068)
[SWS_Dem_00420] dIf the monitor reports DEM_EVENT_STATUS_FAILED, the Dem
module shall set the internal debounce counter value to its configured threshold
being the failed criteria.c(RS_Diag_04068)
[SWS_Dem_00421] dIf the monitor reports DEM_EVENT_STATUS_PASSED, the Dem
module shall set the internal debounce counter value to its configured threshold
being the passed criteria.c(RS_Diag_04067, RS_Diag_04068)
DemDebounceCounterJumpDown for enabling the jump-down behavior.c(RS_Diag_-
04068)
[SWS_Dem_00423] dIf the jump-down behavior is enabled, the Dem module shall
provide the configuration parameter DemDebounceCounterJumpDownValue defin-
ing the new internal debounce counter init value. Each reporting of a pre-
passed value while the current debounce counter value is greater than the
DemDebounceCounterJumpDownValue shall first reset the debounce counter
to DemDebounceCounterJumpDownValue before performing the pre-passed de-
bounce event ( [SWS_Dem_00419]).c(RS_Diag_04068)
Note: This will only happen if the counting direction changes from incrementing to
decrementing.
DemDebounceCounterJumpUp for enabling the jump-up behavior.c(RS_Diag_04068)
[SWS_Dem_00425] dIf the jump-up behavior is enabled, the Dem module shall
provide the configuration parameter DemDebounceCounterJumpUpValue defining
the new internal debounce counter init value. Each reporting of a pre-
failed value while the current debounce counter value is smaller than the
DemDebounceCounterJumpUpValue shall first reset the debounce counter to
DemDebounceCounterJumpUpValue before performing the pre-failed debounce event
( [SWS_Dem_00418]).c(RS_Diag_04068)
Note: This will only happen if the counting direction changes from decrementing to
incrementing.

AUTOSAR CP R20-11
FAILED
jump up jump up
PREFAILED
Reports
PREPASSED
jump down don't jump jump down
PASSED
FDC max
Failed
step up
Fault
0
Detection
Counter jump down value
step down
jump up value
Passed
FDC min
Failed
Event
status
Passed
Figure 7.30: Example of counter based debouncing (including jump behaviour)
Note: In figure 7.30, the value of Fault Detection Counter maps linearly to the internal
debounce counter value.
The action DEM_DEBOUNCE_STATUS_FREEZE of the API Dem_ResetEventDe-
bounceStatus is not relevant for counter-base debouncing. The action DEM_DE-
BOUNCE_STATUS_RESET of the Dem_ResetEventDebounceStatus is covered by
[SWS_Dem_00684].
The DemDebounceBehavior DEM_DEBOUNCE_STATUS_FREEZE is covered in chap-
ter 7.7.6. The DemDebounceBehavior DEM_DEBOUNCE_RESET is covered by
[SWS_Dem_00654] and [SWS_Dem_00677]. This is shown in figure 7.31.

AUTOSAR CP R20-11
DemDebounceBehavior = FREEZE
FAILED /
PASSED
PREFAILED /
PREPASSED
Reports
Failed / FDC max/min (+127/-128)

Passed
Enable Condition(s) not fulfilled OR

Fault ControlDTCSetting disabled
0
Detection
Counter
t
DemDebounceBehavior = RESET
FAILED /
PASSED
PREFAILED /
PREPASSED
Reports

Passed

0
Detection
Counter
t
Figure 7.31: Counter based debouncing behavior on enable conditions
[SWS_Dem_00674] dIf the configuration parameter DemDebounceCounterStorage

is set to True, the Dem module shall store the current value of the internal debounce
counter non-volatile (refer to [SWS_Dem_00341]).c(RS_Diag_04124)

AUTOSAR CP R20-11
Note: DemDebounceCounterStorage is not supported for time based debouncing.

[SWS_Dem_00675] dIf the configuration parameter DemDebounceCounterStorage
is set to True, the Dem module shall re-store the current value of the internal debounce
counter during each startup (latest in Dem_Init).c(RS_Diag_04124)
Note: BSW events using non-volatile storage of the internal debounce counter can-
not be reported before Dem_Init, because the value needs first to be restored.
[SWS_Dem_00676] dIf development error detection is enabled and Dem_-
SetEventStatus or Dem_ResetEventDebounceStatus is called before Dem_-
Init or after Dem_Shutdown for events which have DemDebounceCounterStor-
age set to True, the Dem module shall set the error code DEM_E_WRONG_CONDITION.c
(RS_Diag_04124)
[SWS_Dem_CONSTR_06151] Dependency on DemCounterBasedFdcThreshold-
StorageValue dThe configuration parameter DemCounterBasedFdcThreshold-
StorageValue shall only be present if DemFreezeFrameRecordTrigger is set to
DEM_TRIGGER_ON_FDC_THRESHOLD or DemExtendedDataRecordTrigger is set
to DEM_TRIGGER_ON_FDC_THRESHOLD or DemEventMemoryEntryStorageTrig-
ger is set to DEM_TRIGGER_ON_FDC_THRESHOLD.c()
[SWS_Dem_CONSTR_06152] Dependency on DemDebounceCounterJump-
DownValue dDemDebounceCounterJumpDownValue shall only be present if
DemDebounceCounterJumpDown is set to TRUE.c()
[SWS_Dem_CONSTR_06153] Dependency on DemDebounceCounterJumpUp-
Value dDemDebounceCounterJumpUpValue shall only be present if DemDe-
bounceCounterJumpUp is set to TRUE.c()
[SWS_Dem_CONSTR_06154] Dependency on DemDebounceCounterStorage d
DemDebounceCounterStorage shall only be present if DemOperationCycleSta-
tusStorage is set to TRUE.c()
7.7.3.2 Time based debounce algorithm
[SWS_Dem_00527] dThe Dem module shall provide a configuration parameter

DemDebounceTimeBasedSupport (refer to DemGeneral) to enable or disable the
Dem-internal time based debouncing.c(RS_Diag_04068)
is set to DemDebounceTimeBased, the Dem module shall provide an internal de-
bounce timer for each individual event, to qualify the reported event.c(RS_Diag_04068)
For long debounce periods, the maximal range of the internal debounce timer is defined
as sint16. This does not imply any explicit implementation.

AUTOSAR CP R20-11
+choice
DemDebounceTimeBase:
DemDebounceTimeBaseClass:
DemDebounceTimeBaseRef: EcucParamConfContainerDef
upperMultiplicity = 1 +reference EcucReferenceDef +destination
Figure 7.32: Time based debounce algorithm
[SWS_Dem_00427] dThe Dem module shall calculate the fault detection counter (-
128 ... +127 according to UDS) based on the value and range of the internal debounce
timer, to map the internal timer values linearly to the external values.c(RS_Diag_04068)
[SWS_Dem_00428] dThe Dem module shall start the internal debounce timer to qual-
ify the reported event as failed when the monitor reports DEM_EVENT_STATUS_PRE-
FAILED.c(RS_Diag_04068)
[SWS_Dem_00429] dIf the internal debounce timer of a specific event was already
triggered as pre-failed or the event is qualified as failed, and the monitor reports con-
secutively DEM_EVENT_STATUS_PREFAILED again, the Dem module shall not restart
the internal debounce timer.c(RS_Diag_04068)
Note: The Dem module provides the configuration parameter DemDebounceTime-
FailedThreshold used to define the event-specific delay indicating the failed status
(active).
[SWS_Dem_00431] dIf the monitor reports DEM_EVENT_STATUS_FAILED, the Dem
module shall set the internal debounce timer value to its configured threshold being the
failed criteria (refer to DemDebounceTimeFailedThreshold).c(RS_Diag_04067,
RS_Diag_04068)
[SWS_Dem_00432] dThe Dem module shall start the internal debounce timer to qual-
ify the reported event as passed when the monitor reports DEM_EVENT_STATUS_-
PREPASSED.c(RS_Diag_04068)
[SWS_Dem_00433] dIf the internal debounce timer of a specific event was already trig-
gered as pre-passed or the event is qualified as passed, and the monitor reports con-
secutively DEM_EVENT_STATUS_PREPASSED again, the Dem module shall not restart
the internal debounce timer.c(RS_Diag_04068)
DemDebounceTimePassedThreshold used to define the event-specific delay indi-
cating the passed status (not active).c(RS_Diag_04068)

AUTOSAR CP R20-11
[SWS_Dem_00435] dIf the monitor reports DEM_EVENT_STATUS_PASSED the Dem

module shall set the internal debounce timer value to its configured threshold being the
passed criteria (refer to DemDebounceTimePassedThreshold).c(RS_Diag_04068)
FAILED
PREFAILED
Reports
PREPASSED
PASSED
FDC max (+127)

Failed
Fault
0
Detection
Counter
Passed
FDC min (-128)
t failed t passed t failed t failed t failed
t passed
Failed
Event
status
Passed
Figure 7.33: Example of time based debouncing
[SWS_Dem_00685] dIf the API Dem_ResetEventDebounceStatus is called with

DEM_DEBOUNCE_STATUS_FREEZE, it shall freeze the related internal debounce timer.c
(RS_Diag_04068)
The action DEM_DEBOUNCE_STATUS_RESET of the API Dem_ResetEventDe-
bounceStatus is covered by [SWS_Dem_00684].

AUTOSAR CP R20-11
[SWS_Dem_00655] dIf the configuration parameter DemDebounceBehavior is set

to DEM_DEBOUNCE_STATUS_FREEZE, the Dem module shall freeze the internal de-
bounce timer when at least one enable condition for the related event is set to not
fulfilled.c(RS_Diag_04125)
to DEM_DEBOUNCE_STATUS_FREEZE, the Dem module shall freeze the internal de-
bounce timer when ControlDTCSetting is set to disabled for the related event.c(RS_-
Diag_04125)
[SWS_Dem_00656] dIf an internal debounce timer is frozen and a new (valid)
(debouncing-)result is reported for this event (as per [SWS_Dem_00428] /
[SWS_Dem_00432]), the Dem module shall continue running the internal debounce
timer (from current value).c(RS_Diag_04125)
The DemDebounceBehavior DEM_DEBOUNCE_RESET is covered by
[SWS_Dem_00654] and [SWS_Dem_00677].

AUTOSAR CP R20-11
DemDebounceBehavior = FREEZE
FAILED /
PASSED
PREFAILED /
PREPASSED
Reports

Passed

0
Detection
Counter
t
DemDebounceBehavior = RESET
FAILED /
PASSED
PREFAILED /
PREPASSED
Reports

Passed

0
Detection
Counter
t
Figure 7.34: Time based debouncing behavior on enable conditions

AUTOSAR CP R20-11
7.7.3.3 Monitor internal debounce algorithm

is set to DemDebounceMonitorInternal, the Dem module shall not use a Dem-
internal debounce mechanism for each individual event, to qualify the reported event.c
(RS_Diag_04068)
Note: The monitor is not allowed to report the event states DEM_EVENT_STATUS_-
PREFAILED and DEM_EVENT_STATUS_PREPASSED for monitor internal debouncing.
DemDebounceAlgorithmClass: DemDebounceMonitorInternal: DemCallbackGetFDC:
EcucChoiceContainerDef +choice EcucParamConfContainerDef +subContainer EcucParamConfContainerDef

+parameter
DemCallbackGetFDCFnc:
EcucFunctionNameDef
Figure 7.35: Monitor internal debounce algorithm
7.7.3.4 Debounce algorithm initialization and reset conditions
[SWS_Dem_00438] dIf Dem-internal debouncing is configured, the Dem module shall

reset the Dem-internal debounce algorithm when Dem_PreInit has been called.c
(RS_Diag_04068)
[SWS_Dem_00343] dAfter receiving a command for clearing the event memory, the
Dem-internal debounce algorithm shall be reset, presuming event debouncing is
handled Dem-internally.c(RS_Diag_04117, RS_Diag_04068)
[SWS_Dem_00684] dIf the API Dem_ResetEventDebounceStatus is called with
DEM_DEBOUNCE_STATUS_RESET, it shall reset the related fault detection counter.c
(RS_Diag_04068)
Note: The internal debounce counter is reset to zero. The reset of an internal
debounce timer will also stop this timer.
[SWS_Dem_00344] dIf Dem-internal debouncing is configured, the Dem module shall
reset the Dem-internal debounce algorithm upon starting a new operation cycle.c(RS_-
Diag_04068)
For details see chapter 7.6.
Note: Resetting the debounce algorithm will also lead to a fault detection counter value
of 0 (zero).

AUTOSAR CP R20-11

to DEM_DEBOUNCE_RESET and the function Dem_SetEnableCondition sets one
configured enable condition for the event to not fulfilled, it shall reset the related fault
detection counter(s).c(RS_Diag_04125)
to DEM_DEBOUNCE_RESET, the function Dem_DisableDTCSetting shall reset the
related fault detection counter(s).c(RS_Diag_04125)
7.7.3.5 Fault detection counter retrieval
[SWS_Dem_00204] dThe event-specific fault detection counter shall be accessible by

using the API Dem_GetFaultDetectionCounter.c(RS_Diag_04068)
The fault detection counter can be:
1. located inside the Dem, if Dem-internal debouncing is configured (refer to chapter
7.7.3.1 and chapter 7.7.3.2).
2. located inside the monitor, if debouncing is performed by the monitor (refer to
[SWS_Dem_00264], [SWS_Dem_00439], [SWS_Dem_00513]).
[SWS_Dem_00264] dIf debouncing is performed by a SW-C (not handled Dem inter-
nally), the Dem module shall retrieve the current value of the fault detection counter for
the requested event by using the method defined in DemCallbackGetFDC container.c
(RS_Diag_04068)
Note: The configuration container DemCallbackGetFDC (in DemDebounceMoni-
torInternal) is used to specify the related port or c-callback per event.
[SWS_Dem_00439] dIf monitor internal debouncing is used and the container Dem-
CallbackGetFDC is configured and the configured callback-function returns other
than E_OK, this return value shall also be returned by the API Dem_GetFaultDe-
tectionCounter.c(RS_Diag_04068)
Note: For resetting the fault detection counter implemented in a monitor, the Dem
module uses the callback-function InitMonitorForEvent (refer to chapter 7.2).
[SWS_Dem_00671] dIf monitor internal debouncing is used and the container Dem-
CallbackGetFDC is not configured for a given event, the API Dem_GetFaultDe-
tectionCounter shall return DEM_E_NO_FDC_AVAILABLE.c()

AUTOSAR CP R20-11
7.7.3.6 Fault detection counter reporting
The maximum value the DTC Fault Detection Counter has reached during current op-
eration cycle.
[SWS_Dem_00788] dIf the maximum FDC during current operation cycle is
mapped to an extended data record (DemInternalDataElement set to
DEM_MAX_FDC_DURING_CURRENT_CYCLE), it shall be available for all events ref-
erencing a UDS DTC.c(RS_Diag_04125)
[SWS_Dem_00789] dIf the UDS DTC of [ [SWS_Dem_00788]] is referenced by multiple
events or an combined DTC, the event with the highest maximum FDC value shall be
used to report.c(RS_Diag_04125)
[SWS_Dem_00790] dThe maximum FDC during current operation cycle shall be reset
to zero with each restart operation cycle (refer to DemOperationCycleRef).c(RS_-
Diag_04125)
[SWS_Dem_00791] dThe maximum FDC during current operation cycle shall be up-
date if the current fault detection counter value is greater than the current value of the
maximum FDC during current operation cycle.c(RS_Diag_04125)
The maximum value the DTC Fault Detection Counter has reached since the last time
DTC information was cleared.
[SWS_Dem_00792] dIf the maximum FDC since last clear is mapped to an ex-
tended data record (DemInternalDataElement set to DEM_MAX_FDC_SINCE_-
LAST_CLEAR), it shall be available for all events referencing a UDS DTC.c(RS_Diag_-
04125)
[SWS_Dem_00793] dIf the UDS DTC of [SWS_Dem_00792] is referenced by multiple
events or an combined DTC, the event with the highest maximum FDC value shall be
used to report.c(RS_Diag_04125)
[SWS_Dem_00794] dThe maximum FDC since last clear shall be reset to zero with
each clear DTC command affecting this particular event.c(RS_Diag_04125)
[SWS_Dem_00795] dThe maximum FDC since last clear shall be update if the current
fault detection counter value is greater than the current value of the maximum FDC
since last clear.c(RS_Diag_04125)
7.7.4 Fault confirmation
After reporting, a fault and entering the pending status, the fault confirmation process
begins within the Dem (refer to Figure 7.26 General diagnostic event storage process-
ing).
This fault confirmation process results in the confirmed state. For that purpose, re-
spective counter thresholds and counter types are specified.

AUTOSAR CP R20-11
[SWS_Dem_00528] dThe Dem module shall provide the configuration parameter De-
mEventConfirmationThreshold per event defining the maximum number of tested
and failed cycles, before the event becomes “confirmed”, i.e. enters the confirmed
state.c()
[SWS_Dem_00529] dThe configuration parameter DemOperationCycleRef (refer
to DemEventParameter) shall be used for calculating the trip counter according
ISO14229-1[2].c(RS_Diag_04067)
The healing confirmation process (described in chapter 7.7.8) handles reported OK /
passed results, which yields in the deactivation of a specific warning indicator. For that
purpose, respective counter thresholds and counter types are specified.
Note: If the fault confirmation of an event is disabled, its UDS status bit 3 is set
during the qualification to failed (according to [SWS_Dem_00391]).
[SWS_Dem_01242] dThe Dem shall support calls of Dem_SetEventConfirmation-
ThresholdCounter after Dem_PreInit.c(RS_Diag_04161)
[SWS_Dem_01243] dA call of the API
Dem_SetEventConfirmationThresholdCounter shall set a new failure confir-
mation threshold.c(RS_Diag_04161)
Note: A new failure confirmation threshold value will overwrite the default value given
by DemEventConfirmationThreshold).
[SWS_Dem_01244] dIf Dem_SetEventConfirmationThresholdCounter is
called and the corresponding event is already stored in event memory and the new
failure threshold is less or equal to the current failure counter, then the event will get
confirmed. This implies, that the event related data will also be updated according
their defined triggers.c(RS_Diag_04161)
[SWS_Dem_01245] dIf Dem_SetEventConfirmationThresholdCounter is
called and the corresponding event is already stored in event memory and already
confirmed, the event memory entry and confirmation status will remain, even if
the new threshold is greater than the failure counter. Also after new error status
reports, the confirmation status will remain.c(RS_Diag_04161)
[SWS_Dem_01246] dA DemIndicatorAttribute with a configured DemMILIndi-
catorRef, shall use the DemEventConfirmationThreshold instead of the De-
mIndicatorFailureCycleCounterThreshold to calculate the indicator On Cri-
teria (WarningIndicatorOnCriteriaFulfilled).c(RS_Diag_04161)

AUTOSAR CP R20-11
7.7.4.1 Method for grouping of association of events for OBD purpose
[SWS_Dem_00965] dThe Dem module shall provide a configuration parameter De-

mOBDGroupingAssociativeEventsRef for each event to reference a representive
event to one group of associate events.c()
Note: One event is only allowed to be referenced to only one group of associate events.
A referenced event must refer to it self.
[SWS_Dem_00967] dFor each report of a Malfunction within in a group of events Dem
shall proceed cycle counter towards MIL activation, either by processing a common
cycle counter or by counting the respective counter of the reported event referenceing
to the event with the counter value “closest to MIL ON”.c()
[SWS_Dem_00968] dThe healing / aging for each event shall to be performed indi-
vidually.c(RS_Diag_04178)
7.7.5 Event Combination
Event combination defines the ability of the Dem module to merge several events to
one DTC. It is used to adapt different monitor results to one significant fault, which is
clearly evaluable in a service station. The essential part of implementing a combined
DTC is the calculation of its status information. The combined DTC status byte results
from a bitwise logical operation of all associated events.
[SWS_Dem_00536] dThe following event combination types are supported:
1. Combination on storage: configuration parameter DemEventCombination-
Support is set to DEM_EVCOMB_ONSTORAGE. The combined DTC is stored and
updated in a single event memory entry.
2. Combination on retrieval: configuration parameter DemEventCombination-
Support is set to DEM_EVCOMB_ONRETRIEVAL. Each event is stored in a sepa-
rate event memory location.
3. Disabled: configuration parameter DemEventCombinationSupport is set to
DEM_EVCOMB_DISABLED and event combination is not used
c()
[SWS_Dem_00024] dIn case DemEventCombinationSupport is set to DEM_-
EVCOMB_ONRETRIEVAL or DEM_EVCOMB_ONSTORAGE, the combination of multiple
events to a DTC is defined by referencing from each event to the same DTC.c()
Note: For OBD it is also possible to assign multiple time the same DTC number via
DemObdDTCRef. But as a difference to UDS and J1939 DTCs the OBD DTCs are
reported multiple times to the Dcm.

AUTOSAR CP R20-11
Based on the configuration of the event related data the Dem module allows two dif-
ferent types of event combination (assign event related data to the combine even-
t/DTC or to the sub-events).
Note: The primary use-case of event combination is to map more than one event
(represented by an EventId) to only one DTC number. If combination “on storage” is
used, the Dem module uses only one event memory entry and its related data
for all events combined to the DTC. If combination on retrieval is used, each event is
stored in a separate event memory location with its own set of event related data.
The Dem module handles the combined DTC in consideration of its related event
memory entries.
Table 7.1 shows an example of a Dem configuration table including combined DTCs.
Several events are mapped to the same DTC. The combination on storage is repre-
sented by the DTC[1]. The DTC[2] shows an example of the combination on retrieval.
The freeze frame data is stored individual for each event.
Unique Monitor UDS status Assigned Freeze ....
EventId status DTC frame
Event[1] S1 S1|S2|S3 DTC[1] FF[28]
Event[7] S7 S7 DTC[3] FF[89]
Event[8] S8 S8 DTC[4] FF[67]
.... .... .... .... .... ....
Table 7.1: Example of a Dem configuration table including combined DTCs
[SWS_Dem_00441] dThe Dem module shall implement the status bit calculations for
the UDS status byte according to Table 7.2.c()
UDS status bit Combined UDS status information logical equation

description
0 TestFailed CbDTCBit0 = Event[1]Bit0 | Event[2]Bit0 | ... |Event[n]Bit0
1 TestFailedThis CbDTCBit1 = Event[1]Bit1 | Event[2]Bit1 | ... |Event[n]Bit1
OperationCy-
cle
2 PendingDTC CbDTCBit2 = Event[1]Bit2 | Event[2]Bit2 | ... |Event[n]Bit2
3 ConfirmedDTC CbDTCBit3 = Event[1]Bit3 | Event[2]Bit3 | ... |Event[n]Bit3
4 TestNotCompleted CbDTCBit4 = ( Event[1]Bit4 | Event[2]Bit4 | ... |Event[n]Bit4 ) & !
SinceLastClear CbDTCBit5
5 TestFailedSince CbDTCBit5 = Event[1]Bit5 | Event[2]Bit5 | ... |Event[n]Bit5
LastClear
6 TestNotCompleted CbDTCBit6 = ( Event[1]Bit6 | Event[2]Bit6 | ... |Event[n]Bit6 ) & !
ThisOpera- CbDTCBit1 CbDTC
tionCycle
7 WarningIndicator CbDTCBit7 = Event[1]Bit7 | Event[2]Bit7 | ... |Event[n]Bit7
Requested

AUTOSAR CP R20-11
Table 7.2: Calculation of UDS status byte
In the table above the following logical operators are used:

• ! = logical negation (NOT)
• | = logical bitwise OR-operation
• & logical bitwise AND-operation
[SWS_Dem_00440] dIf the Dem module is requested to clear a combined DTC
(refer to Dem_ClearDTC), the Dem module shall clear all related events (refer to
[SWS_Dem_01049] and [SWS_Dem_01050])c()
[SWS_Dem_01049] dIf the Dem module is requested to report the status of a com-
bined DTC (refer e.g. Dem_GetStatusOfDTC or Dem_GetNextFilteredDTC), the
calculation of the status byte shall be performed according [SWS_Dem_00441].c()
[SWS_Dem_01050] dEach time the status of an event is updated, the combined
DTC status shall be calculated. If the combined DTC status has changed the rel-
evant callbacks shall be invoked; refer to [SWS_Dem_00284], [SWS_Dem_00986],
[SWS_Dem_00987] and [SWS_Dem_00828].c()
[SWS_Dem_00672] dThe fault detection counter of the combined DTC shall be the
maximum fault detection counter value of the sub-events.c()
Note: The combined fault detection counter value is required for Dem_GetNextFil-
teredDTCAndFDC (in UDS Service 0x19 14).
[SWS_Dem_CONSTR_6103] dIn case the event combination is disabled, it is not
allowed to reference from multiple events to the same dtc.c()
7.7.5.1 Combination On Storage
The following section describes the behavior of the Dem module in case the combina-
tion on storage is configured.
[SWS_Dem_00163] dIf the Dem module is requested to support combination on stor-
age, the DTC status bit transitions of the combined DTC (refer [SWS_Dem_00441])
shall be used as trigger source for the allocation of the event memory entry, as
well as the collection or update of its related data (freeze frames or extended data
records).c()
[SWS_Dem_00442] dIf a combined DTC (combination on storage) is aged, the
Dem module shall remove this event memory entry and reset the status
bytes of all sub-events according to [SWS_Dem_00823], [SWS_Dem_00824] and
[SWS_Dem_00498].c(RS_Diag_04133)
[SWS_Dem_00443] dIf a combined DTC (combination on storage) is displaced, the
Dem module shall remove this event memory entry and reset the status bytes of

AUTOSAR CP R20-11
all sub-events according to [SWS_Dem_00409] and [SWS_Dem_01186].c(RS_Diag_-

04118)
7.7.5.2 Combination On Retrieval
The section below describes the behavior of combination on retrieval.

[SWS_Dem_00539] dIf the Dem module is requested to support combination on re-
trieval , the status bit transition of each event shall trigger the collection, update and
storage of the related data (freeze frame / extended data).c(RS_Diag_04067)
[SWS_Dem_00540] dIf the Dem module is requested to report data of a combined
DTC (combination on retrieval ), the Dem module shall return the event related data of
all assigned events.c()
[SWS_Dem_00541] dAging of each event of a combined DTC (combination on
retrieval ) shall be processed individually according to [SWS_Dem_00493] and
[SWS_Dem_00498].c()
[SWS_Dem_00542] dFor combination on retrieval, the displacement algorithm for each
event of a combined DTC shall be treated individually (refer to [SWS_Dem_00408]).c
()
7.7.6 Enable and storage conditions of diagnostic events
In certain cases, the event retention depends on parameters, which are available on
operation system level. These parameters are combined to groups and define a certain
number of checks (e.g. correct voltage range) before the event report is accepted or the
event gets qualified. The checks are done by software components. The Dem module
provides the ability to consider the reported result (a specific condition is fulfilled or
not) during the event handling. There are two different types of conditions: enable
conditions and storage conditions.
The strategy how to use the conditions (e.g. suppression of subsequent faults) and
especially the assigning matrix of conditions to the events depends on the OEM.
The enable conditions are defined as a set of parameters, which are assigned to a
specific condition. As long as this condition is not fulfilled, the event reports (refer
to Dem_SetEventStatus) are not valid and therefore will not be accepted. It has
no impact on Dem_ResetEventDebounceStatus, Dem_ResetEventStatus and
Dem_ClearDTC. A similar functionality is used for the function inhibition. In contrast to
the mutual exclusion matrix of the FiM, which is based on events, the enable conditions
are based on system parameters (e.g. ignition status, local voltage).
The storage conditions are defined as a set of parameters, which are assigned to a
specific condition. As long as this condition is not fulfilled, the Dem module does not
store the event to the event memory.

AUTOSAR CP R20-11
The following requirements introduce the handling of the enable conditions.

Note:The Dem module supports enable conditions and provides the API Dem_SetEn-
ableCondition to receive the current status (condition fulfilled or not)of a specific
enable condition.
Note: The Dem module supports enable conditions that can be assigned to a specific
event.
Note: The enable condition groups are introduced to improve the configuration method-
ology of the Dem module. If a significant number of events depend always on the same
enable conditions, it is less effort to select one of the defined enable condition groups
instead of assigning several enable conditions to each of those events.
[SWS_Dem_00447] dIf the Dem module is requested to support enable conditions, the
Dem module shall check the assigned enable conditions after the diagnostic monitor
reports an event (passed/failed or pre-passed/pre-failed, refer to Dem_SetEventSta-
tus).c(RS_Diag_04192)
[SWS_Dem_00449] dIf one enable condition is not fulfilled, all of Dem_SetEventSta-
tus calls for those events being assigned to this condition shall be ignored (no change
of event status byte) by the Dem.c(RS_Diag_04192)
Note: In case of Dem-internal debouncing the related fault detection counter will be
frozen or reset (refer to chapter Figure 29 and Figure 32).
[SWS_Dem_00450] dIf all event-specific enable conditions are fulfilled, all status re-
ports from SW-Cs and BSW modules via Dem_SetEventStatus for those events
being assigned to these conditions shall be accepted by the Dem from this point in
time on.c(RS_Diag_04192)
DemEventParameter: DemEnableConditionGroupRef:
EcucParamConfContainerDef +reference EcucReferenceDef

+destination
DemGeneral: EcucParamConfContainerDef DemEnableConditionGroup: DemEnableConditionRef:

+subContainer EcucParamConfContainerDef +reference EcucReferenceDef
+destination
DemEnableCondition: DemEnableConditionId:
upperMultiplicity = 255 +parameter max = 255

+subContainer upperMultiplicity = 1
DemEnableConditionStatus:
Figure 7.36: Enable condition assignment configuration

AUTOSAR CP R20-11
The following requirements introduce the handling of the storage conditions.

Note: The Dem module supports storage conditions and provides the API Dem_Set-
StorageCondition to receive the current status (condition fulfilled or not)of a specific
storage condition.
Note: The Dem module supports storage conditions that can be assigned to a specific
event.
Note: The storage condition groups are introduced to improve the configuration
methodology of the Dem module. If a significant number of events depend always on
the same storage conditions, it is less effort to select one of the defined storage condi-
tion groups instead of assigning several storage conditions to each of those events.
[SWS_Dem_00455] dIf storage conditions are used and assigned to an event, the
Dem shall evaluate the assigned storage conditions after the event gets qualified
as PASSED or FAILED and process DemFreezeFrameRecordTrigger, DemEx-
tendedDataRecordTrigger and DemEventMemoryEntryStorageTrigger only
if the storage condition is fulfilled.c(RS_Diag_04219)
Note: The Dem module supports storage conditions and checks the assigned storage
conditions after the event reports DEM_EVENT_STATUS_FDC_THRESHOLD_REACHED
(e.g. either via interface call or when reaching the configured threshold in debounce
algorithm).
Note: If one storage condition is not fulfilled and no respective event memory entry
exists, the Dem module will not enter the reported event into the event memory.
Note: If one storage condition is not fulfilled and a respective event memory entry
exists, the Dem module will not update the event memory of the reported event.
[SWS_Dem_01309] dIf at least one storage condition assigned to an event is not ful-
filled, the Dem shall skip the calculation of the bits:
• bit 2 (PendingDTC) and
• bit 3 (ConfirmedDTC).
in the corresponding event status byte and UDS status byte.c(RS_Diag_-
04219)
[SWS_Dem_00459] dIf all event-specific storage conditions are fulfilled, the Dem mod-
ule shall permit the storage of the reported event.c(RS_Diag_04219)

AUTOSAR CP R20-11
DemGeneral: DemStorageCondition: DemStorageConditionId: EcucIntegerParamDef

EcucParamConfContainerDef EcucParamConfContainerDef
+parameter symbolicNameValue = true
upperMultiplicity = 1 upperMultiplicity = 255 min = 0
lowerMultiplicity = 1 lowerMultiplicity = 0 max = 255
DemStorageConditionStatus:
+subContainer +parameter EcucBooleanParamDef
DemStorageConditionReplacementEventRef:
+destination
DemStorageConditionRef:
EcucReferenceDef
+reference
DemStorageConditionGroup:
+destination
DemStorageConditionGroupRef:
EcucReferenceDef
+reference
DemEventParameter:
EcucParamConfContainerDef +destination
Figure 7.37: Storage condition assignment configuration
For each storage condition a replacement event may be defined (see DemStorage-
ConditionReplacementEventRef). This replacement event will be used as a re-
placement failure info.
[SWS_Dem_01086] dIf an event is reported as FAILED and a storage condition ref-
erencing this event by DemStorageConditionReplacementEventRef exists and
the storage condition is FALSE, the replacement event shall be set to FAILED.c(RS_-
Diag_04137)
Note: As long as the storage condition is not fulfilled and no event assigned to the
storage condition reports FAILED, the replacement event shall not be set.
Note: The replacement event has an EventStatus (Dem_UdsStatusByteType) as
every other event.

AUTOSAR CP R20-11
Note: The status/behavior of the filtered event (filtered by the storage condition) is not
affected by the replacement event. The failure which is filtered by the storage condition
behaves identical in case of having a replacement event or in case of NOT having a
replacement event configured for the storage condition.
[SWS_Dem_01089] dThe replacement event shall be reset (status PASSED), when
the storage condition is fulfilled (on enabling the storage condition).c(RS_Diag_04137)
[SWS_Dem_CONSTR_06167] dthe replacement event:
• shall not be mapped to a storage condition (DemStorageConditionGroupRef)
• shall not be configured to use debouncing (DemDebounceAlgorithmClass)
• shall not have an InitMForE callback/ clearEventAllowed (DemCallbackInitM-
ForE/DemCallbackClearEventAllowed)
• shall not be configured for enableConditions (DemEnableConditionGroupRef)
• shall be configured as DEM_EVENT_KIND_BSW
c(RS_Diag_04137)
7.7.7 Event related data
‘Event related data’ are additional data, e.g. sensor values or time stamp/mileage,
which are stored in case of an event. ISO-14229-1[2] defines two different types of
event related data: snapshot data (freeze frames) and extended data. The number or
sets of stored event related data are strongly OEM / failure specific and are therefore
configurable. This data is provided by SW-C or other BSW modules.
[SWS_Dem_00796] dEach event memory entry shall support the capability to
store the configured ‘Event related data’ (freeze frame data (DTCSnapshot) or DTCEx-
tendedData).c()
Note: The presence of a Confirmed UDS status does not necessarily mean that ‘event
related data’ is available as well.
The Dem module is not in charge of validity of event related data. Time consistency of
event related data is depending on data source and storage time.
The Dem module provides a configuration table to combine event related data (freeze
frames & extended data) with a specific DTC number, etc. (refer to chapter 7.7.7.4).
Note: This does not define a specific implementation (e.g. look-up table, matrix, etc.).
Furthermore it relates to the link between the configured data. An event is character-
ized by its event Id, DTC value, configured freeze frames and extended data records,
etc.

AUTOSAR CP R20-11
7.7.7.1 Storage of freeze frame data
[SWS_Dem_00039] dThe Dem module shall support event-specific freeze frame stor-
age.c()
In general, there are two options for freeze frame configuration: (1) Non-emission re-
lated freeze frames are configured specific to one particular event. The freeze frame
records can be addressed by using relative numbers (calculated or configured), so
the record numbers are unique to an event (not globally). (2) Emission related freeze
frames are configured globally for a particular ECU (OBD legislation requires one sin-
gle freeze frame class only). The freeze frame record can be addressed per event by
using the value 0x00.
[SWS_Dem_00040] dThe Dem module shall support the storage of one or several
DIDs per freeze frame record assigned by configuration (refer to DemFreezeFrame-
Class).c()
Note: A freeze frame is represented as a list of DIDs (refer to DemDidClass ) or PIDs
(refer to DemPidClass).
Note: Due to implementation reasons, the Dem usually needs to reserve memory for
the maximum freeze frame size multiplied by the number of freeze frames.
[SWS_Dem_00337] dIf DemTypeOfFreezeFrameRecordNumeration is set to
DEM_FF_RECNUM_CALCULATED (refer to DemPrimaryMemory or DemUserDe-
finedMemory), the Dem shall store DemMaxNumberFreezeFrameRecords number
of freeze frames for this DTC.c(RS_Diag_04127)
[SWS_Dem_CONSTR_06166] dIf DemTypeOfFreezeFrameRecordNumeration is
set to DEM_FF_RECNUM_CALCULATED, parameter DemFreezeFrameRecordTrig-
ger shall be set to DEM_TRIGGER_ON_TEST_FAILED.c(RS_Diag_04127)
[SWS_Dem_00581] dIf the Dem module uses calculated record numbers, the Dem
module shall numerate the event-specific freeze frame records consecutively starting
by 1, based on their chronological order.c(RS_Diag_04127)
[SWS_Dem_00582] dIf DemTypeOfFreezeFrameRecordNumeration is set to
DEM_FF_RECNUM_CONFIGURED (refer to DemPrimaryMemory or DemUserDe-
finedMemory), the Dem shall store per event memory entry all configured freeze
frame records for this DTC.c()
[SWS_Dem_00797] dIf the FreezeFrame uses dedicated, configured record numbers
(refer to DemFreezeFrameRecNumClassRef) and an event memory entry exists,
the Dem module shall capture the FreezeFrame on the configured trigger (refer to Dem-
FreezeFrameRecordTrigger) and store it to the event memory entry.c(RS_-
Diag_04127)
In case, the storage trigger was not able to allocate an event memory entry (due to
event retention) there might meanwhile the possibility (due to aging) to have suitable
memory entries Therefore the FreezeFrame trigger should try again to allocate an
event memory entry.

AUTOSAR CP R20-11
[SWS_Dem_00798] dIf the FreezeFrame uses dedicated, configured record num-

bers (refer to DemFreezeFrameRecNumClassRef) and no event memory entry
exists, the Dem module shall first try to allocate an event memory entry as
described in [SWS_Dem_00783], [SWS_Dem_00784], [SWS_Dem_00785] and
[SWS_Dem_00786]. Afterwards requirement [SWS_Dem_00797] applies.c(RS_-
Diag_04127)
[SWS_Dem_00799] dIf the DemFreezeFrameRecordTrigger is set to DEM_-
TRIGGER_ON_FDC_THRESHOLD, the FreezeFrame shall be captured (as allowed by
[SWS_Dem_00797]) each time the configured FDC threshold (refer to DemCoun-
terBasedFdcThresholdStorageValue or DemTimeBasedFdcThresholdStor-
ageValue) is reached (by a positive increment), but at most once per operation cycle.c
(RS_Diag_04127)
TRIGGER_ON_FDC_THRESHOLD and the event reports DEM_EVENT_STATUS_FDC_-
THRESHOLD_REACHED (monitor-internal debounced event), the FreezeFrame shall be
captured (refer [SWS_Dem_00797]), but at most once per operation cycle.c(RS_-
Diag_04127)
TRIGGER_ON_TEST_FAILED, the FreezeFrame shall be captured (as allowed by
[SWS_Dem_00797]) each time the UDS status bit 0 is set (changing from 0 to
1).c(RS_Diag_04127)
TRIGGER_ON_PENDING, the FreezeFrame shall be captured (as allowed by
1).c(RS_Diag_04127)
TRIGGER_ON_CONFIRMED, the FreezeFrame shall be captured (as allowed by
[SWS_Dem_00797]) each time the Confirmed UDS status bit 3 is set (changing
from 0 to 1).c(RS_Diag_04127)
[SWS_Dem_01351] dIf the DemFreezeFrameRecordTrigger is set to DEM_TRIG-
GER_ON_TEST_FAILED_THIS_OPERATION_CYCLE, the FreezeFrame shall be cap-
tured each time the UDS status bit 1 (TFTOC) has a transition from 0 to 1.c(RS_Diag_-
04127)
[SWS_Dem_01308] Continous trigger conditions for freeze frames dIf the Dem-
FreezeFrameRecordTrigger is set to DEM_TRIGGER_ON_EVERY_TEST_FAILED,
each time an event was reported as FAILED or after optional debouncing a qualified
FAILED is detected the Dem shall capture the Freeze frame.c(RS_Diag_04127)
(refer to DemFreezeFrameRecNumClass) and DemFreezeFrameRecordUpdate is
set to DEM_UPDATE_RECORD_NO, the FreezeFrame shall be stored only if the Freeze-
Frame is currently not stored in this event memory entry.c(RS_Diag_04127)

AUTOSAR CP R20-11

(refer to DemFreezeFrameRecNumClass) and DemFreezeFrameRecordUpdate is
set to DEM_UPDATE_RECORD_YES, the FreezeFrame shall be updated with each trig-
ger (refer to DemFreezeFrameRecordTrigger).c(RS_Diag_04127)
[SWS_Dem_00461] dIf the configuration parameter DemEnvironmentDataCap-
ture is set to DEM_CAPTURE_ASYNCHRONOUS_TO_REPORTING (refer to DemPrima-
ryMemory or DemUserDefinedMemory), event-specific freeze frame data shall
be captured latest in the next cycle of the Dem_MainFunction.c(RS_Diag_04127)
[SWS_Dem_00805] dIf the configuration parameter DemEnvironmentDataCapture
is set to DEM_CAPTURE_SYNCHRONOUS_TO_REPORTING (refer to DemPrimaryMem-
ory or DemUserDefinedMemory) and DemDebounceTimeBasedSupport is set to
‘false’, event-specific freeze frame data shall be captured within the reporting function
(i.e. in the context of Dem_SetEventStatus).c(RS_Diag_04127)
Note: [SWS_Dem_00461] and [SWS_Dem_00805] does not apply if a pre-stored
freeze frame is available, see also [SWS_Dem_00464].
[SWS_Dem_01081] dIf the configuration parameter DemEnvironmentDataCap-
ture is set to DEM_CAPTURE_ASYNCHRONOUS_TO_REPORTING (refer to DemPrima-
ryMemory or DemUserDefinedMemory), event-specific extended data shall be cap-
tured latest in the next cycle of the Dem_MainFunction.c(RS_Diag_04127)
[SWS_Dem_01082] dIf the configuration parameter DemEnvironmentDataCapture
ory or DemUserDefinedMemory), event-specific extended data shall be captured
within the context of Dem_SetEventStatus.c(RS_Diag_04127)
If DemEnvironmentDataCapture is equal to DEM_CAPTURE_SYNCHRONOUS_TO_-
REPORTING (refer to DemPrimaryMemory or DemUserDefinedMemory), a queue
could be used to store the environment data until the data is transferred to the event
memory. To not loose any reporting, the queue size needs to be configured to store all
reporting between two cycles of Dem_MainFunction.
[SWS_Dem_01083] dIf DemEnvironmentDataCapture is equal to DEM_CAP-
TURE_SYNCHRONOUS_TO_REPORTING, the Dem module shall queue the environmen-
tal data from the reporting (see [SWS_Dem_00805] and [SWS_Dem_01082]) till the
next call of the Dem_MainFunction. The Dem shall at minimum queue the configured
size (refer DemMaxNumberEventEntryEventBuffer). In case the queue is full, the
environmental data shall be captured when the event is processed in Dem_MainFunc-
tion.c(RS_Diag_04127)
[SWS_Dem_CONSTR_06121] Dependency for DemMaxNumberEventEntryEvent-
Buffer dThe DemMaxNumberEventEntryEventBuffer shall only be present if
DemEnvironmentDataCapture is set to DEM_CAPTURE_SYNCHRONOUS_TO_RE-
PORTING (refer to DemPrimaryMemory or DemUserDefinedMemory).c()
[SWS_Dem_CONSTR_06122] Dependency for DemOccurrenceCounterProcess-
ing dThe DemOccurrenceCounterProcessing (refer to DemPrimaryMemory or

AUTOSAR CP R20-11
DemUserDefinedMemory) shall only be present if DemEnvironmentDataCapture

ory or DemUserDefinedMemory).c()
[SWS_Dem_CONSTR_06123] Dependency for DemOperationCycleStatusStor-
age dThe DemOperationCycleStatusStorage shall only be present if DemOBD-
Support is set to DEM_OBD_MASTER_ECU or DEM_OBD_PRIMARY_ECU.c()
[SWS_Dem_CONSTR_06124] Dependency for DemPTOSupport dDemPTOSup-
port shall only be present if DemOBDSupport is set to DEM_OBD_MASTER_ECU or
DEM_OBD_PRIMARY_ECU.c()
[SWS_Dem_CONSTR_06125] Dependency for DemAgingCycleCounterThresh-
old dDemAgingCycleCounterThreshold shall only be present if DemAgingAl-
lowed is set to TRUE.c()
[SWS_Dem_CONSTR_06126] Dependency for DemAgingCycleCounterThresh-
oldForTFSLC dDemAgingCycleCounterThresholdForTFSLC shall only be
present if DemStatusBitHandlingTestFailedSinceLastClear is set to DEM_-
STATUS_BIT_AGING_AND_DISPLACEMENT.c()
[SWS_Dem_CONSTR_06127] Dependency for DemMaxNumberFreezeFrameRe-
cords dDemMaxNumberFreezeFrameRecords shall only be present if DemTypeOf-
FreezeFrameRecordNumeration is set to DEM_FF_RECNUM_CALCULATED.c()
[SWS_Dem_CONSTR_06128] Dependency for DemAgingCycleRef dDemAging-
CycleRef shall only be present if DemAgingAllowed is set to TRUE.c()
[SWS_Dem_CONSTR_06129] Dependency for DemFreezeFrameRecNumClass-
Ref dDemFreezeFrameRecNumClassRef shall only be present if that DTC refer-
ences a fault memory that has DemTypeOfFreezeFrameRecordNumeration is set
to DEM_FF_RECNUM_CONFIGURED (refer to DemPrimaryMemory or DemUserDe-
finedMemory).c()
[SWS_Dem_CONSTR_06130] Dependency for DemReportBehavior dDemRe-
portBehavior shall only be present if DemEventKind is set to DEM_EVENT_KIND_-
SWC.c()
[SWS_Dem_CONSTR_06131] Dependency for DemOBDGroupingAssocia-
tiveEventsRef dDemOBDGroupingAssociativeEventsRef shall only be present if
DemOBDSupport is set to DEM_OBD_MASTER_ECU or DEM_OBD_PRIMARY_ECU.c()
[SWS_Dem_CONSTR_06132] Dependency for DemOBDCentralized-
PID21Handling dDemOBDCentralizedPID21Handling shall only be present
if DemOBDSupport is set to DEM_OBD_MASTER_ECU or DEM_OBD_PRIMARY_ECU.c()
[SWS_Dem_CONSTR_06133] Dependency for DemOBDCentralized-
PID31Handling dDemOBDCentralizedPID31Handling shall only be present

AUTOSAR CP R20-11
[SWS_Dem_CONSTR_06134] Dependency for DemOBDCompliancy dDemOBD-

Compliancy shall only be present if DemOBDSupport is set to DEM_OBD_MASTER_-
[SWS_Dem_CONSTR_06135] Dependency for DemOBDEngineType dDemOB-
DEngineType shall only be present if DemOBDSupport is set to DEM_OBD_MASTER_-
[SWS_Dem_CONSTR_06136] Dependency for DemOBDEventDisplacement dDe-
mOBDEventDisplacement shall only be present if DemOBDSupport is set to DEM_-
OBD_MASTER_ECU or DEM_OBD_PRIMARY_ECU.c()
[SWS_Dem_CONSTR_06137] Dependency for DemOBDInputAcceleratorPedalIn-
formation dDemOBDInputAcceleratorPedalInformation shall only be present
[SWS_Dem_CONSTR_06138] Dependency for DemOBDInputAmbientPressure d
DemOBDInputAmbientPressure shall only be present if DemOBDSupport is set to
DEM_OBD_MASTER_ECU or DEM_OBD_PRIMARY_ECU.c()
[SWS_Dem_CONSTR_06139] Dependency for DemOBDInputAmbientTempera-
ture dDemOBDInputAmbientTemperature shall only be present if DemOBDSupport
is set to DEM_OBD_MASTER_ECU or DEM_OBD_PRIMARY_ECU.c()
[SWS_Dem_CONSTR_06140] Dependency for DemOBDInputDistanceInforma-
tion dDemOBDInputDistanceInformation shall only be present if DemOBDSup-
port is set to DEM_OBD_MASTER_ECU or DEM_OBD_PRIMARY_ECU.c()
[SWS_Dem_CONSTR_06141] Dependency for DemOBDInputEngineSpeed dDe-
mOBDInputEngineSpeed shall only be present if DemOBDSupport is set to DEM_-
[SWS_Dem_CONSTR_06142] Dependency for DemOBDInputEngineTemperature
dDemOBDInputEngineTemperature shall only be present if DemOBDSupport is set
to DEM_OBD_MASTER_ECU or DEM_OBD_PRIMARY_ECU.c()
[SWS_Dem_CONSTR_06143] Dependency for DemOBDInputProgrammingEvent
dDemOBDInputProgrammingEvent shall only be present if DemOBDSupport is set
to DEM_OBD_MASTER_ECU or DEM_OBD_PRIMARY_ECU.c()
[SWS_Dem_CONSTR_06144] Dependency for DemOBDInputVehicleSpeed dDe-
mOBDInputVehicleSpeed shall only be present if DemOBDSupport is set to DEM_-
[SWS_Dem_CONSTR_06145] Dependency for DemConsiderPtoStatus dDemCon-
siderPtoStatus shall only be present if DemOBDSupport is set to DEM_OBD_MAS-
TER_ECU or DEM_OBD_PRIMARY_ECU.c()
The snapshot record data is usually captured asynchronously from reporting the event
status. In certain situations the captured data needs to be aligned with the reported
event status. For this purpose the Dem_SetEventStatusWithMonitorData pro-
vides the possibility to add 2 monitor data. The monitorData0 can optionally be

AUTOSAR CP R20-11
passed to the DataServices_Data ReadData operation, so the application can

align the data capture call to the initiated Dem_SetEventStatus function call.
[SWS_Dem_01330] Capturing event related data with monitor data dIf the Read-
Data operation is configured to provide the monitorData0, the Dem shall add the
monitorData0 from the Dem_SetEventStatusWithMonitorData to the Read-
Data operation parameter monitorData0.c()
[SWS_Dem_01331] Handling of missing monitorData dIf the data capturing was
triggered from within an API call without monitorData, the Dem shall use a value of 0 as
monitorData.c()
[SWS_Dem_00261] dThe Dem module shall use the C-callback DemRead respectively
the operation ReadData of the interface DataServices_Data to collect all config-
ured data elements of the respective freeze frame.c(RS_Diag_04127)
[SWS_Dem_00463] dIf the SW-C or BSW module cannot not provide the requested
data (ReadDataElement returns other than E_OK), the Dem shall fill the missing data
with the padding value 0xFF, report the runtime error DEM_E_NODATAAVAILABLE to
the Det and continue its normal operation.c(RS_Diag_04085)
[SWS_Dem_00585] dIf the Dem module uses calculated record numbers, and if more
than one freeze frame record is configured for a specific event, and this event is up-
dated in the event memory, and all available freeze frame record slots for this event
are occupied, the Dem module shall update the most recent record.c()
Note: The first freeze frame record slot will always represent the first occurrence.
7.7.7.2 Pre-storage of freeze frame data
The pre-storage of freeze frames can be used for events with highly volatile freeze
frame data. With the first indication of the appearance of a specific event, even if the
event is not yet de-bounced or qualified, the freeze frame data is captured (e.g. be-
cause of rapid changing of event related data during running failure monitoring phase).
The pre-stored freeze frame functionality is used by monitors.
DemFFPrestorageSupported (refer to DemEventParameter) to enable or disable
pre-storage handling of freeze frames per event.c(RS_Diag_04127)
Note: If DemMaxNumberPrestoredFF is set to 0, DemFFPrestorageSupported
can not be enabled for any DTC.
[SWS_Dem_00334] dIf any event is configured to use pre-storage of freeze frames
(refer to DemFFPrestorageSupported), the Dem module shall provide the API
Dem_PrestoreFreezeFrame and Dem_ClearPrestoredFreezeFrame. Other-
wise they are not provided.c(RS_Diag_04127)

AUTOSAR CP R20-11
[SWS_Dem_00189] dThe Dem module shall provide the API Dem_Prestore-

FreezeFrame to capture the pre-storage data of an event-specific freeze frame re-
gardless of the UDS status bit changes.c()
Note: If a request to prestore a freeze frame (Dem_PrestoreFreezeFrame) is
interrupted by reporting an event status (Dem_SetEventStatus) or a call to Dem_-
ClearPrestoredFreezeFrame of the same EventId the detailed behavior is imple-
mentation specific. The freeze frame which is requested to be prestored might be
used immediately or might be stored and used with next upcoming event report or vice
versa.
[SWS_Dem_00808] dThe API Dem_PrestoreFreezeFrame shall return E_NOT_OK
if no memory is available (see DemMaxNumberPrestoredFF).c(RS_Diag_04127)
[SWS_Dem_00464] dIf a pre-stored freeze frame is available, the Dem module shall
use the data of the pre-stored freeze frame instead of the current data at the point in
time when the event related date is captured (refer to [SWS_Dem_00461].c()
[SWS_Dem_00969] dA pre-stored freeze frame shall be released after it has been
stored in the event memory or discarded.c()
Note : A pre-stored freeze frame is considered to be stored if event retention is suc-
cessful. A pre-stored freeze frame is discarded if the event retention failed.
[SWS_Dem_00191] dIf no pre-stored freeze frame is available, the Dem module shall
behave according to Storage of freeze frame data (refer to [SWS_Dem_00039]).c()
Note: The captured data while using pre-stored freeze frames can differ from the data,
which is collected using the UDS status bit transitions as a trigger.
Note: To ensure absence of reaction to stored freeze frames of qualified events an
additional freeze frame buffer should be used. Due to restrictions in hardware usage,
the amount of possible entries can be restricted. Therefore, a replacement strategy
could be required.
Figure 7.38: Example to use Dem_PrestoreFreezeFrame to prestore freeze frame data
Some events detect a failure in one operation cycle of the control unit, but only de-
termine the conditions to allow storage of the failure in the next operation cycle. The

AUTOSAR CP R20-11
freeze-frame of such events shows the values from the old operation cycle. For this
purpose, the Dem supports non-volatile storage of pre-stored freeze-frame data. To
avoid excessive storage, the storage can be enabled/disabled per event individually
through the configuration DemFFPrestorageInNvm.
[SWS_Dem_01320] dIf DemFFPrestorageInNvm is set to TRUE, the Dem shall
store pre-stored freeze-frame data for this event on in Nvm.c(Non volatile storage of
pre-stored data)
[SWS_Dem_01321] Point in time to store pre-stored data in non-volatile memory
dIf the Dem is configured to store pre-stored freezeframe data in non-volatile memory
according to [SWS_Dem_01320], the Dem shall store the data once and latest during
Dem_Shutdown.c()
[SWS_Dem_01322] Point in time to retrieve pre-stored data from non-volatile
memory dIf the Dem is configured to store pre-stored freezeframe data in non-volatile
memory according to [SWS_Dem_01320], the Dem shall restore the pre-stored data
before Dem_Init has returned.c()
[SWS_Dem_01323] Consistency of non-volatile stored pre-stored data dIf the Dem
is restoring pre-stored data according to [SWS_Dem_01322], the Dem shall only re-
store this data if it is consistent to the current configuration. If after reprogramming or
calibration, the data layout has changed, the Dem shall skip the pre-stored data.c()
[SWS_Dem_00050] dThe Dem module shall provide the API Dem_ClearPre-
storedFreezeFrame to release the pre-stored freeze frame for the specific event.c
()
[SWS_Dem_00465] dIf an event gets qualified as passed (UDS status bit 0
changes from 1 to 0) the Dem module shall release the pre-stored freeze frame for
the specific event.c()
7.7.7.3 Storage of extended data
An extended data record contains additional information associated to a specific event

that is not contained in a freeze frame (extended data, e.g. frequency counters, Ag-
ing counters, etc.). According to the DID- or PID-based configuration of freeze
frame data, extended data are divided in extended data records defined by its record
numbers.
[SWS_Dem_00809] dIf an event memory entry exists, the Dem module shall cap-
ture the ExtendedDataRecord on the configured trigger (refer to DemExtended-
DataRecordTrigger) and store it to the event memory entry.c(RS_Diag_-
04127)
In case, the storage trigger was not able to allocate an event memory entry (due to
event retention) there might meanwhile the possibility (due to aging) to have suitable
memory entries Therefore the ExtendedDataRecord trigger should try again to allocate
an event memory entry.

AUTOSAR CP R20-11
[SWS_Dem_00810] dIf no event memory entry exists, the Dem module shall
first try to allocate an event memory entry as described in [SWS_Dem_00783],
[SWS_Dem_00784], [SWS_Dem_00785] and [SWS_Dem_00786]. Afterwards re-
quirement [SWS_Dem_00809] applies.c(RS_Diag_04127)
[SWS_Dem_00811] dIf the DemExtendedDataRecordTrigger is set to DEM_-
TRIGGER_ON_FDC_THRESHOLD, the ExtendedDataRecord shall be captured (as al-
lowed by [SWS_Dem_00810]) each time the configured FDC threshold (refer to Dem-
CounterBasedFdcThresholdStorageValue or DemTimeBasedFdcThreshold-
StorageValue) is reached (by a positive increment), but at most once per operation
cycle.c(RS_Diag_04127)
TRIGGER_ON_FDC_THRESHOLD and the event reports DEM_EVENT_STATUS_FDC_-
THRESHOLD_REACHED (monitor-internal debounced event), the ExtendedDataRecord
shall be captured (refer [SWS_Dem_00810]), but at most once per operation cycle.c
(RS_Diag_04127)
TRIGGER_ON_TEST_FAILED, the ExtendedDataRecord shall be captured (as allowed
by [SWS_Dem_00810]) each time the UDS status bit 0 is set (changing from 0
to 1).c(RS_Diag_04127)
TRIGGER_ON_PENDING, the ExtendedDataRecord shall be captured (as allowed by
1).c(RS_Diag_04127)
TRIGGER_ON_CONFIRMED, the ExtendedDataRecord shall be captured (as allowed
by [SWS_Dem_00810]) each time the UDS status bit 3 is set (changing from 0
to 1).c(RS_Diag_04127)
TRIGGER_ON_PASSED, the ExtendedDataRecord shall be captured with the change
of Testfailed UDS status bit 0 is reset (changing from 1 to 0). If no entry exists,
on passed report no new entry shall be created.c(RS_Diag_04127)
TRIGGER_ON_MIRROR, the ExtendedDataRecord shall be captured with the transfer
of the memory entry to the mirror memory.c(RS_Diag_04127)
[SWS_Dem_CONSTR_6101] dDemExtendedDataRecordTrigger needs to be
configured. DemExtendedDataRecordTrigger shall always be configured, except
for internal data elements like occurrence counters.c()
[SWS_Dem_00815] dIf the configuration parameter DemExtendedDataRecordUp-
date is set to DEM_UPDATE_RECORD_NO, the ExtendedDataRecord shall be stored
only if the ExtendedDataRecord is currently not stored in this event memory en-
try.c(RS_Diag_04127)

AUTOSAR CP R20-11
[SWS_Dem_00816] dIf the configuration parameter DemExtendedDataRecordUp-

date is set to DEM_UPDATE_RECORD_YES, the ExtendedDataRecord shall be updated
with each trigger (refer to DemExtendedDataRecordTrigger).c(RS_Diag_04127)
[SWS_Dem_00282] dThe Dem module shall use the C-callback ReadDataElement re-
spectively the operation ReadData of the interface DataServices_Data to collect
all configured data elements which are not typed as internal data elements (refer to
DemInternalDataElementClass) of the respective extended data record.c()
[SWS_Dem_00468] dIf an event is stored or updated in the event memory, the
Dem module shall store the collected extended data into the event memory entry.c
(RS_Diag_04127)
[SWS_Dem_01391] Configuration of DTC priority as extended data record dIf
DemInternalDataElement is set to DEM_DTC_PRIORITY, the Dem shall set the value
of this internal data element to the DTC priority assigned by DemDTCPriority for this
DTC. The length of this internal data element is one byte.c(RS_Diag_04134)
7.7.7.4 Configuration of Event related data
This section describes the configuration of event related data and the access of event
related data from the SW-Cs/BSW modules.
Note: The configuration model follows a flexible configuration process, but does not
imply any explicit implementation.
The event related data of diagnostic events contain none or one set of extended data
records (refer to DemExtendedDataClass), and none or one set of freeze frame
records (refer to DemFreezeFrameClass) with its calculated or configured record
numbers. Therefore a class-concept is used (refer to Figure 37).
An extended data record, a DID, or a PID can contain one ore more data elements
(refer to DemDataElementClass).
Note: Asynchronous DIDs, as well as DIDs with a variable length are not supported by
the Dem module, and shall therefore not be connected to the Dem.

AUTOSAR CP R20-11
DemExtendedDataClassRef: DemFreezeFrameClassRef:
EcucReferenceDef EcucReferenceDef
+subContainer +destination +destination +subContainer
DemExtendedDataClass: DemFreezeFrameClass:

+reference +reference
DemExtendedDataRecordClassRef: DemDidClassRef: EcucReferenceDef

EcucReferenceDef
lowerMultiplicity = 1 requiresIndex = true
requiresIndex = true
DemExtendedDataRecordClass: DemDataElementClassRef: DemDidClass:

EcucParamConfContainerDef +reference EcucReferenceDef EcucParamConfContainerDef
upperMultiplicity = 253 upperMultiplicity = 255 upperMultiplicity = 65535

+subContainer
+destination +reference
DemDataElementClass:
EcucChoiceContainerDef DemDidDataElementClassRef:
EcucReferenceDef
+destination upperMultiplicity = 255
DemInternalDataElementClass: EcucParamConfContainerDef
+choice
+choice DemExternalCSDataElementClass: EcucParamConfContainerDef
DemExternalSRDataElementClass: EcucParamConfContainerDef
+choice
DemPidDataElementClassRef: EcucReferenceDef
+destination
Figure 7.39: Event related data configuration
A data element is provided from a SW-C or BSW module, or is computed Dem-

internally.
For each external data element a respective require-port (refer to Service Interface
DataServices_<Data>) or C-callback (refer to ReadDataElement) is generated based

AUTOSAR CP R20-11
on the configuration DemExternalCSDataElementClass and DemExternalSR-

DataElementClass. For each internal data element, the respective Dem-internal
value is mapped.
Note: These data elements are typically specified in a Diagnostic Data Template.
DemGeneral:
+subContainer
DemDataElementClass: DemInternalDataElementClass: DemDataElementDataSize:

EcucChoiceContainerDef EcucParamConfContainerDef EcucIntegerParamDef
upperMultiplicity = 65535 lowerMultiplicity = 0 max = 255
+choice upperMultiplicity = 1
+parameter DemInternalDataElement:
DemExternalCSDataElementClass: DemDataElementArraySize:
+parameter
lowerMultiplicity = 0 max = 4294967295
DemDataElementDataType:
+choice DemDataElementUsePort:
DemDataElementReadFnc:
+parameter EcucFunctionNameDef
DemDataElementProvideMonitorData:
EcucBooleanParamDef
+parameter
DemExternalSRDataElementClass: DemDataElementArraySize:
+parameter
DemSRDataElementClass:
+subContainer EcucChoiceContainerDef
Figure 7.40: Data element configuration

AUTOSAR CP R20-11
[SWS_Dem_CONSTR_06158] dExistence of size parameter DemDataElementAr-

raySize [ECUC_Dem_00949] in container DemExternalCSDataElementClass
shall be present if DemDataElementDataType [ECUC_Dem_00950] in the same
container is set to: UINT8_N, SINT8_N, UINT16_N, SINT16_N, UINT32_N,
SINT32_N, FLOAT_N.c()
Note: DemDataElementArraySize [ECUC_Dem_00949] in container DemExter-
nalCSDataElementClass is not required for primitive datatypes.
[SWS_Dem_CONSTR_06159] dRestrictions on size parameter for 16 Bit arrays Dem-
DataElementArraySize [ECUC_Dem_00949] shall be a multiple of 2 if the value is
greater than 2 and DemDataElementDataType [ECUC_Dem_00950] is UINT16_N
or SINT16_N.c()
greater than 4 and DemDataElementDataType [ECUC_Dem_00950] is UINT32_N,
SINT32_N or FLOAT_N.c()
[SWS_Dem_CONSTR_06161] dExistence of size parameter DemDataElementAr-
raySize [ECUC_Dem_00967] in container DemExternalSRDataElementClass
shall be present if DemDataElementDataType [ECUC_Dem_00840] in the same
container is set to: UINT8_N, SINT8_N, UINT16_N, SINT16_N, UINT32_N,
SINT32_N, FLOAT_N.c()
Note: DemDataElementArraySize [ECUC_Dem_00967] in container DemExter-
nalSRDataElementClass is not required for primitive datatypes.
or SINT16_N.c()
or SINT32_N.c()
[SWS_Dem_00469] dThe Dem module shall provide the ability to map Dem-internal
data values (e.g. aging counter, occurrence counter) to specific data element (re-
fer to DemInternalDataElement in DemDataElementClass)contained in an extended
data records.c(RS_Diag_04189, RS_Diag_04190)
Note: If a Dem-internal data element is mapped to e.g. an extended data record (by
configuration), this information can simply be requested by UDS Service ReadDTCIn-
formation - Sub-Service reportDTCExtendedDataRecordByDTCNumber (0x19, 06).
[SWS_Dem_00817] dInternal data elements (refer to DemInternalDataElement-
Class) shall not be stored, but the current value shall be used instead.c(RS_Diag_-
04127, RS_Diag_04190)

AUTOSAR CP R20-11
Note: Further customer-specific Dem-internal data elements (according to

[SWS_Dem_00470]) can have different semantics (e.g. Dem-internal data elements
can freeze a value or provide a current value)
[SWS_Dem_CONSTR_06169] Usage of internal data elements only for extended
data records dThe DemInternalDataElementClass shall be only allowed for Dem-
DataElementClass if it is only referenced by DemDataElementClassRef from
DemExtendedDataRecordClass.c()
[SWS_Dem_00471] dIf the configuration parameter DemInternalDataElement is
set to DEM_OCCCTR, then the Dem-internal value of the occurrence counter shall be
mapped to the respective data element.c(RS_Diag_04127, RS_Diag_04190)
set to DEM_AGINGCTR_UPCNT or to DEM_AGINGCTR_DOWNCNT, then the Dem-internal
value of the aging counter shall be mapped to the respective data element (based
on [SWS_Dem_00643] or [SWS_Dem_00673]).c(RS_Diag_04190)
[SWS_Dem_00643] dIf the data element DEM_AGINGCTR_UPCNT is configured, the
aging counter mapping shall be based on a count-up mechanism from 0 to
DemAgingCycleCounterThreshold (refer to ISO-14229-1[2], Annex D).c(RS_-
Diag_04068, RS_Diag_04190)
[SWS_Dem_00673] dIf the data element DEM_AGINGCTR_DOWNCNT is configured, the
aging counter mapping shall be based on a count-down mechanism from DemAg-
ingCycleCounterThreshold to 0 (refer to ISO-14229-1[2], Annex D).c(RS_Diag_-
04178, RS_Diag_04190)
[SWS_Dem_01043] dIf DemAgingAllowed is set to ‘false’ the internal data element
DEM_AGINGCTR_DOWNCNT shall be DemAgingCycleCounterThreshold if config-
ured or ‘255’.c(RS_Diag_04190)
[SWS_Dem_01044] dIf Dem DemAgingAllowed is set to ‘false’ the internal data ele-
ment DEM_AGINGCTR_UPCNT shall be ‘0’.c(RS_Diag_04190)
set to DEM_AGINGCTR_UPCNT_FIRST_ACTIVE, the value shall be calculated anal-
ogous to DEM_AGINGCTR_UPCNT. The difference is, that in case the current aging
counter has a value of 0 and the event status bits TestFailedThisOperationCycle and
TestNotCompletedThisOperationCycle are set to False, a value of 1 is reported upon
reading the Dem internal aging counter.c(RS_Diag_04133)
set to DEM_OVFLIND, then the Dem-internal value of the overflow indication shall be
mapped to the respective data element as boolean (0 = False, 1 = True).c(RS_Diag_-
04190)

AUTOSAR CP R20-11

set to DEM_SIGNIFICANCE, then the (static) Dem-internal value of the DTC signifi-
cance shall be mapped to the respective data element with 0 = OCCURRENCE and 1
= FAULT.c(RS_Diag_04190)
set to DEM_CURRENT_FDC, then the Dem-internal value of the current fault detec-
tion counter shall be mapped to the respective data element with the following value-
translation:
[0..127]->[0x00..0x7F] and [-1..-128]->[0xFF..0x80].c(RS_Diag_04190)
For details see chapter 7.7.3.3 and chapter 7.7.3.4.
set to DEM_MAX_FDC_SINCE_LAST_CLEAR, then the Dem-internal value of the maxi-
mum Fault Detection Counter sincle last clear shall be mapped to the respective data
element.c(RS_Diag_04068, RS_Diag_04190)
set to DEM_MAX_FDC_DURING_CURRENT_CYCLE, then the Dem-internal value of
the maximum Fault Detection Counter during current operation cycle shall be mapped
to the respective data element.c(RS_Diag_04127, RS_Diag_04190)
set to DEM_CYCLES_SINCE_LAST_FAILED, then the Dem-internal value of the oper-
ation cycle counter since last failed shall be mapped to the respective data element.c
(RS_Diag_04127, RS_Diag_04190)
set to DEM_CYCLES_SINCE_FIRST_FAILED, then the Dem-internal value of the op-
eration cycle counter since first failed shall be mapped to the respective data element.c
set to DEM_FAILED_CYCLES, then the Dem-internal value of the failed operation cycle
counter shall be mapped to the respective data element.c(RS_Diag_04190)
The Dem module may be extended with further specific Dem-internal data elements,
if a specific configuration requires particular data values, which are computed Dem-
internally.

AUTOSAR CP R20-11
[SWS_Dem_01350] Mapping of static event associated identifier to internal data

elements dIf the DemInternalDataElement is set to DEM_EVENT_ASSOCIATED_-
IDENTIFICATION, the Dem shall use the static configured value in DemEventAsso-
ciatedIdentification as value for this internal data element.c(RS_Diag_04190)
[SWS_Dem_CONSTR_06168] Required DEM_EVENT_ASSOCIATED_IDENTIFI-
CATION for events dIf an DemEvent refers an DemDTC that itself requires snap-
shot record or extended data records that contain a DemInternalDataElement
= DEM_EVENT_ASSOCIATED_IDENTIFICATION, the DemEventAssociatedIden-
tification shall be configured for that event.c()
[SWS_Dem_00470] dIf the Dem module implements customer-specific Dem-internal
data elements, the configuration parameter DemInternalDataElement shall be ex-
tended with the respective enumeration values.c(RS_Diag_04190)
Note: The computation of any Dem-internal data value, which is not configured as data
element, can be discarded (if it is not necessary for other internal behavior handling).
set to DEM_CURRENT_FDC, then the fault detection counter shall be mapped to the
respective data element.c(RS_Diag_04190)
[SWS_Dem_01334] Usage of monitorData0 in internal data dIf DemInternal-
DataElement is set to DEM_MONITOR_DATA_0, the Dem shall use the 32 bit value
of the provided monitorData0 parameter value of the call Dem_SetEventSta-
tusWithMonitorData as internal data value.c()
[SWS_Dem_01314] Usage of monitorData1 in internal data dIf DemInternal-
DataElement is set to DEM_MONITOR_DATA_1, the Dem shall use the 32 bit value
of the provided monitorData1 parameter value of the call Dem_SetEventSta-
tusWithMonitorData as internal data value.c()
[SWS_Dem_00918] dThe Dem shall treat the non-integer data type uint8[n] either like
an integer data type of the matching size or leave the contents uninterpreted in case
the DemDataElementEndianness is configured to OPAQUE.c(SRS_Com_02041)
[SWS_Dem_00919] dThe Dem shall interpret opaque data as uint8[n] and shall always
map it to an n-bytes sized signal.c(SRS_Com_02041)
Note: For opaque data endianness, conversion has to be configured to OPAQUE.
[SWS_Dem_00920] dThe Dem shall extend the endianness conversion defined in [16]
Chapter 2.4 to signed data types.c(SRS_Com_02041)
Note: In [16] Chapter 2.4 defines the endianness conversion for unsigned data types.
[SWS_Dem_01216] dTo serialize the required signed- and unsigned integer AUTOSAR
data types into the FreezeFrame/ExtendedRecord the target endianness configured

AUTOSAR CP R20-11
in DemDataElementEndianness shall be considered. If DemDataElementEndi-

anness is not present, the DemDataElementDefaultEndianness shall be used
instead.c(RS_Diag_04189)
7.7.7.5 Notification of data changes
The Dem module shall notify other SW-Cs / BSW modules about updates of the event
related data in the event memory (refer to chapter 8.4.3.8).
An update of the event related data occurs every time, a new event memory entry
is done or an existing is updated.
Note: The Dem does not evaluate the return value (e.g. if other than E_OK) of this
callback function.
Note: The configuration container DemCallbackEventDataChanged (in DemEvent-
Parameter) is used to specify the related port or c-callback per event.
[SWS_Dem_00475] dIf ’event related data’ (extended data or freeze frame data) of an
event memory entry is added or updated AND notifications on data changes are
configured via DemCallbackEventDataChanged, the Dem shall trigger these con-
figured event-specific notifications as well as the general notification GeneralCall-
backEventDataChanged.c(RS_Diag_04155)
Note: In case of:
• deletion
• displacement (refer to chapter 7.7.2.4)
• aging (refer to chapter 7.7.8)
the Dem doesn’t trigger the datachanged-callbacks.
[SWS_Dem_01062] dThe functions Dem_GetEventExtendedDataRecordEx and
Dem_GetEventFreezeFrameDataEx shall consider only primary and user defined
memory.c()
Note: The origin of the Event can be derived from the EventId (DemMemoryDestina-
tionRef).
[SWS_Dem_00479] dThe function Dem_GetEventFreezeFrameDataEx shall report
the data of the DID (defined by parameter DataId) in the requested freeze frame record
(defined by parameter RecordNumber, except RecordNumber equal 0xFF) of the re-
quested diagnostic event (EventId). If the RecordNumber is equal to 0xFF and parame-
ter DemTypeOfFreezeFrameRecordNumeration is set to DEM_FF_RECNUM_CAL-
CULATED (refer to DemPrimaryMemory or DemUserDefinedMemory) the most re-
cent record shall be used, otherwise E_NOT_OK shall be returned.c(RS_Diag_04024)
[SWS_Dem_01194] dThe function Dem_GetEventFreezeFrameDataEx shall return
the WWH-OBD freeze frame when called with RecordNumber 0x00. If WWH-OBD is

AUTOSAR CP R20-11
not supported, the function shall return DEM_NO_SUCH_ELEMENT instead (refer to

DemOBDSupport).c(RS_Diag_04024)
[SWS_Dem_00991] dThe format of the data in the destination buffer (DestBuffer) of the
function Dem_GetEventFreezeFrameDataEx is raw hexadecimal values and con-
tains no header-information like RecordNumber or DataId. The size of the buffer equals
to the configuration settings of all respective data elements.c(RS_Diag_04127)
[SWS_Dem_00477] dThe function Dem_GetEventExtendedDataRecordEx shall
report the data of the extended data record of the requested diagnostic event.c(RS_-
Diag_04195)
[SWS_Dem_00989] dThe format of the data in the destination buffer (DestBuffer) of the
function Dem_GetEventExtendedDataRecordEx is raw hexadecimal values and
contains no header-information like RecordNumber.c()
Note: The Dcm uses the function Dem_GetNextExtendedDataRecord instead of the
function Dem_GetEventExtendedDataRecordEx.
[SWS_Dem_00995] dIf the interfaces Dem_GetEventFreezeFrameDataEx and
Dem_GetEventExtendedDataRecordEx are called in the context of General-
CallbackEventDataChanged or CallbackEventDataChanged, the data of the
triggering event shall be retrievable (return value E_NOT_OK is not allowed).c(RS_-
Diag_04189)
[SWS_Dem_00996] dDem_GetEventFreezeFrameDataEx shall return E_NOT_OK
in case the requested FreezeFrame data is currently not accessible (e.g. in case of
asynchronous preempted data retrieval from application).c()
[SWS_Dem_00997] dDem_GetEventExtendedDataRecordEx shall return
E_NOT_OK if the requested data is currently not accessible (e.g.in case of asyn-
chronous preempted data retrieval from application).c()
7.7.8 Aging of diagnostic events
The Dem module provides the ability to remove a specific event from the event mem-
ory, if its fault conditions are not fulfilled for a certain period of time (operation cycles).
This process is called as "aging" or "unlearning".

AUTOSAR CP R20-11

[FALSE]
WarningIndicatorOn-
CriteriaFulfilled?
[TRUE]
[OCY completed && TFTOC==0 && TNCTOC==0]

HealingCounter-- Process healing
[TFTOC==1]
[HealingCounter==0]
WarningIndicatorOff-
CriteriaFulfilled!
!" #$ "

%&%''()* %&%''+,
try to allocate an
event memory entry
[FALSE] Event memory [TFTOC==1]

entry exists?
[TRUE]
[Aging cycle completed && TNCTOC==0]

count further AgingCounter
[TFTOC==1]
Process aging
[DemAgingCycleCounterThreshold reached]
Delete event
memory entry,
CDTC=0
Figure 7.41: General diagnostic event deletion processing
[SWS_Dem_00698] dThe process of aging (counting of aging counter) starts

when healing is completed (WarningIndicatorRequested bit == 0).c(RS_Diag_04133,
RS_Diag_04178)
[SWS_Dem_00019] dThe Dem module shall support at least an aging counter for
each event memory entry.c(RS_Diag_04133, RS_Diag_04068, RS_Diag_04178)

AUTOSAR CP R20-11
[SWS_Dem_00985] dThe aging counter shall be calculated based on the refer-

enced aging/operation cycle (refer to configuration parameter DemAgingCycleRef),
if aging is enabled (refer to DemAgingAllowed) for this event.c(RS_Diag_04133,
RS_Diag_04068, RS_Diag_04178)
[SWS_Dem_00492] dThe Dem module shall be able to cover the current value of the
aging counter of each individual event memory entry, to support an output.c
(RS_Diag_04133)
Note: For extended fault analysis, it is possible to map the current value of the aging
counter to a specific data element of an extended data record (refer to chapter 7.7.7.3
Storage of extended data).
[SWS_Dem_00493] dDemAgingCycleCounterThreshold or DemAgingCycle-
CounterThresholdForTFSLC (depending on which value is higher) defines the
number of completed aging cycles, after which the event memory entry shall be
deleted(aged) from the event memory.c(RS_Diag_04133)
Note: For completed aging cycles definition see [SWS_Dem_00489]
[SWS_Dem_00823] dIf configuration parameter DemResetConfirmedBitOnOver-
flow is set to false and in case an event has UDS status bit 3 set and gets qual-
ified as passed and is not stored in an event memory entry the Dem module shall
try to allocate an event memory entry to get an aging counter.c(RS_Diag_-
04067)
Note: If it is not possible to allocate an event memory entry, the aging delays
until an event memory entry becomes available. (either by [SWS_Dem_00823] or
by [SWS_Dem_00824]).
[SWS_Dem_00824] dIf configuration parameter DemResetConfirmedBitOnOver-
flow is set to false and an event memory entry aging occurs the Dem module
shall check for other events having UDS status bit 3 set to 1 and UDS status
bit 0 set to 0. If such an event is found, the Dem shall allocate an event memory
location to get an aging counter.c(RS_Diag_04133)
Note: The priorizitation which event is choosen is implementation specific.
[SWS_Dem_00498] dUpon event aging counter reach threshold DemAgingCy-
cleCounterThreshold, the UDS status bit 3 shall be set to 0.c(RS_Diag_-
04133)
Note: All other UDS status bits are not modified by aging of corresponding event
memory entry.
[SWS_Dem_00161] dThe Dem module shall handle the reoccurrence of unlearned
events like new events, since they were previously deleted from the event memory
by aging.c(RS_Diag_04195)
[SWS_Dem_00489] dThe Dem module shall only allow processing (counting further)
the value of the aging counter, if the related event is stored in the event memory
and is qualified as passed.c(RS_Diag_04133)

AUTOSAR CP R20-11
Note: Aging is independent of the UDS status bit 3 and therefore independent
of the fault confirmation (refer to chapter 7.7.4).
[SWS_Dem_01054] dUpon event aging counter reach threshold DemAgingCy-
cleCounterThresholdForTFSLC, the UDS status bit 5 (TestFailedSinceLast-
Clear) shall be set to 0 if DemStatusBitHandlingTestFailedSinceLastClear
is set to DEM_STATUS_BIT_AGING_AND_DISPLACEMENT.
In case parameter DemAgingCycleCounterThresholdForTFSLC is not config-
ured, TestFailedSinceLastClear will not be aged.c(RS_Diag_04133)
[SWS_Dem_01075] dUpon event aging, the Dem shall remove the event related Snap-
shot data (Freeze frame) and extended data records from the event memory.c
()
[SWS_Dem_01185] dIn case there is no memory location available or occupied by an
individual event, the UDS status bit TestFailedSinceLastClear of this event will not be
aged.c(RS_Diag_04133)
DemAgingCycleRef (refer to DemDTCAttributes) defining the event-specific op-
eration/aging cycle, whose status change triggers the processing (counting further) of
the aging counter value.c()
Note: Refer to chapter 7.6 for the handling of the operation cycle.
[SWS_Dem_00490] dIf the configuration parameter DemAgingRequiresTestedCy-
cle is set to False, the Dem module shall process (count further) the aging counter
value, if the respective aging cycle ends/restarts.c(RS_Diag_04133)
Note: The aging counter in [SWS_Dem_00490] is processed also if no new test
result is available in the respective aging cycle.
[SWS_Dem_00826] dIf the configuration parameter DemAgingRequiresTestedCy-
cle is set to True, the Dem module shall process (count further) the aging cycle counter
value, if the respective aging cycle ends/restarts and the UDS status bit 6 is set
to zero.c(RS_Diag_04178)
[SWS_Dem_01214] dIf the configuration parameter DemAgingRequiresNot-
FailedCycle is set to true, the aging counter shall only be processed in an oper-
ation cycle without a test failed report.c(RS_Diag_04133)
[SWS_Dem_01215] dIf the configuration parameter DemAgingRequiresNot-
FailedCycle is set to false, the aging counter behavior shall not be influenced.c
(RS_Diag_04133)

AUTOSAR CP R20-11
7.7.9 Healing of diagnostic events
The Dem module provides the ability to activate and deactivate indicators per event
stored in the event memory. The process of deactivation is defined as healing of a
diagnostic event (refer to Figure 7.41).
[SWS_Dem_01056] dThe Dem shall process healing only on passed events using
the current operation cycle DemOperationCycleRef.c()
7.7.9.1 Warning indicator handling
The detailed configuration of the warning indicator handling within the Dem is shown
in Figure 10.15.

AUTOSAR CP R20-11
DemGeneral: +subContainer
EcucParamConfContainerDef DemOperationCycle:
upperMultiplicity = 1 DemMILIndicatorRef: EcucReferenceDef
+destination
DemIndicator: EcucParamConfContainerDef
+destination
DemEventParameter:
+subContainer
DemIndicatorAttribute:
EcucParamConfContainerDef DemIndicatorRef: EcucReferenceDef
+reference
DemIndicatorFailureCycleCounterThreshold:
EcucIntegerParamDef
+parameter
max = 255
min = 1
DemIndicatorHealingCycleCounterThreshold:
EcucIntegerParamDef
+parameter
max = 255
min = 0
+literal
DemIndicatorBehaviour: DEM_INDICATOR_CONTINUOUS:
EcucEnumerationParamDef EcucEnumerationLiteralDef
+literal
DEM_INDICATOR_BLINK_CONT:
+parameter +literal
DEM_INDICATOR_BLINKING:
+literal
DEM_INDICATOR_SLOW_FLASH:
+literal
DEM_INDICATOR_FAST_FLASH:
Figure 7.42: Warning indicator configuration
The Dem module supports event specific counters to activate and deactivate indicators.
These counters are calculated based on the configured failure and healing cycles (e.g.
to turn on the MIL upon fault confirmation, and turn off the MIL after subsequent healing
over three OBD-driving cycles).
Note: During the integration process of the Dem module, different indicators and be-
haviors (e.g. indicator lamps, text messages or icons) can be assigned to an event.

AUTOSAR CP R20-11
[SWS_Dem_00566] dIf more than one indicator is configured for a specific event, the
Dem module shall use a logical OR operation of all combined warning indicators as-
signed to this event to calculate the UDS status bit 7 (WarningIndicator).c(RS_Diag_-
04067)
[SWS_Dem_00501] dThe condition WarningIndicatorOnCriteriaFulfilled shall be ful-
filled if at least one respective event indicator failure counter has reached its De-
mIndicatorFailureCycleCounterThreshold of tested and failed DemOpera-
tionCycles.c()
[SWS_Dem_00503] dIf an indicator is configured (via DemIndicatorAttribute)
the Dem module shall set at the end of an operation cycle the UDS status bit 7
(WarningIndicatorRequested)to 0, if the following conditions are fulfilled:
• at least one DemIndicatorHealingCycleCounterThreshold is unequal to
0
• all respective events indicator healing counters have reached their DemIndica-
torHealingCycleCounterThreshold of tested and passed healing DemOp-
erationCycles (equals WarningIndicatorOffCriteriaFulfilled)
• WIRbit is not enabled by calling the API Dem_SetWIRStatus
c()
[SWS_Dem_01233] dIf an indicator is configured (via DemIndicatorAttribute) the
Dem module shall set when the Event is reported/qualified to PASSED the UDS status
bit 7 (WarningIndicatorRequested)to 0, if the following conditions are fulfilled:
• all DemIndicatorHealingCycleCounterThreshold are equal to 0
• WIRbit is not enabled by calling the API Dem_SetWIRStatus
c()
7.7.9.2 User controlled WarningIndicatorRequested-bit
In some cases (e.g. controlling a failsafe reaction in application) the WIR-bit of a cor-
responding event in Dem shall be set/reset by an especial “failsafe SW-C”.
The failsafe SW-C has to ensure a proper status of the WIR-bit (e.g. regarding to ISO-
14229-1[2] or manufacture specific requirements). Therefore, the failsafe SW-C can
use existing Dem mechanism to get the information about status changes of events in
Dem (e.g. Callback EventUdsStatusChanged).
The failsafe SW-C shall report the required WIR-status to Dem (via
Dem_SetWIRStatus and has to ensure that the current WIR-status of an event
(in Dem) fits to the current failsafe-status in application:
• failsafe running: WIR-bit shall be set to "1"

AUTOSAR CP R20-11
• failsafe not running: WIR-bit shall be set to "0"

The failsafe SW-C has to report the status after every change of failsafe state.
Each invocation of Dem_SetWIRStatus updated the WIR-bit for the corresponding
event (see parameter EventId)
Due to not storing the StatusOfDTC-bit 7 (WIR-bit) on ECU shutdown the failsafe SW-
C has to ensure that the WIR-bit of an event fit to the current failsafe status after
Dem_Init.
[SWS_Dem_00831] dDem shall provide a function to control (set/reset) the
WarningIndicatorRequested-bit of a configured event (in Dem) regarding to e.g. failsafe
state.c()
[SWS_Dem_00832] dSetting of the WIR-bit of an event can be controlled via Dem_-
SetWIRStatus OR by the Dem internal WIR-bit handling. (OR-Operation).c()
Note: The parallel use of Dem_SetWIRStatus and the Dem internal WIR-Bit handling
(at the same time) is needed for example for OBD systems, where the WIR-Bit needs
to be activated according to the legislation (Dem-Internal) and a system reaction is
controlled by the same event. Therefore the WIR-Bit needs to stay active until the
system reaction is deactivated (Dem_SetWIRStatus).
[SWS_Dem_00833] dThe WIR-bit of the corresponding event shall be set to "1" if
Dem_SetWIRStatus is called with parameter WIRStatus = TRUE .c()
[SWS_Dem_00834] dThe WIR-bit of the corresponding event shall be set to "0" if
Dem_SetWIRStatus is called with WIRStatus = FALSE and no referenced Dem Indi-
cator(s) are set.c()
[SWS_Dem_00836] dDuring disabled ControlDTCSettings the WIR-bit of an event
shall not be changed via Dem_SetWIRStatus and the function shall return
E_NOT_OK.c()
Note: In case the failsafe application is not able to set the WIR bit (Dem_SetWIRSta-
tus returned E_NOT_OK), the failsafe application needs to observe the general sta-
tus of the event and coordinate the retry of Dem_SetWIRStatus itself e.g. by us-
ing the callback function InitMonitorForEvent with parameter DEM_INIT_MONI-
TOR_REENABLED.
[SWS_Dem_01303] Asynchronous behavior of Dem_SetWirStatus dThe Dem shall
process a call of the Dem_SetWIRStatus asynchronously. This means that the final
result is available at a later point in time.c().
A later point in time is meant to be implementation specific, it could be the next main
function and after Dem_SetWIRStatus has returned.

AUTOSAR CP R20-11
7.7.9.3 Handling of the warning indicator lamp (MIL)
[SWS_Dem_00546] dFor OBD-relevant ECUs, the Dem module shall provide the con-
figuration parameter DemMILIndicatorRef to indicate that the configured indicator
controls the MIL activation and deactivation.c(RS_Diag_04110)
[SWS_Dem_00567] dIf an indicator is configured for controlling the MIL of an OBD-
relevant ECU, the Dem module shall use the configured event failure cycle counter of
this event (refer to 0 Fault confirmation) to define the maximum number of tested and
failed cycles, before the stored event activates the respective indicator.c()
Note: For OBD systems, the activation of the Malfunction Indicator Lamp (MIL) is linked
with the entry to confirmed state. Therefore the event specific fault confirmation counter
(refer to the configuration parameter DemEventConfirmationThreshold and De-
mOperationCycleRef) has to be consistent with the indicator failure cycle counter.
Note: Leaving Pending state and the deactivation of the MIL is controlled by the con-
figuration of the indicator healing cycle counter.
[SWS_Dem_00701] dIf the MIL is deactivated and the event is confirmed the MIL shall
be reactivated according to [SWS_Dem_00567] i.e. again according to the indicator
failure cycle counter is reaching it’s threshold.c()
[SWS_Dem_00535] dIn case of OBD-relevant events the indicator cycles shall be
based on cycles defined by OBD legislation.c()
[SWS_Dem_CONSTR_06165] Dependency for DemMILIndicatorRef dDem-
MILIndicatorRef shall only be present if DemOBDSupport is set to DEM_OBD_-
MASTER_ECU or DEM_OBD_PRIMARY_ECU.c()
7.7.9.4 Notification and Set of the warning indicator status
[SWS_Dem_00046] dThe Dem module shall provide the API Dem_GetIndica-

torStatus that a software component can get information about the calculated in-
dicator status.c()
7.8 BSW Error Handling

Beside application software components also the basic software (BSW) can detect
errors (e.g. hardware driver faults), especially during startup (ref. to document [11] for
further details). For these errors (only a small number compared to application specific
events), some additional aspects apply:
• Errors can be detected at startup before Dem is fully initialized
• Errors can be reported during startup, information needs to be buffered until Dem
is fully available

AUTOSAR CP R20-11
• Errors can be reported between startup and shutdown, information needs to be

buffered and need to be processed by the Dem main function (RTE related call
tree requirement)
• Entries in the event memory can have a different configuration (e.g. no empha-
sis on freeze frame data for the workshop)
Dem_SetEventStatus is used by BSW modules to report errors from the point in time
when the Dem module is pre-initialized. Within Dem_Init, the queued events are
processed. During normal operation (after full initialization), the queuing mechanism of
the API Dem_SetEventStatus is necessary to process the reported fault within the
main function of the Dem module.
Dem_SetEventStatus can be used by BSW modules to report errors from the point
in time when the Dem module is pre-initialized. Within Dem_Init, the queued events
are processed.
[SWS_Dem_01212] dAfter Dem_PreInit, the Dem shall support debouncing by call-
ing API Dem_SetEventStatus with EventStatus set to DEM_EVENT_STATUS_-
PREPASSED or DEM_EVENT_STATUS_PREFAILED.c(SRS_BSW_00339)
The Fim can be run in trigger or polling mode. For the initialization sequence this mode
is not important, the Dem always initializes the Fim.
[SWS_Dem_01213] dThe Dem-internal debouncing (counters and timers) shall be ini-
tialized by calling Dem_PreInit.c(RS_Diag_04068)
[SWS_Dem_00167] dThe Dem module shall provide a buffer mechanism to queue
events which are reported before Dem_Init via Dem_SetEventStatus as qual-
ified as Passed or Failed or reaching the qualification (debouncing). Reporting
of DEM_EVENT_STATUS_FDC_THRESHOLD_REACHED shall not be queued.c(SRS_-
BSW_00339)
[SWS_Dem_00207] dThe size of the queue of the function Dem_SetEventStatus
which is used while Dem is not initialized is configurable by the configuration parameter
DemBswErrorBufferSize.c(SRS_BSW_00339)
[SWS_Dem_01079] dThe Dem shall determine the queue size depending on the num-
ber of events that can be reported before Dem_Init, i.e., those events with unde-
fined DemReportBehavior or DemReportBehavior = REPORT_BEFORE_INIT. In
case DemBswErrorBufferSize is configured, it overwrites the calculated size of the
queue.c(SRS_BSW_00339)

AUTOSAR CP R20-11
BSW (below RTE) SW-C (above RTE)

Dem_SetEventStatus() Dem_SetEventStatus()
API Port
Available during startup

and normal operation
Available during
normal operation
Buffer
Dem_Init()
Dem_MainFunction()
Event Memory
Dem
Figure 7.43: Dem_SetEventStatus buffering behavior
[SWS_Dem_01289] dAll events which are reported via Dem_SetEventStatus after

Dem_PreInit and before Dem_Init shall not trigger any monitor status change call-
back.c(SRS_BSW_00339)
7.9 OBD-specific functionality
7.9.1 General overview and restrictions
In the following, a specification of the OBD handling in AUTOSAR is introduced. Herein,

“OBD“ is used for automotive OBD with respect to different target markets. For SW-
sharing and distributed development reasons as well as aspects of packaging and
responsibility of releases, the OBD-relevant information / data structures need to be
reported via Standardized AUTOSAR interfaces.
In a vehicle there can be 3 different kinds of OBD ECUs:
• Master ECU (one per vehicle), in WWH-OBD [3] referenced as VOBD
• Primary ECU (several per vehicle)
• Dependent / Secondary ECUs (several per vehicle)
From the Basic Software point of view Dependent / Secondary ECUs doesn’t
need any specific OBD functionality. In Dependent / Secondary ECUs are always
related to a Master or a Primary ECU. In Dependent / Secondary ECUs OBD-
relevant information will not be stored in the Basic Software (e.g. OBD events will be
forwarded to the respective Master or Primary ECU via the Bussystem). In Depen-
dent / Secondary ECUs this "reported errors" and other OBD functionality might
be handeled by a SW component.

AUTOSAR CP R20-11
The following table will give an overview about which OBD functionality must be sup-
ported in a Master ECU, Primary ECU or Dependent / Secondary ECU:
Functionality Master ECU Primary ECU Dependent /

Secondary ECU
OBD Event Memory Own and Own and No
“reported errors” “reported errors”
of Dep. / Sec of Dep. / Sec
ECUs ECUs
MIL Master Yes No No
Readiness per vehicle (PID $90) Yes No No
Readiness per ECU (PID $91) Yes Yes No
Vehicle OBD counters (PID $93) Yes No No
Calulation and provision of Yes No No
General Information (DYC, General
Nominator, PFC cycle,..)
Reception and execution of (Yes) Yes No
General Information (DYC, General
Nominator, PFC cycle,..)
Continuous-MI counter Yes No No
Cumulative Continuous-MI counter Yes No No
Calibration Identification (CAL-ID) Not in BSW Not in BSW Not in BSW
Calibration Verification Number Not in BSW Not in BSW Not in BSW
(CVN)
Table 7.3: Overview about OBD functionality in different OBD ECUs
The following OBD requierments are only valid for Master and Primary ECUs. If neces-
sary the OBD requierments differenciate between Master and Primary Requierment.
Master and Primary ECUs should have the same interface to the SWComponents. To
build a sufficant and lean Master ECU there is no compulsion to use this interfaces.
Some details on the interaction between Dem and specific SW-C might remain open,
since they are dependent on the Dem and SW-C implementation. The following func-
tionality is not defined:
• Malfunction Indicator Lamp (MIL)-activation (interface Dem to MIL handler, MIL-
bulb check, readiness blinking, blinking in case of catalyst damaging misfire,
Continuous-MI, Short-MI, On-demand MI,...)
• Misfire fault handling (common debouncing, filtering single / multiple misfire
faults).
However, this Dem SWS does not prescribe implementation details on how OBD com-
pliance can be achieved within the Dem module, e.g. concerning state handling. Fur-
thermore, the Dem SWS does not prescribe implementation details on the diagnostic
algorithms of the SW-C necessary to achieve OBD compliance (how to detect a fault,
when to trigger incrementation of IUMPR-numerator...).

AUTOSAR CP R20-11
In the following chapters, OBD relevant functionality and interfaces are described. It is
important to note, that independent of standard Autosar mechanisms (e.g. communica-
tion via RTE), response codes and timing constraints need to fulfill OBD requirements
(refer to [12] and [17]).
[SWS_Dem_01248] dThe configuration parameter DemOBDEventMemorySetRef
shall be used to reference to the one and only DemEventMemorySet that contains
OBD relevant information. All OBD operations of the Dem shall be only executed on this
DemEventMemorySet.c()
[SWS_Dem_00584] dWhile applying standard mechanisms (like Std_ReturnType), the
Dem module shall only return values ensuring OBD compliant behavior with regard to
permitted response codes and timing constraints.c()
Calulation and provision of General Information Data:
The Master ECU shall calculate and provide the following General Information Data via
the Bussystem to the Primary ECUs:
• OBD Driving cycle information (DYC)
• General Nominator / Rate-based monitoring - driving cycle (RBM cycle)
• Warm up cycle (WUC)
• Ignition cycle
• Qualified OBD Driving cycle
• Permanent fault code - driving cycle (PFC cycle)
OBD Driving cycle information (DYC)
The Master ECU will provide the driving cycle information (DYC) via the Busystem. The
driving cycle information (DYC) shall not be computed internally in the Primary ECUs.
General Nominator / Rate-based monitoring - driving cycle (RBM cycle)
Included in the IUMPR-Cycle Flag
Warm up cycle (WUC)
The warm up cycle (WUC) is a legally prescribed cycle and is computed by the Mas-
ter ECU. The Master ECU will provide the warm-up cycle information (WUC) via the
Busystem.
Ignition cycle
An ignition cycle describes the cycle between the “Terminal 15 on“ status and “Terminal
15 off“, including the shut down/after-run phase of the electronic control unit if the
engine start condition was met for at least 2 seconds after “Terminal 15 on“. The
Master ECU will provide the Ignition cycle information via the Busystem.
Qualified OBD Driving cycle
The Qualified OBD Driving cycle is a legally prescribed cycle and has the following
definition: For combustion engines (no hybrid): A driving cycle starts with “ignition on“
and ends with the next time “ignition on“ if the engine has reached the first engine start

AUTOSAR CP R20-11
conditions for at least 2 seconds (+/-a sec.) in between. Engine stops which are not
caused by the driver or ECU don’t end the driving cycle.
For hybrids and engines with shutoff strategies, the driving cycle is defined as the time
between “ignition on“ and the next time “ignition on“ after the driving cycle is qualified.
If a driving cycle is qualified every “ignition off > ignition on - EVENT“ results in the
beginning of a new driving cycle. This new driving shall be qualified. A driving cycle
is qualified when the engine speed has exceeded the minimum speed for engine start
conditions for at least 2 seconds (+/-a sec.) or condition ready for driving for at least 2
seconds (+/-a sec.)
Permanent fault code - driving cycle (PFC cycle)
(refer to chapter 7.9.5.8)
Note: Calibration Identification (CAL-ID) and Calibration Verification Number
(CVN)
The Calulation of the Calibration Identification (CAL-ID) and Calibration Verification
Number (CVN) is not a BSW Task and will not handled within the Dem.
7.9.2 PIDs provided by Dem
[SWS_Dem_00293] dFor the following PIDs the data layout shall be compliant to SAE
J1979DA [18].
• PID $01 monitor status since DTCs cleared (4 byte)
• PID $021 DTC that caused required freeze frame storage (2 byte)
• PID $1C OBD requirements to which vehicle or engine is certified (1 byte)
• PID $21 distance traveled while MIL is activated (2 byte)
• PID $30 number of warm-ups (WUC) since DTCs cleared (1 byte)
• PID $31 distance traveled since DTCs cleared (2 byte)
• PID $41 monitor status this driving cycle (4 byte)
• PID $4D engine run time while MIL is activated (2 byte)
• PID $4E engine run time since DTCs cleared (2 byte)
• PID $91 ECU OBD System Information (5 byte)
c()
Note: PID $90 and $93 are calculated in the application of the VOBD. Primary ECUs
only provides interfaces to retrieve the related data.
1
PID $02 is only required for service $02 and therefore no interface (like
Dem_DcmReadDataOfPID02) is necessary. Instead the API Dem_DcmGetDTCOfOBDFreezeFrame is
used (refer to[SWS_Dem_00623])

AUTOSAR CP R20-11
[SWS_Dem_CONSTR_06150] Dependency on container DemPidClass dThe con-

tainer DemPidClass and aggregated sub-container shall only be present if DemOBD-
Support is set to DEM_OBD_MASTER_ECU or DEM_OBD_PRIMARY_ECU.c()
[SWS_Dem_00351] dThe Dem module shall compute and provide the number of con-
firmed faults (PID $01, Byte A).c()
[SWS_Dem_01137] dFor WWH-OBD PID$01 shall not provide the number of confirmed
faults.c()
[SWS_Dem_01138] dThe Dem module shall compute and provide the ECU MIL status
(PID $01, Byte A).c()
[SWS_Dem_01139] dFor WWH-OBD PID$01 shall not provide the ECU MIL status.c()
[SWS_Dem_00748] dThe function Dem_DcmReadDataOfPID1C shall return the ap-
propriate value “OBD requirements to which vehicle or engine is certified.“ according
to the respective standards [12], e.g. OBD, OBDII, JOBD etc. The value PID1Cvalue
to return is in configuration parameter DemOBDCompliancy defined.c()
7.9.2.1 Centralized PID $21 / $31 / $4D / $4E handling
[SWS_Dem_00703] d The Dem of the Master ECU shall calculate information for PID
$31 / $4D / $4E vehicle wide.c()
A Primary ECU is not allowed to calculate information for PID $31 / $4D / $4E.
Note: Therefore a Software component of the Master ECU will use API
Dem_DcmReadDataOfPID<NN> (where NN is 31 / 4D / 4E) to read out the informa-
tion and will provide information about mileage / time for PID $31 / $4D / $4E to the
Primary ECU via the bussystem.
On receiving the information for PID $31 / $4D / $4E in a software component in the
Primary ECU via the bussystem, the software component will set the PID $31 / $4D
/ $4E in calling the API Dem_SetDataOfPID<NN> (where NN is 31 / 4D / 4E) of the
Dem of the Primary ECU.
[SWS_Dem_00704] dOnly the Master ECU is allowed to report information for PID
$31 / $4D / $4E to the scan tool.c()
Primary ECUs are not allowed report informations for PID $31 / $4D / $4E to the scan
tool.
On receiving the information for PID $21 in a software component in the Primary ECU
via the bussystem, the software component will set the PID $21 in calling the API
Dem_SetDataOfPID21 of the Dem of the Primary ECU.
[SWS_Dem_00346] dThe Dem module shall use PID $0D to calculate PID $21 and
PID $31.c()

AUTOSAR CP R20-11
[SWS_Dem_00304] dA Dem delivery shall provide function call interfaces to the Dcm
and the respective ServiceNeeds to declare to the Dcm that these PIDs are supported.c
()
[SWS_Dem_00347] dIf PID $1E (auxiliary input status) is supported the PTO (Power
Take Off) related event status handling shall implemented inside the Dem module (refer
to [19]).c()
[SWS_Dem_00377] dThe Dem module shall provide the interface Dem_SetPtoSta-
tus allowing a SWC implementing the PTO functionality to notify the Dem module if
PTO is active or inactive (refer to section 8).c()
[SWS_Dem_00378] dThe Dem module shall support the configuration parameter
DemConsiderPtoStatus indicating that a certain event is affected by the Dem PTO
handling.c()
The Dem module provides the configuration switch DemPTOSupport to enable or dis-
able the usage of PID $1E.
A special configuration is applied for the computation of PID $01 and $41:
[SWS_Dem_00349] dThe Dem module shall support the configuration parameter De-
mEventOBDReadinessGroup for OBD systems, to assign individual events to one
specific readiness group.c()
According to SAEJ1979 [17], the group AirCondition Component shall not be supported
anymore. However, it is still included in ISO 15031-5 [12]. The groups distinguish
between spark ignition engines (spark) and compression ignition engines (compr.).
However, it is necessary to configure per event, to which readiness group the monitor
contributes (if at all).
PID $21 handling
PID $21 is either reported only by the OBD Master ECU, or a synchronized valued by
all OBD ECUs (centralized PID handling).
If the configuration switch DemOBDCentralizedPID21Handling is enabled:
A Software component of the OBD Master ECU could retrieve the current PID $21
value via the interface GetDataOfPID21 from Dem module with the goal to distribute
the value to all other Primary ECUs in the vehicle.
A Software component of the OBD Primary ECU receiving the information for PID $21
could forward this information to the Dem module via the interface SetDataOfPID21
to synchronize the value with the OBD Master ECU.
[SWS_Dem_01095] dOn invocation of Dem_SetDataOfPID21 the internal PID $21
value shall be updated.c()

AUTOSAR CP R20-11
Note: AUTOSAR defines that OBD Primary ECUs do not calculate the PID $21 value
by its own.
[SWS_Dem_01096] dAn OBD Master ECU shall calculate the PID $21 value by its
own (considering [SWS_Dem_00346]).c()
[SWS_Dem_01097] dOn invocation of Dem_GetDataOfPID21 the internal calculated
PID $21 value shall be returned.c()
Note: AUTOSAR defines that OBD Primary ECUs do not calculate the PID $21 value
by its own.
[SWS_Dem_01098] dOn invocation of Dem_DcmReadDataOfPID21 the Dem shall re-
turn the current value of PID $21.c()
[SWS_Dem_01099] dIf Dem_DcmReadDataOfPID21 is called before Dem_Set-
DataOfPID21, the Dem shall return 0xFFFF as PID $21 value.c()
7.9.3 Readiness status
[SWS_Dem_00354] dThe Dem module shall compute for PID $01 the readiness status
(if all events of a DemEventOBDReadinessGroup are reported as OK tested since
last clear, or the event has caused MIL on). Suppressed Events shall be ignored for
this computation.c()
Note: DemEventOBDReadinessGroup has a regulation background and special
computations based on ModelYear (MY) and Market.
[SWS_Dem_CONSTR_06147] Dependency for DemEventOBDReadinessGroup d
DemEventOBDReadinessGroup shall only be present if DemOBDSupport is set to
DEM_OBD_MASTER_ECU.c()
[SWS_Dem_00355] dThe Dem module shall compute for PID $41 the readiness group
complete for current driving cycle (if all events of a group are tested in the current
driving cycle). OBD Events Suppression shall be ignored for this computation.c()
Note: For calculation of the group readiness, the Dem module considers all events
assigned to the specific readiness group.
[SWS_Dem_00356] dThe Dem module shall compute the readiness group disabled (if
the disabled status is reported by the monitor for any event of a group). OBD Events
Suppression shall be ignored for this computation.c()

AUTOSAR CP R20-11
[SWS_Dem_00348] dThe Dem module shall provide the disabling of events (refer to
Dem_SetEventDisabled). OBD Events Suppression shall be ignored for this com-
putation.c()
[SWS_Dem_00294] dIn order to allow a monitor to report that the event cannot be
computed in the driving cycle (aborted e.g. due to physical reasons), the Dem shall
provide the API Dem_SetEventDisabled.c()
Note: For the computation of PID $41, the monitor has to report its event as disabled,
if the test cannot be carried out anymore until the end of this driving cycle.
Note: SetEventDisabled does report an Event as “uncompletable“ during the current
driving cycle. It does not turn the Event into a Events Suppression according to chapter
7.4.8
SW-C 1 SW-C 2 SW-C 3
[DiagnosticMonitor]
à SetEventDisabled()
[DiagnosticMonitor]
RTE -> SetEventStatus()
Dem_DcmReadDataOfPID01()
Dem Dcm
Dem_DcmReadDataOfPID41()
Figure 7.44: Dem calculates PID$01 and PID$41 data based on specific port operations
7.9.4 In-Use-Monitor Performance Ratio (IUMPR) Support
The In-Use-Monitor Performance Ratio (IUMPR) indicates how often the OBD system
monitors particular components, compared to the amount of the vehicle operation. It is
defined as the number of times a fault could have been found (=numerator), divided by
the number of times the vehicle operation conditions have been fulfilled (=denominator)
as defined in the respective OBD regulations.

AUTOSAR CP R20-11
The IUMPR will be calculated within the ECU using the following formula: In-Use-
Monitor Performance Ratio = NUMERATOR / DENOMINATOR
[SWS_Dem_00709] dRatios which refer to a Suppressed Event shall not be com-
puted.c()
[SWS_Dem_00710] dThe numerator shall be calculated in the ECU (Master and Pri-
mary).c()
[SWS_Dem_00711] dThe Dem of the Master ECU shall calulate the IUMPR-Cycle
Flag.c()
[SWS_Dem_00966] dThe Dem shall provide an API Dem_GetIUMPRDenCondition
to give a software component the possibility to get the General Denominator status
information.c()
The Master ECU (software component) will provide the IUMPR-Cycle Flag (included in
the General Denominator signal) via the bus system.
[SWS_Dem_00712] dIn master and optionally primary OBD ECUs, the Dem shall incre-
ment ECU global internal general denominator depending on the denominator
DEM_IUMPR_GENERAL_OBDCOND, if available. Depending on the system definition the
global general denominator (and therefore the DEM_IUMPR_GENERAL_OBDCOND) may
not be needed in some or even all primary ECUs. In such cases the DEM_IUMPR_-
GENERAL_OBDCOND is never set, and the general denominator is stuck at 0 (and
reporting of the InfoType $08 / $0B is disabled in the Dcm).c()
[SWS_Dem_01236] dThe Dem shall increment monitor internal denominators depend-
ing on the DEM_IUMPR_GENERAL_INDIVIDUAL_DENOMINATOR, and additional con-
ditions if configured in DemIUMPRDenGroup a maximum of once per driving cycle, and
shall consider monitor specific conditions only for the cycle the Release operation was
called in.c()
[SWS_Dem_00714] dThe Dem shall provide an API Dem_SetIUMPRDenCondition
to get informed about the IUMPR-Cycle Flag status by a software component.c()
Note: A Timeout of the IUMPR-Cycle Flag / General Denominator signal of the Master
will lead to an event memory entry in the COM Stack (timeout of signal) in the
Primary ECU.
Further details concerning In-Use-Monitor Performance Ratio (IUMPR) can be found
in regulation documentation.
Differencation InfoType $08 / InfoType $0B
The IUMPR-data collected need to be provided upon a service $09 request. For gaso-
line engines, the Info Type $08 is used and for diesel engines the Info Type $0B is used
(refer to [12] and [17]).
[SWS_Dem_00298] dIn order to support the data requests in service $09 as de-
scribed above, the Dem shall provide the API Dem_DcmGetInfoTypeValue08 or
Dem_DcmGetInfoTypeValue0B to the Dcm.c()

AUTOSAR CP R20-11
[SWS_Dem_00357] dIf the DemOBDEngineType is set to DEM_IGNITION_SPARK the

Dem module shall provide the API Dem_DcmGetInfoTypeValue08 for InfoType $08
IUMPR data.c()
Note: The service Dem_DcmGetInfoTypeValue08 will be used by the Dcm, to re-
quest the IUMPR-data according to the InfoType $08 data format used for the output
to service $09.
[SWS_Dem_00358] dIf the DemOBDEngineType is set to DEM_IGNITION_COM-
PRESSION the Dem module shall provide the API Dem_DcmGetInfoTypeValue0B
for Info Type $0B IUMPR data.c()
Note: The API Dem_DcmGetInfoTypeValue0B will be used by the Dcm, to request
the IUMPRdata according to the InfoType $0B data format used for the output to ser-
vice $09.
The type of OBD system is defined by using the configuration switch DemOBDSupport
(refer to DemGeneral).
In-Use-Monitor Performace Ratio (IUMPR) groups or components
The relevant In-Use-Monitor Performace Ratio (IUMPR) data recording is allocated in
the Dem based on FIDs and events. The IUMPR data are recorded for different groups
or components respectively.
Typically, one or more events serve for the monitoring of these components, e.g. the
oxygen sensor. Hence, in order to record the in-use performance of the OBD-system,
the test performance of all the relevant events for all the IUMPR-groups needs to be
recorded. For that purpose, certain data structures need to be configured by the Dem.
However, in order to stop the incrementing of numerator and denominator in the case a
monitor is stopped, due to the occurrence of another event preventing the monitor from
running, it is necessary to list all events that can affect the computation of a particular
IUMPRrelevant event. However, this information is already embodied in a FID (refer to
FiM SWS) representing a function which serves for the computation e.g. of a particular
even. A FID is inhibited in case of certain events and thus, this relation can also be
used to stop the IUMPR record.
This leads to a combination of an event to be recorded and a primary FID (and option-
ally multiple secondary FIDs) representing all the events stopping the computation of
the IUMPR-event. For the purpose of classifying the events into groups, an IUMPR-
group is also part of this combination.
For the configuration of data structure per EventId / FID(s) / IUMPR-group combination,
a new data object is introduced, namely, the RatioId (refer to DemRatioId). Thus, the
container DemRatio contains the EventId, primary FID, secondary FIDs, IUMPR-group
and an interface option to configure “APIuse“ vs. “observer“, whereas the interface
option is explained in more detail in the following.
Also for the purpose of the port configuration, an ObdRatioServiceNeeds is offered to
the SW-C. If a SW-C is IUMPRrelevant, this ServiceNeed is filled out.

AUTOSAR CP R20-11
If the monitor is “symmetric“, i.e. upon completion of the test a fault could have been
found, even if there is currently no fault in the system, then the numerator can be
incremented just by observing the TESTED-status of the assigned event.
[SWS_Dem_00359] dOnly for monitors being configured with the option “observer“,
the Dem module shall increment the numerator of the corresponding monitor, if the
assigned event gets tested/qualified (as passed or failed).c()
If the diagnostic is asymmetric and it takes more efforts to detect a malfunction than
to detect an OK status, the monitor needs to call an API in order to report that a
malfunction could have been found, because this may require some simulation within
the monitor and can therefore not be purely derived from the TESTED status.
[SWS_Dem_00360] dFor OBD relevant systems the Dem module shall provide the API
Dem_RepIUMPRFaultDetect.c()
[SWS_Dem_00296] dThe Dem module shall provide the API Dem_RepIUMPRFault-
Detect for the asymmetric monitor to report that a malfunction could have been
found.c()
Note: This service shall be used by the monitor to report that a fault could have been
found even if there is currently no fault at all according to the IUMPR regulations that
all conditions are met for the detection of a malfunction.
[SWS_Dem_01188] dThe Dem shall increment the ratio-individual IUMPR-numerator
at maximum of one time per OBD driving cycle.c()
DemRatioKind, to indicate per RatioId if the numerator is calculated based on the
TESTED-status or the API call.c()
Additional denominator conditions:
For some particular monitors (e.g. for secondary air system, comprehensive compo-
nents), there are additional conditions defined on the denominator: Their denominator
will only be incremented if certain temperature or activity conditions are met. Then, the
monitor needs unlock (Release) the denominator when the additional conditions are
met in a driving cycle.
In case of a fault being detected that prevents further computations of these additional
denominator conditions, the numerator is required to be frozen as well. For that reason
it is necessary to assign particular denominator conditions if applicable. Upon the
report of an inhibited computation of a particular denominator condition, the affected
ratio are set to frozen,
For this handling of commonly used denominator conditions within the Dem, further
interfaces and configuration items are introduced.
[SWS_Dem_00715] dThe Dem module shall provide configuration parameter DemI-
UMPRDenGroup to offer several conditions to be applied to the denominator per Ra-
tioId.c()

AUTOSAR CP R20-11
[SWS_Dem_00362] dThe Dem module shall provide the APIs for releasing (refer to
Dem_RepIUMPRDenRelease) the denominator under special conditions if the DemI-
UMPRDenGroup is configured as DEM_IUMPR_DEN_PHYS_API.c()
[SWS_Dem_00308] dThe Dem shall provide the API Dem_RepIUMPRDenRelease to
IUMPRrelevant SW-C, to control the denominator specific to the respective RatioId.c()
Note: This service shall be used by the monitor to report, that a denominator of a
specific monitor (represented by FID and EventId) is released for physical reasons.
In systems with multiple ECUs being OBD relevant and even IUMPR relevant, the
status information on the additional denominator conditions needs to be communicated
to synchronize the behavior of the counters. For that reason, an additional interface is
introduced to read out and to report the status of the individual denominator conditions.
[SWS_Dem_00716] dThe Dem shall provide the API Dem_GetIUMPRDenCondition
to read out the status of a particular condition.c()
[SWS_Dem_00717] dThe Dem shall provide the API Dem_SetIUMPRDenCondition
to set the status of a particular condition (mainly in depending ECUs).c()
Note: To comuincate the received general denominator status, the Primary ECU should
make use existing API as offered for SWCs.
Legislation requires that IUMPR tracking shall be stopped for a specific monitor, if it is
inhibited by another service $07 visible fault.
[SWS_Dem_01392] dThe IUMPR ratio shall be blocked whenever any of the Events
linked (via FunctionInhibitionConfiguration or through SummaryEvents) to one of the
FIDs referenced by DemFunctionIdRef is in state PENDING, or any other event
causal to this event (according to component dependency structure) is in state PEND-
ING (see DemComponentClassRef referenced by DemDiagnosticEventRef).c()
[SWS_Dem_00299] dAs long as an event has Pending status, the Dem module shall
stop increasing the numerator and denominator.c()
Based on the related FID (FiM access) and RatioId, the Dem module can determine
which numerator and denominator has to be stopped.

AUTOSAR CP R20-11
[IUMPRNumerator]
à RepIUMPRFaultDetect()
No API !
RTE Observe event status
Dem_DcmGetInfoTypeValue08()
Dcm
Dem
Exchange of inhibit matrix

FiM
Figure 7.45: Dem calculates IUMPR data based on specific interface operations
7.9.5 OBD for light duty (OBD2)
Together with the Dcm, this Dem SWS provides standardized AUTOSAR interfaces to
support the OBD services $01 - $0A defined in SAE J1979 [17]. With these services,
Autosar OBD functionality shall be capable of meeting all light duty OBD regulations
worldwide (California OBDII, EOBD, Japan OBD, and all others.)
[SWS_Dem_CONSTR_06148] Dependency on container DemRation dThe con-
tainer DemRatio shall only be available if DemOBDSupport is set to DEM_OBD_MAS-
TER_ECU.c()
7.9.5.1 Service $01 Read Current Powertrain Diagnostic Data
With Service $01, the current value of any PID (except PID $02) can be read. For each
PID calculated by the Dem, a dedicated API function Dem_DcmReadDataOfPID<NN>
as described in chapter 7.9.2 is provided.

AUTOSAR CP R20-11
7.9.5.2 Service $02 Read Powertrain Freeze Frame Data
In order to retrieve relevant data a fault entry, the Dem needs access to current data,
addressed via PIDs. For that purpose, a Client (=Dcm/Dem)/Server (=SW-C) interface
is assigned based on configuration items.
[SWS_Dem_00291] dThe Dem module shall support only the legislative freeze frame
(record number 0). This will be a single list of PIDs assigned to this freeze frame (refer
to DemPidClass).c()
This means a request by a generic scan tool for record number one and above will be
ignored.
Upon the entry of a fault in the memory, the values of these PIDs/DIDs are requested
through the RTE via a client server interface.
[CSDataServices_<...>]
RTE à ReadData()
Dem Dcm
Figure 7.46: Dem and Dcm module requests PID data elements of SW-C via ReadData
operation
[SWS_Dem_00596] dThe Dem module shall provide access on PID data elements of
the most important freeze frame being selected for the output of service $02 (OBD
freeze frame of the event which caused MIL on) to the Dcm module (refer to Dem_-
DcmReadDataOfOBDFreezeFrame).c()
Note: The Dem processes and stores only the raw data for service $02. Any PID
header-information and fill bytes are added by the Dcm. The Dcm configuration defines
the individual PID layout, which also defines an order of the contained data elements.
Each data element references to its linked element in the Dem configuration (refer to
Figure 47).
The individual data elements of a PID are selected via an index by the Dcm.
[SWS_Dem_00597] dThe index values (refer to API parameter DataElementIndexOf-
PID) of Dem_DcmReadDataOfOBDFreezeFrame shall be assigned zerobased and

AUTOSAR CP R20-11
consecutive. Their order shall be derived from the position of the data elements (refer
to DcmDspPidDataPos, of the referencing DcmDspPidData containers) in the Dcm’s
PID layout.c()
Note: This index is not configured explicitly (to be able to avoid resource overhead for
e.g. mapping tables in the implementation).
DataElementIndexOfPID
DataElementIndexOfPID
(implicit index)
(implicit index)
Dem PID configuration Dcm PID configuration
DemPidClass DcmDspPid (PID layout)
DcmDspPidData/
DemPidDataElement/ DcmDspPidData/ DcmDspPidData/ DcmDspPidDataPos
ShortName DcmDspPidDataDemRef ShortName (Example)
0 DataElement M reference to DataElement M 8 result 0
3 DataElement P DataElement L 24 result 2
2 DataElement L DataElement O 16 result 1
1 DataElement O DataElement P 32 result 3
Figure 7.47: PID layout configuration within Dcm (master) and Dem
[SWS_Dem_00623] dThe function Dem_DcmGetDTCOfOBDFreezeFrame shall return

the DTC associated with the most important freeze frame being selected for the output
of service $02 (PID $02).c()
7.9.5.3 Service $03 - Read Emission-Related Powertrain Diagnostic Trouble

Codes
The diagnostic service provides the OBD DTCs where the UDS status bit 3 is
currently set. Therefore the interfaces described in chapter 8.3.4.1 will be used by
Dcm.
7.9.5.4 Service $04 - Clear Reset Emission-Related Diagnostic Information
[SWS_Dem_00718] dIn Master, Primary and Dependent / Secondary ECUs ex-

ecuting service $04 shall clear all emission-related diagnostic information in primary
and user defined (event) memory (if configured) as defined in SAE J1979 [17].c()
[SWS_Dem_00719] dExecuting service $04 shall include non emissionrelated diag-
nostic information (e.g. Debouncing counter, Event/DTC related status information as

AUTOSAR CP R20-11
TestFailedSinceLastClear) of primary and all user defined event memories (if con-
figured) in Master, Primary and Dependent / Secondary ECUs.c()
7.9.5.5 Service $06 - Support of central DTR handling
With Service $06, an external test tool can request an emissionrelated ECU to return
the supported OBDMIDs (“OBD Monitor Identifier”) and / or the standardized diagnostic
test results associated with the OBDMID.
The OBD related standards (refer to ISO 15031-5 [12] and SAE J1979 [17]) reserve
certain OBDMIDs for the special purpose of obtaining the list of supported OBDMIDs
within the vehicle. These OBDMIDs are called “availability OBDMIDs” and are num-
bered with $00, $20, $40, $60, $80, $A0, $C0 and $E0.
In contrast to earlier Autosar releases, the Dem additionally provides interfaces to re-
port latest test results handled per particular identifier (DTR “Diagnostic Test Result“)
introduced for that purpose.
Within the Service $06, the response (apart from the support information) consists of a
data triple with test result, lower and upper limit representing the latest result of a con-
ducted and qualified monitoring check. In order to refer to a particular component and
a particular certified test, the response also contains the OBDMID and the TID (“Test
Identifier“). For the external representation of the data, a socalled UnitandScalingID
(UaSID) is passed along with the response onto the tester. From OBD regulation point
of view it is required to have consistent data in Service$06 and Service$07. And in this
scenario, a test has failed if the test result is either less than the lower limit or higher
than the upper limit. Along with this violation of the thresholds, a corresponding Event
has to be reported and vice versa. Note that this consistency is valid strictly only upon
first detection of the malfunction, since a healing from Service$07 takes one entire cy-
cle without a failure detected while the Service$06 contents simply represent the latest
test result.
In order to support this consistency requirement, the Dem provides a specific interface
to report the results per DTR whereas an Event is associated to a DTR on configuration
level to refer to.
Note that the Event serves as master and within its status additional effects such as
enable / storage conditions are encountered. Given a specific DTR update type (by
configuration), the UDS status (Tested, Failed, debounce status etc.) decides whether
a DTR result being reported is further processed or suppressed/ignored.
The Dem offers a service of conversion for the SWC to support a report of test re-
sults and thresholds within the ECU-internal resolution. The conversion onto the tar-
get format (standardized by [17, 19]: uint16, formula according to UaSID) including
a correction in case of rounding effects is done within the Dem. For that reason the
configuration includes a conversion formula similar to the one used by the RTE to de-
scribe physical data (but simpler) where only a linear mapping is supported. Note that
the conversion does not respect the UaSId. The service Need for the DTR provides a

AUTOSAR CP R20-11
reference to a physical unit (see SWC Template chapter “Physical Units“) and a linear
conversion (see SWC Template chapter “Computation Methods“) of CompuRational-
Coeffs with a maximum of two numerator coefficients and one denominator coefficient,
as well as the desired UaSId During the configuration process, this information is pro-
cessed into a single linear conversion, which is then stored inside the ECUC of the
Dem.
By this central data handling, the aspect of data consistency for Service$07 / $06 is
supported as well as reset in case of fault clear.
[SWS_Dem_00751] dThe Dem shall provide data structures and functionality to re-
ceive, store and report Service$06 test results persistently.c()
[SWS_Dem_00752] dThe DemDtrId is assigned by the Dem during the BSW configu-
ration step.c(RS_Diag_04129)
Note: The Dem refers to a BSW configuration DemDtr which associates
• a DemDtrId to an EventId
• an indication whether the Monitor will provide data for the minimum limit, maxi-
mum limit, or both
• OBDMID
• TID
• UaSID
• DemDtrUpdateKind
• Coefficients for linear conversion analogous to the SW-C Description (chapter
5.5.)
[SWS_Dem_00753] dFor ensuring data consistency, an EventId can only be refer-
enced by at maximum one DTR.c()
[SWS_Dem_00754] dThe Dem shall use the DemDtrUpdateKind for the evaluation
and processing of reported DTR-values:
• DEM_DTR_UPDATE_ALWAYS: State of the event is not considered (default, and
used if DemDtrEventRef is not configured).
• DEM_DTR_UPDATE_STEADY: Only when the events pre-debouncing within Dem
is “stuck“ at the FAIL or PASS limit, and the latest result matches the debouncing
direction.
c()
[SWS_Dem_00755] dThe Dem shall only support a linear mapping, i.e. only support
values for the coefficients b, c, and f.c()
Note: ASAM formula coefficients: (ax2 + bx + c) / (dx2 2 + ex + f) supporting on b, c and
f.

AUTOSAR CP R20-11
[SWS_Dem_00756] dThe Dem shall provide an API Dem_SetDTR within an interface

DTRCentralReport to provide a report mechanism to the SWC for their test results.
Arguments shall be the DemDtrId, the test value, the minimum and maximum limit,
and a state indicating whether the monitor provides a valid minimum limit, maximum
limit, or both, or whether the reported values shall be reset to zero.c(RS_Diag_04179)
[SWS_Dem_00757] dIf DemDtrEventRef references a DemEventParameter, the
Dem shall process the reported DTR values only if all the enable/storage conditions of
the referenced event are fulfilled, independent of DemDtrUpdateKind. If any of the
enable/storage conditions of the referenced event are not fulfilled, then the Dem shall
ignore the reported DTR values.c()
Note the example with DEM_DTR_UPDATE_STEADY: If an event has reached that status
TESTED starting from an initialized state but has not detected a FAILED, the received
DTR values within the limits are processed (=converted and stored). If the test result
violates its associated limit (cf. control value) while the eventis indeed TESTED and
FAILED, the DTR report is processed as well. But if the test result violates its associated
limit (cf. control value) while the event is TESTED and PASSED, the DTR report is
ignored assuming that the EventId is also not updated for good reasons (cf. enable /
storage conditions).
Applying this validation check within the DTR report, the data consistency in Service$06
and $07 is ensured.
[SWS_Dem_00758] dThe Dem shall support a conversion of the ECUinternal resolu-
tion into the standardized external uint16 size and resolution according to the config-
ured and standardized UaSID. For that reason, the conversion formula is configured
per DTR. It is assumed that the conveyed parameter of the API call contain the values
in the internal size and resolution. The Dem does offer sint32 as parameter for that
reason to cover uint16 as well as sint16 (or even sint32) internal data types.c()
[SWS_Dem_00759] dThe Dem shall ensure the validity of the test results vs. thresh-
old(s). If the parameter TestResult passed in Dem_SetDTR is inside/outside the
thresholds given by UpperLimit and LowerLimit, Testvalue of Dem_DcmGet-
DTRData shall also be inside/outside Upplimvalue and Lowlimvalue. If rounding
effects lead to an unintended change of the meaning, the thresholds shall be shifted
by one increment accordingly to restore the result.c(RS_Diag_04179)
[SWS_Dem_00760] Computing available OBD MID values dIf Dem_DcmGetAvail-
ableOBDMIDs is called with an "availablity Obdmid" value of 0x00, 0x20, 0x40, 0x60,
0x80, 0xA0, 0xC0 or 0xE0 and the Dem has configured DemDtrMid, the Dem shall
compute and provide the “Supported-OBDMID” information in the OUT parameter Ob-
dmidvalue and return E_OK. The computed Obdmids parameter is according to ISO
15031-5[12] and sets a bit for each supported Obdmid in the request range (starting
with Obdmid+1) and having the last bit of the Obdmidvalue set, if any subsequent
range has configured Obdmids.c()
[SWS_Dem_01301] Behavior on invalid Obdmid value dIf Dem_DcmGetAvail-
ableOBDMIDs is called with an invalid Obdmid value which is different to 0x00, 0x20,

AUTOSAR CP R20-11
0x40, 0x60, 0x80, 0xA0, 0xC0 or 0xE0, the Dem shall report the Det development error
DEM_E_INVALID_OBDMID.c()
[SWS_Dem_00761] dUpon request by the Dcm, the Dem shall repond with the number
of TIDs per requested OBDMID using the API Dem_DcmGetNumTIDsOfOBDMID. This
value can be used by the Dcm to iteratively request for the DTR data per OBDMID /
TID-index whereas the TID-index loops from 0 to number-of-TIDs minus one.c()
[SWS_Dem_00762] dUpon request by the Dcm, the Dem shall respond with the data
available for a particular OBDMID / TIDindex per requested OBDMID using the API
Dem_DcmGetDTRData. This value can be used by the Dcm to iteratively request for
the DTR data per OBDMID / TIDindex starting from 0 to numberofTIDs minus one.c()
[SWS_Dem_00763] dThe Dem shall reset the DTR data using the reference to the Event
per DTR, whenever the Event is affected by a fault clear command.c()
[SWS_Dem_00764] dIf no Event is assigned per DTR, the Dem shall reset the DTR
data upon a Service$04 clear command by the Dcm, i.e. a Dem_ClearDTC with:
DTC = DEM_DTC_GROUP_ALL_DTCS
DTCFormat = DEM_DTC_FORMAT_OBD
DTCOrigin = DEM_DTC_ORIGIN_PRIMARY_MEMORY
c()
[SWS_Dem_CONSTR_06149] Dependency on container DemDtr dThe container
DemDtr shall only be available if DemOBDSupport is set to DEM_OBD_MASTER_ECU
or DEM_OBD_PRIMARY_ECU.c()
A DTR can refer to an event via DemDtrEventRef. The referenced event can be
unavailable according to chapter chapter 7.4.8. In this case the Dem treats the DTR as
not supported and will neither compute the DTR or report a result of it.
[SWS_Dem_01335] Setting DTR results for unavailable events dIf Dem_SetDTR is
called for an DTR that references via DemDtrEventRef an event that itself is config-
ured with DemEventAvailable to FALSE, the Dem shall return E_NOT_OK and not
compute the DTR.c(RS_Diag_04126)
[SWS_Dem_01336] Reporting DTRs for unavailable events dIf Dem_DcmGetDTR-
Data is called for an DTR that references via DemDtrEventRef an event that itself is
configured with DemEventAvailable to FALSE, the Dem shall return E_NOT_OK. In
this case all the out-parameters of Dem_DcmGetDTRData are undefined.c(RS_Diag_-
04126)

AUTOSAR CP R20-11
7.9.5.6 Service $07 - Read emission-related diagnostic trouble codes detected

during during current or last completed driving cycle
The diagnostic service provides the OBD DTCs where the DTC Status bit 2 (Pend-
ingDTC) is currently set. Therefore the interfaces described in chapter 8.3.4.1 will be
used by Dcm.
7.9.5.7 Service $0A - Read Emission-Related Diagnostic Trouble Codes with

Permanent Status
Permanent DTCs are stored in the permanent fault memory.

An OBD related DTC entering the permanent fault memory with illuminating the MIL
and leaving it with deactivating the MIL.
The permanent fault memory is robust against ClearDTC and Power Fail. After a
ClearDTC an event can only be removed from the permanent fault memory under
special conditions. This special conditions are defined by the OBD regulation.
[SWS_Dem_00300] dThe Dem shall be able to handle Permanent DTCs according to
regulations (refer to [20]) within the specific event memory type "permanent".c()
[SWS_Dem_00590] dEvents that have been confirmed and activate the MIL, shall be
stored robustly against ClearDTC or powerfail (for details confer [20]).c()
For details refer to OBDrelevant DTCs, chapter 7.4.1.
[SWS_Dem_00301] dThe Dem shall provide the ability to access the non-volatile stored
Permanent DTC by filtering for permanent DTCs to the Dcm (refer to Dem_SetDTCFil-
ter and Dem_GetNextFilteredDTC).c()
Note: For service $0A, the Dcm uses the DTCOrigin DEM_DTC_ORIGIN_PERMA-
NENT_MEMORY.
[SWS_Dem_01076] dNew permanent faults of the current driving cycle shall be re-
ported to the Dcm service $0A request latest after the next OBD driving cycle starts.c
()
[SWS_Dem_01077] dNew permanent faults shall be stored in non-volatile memory
(Next Driving Cycle after WriteAll or after positive Callback from NvM) latest at ECU
shutdown.c()
In a Master ECU the interface Dem_GetCycleQualified can be used to read the
current state of the PFC cycle, providing the operation cycle id of the DemOBDPFC-
CycleRef. A value of TRUE in isQualified indicates that during the current OBD
driving cycle the conditions for the PFC cycle have been met.

AUTOSAR CP R20-11
Note: A SWC on the MIL Master Ecu forwards the information "Minimum trip conditions
satisfied" (PFC cycle) via Bussystem to the primary ECUs.
Note: A software component in the Master ECU optionally polls the API Dem_GetCy-
cleQualified and send the information via the bussystem.
In a primary ECU the interface Dem_GetCycleQualified can be used to get in-
formed that the current OBD driving cycle has met the criteria for the PFC cycle by a
software component.
7.9.5.8 MIL Handling
Typically, the “MIL Master functionality“ is located in the OBD master ECU. Only the
MIL master functionality is allowed to send the MIL request to the instrument cluster.
Therefore in primary ECUs the function Dem_GetIndicatorStatus can be used
to poll the MIL indicator status and send the information to the “MIL Master functional-
ity“ (e.g. located in the master ECU).
7.9.6 WWH-OBD
7.9.6.1 DTC WWHOBD class
[SWS_Dem_01140] dThe Dem shall provide a class value per DTC (to characterize the
impact of a malfunction OBD system’s monitoring capability) according to ISO 14229-1
[1], Annex D.3 “DTCSeverityMask and DTC class information bit definitions” (refer to
Dem_GetSeverityOfDTC and Dem_GetNextFilteredDTCAndSeverity), only if
configured for at least one DTC.c()
[SWS_Dem_CONSTR_6109] dThe DTC class is only available for ISO 14229-1 [1]
DTCs. It is configurable per DTC optionally (refer to DemWWHOBDDTCClass).c()
[SWS_Dem_CONSTR_6110] dThe WWH-OBD DTC priority shall be according table
Table 7.4.c()
WWH-OBD DTC class Priority

A > B1 DTC
B1 > B2 DTC
B2 > C DTC
C > no OBD DTC
Table 7.4: WWH-OBD DTC priority
Note : ISO 27145-3 [21]defines the following DTC Classes utilizing the severity levels:
No Class, Class A, Class B1, Class B2 and Class C.

AUTOSAR CP R20-11
7.9.6.2 Continuous-MI counter
The counter Continuous-MI counter is representing the number of engine hours

during which the MIL was continuously commanded to be on.
[SWS_Dem_01141] dIf Activation Mode 4 becomes active the counter shall be reset
to 0.c()
[SWS_Dem_01142] dThe counter shall increment for each engine operating hour dur-
ing which the event is detected and the Continuous-MI is commanded to be on.c()
[SWS_Dem_01143] dThe counter shall halt its value when the Continuous-MI is no
longer commanded to be on.c()
[SWS_Dem_01144] dThe counter shall continue its incrementation if the Continuous-
MI is again commanded on within three operation sequences.c()
[SWS_Dem_01145] dThe counter shall reset to zero and start incrementing its value
if the Continuous-MI is again commanded on after more than three operation se-
quences.c()
[SWS_Dem_01146] dThe counter shall reset to zero if the Continuous-MI is not com-
manded on after more than 40 warm-up cycles or after more than 200 engine operating
hours or upon a ClearDTC request.c()
[SWS_Dem_01147] dThe counter shall be reported as a two byte value. If any count
operation occurs which would cause a counter to roll over past 0x00FF then the count
value shall instead be maintained at 0x00FF.c()
[SWS_Dem_01148] dThe counter shall be stored non-volatile.c()
7.9.6.3 Cumulative Continuous-MI counter (Master ECU)
The counter Cumulative Continuous-MI counter is representing the number of

engine hours during which MIL has been continuously commanded to be on during its
lifetime. The counter shall only be implemented in the VOBD.
[SWS_Dem_01149] dThe counter shall increment for each engine operating hour dur-
ing which the event is detected and the Continuous-MI is commanded to be on,c()
[SWS_Dem_01150] dThe counter shall halt its value when the Continuous-MI is no
longer commanded to be on,c()
[SWS_Dem_01151] dThe counter shall never be reset.c()
[SWS_Dem_01152] dThe counter shall be reported as a two byte value. If any count
operation occurs which would cause a counter to roll over past 0x00FF then the count
value shall instead be maintained at 0x00FF.c()
[SWS_Dem_01153] dThe counter shall be stored non-volatile.c()

AUTOSAR CP R20-11
7.9.6.4 Class B1 counter
The Class B1 counter is representing the number of engine hours during which a
Class B1 has been Confirmed and TestFailed. The counter can be implemented as
global, i.e. one counter per ECU or local, i.e. one counter per B1 Event. The Dem
module supports only the global B1 counter.
[SWS_Dem_01154] dThe B1 counter shall increment for each 1 hour engine oper-
ating hour during which at least one Class B1 event is detected as Confirmed and
TestFailed.c()
[SWS_Dem_01155] dThe B1 counter shall latch its value when no Class B1 event is
no longer detected as Confirmed and TestFailed or after a ClearDTC request.c()
The B1 counter continue its incrementation if a Class B1 event is again detected as
Confirmed and TestFailed.
[SWS_Dem_01156] dThe B1 counter shall reset to zero after three consecutive oper-
ating sequences where no Class B1 event have been detected.c()
[SWS_Dem_01157] dIf B1 Counter exceeds 200 engine operating hours and no Class
B1 event have been detected the counter shall be set to 190.c()
[SWS_Dem_01158] dThe B1 counter shall be reported as a two byte value. If any
count operation occurs which would cause a counter to roll over past 0x00FF then the
count value shall instead be latched at 0x00FF.c()
[SWS_Dem_01159] dThe B1 counter shall be stored non-volatile.c()
7.9.6.5 Activation Mode
Activation Mode Escalation
[SWS_Dem_01160] dIf the B1 counter exceeds 200 engine operating hours the Ac-
tivation Mode 4 shall be active.c()
[SWS_Dem_01161] dIf at least one Class A event is Confirmed and TestFailed the
Activation Mode 4 shall be active.c()

AUTOSAR CP R20-11
Activation Mode Deescalation/ Healing
[SWS_Dem_01162] dIf Activation Mode 4 is active and no Activation Mode

4 relevant condition is present anymore, then the Activation Mode 3 shall be acti-
vated.c()
[SWS_Dem_01163] dIf Activation Mode 4 has been degraded to Activation
Mode 3 and an Activation Mode 4 relevant event is confirmed the Activa-
tion Mode 4 shall be reactivated if the configured value of EventFailureCycleCoun-
terThreshold is reached.c()
[SWS_Dem_01164] dIf Activation Mode 3 is active and no Activation Mode
3 and Activation Mode 4 relevant condition is present, then the Activation
Mode 1 shall be set.c()
[SWS_Dem_01165] dIf an Class C event is Confirmed and TestFailed and no Acti-
vation Mode 3 or Activation Mode 4 is active, the Activation Mode 2 shall
be set to active.c()
[SWS_Dem_01166] dThe function Dem_GetIndicatorStatus shall return the cur-
rent "indicator status"(refer to Table 7.5) of those events referenced by the Dem-
MILIndicatorRef. The conditions for the activation modes are defined in Table
7.5.c()
Condition Activation Mode Indicator Status

No WWH-OBD event active 1 DEM_INDICATOR_OFF
Class C event active 2 DEM_INDICATOR_ON_DEMAND
Class B event active and B1 counter 3 DEM_INDICATOR_SHORT
< 200h
Class A event active or B1 counter 4 DEM_INDICATOR_CONTINUOUS
>= 200h
Table 7.5: Mapping of conditions to the activation mode
7.9.6.6 Freeze Frame 0x00
The Freeze Frame shall provide the operating conditions of the vehicle at the time of
malfunction detection.
[SWS_Dem_01170] dThe legislative Freeze Frame 0x00 shall be stored on transition
of UDS status bit 2 from 0 to 1 (via DemFreezeFrameRecordTrigger set to
DEM_TRIGGER_ON_PENDING).c()
[SWS_Dem_01171] dThe update behavior if the Freeze Frame 0x00 is updated on
transition of UDS status bit 3 from 0 to 1, can be configured using DemFreeze-
FrameRecordUpdate.c()
[SWS_Dem_01172] dThe storage/reporting of freeze frame information associated
with a Class A malfunction shall take precedence over a Class B1 malfunction which

AUTOSAR CP R20-11
shall take precedence over a Class B2 malfunction and likewise for information asso-
ciated with a Class C malfunction.c()
[SWS_Dem_01173] dThe first malfunction detected shall take precedence over the
most recent malfunction unless the most recent malfunction is of a higher class.c()
[SWS_Dem_01174] dThe Freeze Frame 0x00 shall be erased if the event was removed
from fault memory due to aging.c()
[SWS_Dem_01175] dThe legislative freeze frame 0x00 is configured analogues to the
non-emission related freeze frames.c()
7.9.6.7 Extended Data Record 0x90
Extended Data Record 0x90 is not supported due to a single B1 counter only supported
in Dem.
7.9.6.8 Aging
[SWS_Dem_01176] dAdditional to event aging (refer to [SWS_Dem_00698]) the event

shall be aged after 200 hours of engine operation while the aging conditions are met.c
()
[SWS_Dem_CONSTR_6111] dAn OBD related DTC shall have an aging counter
threshold of 40.c()
[SWS_Dem_CONSTR_6112] dAn OBD related DTC shall have the Warm-Up cycle as
aging cycle.c()
7.9.6.9 Service $19 42 - Read WWH-OBD DTC By Mask Record
This diagnostic service returns the OBD related DTCs that will match the given DTC
Status mask and DTC Severity mask.
[SWS_Dem_01177] dThe interface Dem_GetDTCSeverityAvailabilityMask
shall provide the DtcSeverityAvailabilityMask to the DCM.c()
Note: The DTCSeverityAvailabilityMask can be derived from the configured DTC sever-
ity and the WWH-OBD DTC class.

AUTOSAR CP R20-11
7.9.6.10 Service $14 FFFF33 - Clear Emission Related DTCs
[SWS_Dem_01178] dIn addition to clearing event memory entries (refer to

[SWS_Dem_01203]) the Dem shall clear/reset the following values:
• Activation Mode
• Readiness (PID $01, PID $41 and PID $90)
• Continuous-MI Counter
• Highest ECU B1 Counter
• B1 Counter
• Legislative Freeze Frame
c()
[SWS_Dem_01179] dService $14 FFFF33 shall clear all DTCs (WWH-OBD DTCs and
UDS DTCs)c()
7.10 J1939 specific functionality

The Dem module is capable to support J1939 networks. On these, it uses a J1939
specific DTC.
[SWS_Dem_00845] dThe J1939 support shall be available in case the configuration
container DemGeneralJ1939 (see DemGeneral) is present.c(RS_Diag_04112)
Note: The Dem is designed to distinguish ’Service only DTCs’ and ’all other DTCs’
assigning DTCs to certain event memories. In order to work correctly, with the
J1939Dcm APIs ’Service only DTCs’ need to be assigned to the user defined memory.
All other DTCs need to be assigned to primary memory.
7.10.1 Read DTC
[SWS_Dem_00855] dThe function Dem_J1939DcmSetDTCFilter

shall set the filter mask attributes to be used for the subse-
quent calls of Dem_J1939DcmGetNumberOfFilteredDTC and Dem_-
J1939DcmGetNextFilteredDTC, and reset an internal counter to the first event.c
(RS_Diag_04112)
[SWS_Dem_00856] dThe filter mask attributes set via Dem_-
J1939DcmSetDTCFilter shall be used until the next call of Dem_-
J1939DcmSetDTCFilter or Dem initialization.c(RS_Diag_04112)

AUTOSAR CP R20-11
[SWS_Dem_00857] dThe function Dem_J1939DcmSetDTCFilter shall return the

current composite status of the J1939 lamps. The matching filter citreria are defined in
Table 7.6.c()
DM representation
SetFilter Parameter UDS Status filter further filter AllDTCs EmissionDTCs
criteria
DEM_J1939DTC_ACTIVE (ConfirmedDTC == 1 n/a DM01 DM12
AND TestFailed == 1) OR
MIL_ON
DEM_J1939DTC ConfirmedDTC == 1 AND n/a DM02 DM23
_PREVIOUSLY_ACTIVE TestFailed == 0 AND
MIL_OFF
DEM_J1939DTC_PENDING PendingDTC == 1 n/a DM27 DM06
DEM_J1939DTC_- n/a permanent n/a DM28
PERMANENT memory
entry
available
DEM_J1939DTC TestFailed == 1 n/a DM35 n/a
_CURRENTLY_ACTIVE
Table 7.6: Types of errors which can be detected by the Dem module
Each reading of DTC returns a composite lamp status of the following lamps:
a) Malfunction Indicator Lamp
b) Red Stop Lamp
c) Amber Warning Lamp
d) Protect Lamp
7.10.1.1 Composite Malfunction Indicator Lamp Status
[SWS_Dem_00858] dThe composite “Malfunction Indicator Lamp” shall be set

to “Lamp Off” in case the Indicator referenced by DemMILIndicatorRef has
an IndicatorStatus DEM_INDICATOR_OFF. All other IndicatorStatus states than
“DEM_INDICATOR_OFF” shall set the composite Malfunction Indicator Lamp to “Lamp
On”.c(RS_Diag_04110)
[SWS_Dem_00859] dThe composite “Flash Malfunction Indicator Lamp” shall be set to
“Unavailable / Do Not Flash” (0x03) in case the Indicator referenced by DemMILIndi-
catorRef has an IndicatorStatus DEM_INDICATOR_OFF or DEM_INDICATOR_CON-
TINUOUS.c(RS_Diag_04110)
[SWS_Dem_00860] dThe composite “Flash Malfunction Indicator Lamp” shall be set
to “Slow Flash” (0x00) in case the Indicator referenced by DemMILIndicatorRef has
an IndicatorStatus DEM_INDICATOR_SLOW_FLASH.c(RS_Diag_04110)

AUTOSAR CP R20-11
[SWS_Dem_00861] dThe composite “Flash Malfunction Indicator Lamp” shall be set

to “Fast Flash” (0x01) in case the Indicator referenced by DemMILIndicatorRef has
an IndicatorStatus DEM_INDICATOR_FAST_FLASH.c(RS_Diag_04110)
7.10.1.2 Composite Red Stop Lamp Status
[SWS_Dem_00862] dThe composite “Red Stop Lamp” shall be set to “Lamp

Off” in case the Indicator referenced by DemRedStopLampIndicatorRef has
an IndicatorStatus DEM_INDICATOR_OFF. All other IndicatorStatus states than
“DEM_INDICATOR_OFF” shall set the composite Red Stop Lamp to “Lamp On”.c(RS_-
Diag_04110)
[SWS_Dem_00863] dThe composite “Flash Red Stop Lamp” shall be set to “Un-
available / Do Not Flash” (0x03) in case the Indicator referenced by DemRedSto-
pLampIndicatorRef has an IndicatorStatus DEM_INDICATOR_OFF or DEM_INDI-
CATOR_CONTINUOUS.c(RS_Diag_04110)
[SWS_Dem_00864] dThe composite “Flash Red Stop Lamp” shall be set to “Slow
Flash” (0x00) in case the Indicator referenced by DemRedStopLampIndicatorRef
has an IndicatorStatus DEM_INDICATOR_SLOW_FLASH.c(RS_Diag_04112)
[SWS_Dem_00865] dThe composite “Flash Red Stop Lamp” shall be set to “Fast
Flash” (0x01) in case the Indicator referenced by DemRedStopLampIndicatorRef
has an IndicatorStatus DEM_INDICATOR_FAST_FLASH.c()
7.10.1.3 Composite Amber Warning Lamp Status
[SWS_Dem_00866] dThe composite “Amber Warning Lamp” shall be set to “Lamp

Off” in case the Indicator referenced by DemAmberWarningLampIndicatorRef has
an IndicatorStatus DEM_INDICATOR_OFF. All other IndicatorStatus states than DEM_-
INDICATOR_OFF shall set the composite Amber Warning Lamp to “Lamp On”.c(RS_-
Diag_04110)
[SWS_Dem_00867] dThe composite “Amber Warning Lamp” shall be set to “Unavail-
able / Do Not Flash” (0x03) in case the Indicator referenced by DemAmberWarn-
ingLampIndicatorRef has an IndicatorStatus DEM_INDICATOR_OFF or DEM_IN-
DICATOR_CONTINUOUS.c(RS_Diag_04110)
[SWS_Dem_00868] dThe composite “Flash Amber Warning Lamp” shall be set
to “Slow Flash” (0x00) in case the Indicator referenced by DemAmberWarn-
ingLampIndicatorRef has an IndicatorStatus DEM_INDICATOR_SLOW_FLASH.c
(RS_Diag_04110)
[SWS_Dem_00869] dThe composite “Flash Amber Warning Lamp” shall be set to “Fast
Flash” (0x01) in case the Indicator referenced by DemAmberWarningLampIndica-
torRef has an IndicatorStatus DEM_INDICATOR_FAST_FLASH.c(RS_Diag_04110)

AUTOSAR CP R20-11
7.10.1.4 Composite Protect Lamp Status
[SWS_Dem_00870] dThe composite “Protect Lamp” shall be set to “Lamp Off” in case
the Indicator referenced by DemProtectLampIndicatorRef has an IndicatorStatus
DEM_INDICATOR_OFF. All other IndicatorStatus states than DEM_INDICATOR_OFF
shall set the composite Protect Lamp to “Lamp On”.c(RS_Diag_04110)
[SWS_Dem_00871] dThe composite “Flash Protect Lamp” shall be set to “Unavailable
/ Do Not Flash” (0x03) in case the Indicator referenced by DemProtectLampIndi-
catorRef has an IndicatorStatus DEM_INDICATOR_OFF or DEM_INDICATOR_CON-
TINUOUS.c()
[SWS_Dem_00872] dThe composite “Flash Protect Lamp” shall be set to “Slow Flash”
(0x00) in case the Indicator referenced by DemProtectLampIndicatorRef has an
IndicatorStatus DEM_INDICATOR_SLOW_FLASH.c(RS_Diag_04110)
[SWS_Dem_00873] dThe composite “Flash Protect Lamp” shall be set to “Fast Flash”
(0x01) in case the Indicator referenced by DemProtectLampIndicatorRef has an
IndicatorStatus DEM_INDICATOR_FAST_FLASH.c(RS_Diag_04110)
7.10.1.5 DTC data acqusition
[SWS_Dem_00874] dThe function Dem_J1939DcmGetNumberOfFilteredDTC

shall return the number of J1939 DTCs matching the defined filter criteria of Table
7.6 for the corresponding primary event memory of the requested ClientId by the func-
tion call of Dem_J1939DcmSetDTCFilter.
• In case the function has calculated the total number of matching DTCs, the return
value shall be E_OK.
• In case the search needs to be interrupted due to internal implementa-
tions or limitations, the return value can be set to DEM_PENDING. The
out parameter needs not to be valid in this case. The next call of Dem_-
J1939DcmGetNumberOfFilteredDTC should continue after the interrupted el-
ement.
c(RS_Diag_04112)
[SWS_Dem_00875] dEach call of the function Dem_-
J1939DcmGetNextFilteredDTC shall search for the next event having a J1939DTC
assigned and matching the filter criteria of Table 7.6 for the node provided by the
function call of Dem_J1939DcmSetDTCFilter. In case no more events are matching
the filter criteria, the function return value shall be DEM_NO_SUCH_ELEMENT. The
out parameters need not to be valid in this case.c(RS_Diag_04112)
[SWS_Dem_00877] dIn case the function Dem_J1939DcmGetNextFilteredDTC
has found an event matching the filter criteria it shall return the corresponding

AUTOSAR CP R20-11
J1939DTC (refer to DemDTCAttributes for details) and the corresponding occur-

rence counter. The return value shall be E_OK. In case the search needs to be in-
terrupted due to internal implementations or limitations, the return value can be set to
DEM_PENDING. The out parameter needs not to be valid in this case. The next call
of Dem_J1939DcmGetNextFilteredDTC should continue after the interrupted ele-
ment. In case the occurrence counter is above +126 (0x7E), the returned values shall
be set to +126 (0x7E).c(RS_Diag_04111)
7.10.2 Clear DTCs
For definition of locking the clearing process, refer to chapter 7.7.2.2.

[SWS_Dem_00878] dThe Dem module shall provide the Dem_J1939DcmClearDTC
to the J1939Dcm [7] for deleting all active or previously active DTCs from the event
memory. This shall trigger also initializing of related SW-Cs / BSW modules according
to [SWS_Dem_00003].c()
When one of the diagnostic messages DM03 and DM11 of SAE J1939-73 [14] are
requested, all active (DM11) or previously active (DM03) DTCs have to be cleared,
along with additional information like freeze frames.
[SWS_Dem_00879] dThe function Dem_J1939DcmClearDTC shall clear the status of
all event(s) related to the specified DTC(s), as well as all associated event memory
entries for these event(s).c(RS_Diag_04117)
Note: Exceptions may apply due to [SWS_Dem_00515].
7.10.3 DM31
The DM31 provides the applicable lamp(s) and their status for each individual DTC,
wherefore the DTC-specific lamp status needs to be returned by the function Dem_-
J1939DcmFirstDTCwithLampStatus.
[SWS_Dem_00880] dEach call to Dem_J1939DcmFirstDTCwithLampStatus shall
set the internal counter to the first event having a J1939DTC for this particular “ClientId”
assiged.c(RS_Diag_04113)
[SWS_Dem_00881] dEach call to Dem_J1939DcmGetNextDTCwithLampStatus
shall search within the event memory (set by the function Dem_-
J1939DcmFirstDTCwithLampStatus) for the next event having a J1939DTC
assigned. In case no more events are available that have a J1939DTC assigend, the
function return value shall be DEM_NO_SUCH_ELEMENT. The out parameter needs
not to be valid in this case.c(RS_Diag_04113)
[SWS_Dem_00882] dIn case Dem_J1939DcmGetNextDTCwithLampStatus has
found an event matching the filter criteria it shall return the J1939DTC specific status

AUTOSAR CP R20-11
of the lamps (refer to following sections for details), the corresponding J1939DTC (re-
fer DemDTCAttributes for details) and the corresponding occurrence counter. The
return value shall be E_OK. In case the search needs to be interrupted due to inter-
nal implementations or limitations, the return value can be set to DEM_PENDING.
The out parameter needs not to be valid in this case. The next call of Dem_-
J1939DcmGetNextDTCwithLampStatus should continue after the interrupted ele-
ment. In case the occurrence counter is above +126 (0x7F), the returned values shall
be set to +126 (0x7F).c(RS_Diag_04113)
7.10.3.1 Malfunction Indicator Lamp
[SWS_Dem_00883] dThe DTCspecific “Malfunction Indicator Lamp” returned in the

function Dem_J1939DcmGetNextDTCwithLampStatus shall be set to “Lamp On” in
case the corresponding event has assigned the Indicator referenced by DemMILIndi-
catorRef and the UDS status bit 7 (WarningIndicator) is active (set to 1), otherwise it
shall be set to ’Lamp Off’.c(RS_Diag_04110)
[SWS_Dem_00884] dThe DTC-specific “Flash Malfunction Indicator Lamp” shall be set
to “Unavailable / Do Not Flash” (0x03) in case the corresponding event has set “Lamp
On” and the DemIndicatorBehaviour of the Indicator referenced by DemMILIndi-
catorRef is set to DEM_INDICATOR_CONTINUOUS.c(RS_Diag_04110)
[SWS_Dem_00885] dThe DTC-specific “Flash Malfunction Indicator Lamp” shall be
set to “Slow Flash” (0x00) in case the corresponding event has set “Lamp On” and the
DemIndicatorBehaviour of the Indicator referenced by DemMILIndicatorRef is
set to DEM_INDICATOR_SLOW_FLASH.c(RS_Diag_04110)
[SWS_Dem_00886] dThe DTC-specific “Flash Malfunction Indicator Lamp” shall be
set to “Fast Flash” (0x01) in case the corresponding event has set “Lamp On” and the
DemIndicatorBehaviour of the Indicator referenced by DemMILIndicatorRef is
set to DEM_INDICATOR_FAST_FLASH.c()
7.10.3.2 Red Stop Lamp
[SWS_Dem_00887] dThe DTC-specific “Red Stop Lamp” returned in the function

Dem_J1939DcmGetNextDTCwithLampStatus shall be set to “Lamp On” in case the
corresponding event has assigned the Indicator referenced by DemRedStopIndicator-
Ref and the UDS status bit 7 (WarningIndicator) is active (set to 1), otherwise it shall
be set to “Lamp Off”.c(RS_Diag_04110)
[SWS_Dem_00888] dThe DTC-specific “Flash Red Stop Lamp” shall be set to “Un-
available / Do Not Flash” (0x03) in case the corresponding event has set “Lamp On”
and the DemIndicatorBehaviour of the Indicator referenced by DemRedStopIndi-
catorRef is set to DEM_INDICATOR_CONTINUOUS.c(RS_Diag_04110)

AUTOSAR CP R20-11
[SWS_Dem_00889] dThe DTC-specific “Flash Red Stop Lamp” shall be set to “Slow
Flash” (0x00) in case the corresponding event has set “Lamp On” and the DemIndi-
catorBehaviour of the Indicator referenced by DemRedStopIndicatorRef is set to
DEM_INDICATOR_SLOW_FLASH.c(RS_Diag_04110)
[SWS_Dem_00890] dThe DTC-specific “Flash Red Stop Lamp” shall be set to “Fast
catorBehaviour of the Indicator referenced by DemRedStopIndicatorRef is set to
DEM_INDICATOR_FAST_FLASH.c()
7.10.3.3 Amber Warning Lamp
[SWS_Dem_00891] dThe DTC-specific “Amber Warning Lamp” returned in the func-

tion Dem_J1939DcmGetNextDTCwithLampStatus shall be set to “Lamp On” in
case the corresponding event has assigned the Indicator referenced by DemAmber-
WarningIndicatorRef and the UDS status bit 7 (WarningIndicator) is active (set to 1),
otherwise it shall be set to “Lamp Off”.c(RS_Diag_04110)
[SWS_Dem_00892] dThe DTC-specific “Flash Amber Warning Lamp” shall be set to
“Unavailable / Do Not Flash” (0x03) in case the corresponding event has set “Lamp
On” and the DemIndicatorBehaviour of the Indicator referenced by DemAmber-
WarningIndicatorRef is set to DEM_INDICATOR_CONTINUOUS.c(RS_Diag_04110)
“Slow Flash” (0x00) in case the corresponding event has set “Lamp On” and the De-
mIndicatorBehaviour of the Indicator referenced by DemAmberWarningIndicator-
Ref is set to DEM_INDICATOR_SLOW_FLASH.c(RS_Diag_04110)
“Fast Flash” (0x01) in case the corresponding event has set “Lamp On” and the De-
mIndicatorBehaviour of the Indicator referenced by DemAmberWarningIndicator-
Ref is set to DEM_INDICATOR_FAST_FLASH.c(RS_Diag_04110)
7.10.3.4 Protect Lamp
[SWS_Dem_00895] dThe DTC-specific “Protect Lamp” returned in the function Dem_-

J1939DcmGetNextDTCwithLampStatus shall be set to “Lamp On” in case the cor-
responding event has assigned the Indicator referenced by DemProtectLampIndi-
catorRef and the UDS status bit 7 (WarningIndicator) is active (set to 1), otherwise it
shall be set to “Lamp Off”.c(RS_Diag_04110)
[SWS_Dem_00896] dThe DTC-specifc “Flash Protect Lamp” shall be set to “Unavail-
able / Do Not Flash” (0x03) in case the corresponding event has set “Lamp On” and the
DemIndicatorBehaviour of the Indicator referenced by DemProtectLampIndi-
catorRef is set to DEM_INDICATOR_CONTINUOUS.c()

AUTOSAR CP R20-11
[SWS_Dem_00897] dThe DTC-specifc “Flash Protect Lamp” shall be set to “Slow

catorBehaviour of the Indicator referenced by DemProtectLampIndicatorRef
is set to DEM_INDICATOR_SLOW_FLASH.c(RS_Diag_04110)
[SWS_Dem_00898] dThe DTC-specifc “Flash Protect Lamp” shall be set to “Fast
catorBehaviour of the Indicator referenced by DemProtectLampIndicatorRef
is set to DEM_INDICATOR_FAST_FLASH.c(RS_Diag_04110)
7.10.3.5 J1939 lamp status

set to DEM_J1939LAMP_STATUS, then the lamp status in the format of type Dem_-
J1939DcmLampStatusType shall be mapped to the respective data element.c(RS_-
Diag_04134, RS_Diag_04190)
[SWS_Dem_01311] dThe DemInternalDataElement for DEM_J1939LAMP_STA-
TUS shall contain the lamp status before the event was processed Dem internally.c
7.10.4 FreezeFrame
[SWS_Dem_00899] dThe function Dem_J1939DcmSetFreezeFrameFilter shall

set the filter mask attributes to be used for the subsequent calls of Dem_-
J1939DcmGetNextFreezeFrame, and reset an internal counter to the first
freeze frame. The filter mask attributes shall be used until the next call
of Dem_J1939DcmSetFreezeFrameFilter or Dem initialization. The match-
ing filter citreria are DEM_J1939DCM_FREEZEFRAME (filtering the data in
DemJ1939FreezeFrameClassRef) or DEM_J1939DCM_EXPANDED_FREEZEFRAME
(filtering the data in DemJ1939ExpandedFreezeFrameClassRef).c(RS_Diag_-
04111)
[SWS_Dem_00900] dEach function call of Dem_J1939DcmGetNextFreezeFrame
shall step to the next (Expanded-)FreezeFrame for a specific event mem-
ory defined by the filter criteria (FreezeFrameKind and ClientId) of Dem_-
J1939DcmSetFreezeFrameFilter. In case no more (Expanded-)FreezeFrames
are matching the filter criteria, the function shall return DEM_NO_SUCH_ELEMENT.
The out parameters need not to be valid in this case.c(RS_Diag_04111)
[SWS_Dem_00901] dThe function Dem_J1939DcmGetNextFreezeFrame shall trig-
ger the Det error DEM_E_WRONG_CONDITION in case of not supported Freeze-
FrameKind. Valid values are DEM_J1939DCM_FREEZEFRAME and DEM_J1939DCM_-
EXPANDED_FREEZEFRAME.c(RS_Diag_04111)

AUTOSAR CP R20-11
[SWS_Dem_00902] dIn case the search of [SWS_Dem_00901] needs to be inter-

rupted due to internal implementations or limitations, the return value can be set to
of Dem_J1939DcmGetNextFreezeFrame should continue after the interrupted ele-
ment.c(RS_Diag_04111)
[SWS_Dem_00903] dIn case the function Dem_J1939DcmGetNextFreezeFrame
has found a FreezeFrame, the Dem shall:
• Check if the buffer in the BufSize parameter is big enough to hold the (Expanded-
)FreezeFrame. If not, DEM_FILTERED_BUFFER_TOO_SMALL shall be re-
turned without any further actions. The out parameters need not to be valid in
this case.
• Copy the (Expanded-)FreezeFrame data into the buffer provided by the parameter
DestBuffer (in case of Expanded FreezeFrames without any SPN informations).
Unused bits shall be filled with “0”.
• Set the parameter J1939DTC to the corresponding J1939DTC value (refer
DemDTCAttributes for details) and the parameter OccurrenceCounter to the
corresponding occurrence counter value.
• Return with E_OK. In case the occurrence counter is above +126 (0x7F), the
returned value shall be set to +126 (0x7F).
c(RS_Diag_04111)
7.10.4.1 SPNs in ExpandedFreezeFrame
[SWS_Dem_00904] dEach call to Dem_J1939DcmGetNextSPNInFreezeFrame

shall step to the next SPN of the ExpandedFreezeFrame for this DemEventMemory.
In case no more SPN of the ExpandedFreezeFrame definition is available, the function
return value shall be DEM_NO_SUCH_ELEMENT. The out parameter needs not to be
valid in this case.c(RS_Diag_04111)
[SWS_Dem_00905] dIn case the search of [SWS_Dem_00904] needs to be inter-
rupted due to internal implementations or limitations, the return value can be set to
of Dem_J1939DcmGetNextSPNInFreezeFrame should continue after the interrupted
element.c(RS_Diag_04111)
[SWS_Dem_00906] dThe function Dem_J1939DcmGetNextSPNInFreezeFrame shall
trigger the Det error DEM_E_WRONG_CONDITION in case of not supported Freeze-
FrameKind. Valid value is Dem_SPNsInExpandedFreezeFrame.c(RS_Diag_04057,
RS_Diag_04111)
[SWS_Dem_00907] dIn case Dem_J1939DcmGetNextSPNInFreezeFrame has
found an SPN of the ExpandedFreezeFrame definition, the Dem shall:

AUTOSAR CP R20-11
• Check if the buffer in the BufSize parameter is big enough to hold the (Expanded-
)FreezeFrame. If not, DEM_FILTERED_BUFFER_TOO_SMALL shall be re-
turned without any further actions. The out parameters need not to be valid in
this case.
• Copy the (Expanded-)FreezeFrame data into the buffer provided by the parameter
DestBuffer (in case of Expanded FreezeFrames without any SPN informations).
Unused bits shall be filled with “0”.
• Set the parameter J1939DTC to the corresponding J1939DTC value (refer
DemDTCAttributes for details) and the parameter OccurrenceCounter to the
corresponding occurrence counter value.
• Return with E_OK. In case the occurrence counter is above +126 (0x7F), the
returned value shall be set to +126 (0x7F).
c(RS_Diag_04111)
7.10.5 Diagnostic Readiness
The Dem module needs to calculate internally the (Non-)Continuously Monitored Sys-
tems support and status for “Diagnostic Readiness 1” (DM05), “Diagnostic Readiness
2” (DM21), and “Diagnostic Readiness 3” (DM26).
[SWS_Dem_00908] dThe J1939 events shall use the configuration parameter De-
mEventOBDReadinessGroup (refer to DemObdDTC) to assign individual events to a
Continuously or Non-Continuously Monitored System.c(RS_Diag_04113)
Dem_J1939DcmReadDiagnosticReadiness1 reports the diagnostics information
that relates to diagnostic readiness according DM05.
[SWS_Dem_00909] dA call of Dem_J1939DcmReadDiagnosticReadiness1 shall
report a response message based on the J1939-73 [14] DM05 definition:
• “Active Trouble Codes” shall report the number of active DTCs identical to
the number of filtered DTCs by Dem_J1939DcmSetDTCFilter (Dem_Active,
DEM_DTC_KIND_ALL_DTCS).
• “Previously Active Diagnostic Trouble Codes” shall report the num-
ber of previously active DTCs identical to the number of filtered
DTCs by Dem_J1939DcmSetDTCFilter (Dem_PreviouslyActive,
DEM_DTC_KIND_ALL_DTCS).
• “OBD Compliance” shall be based on the configuration parameter DemOBDCom-
pliancy (in DemGeneralOBD). For nonOBD ECUs the value five (5) shall be re-
ported.
• The (Non-)Continuously Monitored Systems support and status shall be reported
according to SAE J1939-73 chapter 5.7.5.4 to 5.7.5.6. The calculation shall be
based on those events referencing the corresponding configuration parameter

AUTOSAR CP R20-11
DemEventOBDReadinessGroup. In case there is no reference by any event

parameter, the support bit shall be set to zero (0). The “monitoring status” bit
shall be set to “test complete” (0) if all assigned event parameter have the Test-
NotCompletedSinceLastClear status bit set to zero (0), otherwise the “monitoring
status” bit shall be set to “test not complete” (1).
c(RS_Diag_04113)
Dem_J1939DcmReadDiagnosticReadiness2 reports the diagnostic information
relevant to a second PGN conveying diagnostic readiness according to DM21 (see
also DM05).
• “Distance Traveled While MIL is Activated” shall be identical to PID 0x21, except
the maximum value is 64255 (all values above 64255 shall be reported as 64255).
• “Distance Since Diagnostic Trouble Codes Cleared” shall be identical to PID 0x31,
except the maximum value is 64255 (all values above 64255 shall be reported as
64255).
• “Minutes Run by Engine While MIL is Activated” shall be identical to PID 0x4D,
64255).
• “Time Since Diagnostic Trouble Codes Cleared” shall be identical to PID 0x4E,
64255).
c(RS_Diag_04112)
Dem_J1939DcmReadDiagnosticReadiness3 reports the diagnostic information
conveying the pending status of OBD system monitors for the current drive cycle ac-
cording to DM26 (See also DM05 and DM21).
• “Time Since Engine Start” shall be retrieved by the DemOBDTimeSinceEngineS-
tart (in DemGeneralOBD)
• “Number of Warmups Since DTCs Cleared” shall be identical to PID 0x30, except
the maximum value is 250 (all values above 250 shall be reported as 250).
• The (Non-)Continuously Monitored Systems Enable/Completed status shall be
reported according to SAE J1939-73 [14] chapter 5.7.26.3 to 5.7.26.5. The cal-
culation shall be based on those events referencing the corresponding configura-
tion parameter DemEventOBDReadinessGroup. In case there is no reference
by any event parameter it shall shall indicate disabled and complete. Otherwise
the disable state shall be based on the readiness group disabled status according

AUTOSAR CP R20-11
to [SWS_Dem_00356], and the complete status shall be set to “monitor complete”

(0) if all assigned event parameter have the TestNotCompletedSinceThisOpera-
tionCycle status bit set to zero (0); otherwise the status bit shall be set to “monitor
not complete” (1).
c(RS_Diag_04112)
7.10.6 Monitor Performance Ratio
For J1939 the In-Use-Monitor Performace Ratio (IUMPR) requires a reporting for each
supported Applicable System Monitor only.
[SWS_Dem_00912] dThe function Dem_J1939DcmSetRatioFilter shall reset an
internal counter to the first valid SPN with DemRatioId defined to be used for the subse-
quent calls of Dem_J1939DcmGetNextFilteredRatio. Furthermore, it shall return
the “Ignition Cycle Counter” according SAEJ193973 chapter 5.7.20.1, as well as “OBD
Monitoring Conditions Encountered” according SAEJ193973 chapter 5.7.20.2 (CARB
defines this as the general denominator).c(RS_Diag_04112)
[SWS_Dem_00913] dEach call of the function Dem_-
J1939DcmGetNextFilteredRatio shall skip to the next valid SPN within the
event memory with DemRatioId defined.
• The events referenced by this SPN via DemRatioId shall be used to calculate
the return values SPN (for “SPN of Applicable System Monitor”), Numerator (for
“Applicable System Monitor Numerator”), and Denominator (for “Applicable Sys-
tem Monitor Denominator”). The return value shall be E_OK.
• In case the calculation needs to be interrupted due to internal implemen-
tations or limitations, the return value can be set to DEM_PENDING. The
out parameter needs not to be valid in this case. The next call of Dem_-
J1939DcmGetNextFilteredRatio should continue after the interrupted ele-
ment.
• In case no more SPNs are available, the function return value shall be
DEM_NO_SUCH_ELEMENT. The out parameter needs not to be valid in this
case.
c(RS_Diag_04113)
7.11 Interaction with other Software Modules
7.11.1 Interaction with Software Components (SW-C)
In the AUTOSAR ECU architecture, the Diagnostic Event Manager implements an

AUTOSAR Service. This means that the Dem module does not exclusively commu-
nicate with other BSW modules, but also with SWC via the RTE (refer to Figure 5.1).

AUTOSAR CP R20-11
From the viewpoint of the BSW “Cmodule” Dem, there are three kinds of dependencies
between the Service and the AUTOSAR Software Components above the RTE:
• The application accesses the API (implemented as Cfunctions) of the Dem (by
accessing the Dem Service Component).
• The application is optionally notified upon the outcome of requested asyn-
chronous activity (via direct/indirect RTE API by the Dem).
• An initialization function of the SWC is invoked by the Dem.
These dependencies must be described in terms of the AUTOSAR metamodel, which
will contribute to the SWC Description of the application component as well as to the
Service Component Description of the Dem Service.
The service component description of the Dem Service will define the ports below the
RTE. Each SWC, which uses the Dem Service, must contain respective ports in its own
SWC description, which will be typed by the same (or compatible) interfaces and must
be connected to the ports of the Dem, so that the RTE can be generated. Ids used in
these Dem-ports are abstracted with portdefined arguments.
[SWS_Dem_00512] dThe name of the Dem Service Component shall be “Dem”.c
(SRS_BSW_00300)
The callbacks to SWCs do not use the mechanism of the portdefined arguments. In-
stead, the Dem configuration mechanism must ensure that the callback is delivered to
the configured port and invokes the correct operation at this port using an RTE (direct
or indirect) API call. For example, the EventId must not be passed as the first argument
of the operation, because the monitors (and other SW-Cs) do not cope with EventIds
explicitly.
In contrast to that, there are some special SWCs, that need to handle event status/-
data changes uniformly. These SWCs are notified by the Dem, which provides then
also the EventId for the application, to be able, to request the respective data from the
Dem. Therefore, general interfaces are provided (refer to GeneralCallbackEven-
tUdsStatusChanged, GeneralDiagnosticInfo and CallbackEventUdsSta-
tusChanged), which shall only be used in the way, that the EventIds (given by the
Dem) shall not be interpreted by SWCs in any way, as well as the EventId values (used
by the SW-Cs to request the event-specific data) have always to be provided by the
Dem. Here only a handthrough mechanism is allowed to be used by SWCs for Even-
tIds.
In the current Autosar release, the RTE analyzes the complete calltree of triggered
runnables. Therefore, some limitations in the Dem API are introduced to avoid function
calls from BSW modules, which rely on callbacks to SWCs via RTE.

AUTOSAR CP R20-11
7.11.2 Interaction with Diagnostic Clients
The Dem module provides interfaces to diagnostic clients. A diagnostic client is a

BSW module, which is related to processing diagnostic requests. The most common
diagnostic client is the Dcm. There are further used cases, where a diagnostic client is
a SW-C interacting with the Dem via the RTE interfaces. A diagnostic client accesses
the Dem module in order to delegate diagnostic services, which are related to the event
memory.
For detailed description of the interface usage between Dcm and Dem consult the Dcm
SWS document [9, SWS Dcm]. There, especially the handling of freeze frame data is
described.
[SWS_Dem_00171] dIf the Dcm has requested an unavailable event memory /
DTC origin, the Dem module functions with the respective return value shall return
DEM_<...>_WRONG_DTCORIGIN.c(RS_Diag_04058)
[SWS_Dem_00172] dIf the Dcm has requested a DTC that is not available at all
or that is available but has a different event memory / DTC origin than the re-
quested one, the Dem module functions with the respective return value shall return
DEM_<...>_WRONG_DTC.c()
[SWS_Dem_00828] dIf the status of a DTC changes, the Dem shall call the configured
DemCallbackDTCStatusChanged functionc()
The ClientID is also used to filter for specific contents (like UDS instances , J1939
nodes, OBD,..).
7.11.2.1 Parallel event memory access
There are multiple clients that can request access to the fault memory. To allow parallel
access to the clients, the Dem uses the concept of a client ID. The client IDs are
configured in the container DemClient. Each client which requests access to the fault
memory of the Dem has an assigned unique client ID. Examples for these clients are:
• Parallel OBD and UDS communication, where each protocol is handled by an
own Dcm client
• Multiple Dcm instances in virtual ECUs, where Dcm instances are independent
from each other
• SWCs or complex device driver, as proxy in OBD systems for secondary ECUs
• Clearing DTC by different clients
The Dem supports the client id as parameter ‘ClientId’ in various APIs to:
• Access fault memory information
• Read event related data

AUTOSAR CP R20-11
• Clear DTC and fault memory

• Control fault memory behavior
[SWS_Dem_01251] dThe Dem shall ensure that clients with a different client Id can call
all APIs with ‘ClientId’ as parameter in parallel. An API call from one client shall be
processed independently from calls of the same API from a client with a different ID.
E.g. if one client is setting a filter to iterate over extended data records, another client
can set a different filter and iterate the extended data records.c(RS_Diag_04162)
[SWS_Dem_01252] dThe Dem shall accept in all APIs with ‘ClientId’ as parameter only
a ClientId value matching to any of the configured DemClientId. If a not configured
ClientId value is passed, the Dem shall report the Det error DEM_E_WRONG_CONFIG-
URATION.c(RS_Diag_04162)
Note: A client is a BSW/SW-C module or a CDD that is processing diagnostic requests
or is used to support a distributed diagnostic environment such as events from a sec-
ondary ECU that are handled on a primary ECU. The client id concept is explicitly not
designed to provide any arbitrary BSW module access to the fault memory, especially
if the modules purpose is different than processing diagnostic requests. The design fo-
cuses on Dcm for OBD and UDS processing, as well as remote event communication
modules for distributed OBD systems.
For each DemClient with the parameter DemClientUsesRte set to TRUE, the Dem
will provide the C/S interfaces ClearDTC and EvMemOverflowIndication.
7.11.2.2 Accessing diagnostic fault memory
The Dem provides a range of APIs controlling and accessing event memory and its
behavior or configuration and states. Many of those APIs follow a ‘select and request’
mechanism. Initially a client selects a DTC or a group of DTCs and then calls APIs
working on the active selection. A selection is client local and remains until a new
selection is made.
[SWS_Dem_01253] dIf the API Dem_SelectDTC is called, the Dem shall use the se-
lected DTC or group of DTC in the requested DTCOrigin and DTCFormat as target
for the following API calls:
• Dem_ClearDTC
• Dem_DisableDTCRecordUpdate
• Dem_GetDTCSelectionResultForClearDTC
• Dem_GetDTCSelectionResult
• Dem_GetFunctionalUnitOfDTC
• Dem_GetSeverityOfDTC
• Dem_GetStatusOfDTC

AUTOSAR CP R20-11
• Dem_SetDTCSuppression
• Dem_GetDTCSuppression.
c()
[SWS_Dem_01306] Behavior if one client calling Dem_SelectDTC before the pre-
vious operation finished dIf Dem_SelectDTC is called by one client and the same
client is calling Dem_SelectDTC again and the Dem is currently still processing the
previous operation based on Dem_SelectDTC according to [SWS_Dem_01253], the
Dem shall return DEM_BUSY.c()
[SWS_Dem_01305] Behavior if one client starting a new operation while the pre-
vious one is still running dIn case any of the Dem_SelectDTC related APIs ac-
cording to [SWS_Dem_01253] is called by one client and the same client has already
started another Dem_SelectDTC related operation according to [SWS_Dem_01253]
and this different operation is not completed, the Dem shall return DEM_BUSY.c()
[SWS_Dem_01304] Life cycle of Dem_Select dependent operations dThe
Dem shall consider an operation based on Dem_SelectDTC according to
[SWS_Dem_01253] to be finished independently if the client has requested the E_OK
result from the Dem or not.c()
A client calling Dem_SelectDTC while another operation of the same client is still
running, would indicate that the client is no longer interested in the result of the running
operation. The result can be dropped and new select can be processed after Dem is
ready.
[SWS_Dem_01198] dFor addressing all DTCs, the Dem shall provide the symbol
DEM_DTC_GROUP_ALL_DTCS which is selecting all configured DTCs (representation
is 0xFFFFFF).c()
[SWS_Dem_01254] dThe API Dem_SelectDTC triggers the Dem internal DTC selec-
tion process on the event memory assigned to the ClientId. The result of the selection
shall be reflected in the return value of the API calls following the Dem_SelectDTC
call, see [SWS_Dem_01253].c()
Note:The behaviour of Dem_SelectDTC depending APIs with calling Dem_Select-
DTC is described in [SWS_Dem_01299].
Note: The Dem_SelectDTC selects internally a DTC or group of DTC. In case a client
is interested only in the result of the selection without a further action behind, the API
Dem_GetDTCSelectionResult can be used. One use case of this API is the NRC
handling for the UDS service 0x14 ClearDTC. The Dcm needs to perform further NRC
relevant verifications between selecting and deleting the DTC.

AUTOSAR CP R20-11
[SWS_Dem_01261] API Behaviour on undefined DTC or format dIf any of the APIs
requiring a Dem_SelectDTC according to [SWS_Dem_01253] is called while the se-
lection with Dem_SelectDTC is invalid, then the Dem shall return DEM_WRONG_DTC.
A selection is invalid in case the provided DTC does not specify a valid DTC or
GroupOfDTCs in the corresponding DTCFormat. The selection also is invalid, if Dem_-
SelectDTC was not called before.c(SRS_BSW_00369)
[SWS_Dem_01299] API behavior without selected DTC dIf any of the APIs
requiring a Dem_SelectDTC according to [SWS_Dem_01253] is called without
a prior call of Dem_SelectDTC for this client, the Dem shall report the Det
DEM_E_WRONG_CONDITION.c(SRS_BSW_00369)
[SWS_Dem_01262] API Behaviour on undefined DTCOrigin dIf any of the APIs re-
quiring a Dem_SelectDTC (see [SWS_Dem_01253]) is called on a not existing se-
lected DTCOrigin, the Dem shall return DEM_WRONG_DTCORIGIN on this API.c
().
[SWS_Dem_01256] dThe API Dem_GetDTCSelectionResult shall return E_OK, if
the selection of Dem_SelectDTC was successful and the DTC or group of DTC are
ready for further processing.c()
Note: The call of Dem_GetDTCSelectionResult after a Dem_SelectDTC is op-
tional. APIs depending on Dem_SelectDTC have the same behaviour with or without
a call of Dem_GetDTCSelectionResult.
[SWS_Dem_01257] dIf the API Dem_GetDTCSelectionResult is called and the
DTC or group of DTC from Dem_SelectDTC is invalid, the Dem shall return
DEM_WRONG_DTC.c()
[SWS_Dem_01258] dIf the API Dem_GetDTCSelectionResult is called and
the Origin provided to Dem_SelectDTC is invalid, the Dem shall return
DEM_WRONG_DTCORIGIN.c()
[SWS_Dem_01296] Definition of Dem_GetDTCSelectionResultForClearDTC
functionality dThe API Dem_GetDTCSelectionResultForClearDTC shall be-
have exactly as Dem_GetDTCSelectionResult with the only difference that,
DEM_WRONG_DTC is returned in case of a single DTC was selected and Dem-
ClearDTCLimitation is set to DEM_ONLY_CLEAR_ALL_DTCS for that client.c
()
7.11.2.3 Access DTCs and Status Information
The following chapter defines the APIs, which shall be used to access the number of
DTCs, and DTCs matching specific filter criteria and the associated status information.
[SWS_Dem_00231] dThe API Dem_GetTranslationType shall return the transla-
tion format of the DemEventMemorySet configured in DemTypeOfDTCSupported.c
(RS_Diag_04201)

AUTOSAR CP R20-11
[SWS_Dem_00060] dThe function Dem_GetDTCStatusAvailabilityMask shall

set the out parameter DTCStatusMask to the value configured in DemDtcSta-
tusAvailabilityMask of the DemEventMemorySet for the assigned client ID.c
(RS_Diag_04067)
[SWS_Dem_01342] dIf the function Dem_GetDTCStatusAvailabilityMask is
called with a DTCOrigin different to DEM_DTC_ORIGIN_PRIMARY_MEMORY or
DEM_DTC_ORIGIN_USERDEFINED_MEMORY_<Name>, the Dem shall report the
development error DEM_E_PARAM_DATA.c(RS_Diag_04067)
[SWS_Dem_01181] dThe Dem module shall be able to return the DTC severity avail-
ability mask (refer to Dem_GetDTCSeverityAvailabilityMask) in accordance to
ISO 14229-1 [1].c()
[SWS_Dem_01182] dThe function Dem_GetDTCSeverityAvailabilityMask
shall calculate the DTC severity availability mask in accordance to ISO 14229-1 [1]
from the severity configuration of each supported DTC.c()
[SWS_Dem_00657] dThe Dem module shall mask all DTC status bytes (API param-
eters DTCStatus) provided to the Dcm with the DTC status availability mask (by per-
forming a bit-wise AND operation).c()
[SWS_Dem_00059] dThe function Dem_GetStatusOfDTC shall copy the status of
the selected DTC to the parameter DTCStatus. The DTCStatus format is according to
ISO-14229-1[2].c(RS_Diag_04067)
[SWS_Dem_01259] dIf the API Dem_GetStatusOfDTC is called on a selected DTC
that does not exist in the selected format or if the selected DTC is a group of DTC or no
DTC was selected, the Dem shall return DEM_WRONG_DTC.c()
[SWS_Dem_01260] dIf the API Dem_GetStatusOfDTC is called on a not existing
selected DTCOrigin, the Dem shall return DEM_WRONG_DTCORIGIN.c()
[SWS_Dem_01275] dIf the API Dem_GetStatusOfDTC is called on a se-
lected DTC that does not have an assigned DTC status, the Dem shall return
DEM_NO_SUCH_ELEMENT.c()
Note: In mirror event memory the DTCs does not necessarily have a status assigned.
It is possible, that a DTC with different states exists depending on the location. If the
mirror memory is used as a kind of protocol stack that gives information which services
have been performed on the primary memory, different DTC states might appear (e.g.
DTC has been deleted from the primary memory and is written to the mirror memory
with its latest status).
[SWS_Dem_00057] dThe function Dem_SetDTCFilter shall set the filter criteria for
the client with the same client ID for subsequent calls of::
• Dem_GetNumberOfFilteredDTC
• Dem_GetNextFilteredDTC

AUTOSAR CP R20-11
• Dem_GetNextFilteredDTCAndFDC
• Dem_GetNextFilteredDTCAndSeverity.
The filter criteria attributes shall be used until the next call of Dem_SetDTCFilter or
Dem initialization.c(RS_Diag_04057)
Note: Calls to Dem_SetDTCFilter with different ClientID can be called in parallel
(see [SWS_Dem_01251]) without interfering each other. This way multiple clients can
access the fault memory data in parallel.
In figure 7.48 a situation is shown, where two clients (e.g. an Dcm for OBD and an
Dcm for UDS) are reading the number of filtered DTCs in parallel.
Client1 Client2 «Module»
:Dem
Dem_SetDTCFilter(Std_ReturnType, "Client1", uint8, Dem_DTCFormatType, Dem_DTCOriginType, boolean, Dem_DTCSeverityType, boolean)
Dem_SetDTCFilter(Std_ReturnType, "Client2", uint8, Dem_DTCFormatType, Dem_DTCOriginType, boolean, Dem_DTCSeverityType, boolean)
Dem_GetNumberOfFilteredDTC(Std_ReturnType, "Client1", uint16*)
Figure 7.48: Multiple clients requesting event memory information in parallel
[SWS_Dem_01300] API behavior without set DTC filter dIf any of the APIs re-
quiring a Dem_SetDTCFilter according to [SWS_Dem_00057] is called without
a prior call of Dem_SetDTCFilter for this client, the Dem shall report the Det
[SWS_Dem_01264] dIF Dem_SetDTCFilter is called with an invalid DTCOrigin,
[SWS_Dem_01265] dIF Dem_SetDTCFilter is called with an invalid DTCFormat,
[SWS_Dem_01266] dIn case of calling any subsequent function of Dem_SetDTC-
Filter (see [SWS_Dem_00057]) after the initial Dem_SetDTCFilter did not return
E_OK, the Dem shall shall return E_NOT_OK on this subsequent function call.c()

AUTOSAR CP R20-11
[SWS_Dem_01263] dA call of Dem_SetDTCFilter sets the requested filter on the

event memory assigned to ClientID of the call.c(RS_Diag_04162)
[SWS_Dem_00649] dEach call of Dem_SetDTCFilter shall lead to a reset of the
sequence for that client.c(RS_Diag_04057)
[SWS_Dem_01058] dThe function Dem_SetDTCFilter shall ignore unsupported bits
(refer to configuration parameter DemDtcStatusAvailabilityMask) retrieved in
DTCStatusMask.c()
The parameter DTCFormat of Dem_SetDTCFilter is relevant to decide about spe-
cific protocol characteristics like OBD vs. UDS vs. J1939. The DTCOrigin only refer-
ences the fault memory location.
[SWS_Dem_01066] dThe Det error DEM_E_WRONG_CONFIGURATION shall be re-
ported if the function Dem_SetDTCFilter is called with a value of the parameter DTC-
Format that is not supported per configuration (e.g. if DTCFormat = DEM_DTC_FOR-
MAT_OBD is passed, but OBD is not supported per configuration).c(RS_Diag_04057)
[SWS_Dem_01067] dThe Det error DEM_E_WRONG_CONFIGURATION shall be re-
ported if the function Dem_SetDTCFilter is called with a value of the parameter
DTCOrigin that is not supported per configuration (e.g. if DTCOrigin "DEM_DTC_-
ORIGIN_MIRROR_MEMORY" is passed, but no mirror memory is configured).c()
[SWS_Dem_00061] dThe function Dem_GetNumberOfFilteredDTC shall get the
number of DTCs matching the filter criteria defined by the function call of Dem_Set-
DTCFilter [SWS_Dem_00057].c()
Note:The behaviour of Dem_SetDTCFilter depending APIs with calling Dem_Set-
DTCFilter is described in [SWS_Dem_01300].
[SWS_Dem_00216] dWith each call to the function Dem_GetNextFilteredDTC the
Dem module shall return the next DTC and its associated status matching the filter
criteria defined by the function call of Dem_SetDTCFilter [SWS_Dem_00057].c()
The Dcm calls the function Dem_GetNextFilteredDTC continuously until the return
value of the function is DEM_NO_SUCH_ELEMENT, to receive all DTCs matching the
filter criteria.
[SWS_Dem_00653] d
The API Dem_GetNextFilteredDTC shall not return the value DEM_PENDING
when DTCFormat = DEM_DTC_FORMAT_OBD (indicating emission-related services).c
()
Rationale: The API Dem_GetNextFilteredDTC is used for UDS service 0x19 as
well as OBD services $03/$07/$0A (refer to [SWS_Dem_00301]). UDS service 0x19
is allowed to respond with NRC 0x78 (response pending) to the tester, while the OBD
services are not.
[SWS_Dem_00228] dWith each call to the function Dem_GetNextFilteredDTCAn-
dFDC the Dem module shall return the next DTC and its associated fault detection

AUTOSAR CP R20-11
counter (FDC, refer to [SWS_Dem_00264]) matching the filter criteria defined by the
function call Dem_SetDTCFilter (refer to [SWS_Dem_00057]).c()
[SWS_Dem_00513] dIf the callback-function Dem_GetFaultDetectionCounter re-
turns other than E_OK or is not configured for a DTC filtered by Dem_GetNextFil-
teredDTCAndFDC, this FDC value shall be returned as 0.c()
The Dcm calls the function Dem_GetNextFilteredDTCAndFDC continuously until
the return value of the function is DEM_NO_SUCH_ELEMENT, to receive all DTCs
matching the filter criteria.
Note: Non-Dem-internal calculated fault detection counters are typically requested
from SWCs through the RTE. To indicate an equivalent calltree for these runnables,
a workaround is used: The Dcm main function specifies a trigger to the Dem inter-
face GeneralEvtInfo (operation GetFaultDetectionCounter), which triggers the respec-
tive runnable (refer to RunnableEntity Dem_GetFaultDetectionCounter).
[SWS_Dem_00287] dWith each call to the function Dem_GetNextFilteredDTCAn-
dSeverity the Dem module shall return the next DTC and its associated fault severity
matching the filter criteria defined by the function call Dem_SetDTCFilter (refer to
[SWS_Dem_00057]).c()
The Dcm calls the function Dem_GetNextFilteredDTCAndSeverity continuously
until the return value of the function is DEM_NO_SUCH_ELEMENT, to receive all DTCs
matching the filter criteria.
For information about the functions Dem_GetSeverityOfDTC and Dem_GetFunc-
tionalUnitOfDTC, refer to chapter 7.4.
[SWS_Dem_00595] dThe function Dem_SetFreezeFrameRecordFilter shall set
the static filter criteria attribute “all freeze frame records currently stored in the event
memory” to be used for the subsequent calls of Dem_GetNextFilteredRecord and
Dem_GetNumberOfFreezeFrameRecords. This filter always belongs to primary
memory.c()
[SWS_Dem_00650] dThe filter criteria attributes of Dem_SetFreezeFrameRecord-
Filter shall be used until the next call of Dem_SetFreezeFrameRecordFilter or
Dem initialization. Each call of Dem_SetFreezeFrameRecordFilter shall lead to a
reset of the sequence iterating over freezeframes.c(RS_Diag_04204)
[SWS_Dem_01312] dDem_GetNumberOfFreezeFrameRecords shall retrieve the
number of freeze frame records in primary memory that match the current filter.c(RS_-
Diag_04205)
[SWS_Dem_01313] API behavior without set DTC filter dIf any of the APIs re-
quiring a Dem_SetFreezeFrameRecordFilter is called without a prior call of
Dem_SetFreezeFrameRecordFilter for this client, the Dem shall report the Det

AUTOSAR CP R20-11
[SWS_Dem_00225] dWith each call to the function Dem_GetNextFilteredRecord

the Dem module shall return the next DTC and its associated relative addressed freeze
frame record numbers matching the filter criteria defined by the function call Dem_-
SetFreezeFrameRecordFilter.c()
The client calls the function Dem_GetNextFilteredRecord continuously until the re-
turn value of the function is DEM_NO_SUCH_ELEMENT, to receive all records match-
ing the filter criteria.
[SWS_Dem_00219] dThe function Dem_GetDTCByOccurrenceTime shall provide
the capability to get one DTC stored in the primary event memory of the addressed De-
mEventMemorySet according to the API parameter DTCRequest.c(RS_Diag_04195)
[SWS_Dem_00221] dThe API Dem_GetDTCByOccurrenceTime shall return
DEM_NO_SUCH_ELEMENT, if no DTC is matching the requested occurrence time in
the parameter DTCRequest.c(RS_Diag_04195)
7.11.2.4 Access event related data
This section defines the APIs, to get access to the event related data (refer to chapter
7.7.7.1 and chapter 7.7.7.3) stored with the DTCs in the event memory of the Dem
via diagnostics. Furthermore, access to WWH-OBD relevant PIDs stored in a freeze
frame is made available. Details concerning freeze frame handling can be found in
ISO-14229-1[2] and ISO 27145-3[21].
Example for the mapping of a PID to a DID: PID $04 –> DID 0xF404
Note: The data returned include the DTCSnapshotRecordNumberOfIdentifiers (Num
of DIDs) as defined by ISO-14229-1[2] for the response message to service 0x19 0x05.
[SWS_Dem_01268] dIf the API Dem_SelectFreezeFrameData is called, the Dem
shall use the DTC selected by Dem_SelectDTC and the RecordNumber as a target
for the following API calls:
• Dem_GetNextFreezeFrameData
• Dem_GetSizeOfFreezeFrameSelection
c()
[SWS_Dem_01269] dThe API Dem_SelectFreezeFrameData triggers the Dem in-
ternal Freeze Frame selection process on the event memory assigned to the ClientId.
The Dem shall provide the result of the selection process in the return value of the API
calls following the Dem_SelectFreezeFrameData call, see [SWS_Dem_01268].c()
[SWS_Dem_01270] dIf any of the APIs requiring a Dem_SelectFreezeFrameData
(see [SWS_Dem_01268]) are called without a prior call to Dem_SelectFreeze-
FrameData, the Dem shall report the Det error DET_E_WRONG_CONDITION.c
(SRS_BSW_00369)

AUTOSAR CP R20-11
[SWS_Dem_01271] dIf any of the APIs requiring a Dem_SelectFreezeFrameData

is called without a prior call to Dem_SelectFreezeFrameData, the Dem shall report
the Det error DEM_E_WRONG_CONDITION.c(SRS_BSW_00369)
[SWS_Dem_00071] dThe function Dem_GetNextFreezeFrameData shall copy the
specific data identifiers (DIDs) of the freezeframe record selected by the API Dem_-
SelectFreezeFrameData for the specified ClientId to the destination buffer provided
by the DestBuffer parameter. The Dem shall transmit these data as a complete
record with the Buffer format.c()
For Buffer format see figure 7.49.
[SWS_Dem_00576] dIf the RecordNumber selected by the API Dem_SelectFreeze-
FrameData is set to 0x00, Dem_GetNextFreezeFrameData shall provide the even-
t/DTC specific WWH-OBD equivalent freeze frame record.c()
Note: Retrieving record 0x00 with Dem_SelectFreezeFrameData and Dem_Get-
NextFreezeFrameData is only supported if the Dem module supports WWH-OBD
(refer to DemOBDSupport)
requested freeze frame record
calculated (e.g. 1), or configured
(e.g. first value from list)
RecordNum Num of DIDs 1st DID Data #1 ... Nth DID Data #N
Byte 0 Byte 1 Byte 2..3 Byte 4..j Byte j..k Byte k..(k+2) Byte (k+2)..n
Data element #1 ... Data element #N
Figure 7.49: Buffer format used by Dem_GetNextFreezeFrameData
Note: The data returned include the DTCSnapshotRecordNumber (RecordNum) and

DTCSnapshotRecordNumberOfIdentifiers (Num of DIDs) as defined by ISO-14229-
1[2] for the response message to service 0x19 0x04. In contradiction to the Dcm
PIDstructure handling, the DIDstructure is handled within the Dem module. Therefore,
the Dem returns already full freeze frame records according to the response layout.
This results in an optimized Dem/Dcm interface.
[SWS_Dem_00630] dIf a single DTC is selected and the API Dem_SelectFreeze-
FrameData is called with a valid RecordNumber which is not stored, Dem_Get-
NextFreezeFrameData shall return E_OK and BufSize 0 (empty buffer).c()
[SWS_Dem_00074] dThe function Dem_GetSizeOfFreezeFrameSelection shall
return the size of the requested freeze frame record(s) by Dem_SelectFreeze-
FrameData for the specified ClientId, which represents the number of user data
bytes, including any freeze frame headerinformation (according to the format defined
in [SWS_Dem_00071]).c(RS_Diag_04204)

AUTOSAR CP R20-11
Note: If the record number value 0xFF is requested, the Dem considers the size of all
stored freeze frame records according to [SWS_Dem_00074].
[SWS_Dem_01348] Select freeze frame data for single DTCs only dIn case
the function Dem_SelectFreezeFrameData is called and the DTC selected by
Dem_SelectDTC is not a single DTC but a group of DTC, the Dem shall return
[SWS_Dem_01349] Select extended data record for single DTCs only dIn case
the function Dem_SelectExtendedDataRecord is called and the DTC selected
by Dem_SelectDTC is not a single DTC but a group of DTC, the Dem shall return
[SWS_Dem_01272] dIf the API Dem_SelectExtendedDataRecord is called, the
Dem shall use the DTC selected by Dem_SelectDTC and the ExtendedDataNumber
as a target for the following API calls:
• Dem_GetNextExtendedDataRecord
• Dem_GetSizeOfExtendedDataRecordSelection
c()
[SWS_Dem_01273] dThe API Dem_SelectExtendedDataRecord triggers the Dem
internal extended data record selection process on the event memory assigned to
the ClientId. The Dem shall provide the result of the selection process in the re-
turn value of the API calls following the Dem_SelectExtendedDataRecord, see
[SWS_Dem_01272].c()
[SWS_Dem_01274] dIf any of the APIs requiring a Dem_SelectExtended-
DataRecord (see [SWS_Dem_01272]) are called without a prior call to Dem_Se-
lectExtendedDataRecord, the Dem shall report the Det error DEM_E_WRONG_-
CONDITION.c(SRS_BSW_00369)
[SWS_Dem_00075] dThe API Dem_GetNextExtendedDataRecord shall copy the
complete data of the requested extended data record by Dem_SelectExtended-
DataRecord API for the specified ClientId to the destination buffer (DestBuffer). The
function shall transmit these data as a complete record with the Buffer format. The
extended data record number is placed as the first byte in the copied data.c()
For Buffer format see figure 7.50.
Extended Data Record Buffer
ExtendedData
Data element #1 … Data element #n
RecordNumber
Byte 0 Byte 1 Byte n
Figure 7.50: Buffer format used by Dem_GetNextExtendedDataRecord

AUTOSAR CP R20-11
[SWS_Dem_00631] dIf the API Dem_SelectExtendedDataRecord is called with

a valid DTC and a valid extended data record number which is not stored, the API
shall return E_OK and Dem_GetNextExtendedDataRecord shall return BufSize 0
(empty buffer).c()
[SWS_Dem_00076] dThe function Dem_GetSizeOfExtendedDataRecordSelec-
tion shall return the size of the requested extended data record(s) selected by
Dem_SelectExtendedDataRecord, which represents the number of user data bytes
stored in the extended data record, including any extended data record headerin-
formation (i.e. the extended data record number, different to the format defined in
[SWS_Dem_00075]).c()
Note: If the record number value 0xFE is requested, the Dem considers the size
of all OBD stored extended data records in the range of 0x90 to 0xEF according to
[SWS_Dem_00076].
Note: If the record number value 0xFF is requested, the Dem considers the size
of all stored extended data records (in the range of 0x01 to 0xEF) according to
[SWS_Dem_00076].
The Dcm uses the function Dem_DisableDTCRecordUpdate, if the freeze frame or
extended data of a specific DTC is about to be accessed by subsequent API calls. This
is done to ensure, that the requested data of this DTC are not changed while the Dcm
accesses those by several APIcalls.
[SWS_Dem_00270] dThe function Dem_DisableDTCRecordUpdate shall protect
the event related data of the selected DTC within the selected DTCOrigin from up-
dating or deleting, to allow a consistent read for the following subsequent APIcalls:
Dem_GetSizeOfFreezeFrameSelection and
Dem_GetNextFreezeFrameData
Dem_GetSizeOfExtendedDataRecordSelection and
Dem_GetNextExtendedDataRecord.
c()
New and other events including their associated freeze frames and extended data
records can still be added to and changed in the event memory as long as space
is available.
Note: Event related data might still be updated in background (e.g. Dem-internal data
elements).
Note: The function Dem_DisableDTCRecordUpdate does not affect the UDS status
information update.
[SWS_Dem_00271] dThe function Dem_EnableDTCRecordUpdate shall release
the currently disabled DTC which has been protected by the function Dem_Dis-
ableDTCRecordUpdate, so that the data can be updated again.c()

AUTOSAR CP R20-11
The function Dem_EnableDTCRecordUpdate is the counterpart to the function

Dem_DisableDTCRecordUpdate.
The Dcm calls the function Dem_EnableDTCRecordUpdate after the freeze frame
and extended data of the specific DTC were protected by the function Dem_Dis-
ableDTCRecordUpdate, after the access by subsequent APIcalls is finished.
[SWS_Dem_00648] dIf development error detection is enabled and the function Dem_-
DisableDTCRecordUpdate is called while another DTC is locked by the same client,
the Dem module shall report the Det DEM_E_WRONG_CONDITION.c()
7.11.2.5 Clear diagnostic information
The Dem provides the functionality to clear DTCs to the Dcm and other diagnostic
clients. The general DTC clearing process is described in chapter 7.7.2.2.
7.11.2.6 Control DTC setting
[SWS_Dem_01290] DTCs affected by Dem_DisableDTCSetting and Dem_En-

ableDTCSetting dCalls of the APIs Dem_DisableDTCSetting and Dem_En-
ableDTCSetting have effect on all events and UDS status bytes assigned the
DemEventMemorySet referenced by the clientId of the call. DTCs not referenced
from this DemEventMemorySet are not affected.c()
[SWS_Dem_00079] dIf the function Dem_DisableDTCSetting is called, the Dem
shall disable the storage of corresponding events and UDS status byte updates.c()
The function Dem_DisableDTCSetting is used in case of an induced failure situation
in a system, e.g. during flashreprogramming of one ECU in a network. In that case
all the ECUs are commanded via diagnostic request (forwarded from Dcm by using
Dem_DisableDTCSetting / Dem_EnableDTCSetting) to ignore DTC reports, as
the flashed ECU is not participating in the normal communication anymore.
Note: If one of the other networked ECUs needs one of the signals, which are now
missing, for this case a failsafereaction of the ECU cannot be assigned to the UDS
status byte updates, as these are also suppressed during disabled DTC setting.
[SWS_Dem_00080] dIf the function Dem_EnableDTCSetting is called, the Dem shall
enable the storage of corresponding events and UDS status byte.c(RS_Diag_-
04115)
[SWS_Dem_00626] dWhen DTC setting is disabled, all status reports from the
API Dem_SetEventStatus and Dem_SetEventFailedWithSyncFreezeFrame
for the related events shall be ignored (no change of UDS status byte) by the Dem.c
(RS_Diag_04115)

AUTOSAR CP R20-11
Note: This is similar like the enable condition handling (refer to [SWS_Dem_00449]).
It has no impact on Dem_ResetEventDebounceStatus, Dem_ResetEventStatus
and Dem_ClearDTC. In case of Dem-internal debouncing the related fault detection
counter will be frozen or reset (refer to chapter Figure 7.31 and Figure 7.34).
7.11.2.7 Asynchronous Dcm operations
Most of the APIs of the Dem/Dcm interface depend on NVRAM data. There-
fore, an asynchronous processing of these APIs is realized by using the additional
“DEM_PENDING” return value.
7.11.3 Interaction with J1939 Diagnostic Manager (J1939)
[SWS_Dem_00971] dIn case the TestFailed bit of an event within an primary event
memory changes and a J1939 DTC number is assigned to that event, the function
J1939Dcm_DemTriggerOnDTCStatus shall be called for each DemClient referencing
this DemEventMemorySetc(RS_Diag_04112)
7.11.4 Interaction with Function Inhibition Manager (FIM)
The purpose of the Function Inhibition Manager is to control (enable/disable) func-

tion entities within software components based on inhibit conditions such as detected
errors. The Dem contribution to this functionality is to provide the monitoring status
change and the DemComponent information to the FiM.
[SWS_Dem_00029] dIf DemTriggerFiMReports is set to True, the Dem module shall
notify the FiM module (refer to [8]) on each change of the monitoring status (refer
also to [SWS_Dem_00016]), by calling the function FiM_DemTriggerOnEventStatus
(with same syntax as <Module>_DemTriggerOnMonitorStatus) in the context of
Dem_SetEventStatus.c(RS_Diag_04031)
The Fim uses the function Dem_GetMonitorStatus for possible plausibility checks,
rebuilding, etc. of inhibition relations.
[SWS_Dem_01325] d The Dem shall call FiM_DemInit after the monitor and compo-
nent states have been initialized.c(RS_Diag_04031)
[SWS_Dem_01189] dIf DemTriggerFiMReports is set to True, the Dem shall call
FiM_DemInit during Dem_Init to trigger the initialization of the permissions inside
the Fim(independent of trigger or polling mode). The FiM_DemInit shall not be called
at any other point in time.c(RS_Diag_04031)

AUTOSAR CP R20-11
7.11.5 Interaction with NVRAM Manager (NvM)
Typically, the Dem module uses nonvolatile memory blocks (configurable in size by
the NVRAM Manager [5]) to achieve permanent storage of UDS status information,
event related data and required internal states (e.g. retrieve status at startup). Each
nonvolatile memory block used from the Dem, needs also to be configured (refer to
DemNvRamBlockId). The number, the type, and the content of the used nonvolatile
memory blocks are not prescribed. These shall be handled implementation specific.
The NvM usage can also be deactivated by configuration (refer to multiplicity of Dem-
NvRamBlockId), so that the Dem will work based on RAM only.
[SWS_Dem_00339] dThe Dem module shall verify the validity (which relates to block
states), integrity (which relates to CRC results), and for general NvM-reading errors of
its nonvolatile blocks (before using the respective data).c(RS_Diag_04107)
Usually this verification is done in the API Dem_Init by using NvM_GetErrorStatus for
these blocks, which are read by the ECU State Manager (refer to API NvM_ReadAll).
Note: For the non-volatile data of the Dem module, it is recommended to configure a
CRC in the NvM.
[SWS_Dem_00578] dIf the NVM module was not able to read some nonvolatile data
of the Dem module, the Dem module shall initialize all non-volatile data with their initial
values.c(SRS_Mem_08549)
Note: To avoid inconsistencies between readable blocks and erroneous blocks, all
nonvolatile data are initialized. The initialization is done to allow the fault detection
mechanism of the NvM module, to report the respective reading error(s) to the Dem
module (refer to Dem_SetEventStatus). These errors denote the defective NVRAM.
[SWS_Dem_00340] dAfter the API Dem_Init has finished, the Dem shall be fully
operational.c(SRS_BSW_00101)
[SWS_Dem_01237] dIf a DTC is reported as failed (UDS status testfailed flag changes
from 0->1) and gets newly stored to the event memory (no entry existed for this
DTC) and this DTC is configured with DemNvStorageStrategy = IMMEDIATE_-
AT_FIRST_OCCURRENCE, the Dem shall trigger the immediate storage to NvM.c(RS_-
Diag_04077)
[SWS_Dem_01238] dIf a DTC is configured with DemNvStorageStrategy = DUR-
ING_SHUTDOWN, any change of its data (DTC, UDS status, event memory entry) shall
only be stored to NvM during shutdown.c(RS_Diag_04077)
[SWS_Dem_00551] dIf immediate nonvolatile storage is enabled for a specific DTC,
the Dem module shall trigger the storage for new event memory entries and after
every change of the event related data (event memory entry was updated).c(RS_-
Diag_04077)
Note: For event memory entries, which are stored immediately, it is necessary to
ensure data consistency (e.g. with the UDS status byte) during Dem_Init.

AUTOSAR CP R20-11
Note: If the immediate nonvolatile storage is disabled, the event memory entry
and its event related data are stored persistently during the shutdown phase (refer to
[SWS_Dem_00102], [SWS_Dem_00341] and the note below).
Note: Write operations to NVRAM will perform in any case at ECU shutdown.
[SWS_Dem_00102] dThe API Dem_Shutdown shall finalize all pending operations in
the Dem module to prepare the internal states and data for transfer to the NVRAM. The
event memory shall be locked and not modified until the API Dem_Init is recalled.c
(SRS_BSW_00336)
[SWS_Dem_00341] dFor changed nonvolatile data, the Dem module shall trigger the
storage to NVRAM before or during Dem_Shutdown.c(SRS_BSW_00336)
Based on the Dem configuration and implementation, the copying process to NVRAM
of those Demrelated NvMblocks to be stored after Dem_Shutdown, is performed by
the API NvM_WriteAll called by the ECU State Manager.
If the ECU power supply is disconnected before the NvM has finished copying all data
to NVRAM, these data will be incomplete/inconsistent or not stored. At next startup, the
events of the last operating cycle could not be found anymore. Therefore, the NVRAM
Manager configuration provides mechanisms for data consistency, like redundant data
blocks.
[SWS_Dem_00164] dThe Dem module shall use the APIs NvM_WriteBlock and
NvM_ReadBlock of the NVRAM Manager, if there is the necessity to store and restore
data between Dem_Init and Dem_Shutdown.c(RS_Diag_04077)
Note: The NvM module realizes a retry mechanism for block reading and writing.
Therefore, the Dem module does not implement any retry mechanism for its nonvolatile
blocks.
[SWS_Dem_00579] dIf the NVM module was not able to write (some) nonvolatile data
of the Dem module, the Dem module shall ignore the reported negative return values
by the NvM.c(SRS_BSW_00171)
Note: If writing of nonvolatile Dem data fails, the Dem module is not able to perform
any adequate reaction.
7.11.6 Interaction with Default Error Tracer (Det)
The interaction with the Det is described in chapter 7.13.
7.11.7 Required data by the Dem module
The Dem module requires different information for internal computation/processing.

If this information is provided by SWCs (as provide-ports), they are described in the
respective ServiceNeeds (diagnostic capabilities).

AUTOSAR CP R20-11
One kind of information required by the Dem module are event related data (repre-
sented by freeze frames and extended data records, refer to chapter 7.7.7).
Note: For OBDrelevant ECUs, the Dem module could access (via the data element
interface) on the following data values:
• engine temperature engine speed
• vehicle speed (refer to [SWS_Dem_00346], PID $0D)
• distance information
• programming event
• ambient temperature
• ambient pressure
• accelerator pedal information
However, the list of data elements and their required size and resolution are
implementationspecific and will be configured in OBD and handled during integration
process. For example, the vehicle speed, accelerator pedal information, ambient tem-
perature, etc. are necessary to evaluate the cycle conditions of the IUMPR General
Denominator. Similar inputs are necessary for the PID computation (e.g. the engine
temperature for the computation of the WarmUp cycle or the WarmUp cycle condition
itself). These variables are typically accessed through the RTE.
7.11.8 Scaling information on Service Interfaces
The SoftwareComponentTemplate [22] defines the meta-class SwDataDefProps which

covers all properties of a particular data object under various aspects. This chap-
ter describes two alternative workflows how the SwDataDefProps properties such as
CompuMethod, DataContraints and Units can be used within the Dem Service SWC
and make them there available per DemExternalSRDataElementClass.
[SWS_Dem_CONSTR_6117] dThe aggregation of DemTextTableMapping at De-
mAlternativeDataType is only valid if the category of the CompuMethod of the
DataType referenced by DemApplicationDataType has category set to TEXT-
TABLE or SCALE_LINEAR_AND_TEXTTABLE.c()
Work flow 1
This work flow is the use of a EcucForeignReference inside the generated EcuC
values. While importing the DEXT [23] information the DemDiagnosticDataEle-
mentRef is derived and holds a EcucForeignReference to a DiagnosticDataElement
in the DEXT [23] file. This EcucForeignReference enables the access to all Sw-
DataDefProps (BaseTyoe, CompuMethod, DatConstr, etc.) of the corresponding Di-
agnosticDataElement. The container DemAlternativeDiagnosticDataElement

AUTOSAR CP R20-11
aggregates this EcucForeignReference. In the process step of generating the cor-

responding Service SWC all needed content will be copied directly based on the
EcucForeignReference from DEXT [23] to the Service SWC. In this work flow the
existence of the DEXT file while the generation of the Service SWC is required.
OEM Supplier
DEXT
EcuC
DiagnosticDataIdentifier
DEM Service
-> DiagnosticDataElement DemAlternativeDataType.Dem
-> SwDataDefProps ApplicationDataType SWC
-> CompuMethodRef
CompuMethod
-> ASCII_10Byte SWC DEXT based
depends on
EcuCValues
DEM
Internal Configuration
EcuCValues
* The DEXT importer generates one SWC which contains all SwDataDefProps and the ECUC parameter
(DemAlternativeDataType.DemApplicationDataType) refers to the SWC. Within the SWBuild processing this reference to SWC is
taken and the required contents (CompuMethod / DataContraints / Units) are included into the Dem SWCD.
Figure 7.51: Workflow 1
Work flow 2
This work flow is that while importing the DEXT [23] information beside the EcuC
values also a SWC fragment is generated. In this SWC fragment all needed
SwDataDefProps are directly copied from the DEXT [23] file. Inside the gener-
ated EcuC values the EcuC Parameter DemApplicationDataType refers to the
SWC fragment and enables the access to all SwDataDefProps (BaseTyoe, Com-
puMethod, DatConstr, etc.). In the process step of generating the corresponding
Service SWC all needed content will be included based on the reference from
DemApplicationDataType to the SWC fragment. In this work flow the existence
of the DEXT [23] file while the generation of the Service SWC is not required.

AUTOSAR CP R20-11
OEM Supplier
DEXT
EcuC
DiagnosticDataIdentifier
DEM Service
-> DiagnosticDataElement DemAlternativeDataType.Dem
-> SwDataDefProps ApplicationDataType SWC
-> CompuMethodRef
CompuMethod
-> ASCII_10Byte SWC DEXT based
depends on
EcuCValues
DEM
Internal Configuration
EcuCValues
* The DEXT importer generates one SWC which contains all SwDataDefProps and the ECUC parameter
(DemAlternativeDataType.DemApplicationDataType) refers to the SWC. Within the SWBuild processing this reference to SWC is
taken and the required contents (CompuMethod / DataContraints / Units) are included into the Dem SWCD.
Figure 7.52: Workflow 2
7.12 Version check

For details refer to the chapter 5.1.8 “Version Check” in SWS_BSWGeneral.
7.13 Error classification

Section 7.13 "Error Handling" of the document "General Specification of Basic Software
Modules" describes the error handling of the Basic Software in detail. Above all, it
constitutes a classification scheme consisting of five error types which may occur in
BSW modules.
Based on this foundation, the following section specifies particular errors arranged in
the respective subsections below.

AUTOSAR CP R20-11
7.13.1 Development Errors
[SWS_Dem_00173] d
Type of error Related error code Error value
API function called with a parameter value, which DEM_E_WRONG_CONFIGURATION 0x10
is not allowed by active configuration
API function called with a NULL pointer DEM_E_PARAM_POINTER 0x11
API function called with wrong parameter value DEM_E_PARAM_DATA 0x12
API function called with wrong length parameter DEM_E_PARAM_LENGTH 0x13
value
Dem initialisation failed (refer to SWS_ DEM_E_INIT_FAILED 0x14
BSW_00151)
API function called before the Dem module has DEM_E_UNINIT 0x20
been full initialized (refer to
[SWS_Dem_00124],[SWS_Dem_00364]) or after
the Dem module has been shut down (refer to
[SWS_Dem_00368])
Required conditions for the respective API call are DEM_E_WRONG_CONDITION 0x40
not fulfilled (e.g. an invalid status change was
initiated, or a filter was not set correctly, etc. - refer
to [SWS_Dem_00518]).
Dem_DcmGetAvailableOBDMIDs called with DEM_E_INVALID_OBDMID 0x50
invalid OBDMID.
c(SWS_BSW_00050, SWS_BSW_00212)
[SWS_Dem_00124] dIf DemDevErrorDetect is set to TRUE and any Dem API ex-
cluding :
• Dem_SetEventAvailable
• Dem_GetVersionInfo
• Dem_MainFunction
is called before Dem has been fully initialized, the Dem module shall set the error code
DEM_E_UNINIT.c(SRS_BSW_00406)
Note: If development error detection is disabled and the Dem is not fully initialized, the
behavior of the APIs is undefined.
[SWS_Dem_01324] d During Dem_Init the Dem initializes the monitor and component
states. After this point in time, the Dem shall return E_OK on the APIs Dem_GetMoni-
torStatus and Dem_GetComponentFailed.c()
[SWS_Dem_00364] dIf development error detection is enabled and any instance calls
Dem_SetEventStatus or Dem_ResetEventDebounceStatus before the Dem was

AUTOSAR CP R20-11
preinitialized, the Dem module shall set the error code DEM_E_UNINIT.c(SRS_BSW_-
00406)
Note: If development error detection is disabled and the Dem is not preinitialized, the
behavior of these APIs is undefined.
[SWS_Dem_00368] dIf development error detection is enabled and any instance calls
any Dem API, excluding Dem_SetEventStatus, Dem_ResetEventDebounceSta-
tus, Dem_GetVersionInfo and Dem_MainFunction, after Dem_Shutdown has
been called, the Dem module shall set the error code DEM_E_UNINIT until Dem_Init
is called again.c(SRS_BSW_00337)
Note: If development error detection is disabled and the Dem is shut down, the behavior
of these APIs is undefined.
[SWS_Dem_00518] dIf development error detection is enabled and a Dem function is
called with required preconditions not fulfilled, the Dem module shall set the error code
DEM_E_WRONG_CONDITION.c(RS_Diag_04057)
Note: For example, Dem_GetNextFilteredDTCAndFDC is called, after Dem_Set-
DTCFilter with FilterForFaultDetectionCounter = FALSE was called.
7.13.2 Runtime Errors
[SWS_Dem_91035] d
Type of error Related error code Error value
The UDS status corresponding to a changed DEM_E_UDS_STATUS_PROCESSING_FAILED 0x21
monitor status could not be processed.
No valid data for data element available by SW-C DEM_E_NODATAAVAILABLE 0x30
or BSW call
c()
7.13.3 Transient Faults
There are no transient faults.
7.13.4 Production Errors
There are no production errors.

AUTOSAR CP R20-11
7.13.5 Extended Production Errors
There are no extended production errors.

AUTOSAR CP R20-11
8 API specification
The figures below show the interfaces between Dem and its surrounding SW-Cs and
BSW modules. The description of the interface shall give a simple overview of these
relations.
«module» «... «interface»
Dcm Dem Dem_Det_Optional «modu...
Det
«function»
«optional» ::Det_ReportError
«module» Det_ReportError(return, ModuleId, InstanceId, ApiId, ErrorId)
[BSW]
«interface»
«module» Dem_Fim_Optional
[SWC]
«function»
«optional» ::FiM_DemInit
FiM_DemInit()
::FiM_DemTriggerOnMonitorStatus
«interface» FiM_DemTriggerOnMonitorStatus(EventId)
SchM_Dem_Mandatory
«scheduled_function» «interface»
::Dem_MainFunction Fim_Dem_Mandatory «mandatory»
Dem_MainFunction()
«function» «modu...
::Dem_GetMonitorStatus FiM
Dem_GetMonitorStatus(return, EventID, MonitorStatus)
«optional»
«module» «module»
SchM EcuM «interface»
Dem_NvM_Optional
«function»
::NvM_SetRamBlockStatus
«optional» NvM_SetRamBlockStatus(return, BlockId, BlockChanged) «modu...
«optional»
::NvM_ReadBlock NvM
«interface» NvM_ReadBlock(return, BlockId, NvM_DstPtr)

EcuM_Dem_Optional ::NvM_GetErrorStatus
NvM_GetErrorStatus(return, BlockId, RequestResultPtr)
«function» ::NvM_WriteBlock
::Dem_Shutdown NvM_WriteBlock(return, BlockId, NvM_SrcPtr)
Dem_Shutdown()
::Dem_Init
Dem_Init(ConfigPtr)
::Dem_PreInit
Dem_PreInit()
Figure 8.1: Overview of interfaces between the Dem and other BSW modules

AUTOSAR CP R20-11
«m... «interface» «m...

Dem BSW_Dem_Use [BSW]
«function»
::Dem_ClearDTC «use»
+ Dem_ClearDTC(Std_ReturnType, uint8)
::Dem_GetVersionInfo
+ Dem_GetVersionInfo(Std_VersionInfoType**)
«interface»
BSW/SWC_Dem_Use
«function»
::Dem_GetDTCOfEvent
+ Dem_GetDTCOfEvent(Std_ReturnType, Dem_EventIdType, Dem_DTCFormatType, uint32**)
::Dem_SetEventDisabled
+ Dem_SetEventDisabled(Std_ReturnType, Dem_EventIdType)
::Dem_GetEventExtendedDataRecordEx
«use»
+ Dem_GetEventExtendedDataRecordEx(Std_ReturnType, Dem_EventIdType, uint8, uint8**, uint16**): void
::Dem_GetEventFreezeFrameDataEx
+ Dem_GetEventFreezeFrameDataEx(Std_ReturnType, Dem_EventIdType, uint8, uint16, uint8**, uint16**): void
::Dem_GetEventMemoryOverflow
+ Dem_GetEventMemoryOverflow(Std_ReturnType, uint8, Dem_DTCOriginType, boolean**): void
::Dem_SetDTCSuppression
+ Dem_SetDTCSuppression(Std_ReturnType, uint8, boolean): void
::Dem_GetIndicatorStatus
+ Dem_GetIndicatorStatus(Std_ReturnType, uint8, Dem_IndicatorStatusType**)
::Dem_SetEnableCondition
+ Dem_SetEnableCondition(Std_ReturnType, uint8, boolean)
::Dem_SetStorageCondition
+ Dem_SetStorageCondition(Std_ReturnType, uint8, boolean): void
::Dem_RepIUMPRDenRelease
+ Dem_RepIUMPRDenRelease(Std_ReturnType, Dem_RatioIdType)
::Dem_ResetEventDebounceStatus
+ Dem_ResetEventDebounceStatus(Std_ReturnType, Dem_EventIdType, Dem_DebounceResetStatusType) «m...
::Dem_GetEventUdsStatus [SWC]
+ Dem_GetEventUdsStatus(Std_ReturnType, Dem_EventIdType, Dem_UdsStatusByteType**)
::Dem_SetPtoStatus
«use»
+ Dem_SetPtoStatus(Std_ReturnType, boolean)
::Dem_RepIUMPRFaultDetect
+ Dem_RepIUMPRFaultDetect(Std_ReturnType, Dem_RatioIdType)
«interface»
SWC_Dem_Use
«function»
::Dem_ResetEventStatus
+ Dem_ResetEventStatus(Std_ReturnType, Dem_EventIdType)
::Dem_PrestoreFreezeFrame «use»
+ Dem_PrestoreFreezeFrame(Std_ReturnType, Dem_EventIdType)
::Dem_RestartOperationCycle
+ Dem_RestartOperationCycle(Std_ReturnType, uint8)
::Dem_SetEventStatus
+ Dem_SetEventStatus(Std_ReturnType, Dem_EventIdType, Dem_EventStatusType)
::Dem_ClearPrestoredFreezeFrame
+ Dem_ClearPrestoredFreezeFrame(Std_ReturnType, Dem_EventIdType)
::Dem_GetFaultDetectionCounter
+ Dem_GetFaultDetectionCounter(Std_ReturnType, Dem_EventIdType, sint8**)
Figure 8.2: Overview of interfaces between the Dem and other BSW modules (in general)

AUTOSAR CP R20-11
«module» «interface» «module»

Dem Dcm_Dem_Configurable Dcm
«function»
::Dem_DcmReadDataOfPID01
+ Dem_DcmReadDataOfPID01(return, PID01value)
::Dem_DcmGetInfoTypeValue08
+ Dem_DcmGetInfoTypeValue08(return, OpStatus, Iumprdata08, Iumprdata08BufferSize)
«realize» ::Dem_DcmGetInfoTypeValue0B
«configurable»
+ Dem_DcmGetInfoTypeValue0B(return, OpStatus, Iumprdata0B, Iumprdata0BBufferSize)
::Dem_DcmReadDataOfPID4D
+ Dem_DcmReadDataOfPID4D(return, PID4Dvalue)
::Dem_DcmReadDataOfPID1C
+ Dem_DcmReadDataOfPID1C(return, PID1Cvalue)
::Dem_DcmReadDataOfPID4E
+ Dem_DcmReadDataOfPID4E(return, PID4Evalue)
«optional»
«interface»
Dcm_Dem_Optional
«function»
::Dem_SetFreezeFrameRecordFilter
+ Dem_SetFreezeFrameRecordFilter(return, ClientId, DTCFormat)
::Dem_ClearDTC
+ Dem_ClearDTC(return, ClientId)
::Dem_GetNextFilteredDTC
+ Dem_GetNextFilteredDTC(return, ClientId, DTC, DTCStatus)
::Dem_GetSeverityOfDTC
+ Dem_GetSeverityOfDTC(return, DTCSeverity, ClientId)
::Dem_GetNumberOfFilteredDTC
+ Dem_GetNumberOfFilteredDTC(return, ClientId, NumberOfFilteredDTC)
::Dem_SetDTCFilter
+ Dem_SetDTCFilter(return, ClientId, DTCStatusMask, DTCFormat, DTCOrigin, FilterWithSeverity, DTCSeverityMask, FilterForFaultDetectionCounter)
::Dem_GetTranslationType
+ Dem_GetTranslationType(return, ClientId)
::Dem_GetDTCStatusAvailabilityMask
+ Dem_GetDTCStatusAvailabilityMask(return, ClientId, DTCStatusMask, DTCOrigin)
::Dem_GetNextFilteredDTCAndFDC
+ Dem_GetNextFilteredDTCAndFDC(return, ClientId, DTC, DTCFaultDetectionCounter)
::Dem_GetStatusOfDTC
+ Dem_GetStatusOfDTC(return, ClientId, DTCStatus)
::Dem_GetSizeOfFreezeFrameSelection
+ Dem_GetSizeOfFreezeFrameSelection(return, ClientId, SizeOfFreezeFrame)
::Dem_DcmReadDataOfOBDFreezeFrame
+ Dem_DcmReadDataOfOBDFreezeFrame(return, PID, DataElementIndexOfPID, DestBuffer, BufSize)
::Dem_GetNextExtendedDataRecord
+ Dem_GetNextExtendedDataRecord(return, ClientId, DestBuffer, BufSize)
::Dem_GetDTCByOccurrenceTime
+ Dem_GetDTCByOccurrenceTime(return, ClientId, DTCRequest, DTC)
::Dem_GetNextFilteredRecord
+ Dem_GetNextFilteredRecord(return, ClientId, DTC, RecordNumber)
::Dem_DisableDTCSetting
+ Dem_DisableDTCSetting(return, ClientId)
::Dem_EnableDTCRecordUpdate
+ Dem_EnableDTCRecordUpdate(return, ClientId)
::Dem_GetNextFreezeFrameData
+ Dem_GetNextFreezeFrameData(return, ClientId, DestBuffer, BufSize)
::Dem_GetNextFilteredDTCAndSeverity
+ Dem_GetNextFilteredDTCAndSeverity(return, ClientId, DTC, DTCStatus, DTCSeverity, DTCFunctionalUnit)
::Dem_GetSizeOfExtendedDataRecordSelection
+ Dem_GetSizeOfExtendedDataRecordSelection(return, ClientId, SizeOfExtendedDataRecord)
::Dem_DisableDTCRecordUpdate
+ Dem_DisableDTCRecordUpdate(return, ClientId)
Figure 8.3: Overview of interfaces between the Dem and Dcm

AUTOSAR CP R20-11
8.1 Imported Types

This section lists all types included from other modules.
[SWS_Dem_00176] d
Module Header File Imported Type
Dcm Rte_Dcm_Type.h Dcm_OpStatusType
NvM Rte_NvM_Type.h NvM_BlockIdType
Rte_NvM_Type.h NvM_RequestResultType
Std Std_Types.h Std_ReturnType
Std_Types.h Std_VersionInfoType
c(SRS_BSW_00301)
8.2 Type definitions

The following Data Types shall be used for the functions defined in this specification.
8.2.1 Dem data types
8.2.1.1 Dem_ComponentIdType
[SWS_Dem_01114] d
Name Dem_ComponentIdType
Kind Type
Derived from uint16
Range 1..65535 – Internal identifier of a monitored
component. Remark: 0 is not a
valid value
Description Identification of a DemComponent by assigned ComponentId. The ComponentId is automatically
assigned by the Dem.
Available via Dem.h
c()
8.2.1.2 Dem_ConfigType
[SWS_Dem_00924] d

AUTOSAR CP R20-11
Name Dem_ConfigType
Kind Structure
Elements implementation specific
Type –
Comment –
Description This type of the external data structure shall contain the post build initialization data for the Dem.
Available via Dem.h
c()
8.2.1.3 Dem_EventIdType
This data type is used in both, C-APIs and service interfaces. It’s definition is available
in chapter 8.6.1.8.
8.2.1.4 Dem_EventStatusType
in chapter 8.6.1.9.
8.2.1.5 Dem_DebouncingStateType
in chapter 8.6.1.5.
8.2.1.6 Dem_DebounceResetStatusType
in chapter 8.6.1.6.
8.2.1.7 Dem_UdsStatusByteType
in chapter 8.6.1.21.
8.2.1.8 Dem_IndicatorStatusType

AUTOSAR CP R20-11
8.2.1.9 Dem_MonitorDataType
8.2.1.10 Dem_MonitorStatusType
8.2.1.11 Dem_DTCKindType
[SWS_Dem_00932] d
Name Dem_DTCKindType
Kind Type
Derived from uint8
Range DEM_DTC_KIND_ALL_DTCS 0x01 Select all DTCs
DEM_DTC_KIND_EMISSION_ 0x02 Select OBD-relevant DTCs
REL_DTCS
Description This type is used to filter DTCs for their kind.
Available via Dem_J1939Dcm.h
c(RS_Diag_04129)
8.2.1.12 Dem_DTCFormatType
8.2.1.13 Dem_DTCOriginType
in chapter 8.6.1.4.
8.2.1.14 Dem_DTCRequestType
[SWS_Dem_00935] d

AUTOSAR CP R20-11
Name Dem_DTCRequestType
Kind Type
Derived from uint8
Range DEM_FIRST_FAILED_DTC 0x01 first failed DTC requested
DEM_MOST_RECENT_FAILED_ 0x02 most recent failed DTC requested
DTC
DEM_FIRST_DET_ 0x03 first detected confirmed DTC
CONFIRMED_DTC requested
DEM_MOST_REC_DET_ 0x04 most recently detected confirmed
CONFIRMED_DTC DTC requested
Description This type is used to request a DTC with specific attributes.
Available via Dem.h
c(RS_Diag_04195)
8.2.1.15 Dem_DTCTranslationFormatType
[SWS_Dem_00936] d
Name Dem_DTCTranslationFormatType
Kind Type
Derived from uint8
Range DEM_DTC_TRANSLATION_ 0x00 ISO15031-6 DTC format/SAE
ISO15031_6 J2012-DA_DTCFormat_00 DTC
format
DEM_DTC_TRANSLATION_ 0x01 ISO14229-1 DTC format
ISO14229_1
DEM_DTC_TRANSLATION_ 0x02 SAEJ1939-73 DTC format
SAEJ1939_73
DEM_DTC_TRANSLATION_ 0x03 ISO11992-4 DTC format
ISO11992_4
DEM_DTC_TRANSLATION_ 0x04 SAE_J2012-DA_DTCFormat_04
J2012DA_FORMAT_04 DTC format
Description DTC translation format as defined in ISO14229-1.
Available via Dem.h
c(RS_Diag_04067)
8.2.1.16 Dem_DTCSeverityType
[SWS_Dem_00937] d

AUTOSAR CP R20-11
Name Dem_DTCSeverityType
Kind Bitfield
Derived from uint8
Kind Name Mask Description
Elements
bit DEM_SEVERITY_NO_ 0x00 No severity information available
SEVERITY
bit DEM_SEVERITY_WWHOBD_ 0x01 No class information
CLASS_NO_CLASS
bit DEM_SEVERITY_WWHOBD_ 0x02 WWH-OBD Class A
CLASS_A
bit DEM_SEVERITY_WWHOBD_ 0x04 WWH-OBD Class B1
CLASS_B1
bit DEM_SEVERITY_WWHOBD_ 0x08 WWH-OBD Class B2
CLASS_B2
bit DEM_SEVERITY_WWHOBD_ 0x10 WWH-OBD Class C
CLASS_C
bit DEM_SEVERITY_ 0x20 maintenance required
MAINTENANCE_ONLY
bit DEM_SEVERITY_CHECK_AT_ 0x40 check at next halt
NEXT_HALT
bit DEM_SEVERITY_CHECK_ 0x80 Check immediately
IMMEDIATELY
Description Type definition of DTCSeverityMask / DTCSeverity byte containing the DTC severity and DTC class
information according to ISO 14229-1 Annex D.3. The upper 3 bits (bit 7-5) are used to represent
the DTC severity information. The lower 5 bits (bit 4-0) are used to represent the DTC class
information.
Available via Dem.h
c()
8.2.1.17 Dem_RatioIdType
8.2.1.18 Dem_DTRControlType
in chapter 8.6.1.7.
8.2.1.19 Dem_InitMonitorReasonType

AUTOSAR CP R20-11
8.2.1.20 Dem_IumprDenomCondIdType
8.2.1.21 Dem_IumprDenomCondStatusType
8.2.1.22 Dem_J1939DcmDTCStatusFilterType
[SWS_Dem_00945] d
Name Dem_J1939DcmDTCStatusFilterType
Kind Type
Derived from uint8
Range DEM_J1939DTC_ACTIVE 0 active DTCs
DEM_J1939DTC_PREVIOUSLY_ 1 previously active DTCs
ACTIVE
DEM_J1939DTC_PENDING 2 pending DTCs
DEM_J1939DTC_PERMANENT 3 permanent DTCs
DEM_J1939DTC_CURRENTLY_ 4 currently active DTC
ACTIVE
Description The type to distinguish which DTCs should be filtered.
Available via Dem.h
c(RS_Diag_04112)
8.2.1.23 Dem_J1939DcmSetClearFilterType
[SWS_Dem_00946] d
Name Dem_J1939DcmSetClearFilterType
Kind Type
Derived from uint8
Range DEM_J1939DTC_CLEAR_ 0 active DTCs
ACTIVE
DEM_J1939DTC_CLEAR_ 1 previously active DTCs
PREVIOUSLY_ACTIVE
DEM_J1939DTC_CLEAR_ 2 active and previously active DTCs
ACTIVE_AND_PREVIOUSLY_
ACTIVE
5

AUTOSAR CP R20-11
4
Description The type to distinguish which DTCs gets cleared
Available via Dem.h
c(RS_Diag_04112)
8.2.1.24 Dem_J1939DcmSetFreezeFrameFilterType
[SWS_Dem_00947] d
Name Dem_J1939DcmSetFreezeFrameFilterType
Kind Type
Derived from uint8
Range DEM_J1939DCM_ 0 FreezeFrame (DM04)
FREEZEFRAME
DEM_J1939DCM_EXPANDED_ 1 ExpandedFreezeFrame (DM25)
FREEZEFRAME
DEM_J1939DCM_SPNS_IN_ 2 SPNs in ExpandedFreezeFrame
EXPANDED_FREEZEFRAME (DM24)
Description The type to distinguish which DTCs gets cleared
Available via Dem.h
c()
8.2.1.25 Dem_J1939DcmLampStatusType
[SWS_Dem_00948] d
Name Dem_J1939DcmLampStatusType
Kind Structure
Elements LampStatus
Type uint8
Comment lamp status
FlashLampStatus
Type uint8
Comment flash lamp status
Description For details refer SAE J1939-73
Available via Dem.h
c(RS_Diag_04110)

AUTOSAR CP R20-11
8.2.1.26 Dem_J1939DcmDiagnosticReadiness1Type
[SWS_Dem_00949] d
Name Dem_J1939DcmDiagnosticReadiness1Type
Kind Structure
ActiveTroubleCodes
Elements Type uint8
Comment Number of active DTCs
PreviouslyActiveDiagnosticTroubleCodes
Type uint8
Comment Number of previously active DTCs
OBDCompliance
Type uint8
Comment OBD Compliance
ContinuouslyMonitoredSystemsSupport_Status
Type uint8
Comment Identifies the continuously monitored system support and status
NonContinuouslyMonitoredSystemsSupport5
Type uint8
Comment Identifies the non-continuously monitored systems support (byte5)
NonContinuouslyMonitoredSystemsSupport6
Type uint8
Comment Identifies the non-continuously monitored systems support (byte6)
NonContinuouslyMonitoredSystemsStatus7
Type uint8
Comment Identifies the non-continuously monitored systems status (byte7)
NonContinuouslyMonitoredSystemsStatus8
Type uint8
Comment Identifies the non-continuously monitored systems status (byte8)
Description This structure represents all data elemets of the DM05 message. The encoding shall be done
acording SAE J1939-73
Available via Dem.h
c(RS_Diag_04113)
[SWS_Dem_00950] d

AUTOSAR CP R20-11
Kind Structure
DistanceTraveledWhileMILisActivated
Elements
Type uint16
Comment The kilometers accumulated while the MIL is activated
DistanceSinceDTCsCleared
Type uint16
Comment Distance accumulated since emission related DTCs were cleared
MinutesRunbyEngineWhileMILisActivated
Type uint16
Comment Accumulated count (in minutes) while the MIL is activated (on)
TimeSinceDiagnosticTroubleCodesCleared
Type uint16
Comment Engine running time accumulated since emission related DTCs were
cleared
Available via Dem.h
c(RS_Diag_04113)
[SWS_Dem_00951] d
Kind Structure
TimeSinceEngineStart
Type uint16
Comment Time since key-on that the engine has been running.
NumberofWarmupsSinceDTCsCleared
Type uint8
Comment Number of OBD warm-up cycles since all DTCs were cleared
ContinuouslyMonitoredSystemsEnableCompletedStatus
Type uint8
Comment Identifies the continuously monitored system enable/completed
support and status.
NonContinuouslyMonitoredSystemsEnableStatus5
Type uint8
Comment Enable status of non-continuous monitors this monitoring cycle (byte5)
NonContinuouslyMonitoredSystemsEnableStatus6
Type uint8
5

AUTOSAR CP R20-11
4
Comment Enable status of non-continuous monitors this monitoring cycle (byte6)
NonContinuouslyMonitoredSystems7
Type uint8
Comment Completion status of non-continuous monitors this monitoring cycle
(byte7)
NonContinuouslyMonitoredSystems8
Type uint8
Comment Completion status of non-continuous monitors this monitoring cycle
(byte8)
Available via Dem.h
c(RS_Diag_04113)
8.3 Function definitions

This is a list of functions provided for upper layer modules.
8.3.1 Dem_GetVersionInfo
[SWS_Dem_00177] d
Service Name Dem_GetVersionInfo
Syntax void Dem_GetVersionInfo (
Std_VersionInfoType* versioninfo
)
Service ID [hex] 0x00

Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) versioninfo Pointer to where to store the version information of this module.
Return value None
Description Returns the version information of this module.
API Availability: This API will be available only if ({ecuc(Dem/DemGeneral.DemVersionInfoApi)}
== true)
Available via Dem.h
c(SRS_BSW_00402, SRS_BSW_00407)

AUTOSAR CP R20-11
8.3.2 Interface ECU State Manager <=> Dem
8.3.2.1 Dem_PreInit
[SWS_Dem_00179] d
Service Name Dem_PreInit
Syntax void Dem_PreInit (
void
)

Reentrancy Non Reentrant
Parameters (out) None
Return value None
Description Initializes the internal states necessary to process events reported by BSW-modules.
Available via Dem.h
c()
8.3.2.2 Dem_Init
[SWS_Dem_00181] d
Service Name Dem_Init
Syntax void Dem_Init (
const Dem_ConfigType* ConfigPtr
)

Parameters (in) ConfigPtr Pointer to the configuration set in VARIANT-POST-BUILD.
Return value None
Description Initializes or reinitializes this module.
Available via Dem.h
c(SRS_BSW_00101)
8.3.2.3 Dem_Shutdown
[SWS_Dem_00182] d

AUTOSAR CP R20-11
Service Name Dem_Shutdown

Syntax void Dem_Shutdown (
void
)

Return value None
Description Shuts down this module.
Available via Dem.h
c(SRS_BSW_00336)
8.3.3 Interface BSW modules / SW-Components <=> Dem
8.3.3.1 Dem_ClearDTC
[SWS_Dem_00665] d
Service Name Dem_ClearDTC
Syntax Std_ReturnType Dem_ClearDTC (
uint8 ClientId
)

Sync/Async Asynchronous
Reentrancy Reentrant for different ClientIds, non reentrant for the same ClientId.
Parameters (in) ClientId Unique client id, assigned to the instance of the calling module.
Return value Std_ReturnType E_OK: DTC successfully cleared
E_NOT_OK: No DTC selected
DEM_WRONG_DTC: Selected DTC value in selected format
does not exist or clearing is restricted by configuration to group of
all DTCs only.
DEM_WRONG_DTCORIGIN: Selected DTCOrigin does not exist
DEM_CLEAR_FAILED: DTC clearing failed
DEM_CLEAR_BUSY: Another client is currently clearing DTCs.
The requested operation will not be started and the caller shall try
again at a later moment.
DEM_CLEAR_MEMORY_ERROR: An error occurred during
erasing a memory location (e.g. if DemClearDTCBehavior is set
to DEM_CLRRESP_NON-VOLATILE_FINISH and erasing
of non-volatile-block failed).
5
5

AUTOSAR CP R20-11
4
4
DEM_PENDING: Clearing the DTCs is currently in progress. The
caller shall call this function again at a later moment.
DEM_BUSY: A different Dem_SelectDTC dependent operation
according to SWS_Dem_01253 of this client is currently in
progress.
Description Clears single DTCs, as well as groups of DTCs.
Available via Dem.h
c()
8.3.3.2 Dem_ClearPrestoredFreezeFrame
[SWS_Dem_00193] d
Service Name Dem_ClearPrestoredFreezeFrame
Syntax Std_ReturnType Dem_ClearPrestoredFreezeFrame (
Dem_EventIdType EventId
)

Reentrancy Reentrant for different EventIds. Non reentrant for the same EventId.
Parameters (in) EventId Identification of an event by assigned EventId.
Return value Std_ReturnType E_OK: Clear prestored freeze frame was successful
E_NOT_OK: Clear prestored freeze frame failed
Description Clears a prestored freeze frame of a specific event. This API can only be used through the RTE
and therefore no declaration is exported via Dem.h.
API Availability: This API will be available only if ({ecuc(Dem/DemConfigSet/DemEvent
Parameter.DemFFPrestorageSupported)} == true)
Available via Dem.h
c()
8.3.3.3 Dem_GetComponentFailed
[SWS_Dem_01115] d
Service Name Dem_GetComponentFailed
5

AUTOSAR CP R20-11
4
Syntax Std_ReturnType Dem_GetComponentFailed (
Dem_ComponentIdType ComponentId,
boolean* ComponentFailed
)
Service ID [hex] 0x2a

Parameters (in) ComponentId Identification of a DemComponent
Parameters (out) ComponentFailed TRUE: failed FALSE: not failed
Return value Std_ReturnType E_OK: getting "ComponentFailed" was successful
E_NOT_OK: getting "ComponentFailed" was not successful
Description Gets the failed status of a DemComponent.
Available via Dem.h
c()
8.3.3.4 Dem_GetDTCSelectionResult
[SWS_Dem_91023] d
Service Name Dem_GetDTCSelectionResult
Syntax Std_ReturnType Dem_GetDTCSelectionResult (
uint8 ClientId
)
Service ID [hex] 0xb8

Return value Std_ReturnType E_OK: The DTC select parameter check is successful and the
requested DTC or group of DTC in the selected origin is selected
for further operations.
does not exist
DEM_PENDING: Checking the SelectDTC parameters is
currently in progress. The caller shall call this function again later.
progress.
Description Provides information if the last call to Dem_SelectDTC has selected a valid DTC or group of
DTCs.
Available via Dem.h
c()

AUTOSAR CP R20-11
8.3.3.5 Dem_GetDTCSelectionResultForClearDTC
[SWS_Dem_91020] d
Service Name Dem_GetDTCSelectionResultForClearDTC
Syntax Std_ReturnType Dem_GetDTCSelectionResultForClearDTC (
uint8 ClientId
)
Service ID [hex] 0xbb

Return value Std_ReturnType E_OK: The DTC select parameter check is successful and the
requested DTC or group of DTC in the selected origin is selected
for further operations.
does not exist or a single DTC was selected and Dem only
supports to Clear all DTCs.
DEM_WRONG_DTCORIGIN: Selected DTCOrigin does not exist.
DEM_PENDING: Checking the SelectDTC parameters is
currently in progress. The caller shall call this function again later.
progress.
E_NOT_OK: No DTC selected.
Description Provides information if the last call to Dem_SelectDTC has selected a valid DTC or group of
DTCs, respecting the settings if the Dem shall clear only all DTCs.
Available via Dem.h
c()
8.3.3.6 Dem_GetEventUdsStatus
[SWS_Dem_91008] d
Service Name Dem_GetEventUdsStatus
Syntax Std_ReturnType Dem_GetEventUdsStatus (
Dem_EventIdType EventId,
Dem_UdsStatusByteType* UDSStatusByte
)

5

AUTOSAR CP R20-11
4
Parameters (out) UDSStatusByte UDS DTC status byte of the requested event (refer to chapter
"Status bit support"). If the return value of the function call is E_
NOT_OK, this parameter does not contain valid data.
Return value Std_ReturnType E_OK: get of event status was successful
E_NOT_OK: get of event status failed
Description Gets the current UDS status byte assigned to the DTC for the event
Available via Dem.h
c(RS_Diag_04067)
8.3.3.7 Dem_GetMonitorStatus
[SWS_Dem_91007] d
Service Name Dem_GetMonitorStatus
Syntax Std_ReturnType Dem_GetMonitorStatus (
Dem_EventIdType EventID,
Dem_MonitorStatusType* MonitorStatus
)

Parameters (in) EventID Identification of an event by assigned EventId.
Parameters (out) MonitorStatus Monitor status byte of the requested event. If the return value of
the function call is E_NOT_OK, this parameter does not contain
valid data.
Return value Std_ReturnType E_OK: Get monitor status was successful,
E_NOT_OK: getting the monitor status failed (e.g. an invalid
event id was provided).
Description Gets the current monitor status for an event.
Available via Dem.h
c()
8.3.3.8 Dem_GetDebouncingOfEvent
[SWS_Dem_00730] d
Service Name Dem_GetDebouncingOfEvent
5

AUTOSAR CP R20-11
4
Syntax Std_ReturnType Dem_GetDebouncingOfEvent (
Dem_DebouncingStateType* DebouncingState
)
Service ID [hex] 0x9f

Parameters (out) DebouncingState Bit 0 Temporarily Defective (corresponds to 0 < FDC < 127) Bit 1
finally Defective (corresponds to FDC = 127) Bit 2 temporarily
healed (corresponds to -128 < FDC < 0) Bit 3 Test complete
(corresponds to FDC = -128 or FDC = 127) Bit 4 DTR Update (=
Test complete && Debouncing complete && enable conditions /
storage conditions fulfilled)
Return value Std_ReturnType E_OK: get of debouncing status per event state successful
E_NOT_OK: get of debouncing per event state failed
Description Gets the debouncing status of an event. This function shall not be used for EventId with native
debouncing within their functions. It is rather for EventIds using debouncing within the Dem.
Available via Dem.h
c(RS_Diag_04068)
8.3.3.9 Dem_GetDTCOfEvent
[SWS_Dem_00198] d
Service Name Dem_GetDTCOfEvent
Syntax Std_ReturnType Dem_GetDTCOfEvent (
Dem_DTCFormatType DTCFormat,
uint32* DTCOfEvent
)
Service ID [hex] 0x0d

DTCFormat Defines the output-format of the requested DTC value.
Parameters (out) DTCOfEvent Receives the DTC value in respective format returned by this
function. If the return value of the function is other than E_OK this
parameter does not contain valid data.
Return value Std_ReturnType E_OK: get of DTC was successful
E_NOT_OK: the call was not successful
DEM_E_NO_DTC_AVAILABLE: there is no DTC configured in
the requested format
Description Gets the DTC of an event.
5

AUTOSAR CP R20-11
4
Available via Dem.h
c(RS_Diag_04201)
8.3.3.10 Dem_GetDTCSuppression
[SWS_Dem_91025] d
Service Name Dem_GetDTCSuppression
Syntax Std_ReturnType Dem_GetDTCSuppression (
uint8 ClientId,
boolean* SuppressionStatus
)
Service ID [hex] 0xbc

Parameters (in) ClientId Unique client id, assigned to the instance of the calling module
Parameters (out) SuppressionStatus Defines whether the respective DTC is suppressed (TRUE) or
enabled (FALSE).
Return value Std_ReturnType E_OK: Operation was successful.
E_NOT_OK: Dem_SelectDTC was not called.
DEM_WRONG_DTC: No valid DTC or DTC group selected.
DEM_WRONG_DTCORIGIN: Wrong DTC origin selected.
DEM_PENDING: The requested value is calculated
asynchronously and currently not available. The caller can retry
later.
Description Returns the suppression status of a specific DTC. API Availability: This API will be available
only if ({ecuc(Dem/DemGeneral.DemSuppressionSupport)} == DEM_DTC_SUPPRESSION)
Available via Dem.h
c()
8.3.3.11 Dem_GetEventAvailable
[SWS_Dem_91040] d
Service Name Dem_GetEventAvailable
Syntax Std_ReturnType Dem_GetEventAvailable (
boolean* AvailableStatus
)
Service ID [hex] 0xbe

5

AUTOSAR CP R20-11
4
Parameters (out) AvailableStatus TRUE if the event is available. FALSE if the event is not available.
Return value Std_ReturnType E_OK : Event availability has been obtained.
E_NOT_OK : Event availability cannot be obtained.
Description Get the Event’s availability.
Available via Dem.h
c()
8.3.3.12 Dem_GetFaultDetectionCounter
[SWS_Dem_00203] d
Service Name Dem_GetFaultDetectionCounter
Syntax Std_ReturnType Dem_GetFaultDetectionCounter (
sint8* FaultDetectionCounter
)
Service ID [hex] 0x3e

Parameters (out) FaultDetectionCounter This parameter receives the Fault Detection Counter information
of the requested EventId. If the return value of the function call is
other than E_OK this parameter does not contain valid data.
-128dec...127dec PASSED...FAILED according to ISO 14229-1
Return value Std_ReturnType E_OK: request was successful
E_NOT_OK: request failed
DEM_E_NO_FDC_AVAILABLE: there is no fault detection
counter available for the requested event
Description Gets the fault detection counter of an event. This API can only be used through the RTE, and
therefore no declaration is exported via Dem.h.
Available via Dem.h
c()
8.3.3.13 Dem_GetIndicatorStatus
[SWS_Dem_00205] d

AUTOSAR CP R20-11
Service Name Dem_GetIndicatorStatus

Syntax Std_ReturnType Dem_GetIndicatorStatus (
uint8 IndicatorId,
Dem_IndicatorStatusType* IndicatorStatus
)

Parameters (in) IndicatorId Number of indicator
Parameters (out) IndicatorStatus Status of the indicator, like off, on, or blinking.
Return value Std_ReturnType E_OK: Operation was successful
E_NOT_OK: Operation failed
Description Gets the indicator status derived from the UDS status.
API Availability: This API will be available only if ({ecuc(Dem/DemGeneral/DemEventMemory
Set/DemIndicator)} != NULL)
Available via Dem.h
c()
8.3.3.14 Dem_GetEventFreezeFrameDataEx
[SWS_Dem_01191] d
Service Name Dem_GetEventFreezeFrameDataEx
Syntax Std_ReturnType Dem_GetEventFreezeFrameDataEx (
uint8 RecordNumber,
uint16 DataId,
uint8* DestBuffer,
uint16* BufSize
)

RecordNumber This parameter is a unique identifier for a freeze frame record as
defined in ISO14229-1. 0xFF means most recent freeze frame
record is returned. 0x00 is only supported if the Dem module
supports WWH-OBD (refer to DemOBDSupport)
DataId This parameter specifies the DID (ISO14229-1) that shall be
copied to the destination buffer.
Parameters (inout) BufSize When the function is called this parameter contains the maximum
number of data bytes that can be written to the buffer. The
function returns the actual number of written data bytes in this
parameter.
5

AUTOSAR CP R20-11
4
Parameters (out) DestBuffer This parameter contains a byte pointer that points to the buffer, to
which the freeze frame data record shall be written to. The format
is raw hexadecimal values and contains no header-information.
E_NOT_OK: Operation could not be performed
DEM_NO_SUCH_ELEMENT: The requested event data is not
currently stored (but the request was valid) OR The requested
record number is not supported by the event OR The requested
DID is not supported by the freeze frame.
DEM_BUFFER_TOO_SMALL: The provided buffer size is too
small.
Description Gets the data of a freeze frame by event.
Available via Dem.h
c()
8.3.3.15 Dem_GetEventExtendedDataRecordEx
[SWS_Dem_01190] d
Service Name Dem_GetEventExtendedDataRecordEx
Syntax Std_ReturnType Dem_GetEventExtendedDataRecordEx (
uint8 RecordNumber,
uint8* DestBuffer,
uint16* BufSize
)

RecordNumber Identification of requested Extended data record. Valid values are
between 0x01 and 0xEF as defined in ISO14229-1.
parameter.
which the extended data shall be written to. The format is raw
hexadecimal values and contains no header-information.
E_NOT_OK: Operation could not be performed
DEM_NO_SUCH_ELEMENT: The requested event data is not
currently stored (but the request was valid) OR the requested
record number is not supported by the event.
DEM_BUFFER_TOO_SMALL: The provided buffer size is too
small.
Description Gets the data of an extended data record by event.
Available via Dem.h
c(RS_Diag_04205)

AUTOSAR CP R20-11
8.3.3.16 Dem_GetEventMemoryOverflow
[SWS_Dem_00559] d
Service Name Dem_GetEventMemoryOverflow
Syntax Std_ReturnType Dem_GetEventMemoryOverflow (
uint8 ClientId,
Dem_DTCOriginType DTCOrigin,
boolean* OverflowIndication
)

Reentrancy Re-entrant for different ClientIDs, Non re-entrant for same ClientId.
Parameters (in) ClientId DemClientID identifying the DemEventMemorySet indicating in
which event memory the overflow has occurred.
DTCOrigin If the Dem supports more than one event memory this parameter
is used to select the source memory the overflow indication shall
be read from.
Parameters (out) OverflowIndication This parameter returns TRUE if the according event memory was
overflowed, otherwise it returns FALSE.
E_NOT_OK: Operation failed or is not supported
Description Gets the event memory overflow indication status.
Available via Dem.h
c(RS_Diag_04093)
8.3.3.17 Dem_GetNumberOfEventMemoryEntries
[SWS_Dem_00652] d
Service Name Dem_GetNumberOfEventMemoryEntries
Syntax Std_ReturnType Dem_GetNumberOfEventMemoryEntries (
uint8 ClientId,
uint8* NumberOfEventMemoryEntries
)

Parameters (in) ClientId DemClientID identifying the DemEventMemorySet to which the
requested event memory belongs to.
is used to select the source memory the number of entries shall
be read from.
5

AUTOSAR CP R20-11
4
Parameters (out) NumberOfEventMemory Number of entries currently stored in the requested event
Entries memory.
Description Returns the number of entries currently stored in the requested event memory.
Available via Dem.h
c(RS_Diag_04109)
8.3.3.18 Dem_ResetEventDebounceStatus
[SWS_Dem_00683] d
Service Name Dem_ResetEventDebounceStatus
Syntax Std_ReturnType Dem_ResetEventDebounceStatus (
Dem_DebounceResetStatusType DebounceResetStatus
)

DebounceResetStatus Freeze or reset the internal debounce counter/timer of the
specified event.
E_NOT_OK: Only on development error
Description Control the internal debounce counter/timer by BSW modules and SW-Cs. The event
qualification will not be affected by these debounce state changes. This API is available for
BSW modules as soon as Dem_PreInit has been completed (refer to SWS_Dem_00438 and
SWS_Dem_00167).
Available via Dem.h
c(RS_Diag_04105)
8.3.3.19 Dem_ResetEventStatus
[SWS_Dem_00185] d

AUTOSAR CP R20-11
Service Name Dem_ResetEventStatus

Syntax Std_ReturnType Dem_ResetEventStatus (
)

Return value Std_ReturnType E_OK: Request to reset the event status was successful
accepted.
E_NOT_OK: Request to reset the event status failed or is not
allowed, because the event is already tested in this operation
cycle.
Description Resets the event failed status. This API can only be used through the RTE and therefore no
declaration is exported via Dem.h.
Available via Dem.h
c()
8.3.3.20 Dem_RestartOperationCycle
[SWS_Dem_00194] d
Service Name Dem_RestartOperationCycle
Syntax Std_ReturnType Dem_RestartOperationCycle (
uint8 OperationCycleId
)

Parameters (in) OperationCycleId Identification of operation cycle, like power cycle, driving cycle.
Return value Std_ReturnType E_OK: set of operation cycle was accepted and will be handled
asynchronously
E_NOT_OK: set of operation cycle was rejected
Description Sets an operation cycle state. This API can only be used through the RTE and therefore no
declaration is exported via Dem.h. The interface has an asynchronous behavior to avoid
exceeding of typical timing requirements on APIs if a large number of events has to be
processed and during the re-initializations of the related monitors. The asynchronous
acknowledgements are the related InitMonitorForEvent callbacks.
Available via Dem.h
c()

AUTOSAR CP R20-11
8.3.3.21 Dem_PrestoreFreezeFrame
[SWS_Dem_00188] d
Service Name Dem_PrestoreFreezeFrame
Syntax Std_ReturnType Dem_PrestoreFreezeFrame (
)

Return value Std_ReturnType E_OK Freeze frame prestorage was successful
E_NOT_OK Freeze frame prestorage failed
Description Captures the freeze frame data for a specific event. This API can only be used through the RTE
and therefore no declaration is exported via Dem.h.
API Availability: This API will be available only if ({ecuc(Dem/DemConfigSet/DemEvent
Parameter.DemFFPrestorageSupported)} == true)
Available via Dem.h
c()
8.3.3.22 Dem_SelectDTC
[SWS_Dem_91016] d
Service Name Dem_SelectDTC
Syntax Std_ReturnType Dem_SelectDTC (
uint8 ClientId,
uint32 DTC,
Dem_DTCOriginType DTCOrigin
)

DTC Defines the DTC in respective format that is selected. If the DTC
fits to a DTC group number, the DTC group is selected.
DTCFormat Defines the input-format of the provided DTC value.
DTCOrigin The event memory of the requested DTC or group of DTC.
5

AUTOSAR CP R20-11
4
Return value Std_ReturnType E_OK: DTC successfully selected.
DEM_BUSY: Another Dem_SelectDTC or Dem_SelectDTC
dependent operation of this client is currently in progress.
Description Selects a DTC or DTC group as target for further operations.
Available via Dem.h
c()
8.3.3.23 Dem_SetComponentAvailable
[SWS_Dem_01117] d
Service Name Dem_SetComponentAvailable
Syntax Std_ReturnType Dem_SetComponentAvailable (
Dem_ComponentIdType ComponentId,
boolean AvailableStatus
)
Service ID [hex] 0x2b

Parameters (in) ComponentId Identification of a DemComponent.
AvailableStatus This parameter specifies whether the respective Component shall
be available (TRUE) or not (FALSE).
Description Set the availability of a specific DemComponent.
Available via Dem.h
c()
8.3.3.24 Dem_SetDTCSuppression
[SWS_Dem_01047] d
Service Name Dem_SetDTCSuppression
Syntax Std_ReturnType Dem_SetDTCSuppression (
uint8 ClientId,
boolean SuppressionStatus
)

5

AUTOSAR CP R20-11
4
SuppressionStatus This parameter specifies whether the respective DTC shall be
disabled (TRUE) or enabled (FALSE).
Return value Std_ReturnType E_OK: The status of the DTC is correctly provided in the
DTCStatus parameter.
does not exist.
later.
DEM_BUSY: DEM_BUSY: A different Dem_SelectDTC
dependent operation according to SWS_Dem_01253 of this client
is currently in progress.
Description Set the suppression status of a specific DTC.
API Availability: This API will be available only if ({ecuc(Dem/DemGeneral.DemSuppression
Support)} == DEM_DTC_SUPPRESSION)
Available via Dem.h
c()
8.3.3.25 Dem_SetEnableCondition
[SWS_Dem_00201] d
Service Name Dem_SetEnableCondition
Syntax Std_ReturnType Dem_SetEnableCondition (
uint8 EnableConditionID,
boolean ConditionFulfilled
)

Parameters (in) EnableConditionID This parameter identifies the enable condition.
ConditionFulfilled This parameter specifies whether the enable condition assigned
to the EnableConditionID is fulfilled (TRUE) or not fulfilled
(FALSE).
Return value Std_ReturnType In case the enable condition could be set successfully the API
call returns E_OK. If the setting of the enable condition failed the
return value of the function is E_NOT_OK.
5

AUTOSAR CP R20-11
4
Description Sets an enable condition.
API Availability: This API will be available only if ({ecuc(Dem/DemGeneral/DemEnable
Condition)} != NULL)
Available via Dem.h
c(RS_Diag_04192)
8.3.3.26 Dem_SetEventAvailable
[SWS_Dem_01080] d
Service Name Dem_SetEventAvailable
Syntax Std_ReturnType Dem_SetEventAvailable (
boolean AvailableStatus
)

AvailableStatus This parameter specifies whether the respective Event shall be
available (TRUE) or not (FALSE).
Return value Std_ReturnType E_OK: Request to set the availability status was successful.
E_NOT_OK: Request to set the availability status not accepted.
Description Set the available status of a specific Event.
Available via Dem.h
c(RS_Diag_04126)
8.3.3.27 Dem_SetEventConfirmationThresholdCounter
[SWS_Dem_91004] d
Service Name Dem_SetEventConfirmationThresholdCounter
Syntax Std_ReturnType Dem_SetEventConfirmationThresholdCounter (
uint8 FailureCycleCounterThreshold
)

5

AUTOSAR CP R20-11
4
FailureCycleCounter Failure cycle counter threshold of event to be set.
Threshold
Return value Std_ReturnType E_OK: Change of threshold was successful.
E_NOT_OK: Threshold cannot be changed as DemEvent
ConfirmationThresholdCounterAdaptable is set to FALSE for this
event.
Description Set the failure confirmation threshold of an event.
Available via Dem.h
c()
8.3.3.28 Dem_SetEventStatus
[SWS_Dem_00183] d
Service Name Dem_SetEventStatus
Syntax Std_ReturnType Dem_SetEventStatus (
Dem_EventStatusType EventStatus
)

Sync/Async Synchronous/Asynchronous
EventStatus Monitor test result
Return value Std_ReturnType E_OK: set of event status was successful
E_NOT_OK: Event status setting or processing failed or could not
be accepted.
Description Called by SW-Cs or BSW modules to report monitor status information to the Dem. BSW
modules calling Dem_SetEventStatus can safely ignore the return value. This API will be
available only if ({Dem/DemConfigSet/DemEventParameter/DemEventReportingType} ==
STANDARD_REPORTING)
Available via Dem.h
c()
8.3.3.29 Dem_SetEventStatusWithMonitorData
[SWS_Dem_91037] d

AUTOSAR CP R20-11
Service Name Dem_SetEventStatusWithMonitorData

Syntax Std_ReturnType Dem_SetEventStatusWithMonitorData (
Dem_EventStatusType EventStatus,
Dem_MonitorDataType monitorData0,
Dem_MonitorDataType monitorData1
)
Service ID [hex] 0xbd

Sync/Async Synchronous/Asynchronous
EventStatus Monitor test result
monitorData0 –
monitorData1 –
Return value Std_ReturnType E_OK: set of event status was successful
E_NOT_OK: Event status setting or processing failed or could not
be accepted.
Description This API will be available only if ({Dem/DemConfigSet/DemEventParameter/DemEvent
ReportingType} == STANDARD_REPORTING_WITH_MONITOR_DATA)
Available via Dem.h
c()
8.3.3.30 Dem_SetStorageCondition
[SWS_Dem_00556] d
Service Name Dem_SetStorageCondition
Syntax Std_ReturnType Dem_SetStorageCondition (
uint8 StorageConditionID,
boolean ConditionFulfilled
)

Parameters (in) StorageConditionID This parameter identifies the storage condition.
ConditionFulfilled This parameter specifies whether the storage condition assigned
to the StorageConditionID is fulfilled (TRUE) or not fulfilled
(FALSE).
Return value Std_ReturnType In case the storage condition could be set successfully the API
call returns E_OK. If the setting of the storage condition failed the
return value of the function is E_NOT_OK.
5

AUTOSAR CP R20-11
4
Description Sets a storage condition.
API Availability: This API will be available only if ({ecuc(Dem/DemGeneral/DemStorage
Condition)} != NULL)
Available via Dem.h
c(RS_Diag_04219)
8.3.3.31 Dem_SetWIRStatus
[SWS_Dem_00839] d
Service Name Dem_SetWIRStatus
Syntax Std_ReturnType Dem_SetWIRStatus (
boolean WIRStatus
)

Parameters (in) EventId Identification of an event by assigned EventId. The Event Number
is configured in the DEM. Min.: 1 (0: Indication of no Event or
Failure) Max.:Result of configuration of Event Numbers in DEM
(Max is either 255 or 65535)
WIRStatus Requested status of event related WIR-bit (regarding to the
current status of function inhibition) WIRStatus = TRUE ->
WIR-bit shall be set to "1" WIRStatus = FALSE -> WIR-bit shall
be set to "0"
Return value Std_ReturnType E_OK: Request to set the WIR status was successful.
E_NOT_OK: Request to set the WIR status was not accepted
(e.g. disabled controlDTCSetting) and should be repeated.
Description Sets the WIR status bit via failsafe SW-Cs. This API can only be used through the RTE and
therefore no declaration is exported via Dem.h.
Available via Dem.h
c()
8.3.3.32 Dem_SetEventFailedWithSyncFreezeFrame
[SWS_Dem_91041]{DRAFT} d

AUTOSAR CP R20-11
Service Name Dem_SetEventFailedWithSyncFreezeFrame (draft)

Syntax void Dem_SetEventFailedWithSyncFreezeFrame (
)
Service ID [hex] 0xbf

Return value None
Description If called the Dem sets the event to failed and this failed event requires that a snapshot record is
captured, the Dem synchronously retrieves the data within the call of this API.
Tags:atp.Status=draft
Available via Dem.h
c()
8.3.4 Interface Dcm <=> Dem
8.3.4.1.1 Dem_GetTranslationType
[SWS_Dem_00230] d
Service Name Dem_GetTranslationType
Syntax Dem_DTCTranslationFormatType Dem_GetTranslationType (
uint8 ClientId
)
Service ID [hex] 0x3c

Return value Dem_DTCTranslation Returns the configured DTC translation format. A combination of
FormatType different DTC formats is not possible.
Description Gets the supported DTC formats of the ECU.The supported formats are configured via Dem
TypeOfDTCSupported.
Available via Dem.h
c()

AUTOSAR CP R20-11
8.3.4.1.2 Dem_GetDTCStatusAvailabilityMask
[SWS_Dem_00213] d
Service Name Dem_GetDTCStatusAvailabilityMask
Syntax Std_ReturnType Dem_GetDTCStatusAvailabilityMask (
uint8 ClientId,
Dem_UdsStatusByteType* DTCStatusMask,
)

Reentrancy Non Reentrant Re-entrant for different ClientIDs, Non re-entrant for same ClientId.
DTCOrigin This parameter selects the event memory the DTCStatus
AvailabilityMask is requested for. Only the values DEM_DTC_
ORIGIN_PRIMARY_ MEMORY and DEM_DTC_ORIGIN_
USERDEFINED_MEMORY_<Name> are valid.
Parameters (out) DTCStatusMask DTCStatusMask The value DTCStatusMask indicates the
supported DTC status bits from the Dem. All supported
information is indicated by setting the corresponding status bit to
1. See ISO14229-1.
Return value Std_ReturnType E_OK: get of DTC status mask was successful
E_NOT_OK: get of DTC status mask failed
Description Gets the DTC Status availability mask of the selected fault memory.
Available via Dem.h
c(RS_Diag_04067)
8.3.4.1.3 Dem_GetStatusOfDTC
[SWS_Dem_00212] d
Service Name Dem_GetStatusOfDTC
Syntax Std_ReturnType Dem_GetStatusOfDTC (
uint8 ClientId,
uint8* DTCStatus
)

Parameters (out) DTCStatus This parameter receives the status information of the requested
DTC. It follows the format as defined in ISO14229-1 If the return
value of the function call is other than DEM_FILTERED_OK this
5

AUTOSAR CP R20-11
4
Return value Std_ReturnType E_OK: The status of the DTC is correctly provided in the
DTCStatus parameter.
does not exist
DEM_PENDING: Retrieving the DTC status is currently in
progress. The caller shall call this function again at a later
moment.
DEM_NO_SUCH_ELEMENT - Selected DTC does not have an
assigned DTC status.
progress.
Description Gets the status of a DTC. For large configurations and DTC-calibration, the interface behavior
can be asynchronous (splitting the DTC-search into segments). The DTCs of OBD Events
Suppression shall be reported as Dem_WRONG_DTC.
Available via Dem.h
c(RS_Diag_04067)
8.3.4.1.4 Dem_GetSeverityOfDTC
[SWS_Dem_00232] d
Service Name Dem_GetSeverityOfDTC
Syntax Std_ReturnType Dem_GetSeverityOfDTC (
Dem_DTCSeverityType* DTCSeverity,
uint8 ClientId
)

Parameters (out) DTCSeverity This parameter contains the DTCSeverity according to ISO
14229-1.
Return value Std_ReturnType E_OK: The DTC severity is correctly provided in the DTCSeverity
parameter.
does not exist
DEM_PENDING: Retrieving the DTC is currently in progress. The
progress.
Description Gets the severity of the requested DTC. For large configurations and DTC-calibration, the
interface behavior can be asynchronous (splitting the DTC-search into segments).
Available via Dem.h
c(RS_Diag_04071)

AUTOSAR CP R20-11
8.3.4.1.5 Dem_GetFunctionalUnitOfDTC
[SWS_Dem_00594] d
Service Name Dem_GetFunctionalUnitOfDTC
Syntax Std_ReturnType Dem_GetFunctionalUnitOfDTC (
uint8 ClientId,
uint8* DTCFunctionalUnit
)

Parameters (out) DTCFunctionalUnit Functional unit value of this DTC
Return value Std_ReturnType E_OK: The DTC functional unit is provided in the parameter
DTCFunctionalUnit.
does not exist
DEM_PENDING: Retrieving the DTC functional unit is currently in
moment.
progress.
Description Gets the functional unit of the requested DTC.
Available via Dem.h
c(RS_Diag_04156)
8.3.4.1.6 Dem_SetDTCFilter
[SWS_Dem_00208] d
Service Name Dem_SetDTCFilter
Syntax Std_ReturnType Dem_SetDTCFilter (
uint8 ClientId,
uint8 DTCStatusMask,
boolean FilterWithSeverity,
Dem_DTCSeverityType DTCSeverityMask,
boolean FilterForFaultDetectionCounter
)

5

AUTOSAR CP R20-11
4
DTCStatusMask Status-byte mask for DTC status-byte filtering
Values: 0x00: Autosar-specific value to deactivate the status-byte
filtering (different meaning than in ISO 14229-1) to report all
supported DTCs (used for service 0x19 subfunctions 0x0A/0x15)
0x01..0xFF: Status-byte mask according to ISO 14229-1
DTCStatusMask (handed over by Dcm from service request
directly) to filter for DTCs with at least one status bit set matching
this status-byte mask
DTCFormat Defines the output-format of the requested DTC values for the
sub-sequent API calls. If passed value does not fit to
Configuration, the DET error DEM_E_WRONG_
CONFIGURATION shall be reported, e.g. if DTCFormat "DEM_
DTC_FORMAT_OBD" is passed, but OBD is not supported per
configuration.
is used to select the source memory the DTCs shall be read from.
If passed value does not fit to Configuration, the DET error DEM_
E_WRONG_CONFIGURATION shall be reported, e.g. if
DTCOrigin "DEM_DTC_ORIGIN_MIRROR_MEMORY" is
passed, but no mirror memory is configured.
FilterWithSeverity This flag defines whether severity information (ref. to parameter
below) shall be used for filtering. This is to allow for coexistence
of DTCs with and without severity information.
DTCSeverityMask Contains the DTCSeverityMask according to ISO14229-1.
FilterForFaultDetection This flag defines whether the fault detection counter information
Counter shall be used for filtering. This is to allow for coexistence of DTCs
with and without fault detection counter information. If fault
detection counter information is filter criteria, only those DTCs
with a fault detection counter value between 1 and 0x7E shall be
reported. Remark: If the event does not use the debouncing
inside Dem, then the Dem must request this information via Get
FaultDetectionCounter.
Return value Std_ReturnType E_NOT_OK: Indicates a wrong DTCOrigin or DTCFormat
Description Sets the DTC Filter.
The server shall perform a bit-wise logical AND-ing operation between the parameter
DTCStatusMask and the current UDS status in the server. In addition to the DTCStatus
AvailabilityMask, the server shall return all DTCs for which the result of the AND-ing operation
is non-zero [i.e. (statusOfDTC & DTCStatusMask) != 0]. The server shall process only the DTC
Status bits that it is supporting. OBD Events Suppression shall be ignored for this computation.
If no DTCs within the server match the masking criteria specified in the clients request, no DTC
or status information shall be provided following the DTCStatusAvailabilityMask byte in the
positive response message
(((statusOfDTC & DTCStatusMask) != 0) && ((severity & DTCSeverityMask) != 0)) == TRUE
Available via Dem.h
c(RS_Diag_04205)
8.3.4.1.7 Dem_GetNumberOfFilteredDTC
[SWS_Dem_00214] d

AUTOSAR CP R20-11
Service Name Dem_GetNumberOfFilteredDTC

Syntax Std_ReturnType Dem_GetNumberOfFilteredDTC (
uint8 ClientId,
uint16* NumberOfFilteredDTC
)

Parameters (out) NumberOfFilteredDTC The number of DTCs matching the defined status mask.
Return value Std_ReturnType E_OK: Getting number of filtered DTCs was successful
E_NOT_OK: No DTC filter set
DEM_PENDING: The requested operation is currently in
moment.
Description Gets the number of a filtered DTC.
Available via Dem.h
c()
8.3.4.1.8 Dem_GetNextFilteredDTC
[SWS_Dem_00215] d
Service Name Dem_GetNextFilteredDTC
Syntax Std_ReturnType Dem_GetNextFilteredDTC (
uint8 ClientId,
uint32* DTC,
uint8* DTCStatus
)

Sync/Async Synchronous or Asynchronous
Parameters (out) DTC Receives the DTC value in respective format of the filter returned
by this function. If the return value of the function is other than
DEM_FILTERED_OK this parameter does not contain valid data.
DTCStatus This parameter receives the status information of the requested
5

AUTOSAR CP R20-11
4
Return value Std_ReturnType E_OK: Returned next filtered element
DEM_NO_SUCH_ELEMENT: No further element matching the
filter criteria found
moment. Note that according to SWS_Dem_00653 this return
value is not always allowed.
Description Gets the next filtered DTC matching the filter criteria. For UDS services, the interface has an
asynchronous behavior, because a large number of DTCs has to be processed.
Available via Dem.h
c()
8.3.4.1.9 Dem_GetNextFilteredDTCAndFDC
[SWS_Dem_00227] d
Service Name Dem_GetNextFilteredDTCAndFDC
Syntax Std_ReturnType Dem_GetNextFilteredDTCAndFDC (
uint8 ClientId,
uint32* DTC,
sint8* DTCFaultDetectionCounter
)

DTCFaultDetection This parameter receives the Fault Detection Counter information
Counter of the requested DTC. If the return value of the function call is
other than DEM_FILTERED_OK this parameter does not contain
valid data.
DEM_PENDING: The requested operation is asynchronously
processed is currently in progress. The caller shall call this
function again at a later moment.
Description Gets the next filtered DTC and its associated Fault Detection Counter (FDC) matching the filter
criteria. The interface has an asynchronous behavior, because a large number of DTCs has to
be processed and the FDC might be received asynchronously from a SW-C, too.
Available via Dem.h
c()

AUTOSAR CP R20-11
8.3.4.1.10 Dem_GetNextFilteredDTCAndSeverity
[SWS_Dem_00281] d
Service Name Dem_GetNextFilteredDTCAndSeverity
Syntax Std_ReturnType Dem_GetNextFilteredDTCAndSeverity (
uint8 ClientId,
uint32* DTC,
uint8* DTCStatus,
Dem_DTCSeverityType* DTCSeverity,
uint8* DTCFunctionalUnit
)

DTCStatus This parameter receives the status information of the requested
DTCSeverity Receives the severity value returned by the function. If the return
value of the function is other than DEM_FILTERED_OK this
DTCFunctionalUnit Receives the functional unit value returned by the function. If the
return value of the function is other than DEM_FILTERED_OK
this parameter does not contain valid data.
moment.
Description Gets the next filtered DTC and its associated Severity matching the filter criteria. The interface
has an asynchronous behavior, because a large number of DTCs has to be processed.
Available via Dem.h
c()
8.3.4.1.11 Dem_SetFreezeFrameRecordFilter
[SWS_Dem_00209] d

AUTOSAR CP R20-11
Service Name Dem_SetFreezeFrameRecordFilter

Syntax Std_ReturnType Dem_SetFreezeFrameRecordFilter (
uint8 ClientId,
Dem_DTCFormatType DTCFormat
)

DTCFormat Defines the output-format of the requested DTC values
Return value Std_ReturnType Status of the operation to (re-)set a freeze frame record filter.
E_OK: Filter is accepted
E_NOT_OK: Wrong filter selected
Description Sets a freeze frame record filter.
Available via Dem.h
c()
8.3.4.1.12 Dem_GetNextFilteredRecord
[SWS_Dem_00224] d
Service Name Dem_GetNextFilteredRecord
Syntax Std_ReturnType Dem_GetNextFilteredRecord (
uint8 ClientId,
uint32* DTC,
uint8* RecordNumber
)

Parameters (out) DTC DTC Receives the DTC value in respective format of the filter
returned by this function. If the return value of the function is
RecordNumber Freeze frame record number of the reported DTC (relative
addressing). If the return value of the function is other than E_OK
5

AUTOSAR CP R20-11
4
Return value Std_ReturnType Status of the operation to retrieve a DTC and its associated
snapshot record number from the Dem.
E_OK: Returned next filtered element
DEM_NO_SUCH_ELEMENT: No further element (matching the
filter criteria) found
later. Only used by asynchronous interfaces.
Description Gets the next freeze frame record number and its associated DTC stored in the event memory.
The interface has an asynchronous behavior, because NvRAM access might be required.
Available via Dem.h
c()
8.3.4.1.13 Dem_GetDTCByOccurrenceTime
[SWS_Dem_00218] d
Service Name Dem_GetDTCByOccurrenceTime
Syntax Std_ReturnType Dem_GetDTCByOccurrenceTime (
uint8 ClientId,
Dem_DTCRequestType DTCRequest,
uint32* DTC
)

DTCRequest This parameter defines the request type of the DTC.
Parameters (out) DTC Receives the DTC value in UDS format returned by the function.
If the return value of the function is other than DEM_OCCURR_
OK this parameter does not contain valid data.
Return value Std_ReturnType E_OK: get of DTC was successful
E_NOT_OK: the call was not successful
DEM_NO_SUCH_ELEMENT: The requested element is not
stored
Description Gets the DTC by occurrence time. There is no explicit parameter for the DTC-origin as the
origin always is DEM_DTC_ORIGIN_PRIMARY_MEMORY.
Available via Dem.h
c()
8.3.4.2 Access extended data records and FreezeFrame data
8.3.4.2.1 Dem_DisableDTCRecordUpdate
[SWS_Dem_00233] d

AUTOSAR CP R20-11
Service Name Dem_DisableDTCRecordUpdate

Syntax Std_ReturnType Dem_DisableDTCRecordUpdate (
uint8 ClientId
)

Return value Std_ReturnType E_OK: Event memory update successfully disabled
does not exist or a group of DTC was selected
DEM_PENDING: Disabling the DTC record update is currently in
moment.
progress.
Description Disables the event memory update of a specific DTC (only one at one time).
Available via Dem.h
c(RS_Diag_04192)
8.3.4.2.2 Dem_EnableDTCRecordUpdate
[SWS_Dem_00234] d
Service Name Dem_EnableDTCRecordUpdate
Syntax Std_ReturnType Dem_EnableDTCRecordUpdate (
uint8 ClientId
)

Return value Std_ReturnType E_OK: DTC record successfully updated.
Description Enables the event memory update of the DTC disabled by Dem_DisableDTCRecordUpdate()
before.
Note: As the call to Dem_EnableDTCRecordUpdate is the last action in the sequence of
disabling/enabling a DTC, the caller is not interested in the return value. Therefore E_OK
should be returned even if the DTC is enabled asynchronously.
5

AUTOSAR CP R20-11
4
Available via Dem.h
c()
8.3.4.2.3 Dem_GetSizeOfExtendedDataRecordSelection
[SWS_Dem_00240] d
Service Name Dem_GetSizeOfExtendedDataRecordSelection
Syntax Std_ReturnType Dem_GetSizeOfExtendedDataRecordSelection (
uint8 ClientId,
uint32* SizeOfExtendedDataRecord
)

Parameters (out) SizeOfExtendedData Size of the requested extended data record(s) including record
Record number. The format for a single ExtendedDataRecord is: {Record
Number, data[1], ..., data[N]}
Return value Std_ReturnType E_OK: Size returned successfully
E_NOT_OK : selection function is not called.
later.
DEM_WRONG_DTC: DTC value not existing
DEM_WRONG_DTCORIGIN: Wrong DTC origin
DEM_NO_SUCH_ELEMENT: Record number is not supported
by configuration and therefore invalid
Description Gets the size of Extended Data Record by DTC selected by the call of Dem_SelectExtended
DataRecord.
Available via Dem.h
c()
8.3.4.2.4 Dem_GetSizeOfFreezeFrameSelection
[SWS_Dem_00238] d
Service Name Dem_GetSizeOfFreezeFrameSelection
Syntax Std_ReturnType Dem_GetSizeOfFreezeFrameSelection (
uint8 ClientId,
uint32* SizeOfFreezeFrame
)
5

AUTOSAR CP R20-11
4
Parameters (out) SizeOfFreezeFrame Number of bytes in the requested freeze frame record.
Return value Std_ReturnType E_OK: Size returned successfully
later.
DEM_NO_SUCH_ELEMENT: Record number is not supported
by configuration and therefore invalid
Description Gets the size of freeze frame data by DTC selected by the call of Dem_SelectFreezeFrame
Data.
Available via Dem.h
c()
8.3.4.2.5 Dem_GetNextExtendedDataRecord
[SWS_Dem_00239] d
Service Name Dem_GetNextExtendedDataRecord
Syntax Std_ReturnType Dem_GetNextExtendedDataRecord (
uint8 ClientId,
uint8* DestBuffer,
uint16* BufSize
)

parameter.
which the extended data record shall be written to. The format is:
{ExtendedDataRecordNumber, data[0], data[1], ..., data[n]}
Return value Std_ReturnType E_OK: Size and buffer successfully returned.
DEM_BUFFER_TOO_SMALL: provided buffer size too small.
5
5

AUTOSAR CP R20-11
4
4
later.
DEM_NO_SUCH_ELEMENT: Found no (further) element
matching the filter criteria
Description Gets extended data record for the DTC selected by Dem_SelectExtendedDataRecord. The
function stores the data in the provided DestBuffer.
Available via Dem.h
c()
8.3.4.2.6 Dem_GetNextFreezeFrameData
[SWS_Dem_00236] d
Service Name Dem_GetNextFreezeFrameData
Syntax Std_ReturnType Dem_GetNextFreezeFrameData (
uint8 ClientId,
uint8* DestBuffer,
uint16* BufSize
)

parameter.
which the freeze frame data record shall be written to. The format
is: {RecordNumber, NumOfDIDs, DID[1], data[1], ..., DID[N],
data[N]}
Return value Std_ReturnType E_OK: Size and buffer successfully returned.
DEM_BUFFER_TOO_SMALL: provided buffer size too small
later.
DEM_NO_SUCH_ELEMENT: Found no (further) element
matching the filter criteria
Description Gets freeze frame data by the DTC selected by Dem_SelectFreezeFrameData. The function
stores the data in the provided DestBuffer.
Available via Dem.h
c()

AUTOSAR CP R20-11
8.3.4.2.7 Dem_SelectExtendedDataRecord
[SWS_Dem_91017] d
Service Name Dem_SelectExtendedDataRecord
Syntax Std_ReturnType Dem_SelectExtendedDataRecord (
uint8 ClientId,
uint8 ExtendedDataNumber
)
Service ID [hex] 0xba

ExtendedDataNumber Identification/Number of requested extended data record.
Additionally the values 0xFE and 0xFF are explicitly allowed to
request the overall size of all OBD records / all records.
Return value Std_ReturnType E_OK: Extended data record successfully selected.
does not exist.
DEM_PENDING: Selecting the extended data record is currently
in progress. The caller shall call this function again at a later
moment.
progress.
Description Sets the filter to be used by Dem_GetNextExtendedDataRecord and Dem_GetSizeOfExtended
DataRecordSelection.
Available via Dem.h
c()
8.3.4.2.8 Dem_SelectFreezeFrameData
[SWS_Dem_91015] d
Service Name Dem_SelectFreezeFrameData
Syntax Std_ReturnType Dem_SelectFreezeFrameData (
uint8 ClientId,
uint8 RecordNumber
)

5

AUTOSAR CP R20-11
4
RecordNumber Unique identifier for a snapshot record as defined in ISO
14229-1. The value 0xFF is a placeholder referencing all
snapshot records of the addressed DTC. The value 0x00
indicates the DTC-specific WWH-OBD snapshot record.
Return value Std_ReturnType E_OK: Freeze frame data successfully selected.
does not exist.
DEM_PENDING: Selecting the freeze frame is currently in
moment.
progress.
Description Sets the filter to be used by Dem_GetNextFreezeFrameData and Dem_GetSizeOfFreezeFrame
Selection.
Available via Dem.h
c()
8.3.4.2.9 Dem_GetNumberOfFreezeFrameRecords
[SWS_Dem_91191] d
Service Name Dem_GetNumberOfFreezeFrameRecords
Syntax Std_ReturnType Dem_GetNumberOfFreezeFrameRecords (
uint8 ClientId,
uint16* NumberOfFilteredRecords
)

Parameters (out) NumberOfFiltered Number of all freeze frame records currently stored in the primary
Records event memory.
Return value Std_ReturnType Status of the operation
E_OK: Returned correctly the number of freeze frame records
later
Description This function returns the number of all freeze frame records currently stored in the primary
event memory
Available via Dem.h
c()

AUTOSAR CP R20-11
8.3.4.3 DTC storage
8.3.4.3.1 Dem_DisableDTCSetting
[SWS_Dem_00242] d
Service Name Dem_DisableDTCSetting
Syntax Std_ReturnType Dem_DisableDTCSetting (
uint8 ClientId
)

moment.
Description Disables the DTC setting for all DTCs assigned to the DemEventMemorySet of the addressed
client.
Available via Dem.h
c(RS_Diag_04150)
8.3.4.3.2 Dem_EnableDTCSetting
[SWS_Dem_00243] d
Service Name Dem_EnableDTCSetting
Syntax Std_ReturnType Dem_EnableDTCSetting (
uint8 ClientId
)

Return value Std_ReturnType E_OK: The operation was successful;
DEM_PENDING: The started operation is currently in progress.
The caller shall call this function again at a later moment.
Description (Re)-Enables the DTC setting for all DTCs assigned to the DemEventMemorySet of the
addressed client.
Available via Dem.h
c(RS_Diag_04192, RS_Diag_04159, RS_Diag_04150)

AUTOSAR CP R20-11
8.3.5 OBD-specific Dcm <=> Dem Interfaces
8.3.5.1 Dem_DcmGetInfoTypeValue08
[SWS_Dem_00316] d
Service Name Dem_DcmGetInfoTypeValue08
Syntax Std_ReturnType Dem_DcmGetInfoTypeValue08 (
Dcm_OpStatusType OpStatus,
uint8* Iumprdata08,
uint8* Iumprdata08BufferSize
)

Parameters (in) OpStatus Only DCM_INITIAL will appear, because this API behaves
synchronous.
Parameters (inout) Iumprdata08BufferSize The maximum number of data bytes that can be written to the
Iumprdata08 Buffer.
Parameters (out) Iumprdata08 Buffer containing the number of data elements (as defined in
ISO-15031-5) and contents of InfoType $08. The buffer is
provided by the Dcm.
Return value Std_ReturnType Always E_OK is returned.
Description Service is used for requesting IUMPR data according to InfoType $08. This interface is derived
from the prototype <Module>_GetInfotypeValueData() defined by the Dcm. Therefore Dcm_Op
StatusType and Std_ReturnType are contained. API is needed in OBD-relevant ECUs only.
API Availability: This API will be available only if ({ecuc(Dem/DemGeneral.DemOBDSupport)}
!= DEM_OBD_NO_OBD_SUPPORT)
Available via Dem_Dcm.h
c()
8.3.5.2 Dem_DcmGetInfoTypeValue0B
[SWS_Dem_00317] d
Service Name Dem_DcmGetInfoTypeValue0B
Syntax Std_ReturnType Dem_DcmGetInfoTypeValue0B (
Dcm_OpStatusType OpStatus,
uint8* Iumprdata0B,
uint8* Iumprdata0BBufferSize
)

Parameters (in) OpStatus Only DCM_INITIAL will appear, because this API behaves
synchronous.
5

AUTOSAR CP R20-11
4
Parameters (inout) Iumprdata0BBufferSize The maximum number of data bytes that can be written to the
Iumprdata0B Buffer.
Parameters (out) Iumprdata0B Buffer containing the number of data elements (as defined in
ISO-15031-5) and contents of InfoType $0B. The buffer is
provided by the Dcm.
Description Service is used for requesting IUMPR data according to InfoType $0B. This interface is derived
from the prototype <Module>_GetInfotypeValueData() defined by the Dcm. Therefore Dcm_Op
StatusType and Std_ReturnType are contained. API is needed in OBD-relevant ECUs only.
c()
8.3.5.3 Dem_DcmReadDataOfPID01
[SWS_Dem_00318] d
Service Name Dem_DcmReadDataOfPID01
Syntax Std_ReturnType Dem_DcmReadDataOfPID01 (
uint8* PID01value
)

Parameters (out) PID01value Buffer containing the contents of PID $01 computed by the Dem.
The buffer is provided by the Dcm with the appropriate size, i.e.
during configuration, the Dcm identifies the required size from the
largest PID in order to configure a PIDBuffer.
Return value Std_ReturnType Always E_OK is returned, as E_NOT_OK will never appear.
Description Service to report the value of PID $01 computed by the Dem. API is needed in OBD-relevant
ECUs only.
c()
8.3.5.4 Dem_DcmReadDataOfPID1C
[SWS_Dem_00325] d

AUTOSAR CP R20-11
Service Name Dem_DcmReadDataOfPID1C

Syntax Std_ReturnType Dem_DcmReadDataOfPID1C (
uint8* PID1Cvalue
)

Parameters (out) PID1Cvalue Buffer containing the contents of PID $1C computed by the Dem.
The value of PID$1C is configuration within DemOBDCompliancy.
Description Service to report the value of PID $1C computed by the Dem. API is needed in OBD-relevant
ECUs only.
c()
[SWS_Dem_00319] d
uint8* PID21value
)

ECUs only.
c()

AUTOSAR CP R20-11
[SWS_Dem_00320] d
uint8* PID30value
)

ECUs only.
c()
[SWS_Dem_00321] d
uint8* PID31value
)

5

AUTOSAR CP R20-11
4
ECUs only.
== DEM_OBD_MASTER_ECU)
c()
[SWS_Dem_00322] d
uint8* PID41value
)

ECUs only.
c()
8.3.5.9 Dem_DcmReadDataOfPID4D
[SWS_Dem_00323] d
Service Name Dem_DcmReadDataOfPID4D
Syntax Std_ReturnType Dem_DcmReadDataOfPID4D (
uint8* PID4Dvalue
)
5

AUTOSAR CP R20-11
4
Parameters (out) PID4Dvalue Buffer containing the contents of PID $4D computed by the Dem.
Description Service to report the value of PID $4D computed by the Dem. API is needed in OBD-relevant
ECUs only.
c()
8.3.5.10 Dem_DcmReadDataOfPID4E
[SWS_Dem_00324] d
Service Name Dem_DcmReadDataOfPID4E
Syntax Std_ReturnType Dem_DcmReadDataOfPID4E (
uint8* PID4Evalue
)

Parameters (out) PID4Evalue Buffer containing the contents of PID $4E computed by the Dem.
Description Service to report the value of PID $4E computed by the Dem. API is needed in OBD-relevant
ECUs only.
c()

AUTOSAR CP R20-11
[SWS_Dem_01187] d
uint8* PID91value
)

ECUs only.
c()
8.3.5.12 Dem_DcmReadDataOfOBDFreezeFrame
[SWS_Dem_00327] d
Service Name Dem_DcmReadDataOfOBDFreezeFrame
Syntax Std_ReturnType Dem_DcmReadDataOfOBDFreezeFrame (
uint8 PID,
uint8 DataElementIndexOfPID,
uint8* DestBuffer,
uint16* BufSize
)

Parameters (inout) PID This parameter is an identifier for a PID as defined in
ISO15031-5.
DataElementIndexOfPID Data element index of this PID according to the Dcm
configuration of service $02. It is zero-based and consecutive,
and ordered by the data element positions (configured in Dcm,
refer to SWS_Dem_00597).
5

AUTOSAR CP R20-11
4
Parameters (inout) DestBuffer This parameter contains a byte pointer that points to the buffer, to
which the data element of the PID shall be written to. The format
is raw hexadecimal values and contains no header-information.
BufSize When the function is called this parameter contains the maximum
parameter.
Return value Std_ReturnType E_OK Freeze frame data was successfully reported
E_NOT_OK Freeze frame data was not successfully reported
Description Gets data element per PID and index of the most important freeze frame being selected for the
output of service $02. The function stores the data in the provided DestBuffer. API is needed in
OBD-relevant ECUs only.
c()
8.3.5.13 Dem_DcmGetDTCOfOBDFreezeFrame
[SWS_Dem_00624] d
Service Name Dem_DcmGetDTCOfOBDFreezeFrame
Syntax Std_ReturnType Dem_DcmGetDTCOfOBDFreezeFrame (
uint8 FrameNumber,
uint32* DTC,
Dem_DTCFormatType DTCFormat
)

Parameters (in) FrameNumber Unique identifier for a freeze frame record as defined in ISO
15031-5. The value 0x00 indicates the complete OBD freeze
frame. Other values are reserved for future functionality.
DTCFormat Output format of the DTC value.
Parameters (out) DTC Diagnostic Trouble Code in ODB format. If the return value of the
function is other than E_OK this parameter does not contain valid
data.
Return value Std_ReturnType E_OK: operation was successful
E_NOT_OK: no DTC available
Description Gets DTC by freeze frame record number. API is needed in OBD-relevant ECUs only.
c()

AUTOSAR CP R20-11
8.3.5.14 Dem_DcmGetAvailableOBDMIDs
[SWS_Dem_00766] d
Service Name Dem_DcmGetAvailableOBDMIDs
Syntax Std_ReturnType Dem_DcmGetAvailableOBDMIDs (
uint8 Obdmid,
uint32* Obdmidvalue
)
Service ID [hex] 0xa3

Parameters (in) Obdmid Availablity OBDMID ($00,$20, $40...)
Parameters (out) Obdmidvalue Bit coded information on the support of OBDMIDs.
Return value Std_ReturnType E_OK: Report of DTR result successful
Description Reports the value of a requested "availability-OBDMID" to the DCM upon a Service $06
request. Derived from that the tester displays the supported tests a mechanic can select from.
API is needed in OBD-relevant ECUs only.
c()
8.3.5.15 Dem_DcmGetNumTIDsOfOBDMID
[SWS_Dem_00767] d
Service Name Dem_DcmGetNumTIDsOfOBDMID
Syntax Std_ReturnType Dem_DcmGetNumTIDsOfOBDMID (
uint8 Obdmid,
uint8* numberOfTIDs
)

Parameters (in) Obdmid OBDMID subject of the request to identify the number of
assigned TIDs
Parameters (out) numberOfTIDs Number of assigned TIDs for the requested OBDMID. Used as
loop value for the DCM to retrieve all OBD/TID result data.
Return value Std_ReturnType E_OK: get number of TIDs successful
E_NOT_OK: get number of TIDs failed
5

AUTOSAR CP R20-11
4
Description Gets the number of TIDs per (functional) OBDMID. This can be used by the DCM to iteratively
request for OBD/TID result data within a loop from 0....numberOfTIDs-1 API is needed in
c()
8.3.5.16 Dem_DcmGetDTRData
[SWS_Dem_00768] d
Service Name Dem_DcmGetDTRData
Syntax Std_ReturnType Dem_DcmGetDTRData (
uint8 Obdmid,
uint8 TIDindex,
uint8* TIDvalue,
uint8* UaSID,
uint16* Testvalue,
uint16* Lowlimvalue,
uint16* Upplimvalue
)

Parameters (in) Obdmid Identification of a DTR element by assigned DTRId.
TIDindex Index of the TID within the DEM. Runs from 0 to "numberOfTIDs"
obtained in the call to Dem_DcmGetNumTIDsOfOBDMID()
Parameters (out) TIDvalue TID to be put on the tester reponse

UaSID UaSID to be put on the tester reponse
Testvalue Latest test result
Lowlimvalue Lower limit value associated to the latest test result
Upplimvalue Upper limit value associated to the latest test result
E_NOT_OK: Report of DTR result failed
Description Reports a DTR data along with TID-value, UaSID, test result with lower and upper limit. API is
needed in OBD-relevant ECUs only.
c()

AUTOSAR CP R20-11
8.3.6 Interface J1939Dcm <=> Dem
8.3.6.1.1 Dem_J1939DcmSetDTCFilter
[SWS_Dem_00970] d
Service Name Dem_J1939DcmSetDTCFilter
Syntax Std_ReturnType Dem_J1939DcmSetDTCFilter (
Dem_J1939DcmDTCStatusFilterType DTCStatusFilter,
Dem_DTCKindType DTCKind,
uint8 ClientId,
Dem_J1939DcmLampStatusType* LampStatus
)

Parameters (in) DTCStatusFilter The following types are available: DEM_J1939DTC_ACTIVE
DEM_J1939DTC_PREVIOUSLY_ACTIVE DEM_J1939DTC_
PENDING DEM_J1939DTC_PERMANENT DEM_J1939DTC_
CURRENTLY_ACTIVE
DTCKind Defines the functional group of DTCs to be reported (e.g. all
DTC, OBD-relevant DTC)
DTCOrigin This parameter is used to select the source memory the DTCs
shall be read/cleared from.
ClientId ClientId to address the J1939 event memory
Parameters (out) LampStatus E_OK: Operation successful DEM_NO_SUCH_ELEMENT: The
requested element is not available DEM_PENDING: Operation
successful and result pending. DEM_BUFFER_TOO_SMALL:
The provided buffer is too small
Return value Std_ReturnType E_OK: Operation successful
E_NOT_OK: Filter could not be set
Description The function sets the DTC filter for a specific node and returns the composite lamp status of the
filtered DTCs.
c(RS_Diag_04112)
8.3.6.1.2 Dem_J1939DcmGetNumberOfFilteredDTC
[SWS_Dem_00972] d

AUTOSAR CP R20-11
Service Name Dem_J1939DcmGetNumberOfFilteredDTC

Syntax Std_ReturnType Dem_J1939DcmGetNumberOfFilteredDTC (
uint16* NumberOfFilteredDTC,
uint8 ClientId
)

Parameters (in) ClientId ClientId to address the J1939 event memory
Parameters (out) NumberOfFilteredDTC The number of DTCs matching the defined status mask.
available
DEM_PENDING: Operation successful and result pending.
DEM_BUFFER_TOO_SMALL: The provided buffer is too small
Description Gets the number of currently filtered DTCs set by the function Dem_J1939DcmSetDTCFilter.
c()
8.3.6.1.3 Dem_J1939DcmGetNextFilteredDTC
[SWS_Dem_00973] d
Service Name Dem_J1939DcmGetNextFilteredDTC
Syntax Std_ReturnType Dem_J1939DcmGetNextFilteredDTC (
uint32* J1939DTC,
uint8* OccurenceCounter,
uint8 ClientId
)

Parameters (out) J1939DTC Receives the J1939DTC value. If the return value of the function
is other than DEM_FILTERED_OK this parameter does not
contain valid data.
OccurenceCounter This parameter receives the corresponding occurrence counter. If
the return value of the function call is other than DEM_
FILTERED_OK this parameter does not contain valid data.
available
5

AUTOSAR CP R20-11
4
Description Gets the next filtered J1939 DTC.
c()
8.3.6.1.4 Dem_J1939DcmFirstDTCwithLampStatus
[SWS_Dem_00974] d
Service Name Dem_J1939DcmFirstDTCwithLampStatus
Syntax void Dem_J1939DcmFirstDTCwithLampStatus (
uint8 ClientId
)

Return value None
Description The function sets the filter to the first applicable DTC for the DM31 response for a specific node.
c(RS_Diag_04110)
8.3.6.1.5 Dem_J1939DcmGetNextDTCwithLampStatus
[SWS_Dem_00975] d
Service Name Dem_J1939DcmGetNextDTCwithLampStatus
Syntax Std_ReturnType Dem_J1939DcmGetNextDTCwithLampStatus (
Dem_J1939DcmLampStatusType* LampStatus,
uint32* J1939DTC,
uint8 ClientId
)

5

AUTOSAR CP R20-11
4
Parameters (out) LampStatus Receives the lamp status returned by this function. If the return
J1939DTC Receives the J1939DTC value. If the return value of the function
contain valid data.
available
Description Gets the next filtered J1939 DTC for DM31 including current LampStatus.
c()
8.3.6.2 DTC storage
8.3.6.2.1 Dem_J1939DcmClearDTC
[SWS_Dem_00976] d
Service Name Dem_J1939DcmClearDTC
Syntax Std_ReturnType Dem_J1939DcmClearDTC (
Dem_J1939DcmSetClearFilterType DTCTypeFilter,
uint8 ClientId
)

Parameters (in) DTCTypeFilter Defines the type of DTCs to be cleared.
DTCOrigin This parameter is used to select the source memory the DTCs
shall be read/cleared from.
Return value Std_ReturnType E_OK: DTC successfully cleared
does not exist or clearing is restricted by configuration to group of
all DTCs only.
DEM_CLEAR_FAILED: DTC clearing failed
DEM_CLEAR_BUSY: Another client is currently clearing DTCs.
The requested operation will not be started and the caller shall try
5
5

AUTOSAR CP R20-11
4
4
again at a later moment.
DEM_CLEAR_MEMORY_ERROR: An error occurred during
erasing a memory location (e.g. if DemClearDTCBehavior is set
to DEM_CLRRESP_NON-VOLATILE_FINISH and erasing
of non-volatile-block failed).
DEM_PENDING: Clearing the DTCs is currently in progress. The
Description Clears the status of all event(s) related to the specified DTC(s), as well as all associated event
memory entries for these event(s).
c(RS_Diag_04112)
8.3.6.2.2 Dem_J1939DcmSetFreezeFrameFilter
[SWS_Dem_00977] d
Service Name Dem_J1939DcmSetFreezeFrameFilter
Syntax Std_ReturnType Dem_J1939DcmSetFreezeFrameFilter (
Dem_J1939DcmSetFreezeFrameFilterType FreezeFrameKind,
uint8 ClientId
)

Parameters (in) FreezeFrameKind The following types are available: DEM_J1939DCM_
FREEZEFRAME DEM_J1939DCM_EXPANDED_
FREEZEFRAME DEM_J1939DCM_SPNS_IN_EXPANDED_
FREEZEFRAME
Description The function sets the FreezeFrame filter for a specific node.
c(RS_Diag_04112)
8.3.6.2.3 Dem_J1939DcmGetNextFreezeFrame
[SWS_Dem_00978] d

AUTOSAR CP R20-11
Service Name Dem_J1939DcmGetNextFreezeFrame

Syntax Std_ReturnType Dem_J1939DcmGetNextFreezeFrame (
uint32* J1939DTC,
uint8* DestBuffer,
uint16* BufSize,
uint8 ClientId
)

Parameters (inout) DestBuffer This parameter contains a byte pointer that points to the buffer, to
which the freeze frame data record shall be written to.
BufSize When the function is called this parameter contains the maximum
function returns the actual number of written data bytes in Dest
Buffer
Parameters (out) J1939DTC Receives the J1939DTC value. If the return value of the function
contain valid data.
available
Description Gets next freeze frame data. The function stores the data in the provided DestBuffer.
c(RS_Diag_04112)
8.3.6.2.4 Dem_J1939DcmGetNextSPNInFreezeFrame
[SWS_Dem_00979] d
Service Name Dem_J1939DcmGetNextSPNInFreezeFrame
Syntax Std_ReturnType Dem_J1939DcmGetNextSPNInFreezeFrame (
uint32* SPNSupported,
uint8* SPNDataLength,
uint8 ClientId
)

5

AUTOSAR CP R20-11
4
Parameters (out) SPNSupported This parameter contains the next SPN in the ExpandedFreeze
Frame
SPNDataLength This parameter contains the corresponding dataLength of the
SPN
available
Description Gets next SPN.
c(RS_Diag_04112)
8.3.6.3 Reporting
8.3.6.3.1 Dem_J1939DcmSetRatioFilter
[SWS_Dem_00980] d
Service Name Dem_J1939DcmSetRatioFilter
Syntax Std_ReturnType Dem_J1939DcmSetRatioFilter (
uint16* IgnitionCycleCounter,
uint16* OBDMonitoringConditionsEncountered,
uint8 ClientId
)

Parameters (out) IgnitionCycleCounter Ignition Cycle Counter
OBDMonitoringConditions OBD Monitoring Conditions Encountered
Encountered
Description The function sets the Ratio filter for a specific node and returns the corresponding Ignition
Cycle Counter and General Denominator.
c()
8.3.6.3.2 Dem_J1939DcmGetNextFilteredRatio
[SWS_Dem_00981] d

AUTOSAR CP R20-11
Service Name Dem_J1939DcmGetNextFilteredRatio

Syntax Std_ReturnType Dem_J1939DcmGetNextFilteredRatio (
uint32* SPN,
uint16* Numerator,
uint16* Denominator,
uint8 ClientId
)

Parameters (out) SPN Receives the SPN of the applicaple system monitor. If the return
Numerator Receives the Numerator of the applicable system monitor. If the
return value of the function is other than DEM_FILTERED_OK
Denominator Receives the Denominator of the applicable system monitor. If
the return value of the function is other than DEM_FILTERED_OK
available
Description Gets the next filtered Ratio.
c(RS_Diag_04112)
8.3.6.3.3 Dem_J1939DcmReadDiagnosticReadiness1
[SWS_Dem_00982] d
Service Name Dem_J1939DcmReadDiagnosticReadiness1
Syntax Std_ReturnType Dem_J1939DcmReadDiagnosticReadiness1 (
Dem_J1939DcmDiagnosticReadiness1Type* DataValue,
uint8 ClientId
)

Parameters (out) DataValue Buffer of 8 bytes containing the contents of Diagnostic Readiness
1 (DM05) computed by the Dem.
5

AUTOSAR CP R20-11
4
Description Service to report the value of Diagnostic Readiness 1 (DM05) computed by the Dem.
c(RS_Diag_04113)
[SWS_Dem_00983] d
uint8 ClientId
)

c(RS_Diag_04113)
[SWS_Dem_00770] d
uint8 ClientId
)

5

AUTOSAR CP R20-11
4
c(RS_Diag_04113)
8.3.7 OBD-specific Interfaces
8.3.7.1 Dem_SetEventDisabled
[SWS_Dem_00312] d
Service Name Dem_SetEventDisabled
Syntax Std_ReturnType Dem_SetEventDisabled (
)

Return value Std_ReturnType E_OK set of event to disabled was successfull.
E_NOT_OK set of event disabled failed
Description Service for reporting the event as disabled to the Dem for the PID $41 computation. API is
needed in OBD-relevant ECUs only.
Available via Dem.h
c()
8.3.7.2 Dem_RepIUMPRFaultDetect
[SWS_Dem_00313] d

AUTOSAR CP R20-11
Service Name Dem_RepIUMPRFaultDetect

Syntax Std_ReturnType Dem_RepIUMPRFaultDetect (
Dem_RatioIdType RatioID
)

Reentrancy Reentrant for different RatioIDs. Non reentrant for the same RatioID.
Parameters (in) RatioID Ratio Identifier reporting that a respective monitor could have
found a fault - only used when interface option "API" is selected
Return value Std_ReturnType E_OK report of IUMPR result was successfully reported
Description Service for reporting that faults are possibly found because all conditions are fullfilled. API is
needed in OBD-relevant ECUs only
Available via Dem.h
c()
8.3.7.3 Dem_SetIUMPRDenCondition
[SWS_Dem_00733] d
Service Name Dem_SetIUMPRDenCondition
Syntax Std_ReturnType Dem_SetIUMPRDenCondition (
Dem_IumprDenomCondIdType ConditionId,
Dem_IumprDenomCondStatusType ConditionStatus
)
Service ID [hex] 0xae

Sync/Async Synchronous /Asynchronous
Parameters (in) ConditionId Identification of a IUMPR denominator condition ID (General
Denominator, Cold start, EVAP, 500mi).
ConditionStatus Status of the IUMPR denominator condition (Not-reached,
reached, not reachable / inhibited)
Return value Std_ReturnType E_OK: set of IUMPR denominator condition was successful
E_NOT_OK: set of IUMPR denominator condition failed or could
not be accepted.
Description In order to communicate the status of the (additional) denominator conditions among the OBD
relevant ECUs, the API is used to forward the condition status to a Dem of a particular ECU.
API is needed in OBD-relevant ECUs only.
5

AUTOSAR CP R20-11
4
Available via Dem.h
c(RS_Diag_04192)
8.3.7.4 Dem_GetIUMPRDenCondition
[SWS_Dem_00734] d
Service Name Dem_GetIUMPRDenCondition
Syntax Std_ReturnType Dem_GetIUMPRDenCondition (
Dem_IumprDenomCondIdType ConditionId,
Dem_IumprDenomCondStatusType* ConditionStatus
)
Service ID [hex] 0xaf

Parameters (in) ConditionId Identification of a IUMPR denominator condition ID (General
Denominator, Cold start, EVAP, 500mi).
Parameters (out) ConditionStatus Status of the IUMPR denominator condition (Not-reached,
reached, not reachable / inhibited)
Return value Std_ReturnType E_OK: get of IUMPR denominator condition status was
successful
E_NOT_OK: get of condition status failed
Description In order to communicate the status of the (additional) denominator conditions among the OBD
relevant ECUs, the API is used to retrieve the condition status from the Dem of the ECU where
the conditions are computed. API is needed in OBD-relevant ECUs only.
Available via Dem.h
c()
8.3.7.5 Dem_RepIUMPRDenRelease
[SWS_Dem_00315] d
Service Name Dem_RepIUMPRDenRelease
Syntax Std_ReturnType Dem_RepIUMPRDenRelease (
Dem_RatioIdType RatioID
)

5

AUTOSAR CP R20-11
4
Parameters (in) RatioID Ratio Identifier reporting that specific denominator is released (for
physical reasons - e.g. temperature conditions or minimum
activity)
Return value Std_ReturnType E_OK report of IUMPR denominator status was successfully
reported
E_NOK report of IUMPR denominator status was not
successfully reported
Description Service is used to release a denominator of a specific monitor. API is needed in OBD-relevant
ECUs only
Available via Dem.h
c()
8.3.7.6 Dem_SetPtoStatus
[SWS_Dem_00627] d
Service Name Dem_SetPtoStatus
Syntax Std_ReturnType Dem_SetPtoStatus (
boolean PtoStatus
)

Parameters (in) PtoStatus sets the status of the PTO (TRUE==active; FALSE==inactive)
Return value Std_ReturnType Returns E_OK when the new PTO-status has been adopted by
the Dem; returns E_NOT_OK in all other cases.
Description API is needed in OBD-relevant ECUs only
Available via Dem.h
c()
8.3.7.7 Dem_ReadDataOfPID01
[SWS_Dem_01167] d

AUTOSAR CP R20-11
Service Name Dem_ReadDataOfPID01

Syntax Std_ReturnType Dem_ReadDataOfPID01 (
uint8* PID01value
)

The buffer is provided by the application with the size of 4 bytes.
Description Service to report the value of PID $01 computed by the Dem. API is needed in OBD relevant
ECUs only
Available via Dem.h
c()
8.3.7.8 Dem_GetDataOfPID21
[SWS_Dem_01093] d
Service Name Dem_GetDataOfPID21
Syntax Std_ReturnType Dem_GetDataOfPID21 (
uint8* PID21value
)

Parameters (out) PID21value Content of PID $21 as raw hex value.
Description Service to get the value of PID $21 from the Dem by a software component. API is needed in
API Availability: This API will be available only if ({ecuc(Dem/DemGeneral/DemGeneral
OBD.DemOBDCentralizedPID21Handling)} == true) && ({ecuc(Dem/DemGeneral.Dem
OBDSupport)} == DEM_OBD_MASTER_ECU)
Available via Dem.h
c()
8.3.7.9 Dem_SetDataOfPID21
[SWS_Dem_00735] d

AUTOSAR CP R20-11
Service Name Dem_SetDataOfPID21

Syntax Std_ReturnType Dem_SetDataOfPID21 (
const uint8* PID21value
)

Parameters (in) PID21value Buffer containing the contents of PID $21. The buffer is provided
by the Dcm with the appropriate size, i.e. during configuration,
the Dcm identifies the required size from the largest PID in order
to configure a PIDBuffer.
Description Service to set the value of PID $21 in the Dem by a software component. API is needed in
Available via Dem.h
c()
8.3.7.10 Dem_SetDataOfPID31
[SWS_Dem_00736] d
Service Name Dem_SetDataOfPID31
Syntax Std_ReturnType Dem_SetDataOfPID31 (
const uint8* PID31value
)

Parameters (in) PID31value Buffer containing the contents of PID $31. The buffer is provided
Description Service to set the value of PID $31 in the Dem by a software component. API is needed in
Available via Dem.h
c()

AUTOSAR CP R20-11
8.3.7.11 Dem_SetDataOfPID4D
[SWS_Dem_00737] d
Service Name Dem_SetDataOfPID4D
Syntax Std_ReturnType Dem_SetDataOfPID4D (
const uint8* PID4Dvalue
)

Parameters (in) PID4Dvalue Buffer containing the contents of PID $4D. The buffer is provided
Description Service to set the value of PID $4D in the Dem by a software component. API is needed in
Available via Dem.h
c()
8.3.7.12 Dem_SetDataOfPID4E
[SWS_Dem_00738] d
Service Name Dem_SetDataOfPID4E
Syntax Std_ReturnType Dem_SetDataOfPID4E (
const uint8* PID4Evalue
)

Parameters (in) PID4Evalue Buffer containing the contents of PID $4E. The buffer is provided
5

AUTOSAR CP R20-11
4
Description Service to set the value of PID $4E in the Dem by a software component. API is needed in
Available via Dem.h
c()
8.3.7.13 Dem_GetCycleQualified
[SWS_Dem_00740] d
Service Name Dem_GetCycleQualified
Syntax Std_ReturnType Dem_GetCycleQualified (
uint8 OperationCycleId,
boolean* isQualified
)
Service ID [hex] 0xab

Parameters (in) OperationCycleId Identification of a configured DemOperationCycle.
Parameters (out) isQualified TRUE: The dependent operation cylcle is qualified. FALSE: The
qualification conditions of the dependent operation cylcle have
not been met.
Description Returns the qualification state of the dependent operation cycle.
API Availability: This API will be available only if any of the ({ecuc(Dem/DemGeneral/Dem
OperationCycle.DemLeadingCycleRef)} != NULL)
Available via Dem.h
c()
8.3.7.14 Dem_SetCycleQualified
[SWS_Dem_91001] d
Service Name Dem_SetCycleQualified
Syntax Std_ReturnType Dem_SetCycleQualified (
uint8 OperationCycleId
)

5

AUTOSAR CP R20-11
4
Parameters (in) OperationCycleId Identification of a configured DemOperationCycle
Description Sets a dependent operation cycle as qualified, so it may be processed along with its leading
cycle.
Available via Dem.h
c()
8.3.7.15 Dem_GetDTCSeverityAvailabilityMask
[SWS_Dem_01168] d
Service Name Dem_GetDTCSeverityAvailabilityMask
Syntax Std_ReturnType Dem_GetDTCSeverityAvailabilityMask (
uint8 ClientId,
Dem_DTCSeverityType* DTCSeverityMask
)

Parameters (out) DTCSeverityMask DTCSeverityMask The value DTCSeverityMask indicates the
supported DTC severity bits from the Dem. All supported
information is indicated by setting the corresponding status bit to
1. See ISO14229-1.
Return value Std_ReturnType E_OK: get of DTC severity mask was successful
E_NOT_OK: get of DTC severity mask failed
Description Gets the DTC Severity availability mask.
Available via Dem.h
c()
8.3.7.16 Dem_GetB1Counter
[SWS_Dem_01169] d

AUTOSAR CP R20-11
Service Name Dem_GetB1Counter

Syntax Std_ReturnType Dem_GetB1Counter (
uint16* B1Counter
)

Parameters (out) B1Counter Buffer containing the B1 counter. The buffer is provided by the
application with the size of 2 bytes.
Description Service to report the value of the B1 counter computed by the Dem. API is needed in
WWH-OBD relevant ECUs only
Available via Dem.h
c()
8.3.7.17 Dem_SetDTR
[SWS_Dem_00765] d
Service Name Dem_SetDTR
Syntax Std_ReturnType Dem_SetDTR (
uint16 DTRId,
sint32 TestResult,
sint32 LowerLimit,
sint32 UpperLimit,
Dem_DTRControlType Ctrlval
)

Reentrancy Reentrant for different DTRIds. Non reentrant for the same DTRId.
Parameters (in) DTRId Identification of a DTR element by assigned DTRId.
TestResult Test result of DTR
LowerLimit Lower limit of DTR
UpperLimit Upper limit of DTR
Ctrlval Control value of the DTR to support its interpretation
Dem-internally.
E_NOT_OK: Report of DTR result failed
5

AUTOSAR CP R20-11
4
Description Reports a DTR result with lower and upper limit. The internal eventstatus serves as master
whether the DTR values are forwarded or ignored, also taking the DTRUpdateKind into
account. The EventId that is related to the DTR is assigned per configuration (and derived from
ServiceNeeds). Processing takes enable/storage conditions into account. API is needed in
Available via Dem.h
c()
8.4 Expected Interfaces

In this chapter, all interfaces required from other modules are listed.
8.4.1 Mandatory Interfaces
This chapter defines all interfaces, which are required to fulfill the core functionality of
the Dem module.
API function Description
[] d
API Function Header File Description
There are no mandatory interfaces.
c()
8.4.2 Optional Interfaces
This chapter defines all interfaces, which are required to fulfill an optional functionality
of the Dem module.
[SWS_Dem_00255] d
Dcm_DemTriggerOnDTCStatus Dcm_Dem.h Triggers on changes of the UDS status byte. Allows
to trigger on ROE Event for subservice On
DTCStatusChanged.
Det_ReportError Det.h Service to report development errors.
5

AUTOSAR CP R20-11
4
FiM_DemInit FiM_Dem.h This service re-initializes the FIM.
FiM_DemTriggerOnComponentStatus FiM_Dem.h Triggers on changes of the component failed status.
FiM_DemTriggerOnMonitorStatus FiM_Dem.h This service is provided to be called by the Dem in
order to inform the Fim about monitor status
changes.
J1939Dcm_DemTriggerOnDTCStatus J1939Dcm_Dem.h Trigger for DM01 message that a UDS status
change has happened.
NvM_GetErrorStatus NvM.h Service to read the block dependent error/status
information.
NvM_ReadBlock NvM.h Service to copy the data of the NV block to its
corresponding RAM block.
NvM_SetRamBlockStatus NvM.h Service for setting the RAM block status of a
permanent RAM block or the status of the explicit
synchronization of a NVRAM block.
NvM_WriteBlock NvM.h Service to copy the data of the RAM block to its
corresponding NV block.
c(SRS_BSW_00171)
Note: Based on implementation strategy FiM_DemInit can be used (refer also to chap-
ter chapter 7.11.3).
Note: Based on implementation strategy either NvM_[Read|Write]Block or
NvM_SetRamBlockStatus can be omitted, or the NvM usage is deactivated by con-
figuration completely (refer also to chapter chapter 7.11.5).
8.4.3 Configurable interfaces
In this chapter, all interfaces are listed where the target function could be configured.
The target function is usually a callback function. The names of this kind of interfaces
are not fixed because they are configurable.

AUTOSAR CP R20-11
«module» <Module>_DemGeneralTriggerOnEventUdsStatus
Dem <Module>_DemGeneralTriggerOnMonitorStatus
<Module>_DemTriggerOnDTCStatus
<Module>_DemTriggerOnEventData
<Module>_DemTriggerOnEventUdsStatus
<Module>_DemTriggerOnMonitorStatus
Dem_CallbackClearEventAllowed
Dem_CallbackGetFaultDetectionCounter
Dem_CallbackInitMonitorForEvent
Dem_CallbackReadDataElement
Dem_ComponentFailedCallbackFnc
«interface»
Dem_Configurable
::<Module>_DemTriggerOnDTCStatus
«configurable»
<Module>_DemTriggerOnDTCStatus(return, DTC, DTCStatusOld, DTCStatusNew)
::<Module>_DemGeneralTriggerOnMonitorStatus
<Module>_DemGeneralTriggerOnMonitorStatus(return, EventId)
::<Module>_DemTriggerOnEventUdsStatus
<Module>_DemTriggerOnEventUdsStatus(return, EventStatusByteOld, EventStatusByteNew)
::<Module>_DemTriggerOnMonitorStatus
<Module>_DemTriggerOnMonitorStatus(return)
::Dem_CallbackReadDataElement
<Module>_DemRead<DataElement>(Buffer, return, monitorData0)
::<Module>_DemTriggerOnEventData
<Module>_DemTriggerOnEventData(return, EventId)
::Dem_ComponentFailedCallbackFnc
<Module>_DemTriggerOnComponentStatus(return, ComponentId)
::Dem_CallbackClearEventAllowed
<Module>_DemClearEventAllowed<ForCondition>(return, Allowed)
::Dem_CallbackGetFaultDetectionCounter
<Module>_DemGetFaultDetectionCounter<ForEvent>(return, FaultDetectionCounter)
::<Module>_DemGeneralTriggerOnEventUdsStatus
<Module>_DemGeneralTriggerOnEventUdsStatus(return, EventId, EventStatusByteOld, EventStatusByteNew)
::Dem_CallbackInitMonitorForEvent
<Module>_DemInitMonitorFor<EventName>(return, InitMonitorReason)
«realize» «realize»
«module» «module»
[SWC] [BSW]
Figure 8.4: Configuration interfaces of the Dem module
8.4.3.1 Interface BSW modules / SW-Components <=> Dem
The callback interface from Dem to SW-Components is realized via RTE port inter-
faces. The following callback descriptions address the c-callbacks of other BSW mod-
ules.
8.4.3.1.1 InitMonitorForEvent
[SWS_Dem_00256] d
Service Name <Module>_DemInitMonitorFor<EventName>
Syntax Std_ReturnType <Module>_DemInitMonitorFor<EventName> (
Dem_InitMonitorReasonType InitMonitorReason
)
5

AUTOSAR CP R20-11
4
Parameters (in) InitMonitorReason Specific (re-)initialization reason evaluated from the monitor to
identify the initialization kind to be performed.
Return value Std_ReturnType Return value unused - only for compatibility with according RTE
operation.
Description Inits the diagnostic monitor of a specific event. There is one separate callback per event (if
configured), if no port interface is provided by the Dem.
Available via Dem_Externals.h
c(SRS_BSW_00310, SRS_BSW_00101)
8.4.3.1.2 DemTriggerOnComponentStatus
[SWS_Dem_01116] d
Service Name <Module>_DemTriggerOnComponentStatus
Syntax Std_ReturnType <Module>_DemTriggerOnComponentStatus (
Dem_ComponentIdType ComponentId
)
Parameters (in) ComponentId Identification of a DemComponent.
Return value Std_ReturnType Return value unused - only for compatibility with according RTE
operation.
Description Triggers on changes of the DemComponent failed status.
c()
8.4.3.2 ClearDtcNotification
[SWS_Dem_91002] d
Service Name <Module>_ClearDtcNotification
5

AUTOSAR CP R20-11
4
Syntax Std_ReturnType <Module>_ClearDtcNotification (
uint32 DTC,
)
Parameters (in) DTC DTC or group of DTC that is cleared.
DTCFormat Format of the DTC value.
DTCOrigin Event memory which is selected by the current clear operation.
Return value Std_ReturnType E_OK is always returned
Description Called by the Dem when performing a clear DTC operation.
c()
8.4.3.3 DemGeneralTriggerOnMonitorStatus
[SWS_Dem_91009] d
Service Name <Module>_DemGeneralTriggerOnMonitorStatus
Syntax Std_ReturnType <Module>_DemGeneralTriggerOnMonitorStatus (
)
Return value Std_ReturnType E_OK: this function always returns E_OK for compatibility
reasons with RTE
Description Triggers on changes of the monitor status. Called synchronously in context of event status
reporting.
c()
8.4.3.4 DemGeneralTriggerOnEventUdsStatus
[SWS_Dem_00259] d

AUTOSAR CP R20-11
Service Name <Module>_DemGeneralTriggerOnEventUdsStatus

Syntax Std_ReturnType <Module>_DemGeneralTriggerOnEventUdsStatus (
Dem_UdsStatusByteType EventStatusByteOld,
Dem_UdsStatusByteType EventStatusByteNew
)
EventStatusByteOld UDS DTC status byte of event before change (refer to chapter
"Status bit support").
EventStatusByteNew UDS DTC status byte of event after change (refer to chapter
reasons with RTE.
Description Triggers on changes of the UDS DTC status byte.
c(RS_Diag_04148)
8.4.3.5 DemTriggerOnEventUdsStatus
[SWS_Dem_91006] d
Service Name <Module>_DemTriggerOnEventUdsStatus
Syntax Std_ReturnType <Module>_DemTriggerOnEventUdsStatus (
Dem_UdsStatusByteType EventStatusByteOld,
Dem_UdsStatusByteType EventStatusByteNew
)
Parameters (in) EventStatusByteOld UDS DTC status byte of event before change (refer to chapter
EventStatusByteNew UDS DTC status byte of event after change (refer to chapter
reasons with RTE
Description Triggers on changes of the UDS DTC status byte.
c()

AUTOSAR CP R20-11
8.4.3.6 DemTriggerOnDTCStatus
[SWS_Dem_00260] d
Service Name <Module>_DemTriggerOnDTCStatus
Syntax Std_ReturnType <Module>_DemTriggerOnDTCStatus (
uint32 DTC,
Dem_UdsStatusByteType DTCStatusOld,
Dem_UdsStatusByteType DTCStatusNew
)
Parameters (in) DTC Diagnostic Trouble Code in UDS format.
DTCStatusOld UDS status before change
DTCStatusNew UDS status after change
reasons with RTE.
Description Triggers on changes of the UDS status byte.
c()
8.4.3.7 DemTriggerOnMonitorStatus
[SWS_Dem_91010] d
Service Name <Module>_DemTriggerOnMonitorStatus
Syntax Std_ReturnType <Module>_DemTriggerOnMonitorStatus (
void
)
reasons with RTE
Description Triggers on changes of the monitor status. Called synchronously in context of event status
reporting.
c()

AUTOSAR CP R20-11
8.4.3.8 EventDataChanged
[SWS_Dem_00562] d
Service Name <Module>_DemTriggerOnEventData
Syntax Std_ReturnType <Module>_DemTriggerOnEventData (
)
reasons with RTE.
Description Triggers on changes of the event related data in the event memory.
c(RS_Diag_04160)
8.4.3.9 ClearEventAllowed
[SWS_Dem_00563] d
Service Name <Module>_DemClearEventAllowed<ForCondition>
Syntax Std_ReturnType <Module>_DemClearEventAllowed<ForCondition> (
boolean* Allowed
)
Parameters (out) Allowed True - clearance of event is allowed False - clearance of event is
not allowed
Description Triggers on DTC-deletion, which is not allowed if the out-parameter returns False. There is one
separate callback per condition, which can be assigned to one or several events, if no port
interface is provided by the Dem. Parameter "Allowed" will be unchanged in case E_NOT_OK
is returned.
c()
8.4.3.10 ReadDataElement
[SWS_Dem_00564] d

AUTOSAR CP R20-11
Service Name <Module>_DemRead<DataElement>

Syntax Std_ReturnType <Module>_DemRead<DataElement> (
uint8* Buffer,
[Dem_MonitorDataType monitorData0]
)
Parameters (in) monitorData0 MonitorData that was provided by Dem_SetEventStatusWith
MonitorData
Parameters (out) Buffer Buffer containing the value of the data element
Description Requests the current value of the data element. There is one separate callback per data
element, if no port interface is provided by the Dem.
c()
Note: Square brackets [] indicate that an argument is optional.
8.4.3.11 GetFaultDetectionCounter
[SWS_Dem_00263] d
Service Name <Module>_DemGetFaultDetectionCounter<ForEvent>
Syntax Std_ReturnType <Module>_DemGetFaultDetectionCounter<ForEvent> (
sint8* FaultDetectionCounter
)
Parameters (out) FaultDetectionCounter This parameter receives the fault detection counter information of
the requested EventId. If the return value of the function call is
Return value Std_ReturnType E_OK: request was successful
E_NOT_OK: request failed
Description Gets the current fault detection counter value. There is one c-callback per event using
monitor-internal debouncing, if no port interface is provided by the Dem.
c()

AUTOSAR CP R20-11
8.4.3.12 Dem_CallbackEventSyncStorageProcessed
[SWS_Dem_91042]{DRAFT} d
Service Name Dem_CallbackEventSyncStorageProcessed (draft)
Syntax Std_ReturnType Dem_CallbackEventSyncStorageProcessed (
void
)
Service ID [hex] 0xc0

Return value Std_ReturnType E_OK: For RTE compatiblility reasons, only E_OK is allowed and
returned by the caller.
Description Called by the Dem after the internal processing of Dem_SetEventFailedWithSyncFreezeFrame
is done and a further call of Dem_SetEventFailedWithSyncFreezeFrame with the same event ID
can be processed by the Dem.
Tags:atp.Status=draft
Available via Dem.h
c()
8.5 Scheduled functions

These functions are directly called by Basic Software Scheduler. The following func-
tions shall have no return value and no parameter. All functions shall be non reentrant.
8.5.1 Dem_MainFunction
[SWS_Dem_00266] d
Service Name Dem_MainFunction
Syntax void Dem_MainFunction (
void
)

Description Processes all not event based Dem internal functions.
Available via SchM_Dem.h
c()
[SWS_Dem_00125] dThe function Dem_MainFunction shall process all not event
based Dem module internal functions.c(SRS_BSW_00373)

AUTOSAR CP R20-11
For details refer to the chapter 8.5 “Scheduled Functions” in SWS_BSWGeneral.
8.5.2 Runnable Entity MainFunction
1 RunnableEntity MainFunction
2 symbol "Dem_MainFunction"
3 canbeInvokedConcurrently = FALSE
4 SSCP = port CBEventUdsStatusChanged_*,
CallbackEventUdsStatusChanged
5 SSCP = port GeneralCBStatusEvt,
GeneralCallbackEventUdsStatusChanged
6 SSCP = port CBStatusDTC_*, DTCStatusChanged
7 SSCP = port CBDataEvt_*, EventDataChanged
8 SSCP = port GeneralCBDataEvt, EventDataChanged
9 SSCP = port CBReadData_*, ReadData
8.6 Service Interfaces
8.6.1 Implementation Data Types
8.6.1.1 Dem_DataType
[SWS_Dem_91026] d
Name Dem_DataType_{Data}
Kind Type
Derived from Basetype Variation
Dem_DataArrayType_{Data} {(ecuc((Dem/DemGeneral/DemDataElementClass/Dem
ExternalCSDataElementClass/DemDataElementDataType)
== ([S|U]INT[8|16|32]|FLOAT)_N) || ((Dem/DemGeneral/
DemDataElementClass/DemExternalSRDataElementClass/
DemDataElementDataType) == ([S|U]INT[8|16|32]|FLOAT)_
N))}
Dem_DataPrimitiveType_{Data} {(ecuc((Dem/DemGeneral/DemDataElementClass/Dem
== (BOOLEAN|[S|U]INT[8|16|32]|FLOAT) || ((Dem/Dem
General/DemDataElementClass/DemExternalSRData
ElementClass/DemDataElementDataType) ==
(BOOLEAN|[S|U]INT[8|16|32]|FLOAT))))}
Description Data type definition for external data elements
Variation ((({ecuc(Dem/DemGeneral/DemDataElementClass)} instanceof {ecuc(Dem/DemGeneral/Dem
DataElementClass/DemExternalCSDataElementClass)}) && ({ecuc(Dem/DemGeneral/DemData
ElementClass/DemExternalCSDataElementClass/DemDataElementUsePort)} == true)) ||
({ecuc(Dem/DemGeneral/DemDataElementClass)} instanceof {ecuc(Dem/DemGeneral/DemData
ElementClass/DemExternalSRDataElementClass)}))
Data = {ecuc(Dem/DemGeneral/DemDataElementClass.SHORT-NAME)}
Available via Rte_Dem_Type.h
c()

AUTOSAR CP R20-11
8.6.1.2 Dem_DataPrimitiveType
[SWS_Dem_91033] d
Name Dem_DataPrimitiveType_{Data}
Kind Type
Basetype Variation
Derived from
boolean {(ecuc((Dem/DemGeneral/DemDataElementClass/Dem
== BOOLEAN) || ((Dem/DemGeneral/DemDataElement
Class/DemExternalSRDataElementClass/DemDataElement
DataType) == BOOLEAN)}
float32 {(ecuc((Dem/DemGeneral/DemDataElementClass/Dem
== FLOAT) || ((Dem/DemGeneral/DemDataElementClass/
DemExternalSRDataElementClass/DemDataElementData
Type) == FLOAT)}
sint16 {(ecuc((Dem/DemGeneral/DemDataElementClass/Dem
== SINT16) || ((Dem/DemGeneral/DemDataElementClass/
Type) == SINT16)}
Type) == SINT32)}
Type) == SINT8)}
uint16 {(ecuc((Dem/DemGeneral/DemDataElementClass/Dem
== UINT16) || ((Dem/DemGeneral/DemDataElementClass/
Type) == UINT16)}
Type) == UINT32)}
Type) == UINT8)}
Description –
Variation {(ecu((Dem/DemGeneral/DemDataElementClass/DemExternalCSDataElementClass/DemData
ElementDataType) == (BOOLEAN|[S|U]INT[8|16|32]|FLOAT) || ((Dem/DemGeneral/DemData
ElementClass/DemExternalSRDataElementClass/DemDataElementDataType) ==
(BOOLEAN|[S|U]INT[8|16|32]|FLOAT))))}
c()

AUTOSAR CP R20-11
8.6.1.3 Dem_DataArrayType
[SWS_Dem_91034] d
Name Dem_DataArrayType_{Data}
Kind Array
Element type Type Variation

float32 {(ecuc((Dem/DemGeneral/DemDataElementClass/DemExternalCSData
ElementClass/DemDataElementDataType) == FLOAT_N) || ((Dem/Dem
General/DemDataElementClass/DemExternalSRDataElementClass/
DemDataElementDataType) == FLOAT_N))}
sint16 {(ecuc((Dem/DemGeneral/DemDataElementClass/DemExternalCSData
ElementClass/DemDataElementDataType) == SINT16_N) || ((Dem/Dem
DemDataElementDataType) == SINT16_N))}
uint16 {(ecuc((Dem/DemGeneral/DemDataElementClass/DemExternalCSData
ElementClass/DemDataElementDataType) == UINT16_N) || ((Dem/Dem
DemDataElementDataType) == UINT16_N))}
Size –
Description Array data type definition for external data elements
Variation {(ecuc((Dem/DemGeneral/DemDataElementClass/DemExternalCSDataElementClass/DemData
ElementDataType) == ([S|U]INT[8|16|32]|FLOAT)_N) || ((Dem/DemGeneral/DemDataElement
Class/DemExternalSRDataElementClass/DemDataElementDataType) ==
([S|U]INT[8|16|32]|FLOAT)_N))}
c()
8.6.1.4 Dem_DTCOriginType
[SWS_Dem_00934] d

AUTOSAR CP R20-11
Name Dem_DTCOriginType
Kind Type
Derived from uint16
Range DEM_DTC_ORIGIN_PRIMARY_ 0x0001 Event information located in the
MEMORY primary memory
DEM_DTC_ORIGIN_MIRROR_ 0x0002 Event information located in the
MEMORY mirror memory
DEM_DTC_ORIGIN_ 0x0003 The Event information is located
PERMANENT_MEMORY in the permanent memory
DEM_DTC_ORIGIN_OBD_ 0x0004 Selects all memories which are
RELEVANT_MEMORY storing OBD events (specified by
configuration)
DEM_DTC_ORIGIN_ 0x01XX Event information located in the
USERDEFINED_ user defined memory, where XX is
MEMORY_<Name> the configured DemUserDefined
MemoryIdentifier in hexadecimal
and <Name> is the Short-Name
of the DemUserDefinedMemory.
Description This enum is used to define the location of the events. The definition and use of the different
memory types is OEM-specific.
Variation –
c()
8.6.1.5 Dem_DebouncingStateType
[SWS_Dem_01000] d
Name Dem_DebouncingStateType
Kind Bitfield
Derived from uint8
Elements Kind Name Mask Description
bit DEM_TEMPORARILY_ 0x01 Bit 0: Temporarily Defective
DEFECTIVE (corresponds to 0 < FDC < 127)
bit DEM_FINALLY_DEFECTIVE 0x02 Bit 1: finally Defective
(corresponds to FDC = 127)
bit DEM_TEMPORARILY_HEALED 0x04 Bit 2: temporarily healed
(corresponds to -128 < FDC < 0)
bit DEM_TEST_COMPLETE 0x08 Bit 3: Test complete
(corresponds to FDC = -128 or
FDC = 127)
bit DEM_DTR_UPDATE 0x10 Bit 4: DTR Update (= Test
complete && Debouncing
complete && enable conditions /
storage conditions fulfilled)
Description –
Variation –
5

AUTOSAR CP R20-11
4
c(RS_Diag_04105)
8.6.1.6 Dem_DebounceResetStatusType
[SWS_Dem_00927] d
Name Dem_DebounceResetStatusType
Kind Type
Derived from uint8
Range DEM_DEBOUNCE_STATUS_ 0x00 Freeze the internal debounce
FREEZE counter/timer.
DEM_DEBOUNCE_STATUS_ 0x01 Reset the internal debounce
RESET counter/timer.
0x02 - 0xFF reserved
Description This type contains all definitions to control an internal debounce counter/timer via the function
Dem_ResetEventDebounceStatus().
Variation –
c()
8.6.1.7 Dem_DTRControlType
[SWS_Dem_00941] d
Name Dem_DTRControlType
Kind Type
Derived from uint8
Range DEM_DTR_CTL_NORMAL 0x00 Values are reported and regarded
as valid test result
DEM_DTR_CTL_NO_MAX 0x01 Values are reported, but
maximum limit is not available (not
valid); upper limit value is ignored.
DEM DTR_CTL_NO_MIN 0x02 Values are reported, but minimum
limit is not available (not valid);
lower limit value is ignored.
DEM_DTR_CTL_RESET 0x03 Values are all ignored. External
representation will be all zeros as
initialized (e.g. after fault clear)
DEM DTR_CTL_INVISIBLE 0x04 Values are all ignored. This DTR
is treated for the external view
(tester) as if not integrated.
5

AUTOSAR CP R20-11
4
Description Control parameter for the interpretation of the reported test results.
Variation –
c()
8.6.1.8 Dem_EventIdType
[SWS_Dem_00925] d
Name Dem_EventIdType
Kind Type
Derived from uint16
Range 1..65535 – Internal identifier of a diagnostic
event Remark: 0 is not a valid
value
Description Identification of an event by assigned EventId. The EventId is assigned by the Dem. Example: 1
refers to monitor x, 2 refers to monitor y, etc.
Variation –
c()
8.6.1.9 Dem_EventStatusType
[SWS_Dem_00926] d
Name Dem_EventStatusType
Kind Type
Derived from uint8
DEM_EVENT_STATUS_PASSED 0x00 Monitor reports qualified test
result passed.
DEM_EVENT_STATUS_FAILED 0x01 Monitor reports qualified test
result failed.
DEM_EVENT_STATUS_ 0x02 Monitor reports non-qualified test
PREPASSED result pre-passed (debounced
Dem-internally).
DEM_EVENT_STATUS_ 0x03 Monitor reports non-qualified test
PREFAILED result pre-failed (debounced
Dem-internally).
DEM_EVENT_STATUS_FDC_ 0x04 Monitor triggers the storage of
THRESHOLD_REACHED ExtendedDataRecords and
FreezeFrames ON_FDC_
THRESHOLD.
5

AUTOSAR CP R20-11
4
Description This type contains all monitor test result values, which can be reported via Dem_SetEventStatus().
Variation –
c()
8.6.1.10 Dem_DTCFormatType
[SWS_Dem_00933] d
Name Dem_DTCFormatType
Kind Type
Derived from uint8
Range DEM_DTC_FORMAT_OBD 0 selects the 2-byte OBD DTC
format (refer to configuration
parameter DemObdDTC)
DEM_DTC_FORMAT_UDS 1 selects the 3-byte UDS DTC
format (refer to configuration
parameter DemUdsDTC)
DEM_DTC_FORMAT_J1939 2 selects the merged SPN + FMI to
3-byte J1939 DTC format (refer to
DemJ1939DTC)
Description This type is used to select the format of the DTC value.
Variation –
c(RS_Diag_04112)
8.6.1.11 Dem_InitMonitorReasonType
[SWS_Dem_00942] d
Name Dem_InitMonitorReasonType
Kind Type
Derived from uint8
Range DEM_INIT_MONITOR_CLEAR 0x01 Event was cleared and all internal
values and states are reset.
DEM_INIT_MONITOR_RESTART 0x02 Operation cycle of the event was
restarted.
DEM_INIT_MONITOR_ 0x03 Enable conditions or DTC settings
REENABLED re-enabled.
DEM_INIT_MONITOR_ 0x04 Storage condition reenabled.
STORAGE_REENABLED
5

AUTOSAR CP R20-11
4
Description (Re-)Initialization reason returned by the callback <Module>_DemInitMonitorFor<EventName>().
Variation –
c(RS_Diag_04063)
8.6.1.12 Dem_IumprDenomCondIdType
[SWS_Dem_00943] d
Name Dem_IumprDenomCondIdType
Kind Type
Derived from uint8
Range DEM_IUMPR_DEN_COND_ 0x02 Additional IUMPR denominator
COLDSTART condition "Cold Start"
DEM_IUMPR_DEN_COND_ 0x03 Additional IUMPR denominator
EVAP condition "EVAP"
DEM_IUMPR_DEN_ 0x04 Additional IUMPR denominator
COND_500MI condition "500 miles"
DEM_IUMPR_GENERAL_ 0x05 Individual denominators to
INDIVIDUAL_DENOMINATOR support different conditions than
the general denominator. It acts
on individual denominators and
allows a different condition to be
set than for the general
denominator. If the standard
individual denominator conditions
differ from the general
denominator conditions, they
typically differ by a "fueled engine"
criterion.
DEM_IUMPR_GENERAL_ 0x06 IUMPR denominator condition
OBDCOND "General Denominator" for output
with Infotype $08/$0B
Description This type contains all possible additional IUMPR denominator conditions to be broadcasted among
OBD-relevant ECUs.
Variation –
c()
8.6.1.13 Dem_IumprDenomCondStatusType
[SWS_Dem_00944] d

AUTOSAR CP R20-11
Name Dem_IumprDenomCondStatusType
Kind Type
Derived from uint8
Range DEM_IUMPR_DEN_STATUS_ 0x00 Condition of IUMPR-Denominator
NOT_REACHED given by IUMPRDenCondId is not
met (yet).
DEM_IUMPR_DEN_STATUS_ 0x01 Condition of IUMPR-Denominator
REACHED given by IUMPRDenCondId is met
DEM_IUMPR_DEN_STATUS_ 0x02 Condition of IUMPR-Denominator
INHIBITED given by IUMPRDenCondId is
inhibited and cannot be reached.
Description This type contains all possible states of an additional IUMPR denominator condition to be
broadcasted among OBD-relevant ECUs.
Variation –
c()
8.6.1.14 Dem_MaxDataValueType
[SWS_Dem_01072] d
Name Dem_MaxDataValueType
Kind Array Element type uint8
Size size of largest Extended data class / Freeze frame record Elements
Description –
Variation –
c()
8.6.1.15 Dem_MonitorDataType
[SWS_Dem_91036] d
Name Dem_MonitorDataType
Kind Type
Derived from uint32
Description This type is used to pass monitoring data to the Dem.
Variation –
c()

AUTOSAR CP R20-11
8.6.1.16 Dem_MonitorStatusType
[SWS_Dem_91005] d
Name Dem_MonitorStatusType
Kind Bitfield
Derived from uint8
bit DEM_MONITOR_STATUS_TF 0x01 Bit0: TestFailed
bit DEM_MONITOR_STATUS_ 0x02 Bit1: TestNotCompletedThis
TNCTOC OperationCycle
Description This type contains possible monitor status values.
Variation –
c()
8.6.1.17 Dem_IndicatorStatusType
[SWS_Dem_00930] d
Name Dem_IndicatorStatusType
Kind Type
Derived from uint8
Range DEM_INDICATOR_OFF 0x00 Indicator off mode
DEM_INDICATOR_ 0x01 Indicator continuously on mode
CONTINUOUS
DEM_INDICATOR_BLINKING 0x02 Indicator blinking mode
DEM_INDICATOR_BLINK_CONT 0x03 Indicator blinking or continuously
on mode
DEM_INDICATOR_SLOW_ 0x04 Indicator slow flashing mode
FLASH
DEM_INDICATOR_FAST_FLASH 0x05 Indicator fast flashing mode
DEM_INDICATOR_ON_DEMAND 0x06 Indicator on-demand mode
DEM_INDICATOR_SHORT 0x07 Indicator short mode
Description Indicator mode used by Dem_GetIndicatorStatus().
Variation –
c()
8.6.1.18 Dem_PID21valueType
[SWS_Dem_01073] d

AUTOSAR CP R20-11
Name Dem_PID21valueType
Size 2 Elements
Description –
Variation –
c()
8.6.1.19 Dem_PID31valueType
[SWS_Dem_01074] d
Name Dem_PID31valueType
Size 2 Elements
Description –
Variation –
c()
8.6.1.20 Dem_RatioIdType
[SWS_Dem_00940] d
Name Dem_RatioIdType
Kind Type
Derived from Basetype Variation
uint16 Configurable, size depends on system complexity (refer to
range of configuration parameter DemRatioId)
uint8 Configurable, size depends on system complexity (refer to
range of configuration parameter DemRatioId)
Range 0..255, 0..65535 – Configurable, size depends on
system complexity (refer to range
of configuration parameter Dem
RatioId)
Description OBD specific ratio Id (related to a specific event, a FID, and an IUMPR group). This type depends
on the Dem configuration.
Variation –
c()

AUTOSAR CP R20-11
8.6.1.21 Dem_UdsStatusByteType
[SWS_Dem_00928] d
Name Dem_UdsStatusByteType
Kind Bitfield
Derived from uint8
Lower limit 0x00
Upper limit 0xFF

bit DEM_UDS_STATUS_TF 0x01 bit 0: TestFailed
bit DEM_UDS_STATUS_TFTOC 0x02 bit 1: TestFailedThisOperation
Cycle
bit DEM_UDS_STATUS_PDTC 0x04 bit 2: PendingDTC
bit DEM_UDS_STATUS_CDTC 0x08 bit 3: ConfirmedDTC
bit DEM_UDS_STATUS_TNCSLC 0x10 bit 4: TestNotCompletedSince
LastClear
bit DEM_UDS_STATUS_TFSLC 0x20 bit 5: TestFailedSinceLastClear
bit DEM_UDS_STATUS_TNCTOC 0x40 bit 6: TestNotCompletedThis
OperationCycle
bit DEM_UDS_STATUS_WIR 0x80 bit 7: WarningIndicator
Requested
Description In this data-type each bit has an individual meaning. The bit is set to 1 when the condition holds.
For example, if the 2nd bit (0x02) is set to 1, this means that the test failed this operation cycle. If
the bit is set to 0, it has not yet failed this cycle.
Variation –
c()
8.6.1.22 Dem_PID4DvalueType
[SWS_Dem_91028] d
Name Dem_PID4DvalueType
Size 2 Elements
Description –
Variation ({ecuc(Dem/DemGeneral.DemOBDSupport)} == DEM_OBD_MASTER_ECU)
c()
8.6.1.23 Dem_PID4EvalueType
[SWS_Dem_91029] d

AUTOSAR CP R20-11
Name Dem_PID4EvalueType
Size 2 Elements
Description –
c()
8.6.2 Sender-Receiver-Interfaces
8.6.2.1 DataServices_{Data}
[SWS_Dem_00850] d
Name DataServices_{Data}
Comment –
IsService false
Variation ({ecuc(Dem/DemGeneral/DemDataElementClass)} instanceof {ecuc(Dem/DemGeneral/Dem
DataElementClass/DemExternalSRDataElementClass)})
Data Elements data
Type Dem_DataType_{Data}
Variation Data = {ecuc(Dem/DemGeneral/DemDataElementClass.SHORT-NAME)}
c()
8.6.3 Client-Server-Interfaces
8.6.3.1 CallbackClearEventAllowed
[SWS_Dem_00620] d
Name CallbackClearEventAllowed
Comment If configured, it gets the permission to clear a specific event from the SW-C. For each event,
there can be one port of this interface type.
IsService true
Variation –
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed

AUTOSAR CP R20-11
Operation ClearEventAllowed
Comment –
Variation –
Parameters Allowed
Type boolean
Direction OUT
Comment True - clearance of event is allowed
False - clearance of event is not allowed
Variation –
Possible Errors E_OK
E_NOT_OK
c(RS_Diag_04117)
8.6.3.2 CallbackComponentStatusChanged
[SWS_Dem_01195] d
Name CallbackComponentStatusChanged
Comment –
IsService true
Variation –
Possible Errors – – –
Operation ComponentStatusChanged
Comment –
Variation –
Parameters ComponentFailedStatus
Type boolean
Direction IN
Comment –
Variation –
Possible Errors –
c()
8.6.3.3 CallbackDTCStatusChange
[SWS_Dem_00617] d

AUTOSAR CP R20-11
Name CallbackDTCStatusChange
Comment If configured it triggers SW-Cs on DTC status byte changes via DemCallbackDTCStatus
Changed, DemCallbackOBDDTCStatusChanged, and / or DemCallbackJ1939DTCStatus
Changed. There can be several ports of this interface type, provided globally by the Dem
Service Component.
IsService true
Variation –
Operation DTCStatusChanged
Comment –
Variation –
DTC
Parameters
Type uint32
Direction IN
Comment –
Variation –
DTCStatusOld
Type Dem_UdsStatusByteType
Direction IN
Comment –
Variation –
DTCStatusNew
Direction IN
Comment –
Variation –
E_NOT_OK
c()
8.6.3.4 CallbackEventDataChanged
[SWS_Dem_00618] d
Name CallbackEventDataChanged
Comment If configured it triggers SW-Cs on event related data changes. For each event, there can be
one port of this interface type.
IsService true
Variation –

AUTOSAR CP R20-11
Operation EventDataChanged
Comment –
Variation –
Possible Errors –
c(RS_Diag_04155)
8.6.3.5 CallbackEventUdsStatusChanged
[SWS_Dem_00615] d
Name CallbackEventUdsStatusChanged
Comment If configured it triggers SW-Cs on event status byte changes. For each event, there can be
several ports of this interface type.
IsService true
Variation –
Operation CallbackEventUdsStatusChanged
Comment –
Variation –
EventStatusByteOld
Parameters
Direction IN
Comment –
Variation –
EventStatusByteNew
Direction IN
Comment –
Variation –
Possible Errors –
c()
8.6.3.6 CallbackGetFaultDetectCounter
[SWS_Dem_00622] d

AUTOSAR CP R20-11
Name CallbackGetFaultDetectCounter
Comment If configured it get the monitor-internal fault detection counter value of a specific event from the
SW-C.
IsService true
Variation –
Operation GetFaultDetectionCounter
Comment –
Variation –
Parameters FaultDetectionCounter
Type sint8
Direction OUT
Comment Value of FaultDetectionCounter
Variation –
E_NOT_OK
c()
8.6.3.7 CallbackInitMonitorForEvent
[SWS_Dem_00613] d
Name CallbackInitMonitorForEvent
Comment If configure it triggers an event-specific initialization of the monitor part of the SW-C). For each
event, there can be one port of this interface type.
IsService true
Variation –
Operation InitMonitorForEvent
Comment –
Variation –
Parameters InitMonitorReason
Type Dem_InitMonitorReasonType
Direction IN
Comment –
Variation –
E_NOT_OK
c(SRS_BSW_00457)

AUTOSAR CP R20-11
8.6.3.8 CallbackMonitorStatusChange
[SWS_Dem_91011] d
Name CallbackMonitorStatusChange
Comment If configured it triggers SW-Cs on monitor status changes. For each event, there can be several
ports of this interface type.
IsService true
Variation –
Operation MonitorStatusChanged
Comment –
Variation –
Possible Errors –
c()
[SWS_Dem_91003] d
Name ClearDtcNotification
Comment –
IsService true
Variation (count({ecuc(Dem/DemGeneral/DemEventMemorySet/DemClearDTCNotification/DemClear
DtcNotificationFnc)} == NULL) > 0)
Operation ClearDtcNotification
Comment –
Variation –
DTC
Type uint32
Direction IN
Comment –
Variation –
DTCFormat
Type Dem_DTCFormatType
Direction IN
Comment –
Variation –
DTCOrigin
5

AUTOSAR CP R20-11
4
Type Dem_DTCOriginType
Direction IN
Comment –
Variation –
c()
8.6.3.10 ClearDTC
[SWS_Dem_00666] d
Name ClearDTC
Comment Provides the operations only related to complex device drivers. One port of this interface type is
provided globally by the Dem Service Component. It has ClientId as a port-defined argument.
IsService true
Variation –
0 E_OK Operation successful
Possible Errors
4 DEM_PENDING Clearing the DTCs is currently in progress. The
5 DEM_CLEAR_BUSY Another client is currently clearing DTCs. The
requested operation will not be started and the caller
shall try again at a later moment.
6 DEM_CLEAR_ An error occurred during erasing a memory location
MEMORY_ERROR (e.g. if DemClearDTCBehavior is set to DEM_
CLRRESP_NON-VOLATILE_FINISH and erasing of
non-volatile-block failed).
7 DEM_CLEAR_FAILED DTC clearing failed
8 DEM_WRONG_DTC Selected DTC value in selected format does not
exist or clearing is restricted by configuration to
group of all DTCs only.
9 DEM_WRONG_ Selected DTCOrigin does not exist.
DTCORIGIN
22 DEM_BUSY A different Dem_SelectDTC dependent operation
according to SWS_Dem_01253 of this client is
currently in progress.
Operation ClearDTC
Comment –
Variation –
5

AUTOSAR CP R20-11
4
E_NOT_OK
DEM_PENDING
DEM_CLEAR_BUSY
DEM_CLEAR_MEMORY_ERROR
DEM_CLEAR_FAILED
DEM_WRONG_DTC
DEM_WRONG_DTCORIGIN
DEM_BUSY
Operation SelectDTC
Comment –
Variation –
DTC
Parameters
Type uint32
Direction IN
Comment –
Variation –
DTCFormat
Direction IN
Comment –
Variation –
DTCOrigin
Direction IN
Comment –
Variation –
E_NOT_OK
c()
8.6.3.11 DTCSuppression
[SWS_Dem_00608] d
Name DTCSuppression
Comment Provides the capability to control the suppression of DTCs. One port of this interface type is
provided globally by the Dem Service Component.
IsService true
Variation ({ecuc(Dem/DemGeneral/DemSuppressionSupport)} == DEM_DTC_SUPPRESSION)
0 E_OK Operation successful
5

AUTOSAR CP R20-11
4
4 DEM_PENDING Clearing the DTCs is currently in progress. The
8 DEM_WRONG_DTC Selected DTC value in selected format does not
exist or clearing is restricted by configuration to
group of all DTCs only.
9 DEM_WRONG_ Selected DTCOrigin does not exist.
DTCORIGIN
Operation GetDTCSuppression
Comment –
Variation –
ClientID
Parameters
Type uint8
Direction IN
Comment Unique client id, assigned to the instance of the calling module.
Variation –
SuppressionStatus
Type boolean
Direction OUT
Comment Defines whether the respective DTC is suppressed (TRUE) or enabled
(FALSE).
Variation –
E_NOT_OK
DEM_PENDING
DEM_WRONG_DTC
DEM_WRONG_DTCORIGIN
Operation SetDTCSuppression
Comment –
Variation –
ClientID
Parameters
Type uint8
Direction IN
Comment Unique client id, assigned to the instance of the calling module.
Variation –
SuppressionStatus
Type boolean
Direction IN
Comment –
Variation –
E_NOT_OK
DEM_WRONG_DTC
DEM_WRONG_DTCORIGIN
c()

AUTOSAR CP R20-11
[SWS_Dem_00621] d
Comment If configured it gets the data element value contained in a DID, a PID, or an extended data
record from the respective SW-C via client/server or sender/receiver communication (refer to
Figure "Dem and Dcm module requests PID data elements of SW-C via ReadData operation").
For each data element, one port of this interface type is provided by the SW-Cs.
IsService true
Variation (({ecuc(Dem/DemGeneral/DemDataElementClass)} instanceof {ecuc(Dem/DemGeneral/Dem
DataElementClass/DemExternalCSDataElementClass)})&& ({ecuc(Dem/DemGeneral/Dem
DataElementClass/DemExternalCSDataElementClass/DemDataElementUsePort)} == true))
Operation ReadData
Comment The server is not allowed to return E_NOT_OK, but shall always provide a valid data value (e.g.
a default/replacement value in an error-case) to Dcm/Dem nevertheless the signature of the
operation includes E_NOT_OK to ensure compatibility between server runnable and RTE Call
API, since the RTE may return negative Std_Return values in certain cases (e.g. partition of
server stopped)
Variation –
Data
Parameters
Type Dem_DataType_{Data}
Direction OUT
Comment –
Variation Data = {ecuc(Dem/DemGeneral/DemDataElementClass.SHORT-NAME)}
monitorData0
Type Dem_MonitorDataType
Direction IN
Comment –
Variation ({ecuc(Dem/DemGeneral/DemDataElementClass/DemExternalCSData
ElementClass/DemDataElementProvideMonitorData)} == true))
E_NOT_OK
c()
8.6.3.13 DTRCentralReport
[SWS_Dem_00769] d

AUTOSAR CP R20-11
Name DTRCentralReport
Comment Available if OBD support is configured.
IsService true
Variation –
Operation SetDTR
Comment –
Variation –
TestResult
Parameters Type sint32
Direction IN
Comment –
Variation –
LowerLimit
Type sint32
Direction IN
Comment –
Variation –
UpperLimit
Type sint32
Direction IN
Comment –
Variation –
Ctrlval
Type Dem_DTRControlType
Direction IN
Comment –
Variation –
E_NOT_OK
c()
Note: The Dem- and Dcm-interfaces of this type are compatible, to be connected to
the same provide-port of the application.
Note: The Dem Service Component supports synchronous client/server in-
terfaces only (due to the used mechanisms for the event memory) and is
compatible with the Dcm interface DataServices_<Data> with the setting for
USE_DATA_SYNCH_CLIENT_SERVER. All further operations contained in the Dcm
interface CSDataServices_<Data> like WriteData, ReadDataLength (relates to data
elements with a variable length), ConditionCheckRead, etc. are provided by the SW-C
and used by the Dcm, but are not required/considered by the Dem module.
Note: The Dem Service Component is compatible with the Dcm interface DataSer-
vices_<Data> with the setting for USE_DATA_SENDER_RECEIVER.

AUTOSAR CP R20-11
8.6.3.14 DiagnosticInfo
[SWS_Dem_00599] d
Name DiagnosticInfo
Comment Provides the capability to obtain the event information. One port of this interface type is
provided per diagnostic event by the Dem Service Component. It has EventId as a port-defined
argument.
IsService true
Variation –
10 DEM_E_NO_DTC_ there is no DTC configured in the requested format
AVAILABLE
14 DEM_E_NO_FDC_ there is no fault detection counter available for the
AVAILABLE requested event
21 DEM_BUFFER_TOO_ The provided buffer size is too small
SMALL
48 DEM_NO_SUCH_ The requested event data is not currently stored (but
ELEMENT the request was valid) OR The requested record
number is not supported by the event OR The
requested DID is not supported by the freeze frame
(GetEventFreezeFrameDataEx)
Operation GetDTCOfEvent
Comment –
Variation –
DTCFormat
Parameters
Direction IN
Comment –
Variation –
DTCOfEvent
Type uint32
Direction OUT
Comment –
Variation –
E_NOT_OK
DEM_E_NO_DTC_AVAILABLE
Operation GetDebouncingOfEvent
Comment –
Variation (({ecuc(Dem/DemConfigSet/DemEventParameter/DemDebounceAlgorithmClass)} instanceof
{ecuc(Dem/DemConfigSet/DemEventParameter/DemDebounceAlgorithmClass/DemDebounce
CounterBased)}) ||({ecuc(Dem/DemConfigSet/DemEventParameter/DemDebounceAlgorithm
Class)} instanceof {ecuc(Dem/DemConfigSet/DemEventParameter/DemDebounceAlgorithm
Class/DemDebounceTimeBase)}))
Parameters DebouncingState
5

AUTOSAR CP R20-11
4
Type Dem_DebouncingStateType
Direction OUT
Comment Bit 0 Temporarily Defective (corresponds to 0 < FDC < 127)
Bit 1 finally Defective (corresponds to FDC = 127)
Bit 2 temporarily healed (corresponds to -128 < FDC < 0)
Bit 3 Test complete (corresponds to FDC = -128 or FDC = 127)
Bit 4 DTR Update (= Test complete && Debouncing complete && enable
conditions / storage conditions fulfilled)
Variation –
E_NOT_OK
Operation GetEventAvailable
Comment –
Variation –
Parameters AvailableStatus
Type boolean*
Direction OUT
Comment TRUE if the event is available. FALSE if the event is not available.
Variation –
E_NOT_OK
Operation GetEventExtendedDataRecordEx
Comment –
Variation –
RecordNumber
Parameters
Type uint8
Direction IN
Comment –
Variation –
DestBuffer
Type Dem_MaxDataValueType
Direction OUT
Comment –
Variation –
Bufsize
Type uint16
Direction INOUT
Comment –
Variation –
E_NOT_OK
DEM_BUFFER_TOO_SMALL
DEM_NO_SUCH_ELEMENT

AUTOSAR CP R20-11
Operation GetEventFreezeFrameDataEx
Comment –
Variation –
RecordNumber
Parameters Type uint8
Direction IN
Comment –
Variation –
DataId
Type uint16
Direction IN
Comment –
Variation –
DestBuffer
Direction OUT
Comment –
Variation –
BufSize
Type uint16
Direction INOUT
Comment –
Variation –
E_NOT_OK
DEM_NO_SUCH_ELEMENT
Operation GetEventUdsStatus
Comment Gets the current UDS status byte assigned to the DTC for the event
Variation –
Parameters UDSStatusByte
Direction OUT
Comment –
Variation –
E_NOT_OK
Comment –
Variation –
FaultDetectionCounter
Type sint8
Direction OUT
5

AUTOSAR CP R20-11
4
Comment –
Variation –
E_NOT_OK
DEM_E_NO_FDC_AVAILABLE
Operation GetMonitorStatus
Comment –
Variation –
Parameters MonitorStatus
Type Dem_MonitorStatusType
Direction OUT
Comment Monitor status byte of the requested event. If the return value of the function
call is E_NOT_OK, this parameter does not contain valid data.
Variation –
E_NOT_OK
c()
Note: These DiagnosticInfo ports are also available for each BSW event (so that also
SW-Cs can access on).
8.6.3.15 DiagnosticMonitor
[SWS_Dem_00598] d
Name DiagnosticMonitor
Comment Provide the capability to modify the event information. One port of this interface type is
provided per application-related diagnostic event by the Dem Service Component. It has Event
Id as a port-defined argument.
IsService true
Variation (({Dem/DemGeneral/DemStorageCondition.DemStorageConditionReplacementEvent
Ref})!=({Dem/DemConfigSet/DemEventParameter}) && ({Dem/DemConfigSet/DemEvent
Parameter/DemEventReportingType} == STANDARD_REPORTING))
Operation ClearPrestoredFreezeFrame
Comment –
Variation {ecuc(Dem/DemGeneral/DemMaxNumberPrestoredFF)} > 0
E_NOT_OK

AUTOSAR CP R20-11
Operation PrestoreFreezeFrame
Comment –
Variation {ecuc(Dem/DemGeneral/DemMaxNumberPrestoredFF)} > 0
E_NOT_OK
Operation ResetEventDebounceStatus
Comment –
Variation ({ecuc(Dem/DemGeneral/DemDebounceCounterBasedSupport)} == true) || ({ecuc(Dem/Dem
General/DemDebounceTimeBasedSupport)} == true)
Parameters DebounceResetStatus
Type Dem_DebounceResetStatusType
Direction IN
Comment –
Variation –
E_NOT_OK
Operation ResetEventStatus
Comment –
Variation –
E_NOT_OK
Operation SetEventDisabled
Comment –
Variation {ecuc(Dem/DemGeneral.DemOBDSupport)} != DEM_OBD_NO_OBD_SUPPORT
E_NOT_OK
Operation SetEventStatus
Comment –
Variation –
Parameters EventStatus
Type Dem_EventStatusType
Direction IN
Comment –
Variation –
E_NOT_OK
c()
Note: Each port of the DiagnosticMonitor interface is only connected to one monitor
port.
Note: For internally used events (replacement event), no port will be generated.

AUTOSAR CP R20-11
Caveat: all operations within this client/server interface are mutual exclusive per server
port (same eventId). Preempted invocations may be ignored and not processed by the
Dem.
8.6.3.16 DiagnosticMonitor_MonitorData
[SWS_Dem_91038] d
Name DiagnosticMonitor_MonitorData
Comment Provide means to report diagnostic monitor status with monitor data.
IsService true
Variation ({Dem/DemConfigSet/DemEventParameter/DemEventReportingType} == STANDARD_
REPORTING_WITH_MONITOR_DATA)
Operation SetEventStatusWithMonitorData
Comment –
Variation –
EventStatus
Parameters
Type Dem_EventStatusType
Direction IN
Comment –
Variation –
monitorData0
Direction IN
Comment –
Variation –
monitorData1
Direction IN
Comment –
Variation –
E_NOT_OK
c()
8.6.3.17 EnableCondition
[SWS_Dem_00604] d

AUTOSAR CP R20-11
Name EnableCondition
Comment If at least one enable condition is configured it provide the capability to set an enable condition.
One port of this interface type is provided per enable condition by the Dem Service
Component. It has EnableConditionId as a port-defined argument.
IsService true
Variation –
Operation SetEnableCondition
Comment –
Variation –
Parameters ConditionFulfilled
Type boolean
Direction IN
Comment –
Variation –
E_NOT_OK
c(RS_Diag_04192)
8.6.3.18 EventAvailable
[SWS_Dem_01193] d
Name EventAvailable
Comment –
IsService true
Variation {ecuc(Dem/DemGeneral/DemAvailabilitySupport)} == DEM_EVENT_AVAILABILITY
Operation SetEventAvailable
Comment –
Variation –
Parameters AvailableStatus
Type boolean
Direction IN
Comment –
Variation –
E_NOT_OK
c()

AUTOSAR CP R20-11
8.6.3.19 EventFailureCycleCounterThreshold
[SWS_Dem_91018] d
Name EventFailureCycleCounterThreshold
Comment Provides the capability for dynamical adaptation of the failure cycle threshold. One port of this
interface is provided per diagnostic event with EventId as a port-defined argument.
IsService true
Variation (count({ecuc(Dem/DemConfigSet/DemEventParameter/DemEventConfirmationThreshold
CounterAdaptable)} == TRUE) > 0 )
Operation SetEventFailureCycleCounterThreshold
Comment –
Variation –
Parameters FailureCycleCounterThreshold
Type uint8
Direction IN
Comment Failure cycle counter threshold of event to be set.
Variation –
E_NOT_OK
c()
8.6.3.20 EvMemOverflowIndication
[SWS_Dem_00607] d
Name EvMemOverflowIndication
Comment If the respective event memory is configured it provides the status of the event memory). One
port of this interface type is provided per supported event memory by the Dem Service
Component. It has DTCOrigin as a port-defined argument.
IsService true
Variation –
Operation GetEventMemoryOverflow
Comment –
Variation –
Parameters OverflowIndication
5

AUTOSAR CP R20-11
4
Type boolean
Direction OUT
Comment –
Variation –
E_NOT_OK
Operation GetNumberOfEventMemoryEntries
Comment –
Variation –
Parameters GetNumberOfEventMemoryEntries
Type uint8
Direction OUT
Comment –
Variation –
E_NOT_OK
c(RS_Diag_04105)
8.6.3.21 EventStatus
[SWS_Dem_00838] d
Name EventStatus
Comment Provides the capability modify the event status. One port of this interface type is provided per
application-related diagnostic event by the Dem Service Component. It has EventId as a
port-defined argument.
IsService true
Variation –
Operation SetWIRStatus
Comment –
Variation –
Parameters WIRStatus
Type boolean
Direction IN
Comment –
Variation –
E_NOT_OK
c()

AUTOSAR CP R20-11
Note: Each port of the EventStatus interface is only connected to one port of the
failsafe SW-C.
8.6.3.22 GeneralCallbackEventDataChanged
[SWS_Dem_00619] d
Name GeneralCallbackEventDataChanged
Comment –
IsService true
Variation –
Operation EventDataChanged
Comment –
Variation –
Parameters EventId
Type Dem_EventIdType
Direction IN
Comment –
Variation –
Possible Errors –
c(RS_Diag_04155)
8.6.3.23 GeneralCallbackEventUdsStatusChanged
[SWS_Dem_00616] d
Name GeneralCallbackEventUdsStatusChanged
Comment –
IsService true
Variation –
Operation GeneralCallbackEventUdsStatusChanged
Comment –
Variation –
EventId
Direction IN
5

AUTOSAR CP R20-11
4
Comment –
Variation –
EventStatusByteOld
Direction IN
Comment –
Variation –
EventStatusByteNew
Direction IN
Comment –
Variation –
Possible Errors –
c()
8.6.3.24 GeneralCallbackMonitorStatusChanged
[SWS_Dem_91013] d
Name GeneralCallbackMonitorStatusChanged
Comment –
IsService true
Variation –
Operation MonitorStatusChanged
Comment –
Variation –
Parameters EventId
Direction IN
Comment –
Variation –
Possible Errors –
c()
8.6.3.25 GeneralDiagnosticInfo
[SWS_Dem_00600] d

AUTOSAR CP R20-11
Name GeneralDiagnosticInfo
Comment –
IsService true
Variation –
10 DEM_E_NO_DTC_ there is no DTC configured in the requested format
AVAILABLE
14 DEM_E_NO_FDC_ there is no fault detection counter available for the
AVAILABLE requested event
21 DEM_BUFFER_TOO_ The provided buffer size is too small
SMALL
48 DEM_NO_SUCH_ The requested event data is not currently stored (but
ELEMENT the request was valid) OR The requested record
number is not supported by the event OR The
requested DID is not supported by the freeze frame
(GetEventFreezeFrameDataEx)
Operation GetDTCOfEvent
Comment –
Variation –
EventId
Parameters
Direction IN
Comment –
Variation –
DTCFormat
Direction IN
Comment –
Variation –
DTCOfEvent
Type uint32
Direction OUT
Comment –
Variation –
E_NOT_OK
DEM_E_NO_DTC_AVAILABLE
Operation GetDebouncingOfEvent
Comment –
Variation (({ecuc(Dem/DemConfigSet/DemEventParameter/DemDebounceAlgorithmClass)} instanceof
{ecuc(Dem/DemConfigSet/DemEventParameter/DemDebounceAlgorithmClass/DemDebounce
CounterBased)}) ||({ecuc(Dem/DemConfigSet/DemEventParameter/DemDebounceAlgorithm
Class)} instanceof {ecuc(Dem/DemConfigSet/DemEventParameter/DemDebounceAlgorithm
Class/DemDebounceTimeBase)}))
Parameters EventId
5

AUTOSAR CP R20-11
4
Direction IN
Comment –
Variation –
DebouncingState
Type Dem_DebouncingStateType
Direction OUT
Comment Bit 0 Temporarily Defective (corresponds to 0 < FDC < 127)
Bit 1 finally Defective (corresponds to FDC = 127)
Bit 2 temporarily healed (corresponds to -128 < FDC < 0)
Bit 3 Test complete (corresponds to FDC = -128 or FDC = 127)
Bit 4 DTR Update (= Test complete && Debouncing complete && enable
conditions / storage conditions fulfilled)
Variation –
E_NOT_OK
Operation GetEventExtendedDataRecordEx
Comment –
Variation –
EventId
Parameters Type Dem_EventIdType
Direction IN
Comment –
Variation –
RecordNumber
Type uint8
Direction IN
Comment –
Variation –
DestBuffer
Direction OUT
Comment –
Variation –
Bufsize
Type uint16
Direction INOUT
Comment –
Variation –
E_NOT_OK
DEM_NO_SUCH_ELEMENT

AUTOSAR CP R20-11
Operation GetEventFreezeFrameDataEx
Comment –
Variation –
EventId
Parameters Type Dem_EventIdType
Direction IN
Comment –
Variation –
RecordNumber
Type uint8
Direction IN
Comment –
Variation –
DataId
Type uint16
Direction IN
Comment –
Variation –
DestBuffer
Direction OUT
Comment –
Variation –
BufSize
Type uint16
Direction INOUT
Comment –
Variation –
E_NOT_OK
DEM_NO_SUCH_ELEMENT
Operation GetEventUdsStatus
Comment Gets the current UDS status byte assigned to the DTC for the event
Variation –
EventId
Parameters
Direction IN
Comment –
Variation –
UDSStatusByte
Direction OUT
Comment –
Variation –
5

AUTOSAR CP R20-11
4
E_NOT_OK
Comment –
Variation –
EventId
Parameters
Direction IN
Comment –
Variation –
FaultDetectionCounter
Type sint8
Direction OUT
Comment –
Variation –
E_NOT_OK
DEM_E_NO_FDC_AVAILABLE
Operation GetMonitorStatus
Comment –
Variation –
EventID
Parameters
Direction IN
Comment Identification of an event by assigned EventId.
Variation –
MonitorStatus
Type Dem_MonitorStatusType
Direction OUT
Comment Monitor status byte of the requested event. If the return value of the function
call is E_NOT_OK, this parameter does not contain valid data.
Variation –
E_NOT_OK
c()
8.6.3.26 GetDataOfPID21
[SWS_Dem_01092] d

AUTOSAR CP R20-11
Name GetDataOfPID21
Comment –
IsService true
Variation –
Operation GetDataOfPID21
Comment –
Variation –
Parameters PID21value
Type Dem_PID21valueType
Direction OUT
Comment –
Variation –
E_NOT_OK
c()
8.6.3.27 IndicatorStatus
[SWS_Dem_00606] d
Name IndicatorStatus
Comment One port of this interface type is provided per indicator by the Dem Service Component. It has
IndicatorId as a port-defined argument.
IsService true
Variation –
Operation GetIndicatorStatus
Comment –
Variation –
Parameters IndicatorStatus
Type Dem_IndicatorStatusType
Direction OUT
Comment –
Variation –
E_NOT_OK
c()

AUTOSAR CP R20-11
8.6.3.28 IUMPRDenominator
[SWS_Dem_00611] d
Name IUMPRDenominator
Comment If OBD is configured it provides the capability to define the number of times the vehicle
operation has been fulfilled. One port of this interface type is provided per ratio Id by the Dem
Service Component. It has RatioID as a port-defined argument.
IsService true
Variation –
Operation RepIUMPRDenRelease
Comment –
Variation –
E_NOT_OK
c()
8.6.3.29 IUMPRDenominatorCondition
[SWS_Dem_00742] d
Name IUMPRDenominatorCondition
Comment If OBD is configured it broadcasts the status information of the General Denominator and
additional denominator conditions among all OBD relevant ECUs. One port of this interface
type is provided per denominator condition Id by the Dem Service Component. It has Dem_
IumprDenomCondId as a port-defined argument.
IsService true
Variation –
Operation GetIUMPRDenCondition
Comment –
Variation –
Parameters ConditionStatus
Type Dem_IumprDenomCondStatusType
Direction OUT
Comment –
Variation –
E_NOT_OK

AUTOSAR CP R20-11
Operation SetIUMPRDenCondition
Comment –
Variation –
Parameters ConditionStatus
Type Dem_IumprDenomCondStatusType
Direction IN
Comment –
Variation –
E_NOT_OK
c()
8.6.3.30 IUMPRNumerator
[SWS_Dem_00610] d
Name IUMPRNumerator
Comment If OBD is configured it provides the capability to define the number of times a fault could have
been found. One port of this interface type is provided per ratio Id by the Dem Service
Component. It has RatioID as a port-defined argument.
IsService true
Variation –
Operation RepIUMPRFaultDetect
Comment –
Variation –
E_NOT_OK
c()
8.6.3.31 OperationCycle
[SWS_Dem_00601] d
Name OperationCycle
Comment Provides the capability to set the state of an operation cycle. One port of this interface type is
provided per operation cycle by the Dem Service Component. It has OperationCycleId as a
port-defined argument.
5

AUTOSAR CP R20-11
4
IsService true
Variation –
Operation GetCycleQualified
Comment –
Variation –
Parameters isQualified
Type boolean
Direction OUT
Comment –
Variation –
E_NOT_OK
Operation RestartOperationCycle
Comment –
Variation –
E_NOT_OK
Operation SetCycleQualified
Comment –
Variation –
E_NOT_OK
c()
8.6.3.32 PowerTakeOff
[SWS_Dem_00612] d
Name PowerTakeOff
Comment Available if OBD support is configured. One port of this interface type is provided by the Dem
Service Component.
IsService true
Variation –

AUTOSAR CP R20-11
Operation SetPtoStatus
Comment –
Variation –
Parameters PtoStatus
Type boolean
Direction IN
Comment –
Variation –
E_NOT_OK
c()
8.6.3.33 SetDataOfPID21
[SWS_Dem_00745] d
Name SetDataOfPID21
Comment –
IsService true
Variation –
Operation SetDataOfPID21
Comment –
Variation –
Direction IN
Comment –
Variation –
E_NOT_OK
c()
[SWS_Dem_00746] d

AUTOSAR CP R20-11
Name SetDataOfPID31
Comment –
IsService true
Variation –
Operation SetDataOfPID31
Comment –
Variation –
Direction IN
Comment –
Variation –
E_NOT_OK
c()
8.6.3.35 SetDataOfPID4D
[SWS_Dem_91027] d
Name SetDataOfPID4D
Comment –
IsService true
Variation –
Operation SetDataOfPID4D
Comment –
Variation –
Parameters PID4Dvalue
Type Dem_PID4DvalueType
Direction IN
Comment –
Variation –
c()

AUTOSAR CP R20-11
8.6.3.36 SetDataOfPID4E
[SWS_Dem_91031] d
Name SetDataOfPID4E
Comment –
IsService true
Variation –
Operation SetDataOfPID4E
Comment –
Variation –
Parameters PID4Evalue
Type Dem_PID4EvalueType
Direction IN
Comment –
Variation –
c()
8.6.3.37 StorageCondition
[SWS_Dem_00605] d
Name StorageCondition
Comment Provides the capability to set a storage condition if at least one storage condition is configured.
One port of this interface type is provided per storage condition by the Dem Service
Component. It has StorageConditionId as a port-defined argument.
IsService true
Variation –
Operation SetStorageCondition
Comment –
Variation –
ConditionFulfilled
Type boolean
Direction IN
Comment This parameter specifies whether the enable condition assigned to the Enable
ConditionID is fulfilled (TRUE) or not fulfilled (FALSE).
5

AUTOSAR CP R20-11
4
Variation –
E_NOT_OK
c(RS_Diag_04219)
8.6.4 Ports
8.6.4.1 CBClrEvt
[SWS_Dem_91024] d
Name CBClrEvt_{Name}
Kind RequiredPort Interface CallbackClearEventAllowed
Description –
Variation (({ecuc(Dem/DemConfigSet/DemEventParameter/DemCallbackClearEventAllowed)} != NULL)
&&({ecuc(Dem/DemConfigSet/DemEventParameter/DemCallbackClearEventAllowed/Dem
CallbackClearEventAllowedFnc)} == NULL))
Name = {ecuc(Dem/DemConfigSet/DemEventParameter/DemCallbackClearEvent
Allowed.SHORT-NAME)}
c()
8.6.4.2 CBDataEvt
[SWS_Dem_01003] d
Name CBDataEvt_{Name}
Kind RequiredPort Interface CallbackEventDataChanged
Description –
Variation (({ecuc(Dem/DemConfigSet/DemEventParameter/DemCallbackEventDataChanged)} != NULL)
&&({ecuc(Dem/DemConfigSet/DemEventParameter/DemCallbackEventDataChanged/Dem
CallbackEventDataChangedFnc)} == NULL))
Name = {ecuc(Dem/DemConfigSet/DemEventParameter.SHORT-NAME)}
c(RS_Diag_04155)
8.6.4.3 CBFaultDetectCtr
[SWS_Dem_01004] d

AUTOSAR CP R20-11
Name CBFaultDetectCtr_{Name}
Kind RequiredPort Interface CallbackGetFaultDetectCounter
Description –
Variation ({ecuc(Dem/DemConfigSet/DemEventParameter/DemDebounceAlgorithmClass/DemDebounce
MonitorInternal/DemCallbackGetFDC/DemCallbackGetFDCFnc)} == NULL)
Name = {ecuc(Dem/DemConfigSet/DemEventParameter/DemDebounceAlgorithmClass/Dem
DebounceMonitorInternal/DemCallbackGetFDC.SHORT-NAME)}
c(RS_Diag_04125)
8.6.4.4 CBInitEvt
[SWS_Dem_01005] d
Name CBInitEvt_{Name}
Kind RequiredPort Interface CallbackInitMonitorForEvent
Description –
Variation (({ecuc(Dem/DemConfigSet/DemEventParameter/DemCallbackInitMForE)} != NULL)
&&({ecuc(Dem/DemConfigSet/DemEventParameter/DemCallbackInitMForE/DemCallbackInitMFor
EFnc)} == NULL))
c(SRS_BSW_00457)
8.6.4.5 CBStatusDTC
[SWS_Dem_01007] d
Name CBStatusDTC_{Name}
Kind RequiredPort Interface CallbackDTCStatusChange
Description –
Variation Name = {ecuc(Dem/DemGeneral/DemClient/DemCallbackDTCStatusChanged.SHORT-NAME)}
c()
8.6.4.6 CBEventUdsStatusChanged
[SWS_Dem_01008] d

AUTOSAR CP R20-11
Name CBEventUdsStatusChanged_{EventName}_{CallbackName}
Kind RequiredPort Interface CallbackEventUdsStatusChanged
Description –
Variation EventName = {ecuc(Dem/DemConfigSet/DemEventParameter.SHORT-NAME)}
CallbackName = {ecuc(Dem/DemConfigSet/DemEventParameter/DemCallbackEventUdsStatus
Changed.SHORT-NAME)}
c()
8.6.4.7 CBMonitorStatusChanged
[SWS_Dem_91012] d
Name CBMonitorStatusChanged_{EventName}_{CallbackName}
Kind RequiredPort Interface CallbackMonitorStatusChange
Description –
Variation ({ecuc(Dem/DemConfigSet/DemEventParameter.DemEventKind)} == DEM_EVENT_KIND_SWC)
EventName = {ecuc(Dem/DemConfigSet/DemEventParameter.SHORT-NAME)}
CallbackName = {ecuc(Dem/DemConfigSet/DemEventParameter/DemCallbackMonitorStatus
Changed.SHORT-NAME)}
c()
8.6.4.8 CBStatusComp
[SWS_Dem_01197] d
Name CBStatusComp_{ComponentName}
Kind RequiredPort Interface CallbackComponentStatusChanged
Description –
Variation ({ecuc(Dem/DemConfigSet/DemComponent.DemComponentFailedCallbackUsePort )}== TRUE)
ComponentName = {ecuc(Dem/DemConfigSet/DemComponent.SHORT-NAME)}
c()
8.6.4.9 ClearDTC
[SWS_Dem_01009] d

AUTOSAR CP R20-11
Name ClearDTC_{Client}
Kind ProvidedPort Interface ClearDTC
Description –
Port Defined Type uint8
Argument Value(s)
Value {ecuc(Dem/DemGeneral/DemClient.Short-Name)}
Variation ({ecuc(Dem/DemGeneral/DemClient/DemClientUsesRte)}==True) && ({ecuc(Dem/DemGeneral/
DemClient/DemClientFunctionality)} == DEM_CLIENT_USES_FULL_FUNCTIONALITY)
Client = {ecuc(Dem/DemGeneral/DemClient.SHORT-NAME)}
c()
[] d
Name ClearDtcNotification_{EventMemorySet}_{Notification}
Kind ProvidedPort Interface ClearDtcNotification
Description called by the Dem when performing a clear DTC operation
Variation ({ecuc(Dem/DemGeneral/DemEventMemorySet/DemClearDTCNotification/DemClearDtc
NotificationFnc)}== NULL)
EventMemorySet = {ecuc(Dem/DemGeneral/DemEventMemorySet.SHORT-NAME)}
Notification = {ecuc(Dem/DemGeneral/DemEventMemorySet/DemClear
DTCNotification.SHORT-NAME)}
c()
8.6.4.11 ControlDTCSuppression
[SWS_Dem_01010] d
Name ControlDTCSuppression
Kind ProvidedPort Interface DTCSuppression
Description –
Variation ({ecuc(Dem/DemGeneral/DemSuppressionSupport)} == DEM_DTC_SUPPRESSION)
c()
8.6.4.12 ControlEventAvailable
[SWS_Dem_01011] d

AUTOSAR CP R20-11
Name ControlEventAvailable
Kind ProvidedPort Interface EventAvailable
Description –
Port Defined Type Dem_EventIdType
Argument Value(s)
Value {ecuc(Dem/DemConfigSet/DemEventParameter/DemEventId.value)}
Variation {ecuc(Dem/DemGeneral/DemAvailabilitySupport)} == DEM_EVENT_AVAILABILITY
c()
8.6.4.13 ControlEventFailureCycleCounterThreshold
[SWS_Dem_91019] d
Name ControlEventFailureCycleCounterThreshold_{Name}
Kind ProvidedPort Interface EventFailureCycleCounterThreshold
Description –
Argument Value(s)
Variation {ecuc(Dem/DemConfigSet/DemEventParameter/DemEventConfirmationThresholdCounter
Adaptable)} == TRUE
c()
[SWS_Dem_01012] d
Kind RequiredPort Interface –
Description –
Variation (({ecuc(Dem/DemGeneral/DemDataElementClass)} instanceof {ecuc(Dem/DemGeneral/DemData
ElementClass/DemExternalCSDataElementClass)})&& ({ecuc(Dem/DemGeneral/DemData
ElementClass/DemExternalCSDataElementClass/DemDataElementUsePort)} == TRUE))||
({ecuc(Dem/DemGeneral/DemDataElementClass)} instanceof {ecuc(Dem/DemGeneral/DemData
ElementClass/DemExternalSRDataElementClass)})
c()
8.6.4.15 DTR
[SWS_Dem_01039] d

AUTOSAR CP R20-11
Name DTR_{Name}
Kind ProvidedPort Interface DTRCentralReport
Description –
Argument Value(s)
Value {ecuc(Dem/DemConfigSet/DemDtrs/DemDtr/DemDtrId.value)}
Variation ({ecuc(Dem/DemGeneral.DemOBDSupport)} != DEM_OBD_NO_OBD_SUPPORT)
Name = {ecuc(Dem/DemConfigSet/DemDtrs/DemDtr.SHORT-NAME)}
c()
8.6.4.16 EnableCond
[SWS_Dem_01038] d
Name EnableCond_{Name}
Kind ProvidedPort Interface EnableCondition
Description –
Argument Value(s)
Value {ecuc(Dem/DemGeneral/DemEnableCondition/DemEnableConditionId.value)}
Variation Name = {ecuc(Dem/DemGeneral/DemEnableCondition.SHORT-NAME)}
c(RS_Diag_04192)
8.6.4.17 Event
[SWS_Dem_01037] d
Name Event_{Name}
Kind ProvidedPort Interface DiagnosticMonitor
Description –
Argument Value(s)
Variation Name = {ecuc(Dem/DemConfigSet/DemEventParameter.SHORT-NAME)}
c(RS_Diag_04063)
8.6.4.18 DiagnosticMonitor_MonitorData
[SWS_Dem_91039] d

AUTOSAR CP R20-11
Name DiagnosticMonitor_MonitorData_{Name}
Kind ProvidedPort Interface DiagnosticMonitor_MonitorData
Description –
Argument Value(s)
c()
8.6.4.19 EventStatus
[SWS_Dem_01036] d
Name EventStatus_{Name}
Kind ProvidedPort Interface EventStatus
Description –
Argument Value(s)
c()
8.6.4.20 EventInfo
[SWS_Dem_01034] d
Name EventInfo_{Name}
Kind ProvidedPort Interface DiagnosticInfo
Description –
Argument Value(s)
c(RS_Diag_04063)
8.6.4.21 GeneralCBDataEvt
[SWS_Dem_01041] d

AUTOSAR CP R20-11
Name GeneralCBDataEvt
Kind RequiredPort Interface GeneralCallbackEventDataChanged
Description –
Variation ({ecuc(Dem/DemGeneral/DemGeneralInterfaceSupport)} == True)
c()
8.6.4.22 GeneralCBMonitorStatusChanged
[SWS_Dem_91014] d
Name GeneralCBMonitorStatusChanged
Kind RequiredPort Interface GeneralCallbackMonitorStatusChanged
Description –
c()
8.6.4.23 GeneralCBStatusEvt
[SWS_Dem_01032] d
Name GeneralCBStatusEvt
Kind RequiredPort Interface GeneralCallbackEventUdsStatusChanged
Description –
c()
8.6.4.24 GeneralEvtInfo
[SWS_Dem_01031] d
Name GeneralEvtInfo
Kind ProvidedPort Interface GeneralDiagnosticInfo
Description –
c()

AUTOSAR CP R20-11
8.6.4.25 IndStatus
[SWS_Dem_01030] d
Name IndStatus_{Name}
Kind ProvidedPort Interface IndicatorStatus
Description –
Argument Value(s)
Value {ecuc(Dem/DemGeneral/DemEventMemorySet/DemIndicator/DemIndicator
ID.value)}
Variation Name = {ecuc(Dem/DemGeneral/DemEventMemorySet/DemIndicator.SHORT-NAME)}
c()
8.6.4.26 IUMPRDenominator
[SWS_Dem_01029] d
Name IUMPRDenominator_{Name}
Kind ProvidedPort Interface IUMPRDenominator
Description –
Port Defined Type Dem_RatioIdType
Argument Value(s)
Value {ecuc(Dem/DemGeneral/DemRatio/DemRatioId.value)}
Name = {ecuc(Dem/DemGeneral/DemRatio/DemRatioId.SHORT-NAME)}
c()
8.6.4.27 IUMPRDenominatorCondition
[SWS_Dem_01028] d
Name IUMPRDenominatorCondition_{Name}
Kind ProvidedPort Interface IUMPRDenominatorCondition
Description –
Port Defined Type Dem_IumprDenomCondIdType
Argument Value(s)
Value TBD
Name = {ecuc(Dem/DemGeneral/DemRatio/DemIUMPRDenGroup.SHORT-NAME)}
c()

AUTOSAR CP R20-11
8.6.4.28 IUMPRNumerator
[SWS_Dem_01027] d
Name IUMPRNumerator_{Name}
Kind ProvidedPort Interface IUMPRNumerator
Description –
Port Defined Type Dem_RatioIdType
Argument Value(s)
Value {ecuc(Dem/DemGeneral/DemRatio/DemRatioId.value)}
Name = {ecuc(Dem/DemGeneral/DemRatio/DemRatioId.SHORT-NAME)}
c()
8.6.4.29 OpCycle
[SWS_Dem_01026] d
Name OpCycle_{Name}
Kind ProvidedPort Interface OperationCycle
Description –
Argument Value(s)
Value {ecuc(Dem/DemGeneral/DemOperationCycle/DemOperationCycleId.value)}
Variation Name = {ecuc(Dem/DemGeneral/DemOperationCycle.SHORT-NAME)}
c()
8.6.4.30 OverflowIndMirrorMemory
[SWS_Dem_01025] d
Name OverflowIndMirrorMemory_{Client}
Kind ProvidedPort Interface EvMemOverflowIndication
Description –
Argument Value(s) Value –
Value 0x02
Variation ({ecuc(Dem/DemGeneral/DemEventMemorySet/DemMirrorMemory)} != NULL) &&(({ecuc(Dem/
DemGeneral/DemClient/DemClientUsesRte )} ==TRUE))
Client= {ecuc(Dem/DemGeneral/DemClient.SHORT-NAME)}
c()

AUTOSAR CP R20-11
8.6.4.31 OverflowIndPermanentMemory
[SWS_Dem_01024] d
Name OverflowIndPermanentMemory
Description –
Port Defined Type Dem_DTCOriginType
Argument Value(s)
Value 0x03
Variation ({ecuc(Dem/DemGeneral/DemEventMemorySet/DemMaxNumberEventEntryPermanent)} > 0)
c()
8.6.4.32 OverflowIndPrimaryMemory
[SWS_Dem_01023] d
Name OverflowIndPrimaryMemory_{Client}
Description –
Value 0x01
Variation (({ecuc(Dem/DemGeneral/DemClient/DemClientUsesRte)} ==TRUE))
Client= {ecuc(Dem/DemGeneral/DemClient.SHORT-NAME})
c(RS_Diag_04093)
8.6.4.33 OverflowIndUserDefinedMemory
[SWS_Dem_01022] d
Name OverflowIndUserDefinedMemory_{Client}_{UserDefinedMemory}
Description –
Value {ecuc(Dem/DemGeneral/DemEventMemorySet/DemUserDefinedMemory/
DemUserDefinedMemoryIdentifier.value)}
5

AUTOSAR CP R20-11
4
Variation ({ecuc(Dem/DemGeneral/DemClient/DemEventMemorySetRef->DemEventMemorySet/DemUser
DefinedMemory != NULL)})(({ecuc(Dem/DemGeneral/DemClient/DemClientUsesRte)} ==TRUE))
Client= {ecuc(Dem/DemGeneral/DemEventMemorySet.SHORT-NAME})
UserDefinedMemory = {ecuc(Dem/DemGeneral/DemClient/DemEventMemorySetRef->DemEvent
MemorySet/DemUserDefinedMemory.SHORT-NAME)}
c()
8.6.4.34 PowerTakeOffStatus
[SWS_Dem_01020] d
Name PowerTakeOffStatus
Kind ProvidedPort Interface PowerTakeOff
Description –
Variation {ecuc(Dem/DemGeneral.DemOBDSupport)} != DEM_OBD_NO_OBD_SUPPORT
c()
8.6.4.35 GetDataOfPID21
[SWS_Dem_01094] d
Name GetDataOfPID21
Kind ProvidedPort Interface GetDataOfPID21
Description –
Variation ({ecuc(Dem/DemGeneral/DemGeneralOBD.DemOBDCentralizedPID21Handling)} == true) &&
({ecuc(Dem/DemGeneral.DemOBDSupport)} == DEM_OBD_MASTER_ECU)
c()
[SWS_Dem_01017] d
Name SetDataOfPID21
Kind ProvidedPort Interface SetDataOfPID21
Description –
Variation ({ecuc(Dem/DemGeneral/DemGeneralOBD.DemOBDCentralizedPID21Handling)} == true) &&
({ecuc(Dem/DemGeneral.DemOBDSupport)} == DEM_OBD_PRIMARY_ECU)
c()

AUTOSAR CP R20-11
[SWS_Dem_01016] d
Name SetDataOfPID31
Kind ProvidedPort Interface SetDataOfPID31
Description –
Variation ({ecuc(Dem/DemGeneral.DemOBDSupport)} != DEM_OBD_NO_OBD_SUPPORT) &&
({ecuc(Dem/DemGeneral/DemGeneralOBD.DemOBDCentralizedPID31Handling)} == true)
c()
8.6.4.38 SetDataOfPID4D
[SWS_Dem_91030] d
Name SetDataOfPID4D
Kind ProvidedPort Interface SetDataOfPID4D
Description –
c()
8.6.4.39 SetDataOfPID4E
[SWS_Dem_91032] d
Name SetDataOfPID4E
Kind ProvidedPort Interface SetDataOfPID4E
Description –
c()
8.6.4.40 StorageCond
[SWS_Dem_01015] d

AUTOSAR CP R20-11
Name StorageCond_{Name}
Kind ProvidedPort Interface StorageCondition
Description –
Argument Value(s)
Value {ecuc(Dem/DemGeneral/DemStorageCondition/DemStorageCondition
Id.value)}
Variation Name = {ecuc(Dem/DemGeneral/DemStorageCondition.SHORT-NAME)}
c(RS_Diag_04219)

AUTOSAR CP R20-11
9 Sequence Diagrams
9.1 ControlDTCSetting
Generic Scan Tool «module» «module»
Dcm Dem
Request: ControlDTCSetting(off)
Dem_DisableDTCSetting(Std_ReturnType, uint8)
Positive or negative response()
Request: ControlDTCSetting(on)
Dem_EnableDTCSetting(Std_ReturnType, uint8)
Figure 9.1: Sequence diagram of ControlDTCSetting
9.2 Dem_ClearDTC
Dcm Dem
Request: ClearDTCInformation(DTC)
Dem_SelectDTC(Std_ReturnType, uint8, uint32, Dem_DTCFormatType, Dem_DTCOriginType)
Dem_GetDTCSelectionResultForClearDTC(Std_ReturnType, uint8)
loop Dem_ClearDTC(Std_ReturnType, uint8)
Figure 9.2: Sequence diagram of Dem_ClearDTC

AUTOSAR CP R20-11
«module» «module» SW-C implementing Any SW-C

Dcm Dem the monitoring
Dem_GetDTCSelectionResultForClearDTC(Std_ReturnType, uint8)
Dem_ClearDTC(Std_ReturnType, uint8)
<Module>_DemClearEventAllowed<ForCondition>(Std_ReturnType, boolean*)
opt
[Allowed == TRUE] Process / delete events of

EventBuffer()

reset the events status byte and UDS
status byte()

Trigger status byte related callbacks (e.g. <Module>_DemTriggerOnEventUdsStatus)

clean prestored FreezeFrame of related events()

Clear FreezeFrame data()
<Module>_DemTriggerOnEventData(Std_ReturnType, Dem_EventIdType)

!

<Module>_DemInitMonitorFor<EventName>(Std_ReturnType,
Dem_InitMonitorReasonType)
Figure 9.3: Sequence diagram of Dem_ClearDTC clearing a single DTC Dem-internally

AUTOSAR CP R20-11
9.3 Dem_GetDTCByOccurrenceTime
Dcm Dem
Request: ReadDTCInformation(reportFirstTestFailedDTC/
reportFirstConfirmedDTC/reportMostRecentTestFailedDTC/
reportMostRecentConfirmedDTC)
Dem_GetDTCByOccurrenceTime(Std_ReturnType, uint8, Dem_DTCRequestType, uint32**)
Figure 9.4: Sequence diagram of Dem_DcmGetDTCByOccurenceTime
9.4 Dem_GetNextExtendedDataRecord
Dcm Dem
Request: ReadDTCInformation
(reportDTCExtendedDataRecordByDTCNumber/
reportMirrorMemoryDTCExtendedDataRecordByDTCNumber)
Dem_SelectDTC(Std_ReturnType, uint8, uint32,

Dem_DTCFormatType, Dem_DTCOriginType)
Dem_SelectExtendedDataRecord(Std_ReturnType, uint8, uint8)
Dem_GetSizeOfExtendedDataRecordSelection
(Std_ReturnType, uint8, uint32**)
loop
Dem_GetNextExtendedDataRecord(Std_ReturnType, uint8, uint8**, uint16**)
Figure 9.5: Sequence diagram of Dem_GetNextExtendedDataRecord

AUTOSAR CP R20-11
9.5 Dem_DcmGetStatusOfDTC
Dcm Dem
(reportDTCByStatusMask)
Dem_GetDTCStatusAvailabilityMask(Std_ReturnType, uint8, Dem_UdsStatusByteType**,

Dem_DTCOriginType)
Dem_GetStatusOfDTC(Std_ReturnType, uint8, uint8**)
Figure 9.6: Sequence diagram of Dem_GetStatusOfDTC
9.6 Retrieving freeze frames

Dcm Dem
(reportDTCSnapshotRecordByDTCNumber)
opt
Dem_GetSizeOfFreezeFrameSelection(Std_ReturnType, uint8, uint32**)
loop
Dem_GetNextFreezeFrameData(Std_ReturnType, uint8, uint8**, uint16**)
Figure 9.7: Sequence diagram to retrieve freeze frames

AUTOSAR CP R20-11
9.7 GetOBDFaultInformation
Dcm Dem
Service S01: RequestVehicleInformation PID S01()

Dem_SetDTCFilter(Std_ReturnType, uint8, uint8,
Dem_DTCFormatType, Dem_DTCOriginType, boolean,
Dem_DTCSeverityType, boolean)
Dem_SetDTCFilter()
Dem_GetNumberOfFilteredDTC(Std_ReturnType, uint8,
uint16**)
Dem_DcmGetNumberOfFilteredDTC()
Positive Response to Service S01 with PID S01()
Service S03: Request emission related DTCs()

Dem_SetDTCFilter(Std_ReturnType, uint8, uint8,
Dem_DTCFormatType, Dem_DTCOriginType, boolean,
Dem_DTCSeverityType, boolean)
Dem_SetDTCFilter()
loop Get DTCs

[Repeat until function returns "NoMatchingDTCs"]
Dem_GetNextFilteredDTC(Std_ReturnType, uint8, uint32**,

uint8**)
Dem_GetNextFilteredDTC()
Assemble response
message()
Positive Response to Service S03()
Service S02: Request Powertrain freeze frame data PID S02, FF: S00()
Dem_DcmGetDTCOfOBDFreezeFrame(FrameNumber=0x00, DTC)
Dem_DcmGetDTCOfOBDFreezeFrame()
Positive response to Service S02, PID S02()
Figure 9.8: Sequence diagram of GetOBDFaultInformation

AUTOSAR CP R20-11
9.8 ReportDTCByStatusMask
Dcm Dem
(ReportDTCSnapshotRecordByDTCNumber)
Dem_GetDTCStatusAvailabilityMask(Std_ReturnType,
uint8, Dem_UdsStatusByteType**,
Dem_DTCOriginType)
Dem_SetDTCFilter(Std_ReturnType, uint8, uint8, Dem_DTCFormatType,

Dem_DTCOriginType, boolean, Dem_DTCSeverityType, boolean)
loop Get DTCs
[Repeat until function returns "NoMatchingDTCs"]
Dem_GetNextFilteredDTC(Std_ReturnType, uint8, uint32**,

uint8**)
Assemble
response()
Figure 9.9: Sequence diagram of ReportDTCStatusMask
9.9 FiM_DemTriggerOnEventStatus
«module» SW-C (Functionality) «module»
Dem FiM
FiM_DemTriggerOnMonitorStatus(Dem_EventIdType)
FiM_DemTriggerOnMonitorStatus()
Dem_GetMonitorStatus(Std_ReturnType, Dem_EventIdType,
Dem_MonitorStatusType**)
Dem_GetMonitorStatus()
FiM_GetFunctionPermission(Std_ReturnType,
FiM_FunctionIdType, boolean**)
Fim_GetFunctionPermission()
Figure 9.10: Sequence diagram of FiM_DemTriggerOnEventStatus

AUTOSAR CP R20-11
9.10 ProcessEvent (Example)

«module» «module» Mode Requesting SW-C
FiM Dem
opt optional
Dem_PrestoreFreezeFrame(Std_ReturnType, Dem_EventIdType)
Dem_PrestoreFreezeFrame()
Process Prestored Freezeframes, Event()
Dem_SetEventStatus(Std_ReturnType, Dem_EventIdType, Dem_EventStatusType)
Dem_SetEventStatus()
Process Freezeframes, Events, Counters, etc.()
store current EventStatus to EventStatusNew()
opt if FiM available
FiM_DemTriggerOnMonitorStatus
(Dem_EventIdType)
Fim_DemTriggerOnEventStatus()
store current EventStatus to EventStatusOld()
Figure 9.11: Sequence diagram for an example of ProcessEvent Dem-internally

AUTOSAR CP R20-11
10 Configuration specification
In general, this chapter defines configuration parameters and their clustering into con-
tainers. In order to support the specification Chapter chapter 10.1 describes funda-
mentals. It also specifies a template (table) you shall use for the parameter specifica-
tion. We intend to leave chapter 10.1 in the specification to guarantee comprehension.
• chapter 10.2 specifies the structure (containers) and the parameters of the mod-
ule Dem
• chapter 10.3 specifies published information of the module Dem
10.1 How to read this chapter

For details refer to the chapter 10.1 “Introduction to configuration specification” in
SWS_BSWGeneral
10.2 Containers and configuration parameters

The following chapters summarize all configuration parameters. The detailed meaning
of the parameters are described in chapter 7 and chapter 8.
10.2.1 Dem
Module SWS Item ECUC_Dem_00928

Module Name Dem
Module Description Configuration of the Dem (Diagnostic Event Manager) module.
Post-Build Variant true
Support
Supported Config VARIANT-POST-BUILD, VARIANT-PRE-COMPILE
Variants
Included Containers
Container Name Multiplicity Scope / Dependency
DemConfigSet 1 This container contains the configuration parameters
and sub containers of the Dem module supporting
multiple configuration sets.
DemGeneral 1 This container contains the configuration (parameters)
of the BSW Dem
10.2.2 General
10.2.2.1 DemGeneral
SWS Item [ECUC_Dem_00677]

AUTOSAR CP R20-11
Container Name DemGeneral

Parent Container Dem
Description This container contains the configuration (parameters) of the BSW
Dem
Configuration Parameters
Name DemAgingRequiresNotFailedCycle [ECUC_Dem_00918]

Parent Container DemGeneral
Description Defines if the aging cycle counter is processed in operation cycles with
test failed report or not.
True: Aging cycle counter is processed only in operation cycles without

test failed. False (Default): No effect on aging cycle counter
processing.
Multiplicity 1
Type EcucBooleanParamDef
Default Value false
Post-Build Variant false
Value
Value Configuration Pre-compile time X All Variants
Class
Link time –
Post-build time –
Scope / Dependency scope: local
Name DemAgingRequiresTestedCycle [ECUC_Dem_00877]

Description Defines if the aging cycle counter is processed every aging cycles or if
only tested aging cycle are considered.
true: only tested aging cycle are considered for aging cycle counter
false: aging cycle counter is processed every aging cycle

Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Scope / Dependency scope: ECU

AUTOSAR CP R20-11
Name DemAvailabilitySupport [ECUC_Dem_00878]

Description This configuration switch defines, whether support for availability is
enabled or not.
Multiplicity 1
Type EcucEnumerationParamDef
Range DEM_EVENT_AVAILABILI Support availability by Event
TY
DEM_NO_AVAILABILITY Availability is not supported
Value
Class
Link time –
Post-build time –
Name DemBswErrorBufferSize [ECUC_Dem_00625]

Description Maximum number of elements in buffer for handling of BSW errors (ref.
to SWS_Dem_00207).
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default Value
Multiplicity
Value
Multiplicity Pre-compile time X All Variants
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemClearDTCBehavior [ECUC_Dem_00766]

Description Defines the clearing process of diagnostic information for volatile and
non-volatile memory and the positive response handling for the Dcm
module.
Multiplicity 1
Range DEM_CLRRESP_NONVO Return DEM_CLEAR_OK after volatile
LATILE_FINISH and non-volatile event memory data
cleared.

AUTOSAR CP R20-11
DEM_CLRRESP_NONVO Return DEM_CLEAR_OK after volatile

LATILE_TRIGGER event memory data cleared and
non-volatile event memory clearing is
triggered
DEM_CLRRESP_VOLATI Return DEM_CLEAR_OK after volatile
LE event memory data cleared
Value
Class
Link time –
Post-build time –
Name DemClearDTCLimitation [ECUC_Dem_00790]

Description Defines the supported Dem_<...>ClearDTC API scope.
Multiplicity 1
Range DEM_ALL_SUPPORTED_ Dem_<...>ClearDTC accepts all
DTCS supported DTC values, as well as all
DTC values
which are configured in
DemGroupDTCs and
DEM_DTC_GROUP_ALL_DTCS.
DEM_ONLY_CLEAR_ALL Dem_<...>ClearDTC accepts
_DTCS ClearAllDTCs only.
Default Value DEM_ALL_SUPPORTED_DTCS
Value
Class
Link time –
Post-build time –
Name DemDataElementDefaultEndianness [ECUC_Dem_00858]

Description Defines the default endianness of the data belonging to a data element
which is applicable if the DemExternalSRDataElementClass does not
define a endianness.
Multiplicity 1
Range BIG_ENDIAN Most significant byte shall come at the
lowest address.
LITTLE_ENDIAN Most significant byte shall come
highest address
OPAQUE opaque data endianness
Value

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemDebounceCounterBasedSupport [ECUC_Dem_00724]

Description This configuration switch defines, whether support for counter based
debouncing is enabled or not.
true: counter based debouncing support is enabled false: counter

based debouncing support is disabled
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemDebounceTimeBasedSupport [ECUC_Dem_00725]

Description This configuration switch defines, whether support for time based
debouncing is enabled or not.
true: time based debouncing support is enabled false: time based

debouncing support is disabled
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemDevErrorDetect [ECUC_Dem_00648]

Description Switches the development error detection and notification on or off.
• true: detection and notification is enabled.
• false: detection and notification is disabled.
Multiplicity 1
Default Value false
Value
Class
Link time –
Post-build time –
Name DemEventCombinationSupport [ECUC_Dem_00740]

Description This parameter defines the type of event combination supported by the
Dem.
Multiplicity 1
Range DEM_EVCOMB_DISABLE No event combination supported
D
DEM_EVCOMB_ONRETR Event combination on retrieval
IEVAL
DEM_EVCOMB_ONSTOR Event combination on storage
AGE
Value
Class
Link time –
Post-build time –
Name DemGeneralCallbackMonitorStatusChangedFnc [ECUC_Dem_00938]

Description Function name of prototype "<Module>_DemTriggerOnMonitorStatus".
Function for the General Monitor Status Changed notification.

Multiplicity 0..1
Type EcucFunctionNameDef
Default Value
Regular Expression
Multiplicity

AUTOSAR CP R20-11

Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemGeneralInterfaceSupport [ECUC_Dem_00880]

Description The interfaces GeneralEvtInfo, GeneralCallbackEventDataChanged,
GeneralCallbackMonitorStatusChanged and
GeneralCallbackEventUdsStatusChange are provided if
DemGeneralInterfaceSupport is equal to true.
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemMaxNumberEventEntryEventBuffer [ECUC_Dem_00899]

Description Specifies the size of the buffer for storing environmental data
(freezeframes and extended data) until they are processed and stored
to the event memory.
Multiplicity 0..1
Range 1 .. 250
Default Value
Multiplicity
Value
Configuration Class
Link time –
Post-build time –

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemMaxNumberPrestoredFF [ECUC_Dem_00692]

Description Defines the maximum number for prestored freeze frames. If set to 0,
then freeze frame prestorage is not supported by the ECU.
Multiplicity 1
Range 0 .. 255
Default Value
Value
Class
Link time –
Post-build time –
Name DemOBDSupport [ECUC_Dem_00698]

Description This configuration switch defines OBD support and kind of OBD ECU.
Multiplicity 1
Range DEM_OBD_DEP_SEC_E Kind of OBD ECU: OBD Dependend /
CU Secondary ECU
DEM_OBD_MASTER_EC Kind of OBD ECU: Master ECU
U
DEM_OBD_NO_OBD_SU OBD is not supported within this ECU
PPORT
DEM_OBD_PRIMARY_E Kind of OBD ECU: Pimary ECU
CU
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemPTOSupport [ECUC_Dem_00704]

Description This configuration switch defines, whether PTO support (and therefore
PID $1E support) is enabled or not.
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemResetConfirmedBitOnOverflow [ECUC_Dem_00799]

Description This configuration switch defines, whether the confirmed bit is reset or
not while an event memory entry will be displaced.
Multiplicity 1
Default Value true
Value
Class
Link time –
Post-build time –
Name DemStatusBitHandlingTestFailedSinceLastClear [ECUC_Dem_00784]

Description This configuration switch defines, whether the aging and displacement
mechanism shall be applied to the "TestFailedSinceLastClear" status
bits.
Multiplicity 1
Range DEM_STATUS_BIT_AGIN the "TestFailedSinceLastClear" status
G_AND_DISPLACEMENT bits are reset to 0, if aging or
displacement applies (like done for the
"ConfirmedDTC" status bits)
DEM_STATUS_BIT_NOR aging and displacement has no impact
MAL on the "TestFailedSinceLastClear"
status bits
Default Value DEM_STATUS_BIT_NORMAL
Value

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemStatusBitStorageTestFailed [ECUC_Dem_00714]

Description Activate/Deactivate the permanent storage of the "TestFailed" status
bits.
true: storage activated false: storage deactivated

Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemSuppressionSupport [ECUC_Dem_00793]

Description This configuration switch defines, whether support for suppression is
enabled or not.
Multiplicity 1
Range DEM_DTC_SUPPRESSIO Support suppression by DTC
N
DEM_NO_SUPPRESSIO Suppression is not supported
N
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemTaskTime [ECUC_Dem_00715]

Description Allow to configure the time for the periodic cyclic task. Please note:
This configuration value shall be equal to the value in the Basic
Software Scheduler configuration of the RTE module.
The AUTOSAR configuration standard is to use SI units, so this

parameter is defined as float value in seconds. Dem configuration tools
must convert this float value to the appropriate value format for the use
in the software implementation of Dem.
min: A negative value is not allowed.
max: After event status was reported, processing shall be completed

within 100ms in order to have the fault entry status information updated
as soon as possible (e.g. for PID $01).
upperMultiplicity: Exactly one TaskTime must be specified per

configuration.
lowerMultiplicity: Exactly one TaskTime must be specified per

configuration.
Multiplicity 1
Type EcucFloatParamDef
Range ]0 .. INF[
Default Value
Value
Class
Link time –
Post-build time –
Name DemTriggerFiMReports [ECUC_Dem_00719]

Description Activate/Deactivate the notification to the Function Inhibition Manager.
true: FiM notification activated false: FiM notification deactivated

Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemTriggerMonitorInitBeforeClearOk [ECUC_Dem_00765]

Description Defines if the monitor re-initialization has to be triggered before or after
the Dem module returns DEM_CLEAR_OK. true: trigger
re-initialization before DEM_CLEAR_OK false: trigger re-initialization
after DEM_CLEAR_OK
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemVersionInfoApi [ECUC_Dem_00721]

Description Activate/Deactivate the version information API.
true: version information activated false: version information

deactivated
Multiplicity 1
Default Value false
Value
Class
Link time –
Post-build time –
Name DemClearEventsWithoutDTCEventMemoryRef [ECUC_Dem_00941]

Description Indicating the event memory used as trigger to clear events without
assigned DTCs.
Multiplicity 0..1
Type Reference to DemPrimaryMemory
Multiplicity
Value
Configuration Class
Link time –
Post-build time –

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemOBDEventMemorySetRef [ECUC_Dem_00940]

Description References the DemEventMemorySet used for OBD ECU.
Multiplicity 0..1
Type Reference to DemEventMemorySet
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Included Containers
DemClient 1..255 This container contains possible clients that are using
the Dem APIs.
DemDataElementClass 0..65535 This container contains the configuration (parameters)
for an internal/external data element class.
DemDidClass 0..65535 This container contains the configuration (parameters)
for a data Id class. It is assembled out of one or several
data elements.
DemEnableCondition 0..255 This container contains the configuration (parameters)
for enable conditions.
DemEnableCondition 0..255 This container contains the configuration (parameters)
Group for enable condition groups.
DemEventMemorySet 1..255 This container is a collection of referenced event
memories and related information for a Dem client.
DemExtendedDataClass 0..65535 This class contains the combinations of extended data
records for an extended data class.
DemExtendedData 0..253 This container contains the configuration (parameters)
RecordClass for an extended data record class.
It is assembled out of one or several data elements.

DemFreezeFrameClass 0..65535 This container contains the combinations of DIDs for a
non OBD2 and WWH-OBD relevant freeze frame class.

AUTOSAR CP R20-11
DemFreezeFrameRec 0..65535 This container contains a list of dedicated, different

NumClass freeze frame record numbers assigned to an event. The
order of record numbers in this list is assigned to the
chronological order of the according freeze frame
records.
DemFreezeFrameRecord 0..65535 This container contains a list of dedicated, different
Class freeze frame record numbers.
DemGeneralJ1939 0..1 This container contains the general J1939-specific
configuration (parameters) of the Dem module. If the
container exists the J1939 support is enabled.
DemGeneralOBD 0..1 This container contains the general OBD-specific
configuration (parameters) of the Dem module.
DemNvRamBlockId 0..* This container contains the configuration (parameters)
for a non-volatile memory block, which is used from the
Dem. If no permanent storage of event memory entries
is required, no block needs to be configured.
The number of blocks which are necessary depends on

the implementation and configuration (e.g. number of
used event memories) of the Dem module.
DemOperationCycle 1..256 This container holds all parameters that are relevant to
configure an operation cycle.
DemRatio 0..65535 This container contains the OBD-specific in-use-monitor
performance ratio configuration. It is related to a specific
event, a FID, and an IUMPR group.
DemStorageCondition 0..255 This container contains the configuration (parameters)
for storage conditions.
DemStorageCondition 0..255 This container contains the configuration (parameters)
Group for storage condition groups.

AUTOSAR CP R20-11
DemFunctionIdRef: EcucReferenceDef
DemGeneral: DemRatio:
EcucParamConfContainerDef EcucParamConfContainerDef +reference lowerMultiplicity = 0
upperMultiplicity = *
upperMultiplicity = 1 upperMultiplicity = 65535 requiresSymbolicNameValue = true
+destination
+subContainer FiMFID: EcucParamConfContainerDef
DemDiagnosticEventRef:
+destination
DemIndicatorAttribute: DemEventParameter:
+subContainer
DemFreezeFrameClass: DemFreezeFrameClassRef:
EcucParamConfContainerDef +destination EcucReferenceDef
+reference DemDidClassRef: EcucReferenceDef

DemDidClass: +destination
upperMultiplicity = 65535 requiresIndex = true
+reference
DemDidDataElementClassRef:
EcucReferenceDef
EcucChoiceContainerDef +destination lowerMultiplicity = 1
+subContainer
DemExtendedDataClassRef:
DemExtendedDataClass: +destination EcucReferenceDef
+reference
DemExtendedDataRecordClassRef:
EcucReferenceDef
DemExtendedDataRecordClass:
Figure 10.1: DemGeneral configuration overview (part I)

AUTOSAR CP R20-11
DemGeneral: DemEnableCondition: DemEnableConditionRef:

EcucParamConfContainerDef +subContainer EcucParamConfContainerDef EcucReferenceDef
upperMultiplicity = 1 upperMultiplicity = 255 +destination lowerMultiplicity = 1
lowerMultiplicity = 1 lowerMultiplicity = 0 upperMultiplicity = 255
DemOperationCycle: DemAgingCycleRef:

+subContainer lowerMultiplicity = 1 upperMultiplicity = 1
+destination EcucReferenceDef
DemNvRamBlockId:
+subContainer EcucParamConfContainerDef +reference
lowerMultiplicity = 0 DemEventParameter:
DemIndicator: lowerMultiplicity = 1
+subContainer
DemIndicatorRef: EcucReferenceDef EcucParamConfContainerDef
+reference
DemStorageCondition: DemStorageConditionRef:
+subContainer EcucParamConfContainerDef +destination EcucReferenceDef

DemClient:
Figure 10.2: DemGeneral configuration overview (part II)
10.2.2.2 DemConfigSet

Container Name DemConfigSet
Parent Container Dem
Description This container contains the configuration parameters and sub
containers of the Dem module supporting multiple configuration sets.

AUTOSAR CP R20-11
Included Containers
DemComponent 0..* This container configures the monitored components
and system dependencies.
DemDTC 0..65535 This container contains the configuration (parameters)
for DemUdsDTC.
DemDTCAttributes 0..65535 This container contains the configuration (parameters)
for DemDTCAttributes.
DemDebounceCounter 0..65535 This container contains the configuration of Debounce
BasedClass Counter Based Class
DemDebounceTimeBase 0..65535 This container contains the configuration of Debounce
Class Time Based Class.
DemDtrs 0..1 This container holds the configuration of DTRs
collection.
DemEventParameter 1..65535 This container contains the configuration (parameters)
for events.
DemMultiEventTriggering 0..65535 Configures an event that will trigger other events
whenever the event is reported.
DemObdDTC 0..65535 This container contains the configuration (parameters)
for DemObdDTC.
DemPidClass 0..255 This container contains the different PIDs for the single
global OBD relevant freeze frame class. It is assembled
out of one or several data elements.

AUTOSAR CP R20-11
Dem: EcucModuleDef
+container
DemConfigSet: DemPidClass:
DemDTCAttributes: DemDTCAttributesRef:
+subContainer EcucParamConfContainerDef +destination EcucReferenceDef

+reference
DemDTC:
DemDebounceCounterBasedClass:
DemEventParameter:
+subContainer
DemMultiEventTriggering:

DemObdDTC:
DemComponent:
Figure 10.3: DemConfigSet configuration overview
10.2.2.3 DemClient

Container Name DemClient

AUTOSAR CP R20-11
Description This container contains possible clients that are using the Dem APIs.
Configuration Class
Link time –
Post-build time –
Name DemClientFunctionality [ECUC_Dem_00943]

Parent Container DemClient
Description Functionality provided by Dem for the DemClient.
Multiplicity 1
Range DEM_CLIENT_ONLY_US The Dem provides only the client
ES_EVENTOVERFLOW_I related functionality
NTERFACE EvMemOverflowIndication for this
client Id. Other functionality like
DTCFilter or Clear is not allowed to be
used by this client.
DEM_CLIENT_USES_FU The Dem provides all client related
LL_FUNCTIONALITY functionality for the selected client (e.g.
clear APIs and overflow indications).
Default Value DEM_CLIENT_USES_FULL_FUNCTIONALITY
Value
Class
Link time –
Post-build time –
Scope / Dependency
Name DemClientId [ECUC_Dem_00932]

Description Defines a unique identifier for a Dem client. This number is used by
this client in the ClientID parameter in all API with this parameter.
Multiplicity 1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 255
Default Value
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemClientUsesRte [ECUC_Dem_00933]

Description If set to true, this client shall only use the DEM via RTE (Dem will
provide the C/S interfaces: CddIf, EvMemOverflowIndication). The
client must not do any C_API calls to the DEM.
Multiplicity 1
Default Value false
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemEventMemorySetRef [ECUC_Dem_00942]

Description References to the client assigned event memory container that
contains client specific settings and event memories.
Multiplicity 1
Type Reference to DemEventMemorySet
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Included Containers
DemCallbackDTCStatus 0..* The presence of this container indicates, that the Dem
Changed has access to a "DTCStatusChanged" callback, which
the Dem will call to notify other components about the
change in the status of a DTC.
In case there is a DemCallbackDTCStatusChangedFnc,

this parameter defines the name of the function that the
Dem will call.
In case there is no
DemCallbackDTCStatusChangedFnc, the Dem will have
an R-Port requiring the interface
CallbackDTCStatusChanged whose name is generated
by using the unique callback-prefix followed by the event
name.
Status change notifications are supported for DTCs in

primary memory only.
DemGeneral: EcucParamConfContainerDef DemEventMemorySet:

+destination
+subContainer
DemClient:
EcucParamConfContainerDef DemEventMemorySetRef:
DemClientId: EcucIntegerParamDef
+parameter min = 0
max = 255
DemClientUsesRte:
+parameter
+literal
DEM_CLIENT_USES_FULL_FUNCTIONALITY:
DemClientFunctionality: EcucEnumerationParamDef
defaultValue = DEM_CLIENT_USES_FULL_FUNCTIONALITY
+literal
DEM_CLIENT_ONLY_USES_EVENTOVERFLOW_INTERFACE:
Figure 10.4: DemClient configuration overview

AUTOSAR CP R20-11
10.2.2.4 DemDTCAttributes

Container Name DemDTCAttributes
Parent Container DemConfigSet
Description This container contains the configuration (parameters) for
DemDTCAttributes.
Name DemAgingAllowed [ECUC_Dem_00622]

Parent Container DemDTCAttributes
Description Defines if a DTC can be aged.
TRUE: aging allowed FALSE: aging not allowed

Multiplicity 1
Default Value false
Value
Class
Link time –
Post-build time –
Name DemAgingCycleCounterThreshold [ECUC_Dem_00623]

Description Number of aging cycles needed to unlearn/delete the event.
Multiplicity 0..1
Range 1 .. 255
Default Value
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemAgingCycleCounterThresholdForTFSLC [ECUC_Dem_00897]

Description Number of aging cycles needed to reset the testFailedSinceLastClear
Bit.
Multiplicity 0..1
Range 1 .. 255
Default Value
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemDTCPriority [ECUC_Dem_00662]

Description Priority of the event/dtc, in view of full event memory. A lower value
means higher priority.
Multiplicity 1
Range 0 .. 255
Default Value
Value
Class
Link time –
Post-build time –
Name DemDTCSignificance [ECUC_Dem_00779]

Description Significance of the event, which indicates additional information
concerning fault classification and resolution.
It can be mapped as Dem-internal data element. It shall be configured,

if it is a part of event related data.
Multiplicity 0..1
Range DEM_EVENT_SIGNIFICA failure, which affects the
NCE_FAULT component/ECU itself

AUTOSAR CP R20-11
DEM_EVENT_SIGNIFICA issue, which indicates additional

NCE_OCCURRENCE information concerning insufficient
system behavior
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemMaxNumberFreezeFrameRecords [ECUC_Dem_00605]

Description This parameter defines the number of according freeze frame records,
which can maximal be stored for this event. Therefore all these freeze
frame records have the same freeze frame class.
This parameter is only required for calculated record numeration (refer

to DemTypeOfFreezeFrameRecordNumeration).
Multiplicity 0..1
Range 0 .. 255
Default Value
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemAgingCycleRef [ECUC_Dem_00624]

Description Reference to the cycle which is triggering the aging of the event.
Multiplicity 0..1
Type Reference to DemOperationCycle
Multiplicity

AUTOSAR CP R20-11

Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemExtendedDataClassRef [ECUC_Dem_00667]

Description This reference defines the link to an extended data class sampler.
Multiplicity 0..1
Type Reference to DemExtendedDataClass
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Scope / Dependency
Name DemFreezeFrameClassRef [ECUC_Dem_00674]

Description These references define the links to a freeze frame class sampler.
Multiplicity 0..1
Type Reference to DemFreezeFrameClass
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Scope / Dependency

AUTOSAR CP R20-11
Name DemFreezeFrameRecNumClassRef [ECUC_Dem_00776]

Description This parameter defines the list of dedicated freeze frame record
numbers associated with the diagnostic event. These record numbers
are assigned to the freeze frame records (instead of calculated record
numbers).
This parameter is only required for configured record numeration (refer

to DemTypeOfFreezeFrameRecordNumeration).
Multiplicity 0..1
Type Reference to DemFreezeFrameRecNumClass
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemJ1939ExpandedFreezeFrameClassRef [ECUC_Dem_00834]

Description These references define the links to a J1939 freeze frame class
sampler.
Multiplicity 0..1
Type Reference to DemJ1939FreezeFrameClass
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Scope / Dependency

AUTOSAR CP R20-11
Name DemJ1939FreezeFrameClassRef [ECUC_Dem_00835]

Description These references define the links to a J1939 freeze frame class
sampler.
Multiplicity 0..1
Type Reference to DemJ1939FreezeFrameClass
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Scope / Dependency
Name DemMemoryDestinationRef [ECUC_Dem_00890]

Description The memory destination assigns DTCs to one or two memory
destinations. If more than one memory destination is assigned to a
specific DTC, the DTC can be present in the corresponding event
memories. In this case one of the references has to be
DemMirrorMemory (SWS_Dem_CONSTR_6104).
Multiplicity 1..2
Type Choice reference to
[DemMirrorMemory,DemPrimaryMemory,DemUserDefinedMemory]
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemWWHOBDFreezeFrameClassRef [ECUC_Dem_00911]

Description This reference defines the link to a WWH-OBD freeze frame class
sampler.
Multiplicity 0..1
Type Reference to DemFreezeFrameClass
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
No Included Containers
DemConfigSet: +subContainer DemEventParameter:
DemObdDTC: lowerMultiplicity = 1
lowerMultiplicity = 0 +reference
+destination DemDTCRef:
EcucReferenceDef
DemDTC:
+subContainer
DemDTCAttributes:
lowerMultiplicity = 0 +reference
+destination DemDTCAttributesRef: EcucReferenceDef
+reference DemExtendedDataClassRef: EcucReferenceDef
DemMaxNumberFreezeFrameRecords:
EcucIntegerParamDef
+parameter
min = 0
max = 255
+reference DemFreezeFrameRecNumClassRef: EcucReferenceDef
+reference DemFreezeFrameClassRef: EcucReferenceDef
DemAgingCycleCounterThreshold: EcucIntegerParamDef
+parameter min = 1
max = 255
DemAgingCycleCounterThresholdForTFSLC:
EcucIntegerParamDef
+parameter min = 1
max = 255
Figure 10.5: DTC attribute configuration overview (part I)

AUTOSAR CP R20-11
DemDTCAttributes: +parameter DemAgingAllowed: EcucBooleanParamDef

DemDTCPriority: EcucIntegerParamDef
+parameter
max = 255
min = 0
DemAgingCycleRef: EcucReferenceDef
+reference
DemDTCSignificance: EcucEnumerationParamDef +literal DEM_EVENT_SIGNIFICANCE_FAULT:

+parameter upperMultiplicity = 1
+literal DEM_EVENT_SIGNIFICANCE_OCCURRENCE:
DemUserDefinedMemory:
DemMemoryDestinationRef: EcucChoiceReferenceDef upperMultiplicity = 30
upperMultiplicity = 2 DemPrimaryMemory:
+destination EcucParamConfContainerDef
+reference
+destination DemMirrorMemory:
+reference DemJ1939FreezeFrameClassRef: EcucReferenceDef
+destination
lowerMultiplicity = 0 DemJ1939FreezeFrameClass:
DemJ1939ExpandedFreezeFrameClassRef:
DemWWHOBDFreezeFrameClassRef: DemFreezeFrameClass:

Figure 10.6: DTC attribute configuration overview (part II)
10.2.2.5 DemEventParameter

Container Name DemEventParameter
Description This container contains the configuration (parameters) for events.

AUTOSAR CP R20-11
Name DemCausalityDelayTime [ECUC_Dem_00921]

Parent Container DemEventParameter
Description Time to wait until the event is considered as causal. The parameter is
specified in seconds.
Multiplicity 0..1
Range [0 .. 2.5]
Default Value 0
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemComponentPriority [ECUC_Dem_00909]

Description Specifies the priority within the component. A lower value means
higher priority.
Multiplicity 0..1
Range 0 .. 255
Default Value
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemEventAssociatedIdentification [ECUC_Dem_00969]

Description Event associated identifier that allows to identify an event. This value
can be reported as internal data element in snapshot records or
extended data records.
Multiplicity 0..1
Range 0 .. 65535
Default Value
Value
Value Configuration Pre-compile time X VARIANT-PRE-COMPILE
Class
Link time –
Post-build time X VARIANT-POST-BUILD
Name DemEventAvailable [ECUC_Dem_00792]

Description This parameter configures an Event as unavailable. It is treated by
Dem as if it does not exist. true = Event is available false = Event is not
available
Multiplicity 1
Default Value
Value
Class
Link time –
Name DemEventAvailableInVariant [ECUC_Dem_00968]

Description This parameter defines the enabled or disabled status of an event. If
set to FALSE, the Event is generally disabled, even though the SW-C is
integrated and the Event is described in the ECUC. The Dem shall
ignore all calls from the SW-C. If set to TRUE, the availability of the
event depends on other availability sources.
Multiplicity 0..1
Default Value true
Multiplicity
Value

AUTOSAR CP R20-11

Configuration Class
Link time –
Post-build time –
Class
Link time –
Name DemEventConfirmationThreshold [ECUC_Dem_00924]

Description Defines the operation cycle threshold of the DTC confirmation status
according "Confirmation Threshold" of ISO 14229-1.
Multiplicity 1
Range 1 .. 255
Default Value 1
Value
Class
Link time –
Name DemEventConfirmationThresholdCounterAdaptable
[ECUC_Dem_00929]
Description Indicates whether the events confirmation Cycle threshold can be
adapted by Dem_SetEventConfirmationThresholdCounter.
Multiplicity 0..1
Default Value false
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemEventId [ECUC_Dem_00659]

Description Unique identifier of a diagnostic event.
This parameter should not be changeable by user, because the Id

should be generated by Dem itself to prevent gaps and multiple use of
an Id. The events should be sequentially ordered beginning with 1 and
no gaps in between.
Multiplicity 1
Range 1 .. 65535
Default Value
Value
Class
Link time –
Post-build time –
Name DemEventKind [ECUC_Dem_00660]

Description This parameter is used to distinguish between SW-C and BSW events.
Multiplicity 1
Range DEM_EVENT_KIND_BSW The event is a assigned to a BSW
module
DEM_EVENT_KIND_SWC The event is a assigned to a SW-C
Value
Class
Link time –
Post-build time –
Scope / Dependency
Name DemEventRecoverableInSameOperationCycle [ECUC_Dem_00916]

Description If parameter is configured to FALSE, reporting of PASSED will be
ignored if the event is already "testfailed this operation cycle".
Multiplicity 0..1
Default Value true
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemEventReportingType [ECUC_Dem_00970]

Description This parameter defines the way a monitor can report an event to the
Dem. There are various ways to report an event and the Dem provides
different APIs for it.
Tags:
atp.Status=draft
Multiplicity 1
Range IMMEDIATE_FAIL_AND_ The event is reported over the API
SYNCHRONOUS_PROC Dem_SetEventFailedWithSyncFreezeFrame.
ESSING
Tags:
atp.Status=draft
STANDARD_REPORTIN The event is reported over the API
G Dem_SetEventStatus.
Tags:
atp.Status=draft
STANDARD_REPORTIN The event is reported over the API
G_WITH_MONITOR_DAT Dem_SetEventStatusWithMonitorData.
A
Tags:
atp.Status=draft
Default Value STANDARD_REPORTING
Value
Class
Link time –
Post-build time –
Name DemFFPrestorageInNvm [ECUC_Dem_00948]

Description If the event uses a pre-stored freeze-frame this attribute indicates if the
event requires the pre-stored data to be stored in non-volatile memory.
TRUE = store the pre-stored data in non-volatile memory, FALSE =
pre-stored data is not stored in non-volatile memory.
Multiplicity 0..1
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemFFPrestorageSupported [ECUC_Dem_00671]

Description If this parameter is set to true, then the Prestorage of FreezeFrames is
supported by the assigned event. This parameter is useful to calculate
the buffer size.
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemReportBehavior [ECUC_Dem_00894]

Description Indicates the reporting behavior of the BSW Module (DemEventKind
== DEM_EVENT_KIND_BSW) in order to determine the size of the
reporting queue.
If the parameter is not defined it means REPORT_BEFORE_INIT.

Multiplicity 0..1
Range REPORT_AFTER_INIT Indicates that the Event will not be
reported before Dem_Init().
REPORT_BEFORE_INIT Indicates that the Event may be
reported before Dem_Init().
Default Value REPORT_BEFORE_INIT
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemComponentClassRef [ECUC_Dem_00908]

Description Reference to the monitored component.
Multiplicity 0..1
Type Reference to DemComponent
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemDTCRef [ECUC_Dem_00888]

Description This parameter defines the DTC configuration (typically Uds)
associated with the diagnostic event.
It is allowed to have events without a DTC (e.g. for ECU-internal events

triggering safety reactions without being reported via diagnostic
communication). The same DemDTCAttributes can be used from
several events, to combine these (refer to chapter "Combination of
diagnostic event").
Multiplicity 0..1
Type Reference to DemDTC
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Scope / Dependency

AUTOSAR CP R20-11
Name DemEnableConditionGroupRef [ECUC_Dem_00746]

Description References an enable condition group.
Multiplicity 0..1
Type Reference to DemEnableConditionGroup
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemOBDGroupingAssociativeEventsRef [ECUC_Dem_00839]

Description This parameter defines a reference which points to a representative
event of one group of associate events. The "reverence event" must
refer to it self. Note: One event is only allowed to be reverenced to only
one group of associate events.
Multiplicity 0..1
Type Reference to DemEventParameter
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemOperationCycleRef [ECUC_Dem_00702]

Description Kind of operation cycle for the event (e.g. power cycle, driving cycle, ...)
Multiplicity 1
false
Post-Build Variant
Value

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemStorageConditionGroupRef [ECUC_Dem_00769]

Description References a storage condition group.
Multiplicity 0..1
Type Reference to DemStorageConditionGroup
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Included Containers
DemCallbackClearEvent 0..1 The presence of this container indicates that the Dem
Allowed has access to a "ClearEventAllowed" callback.
In case there is a DemCallbackClearEventAllowedFnc,

Dem will call.
In case there is no DemCallbackClearEventAllowedFnc,

the Dem will have an R-Port requiring the interface
CallbackClearEventAllowed whose name is generated
name.
DemCallbackEventData 0..1 The presence of this container indicates that the Dem
Changed has access to an "EventDataChanged" callback.
In case there is a DemCallbackEventDataChangedFnc,

Dem will call.
In case there is no DemCallbackEventDataChangedFnc,

the Dem will have an R-Port requiring the interface
CallbackEventDataChanged whose name is generated
name.

AUTOSAR CP R20-11
DemCallbackEventSync 0..1 The presence of this container indicates that the Dem
StorageProcessed will call the configured callback after an event status
reported with
Dem_SetEventFailedWithSyncFreezeFrame is finished
and the Dem is ready to process a next call for this
event.
Tags:
atp.Status=draft
DemCallbackEventUds 0..* The presence of this container indicates, that the Dem
StatusChanged has access to an "EventUdsStatusChanged" callback,
which the Dem will call to notify other components about
the change in the status of an event.
In case there is a
DemCallbackEventUdsStatusChangedFnc, this
parameter defines the name of the function that the
Dem will call.
In case there is no
DemCallbackEventUdsStatusChangedFnc, the Dem will
have an R-Port requiring the interface
CallbackEventUdsStatusChanged, whose name is
generated by using the unique callback-prefix followed
by the event name.
DemCallbackInitMForE 0..1 The presence of this container indicates, that the Dem
has access to an "InitMonitorForEvent" callback, which
the Dem will call to initialize a monitor.
In case the container has a DemCallbackInitMForEFnc,

Dem will call.
In case there is no DemCallbackInitMForEFnc, the Dem

will have an R-Port requiring the interface
CallbackInitMonitorForEvent, whose name is generated
name.
DemCallbackMonitor 0..* The presence of this container indicates, that the Dem
StatusChanged has access to an "MonitorStatusChanged" callback,
which the Dem will call to notify other components about
the change in the status of an event.
In case there is a
DemCallbackMonitorStatusChangedFnc, this parameter
defines the name of the function that the Dem will call.
In case there is no
DemCallbackMonitorStatusChangedFnc, the Dem will
have an R-Port requiring the interface
CallbackMonitorStatusChanged, whose name is
generated by using the unique callback-prefix followed
by the event name.

AUTOSAR CP R20-11
DemDebounceAlgorithm 1 Debounce algorithm class: counter based, time based,

Class or monitor internal.
DemIndicatorAttribute 0..255 This container contains the event specific configuration
of Indicators.
DemEventParameter:
+parameter DemEventId: EcucIntegerParamDef
max = 65535
lowerMultiplicity = 1 symbolicNameValue = true
DemCallbackInitMForEFnc:
EcucFunctionNameDef
DemCallbackInitMForE: +parameter lowerMultiplicity = 0

DEM_EVENT_KIND_SWC:
+literal
DemEventKind:
+literal DEM_EVENT_KIND_BSW:
DemCallbackEventUdsStatusChangedFnc:
EcucFunctionNameDef
DemCallbackEventUdsStatusChanged:+parameter lowerMultiplicity = 0
DemCallbackClearEventAllowedFnc:
EcucFunctionNameDef
DemCallbackClearEventAllowed:
+subContainer
DemClearEventAllowedBehavior:
+parameter
defaultValue = DEM_NO_STATUS_BYTE_CHANGE
+literal
DemEventAvailable:
DEM_NO_STATUS_BYTE_CHANGE:
DEM_ONLY_THIS_CYCLE_AND_READINESS:
+destination DemOperationCycle:
DemEventConfirmationThreshold:
EcucIntegerParamDef
+parameter min = 1
max = 255
defaultValue = 1
DemEventAssociatedIdentification:
EcucIntegerParamDef
+parameter
min = 0
max = 65535
DemEventAvailableInVariant: lowerMultiplicity = 0
EcucBooleanParamDef upperMultiplicity = 1
+parameter
defaultValue = true
DemEnableConditionGroupRef: DemEnableConditionGroup:

Figure 10.7: DemEventParameter configuration overview (part I)

AUTOSAR CP R20-11
DemEventParameter: DemDebounceAlgorithmClass:
EcucParamConfContainerDef +subContainer EcucChoiceContainerDef
lowerMultiplicity = 1 DemEventConfirmationThresholdCounterAdaptable:
upperMultiplicity = 1 EcucBooleanParamDef
+parameter
DemFFPrestorageSupported:
EcucBooleanParamDef
DemStorageConditionGroupRef: DemStorageConditionGroup:

DemIndicatorAttribute: DemIndicator:
+destination
EcucParamConfContainerDef +reference DemIndicatorRef: EcucParamConfContainerDef
EcucReferenceDef
+subContainer upperMultiplicity = 255 upperMultiplicity = 255
+parameter DemIndicatorBehaviour:
DemDTCRef: EcucReferenceDef DemDTC: EcucParamConfContainerDef

DemCallbackEventDataChanged: DemCallbackEventDataChangedFnc:
+reference DemOBDGroupingAssociativeEventsRef:
EcucReferenceDef DemFFPrestorageInNvm: EcucBooleanParamDef
+destination lowerMultiplicity = 0 lowerMultiplicity = 0

+parameter
+literal
DemReportBehavior: REPORT_BEFORE_INIT: EcucEnumerationLiteralDef
+parameter
defaultValue = REPORT_BEFORE_INIT +literal REPORT_AFTER_INIT: EcucEnumerationLiteralDef
DemComponentClassRef: DemComponent: EcucParamConfContainerDef

lowerMultiplicity = 0 upperMultiplicity = *
DemEventRecoverableInSameOperationCycle:
EcucBooleanParamDef
+parameter
defaultValue = true DemCausalityDelayTime: EcucFloatParamDef
+parameter max = 2.5
DemComponentPriority: EcucIntegerParamDef upperMultiplicity = 1
defaultValue = 0
+parameter min = 0
max = 255
Figure 10.8: DemEventParameter configuration overview (part II)
10.2.2.6 DemMultiEventTriggering

AUTOSAR CP R20-11

Container Name DemMultiEventTriggering
Description Configures an event that will trigger other events whenever the event is
reported.
Name DemMultiEventTriggeringMasterEventRef [ECUC_Dem_00945]

Parent Container DemMultiEventTriggering
Description Reference to the event that will trigger other events upon reception of
this event.
Multiplicity 1
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Name DemMultiEventTriggeringSlaveEventRef [ECUC_Dem_00946]

Parent Container DemMultiEventTriggering
Description Reference to the event that is triggered upon triggering the master
event.
Multiplicity 1..255
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
DemMultiEventTriggering:
EcucParamConfContainerDef DemMultiEventTriggeringSlaveEventRef: DemEventParameter:
lowerMultiplicity = 0 lowerMultiplicity = 1 upperMultiplicity = 65535
DemMultiEventTriggeringMasterEventRef:
Figure 10.9: DemMultiEventTriggering configuration overview

AUTOSAR CP R20-11
10.2.2.7 DemComponent

Container Name DemComponent
Description This container configures the monitored components and system
dependencies.
Name DemComponentFailedCallbackFnc [ECUC_Dem_00906]

Parent Container DemComponent
Description Specifies the function to be called on component failed status changes.
Multiplicity 0..1
Default Value
Regular Expression
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemComponentFailedCallbackUsePort [ECUC_Dem_00947]

Description Specifies whether CBStatusComp_{ComponentName} for component
change notifications shall be provided.
Multiplicity 0..1
Default Value false
Regular Expression
Multiplicity
Value
Configuration Class
Link time –
Post-build time –

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemComponentId [ECUC_Dem_00930]

Description Unique identifier of a DemComponent.
Component Id should be configured in sequential order beginning with

1 and no gaps in between. This parameter should not be changeable
by user, because the Id should be generated by Dem itself to prevent
gaps and multiple use of an Id
Multiplicity 1
Range 1 .. 65535
Default Value
Value
Class
Link time –
Post-build time –
Name DemComponentIgnoresPriority [ECUC_Dem_00905]

Description This configuration switch defines, whether the priority of events at this
component shall be ignored.
Multiplicity 0..1
Default Value false
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemImmediateChildComponentRef [ECUC_Dem_00907]

Description Reference to all immediate children of the current component.
Multiplicity 0..*
Type Reference to DemComponent
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
DemComponent:
DemComponentId:
EcucIntegerParamDef
+parameter
upperMultiplicity = * max = 65535
min = 1
DemComponentIgnoresPriority:
EcucBooleanParamDef
+parameter
DemComponentFailedCallbackFnc:
+reference DemImmediateChildComponentRef:
EcucReferenceDef
DemComponentFailedCallbackUsePort:
EcucFunctionNameDef
+parameter
Figure 10.10: DemComponent configuration overview
10.2.2.8 DemDTC

Container Name DemDTC

AUTOSAR CP R20-11

DemUdsDTC.
Name DemDTCFunctionalUnit [ECUC_Dem_00643]

Parent Container DemDTC
Description DTCFuncitonalUnit is a 1-byte value which identifies the corresponding
basic vehicle / system function which reports the DTC. This parameter
is necessary for the report of severity information.
If this parameter is configured for no DTC, the Dem provides no DTC

functional unit information.
Multiplicity 0..1
Range 0 .. 255
Default Value
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemDTCSeverity [ECUC_Dem_00645]

Description DTC severity according to ISO 14229-1. This parameter depends on
the automotive manufacturer.
If it is not configured, the value is counted as ’no severity’. If this

parameter is configured for no DTC, the Dem provides no DTC severity
information.
Multiplicity 0..1
Range DEM_SEVERITY_CHECK Check at next halt
_AT_NEXT_HALT
DEM_SEVERITY_CHECK Check immediately
_IMMEDIATELY
DEM_SEVERITY_MAINT Maintenance required
ENANCE_ONLY
DEM_SEVERITY_NO_SE No severity information available
VERITY
Default Value DEM_SEVERITY_NO_SEVERITY

AUTOSAR CP R20-11

Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemDtcValue [ECUC_Dem_00887]

Description Unique Diagnostic Trouble Code value for UDS
(Range: 0x000000 and 0xFFFFFF are reserved for DTC groups by

ISO 14229-1)
Multiplicity 0..1
Range 1 .. 16777214
Default Value
Multiplicity
Value
Multiplicity Pre-compile time X VARIANT-PRE-COMPILE
Configuration Class
Link time –
Class
Link time –
Name DemNvStorageStrategy [ECUC_Dem_00127]

Description This parameter defines when a specific event memory entry is allowed
to be stored in the NVRAM.
Multiplicity 0..1
Range DURING_SHUTDOWN write during shutdown
IMMEDIATE_AT_FIRST_ write at first fail occurrence and during
OCCURRENCE shutdown
Default Value DURING_SHUTDOWN

AUTOSAR CP R20-11

Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemWWHOBDDTCClass [ECUC_Dem_00912]

Description DTC Class according to ISO 14229-1 [2013 version]. This parameter
depends on the automotive manufacturer. If it is not configured, the
value is marked as ’unclassified’. If this parameter is configured for no
DTC, the Dem provides no DTC WWHOBD class information.
Multiplicity 0..1
Range DEM_DTC_WWHOBD_C Class A
LASS_A
DEM_DTC_WWHOBD_C Class B1
LASS_B1
DEM_DTC_WWHOBD_C Class B2
LASS_B2
DEM_DTC_WWHOBD_C Class C
LASS_C
DEM_DTC_WWHOBD_C No Class information
LASS_NOCLASS
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemDTCAttributesRef [ECUC_Dem_00642]

Description This parameter defines the DTC Attributes associated with the
DemDTC.
Multiplicity 1
Type Reference to DemDTCAttributes
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Scope / Dependency
Name DemObdDTCRef [ECUC_Dem_00889]

Description This parameter defines the OBD DTC configuration associated with the
DemDTC.
It is allowed to have events without a OBD DTC.

Multiplicity 0..1
Type Reference to DemObdDTC
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Scope / Dependency

AUTOSAR CP R20-11
DemConfigSet:
DemEventParameter:
+reference
DemDTCRef:
+subContainer DemDtcValue: EcucIntegerParamDef
EcucReferenceDef
max = 16777214
DemDTC: +destination upperMultiplicity = 1
min = 1
+subContainer
DemDTCAttributes:
DemDTCAttributesRef: EcucReferenceDef EcucParamConfContainerDef
+destination
+reference
+subContainer
DemObdDTC:
+literal DEM_SEVERITY_NO_SEVERITY:
DemDTCSeverity: EcucEnumerationParamDef
+literal
defaultValue = DEM_SEVERITY_NO_SEVERITY DEM_SEVERITY_MAINTENANCE_ONLY:
+parameter
+literal
DEM_SEVERITY_CHECK_AT_NEXT_HALT:
+literal
DEM_SEVERITY_CHECK_IMMEDIATELY:
DemDTCFunctionalUnit: EcucIntegerParamDef
min = 0
lowerMultiplicity = 0 DEM_DTC_WWHOBD_CLASS_NOCLASS:
DemWWHOBDDTCClass: +literal
EcucEnumerationParamDef DEM_DTC_WWHOBD_CLASS_A:
+literal
+parameter EcucEnumerationLiteralDef
+literal
+literal
DEM_DTC_WWHOBD_CLASS_C:
+literal DURING_SHUTDOWN:
DemNvStorageStrategy: EcucEnumerationLiteralDef
defaultValue = DURING_SHUTDOWN +literal

upperMultiplicity = 1 IMMEDIATE_AT_FIRST_OCCURRENCE:
lowerMultiplicity = 0 EcucEnumerationLiteralDef
Figure 10.11: DemDTC configuration overview

AUTOSAR CP R20-11
10.2.2.9 DemGroupOfDTC

Container Name DemGroupOfDTC
Parent Container DemPrimaryMemory, DemUserDefinedMemory
Description This container contains the configuration (parameters) for DTC groups.
Name DemGroupDTCs [ECUC_Dem_00678]

Parent Container DemGroupOfDTC
Description DTC values of the selected group of DTC
(Range: 3 byte, 0xFFFFFF is reserved for ’all DTCs’, according to

ISO14229-1 Annex D.1) The DTC group ’all DTCs’ is always available
and will not be configured. The following ranges are reserved by ISO
14229-1 : 0x000000 to 0x0000ff and 0xffff00 to 0xffffff.
Multiplicity 1
Range 256 .. 16776959
Default Value
Value
Class
Link time –
DemGroupOfDTC: DemGroupDTCs:
+parameter
Figure 10.12: DemGroupOfDTC configuration overview
10.2.2.10 DemOperationCycle

Container Name DemOperationCycle
Description This container holds all parameters that are relevant to configure an
operation cycle.

AUTOSAR CP R20-11
Name DemOperationCycleId [ECUC_Dem_00898]

Parent Container DemOperationCycle
Description This parameter’s value is used, together with the aggregating
container, to define a symbolic name of the operation cycle.
Multiplicity 1
Range 0 .. 255
Default Value
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemLeadingCycleRef [ECUC_Dem_00919]

Parent Container DemOperationCycle
Description Defines the operation cycle, which is relevant for processing this
operation cycle.
Multiplicity 0..1
Type Symbolic name reference to DemOperationCycle
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Scope / Dependency

AUTOSAR CP R20-11
+subContainer
DemOperationCycle: DemOperationCycleId:

lowerMultiplicity = 1 +parameter upperMultiplicity = 1
min = 0
max = 255
+reference DemLeadingCycleRef:
EcucReferenceDef
Figure 10.13: DemOperationCycle configuration overview
DemDTCAttributes: DemAgingCycleRef: DemOperationCycle:

EcucParamConfContainerDef EcucReferenceDef EcucParamConfContainerDef

+destination
+reference
DemEventParameter: DemOperationCycleRef:
DemGeneralOBD: DemOBDPFCCycleRef:
EcucParamConfContainerDef +reference EcucReferenceDef +destination
DemLeadingCycleRef: +reference
EcucReferenceDef
Figure 10.14: DemOperationCycle usage overview
10.2.2.11 DemIndicator

Container Name DemIndicator
Parent Container DemEventMemorySet

AUTOSAR CP R20-11
Description This container contains the configuration (parameters) for Indicators.

Name DemIndicatorID [ECUC_Dem_00683]

Parent Container DemIndicator
Description Unique identifier of an indicator.
Multiplicity 1
Range 0 .. 255
Default Value
Value
Class
Link time –
Post-build time –
10.2.2.12 DemIndicatorAttribute

Container Name DemIndicatorAttribute
Description This container contains the event specific configuration of Indicators.
Name DemIndicatorBehaviour [ECUC_Dem_00682]

Parent Container DemIndicatorAttribute
Description Behaviour of the linked indicator
Multiplicity 1
Range DEM_INDICATOR_BLINK The indicator blinks when the event
ING has status FAILED
Not relevant with J1939.
DEM_INDICATOR_BLINK The indicator is active and blinks when
_CONT the event has status FAILED
Not relevant with J1939.
DEM_INDICATOR_CONTI The indicator is active when the even
NUOUS has status FAILED
DEM_INDICATOR_FAST_ Flash Indicator Lamp should be set to
FLASH ’Fast Flash’
DEM_INDICATOR_SLOW Flash Indicator Lamp should be set to
_FLASH ’Slow Flash’

AUTOSAR CP R20-11

Value
Class
Link time –
Name DemIndicatorFailureCycleCounterThreshold [ECUC_Dem_00750]

Description Defines the number of failure cycles for the
WarningIndicatorOnCriteria.
Multiplicity 0..1
Range 1 .. 255
Default Value
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemIndicatorHealingCycleCounterThreshold [ECUC_Dem_00748]

Description Defines the number of healing cycles for the
WarningIndicatorOffCriteria.
Multiplicity 1
Range 0 .. 255
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemIndicatorRef [ECUC_Dem_00687]

Description Reference to the used indicator.
Multiplicity 1
Type Reference to DemIndicator
false
Post-Build Variant
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
DemGeneral: +subContainer
EcucParamConfContainerDef DemOperationCycle:
upperMultiplicity = 1 DemMILIndicatorRef: EcucReferenceDef
+destination
+destination
DemEventParameter:
+subContainer
EcucParamConfContainerDef DemIndicatorRef: EcucReferenceDef
+reference
DemIndicatorFailureCycleCounterThreshold:
EcucIntegerParamDef
+parameter
max = 255
min = 1
DemIndicatorHealingCycleCounterThreshold:
EcucIntegerParamDef
+parameter
max = 255
min = 0
+literal
DemIndicatorBehaviour: DEM_INDICATOR_CONTINUOUS:
+literal
DEM_INDICATOR_BLINK_CONT:
+parameter +literal
DEM_INDICATOR_BLINKING:
+literal
DEM_INDICATOR_SLOW_FLASH:
+literal
DEM_INDICATOR_FAST_FLASH:
Figure 10.15: DemIndicator configuration overview
10.2.2.13 DemNvRamBlockId

Container Name DemNvRamBlockId

AUTOSAR CP R20-11

Description This container contains the configuration (parameters) for a non-volatile
memory block, which is used from the Dem. If no permanent storage of
event memory entries is required, no block needs to be configured.
The number of blocks which are necessary depends on the

implementation and configuration (e.g. number of used event
memories) of the Dem module.
Name DemNvRamBlockIdRef [ECUC_Dem_00697]

Parent Container DemNvRamBlockId
Description This reference contains the link to a non-volatile memory block. For
post build time configurations worst case scenario shall be used.
Multiplicity 1
Type Symbolic name reference to NvMBlockDescriptor
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Scope / Dependency
10.2.3 OBD
10.2.3.1 DemGeneralOBD

Container Name DemGeneralOBD
Description This container contains the general OBD-specific configuration
(parameters) of the Dem module.

AUTOSAR CP R20-11
Name DemOBDCentralizedPID21Handling [ECUC_Dem_00794]

Parent Container DemGeneralOBD
Description Switch to enable the centralized handling of PID $21.
true: centralized handling of PID $21 enabled
false: centralized handling of PID $21 disabled

Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemOBDCentralizedPID31Handling [ECUC_Dem_00879]

Description Switch to enable the centralized handling of PID $31.
true: centralized handling of PID $31 enabled
false: centralized handling of PID $31 disabled

Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemOBDCompliancy [ECUC_Dem_00795]

Description Configuration value to define the appropriate value to PID$1C "OBD
requirements to which vehicle or engine is certified." according to the
respective standards, e.g. OBD, OBDII, JOBD etc. Notice as well
J1979 or the "DiagnosticReadiness 1" DM05 message of J1939-73
Multiplicity 1
Range 0 .. 255
Default Value
Value

AUTOSAR CP R20-11

Configuration Class
Link time –
Post-build time –
Class
Link time –
Name DemOBDDelayedDCYConfirmedAndMIL [ECUC_Dem_00917]

Description Controls the delayed calculation of the confirmed status for the OBD
driving cycle.
Multiplicity 0..1
Default Value false
Value
Class
Link time –
Post-build time –
Name DemOBDEngineType [ECUC_Dem_00900]

Description Switch to provide either Gasoline or Diesel parameters.
Multiplicity 0..1
Range DEM_IGNITION_COMPR Diesel engine type
ESSION
DEM_IGNITION_SPARK Gasoline engine type
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemOBDEventDisplacement [ECUC_Dem_00796]

Description Activate/Deactivate a different displacement behavior for OBD events.
OBD events with special Conditions (e.g. Pending, MIL_On...) shall not
be displaced.
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemOBDDrivingCycleRef [ECUC_Dem_00923]

Description Defines the operationCycle which denotes the OBD driving cycle.
Multiplicity 1
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Scope / Dependency
Name DemOBDInputAcceleratorPedalInformation [ECUC_Dem_00763]

Description Input variable for the accelerator padal information, which is assigned
to a specific data element used as interface for the Dem-internal PID
calculations.
Multiplicity 0..1
Type Choice reference to [DemExternalCSDataElement-
Class,DemExternalSRDataElementClass]
Multiplicity
Value
Configuration Class
Link time –
Post-build time –

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemOBDInputAmbientPressure [ECUC_Dem_00762]

Description Input variable for the ambient pressure, which is assigned to a specific
data element used as interface for the Dem-internal PID calculations.
Multiplicity 0..1
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemOBDInputAmbientTemperature [ECUC_Dem_00761]

Description Input variable for the ambient temperature, which is assigned to a
specific data element used as interface for the Dem-internal PID
calculations.
Multiplicity 0..1
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemOBDInputDistanceInformation [ECUC_Dem_00759]

Description Input variable for the distance information, which is assigned to a
calculations.
Multiplicity 0..1
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemOBDInputEngineSpeed [ECUC_Dem_00757]

Description Input variable for the engine speed, which is assigned to a specific data
element used as interface for the Dem-internal PID calculations.
Multiplicity 0..1
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemOBDInputEngineTemperature [ECUC_Dem_00772]

Description Input variable for the engine temperature, which is assigned to a
calculations.
Multiplicity 0..1
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemOBDInputProgrammingEvent [ECUC_Dem_00760]

Description Input variable for the programming event, which is assigned to a
calculations.
Multiplicity 0..1
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemOBDInputVehicleSpeed [ECUC_Dem_00758]

Description Input variable for the vehicle speed, which is assigned to a specific
data element used as interface for the Dem-internal PID calculations.
Multiplicity 0..1
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemOBDPFCCycleRef [ECUC_Dem_00920]

Description Defines the operationCycle, which is relevant for processing the
OBDPFCCycle.
Multiplicity 1
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Scope / Dependency
Name DemOBDTimeSinceEngineStart [ECUC_Dem_00827]

Description Input variable for the Time Since Engine Start information, which is
assigned to a specific data element.
Multiplicity 0..1
Multiplicity
Value

AUTOSAR CP R20-11

Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemOBDWarmUpCycleRef [ECUC_Dem_00922]

Description Defines the operationCycle which denotes the OBD warm-up cycle.
Multiplicity 1
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Scope / Dependency
Included Containers
DemCallbackOBDDTC 0..* The presence of this container indicates, that the Dem
StatusChanged has access to a "DTCStatusChanged" callback, which

Dem will call.
In case there is no
name.


AUTOSAR CP R20-11
DemGeneralOBD: DemOBDInputEngineTemperature: +destination DemExternalCSDataElemen

EcucParamConfContainerDef +reference EcucChoiceReferenceDef EcucParamConfContaine
lowerMultiplicity = 0 upperMultiplicity = 1 +destination lowerMultiplicity = 0
DemOBDInputEngineSpeed: +destination
+reference EcucChoiceReferenceDef
+destination
DemOBDInputVehicleSpeed:
lowerMultiplicity = 0 +destination
+destination
DemOBDInputDistanceInformation:
+destination
DemOBDInputProgrammingEvent: DemExternalSRDataElemen
+reference EcucChoiceReferenceDef EcucParamConfContaine
lowerMultiplicity = 0 +destination upperMultiplicity = 1

+destination
DemOBDInputAmbientTemperature:
+destination
DemOBDInputAmbientPressure:
+destination
+destination
DemOBDInputAcceleratorPedalInformation:
+destination
DemOBDCentralizedPID21Handling:
DemOBDCentralizedPID31Handling:
DemOBDCompliancy: lowerMultiplicity = 1
EcucIntegerParamDef
+parameter
min = 0
max = 255
upperMultiplicity = 1 DemOBDDelayedDCYConfirmedAndMIL:
EcucBooleanParamDef
+parameter
DemOBDEventDisplacement:
defaultValue = FALSE
DemOBDEngineType: +literal DEM_IGNITION_SPARK:

+parameter
+literal
DEM_IGNITION_COMPRESSION:
Figure 10.16: DemGeneralOBD configuration overview

AUTOSAR CP R20-11
10.2.3.2 DemObdDTC

Container Name DemObdDTC
DemObdDTC.
Name DemConsiderPtoStatus [ECUC_Dem_00602]

Parent Container DemObdDTC
Description This parameter is TRUE, when the event is affected by the Dem PTO
handling.
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemDtcValue [ECUC_Dem_00885]

Description Unique Diagnostic Trouble Code value for OBD
Multiplicity 0..1
Range 1 .. 65535
Default Value
Multiplicity
Value
Configuration Class
Link time –
Class
Link time –

AUTOSAR CP R20-11
Name DemEventOBDReadinessGroup [ECUC_Dem_00755]

Description This parameter specifies the Event OBD Readiness group for PID $01
and PID $41 computation. This parameter is only applicable for
emission-related ECUs.
Multiplicity 0..1
Range DEM_OBD_RDY_AC A/C system component - spark
DEM_OBD_RDY_BOOST Boost Pressure System - compr.
PR
DEM_OBD_RDY_CAT Catalyst - spark
DEM_OBD_RDY_CMPRC Comprehensive component - spark,
MPT compr.
DEM_OBD_RDY_EGR EGR system - spark, compr.
DEM_OBD_RDY_EGSEN Exhaust Gas Sensor - compr.
S
DEM_OBD_RDY_EVAP Evaporative system - spark
DEM_OBD_RDY_FLSYS Fuel system - spark, compr.
DEM_OBD_RDY_FLSYS_ Non Contious Fuel system - spark,
NONCONT compr
DEM_OBD_RDY_HCCAT Non-Methan HC Catalyst - compr.
DEM_OBD_RDY_HTCAT Heated catalyst - spark
DEM_OBD_RDY_MISF Misfire - spark, compr.
DEM_OBD_RDY_NONE None - spark, compr.
DEM_OBD_RDY_NOXCA NOx Catalyst - compr.
T
DEM_OBD_RDY_O2SEN Oxygen sensor - spark
S
DEM_OBD_RDY_O2SEN Oxygen sensor heater - spark
SHT
DEM_OBD_RDY_PMFLT Particle Matters Filter - compr.
DEM_OBD_RDY_SECAIR Secondary air system - spark
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemJ1939DTCValue [ECUC_Dem_00892]

Description Unique Diagnostic Trouble Code value for J1939 (consisting of SPN
and FMI). The SPN is encoded in the lower number range (0x7FFFF)
and the FMI is encoded in the higher range (0xF80000).
Multiplicity 0..1
Range 1 .. 16777214
Default Value
Multiplicity
Value
Configuration Class
Link time –
Class
Link time –

AUTOSAR CP R20-11
DemConfigSet: DemDTC:
+subContainer +reference
DemObdDTC: EcucParamConfContainerDef DemObdDTCRef:

upperMultiplicity = 65535 +destination EcucReferenceDef
DemDtcValue: EcucIntegerParamDef
+parameter min = 1
max = 65535
DemConsiderPtoStatus: EcucBooleanParamDef
+parameter
DemEventOBDReadinessGroup:
+parameter
DemJ1939DTCValue: EcucIntegerParamDef

min = 1
Figure 10.17: DemObdDTC configuration overview
10.2.3.3 DemRatio

Container Name DemRatio
Description This container contains the OBD-specific in-use-monitor performance
ratio configuration. It is related to a specific event, a FID, and an
IUMPR group.

AUTOSAR CP R20-11
Name DemIUMPRDenGroup [ECUC_Dem_00838]

Parent Container DemRatio
Description This parameter specifies the assigned denominator type which is
applied in addition to the
DEM_IUMPR_GENERAL_INDIVIDUAL_DENOMINATOR conditions.
Multiplicity 1
Range DEM_IUMPR_DEN_500M Additional condition based on definition
ILL of 500miles conditions as defined for
OBD2.
DEM_IUMPR_DEN_COL Additional condition based on definition
DSTART of "cold start" as defined for EU5+
DEM_IUMPR_DEN_EVAP Additional condition based on definition
of "EVAP" conditions as defined for
OBD2.
DEM_IUMPR_DEN_NON No further condition. Denominator
E increments based on GEN-
ERAL_INDIVIDUAL_DENOMINATOR
only.
DEM_IUMPR_DEN_PHYS Additional physical condition
_API (component activity) computed within
the SW-C and reported via
Dem_RepIUMPRDenRelease.
Value
Class
Link time –
Post-build time –
Name DemIUMPRGroup [ECUC_Dem_00737]

Description This parameter specifies the assigned IUMPR group of the ratio Id.
Multiplicity 1
Range DEM_IUMPR_AFRI1 Air Fuel Ratio Imbalance Monitor Bank
1
DEM_IUMPR_AFRI2 Air Fuel Ratio Imbalance Monitor Bank
2
DEM_IUMPR_BOOSTPR
S
DEM_IUMPR_CAT1
DEM_IUMPR_CAT2
DEM_IUMPR_EGR
DEM_IUMPR_EGSENSO
R
DEM_IUMPR_EVAP
DEM_IUMPR_FLSYS
DEM_IUMPR_NMHCCAT
DEM_IUMPR_NOXADSO
RB

AUTOSAR CP R20-11
DEM_IUMPR_NOXCAT
DEM_IUMPR_OXS1
DEM_IUMPR_OXS2
DEM_IUMPR_PF1 Particulate Filter Monitor Bank 1
DEM_IUMPR_PF2 Particulate Filter Monitor Bank 2
DEM_IUMPR_PMFILTER
DEM_IUMPR_PRIVATE
DEM_IUMPR_SAIR
DEM_IUMPR_SECOXS1
DEM_IUMPR_SECOXS2
Value
Class
Link time –
Post-build time –
Name DemRatioId [ECUC_Dem_00787]

Description Defines a unique ratio Id.

an Id. The ratio Ids should be sequentially ordered beginning with 0
and no gaps in between.
Multiplicity 1
Range 0 .. 65535
Default Value
Value
Class
Link time –
Post-build time –
Name DemRatioKind [ECUC_Dem_00741]

Description This parameter defines whether the ratio will be calculated API or
observer based.
Multiplicity 1
Range DEM_RATIO_API API based ratio Id
DEM_RATIO_OBSERVER Observer based ratio Id
Value

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemDiagnosticEventRef [ECUC_Dem_00735]

Description This reference contains the link to a diagnostic event.
Multiplicity 1
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Name DemFunctionIdRef [ECUC_Dem_00736]

Description This reference contains the link to a function identifier within the FiM
which is used as a primary FID.
Multiplicity 0..*
Type Symbolic name reference to FiMFID
false
Post-Build Variant
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
DemRatio: DemDiagnosticEventRef: DemEventParameter:
EcucParamConfContainerDef +reference EcucReferenceDef +destination EcucParamConfContainerDef

DemFunctionIdRef: EcucReferenceDef FiMFID: EcucParamConfContainerDef
+reference lowerMultiplicity = 0 +destination lowerMultiplicity = 1

upperMultiplicity = * upperMultiplicity = *
DemIUMPRGroup:
+literal
DemRatioKind: DEM_RATIO_API:
+parameter
DEM_RATIO_OBSERVER:
DemRatioId: EcucIntegerParamDef

min = 0
DemIUMPRDenGroup: +literal
DEM_IUMPR_DEN_NONE:
+literal
DEM_IUMPR_DEN_PHYS_API:
+parameter +literal
DEM_IUMPR_DEN_COLDSTART:
+literal
DEM_IUMPR_DEN_EVAP:
+literal
DEM_IUMPR_DEN_500MILL:
Figure 10.18: DemRatio configuration overview

AUTOSAR CP R20-11
DemIUMPRGroup: +literal
DEM_IUMPR_PRIVATE:
+literal
DEM_IUMPR_CAT1:
+literal
DEM_IUMPR_CAT2:
+literal
DEM_IUMPR_OXS1:
+literal
DEM_IUMPR_OXS2:
+literal
DEM_IUMPR_EGR:
+literal
DEM_IUMPR_SAIR:
+literal
DEM_IUMPR_EVAP:
+literal
DEM_IUMPR_SECOXS1:
+literal
DEM_IUMPR_SECOXS2:
+literal
DEM_IUMPR_NMHCCAT:
+literal DEM_IUMPR_NOXCAT:
+literal
DEM_IUMPR_NOXADSORB:
+literal
DEM_IUMPR_PMFILTER:
+literal
DEM_IUMPR_EGSENSOR:
+literal
DEM_IUMPR_BOOSTPRS:
+literal
DEM_IUMPR_FLSYS:
+literal
DEM_IUMPR_AFRI1:
+literal
DEM_IUMPR_AFRI2:
+literal
DEM_IUMPR_PF1:
+literal
DEM_IUMPR_PF2:
Figure 10.19: DemIUMPRGroup configuration overview

AUTOSAR CP R20-11
10.2.3.4 DemDtrs

Container Name DemDtrs
Description This container holds the configuration of DTRs collection.
Included Containers
DemDtr 0..65535 This container holds the configuration of one individual
DTR.
10.2.3.5 DemDtr

Container Name DemDtr
Parent Container DemDtrs
Description This container holds the configuration of one individual DTR.
Name DemDtrCompuDenominator0 [ECUC_Dem_00815]

Parent Container DemDtr
Description Part of the conversion between the binary representation and the
physical meaning analogous to the SW-C Template conversion
CompuRationalCoeffs with 2 numerator coefficients and 1 denominator
coefficient in the direction compuInternalToPhys. This is the only one
supported denominator value, a constant divisor.
The value 0 is not allowed.

Multiplicity 1
Range [-INF .. INF]
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemDtrCompuNumerator0 [ECUC_Dem_00813]

coefficient in the direction compuInternalToPhys. This is the first
numerator value, which is multiplied with xˆ 0, i.e., the offset.
Multiplicity 1
Range [-INF .. INF]
Default Value
Value
Class
Link time –
Post-build time –
Name DemDtrCompuNumerator1 [ECUC_Dem_00814]

coefficient in the direction compuInternalToPhys. This is the second
numerator value, which is multiplied with xˆ 1, i.e., the factor.
Multiplicity 1
Range [-INF .. INF]
Default Value
Value
Class
Link time –
Post-build time –
Name DemDtrId [ECUC_Dem_00807]

Description The index identifier value assigned to this DTR. The value is generated
during the Dem configuration process.
Multiplicity 1
Range 0 .. 65535
Default Value
Value

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemDtrMid [ECUC_Dem_00809]

Description The OBDMID of the DTR.
The values 0x00, 0x20, 0x40, 0x60, 0x80, 0xA0, 0xC0, 0xE0 are
reserved.
Multiplicity 1
Range 0 .. 255
Default Value
Multiplicity
Value
Configuration Class
Link time –
Class
Link time –
Name DemDtrTid [ECUC_Dem_00810]

Description The OBDTID of the DTR.
Multiplicity 1
Range 0 .. 255
Default Value
Multiplicity
Value
Configuration Class
Link time –
Class
Link time –

AUTOSAR CP R20-11
Name DemDtrUasid [ECUC_Dem_00811]

Description The UaSId the DTR data shall be scaled to, and reported together with
the rescaled DTR data.
Multiplicity 1
Range 0 .. 255
Default Value
Multiplicity
Value
Configuration Class
Link time –
Class
Link time –
Name DemDtrUpdateKind [ECUC_Dem_00812]

Description Update conditions applied by the Dem to reports of DTR values. Only
supported if a related Event is configured
Multiplicity 1
Range DEM_DTR_UPDATE_AL Any DTR result reported by the monitor
WAYS is used by the Dem.
DEM_DTR_UPDATE_STE The Dem accepts reported DTRs only
ADY when the configured debouncing
mechanism is stable at the FAIL or
PASS limit.
Default Value DEM_DTR_UPDATE_ALWAYS
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemDtrEventRef [ECUC_Dem_00808]

Description Reference to the DemEventParameter this DTR is related to. If the
related event is not configured, the Dem cannot ensure consistency
between the DTR and the event.
Multiplicity 0..1
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
DemConfigSet: EcucParamConfContainerDef
+subContainer
DemDtrs: EcucParamConfContainerDef
+subContainer
DemDtr: EcucParamConfContainerDef
DemDtrId: EcucIntegerParamDef
lowerMultiplicity = 0 +parameter max = 65535
min = 0
+subContainer
DemDtrEventRef: EcucReferenceDef DemEventParameter:

DemDtrMid: EcucIntegerParamDef
+parameter
max = 255
min = 0
DemDtrTid: EcucIntegerParamDef
+parameter
max = 255
min = 0
DemDtrUasid: EcucIntegerParamDef
+parameter
max = 255
min = 0
DemDtrUpdateKind: EcucEnumerationParamDef +literal DEM_DTR_UPDATE_ALWAYS:

+parameter defaultValue = DEM_DTR_UPDATE_ALWAYS
+literal DEM_DTR_UPDATE_STEADY:
DemDtrCompuNumerator0:
+parameter EcucFloatParamDef
DemDtrCompuNumerator1:
DemDtrCompuDenominator0:
Figure 10.20: DemDtr configuration overview

AUTOSAR CP R20-11
10.2.3.6 DemPidClass

Container Name DemPidClass
Description This container contains the different PIDs for the single global OBD
relevant freeze frame class. It is assembled out of one or several data
elements.
Name DemPidIdentifier [ECUC_Dem_00705]

Parent Container DemPidClass
Description identifier of the PID
Multiplicity 1
Range 0 .. 255
Default Value
Value
Class
Link time –
Included Containers
DemPidDataElement 1..255 This container contains the different data elements
contained in the specific PID.

AUTOSAR CP R20-11
DemPidIdentifier: EcucIntegerParamDef
DemPidClass:
EcucParamConfContainerDef max = 255
min = 0
DemConfigSet: EcucParamConfContainerDef upperMultiplicity = 255 +parameter lowerMultiplicity = 1
+subContainer
DemPidDataElement:
+reference
+destination
DemExternalSRDataElementClass:
+choice EcucParamConfContainerDef
lowerMultiplicity = 1 +subContainer DemExternalCSDataElementClass:
DemInternalDataElementClass:
Figure 10.21: DemPidClass configuration overview
10.2.3.7 DemPidDataElement

Container Name DemPidDataElement
Parent Container DemPidClass
Description This container contains the different data elements contained in the
specific PID.
Configuration Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemPidDataElementClassRef [ECUC_Dem_00733]

Parent Container DemPidDataElement
Description This reference contains the link to a data element class.
Multiplicity 1
Type Reference to DemDataElementClass
true
Post-Build Variant
Value
Class
Link time –
10.2.4 J1939
10.2.4.1 DemGeneralJ19139

Container Name DemGeneralJ1939
Description This container contains the general J1939-specific configuration
(parameters) of the Dem module. If the container exists the J1939
support is enabled.
Name DemJ1939ClearDtcSupport [ECUC_Dem_00872]

Parent Container DemGeneralJ1939
Description This configuration switch defines whether clearing J1939 DTCs (DM03
und DM11) is supported or not.
This switches on and off the API Dem_J1939DcmClearDTC.

Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemJ1939Dm31Support [ECUC_Dem_00868]

Description This configuration switch defines whether J1939 DM31 is supported or
not.
This switches on and off the APIs

Dem_J1939DcmFirstDTCwithLampStatus and
Dem_J1939DcmGetNextDTCwithLampStatus. .
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemJ1939ExpandedFreezeFrameSupport [ECUC_Dem_00873]

Description This configuration switch defines whether J1939 expanded freeze
frames are supported or not.

Dem_J1939DcmSetFreezeFrameFilter,
Dem_J1939DcmGetNextFreezeFrame and
Dem_J1939DcmGetNextSPNInFreezeFrame.
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemJ1939FreezeFrameSupport [ECUC_Dem_00866]

Description This configuration switch defines whether J1939 freeze frames are
supported or not.

Dem_J1939DcmSetFreezeFrameFilter and
Dem_J1939DcmGetNextFreezeFrame.
Multiplicity 1
Default Value

AUTOSAR CP R20-11

Value
Class
Link time –
Post-build time –
Name DemJ1939RatioSupport [ECUC_Dem_00867]

Description This configuration switch defines whether J1939 performance ratios
are supported or not.
This switches on and off the APIs Dem_J1939DcmSetRatioFilter and

Dem_J1939DcmGetNextFilteredRatio.
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemJ1939Readiness1Support [ECUC_Dem_00869]

Description This configuration switch defines whether J1939 diagnostic readiness 1
is supported or not.
This switches on and off the API

Dem_J1939DcmReadDiagnosticReadiness1.
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11


Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –


Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemJ1939ReadingDtcSupport [ECUC_Dem_00865]

Description This configuration switch defines whether J1939 DTC readout is
supported or not.
This switches on and off the APIs Dem_J1939DcmSetDTCFilter,

Dem_J1939DcmGetNumberOfFilteredDTC and
Dem_J1939DcmGetNextFilteredDTC.
Multiplicity 1
Default Value
Value

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Included Containers
DemCallbackJ1939DTC 0..* The presence of this container indicates, that the Dem
StatusChanged has access to a "DTCStatusChanged" callback, which

Dem will call.
In case there is no
name.

DemJ1939FreezeFrame 0..255 This container contains the combinations of SPNs s for
Class a J1939 relevant freeze frame.
DemSPNClass 0..* This container contains the configuration (parameters)
for a SPN.

AUTOSAR CP R20-11
+subContainer
+subContainer
DemGeneralJ1939: DemJ1939ReadingDtcSupport:
EcucParamConfContainerDef +parameter EcucBooleanParamDef
DemJ1939FreezeFrameSupport:
DemJ1939ExpandedFreezeFrameSupport:
DemJ1939RatioSupport:
DemJ1939Dm31Support:
DemJ1939Readiness1Support:
DemJ1939ClearDtcSupport:
DemCallbackJ1939DTCStatusChanged: DemCallbackDTCStatusChangedFnc:
DemJ1939FreezeFrameClass: DemJ1939FreezeFrameClassRef:
+subContainer
Figure 10.22: DemGeneralJ19139 configuration overview

AUTOSAR CP R20-11
10.2.4.2 DemJ1939FreezeFrameClass

Container Name DemJ1939FreezeFrameClass
Description This container contains the combinations of SPNs s for a J1939
relevant freeze frame.
Name DemSPNClassRef [ECUC_Dem_00829]

Parent Container DemJ1939FreezeFrameClass
Description Reference to an SPN. This reference defines requiresIndex = true
since it represents a ordered list of references where the order
describes the order of single SPNs in the J1939 Freeze Frame.
Attributes:
requiresIndex=true
Multiplicity 1..255
Type Reference to DemSPNClass
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
DemEventParameter:
DemGeneralJ1939: DemJ1939FreezeFrameClass: DemJ1939FreezeFrameClassRef:

EcucParamConfContainerDef EcucParamConfContainerDef +destination EcucReferenceDef

+subContainer
DemJ1939ExpandedFreezeFrameClassRef:
+destination EcucReferenceDef
+reference
DemSPNClassRef:
EcucReferenceDef
+destination
DemSPNClass: DemSPNId: EcucIntegerParamDef

+parameter min = 0
upperMultiplicity = * lowerMultiplicity = 1
+subContainer
DemSPNDataElementClassRef:
+destination
+choice +choice +choice
DemExternalCSDataElementClass: DemExternalSRDataElementClass: DemInternalDataElementClass:

EcucParamConfContainerDef EcucParamConfContainerDef EcucParamConfContainerDef

Figure 10.23: DemJ1939FreezeFrameClass configuration overview
10.2.4.3 DemSPNClass

Container Name DemSPNClass

AUTOSAR CP R20-11

Description This container contains the configuration (parameters) for a SPN.
Name DemSPNId [ECUC_Dem_00831]

Parent Container DemSPNClass
Description Suspect parameter number
Multiplicity 1
Range 0 .. 524287
Default Value
Value
Class
Link time –
Post-build time –
Name DemSPNDataElementClassRef [ECUC_Dem_00832]

Parent Container DemSPNClass
Multiplicity 1
false
Post-Build Variant
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
DemGeneral:
+subContainer
DemGeneralJ1939:
+subContainer
DemSPNClass: DemSPNId: EcucIntegerParamDef

+parameter min = 0
upperMultiplicity = * lowerMultiplicity = 1
DemSPNDataElementClassRef:
Figure 10.24: DemSPNClass configuration overview
10.2.5 Conditions
10.2.5.1 DemEnableCondition

Container Name DemEnableCondition
Description This container contains the configuration (parameters) for enable
conditions.
Name DemEnableConditionId [ECUC_Dem_00654]

Parent Container DemEnableCondition
Description Defines a unique enable condition Id.

an Id. The enable conditions should be sequentially ordered beginning
with 0 and no gaps in between.
Multiplicity 1
Range 0 .. 255
Default Value
Value

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemEnableConditionStatus [ECUC_Dem_00656]

Parent Container DemEnableCondition
Description Defines the initial status for enable or disable of acceptance of event
reports of a diagnostic event.
The value is the initialization after power up (before this condition is

reported the first time). true: acceptance of a diagnostic event enabled
false: acceptance of a diagnostic event disabled
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
10.2.5.2 DemEnableConditionGroup

Container Name DemEnableConditionGroup
Description This container contains the configuration (parameters) for enable
condition groups.
Name DemEnableConditionRef [ECUC_Dem_00655]

Parent Container DemEnableConditionGroup
Description References an enable condition.
Multiplicity 1..255
Type Reference to DemEnableCondition
Multiplicity
Value

AUTOSAR CP R20-11

Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
DemEventParameter: DemEnableConditionGroupRef:

+destination
DemGeneral: EcucParamConfContainerDef DemEnableConditionGroup: DemEnableConditionRef:

+subContainer EcucParamConfContainerDef +reference EcucReferenceDef
+destination
DemEnableCondition: DemEnableConditionId:
upperMultiplicity = 255 +parameter max = 255

DemEnableConditionStatus:
Figure 10.25: DemEnableCondition configuration overview
10.2.5.3 DemStorageCondition

Container Name DemStorageCondition
Description This container contains the configuration (parameters) for storage
conditions.

AUTOSAR CP R20-11
Name DemStorageConditionId [ECUC_Dem_00730]

Parent Container DemStorageCondition
Description Defines a unique storage condition Id. This parameter should not be
changeable by user, because the Id should be generated by Dem itself
to prevent gaps and multiple use of an Id. The storage conditions
should be sequentially ordered beginning with 0 and no gaps in
between.
Multiplicity 1
Range 0 .. 255
Default Value
Value
Class
Link time –
Post-build time –
Name DemStorageConditionStatus [ECUC_Dem_00731]

Description Defines the initial status for enable or disable of storage of a diagnostic
event.
The value is the initialization after power up (before this condition is

reported the first time). true: storage of a diagnostic event enabled
false: storage of a diagnostic event disabled
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemStorageConditionReplacementEventRef [ECUC_Dem_00893]

Description Specifies the reference to an event which is stored to event memory
and supports failure analysis.
Multiplicity 0..1
Multiplicity
Value

AUTOSAR CP R20-11

Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
10.2.5.4 DemStorageConditionGroup

Container Name DemStorageConditionGroup
Description This container contains the configuration (parameters) for storage
condition groups.
Name DemStorageConditionRef [ECUC_Dem_00768]

Parent Container DemStorageConditionGroup
Description References an enable condition.
Multiplicity 1..255
Type Reference to DemStorageCondition
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
DemGeneral: DemStorageCondition: DemStorageConditionId: EcucIntegerParamDef
+parameter symbolicNameValue = true
upperMultiplicity = 1 upperMultiplicity = 255 min = 0
lowerMultiplicity = 1 lowerMultiplicity = 0 max = 255
DemStorageConditionStatus:
+subContainer +parameter EcucBooleanParamDef
DemStorageConditionReplacementEventRef:
+destination
DemStorageConditionRef:
EcucReferenceDef
+reference
DemStorageConditionGroup:
+destination
DemStorageConditionGroupRef:
EcucReferenceDef
+reference
DemEventParameter:
Figure 10.26: DemStorageCondition configuration overview
10.2.6 Event Memory
10.2.6.1 DemEventMemorySet

Container Name DemEventMemorySet
Description This container is a collection of referenced event memories and related
information for a Dem client.

AUTOSAR CP R20-11
Name DemMaxNumberEventEntryPermanent [ECUC_Dem_00689]

Description Maximum number of events which can be stored in the permanent
memory.
The assignment of an event to this memory type is dynamic and used

for emission-related events only.
Multiplicity 1
Range 0 .. 255
Default Value
Value
Class
Link time –
Post-build time –
Name DemTypeOfDTCSupported [ECUC_Dem_00720]

Description This parameter defines the format returned by
Dem_GetTranslationType and does not relate to/influence the
supported Dem functionality.
Multiplicity 1
Range DEM_DTC_TRANSLATIO ISO11992-4 DTC format
N_ISO11992_4
DEM_DTC_TRANSLATIO ISO14229-1 DTC format (3 byte
N_ISO14229_1 format)
DEM_DTC_TRANSLATIO ISO15031-6 DTC format =
N_ISO15031_6 SAE_J2012-DA_DTCFormat_00 (2
byte format)
DEM_DTC_TRANSLATIO SAEJ1939-73 DTC format
N_SAEJ1939_73
DEM_DTC_TRANSLATIO SAE_J2012-DA_DTCFormat_00 (3
N_SAE_J2012_DA_DTCF byte format)
ORMAT_04
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemAmberWarningLampIndicatorRef [ECUC_Dem_00821]

Description This parameter defines the indicator representing the
AmberWarningLamp . This parameter may be used for ECUs
supporting J1939.
Multiplicity 0..1
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemMILIndicatorRef [ECUC_Dem_00723]

Description This parameter defines the indicator representing the MIL.
This parameter is mandatory for ECUs supporting OBD (refer to

DemOBDSupport).
Multiplicity 0..1
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemProtectLampIndicatorRef [ECUC_Dem_00822]

Description This parameter defines the indicator representing the ProtectLamp.
This parameter may be used for ECUs supporting J1939.
Multiplicity 0..1
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemRedStopLampIndicatorRef [ECUC_Dem_00820]

Description This parameter defines the indicator representing the RedStopLamp.
This parameter may be used for ECUs supporting J1939.
Multiplicity 0..1
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Included Containers
DemClearDTC 0..255 Contains callback function definition which are called
Notification during clear DTC operations.
DemIndicator 0..255 This container contains the configuration (parameters)
for Indicators.
DemMirrorMemory 0..1 This container contains the mirror event memory
specific parameters of the Dem module.
DemPrimaryMemory 1 This container contains the primary event memory

AUTOSAR CP R20-11
DemUserDefinedMemory 0..30 This container contains the user defined event memory
DemEventMemorySet: DemIndicatorID:

+parameter
+subContainer lowerMultiplicity = 0
+destination +destination +destination +destination
DemMILIndicatorRef: EcucReferenceDef
+reference lowerMultiplicity = 0
DemProtectLampIndicatorRef:
DemRedStopLampIndicatorRef:
DemAmberWarningLampIndicatorRef:
Figure 10.27: DemEventMemorySet configuration overview

AUTOSAR CP R20-11
DemEventMemorySet: DemMaxNumberEventEntryPrimary:
DemPrimaryMemory:
+subContainer EcucParamConfContainerDef +parameter
DemMaxNumberEventEntryMirror:
DemMirrorMemory: EcucIntegerParamDef
+subContainer EcucParamConfContainerDef +parameter
min = 1
DemUserDefinedMemory: DemMaxNumberEventEntryUserDefined:
EcucParamConfContainerDef +parameter EcucIntegerParamDef
+subContainer
DemUserDefinedMemoryIdentifier:
+parameter EcucIntegerParamDef
min = 0
max = 255
DemClearDTCNotification:
EcucParamConfContainerDef START:
+literal
lowerMultiplicity = 0 DemClearDtcNotificationTime: EcucEnumerationLiteralDef
upperMultiplicity = 255 EcucEnumerationParamDef
+parameter
+subContainer upperMultiplicity = 1 +literal FINISH:
DemClearDtcNotificationFnc:
DemMaxNumberEventEntryPermanent:
EcucIntegerParamDef
+parameter
max = 255
min = 0
DemTypeOfDTCSupported: +literal DEM_DTC_TRANSLATION_ISO15031_6:

upperMultiplicity = 1 +literal
DEM_DTC_TRANSLATION_ISO14229_1:
+parameter +literal DEM_DTC_TRANSLATION_ISO11992_4:

+literal
DEM_DTC_TRANSLATION_SAEJ1939_73:
+literal
DEM_DTC_TRANSLATION_SAE_J2012_DA_DTCFORMAT_04:
Figure 10.28: DemEventMemorySet included containers overview
10.2.6.2 DemPrimaryMemory

Container Name DemPrimaryMemory

AUTOSAR CP R20-11
Description This container contains the primary event memory specific parameters
of the Dem module.
Name DemDtcStatusAvailabilityMask [ECUC_Dem_00652]

Parent Container DemPrimaryMemory
Description Mask for the supported DTC status bits by the Dem. This mask is used
in the positive response of UDS service 0x19.
Multiplicity 1
Range 0 .. 255
Default Value
Value
Class
Link time –
Post-build time –
Name DemEnvironmentDataCapture [ECUC_Dem_00895]

Description DemEnvironmentDataCapture defines the point in time, when the data
actually is captured.
Multiplicity 0..1
Range DEM_CAPTURE_ASYNC The data capturing is postponed to the
HRONOUS_TO_REPORT next cycle of the Dem_Mainfunction.
ING (This means that there is a minimum
delay between report of the failure and
capturing the data).
DEM_CAPTURE_SYNCH The data is captured immediately
RONOUS_TO_REPORTI within the context of
NG Dem_SetEventStatus.
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemEventDisplacementStrategy [ECUC_Dem_00742]

Description This configuration switch defines, whether support for event
displacement is enabled or not, and which displacement strategy is
followed.
Multiplicity 1
Range DEM_DISPLACEMENT_F Event memory entry displacement is
ULL enabled, by consideration of priority
active/passive status, and occurrence.
DEM_DISPLACEMENT_N Event memory entry displacement is
ONE disabled.
DEM_DISPLACEMENT_P Event memory entry displacement is
RIO_OCC enabled, by consideration of priority
and occurrence (but without
active/passive status).
Value
Class
Link time –
Post-build time –
Name DemEventMemoryEntryStorageTrigger [ECUC_Dem_00797]

Description Configures the primary trigger to allocate an event memory entry.
Multiplicity 1
Range DEM_TRIGGER_ON_CO Event Memory entries are triggered if
NFIRMED the UDS status bit 3 (confirmedDTC)
changes from 0 to 1.
DEM_TRIGGER_ON_FD Event Memory entries are triggered
C_THRESHOLD when the FDC threshold is reached.
DEM_TRIGGER_ON_TES Event Memory entries are triggered if
T_FAILED the UDS status bit 0 (testFailed)
Default Value DEM_TRIGGER_ON_TEST_FAILED
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemMaxNumberEventEntryPrimary [ECUC_Dem_00690]

Description Maximum number of events which can be stored in the primary
memory
Multiplicity 1
Range 1 .. 255
Default Value
Value
Class
Link time –
Post-build time –
Name DemOccurrenceCounterProcessing [ECUC_Dem_00767]

Description This configuration switch defines the consideration of the fault
confirmation process for the occurrence counter. For OBD and mixed
systems (OBD/non OBD, refer to DemOBDSupport) configuration
switch shall always set to DEM_PROCESS_OCCCTR_TF.
Multiplicity 1
Range DEM_PROCESS_OCCCT the occurrence counter is triggered by
R_CDTC the TestFailed bit if the fault
confirmation was successful
(ConfirmedDTC bit is set)
DEM_PROCESS_OCCCT the occurrence counter is only
R_TF triggered by the TestFailed bit (and the
fault confirmation is not considered)
This parameter is mandatory in case of
J1939.
Value
Class
Link time –
Post-build time –
Name DemTypeOfFreezeFrameRecordNumeration [ECUC_Dem_00778]

Description This parameter defines the type of assigning freeze frame record
numbers for event-specific freeze frame records.
Multiplicity 1
Range DEM_FF_RECNUM_CAL freeze frame records will be numbered
CULATED consecutive starting by 1 in their
chronological order

AUTOSAR CP R20-11
DEM_FF_RECNUM_CON freeze frame records will be numbered

FIGURED based on the given configuration in
their chronological order
Value
Class
Link time –
Post-build time –
Included Containers
DemGroupOfDTC 0..65535 This container contains the configuration (parameters)
for DTC groups.

AUTOSAR CP R20-11
DemEventMemorySet:
+subContainer
DemPrimaryMemory: DemMaxNumberEventEntryPrimary:
+parameter
DemEnvironmentDataCapture: +literal DEM_CAPTURE_SYNCHRONOUS_TO_REPORTING:

+parameter upperMultiplicity = 1 +literal DEM_CAPTURE_ASYNCHRONOUS_TO_REPORTING:
DemEventDisplacementStrategy: +literal
DEM_DISPLACEMENT_NONE:
+parameter +literal
DEM_DISPLACEMENT_FULL:
+literal
DEM_DISPLACEMENT_PRIO_OCC:
+literal
DemEventMemoryEntryStorageTrigger: DEM_TRIGGER_ON_FDC_THRESHOLD:
+literal
upperMultiplicity = 1 DEM_TRIGGER_ON_CONFIRMED:
defaultValue = DEM_TRIGGER_ON_TEST_FAILED EcucEnumerationLiteralDef
+literal DEM_TRIGGER_ON_TEST_FAILED:
+literal
DemOccurrenceCounterProcessing: DEM_PROCESS_OCCCTR_TF:
+parameter
+literal
DEM_PROCESS_OCCCTR_CDTC:
+literal
DemTypeOfFreezeFrameRecordNumeration: DEM_FF_RECNUM_CALCULATED:
+parameter
+literal
DEM_FF_RECNUM_CONFIGURED:
DemGroupOfDTC:
+subContainer lowerMultiplicity = 0
+parameter DemDtcStatusAvailabilityMask:
EcucIntegerParamDef
min = 0
max = 255
Figure 10.29: DemPrimaryMemory configuration overview
10.2.6.3 DemMirrorMemory

AUTOSAR CP R20-11
Container Name DemMirrorMemory

Description This container contains the mirror event memory specific parameters of
the Dem module.
Name DemMaxNumberEventEntryMirror [ECUC_Dem_00688]

Parent Container DemMirrorMemory
Description Maximum number of events which can be stored in the mirror memory
Multiplicity 1
Range 1 .. 255
Default Value
Value
Class
Link time –
Post-build time –
10.2.6.4 DemUserDefinedMemory

Container Name DemUserDefinedMemory
Description This container contains the user defined event memory specific
parameters of the Dem module.
Name DemDtcStatusAvailabilityMask [ECUC_Dem_00652]

Parent Container DemUserDefinedMemory
Description Mask for the supported DTC status bits by the Dem. This mask is used
in the positive response of UDS service 0x19.
Multiplicity 1
Range 0 .. 255
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemEnvironmentDataCapture [ECUC_Dem_00895]

Description DemEnvironmentDataCapture defines the point in time, when the data
actually is captured.
Multiplicity 0..1
Range DEM_CAPTURE_ASYNC The data capturing is postponed to the
HRONOUS_TO_REPORT next cycle of the Dem_Mainfunction.
ING (This means that there is a minimum
delay between report of the failure and
capturing the data).
DEM_CAPTURE_SYNCH The data is captured immediately
RONOUS_TO_REPORTI within the context of
NG Dem_SetEventStatus.
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemEventDisplacementStrategy [ECUC_Dem_00742]

Description This configuration switch defines, whether support for event
displacement is enabled or not, and which displacement strategy is
followed.
Multiplicity 1
Range DEM_DISPLACEMENT_F Event memory entry displacement is
ULL enabled, by consideration of priority
active/passive status, and occurrence.
DEM_DISPLACEMENT_N Event memory entry displacement is
ONE disabled.
DEM_DISPLACEMENT_P Event memory entry displacement is
RIO_OCC enabled, by consideration of priority
and occurrence (but without
active/passive status).
Value

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemEventMemoryEntryStorageTrigger [ECUC_Dem_00797]

Description Configures the primary trigger to allocate an event memory entry.
Multiplicity 1
Default Value DEM_TRIGGER_ON_TEST_FAILED
Value
Class
Link time –
Post-build time –
Name DemMaxNumberEventEntryUserDefined [ECUC_Dem_00691]

Description Maximum number of events which can be stored in the user defined
memory.
Multiplicity 1
Range 1 .. 255
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemOccurrenceCounterProcessing [ECUC_Dem_00767]

Description This configuration switch defines the consideration of the fault
confirmation process for the occurrence counter. For OBD and mixed
systems (OBD/non OBD, refer to DemOBDSupport) configuration
switch shall always set to DEM_PROCESS_OCCCTR_TF.
Multiplicity 1
Range DEM_PROCESS_OCCCT the occurrence counter is triggered by
R_CDTC the TestFailed bit if the fault
confirmation was successful
(ConfirmedDTC bit is set)
DEM_PROCESS_OCCCT the occurrence counter is only
R_TF triggered by the TestFailed bit (and the
fault confirmation is not considered)
This parameter is mandatory in case of
J1939.
Value
Class
Link time –
Post-build time –
Name DemTypeOfFreezeFrameRecordNumeration [ECUC_Dem_00778]

Description This parameter defines the type of assigning freeze frame record
numbers for event-specific freeze frame records.
Multiplicity 1
Range DEM_FF_RECNUM_CAL freeze frame records will be numbered
CULATED consecutive starting by 1 in their
chronological order
DEM_FF_RECNUM_CON freeze frame records will be numbered
FIGURED based on the given configuration in
their chronological order
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemUserDefinedMemoryIdentifier [ECUC_Dem_00903]

Description Identifier used by external tester to identify the User defined event
memory.
Multiplicity 1
Range 0 .. 255
Default Value
Value
Class
Link time –
Post-build time –
Included Containers
DemGroupOfDTC 0..65535 This container contains the configuration (parameters)
for DTC groups.

AUTOSAR CP R20-11
DemEventMemorySet:
DemMaxNumberEventEntryUserDefined:
+subContainer EcucIntegerParamDef
+parameter min = 1
DemUserDefinedMemory:
max = 255
upperMultiplicity = 30 DemUserDefinedMemoryIdentifier:
min = 0
max = 255
+literal
DemEnvironmentDataCapture: DEM_CAPTURE_SYNCHRONOUS_TO_REPORTING:
+parameter EcucEnumerationParamDef EcucEnumerationLiteralDef
upperMultiplicity = 1 DEM_CAPTURE_ASYNCHRONOUS_TO_REPORTING:
+literal
DemEventDisplacementStrategy: DEM_DISPLACEMENT_NONE:
DEM_DISPLACEMENT_FULL:
+literal
DEM_DISPLACEMENT_PRIO_OCC:
+literal
DemEventMemoryEntryStorageTrigger: DEM_TRIGGER_ON_FDC_THRESHOLD:
DEM_TRIGGER_ON_CONFIRMED:
defaultValue = DEM_TRIGGER_ON_TEST_FAILED EcucEnumerationLiteralDef
+literal
DEM_TRIGGER_ON_TEST_FAILED:
+literal DEM_PROCESS_OCCCTR_TF:
DemOccurrenceCounterProcessing:
+literal
DEM_PROCESS_OCCCTR_CDTC:
DemTypeOfFreezeFrameRecordNumeration: +literal
DEM_FF_RECNUM_CALCULATED:
+literal
DEM_FF_RECNUM_CONFIGURED:
+subContainer DemGroupOfDTC: EcucParamConfContainerDef
DemDtcStatusAvailabilityMask:
min = 0
max = 255
Figure 10.30: DemUserDefinedMemory configuration overview
10.2.7 Debouncing
10.2.7.1 DemDebounceAlgorithmClass

AUTOSAR CP R20-11

Container Name DemDebounceAlgorithmClass
Description Debounce algorithm class: counter based, time based, or monitor
internal.
Container Choices
DemDebounceCounter 0..1 This container contains the configuration (parameters)
Based for counter based debouncing.
DemDebounceMonitor 0..1 This container contains the configuration (parameters)
Internal for monitor internal debouncing.
DemDebounceTimeBase 0..1 This container contains the configuration (parameters)
for time based debouncing.
DemEventParameter:
+subContainer
DemDebounceAlgorithmClass: DemDebounceTimeBase:
EcucChoiceContainerDef EcucParamConfContainerDef DemDebounceTimeBaseRef:
+choice +reference EcucReferenceDef
EcucParamConfContainerDef DemDebounceCounterBasedClassRef:
+choice +reference EcucReferenceDef
DemDebounceMonitorInternal:
EcucParamConfContainerDef DemCallbackGetFDC:
+choice +subContainer EcucParamConfContainerDef
+parameter
EcucFunctionNameDef
Figure 10.31: DemDebounceAlgorithmClass configuration overview
10.2.7.2 DemDebounceCounterBased

AUTOSAR CP R20-11
Container Name DemDebounceCounterBased

Parent Container DemDebounceAlgorithmClass
Description This container contains the configuration (parameters) for counter
based debouncing.
Name DemDebounceCounterBasedClassRef [ECUC_Dem_00883]

Parent Container DemDebounceCounterBased
Description This reference selects the DemDebounceCounterBasedClass applied
for the debouncing of the DemEventParameter.
Multiplicity 1
Type Reference to DemDebounceCounterBasedClass
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Scope / Dependency
+choice
EcucParamConfContainerDef DemDebounceCounterBasedClassRef: DemDebounceCounterBasedClass:
lowerMultiplicity = 0 upperMultiplicity = 1 upperMultiplicity = 65535
Figure 10.32: DemDebounceCounterBased configuration overview
10.2.7.3 DemDebounceCounterBasedClass

Container Name DemDebounceCounterBasedClass
Description This container contains the configuration of Debounce Counter Based
Class

AUTOSAR CP R20-11
Name DemCounterBasedFdcThresholdStorageValue [ECUC_Dem_00914]

Parent Container DemDebounceCounterBasedClass
Description Threshold to allocate an event memory entry and to capture the Freeze
Frame.
Multiplicity 0..1
Range 1 .. 32767
Default Value
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemDebounceBehavior [ECUC_Dem_00786]

Description This parameter defines how the event debounce algorithm will behave,
if a related enable condition is not fulfilled or ControlDTCSetting of the
related event is disabled.
Multiplicity 1
Range DEM_DEBOUNCE_FREE The event debounce counter will be
ZE frozen with the current value and will
not change while a related enable
condition is not fulfilled or
ControlDTCSetting of the related event
is disabled. After all related enable
conditions are fulfilled and
is enabled again, the event qualification
will continue with the next report of the
event (i.e. SetEventStatus).
DEM_DEBOUNCE_RESE The event debounce counter will be
T reset to initial value if a related enable
is disabled. The qualification of the
event will be restarted with the next
valid event report.
Value

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemDebounceCounterDecrementStepSize [ECUC_Dem_00635]

Description Defines the step size for decrementation of the internal debounce
counter (PREPASSED).
Multiplicity 1
Range 1 .. 32768
Default Value
Value
Class
Link time –
Post-build time –
Name DemDebounceCounterFailedThreshold [ECUC_Dem_00618]

Description Defines the value of the internal debounce counter, which indicates the
failed status.
Multiplicity 1
Range 1 .. 32767
Default Value
Value
Class
Link time –
Post-build time –
Name DemDebounceCounterIncrementStepSize [ECUC_Dem_00637]

Description Defines the step size for incrementation of the internal debounce
counter (PREFAILED).
Multiplicity 1
Range 1 .. 32767
Default Value
Value

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemDebounceCounterJumpDown [ECUC_Dem_00685]

Description Switch for the activation of Jump-Down.
true: Jump-Down activated false: Jump-Down deactivated

Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
Name DemDebounceCounterJumpDownValue [ECUC_Dem_00638]

Description Jump-Down value of the internal debounce counter which is taken as
initialization value for the counter when the respective step-down
occurs.
Multiplicity 1
Range -32768 .. 32767
Default Value 0
Value
Class
Link time –
Post-build time –
Name DemDebounceCounterJumpUp [ECUC_Dem_00686]

Description Switch for the activation of Jump-Up.
true: Jump-Up activated false: Jump-Up deactivated

Multiplicity 1
Default Value

AUTOSAR CP R20-11

Value
Class
Link time –
Post-build time –
Name DemDebounceCounterJumpUpValue [ECUC_Dem_00639]

Description Jump-Up value of the internal debounce counter which is taken as
initialization value for the counter when the respective step-up occurs.
Multiplicity 1
Range -32768 .. 32767
Default Value 0
Value
Class
Link time –
Post-build time –
Name DemDebounceCounterPassedThreshold [ECUC_Dem_00636]

Description Defines the value of the internal debounce counter, which indicates the
passed status.
Multiplicity 1
Range -32768 .. -1
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemDebounceCounterStorage [ECUC_Dem_00791]

Description Switch to store the debounce counter value non-volatile or not.
true: debounce counter value shall be stored non-volatile false:

debounce counter value is volatile
Multiplicity 1
Default Value false
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
DemConfigSet:
+subContainer
DemDebounceCounterBasedClass: DemDebounceCounterIncrementStepSize:
EcucParamConfContainerDef +parameter EcucIntegerParamDef
DemDebounceCounterDecrementStepSize:
max = 32768
min = 1
DemDebounceCounterFailedThreshold:
max = 32767
min = 1
DemDebounceCounterPassedThreshold:
max = -1
min = -32768
DemDebounceCounterJumpUp:
DemDebounceCounterJumpDown:
DemDebounceCounterJumpDownValue:
EcucIntegerParamDef
+parameter
max = 32767
min = -32768
defaultValue = 0
DemDebounceCounterJumpUpValue:
EcucIntegerParamDef
+parameter
max = 32767
min = -32768
defaultValue = 0
DemDebounceBehavior: +literal DEM_DEBOUNCE_FREEZE:

+parameter
+literal DEM_DEBOUNCE_RESET:
DemDebounceCounterStorage:
+parameter
EcucBooleanParamDef
DemCounterBasedFdcThresholdStorageValue:
EcucIntegerParamDef
+parameter
max = 32767
min = 1
Figure 10.33: DemDebounceCounterBasedClass configuration overview

AUTOSAR CP R20-11
10.2.7.4 DemDebounceTimeBase

Container Name DemDebounceTimeBase
Description This container contains the configuration (parameters) for time based
debouncing.
Name DemDebounceTimeBaseRef [ECUC_Dem_00891]

Parent Container DemDebounceTimeBase
Description This reference selects the DemDebounceTimeBaseClass applied for
the debouncing of the DemEventParameter.
Multiplicity 1
Type Reference to DemDebounceTimeBaseClass
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Scope / Dependency
+choice
DemDebounceTimeBase:
DemDebounceTimeBaseRef: EcucParamConfContainerDef
upperMultiplicity = 1 +reference EcucReferenceDef +destination
Figure 10.34: DemDebounceTimeBase configuration overview
10.2.7.5 DemDebounceTimeBaseClass

Container Name DemDebounceTimeBaseClass
Description This container contains the configuration of Debounce Time Based
Class.

AUTOSAR CP R20-11
Name DemDebounceBehavior [ECUC_Dem_00789]

Parent Container DemDebounceTimeBaseClass
Description This parameter defines how the event debounce algorithm will behave,
if a related enable condition is not fulfilled or ControlDTCSetting of the
related event is disabled.
Multiplicity 1
Range DEM_DEBOUNCE_FREE The event debounce timer will be
ZE frozen with the current value and will
not change while a related enable
is disabled. After all related enable
conditions are fulfilled and
is enabled again, the event qualification
will continue with the next report of the
event (i.e. SetEventStatus).
DEM_DEBOUNCE_RESE The event debounce timer will be reset
T to initial value if a related enable
is disabled.
The qualification of the event will be
restarted with the next valid event
report.
Value
Class
Link time –
Post-build time –
Name DemDebounceTimeFailedThreshold [ECUC_Dem_00716]

Description Defines the time out duration for "Event Failed" qualification.

Multiplicity 1
Range [0.001 .. 3600]
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemDebounceTimePassedThreshold [ECUC_Dem_00717]

Description Defines the time out duration for "Event Passed" qualification.

Multiplicity 1
Range [0.001 .. 3600]
Default Value
Value
Class
Link time –
Post-build time –
Name DemTimeBasedFdcThresholdStorageValue [ECUC_Dem_00915]

Description Threshold to allocate an event memory entry and to capture the Freeze
Frame.
Multiplicity 0..1
Range [0.001 .. 3600]
Default Value
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
DemConfigSet:
+subContainer
DemDebounceTimeBaseClass: DemDebounceTimeFailedThreshold:
EcucParamConfContainerDef EcucFloatParamDef
+parameter
upperMultiplicity = 65535 min = 0.001
lowerMultiplicity = 0 max = 3600.0
DemDebounceTimePassedThreshold:
min = 0.001
max = 3600.0
+literal
DemDebounceBehavior: DEM_DEBOUNCE_FREEZE:
+literal DEM_DEBOUNCE_RESET:
DemTimeBasedFdcThresholdStorageValue:
EcucFloatParamDef
+parameter
max = 3600
min = 0.001
Figure 10.35: DemDebounceTimeBaseClass configuration overview
10.2.7.6 DemDebounceMonitorInternal

Container Name DemDebounceMonitorInternal
Description This container contains the configuration (parameters) for monitor
internal debouncing.
Included Containers
DemCallbackGetFDC 0..1 DemCallbackGetFDC specifies the callback (parameter
DemCallbackGetFDCFnc is present) or R-Port (no
parameter DemCallbackGetFDCFnc is present) to
retrieve the fault detection counter value. In case no
container is configured, no fault detection counter will be
available.

AUTOSAR CP R20-11
DemDebounceAlgorithmClass: DemDebounceMonitorInternal: DemCallbackGetFDC:

EcucChoiceContainerDef +choice EcucParamConfContainerDef +subContainer EcucParamConfContainerDef

+parameter
EcucFunctionNameDef
Figure 10.36: DemDebounceMonitorInternal configuration overview
10.2.8 Callbacks
10.2.8.1 DemCallbackClearEventAllowed

Container Name DemCallbackClearEventAllowed
Description The presence of this container indicates that the Dem has access to a
"ClearEventAllowed" callback.
In case there is a DemCallbackClearEventAllowedFnc, this parameter

In case there is no DemCallbackClearEventAllowedFnc, the Dem will

have an R-Port requiring the interface CallbackClearEventAllowed
whose name is generated by using the unique callback-prefix followed
by the event name.
Name DemCallbackClearEventAllowedFnc [ECUC_Dem_00609]

Parent Container DemCallbackClearEventAllowed
Description Function name of prototype "ClearEventAllowed".
Multiplicity 0..1
Default Value
Regular Expression
Multiplicity
Value
Configuration Class
Link time –
Post-build time –

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemClearEventAllowedBehavior [ECUC_Dem_00788]

Parent Container DemCallbackClearEventAllowed
Description Defines the resulting UDS status byte for the related event, which must
not be cleared according to the ClearEventAllowed callback.
Multiplicity 1
Range DEM_NO_STATUS_BYTE The UDS status byte keeps
_CHANGE unchanged.
DEM_ONLY_THIS_CYCL The <...>ThisOperationCycle and
E_AND_READINESS readiness bits of the UDS status byte
are reset.
Default Value DEM_NO_STATUS_BYTE_CHANGE
Value
Class
Link time –
Post-build time –
10.2.8.2 DemCallbackDTCStatusChanged

Container Name DemCallbackDTCStatusChanged
Description The presence of this container indicates, that the Dem has access to a
"DTCStatusChanged" callback, which the Dem will call to notify other
components about the change in the status of a DTC.
In case there is a DemCallbackDTCStatusChangedFnc, this parameter

In case there is no DemCallbackDTCStatusChangedFnc, the Dem will

have an R-Port requiring the interface CallbackDTCStatusChanged
by the event name.
Status change notifications are supported for DTCs in primary memory

only.

AUTOSAR CP R20-11
Name DemCallbackDTCStatusChangedFnc [ECUC_Dem_00627]

Parent Container DemCallbackDTCStatusChanged
Description Function name of prototype "DTCStatusChanged".
Multiplicity 0..1
Default Value
Regular Expression
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
10.2.8.3 DemCallbackJ1939DTCStatusChanged

Container Name DemCallbackJ1939DTCStatusChanged


by the event name.

only.

AUTOSAR CP R20-11

Parent Container DemCallbackJ1939DTCStatusChanged
Multiplicity 0..1
Default Value
Regular Expression
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
10.2.8.4 DemCallbackOBDDTCStatusChanged

Container Name DemCallbackOBDDTCStatusChanged


by the event name.

only.

AUTOSAR CP R20-11

Parent Container DemCallbackOBDDTCStatusChanged
Multiplicity 0..1
Default Value
Regular Expression
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
upperMultiplicity = 1 +parameter EcucFunctionNameDef
+subContainer
DemGeneralOBD: DemCallbackOBDDTCStatusChanged: DemCallbackDTCStatusChangedFnc:


+subContainer
DemGeneralJ1939: DemCallbackJ1939DTCStatusChanged: DemCallbackDTCStatusChangedFnc:


Figure 10.37: Notification of DTC status changed configuration overview
10.2.8.5 DemCallbackGetFDC

Container Name DemCallbackGetFDC
Parent Container DemDebounceMonitorInternal

AUTOSAR CP R20-11
Description DemCallbackGetFDC specifies the callback (parameter

DemCallbackGetFDCFnc is present) or R-Port (no parameter
DemCallbackGetFDCFnc is present) to retrieve the fault detection
counter value. In case no container is configured, no fault detection
counter will be available.
Name DemCallbackGetFDCFnc [ECUC_Dem_00631]

Parent Container DemCallbackGetFDC
Description This parameter defines the name of the function that the Dem will call
to retrieve the fault-detection counter value from a complex driver.
Multiplicity 0..1
Default Value
Regular Expression
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
10.2.8.6 DemCallbackEventDataChanged

Container Name DemCallbackEventDataChanged
Description The presence of this container indicates that the Dem has access to an
"EventDataChanged" callback.
In case there is a DemCallbackEventDataChangedFnc, this parameter

In case there is no DemCallbackEventDataChangedFnc, the Dem will

have an R-Port requiring the interface CallbackEventDataChanged
by the event name.

AUTOSAR CP R20-11
Name DemCallbackEventDataChangedFnc [ECUC_Dem_00608]

Parent Container DemCallbackEventDataChanged
Description Function name of prototype "EventDataChanged"
Multiplicity 0..1
Default Value
Regular Expression
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
10.2.8.7 DemCallbackEventUdsStatusChanged

Container Name DemCallbackEventUdsStatusChanged
Description The presence of this container indicates, that the Dem has access to
an "EventUdsStatusChanged" callback, which the Dem will call to
notify other components about the change in the status of an event.
In case there is a DemCallbackEventUdsStatusChangedFnc, this

parameter defines the name of the function that the Dem will call.
In case there is no DemCallbackEventUdsStatusChangedFnc, the

Dem will have an R-Port requiring the interface
CallbackEventUdsStatusChanged, whose name is generated by using
the unique callback-prefix followed by the event name.
Name DemCallbackEventUdsStatusChangedFnc [ECUC_Dem_00629]

Parent Container DemCallbackEventUdsStatusChanged
Description Function name of prototype "Dem_CBEventUdsStatusChanged"
Multiplicity 0..1
Default Value
Regular Expression

AUTOSAR CP R20-11

Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
10.2.8.8 DemCallbackMonitorStatusChanged

Container Name DemCallbackMonitorStatusChanged
an "MonitorStatusChanged" callback, which the Dem will call to notify
other components about the change in the status of an event.
In case there is a DemCallbackMonitorStatusChangedFnc, this

parameter defines the name of the function that the Dem will call.
In case there is no DemCallbackMonitorStatusChangedFnc, the Dem

will have an R-Port requiring the interface
CallbackMonitorStatusChanged, whose name is generated by using
the unique callback-prefix followed by the event name.
Name DemCallbackMonitorStatusChangedFnc [ECUC_Dem_00937]

Parent Container DemCallbackMonitorStatusChanged
Description Function name of prototype "<Module>_DemTriggerOnMonitorStatus"
Multiplicity 0..1
Default Value
Regular Expression
Multiplicity
Value

AUTOSAR CP R20-11

Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
DemEventParameter:
EcucParamConfContainerDef DemCallbackEventUdsStatusChanged: DemCallbackEventUdsStatusChangedFnc:
DemCallbackMonitorStatusChanged: DemCallbackMonitorStatusChangedFnc:
Figure 10.38: Notification of event status changed configuration overview
10.2.8.9 DemCallbackInitMForE

Container Name DemCallbackInitMForE
an "InitMonitorForEvent" callback, which the Dem will call to initialize a
monitor.
In case the container has a DemCallbackInitMForEFnc, this parameter

In case there is no DemCallbackInitMForEFnc, the Dem will have an

R-Port requiring the interface CallbackInitMonitorForEvent, whose
name is generated by using the unique callback-prefix followed by the
event name.
Name DemCallbackInitMForEFnc [ECUC_Dem_00601]

Parent Container DemCallbackInitMForE
Description Function name of prototype "InitMonitorForEvent".
Multiplicity 0..1
Default Value

AUTOSAR CP R20-11
Regular Expression
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Scope / Dependency
10.2.8.10 DemClearDTCNotification

Container Name DemClearDTCNotification
Description Contains callback function definition which are called during clear DTC
operations.
Multiplicity
Name DemClearDtcNotificationFnc [ECUC_Dem_00926]

Parent Container DemClearDTCNotification
Description Notification callback function name which is called on a clear DTC
operation (refer to <Module>_ClearDtcNotification).
Multiplicity 0..1
Default Value
Regular Expression
Multiplicity
Value
Configuration Class
Link time –
Post-build time –

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Name DemClearDtcNotificationTime [ECUC_Dem_00927]

Parent Container DemClearDTCNotification
Description Configure, whether the callback shall be called on start of a clear or
after finishing a clear DTC operation (refer to
<Module>_ClearDtcNotification)
Multiplicity 1
Range FINISH
START
Value
Class
Link time –
Post-build time –
10.2.8.11 DemCallbackEventSyncStorageProcessed

Container Name DemCallbackEventSyncStorageProcessed
Description The presence of this container indicates that the Dem will call the
configured callback after an event status reported with
Dem_SetEventFailedWithSyncFreezeFrame is finished and the Dem is
ready to process a next call for this event.
Tags:
atp.Status=draft
Multiplicity
Configuration Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemCallbackEventSyncStorageProcessedFnc [ECUC_Dem_00972]

Parent Container DemCallbackEventSyncStorageProcessed
Description Function name of prototype CallbackEventSyncStorageProcessed.
Tags:
atp.Status=draft
Multiplicity 1
Default Value
Regular Expression
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
10.2.9 Event related data
DemExtendedDataClassRef: DemFreezeFrameClassRef:
DemExtendedDataClass: DemFreezeFrameClass:

DemExtendedDataRecordClassRef: DemDidClassRef: EcucReferenceDef

EcucReferenceDef
DemExtendedDataRecordClass: DemDataElementClassRef: DemDidClass:

EcucParamConfContainerDef +reference EcucReferenceDef EcucParamConfContainerDef

+subContainer
+destination +reference
EcucChoiceContainerDef DemDidDataElementClassRef:
EcucReferenceDef
+destination upperMultiplicity = 255
DemInternalDataElementClass: EcucParamConfContainerDef
+choice
+choice DemExternalCSDataElementClass: EcucParamConfContainerDef
+choice
+destination
Figure 10.39: Event related data configuration overview
10.2.9.1 DemFreezeFrameClass

AUTOSAR CP R20-11

Container Name DemFreezeFrameClass
Description This container contains the combinations of DIDs for a non OBD2 and
WWH-OBD relevant freeze frame class.
Name DemDidClassRef [ECUC_Dem_00707]

Parent Container DemFreezeFrameClass
Description Reference to the DID elements which shall be contained in the freeze
frame.
Attributes:
requiresIndex=true
Multiplicity 1..255
Type Reference to DemDidClass
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
DemConfigSet:
DemPidClass: DemPidIdentifier:
+subContainer EcucParamConfContainerDef EcucIntegerParamDef

lowerMultiplicity = 0 +parameter min = 0
+subContainer
DemPidDataElementClassRef:
DemPidDataElement: EcucReferenceDef
+reference
+destination
+subContainer
DemGeneral: DemDataElementClass:
EcucParamConfContainerDef EcucChoiceContainerDef
DemDidIdentifier: EcucIntegerParamDef
lowerMultiplicity = 1 min = 0 upperMultiplicity = 65535
max = 65535
+parameter DemDidDataElementClassRef:
EcucReferenceDef
DemDidClass: +reference lowerMultiplicity = 1
+subContainer
lowerMultiplicity = 0 +subContainer
DemDTCAttributes: EcucParamConfContainerDef
+destination
DemDidClassRef: EcucReferenceDef
DemFreezeFrameClassRef: DemFreezeFrameRecNumClassRef:
+reference
DemFreezeFrameClass:
+subContainer
+destination
DemFreezeFrameRecNumClass:
+subContainer EcucParamConfContainerDef DemFreezeFrameRecordClassRef:
+destination
DemFreezeFrameRecordClass: EcucParamConfContainerDef
+subContainer
+parameter +parameter +parameter
DemFreezeFrameRecordTrigger: DemFreezeFrameRecordUpdate: DemFreezeFrameRecordNumber:

EcucEnumerationParamDef EcucEnumerationParamDef EcucIntegerParamDef
lowerMultiplicity = 1 lowerMultiplicity = 1 min = 0

upperMultiplicity = 1 upperMultiplicity = 1 max = 254
Figure 10.40: DemFreezeFrameClass configuration overview

AUTOSAR CP R20-11
10.2.9.2 DemFreezeFrameRecordClass

Container Name DemFreezeFrameRecordClass
Description This container contains a list of dedicated, different freeze frame record
numbers.
Name DemFreezeFrameRecordNumber [ECUC_Dem_00777]

Parent Container DemFreezeFrameRecordClass
Description This parameter defines a record number for a freeze frame record.
This record number is unique per freeze frame record number class.
Multiplicity 1
Range 0 .. 254
Default Value
Value
Class
Link time –
Post-build time –
Name DemFreezeFrameRecordTrigger [ECUC_Dem_00803]

Description Defines the trigger to store the FreezeFrameRecord.
Tags:
atp.Status=draft
Multiplicity 1
DEM_TRIGGER_ON_EVE EventMemory entries are triggered
RY_TEST_FAILED every time the event is reported as
FAILED or PRE_FAILED results in
failed.
DEM_TRIGGER_ON_PE Event Memory entries are triggered if
NDING the UDS status bit 2 (pendingDTC)

AUTOSAR CP R20-11

T_FAILED_THIS_OPERA the UDS status bit 1
TION_CYCLE (testFailedThisOperationCycle)
Value
Class
Link time –
Post-build time –
Name DemFreezeFrameRecordUpdate [ECUC_Dem_00802]

Description This parameter defines the case, when the freeze frame record is
stored/updated.
Multiplicity 1
Range DEM_UPDATE_RECORD This record is only captured for new
_NO event memory entries.
DEM_UPDATE_RECORD This record is captured every time.
_YES
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
DemFreezeFrameRecordNumber:
DemFreezeFrameRecordClass: EcucIntegerParamDef
+parameter min = 0
+literal
DemFreezeFrameRecordUpdate: DEM_UPDATE_RECORD_NO:
+parameter
+literal DEM_UPDATE_RECORD_YES:
DemFreezeFrameRecordTrigger: +literal DEM_TRIGGER_ON_CONFIRMED:

+literal
upperMultiplicity = 1 DEM_TRIGGER_ON_FDC_THRESHOLD:
+parameter
+literal
DEM_TRIGGER_ON_PENDING:
+literal
DEM_TRIGGER_ON_EVERY_TEST_FAILED:
+literal
DEM_TRIGGER_ON_TEST_FAILED_THIS_OPERATION_CYCLE:
Figure 10.41: DemFreezeFrameRecordClass configuration overview
10.2.9.3 DemFreezeFrameRecNumClass

Container Name DemFreezeFrameRecNumClass
Description This container contains a list of dedicated, different freeze frame record
numbers assigned to an event. The order of record numbers in this list
is assigned to the chronological order of the according freeze frame
records.
Name DemFreezeFrameRecordClassRef [ECUC_Dem_00800]

Parent Container DemFreezeFrameRecNumClass
Description This parameter references record number(s) for a freeze frame record.
Attributes:
requiresIndex=true
Multiplicity 1..254
Type Reference to DemFreezeFrameRecordClass
Multiplicity

AUTOSAR CP R20-11

Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
10.2.9.4 DemExtendedDataClass

Container Name DemExtendedDataClass
Description This class contains the combinations of extended data records for an
extended data class.
Name DemExtendedDataRecordClassRef [ECUC_Dem_00774]

Parent Container DemExtendedDataClass
Description This reference contains the link to an extended data class record.
Attributes:
requiresIndex=true
Multiplicity 1..253
Type Reference to DemExtendedDataRecordClass
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Scope / Dependency

AUTOSAR CP R20-11
DemDataElementClass: DemInternalDataElementClass:
DemGeneral:
EcucChoiceContainerDef +choice EcucParamConfContainerDef
EcucParamConfContainerDef +subContainer
DemExternalCSDataElementClass:
+choice
DemExternalSRDataElementClass:
+destination EcucParamConfContainerDef
+subContainer
DemExtendedDataRecordClass: DemDataElementClassRef: lowerMultiplicity = 0
+reference
DemExtendedDataRecordUpdate: +literal
DEM_UPDATE_RECORD_NO:
+parameter
DEM_UPDATE_RECORD_YES:
DemExtendedDataRecordNumber:
max = 239
min = 1
DemExtendedDataRecordTrigger: +literal DEM_TRIGGER_ON_CONFIRMED:

+literal
upperMultiplicity = 1 DEM_TRIGGER_ON_FDC_THRESHOLD:
+literal
DEM_TRIGGER_ON_PENDING:
+parameter
+literal
DEM_TRIGGER_ON_PASSED:
+literal
DEM_TRIGGER_ON_MIRROR:
+destination
DemExtendedDataClass: DemExtendedDataRecordClassRef:
+reference
+subContainer lowerMultiplicity = 0 upperMultiplicity = 253
+destination
DemDTCAttributes: DemExtendedDataClassRef:

Figure 10.42: DemExtendedDataClass configuration overview

AUTOSAR CP R20-11
10.2.9.5 DemExtendedDataRecordClass

Container Name DemExtendedDataRecordClass
Description This container contains the configuration (parameters) for an extended
data record class.
It is assembled out of one or several data elements.

Name DemExtendedDataRecordNumber [ECUC_Dem_00666]

Parent Container DemExtendedDataRecordClass
Description This configuration parameter specifies an unique identifier for an
extended data record.
One or more extended data records can be assigned to one diagnostic

event/DTC.
0x00 is reserved by ISO (therefore the minimal value equals 1)
0xF0 to 0xFF are reserved by ISO (therefore the maximal value equals
239)
Multiplicity 1
Range 1 .. 239
Default Value
Value
Class
Link time –
Post-build time –
Name DemExtendedDataRecordTrigger [ECUC_Dem_00804]

Description Defines the trigger to store the ExtendedDataRecord.
Multiplicity 0..1
Range DEM_TRIGGER_ON_CO ExtendedDataRecord will be stored
NFIRMED when the UDS status confirmed bit
DEM_TRIGGER_ON_FD ExtendedDataRecord will be stored
C_THRESHOLD when the FDC reaches its threshold.
DEM_TRIGGER_ON_MIR ExtendedDataRecord will be stored
ROR when the event is transferred to the
mirror memory.
DEM_TRIGGER_ON_PAS ExtendedDataRecord will be stored
SED when the event is reported as passed
(testFailed bit transition 1 --> 0).

AUTOSAR CP R20-11
DEM_TRIGGER_ON_PE ExtendedDataRecord will be stored

NDING when the UDS status pending bit
DEM_TRIGGER_ON_TES ExtendedDataRecord will be stored
T_FAILED when the UDS status test failed bit
Value
Class
Link time –
Post-build time –
Name DemExtendedDataRecordUpdate [ECUC_Dem_00621]

Description This extended data record is captured if the configured trigger
condition in "DemExtendedDataRecordTrigger" is fulfilled.
Multiplicity 0..1
Range DEM_UPDATE_RECORD This extended data record is only
_NO captured for new event memory
entries.
DEM_UPDATE_RECORD This extended data record is captured
_YES every time.
Value
Class
Link time –
Post-build time –
Name DemDataElementClassRef [ECUC_Dem_00771]

Attributes:
requiresIndex=true
Multiplicity 1..255
Multiplicity
Value
Configuration Class
Link time –
Post-build time –

AUTOSAR CP R20-11

Class
Link time –
Post-build time –
Scope / Dependency
10.2.10 Data elements
10.2.10.1 DemDataElementClass

Container Name DemDataElementClass
Description This container contains the configuration (parameters) for an
internal/external data element class.
Container Choices
DemExternalCSData 0..1 This container contains the configuration (parameters)
ElementClass for an external client/server based data element class.
It defines, how the Dem can obtain the value of the data
element from either a SW-C or another BSW module.
Whether a client/server port or a C function-call is used,
is defined by DemDataElementUsePort.
DemExternalSRData 0..1 This container contains the configuration (parameters)
ElementClass for an external sender/receiver based data element
class. It defines, how the Dem can obtain the value of
the data element from a SW-C, by using a
sender/receiver port.
DemInternalDataElement 0..1 This container contains the configuration (parameters)
Class for an internal data element class.

AUTOSAR CP R20-11
DemGeneral:
+subContainer
DemDataElementClass: DemInternalDataElementClass: DemDataElementDataSize:

EcucChoiceContainerDef EcucParamConfContainerDef EcucIntegerParamDef
upperMultiplicity = 65535 lowerMultiplicity = 0 max = 255
+parameter DemInternalDataElement:
DemExternalCSDataElementClass: DemDataElementArraySize:
+parameter
DemDataElementDataType:
+choice DemDataElementUsePort:
DemDataElementReadFnc:
DemDataElementProvideMonitorData:
EcucBooleanParamDef
+parameter
DemExternalSRDataElementClass: DemDataElementArraySize:
+parameter
DemSRDataElementClass:
+subContainer EcucChoiceContainerDef
Figure 10.43: DemDataElementClass configuration overview

AUTOSAR CP R20-11
DemDataElementDataType: +literal BOOLEAN:

upperMultiplicity = 1 +literal UINT8:
+literal SINT8:
+literal UINT16:
+literal SINT16:
+literal UINT32:
+literal SINT32:
+literal UINT8_N:
+literal SINT8_N:
+literal UINT16_N:
+literal SINT16_N:
+literal UINT32_N:
+literal SINT32_N:
+literal FLOAT:
+literal FLOAT_N:
Figure 10.44: DemDataElementDataType configuration overview
10.2.10.2 DemDataElementInstance

Container Name DemDataElementInstance
Parent Container DemSRDataElementClass
Description Instance Reference to the primitive data in a port where the data
element is typed with an ApplicationPrimitveDataType or an
ImplementationDataType.

AUTOSAR CP R20-11
Name DemDataElementInstanceRef [ECUC_Dem_00861]

Parent Container DemDataElementInstance
Description Instance Reference to the primitive data which shall be read or written.
Supported are VariableDataPrototypes in SenderReceiverInterfaces
and NvDataInterfaces and ParameterDataPrototypes in
ParameterInterfaces (read only). This reference is applicable if the
AutosarDataPrototype is typed with a ApplicationPrimitiveDataType of
category VALUE or BOOLEAN or if the AutosarDataPrototype is typed
with a ImplementationDataType of category VALUE or
TYPE_REFERENCE that in turn boils down to VALUE
Multiplicity 1
Type Instance reference to AUTOSAR-DATA-PROTOTYPE context: ROOT-
SW-COMPOSITION-PROTOTYPE SW-COMPONENT-PROTOTYPE
PORT-PROTOTYPE
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Scope / Dependency
10.2.10.3 DemDidClass

Container Name DemDidClass
Description This container contains the configuration (parameters) for a data Id
class. It is assembled out of one or several data elements.
Name DemDidIdentifier [ECUC_Dem_00650]

Parent Container DemDidClass
Description Identifier of the Data ID.
Multiplicity 1
Range 0 .. 65535
Default Value
Value
Class
Link time –
Post-build time –
Scope / Dependency

AUTOSAR CP R20-11
Name DemDidDataElementClassRef [ECUC_Dem_00617]

Parent Container DemDidClass
Attributes:
requiresIndex=true
Multiplicity 1..255
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
10.2.10.4 DemInternalDataElementClass

Container Name DemInternalDataElementClass
Parent Container DemDataElementClass
Description This container contains the configuration (parameters) for an internal
data element class.
Name DemDataElementDataSize [ECUC_Dem_00614]

Parent Container DemInternalDataElementClass
Description Defines the size of the data element in bytes.
Multiplicity 0..1
Range 1 .. 255
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemInternalDataElement [ECUC_Dem_00616]

Parent Container DemInternalDataElementClass
Description This parameter defines the Dem-internal data value, which is mapped
to the data element.
Multiplicity 1
Range DEM_AGINGCTR_DOWN map down-counting Dem-internal
CNT aging counter, max. range: 1 byte
DEM_AGINGCTR_UPCN map up-counting Dem-internal aging
T counter, max. range: 1 byte
DEM_AGINGCTR_UPCN Map up-counting Dem-internal aging
T_FIRST_ACTIVE counter, max. range: 1 byte, starting at
1 when aging starts.
DEM_CLR_DIST Distance since diagnostic trouble
codes cleared (PID31)
DEM_CLR_TIME Time since diagnostic trouble codes
cleared (PID4E)
DEM_CURRENT_FDC map Dem-internal fault detection
counter, max. range: 1 byte
DEM_CYCLES_SINCE_FI map Dem-internal Operation Cycle
RST_FAILED Counter - Cycles since first failed, max.
range: 1 byte
DEM_CYCLES_SINCE_L map Dem-internal Operation Cycle
AST_FAILED Counter - Cycles since last failed, max.
range: 1 byte
DEM_DTC_PRIORITY DTC priority statically assigned to this
DTC via DemDTCPriority. The length
is one byte.
DEM_EVENT_ASSOCIAT Represents the static value associated
ED_IDENTIFICATION to an event by
DemEventAssociatedIdentification.
DEM_FAILED_CYCLES map Dem-internal Operation Cycle
Counter - Failed cycles, max. range: 1
byte
DEM_J1939LAMP_STAT Current state of applicable lamp(s) for
US this DTC in SAE J1939 DM31 format.
DEM_MAX_FDC_DURIN map Dem-internal DTC Fault Detection
G_CURRENT_CYCLE Counter maximum value during current
operation cycle, max. range: 1 byte
DEM_MAX_FDC_SINCE_ map Dem-internal DTC Fault Detection
LAST_CLEAR Counter maximum value since last
clear, max. range: 1 byte
DEM_MIL_DIST Distance Travelled While MIL is
Activated (PID21)
DEM_MIL_TIME Time run by the engine while MIL is
activated (PID4D)
DEM_MONITOR_DATA_0 The monitorData0 value provided
along with
Dem_SetEventStatusWithMonitorData.
DEM_MONITOR_DATA_1 The monitorData1 value provided
along with
Dem_SetEventStatusWithMonitorData.

AUTOSAR CP R20-11
DEM_OCCCTR map Dem-internal occurrence counter,

max. range: 1 byte
DEM_OVFLIND map Dem-internal overflow indication,
max. range: 1 byte (0 = False, 1 =
True)
DEM_SIGNIFICANCE map (static) Dem-internal event
significance (refer to
DemDTCSignificance), max. range: 1
byte (0 = OCCURRENCE, 1 = FAULT)
DEM_WARM_UPS Number of warm-ups since diagnostic
trouble codes cleared (PID30)
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
+literal
DemInternalDataElement: DEM_OCCCTR: EcucEnumerationLiteralDef
+literal DEM_AGINGCTR_UPCNT:
+literal
DEM_MONITOR_DATA_0:
DEM_AGINGCTR_DOWNCNT:
+literal DEM_OVFLIND: EcucEnumerationLiteralDef
+literal DEM_MONITOR_DATA_1:
+literal DEM_SIGNIFICANCE: EcucEnumerationLiteralDef
+literal DEM_MAX_FDC_SINCE_LAST_CLEAR:
+literal
DEM_EVENT_ASSOCIATED_IDENTIFICATION:
+literal DEM_MAX_FDC_DURING_CURRENT_CYCLE:
+literal DEM_CYCLES_SINCE_LAST_FAILED:
+literal DEM_CYCLES_SINCE_FIRST_FAILED:
+literal DEM_FAILED_CYCLES:
+literal DEM_CURRENT_FDC: EcucEnumerationLiteralDef
+literal DEM_MIL_DIST: EcucEnumerationLiteralDef
+literal DEM_WARM_UPS: EcucEnumerationLiteralDef
+literal
DEM_CLR_DIST: EcucEnumerationLiteralDef
+literal DEM_MIL_TIME: EcucEnumerationLiteralDef
+literal DEM_CLR_TIME: EcucEnumerationLiteralDef
+literal DEM_AGINGCTR_UPCNT_FIRST_ACTIVE:
+literal DEM_DTC_PRIORITY: EcucEnumerationLiteralDef
+literal DEM_J1939LAMP_STATUS:
Figure 10.45: DemInternalDataElementClass configuration overview
10.2.10.5 DemExternalCSDataElementClass

AUTOSAR CP R20-11

Container Name DemExternalCSDataElementClass
Description This container contains the configuration (parameters) for an external
client/server based data element class.
It defines, how the Dem can obtain the value of the data element from
either a SW-C or another BSW module. Whether a client/server port or
a C function-call is used, is defined by DemDataElementUsePort.
Name DemDataElementArraySize [ECUC_Dem_00949]

Parent Container DemExternalCSDataElementClass
Description If the data element is an array data element, it defines the number of
elements in the array. Note that this is not the size in bytes.
Multiplicity 0..1
Range 1 .. 4294967295
Default Value
Value
Class
Link time –
Post-build time –
Name DemDataElementDataType [ECUC_Dem_00950]

Description Provide the implementation data type of this C/S data element.
Multiplicity 1
Range BOOLEAN Type of the data is boolean.
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the data is sint16.
SINT16_N Type of the data is sint16 array.
UINT16 Type of the data is uint16.
UINT16_N Type of the data is uin16 array.
UINT32_N Type of the data is uint32 array.
UINT8_N type of the data is uint8.
Multiplicity

AUTOSAR CP R20-11

Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemDataElementProvideMonitorData [ECUC_Dem_00951]

Description If the parameter is set to True, the generated function call to retrieve
the data element has the monitorData0 as additional first parameter.
Multiplicity 1
Default Value false
Value
Class
Link time –
Post-build time –
Name DemDataElementReadFnc [ECUC_Dem_00619]

Description In case of DemDataElementUsePort is false, this parameter defines
the prototype of the C function "ReadDataElement" used to get the
according value.
Multiplicity 0..1
Default Value
Regular Expression
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemDataElementUsePort [ECUC_Dem_00647]

Description If the parameter is set to True, a R-Port is generated, to obtain the data
element (interface DataServices_{Data}). If the parameter is set to
False, the information is obtained by C function-call on another BSW
module specified by the parameter DemDataElementReadFnc.
Multiplicity 1
Default Value
Value
Class
Link time –
Post-build time –
10.2.10.6 DemExternalSRDataElementClass

Container Name DemExternalSRDataElementClass
Description This container contains the configuration (parameters) for an external
sender/receiver based data element class. It defines, how the Dem can
obtain the value of the data element from a SW-C, by using a
sender/receiver port.
Name DemDataElementArraySize [ECUC_Dem_00967]

Parent Container DemExternalSRDataElementClass
Description If the data element is an array data element, it defines the number of
elements in the array. Note that this is not the size in bytes.
Multiplicity 0..1
Range 1 .. 4294967295
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
Name DemDataElementDataType [ECUC_Dem_00840]

Description Provide the implementation data type of data belonging to a external
data.
Multiplicity 1
Range BOOLEAN type of the data is boolean.
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 type of the data is sint16.
UINT16 type of the data is uint16.
UINT16_N Type of the data is uin16 array.
UINT32_N Type of the data is uint32 array.
UINT8_N type of the data is uint8.
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Name DemDataElementEndianness [ECUC_Dem_00841]

Description Defines the endianness of the data belonging to an external data.
If no DemDataElementEndianness is defined the value of

DemDataElementDefaultEndianness is applicable.
Multiplicity 0..1
Range BIG_ENDIAN Most significant byte shall come at the
lowest address.
LITTLE_ENDIAN Most significant byte shall come
highest address
OPAQUE opaque data endianness
Multiplicity

AUTOSAR CP R20-11

Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Included Containers
DemDiagnosisScaling 0..1 This container contains the configuration (parameters)
of an alternative Diagnosis Representation. Out if this
the scaling between Diagnosis and ECU internal
representation and vice versa can be calculated.
DemSRDataElement 0..1 This container defines the source of data in a provided
Class port which shall be read for a external data element
This container shall contain either one

DemSubElementInDataElementInstance OR
DemDataElementInstance OR
DemSubElementInImplDataElementInstance reference.

AUTOSAR CP R20-11
+subContainer
+parameter
DemDiagnosisScaling: +parameter
EcucChoiceContainerDef DemDataElementArraySize:
EcucIntegerParamDef DemDataElementDataType:
upperMultiplicity = 1 min = 1 lowerMultiplicity = 1
+subContainer
+parameter DemSRDataElementClass:
DemDataElementEndianness: +literal LITTLE_ENDIAN: lowerMultiplicity = 0
EcucEnumerationParamDef EcucEnumerationLiteralDef upperMultiplicity = 1
+literal OPAQUE:
+literal
BIG_ENDIAN:
DemAlternativeDataInterface: DemDataElement: EcucForeignReferenceDef

EcucParamConfContainerDef +reference
+choice lowerMultiplicity = 1
upperMultiplicity = 1 destinationType = VARIABLE-DATA-PROTOTYPE
DemPortInterfaceMapping: EcucForeignReferenceDef
+reference upperMultiplicity = 1
destinationType = PORT-INTERFACE-MAPPING
+choice DemAlternativeDataType: DemApplicationDataType:

EcucParamConfContainerDef +reference EcucForeignReferenceDef
destinationType = APPLICATION-DATA-TYPE
+subContainer
DemInternalDataValue: EcucIntegerParamDef
DemTextTableMapping:
EcucParamConfContainerDef +parameter lowerMultiplicity = 1
DemDiagnosisRepresentationDataValue:
upperMultiplicity = 1 A
+choice
DemAlternativeDiagnosticDataElement:
EcucParamConfContainerDef DemDiagnosticDataElementRef: EcucForeignReferenceDef
+reference
destinationType = DIAGNOSTIC-DATA-ELEMENT
Figure 10.46: DemExternalSRDataElementClass
10.2.10.7 DemSRDataElementClass

AUTOSAR CP R20-11
Container Name DemSRDataElementClass

Description This container defines the source of data in a provided port which shall
be read for a external data element
This container shall contain either one

DemSubElementInDataElementInstance OR
DemDataElementInstance OR
DemSubElementInImplDataElementInstance reference.
Container Choices
DemDataElement 0..1 Instance Reference to the primitive data in a port where
Instance the data element is typed with an
ApplicationPrimitveDataType or an
ImplementationDataType.
DemSubElementInData 0..1 Instance Reference to the primitve sub-element (at any
ElementInstance level) of composite data in a port where the data element
is typed with an ApplicationCompositeDataType.
DemSubElementInImpl 0..1 Instance Reference to the primitve sub-element (at any
DataElementInstance level) of composite data in a port where the data
element is typed with an ImplementationDataType of
category STRUCTURE or ARRAY.
10.2.10.8 DemSubElementInDataElementInstance

Container Name DemSubElementInDataElementInstance
Description Instance Reference to the primitve sub-element (at any level) of
composite data in a port where the data element is typed with an
ApplicationCompositeDataType.

AUTOSAR CP R20-11
Name DemSubElementInDataElementInstanceRef [ECUC_Dem_00860]

Parent Container DemSubElementInDataElementInstance
composite data in a port which shall be read or written. Supported are
VariableDataPrototypes in SenderReceiverInterfaces and
NvDataInterfaces and ParameterDataPrototypes in
AutosarDataPrototype is typed with a ApplicationCompositeDataType.
Multiplicity 1
Type Instance reference to APPLICATION-COMPOSITE-ELEMENT-DATA-
PROTOTYPE context: ROOT-SW-COMPOSITION-PROTOTYPE SW-
COMPONENT-PROTOTYPE PORT-PROTOTYPE AUTOSAR-DATA-P
ROTOTYPE APPLICATION-COMPOSITE-ELEMENT-DATA-PROTOT
YPE*
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Scope / Dependency
10.2.10.9 DemSubElementInImplDataElementInstance

Container Name DemSubElementInImplDataElementInstance
composite data in a port where the data element is typed with an
ImplementationDataType of category STRUCTURE or ARRAY.

AUTOSAR CP R20-11
Name DemSubElementInImplDataElementInstanceRef [ECUC_Dem_00862]

Parent Container DemSubElementInImplDataElementInstance
composite data in a port which shall be read or written. Supported are
VariableDataPrototypes in SenderReceiverInterfaces and
NvDataInterfaces and ParameterDataPrototypes in
AutosarDataPrototype is typed with a ImplementationDataType of
category STRUCTURE or ARRAY. Please note that in case of ARRAY
the index attribute in the target reference has to be set to select a
single array element.
Multiplicity 1
Type Instance reference to IMPLEMENTATION-DATA-TYPE-ELEMENT
context: ROOT-SW-COMPOSITION-PROTOTYPE SW-COMPONENT-
PROTOTYPE PORT-PROTOTYPE AUTOSAR-DATA-PROTOTYPE I
MPLEMENTATION-DATA-TYPE-ELEMENT*
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Scope / Dependency
10.2.10.10 DemDiagnosisScaling

Container Name DemDiagnosisScaling
Description This container contains the configuration (parameters) of an alternative
Diagnosis Representation. Out if this the scaling between Diagnosis
and ECU internal representation and vice versa can be calculated.
Container Choices
DemAlternativeData 0..1 This container contains the configuration (parameters)
Interface of an alternative Diagnosis Representation by the
means of a VariableDataPrototoype in a DataInterface.
Additionally a reference to PortInterfaceMapping can be

defined which provide already the mapping rules
between the VariableDataPrototoype in a DataInterface
used by the software component
(DemSRDataElementClass) and the intended Diagnosis
Representation defined by
DemExternalSRDataElementClass.

AUTOSAR CP R20-11
DemAlternativeDataType 0..1 This container contains the configuration (parameters)

of an alternative Diagnosis Representation by the
means of an ApplicationDataType.
Additionally the definition of a text table mapping can be

a defined for ApplicationDataTypes that refers to a
CompuMethod of category TEXTTABLE and
SCALE_LINEAR_AND_TEXTTABLE.
DemAlternative 0..1 This container contains the configuration (parameters)
DiagnosticDataElement of an alternative Diagnosis Representation by the
means of Diagnostic Extract.
10.2.10.11 DemAlternativeDataInterface

Container Name DemAlternativeDataInterface
Parent Container DemDiagnosisScaling
Diagnosis Representation by the means of a VariableDataPrototoype in
a DataInterface.
Additionally a reference to PortInterfaceMapping can be defined which

provide already the mapping rules between the
VariableDataPrototoype in a DataInterface used by the software
component (DemSRDataElementClass) and the intended Diagnosis
Representation defined by DemExternalSRDataElementClass.
Name DemDataElement [ECUC_Dem_00845]

Parent Container DemAlternativeDataInterface
Description Alternative Diagnosis Representation for the data defined by the
means of a VariableDataPrototoype in a DataInterface.
The CompuMethod of the data type of the referenced

VariableDataPrototype will be applied to the data type of the
VariableDataPrototype in the interface used by the Dem.
Multiplicity 1
Type Foreign reference to VARIABLE-DATA-PROTOTYPE
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Scope / Dependency

AUTOSAR CP R20-11
Name DemPortInterfaceMapping [ECUC_Dem_00846]

Parent Container DemAlternativeDataInterface
Description Optional reference to PortInterfaceMapping which defines the mapping
rules.
The PortInterfaceMapping is used to get the DataPrototypeMapping

that describes a conversion between the data prototype referenced by
DemDataElement and the data prototype referenced from
DcmDspExternalSRDataElementClass.
Multiplicity 0..1
Type Foreign reference to PORT-INTERFACE-MAPPING
Multiplicity
Value
Configuration Class
Link time –
Post-build time –
Class
Link time –
Post-build time –
Scope / Dependency
10.2.10.12 DemAlternativeDiagnosticDataElement

Container Name DemAlternativeDiagnosticDataElement
Diagnosis Representation by the means of Diagnostic Extract.

AUTOSAR CP R20-11
Name DemDiagnosticDataElementRef [ECUC_Dem_00935]

Parent Container DemAlternativeDiagnosticDataElement
Description Alternative Diagnosis Representation for the data defined by the
means of a DiagnosticDataElement in the Diagnostic Extract.
This EcucForeignReference enables the access to all

SwDataDefProps, in particular BaseType, CompuMethod and
DataConstr
The CompuMethod and DataConstr that applies to the referenced

DiagnosticDataElement will be applied to the data type of the
VariableDataPrototype in the interface used by the Dem. The mapped
ImplementationDataType needs to match the given BaseType.
Multiplicity 1
Type Foreign reference to DIAGNOSTIC-DATA-ELEMENT
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
10.2.10.13 DemAlternativeDataType

Container Name DemAlternativeDataType
Diagnosis Representation by the means of an ApplicationDataType.
Additionally the definition of a text table mapping can be a defined for

ApplicationDataTypes that refers to a CompuMethod of category
TEXTTABLE and SCALE_LINEAR_AND_TEXTTABLE.

AUTOSAR CP R20-11
Name DemApplicationDataType [ECUC_Dem_00848]

Parent Container DemAlternativeDataType
Description Alternative Diagnosis Representation for the data defined by the means
of a ApplicationDataType of category VALUE, BOOLEAN or ARRAY.
The CompuMethod that applies to the referenced ApplicationDataType

in case of category VALUE or BOOLEAN will be applied to the data
type of the VariableDataPrototype in the interface used by the Dem.
Multiplicity 1
Type Foreign reference to APPLICATION-DATA-TYPE
false
Post-Build Variant
Value
Class
Link time –
Post-build time –
Scope / Dependency
Included Containers
DemTextTableMapping 0..* The purpose of the DemDspTextTableMapping is to
associate a texttable value defined in the context of the
Dem to a texttable value defined in the context of a
CompuMethod referenced by a DataType that shall be
taken to create a dataElement in a
SenderReceiverInterface. By this means it is possible to
create a primitive version of a TexttableMapping (which
can only be applied if a dataElement already exists).
In other words, the DemDspTextTableMapping provides

a similar mechanism to the TexttableMapping in a
situation where the TexttableMapping cannot be applied
since the SenderReceiverInterface for the PortPrototype
on the Dem ServiceComponent does not yet exist.
10.2.10.14 DemTextTableMapping

Container Name DemTextTableMapping
Parent Container DemAlternativeDataType

AUTOSAR CP R20-11
Description The purpose of the DemDspTextTableMapping is to associate a

texttable value defined in the context of the Dem to a texttable value
defined in the context of a CompuMethod referenced by a DataType
that shall be taken to create a dataElement in a
SenderReceiverInterface. By this means it is possible to create a
primitive version of a TexttableMapping (which can only be applied if a
dataElement already exists).
In other words, the DemDspTextTableMapping provides a similar

mechanism to the TexttableMapping in a situation where the
TexttableMapping cannot be applied since the
SenderReceiverInterface for the PortPrototype on the Dem
ServiceComponent does not yet exist.
Name DemDiagnosisRepresentationDataValue [ECUC_Dem_00851]

Parent Container DemTextTableMapping
Description The data value in the diagnosis representation.
Multiplicity 1
Range 0 ..
18446744073709551615
Default Value
Value
Class
Link time –
Post-build time –
Name DemInternalDataValue [ECUC_Dem_00850]

Parent Container DemTextTableMapping
Description The ECU internal data value.
Multiplicity 1
Range 0 ..
18446744073709551615
Default Value
Value
Class
Link time –
Post-build time –

AUTOSAR CP R20-11
10.3 Published information

For details refer to the chapter 10.3 “Published Information” in SWS_BSWGeneral.

AUTOSAR CP R20-11
11 Not Applicable Requirements

[SWS_Dem_00999] dThese requirements are not applicable to this specifica-
tion.c(SRS_BSW_00005, SRS_BSW_00161, SRS_BSW_00162, SRS_BSW_00164,
SRS_BSW_00168, SRS_BSW_00170, SRS_BSW_00327, SRS_BSW_00331, SRS_-
BSW_00341, SRS_BSW_00347, SRS_BSW_00348, SRS_BSW_00350, SRS_-
BSW_00433, RS_Diag_04005, RS_Diag_04006, RS_Diag_04007, RS_Diag_04015,
RS_Diag_04016, RS_Diag_04019, RS_Diag_04020, RS_Diag_04021, RS_Diag_-
04032, RS_Diag_04033, RS_Diag_04059, RS_Diag_04064, RS_Diag_04086, RS_-
Diag_04087, RS_Diag_04089, RS_Diag_04090, RS_Diag_04091, RS_Diag_04097,
RS_Diag_04098, RS_Diag_04100, RS_Diag_04101, RS_Diag_04119, RS_Diag_-
04120, RS_Diag_04121, RS_Diag_04135, RS_Diag_04136, RS_Diag_04139, RS_-
Diag_04143, RS_Diag_04144, RS_Diag_04145, RS_Diag_04146)

AUTOSAR SWS DiagnosticEventManager

Uploaded by

Copyright:

Available Formats

AUTOSAR SWS DiagnosticEventManager

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AUTOSAR SWS DiagnosticEventManager

Uploaded by

Copyright:

Available Formats

Specification of Diagnostic Event Manager

Document Title Specification of Diagnostic Event

Document Status published

Document Change History

1 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

• Clarified asynchronous API behavior

2 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

AUTOSAR • Further clarification of event

3 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

• Incorporated new and reporting of

4 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

• Improved and extended of Dem

5 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

• Complete rework and extension of

6 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

7 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

2 Acronyms and Abbreviations 21

8 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

7.6.1 Operation Cycle Counters . . . . . . . . . . . . . . . . . . . . 69

9 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

7.9.2 PIDs provided by Dem . . . . . . . . . . . . . . . . . . . . . . 149

10 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

7.10.5 Diagnostic Readiness . . . . . . . . . . . . . . . . . . . . . . 180

11 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

8.2.1.17 Dem_RatioIdType . . . . . . . . . . . . . . . . . . . 213

12 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

8.3.3.28 Dem_SetEventStatus . . . . . . . . . . . . . . . . . 237

13 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

8.3.5.13 Dem_DcmGetDTCOfOBDFreezeFrame . . . . . . . 264

14 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

8.4.3.1.2 DemTriggerOnComponentStatus . . . . . . . . 289

15 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

8.6.3.4 CallbackEventDataChanged . . . . . . . . . . . . . . 310

16 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

8.6.4.12 ControlEventAvailable . . . . . . . . . . . . . . . . . 344

17 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

10.2.2.1 DemGeneral . . . . . . . . . . . . . . . . . . . . . . 362

18 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

10.2.8.4 DemCallbackOBDDTCStatusChanged . . . . . . . . 493

19 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

1 Introduction and functional overview

20 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

2 Acronyms and Abbreviations

21 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

22 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

P-Code Power train code

23 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

24 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

25 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

3.1 Input documents & related standards and norms

26 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

[15] Road vehicles – Interchange of digital information on electrical connections be-

3.2 Related specification

27 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

4 Constraints and assumptions

28 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

4.2 Applicability to car domains

29 of 535 Document ID 19: AUTOSAR_SWS_DiagnosticEventManager

5 Dependencies to other modules