Specification of Diagnostic Event Manager (`DiagnosticEventManager`)¶

属性	值
平台	CP
类别	SWS — 软件模块规范（Software Specification）
UID	019
规范版本	R25-11

本地文件¶

规范 PDF: F:\Work\Standards\01_Sources\CP_SWS_DiagnosticEventManager_019\AUTOSAR_CP_SWS_DiagnosticEventManager.pdf
ARXML 模型: F:\Work\Standards\01_Sources\CP_SWS_DiagnosticEventManager_019\AUTOSAR_CP_SWS_DiagnosticEventManager.arxml
纯文本全文: F:\Work\Standards\01_Sources\CP_SWS_DiagnosticEventManager_019\zzgen\CP_SWS_DiagnosticEventManager.complete.txt

文档简介¶

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.

模块依赖¶

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

The Function Inhibition Manager (FiM) (refer to ) stands for the evaluation and assignment of events to the required actions for Software Components (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 ) is in charge of the UDS and SAE J1979 communication path and execution of diagnostic service resulting in the processing of diagnostic requests from an external tester or onboard test system. It forwards requests coming from an external diagnostic 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.
The Diagnostic Communication Manager for J1939 (J1939Dcm) (refer to ) is in charge of the SAE J1939-73 diagnostics communication protocol.
Software-Components (SW-C) and Basic Software (BSW) modules can access 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 ) 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-initializati

章节详细内容¶

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.

2. 缩略语¶

原文标题：Acronyms and Abbreviations

The glossary below includes acronyms and abbreviations relevant to the Dem module that are not included in the .

3. Acronyms¶

Acronym	Description
Activation Mode 1	Absence of malfunction - The MIL shall blink for one flash.
Activation Mode 2	"on-demand-MI" - The MIL shall show blink for two flashes if the OBD system would command an on-demand-MI according to the discriminatory display strategy.
Activation Mode 3	"short-MI" - The MIL shall blink for three flashes if the OBD system would command a short-MI according to the discriminatory display strategy.
Activation Mode 4	"continuous-MI" - The MIL shall remain continuously ON ("continuous-MI") if the OBD system would command a continuous-MI according to the discriminatory display strategy.
Aging	Unlearning/deleting of a no longer failed event/DTC after a defined number of operation cycles from event memory.
Aging Counter	The "Aging Counter" or "Aging Cycle Counter" or "DTC Aging Counter" specifies the counter which is used to perform Aging. It counts the number of operation cycles until an event/DTC is removed from event memory.
Class B1 counter	Number of engine hours during which a Class B1 malfunction has been Confirmed and TestFailed.
Combined DTC	Normal DTC, but referenced by multiple events reported by several monitors (e.g.

4. 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
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)

S

5. 相关文档¶

原文标题：Related documentation

6. 输入文档与相关标准规范¶

原文标题：Input documents & related standards and norms

7. 相关规范¶

原文标题：Related specification

AUTOSAR provides a General Specification on Basic Software modules , which is also valid for Diagnostic Event Manager.

Thus, the specification SWS BSW General shall be considered as additional and required specification for Diagnostic Event Manager.

8. 约束与假设¶

原文标题：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.

Upstream requirements: ⌈ There shall only be one Dem module available per ECU. ⌋

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.

9. 限制¶

原文标题：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.

The handling of infrastructure errors reported by the RTE during Dem <=> SW-C interactions is missing from the SWS and might have to be taken into account by implementers if they need it.

The Dem is able to support additional event memories (permanent 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 implementation. The following functionality is not defined:

10. 适用的车型领域¶

原文标题：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.

11. 对其他模块的依赖¶

原文标题：Dependencies to other modules

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

The Function Inhibition Manager (FiM) (refer to ) stands for the evaluation and assignment of events to the required actions for Software Components (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 ) is in charge of the UDS and SAE J1979 communication path and execution of diagnostic service resulting in the processing of diagnostic requests from an external tester or onboard test system. It forwards requests coming from an external diagnostic 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.
The Diagnostic Communication Manager for J1939 (J1939Dcm) (refer to ) is in charge of the SAE J1939-73 diagnostics communication protocol.

12. 文件结构¶

原文标题：File structure

13. 代码文件结构¶

原文标题：Code file structure

For details refer to , including subchapters.

14. 头文件结构¶

原文标题：Header file structure

The symbolic names (refer to TPS_ECUC_02108) are generated for configuration containers containing an identifier parameter, like event Id symbols, operation cycles, indicators, 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.

15. 集成 Hints¶

原文标题：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).

16. 需求 traceability¶

原文标题：Requirements traceability

The following table references the requirements specified in as well as and links to the fulfillment of these.

Requirement	Description	Satisfied by
The Diagnostic event (fault) management shall be established as Basic SW Module
Access and handle specific data elements and data element groups if requested by an external scan tool
Notify the Function Inhibition Manager (FIM) upon changes of the event status in order to process them according to the SW components dependencies
Classification of events for series production, OBD and expert usage
Ability to access different event memories
Provide the diagnostic status information according to ISO 14229-1
The diagnostic in AUTOSAR shall support event specific debounce counters to improve signal quality internally (According to ISO 14229-1 Appendix D)
Process events according to their defined importance like priority and/or severity
Uses standard mechanisms provided by persistency modules
Memory overflow indication
Event memory management
Provide defensive behavior
Provide an interface to retrieve the number of event memory entries
SAE J1939 lamp status
SAE J19

17. 功能规范¶

原文标题：Functional specification

The Diagnostic Event Manager (Dem) handles and stores the events detected by diagnostic monitors in both Software Components (SW-Cs) and Basic software (BSW) modules. The stored event information is available via an interface to other BSW modules or SW-Cs.

DemGeneral contains the global part of the configuration and DemConfigSet contains the multiple configuration part.

18. 启动行为¶

原文标题：Startup behavior

Upstream requirements: ⌈ The Dem module shall distinguish between a pre-initialization mode and a full-initialized mode (operation mode). ⌋

Upstream requirements: ⌈ The 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_ResetEventDebounceStatus. ⌋

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 modules can start reporting of related events via Dem_SetEventStatus (refer to ).

The function Dem_Init (refer also to ) 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 environment has called the function Dem_Init.

19. 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.

Upstream requirements: ⌈ The Dem module shall provide the interface InitMonitorForEvent to trigger the initalization of a diagnostic monitor (refer also to ). ⌋

For details see also chapter .

The function parameter InitMonitorReason indicates the reason / trigger of initialization.

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.

Upstream requirements: ⌈ A call to Dem_RestartOperationCycle shall re-initialize the diagnostic monitors of all related events by calling their respective callbacks InitMonitorForEvent with parameter InitMonitorReason set to DEM_INIT_MONITOR_RESTART. ⌋

Upstream requirements: ⌈ The 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. ⌋

20. 诊断 event 定义¶

原文标题：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 ). 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.

Upstream requirements: ⌈ The Dem module shall represent each Diagnostic Event by an EventId and the related EventName. ⌋

All monitors and BSW modules use the EventId as a symbolic EventName. The Dem configuration tool replaces the symbolic names by numbers.

Upstream requirements: ⌈ The EventId and the related EventName shall be unique per Dem module represented by the ECU configuration (refer to ). ⌋

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.

21. 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).

Upstream requirements: , ⌈ Each supported event shall have a priority assigned to it (refer to parameter DemDTCPriority in DemDTCAttributes). ⌋

Upstream requirements: , ⌈ A priority value of 1 shall be the highest priority. Larger priority value shall define lower importance. ⌋

22. Event occurrence¶

Upstream requirements: ⌈ The Dem module shall provide an occurrence counter per event memory entry. ⌋

Upstream requirements: ⌈ The Dem module shall initialize the occurrence counter with the value one if the related event is entered in the respective event memory. ⌋

Upstream requirements: ⌈ If the configuration parameter DemOccurrenceCounterProcessing is set to DEM_PROCESS_OCCCTR_TF (refer to DemPrimaryMemory or DemUserDefinedMemory), 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. ⌋

Upstream requirements: ⌈ If the configuration parameter DemOccurrenceCounterProcessing 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. ⌋

23. 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)

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 ).

24. Event destination¶

The configuration parameter DemMemoryDestinationRef (refer to DemDTCAttributes) defines the dedicated storage location(s) of the event and its related data (refer to chapter ).

The "permanent event memory" assignment is implicitly derived from the related DTC kind (refer to chapter ). 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 ). 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 and permanent).

Limitations on DemMemoryDestinationRef ⌈ A DTC can only reference the event memories via DemMemoryDestinationRef to the event memories of the same DemEventMemorySet.

25. 诊断 monitor 定义¶

原文标题：Diagnostic monitor definition

A diagnostic monitor is a routine entity determining the proper functionality of a component. 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.

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 ), the reporting API is called whenever the code with the functional check is executed.

26. Event dependencies¶

The priority of events within the assigned DemComponent and furthermore the dependency relation between the DemComponents is used for filtering the storage of error reports to the failure memory.

⌈ Whenever an event reports FAILED, it shall be considered as CONSECUTIVE FAULT, if any other event with higher priority at the same DemComponent already is FAILED. ⌋

⌈ Whenever an event reports FAILED, it shall be considered as CONSECUTIVE FAULT, if any parent DemComponent is FAILED. ⌋

⌈ The Dem shall allow to ignore the priority of events of a DemComponentIgnoresPriority). In this case, the event shall only be considered as CONSECUTIVE FAULT if any parent component is FAILED (other events FAILED status at the same component shall be ignored).] ⌋

⌈ If a reported failure is not considered as consecutive fault, it shall be considered as CAUSAL FAULT. Causal faults shall be handled normally. ⌋

⌈ If a reported failure is not considered as consecutive fault and it has configured a DemCausalityDelayTime, it shall be considered as PRELIMINARY-CAUSAL FAULT.

27. 组件 availability¶

原文标题：Component availability

⌈ The Dem shall support the availability of DemComponent. Components 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). ⌋

⌈ The interface Dem_SetComponentAvailable shall be available to set the availability state of a component. ⌋

⌈ With setting a DemComponent to not available, all assigned events shall also be set as not available. ⌋

⌈ After startup all DemComponents shall be available. ⌋

⌈ If a DemComponent is set to 'not available' via Dem_SetComponentAvailable, the Dem shall treat all the dependent components (children) as if they are set as 'not available'. ⌋

⌈ If a DemComponent is set to 'not available' via Dem_SetComponentAvailable, 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). ⌋

⌈ If a DemComponent is set to 'not available' via Dem_SetComponentAvailable and any individual event assigned to it (see ) is already failed, the individual event will be kept as 'available'.

28. 诊断 trouble 代码定义¶

原文标题：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 ).

29. DTC kind¶

No content.

30. DTC format¶

⌈ The Dem module shall support DTC formats for DemDTC according to:

ISO-14229-1
SAE J2012 OBD DTC (aka 2-byte DTC)
SAE J1939-73
ISO 11992-4
SAE J2012 WWH-OBD DTC (aka 3-byte DTC) ⌋

The configuration parameter DemTypeOfDTCSupported is used to specify one of the supported DTC formats defined in of the ECU (refer to Dem_GetTranslationType). This is required to determine the DTC format value to be reported for ISO-14229-1 service Read DTC Information (0x19).

Upstream requirements: ⌈ The Dem module shall support different DTC numbers for UDS, OBD, and J1939 DTCs based on separate configuration parameters (refer to parameters DemDTC and DemObdDTC in DemConfigSet). ⌋

For DTCs multiple combinations of the supported DTC formats (UDS, OBD, OBD3Byte and J1939) are possible. The Dem internally handles one of the two OBD format in combination with UDS and J1939 DTCs.

Some manufacturers don't want to fully change to SAE J1979-2 support with UDS and will only support the J1979-2 functionality on the limited UDS subset defined by J1979-2, wherefore the feature OBD UDS DTC separation was added.

31. DTC groups¶

In addition to single DTC values, groups of DTCs can be configured (refer to DemGroupOfDTC), as defined by ISO 14229-1 - 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 Disable/Enable DTC), the DTCGroup is selected by the DTC value.

⌈ The DemGroupOfDTC shall represent the values of the DTC Group boundaries. ⌋

Note: A group with the global boundaries 0x000100 and 0xfffe00 does not need to be configured, as the group ALL is automatically defined.

⌈ All 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. ⌋

Note: DTC groups are relevant for the diagnostic service ClearDiagnosticInformation (0x14, refer to Dem_ClearDTC).

⌈ The Dem shall support the predefined DTC group GroupOfAllDTCs (0xFFFFFF) within the parameter DTC of Dem_SelectDTC. ⌋

⌈ The Dem shall support the predefined DTC group emission related DTCs for WWH-OBD and J1979-2 (0xFFFF33) within the parameter DTC of Dem_SelectDTC if WWH-OBD or J1979-2 is supported. ⌋

32. DTC severity¶

The DTC severity is used to provide information regarding the importance of the specific events according to ISO-14229-1, Annex D.3 "DTC severity and class definition". The DemDTCSeverity is only available for UDS DTCs.

Upstream requirements: ⌈ If the API Dem_GetSeverityOfDTC or Dem_GetNextFilteredDTCAndSeverity is called and for the selected DTC a severity value in DemDTCSeverity is configured, the Dem shall set the value configured in DemDTCSeverity as DTCSeverity. ⌋

Upstream requirements: ⌈ If the API Dem_GetSeverityOfDTC or Dem_GetNextFilteredDTCAndSeverity is called and for the selected DTC no severity value in DemDTCSeverity is configured, the Dem shall set DEM_SEVERITY_NO_SEVERITY as DTCSeverity. ⌋

33. 功能性 unit¶

原文标题：Functional unit

Upstream requirements: ⌈ If 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 parameter DTCFunctionalUnit. ⌋

Upstream requirements: ⌈ If 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. ⌋

34. 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)

This significance level is configurable per event (refer to DemDTCSignificance in DemDTCAttributes) and can be mapped as a data element (refer to DEM_SIGNIFICANCE).

35. 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) controls the availability of the DTC suppression functionality

Upstream requirements: ⌈ The Dem shall suppress a DTC if all related events of this DTC are not available. ⌋

For details see chapter .

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.

Behavior of DTC query functions for suppressed DTCs Upstream requirements: ⌈ In case any of the following APIs is called

Dem_GetStatusOfDTC
Dem_GetSeverityOfDTC
Dem_GetFunctionalUnitOfDTC
Dem_ClearDTC

36. 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 different 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.

=> ECUC parameter DemEventAvailableInVariant set to TRUE (enabled) or FALSE (disabled)

One calibration covers multiple hardware variants.¶

37. Monitored 组件定义¶

原文标题：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 documented. 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.

其余 521 章（内容从略，见纯文本全文）¶

定义 of components and dependencies
Operation cycle 管理
Operation Cycle Counters
Cycles since last failed
Cycles since first failed
Failed cycles
Event 存储描述
Event status 管理
Status bit 支持
Monitor status and UDS status update
Status bit transitions
Active/Passive status
通知 of status bit changes
Event 存储管理
Event retention
Clearing event 存储 entries
Event 存储 overflow indication
Event displacement
Reporting order of event 存储 entries
Debouncing of 诊断 events
Counter based debounce algorithm
Time based debounce algorithm
Monitor internal debounce algorithm
Debounce algorithm 初始化 and reset conditions
Fault 检测 counter retrieval
Fault 检测 counter reporting
Fault confirmation
Method for grouping of association of events for OBD 目的
Event Combination
Combination On Storage
Combination On Retrieval
Enable and storage conditions of 诊断 events
Event related 数据
Storage of freeze frame 数据
Pre-storage of freeze frame 数据
Storage of extended 数据
Event related 数据的配置
数据 changes的通知
Aging of 诊断 events
Healing of 诊断 events
Warning indicator 处理
User controlled WarningIndicatorRequested-bit
处理 of the warning indicator lamp (MIL)
通知 and Set of the warning indicator status
BSW 错误处理
OBD-specific functionality
通用概述 and restrictions
PIDs provided by Dem
Centralized PID $21 / $31 / $4D / $4E 处理
PID $21 处理
Readiness status
In-Use-Monitor Performance Ratio (IUMPR) 支持
OBD for light duty (OBD2)
服务 $01 Read Current Powertrain 诊断数据
服务 $02 Read Powertrain Freeze Frame 数据
服务 $03 - Read Emission-Related Powertrain 诊断 Trouble Codes
服务 $04 - Clear Reset Emission-Related 诊断 Information
服务 $06 - 支持 of central DTR 处理
DTR visibility
服务 $07 - Read emission-related 诊断 trouble codes detected during during current or last completed driving cycle
Read Emission-Related 诊断 Trouble Codes with Permanent Status
MIL 处理
UDS based OBD protocols
DTC WWHOBD class
服务 $19 42 - Read WWH-OBD DTC By Mask Record
服务 $14 FFFF33 - Clear Emission Related DTCs
WWH-OBD
Continuous-MI counter
Cumulative Continuous-MI counter (Master ECU)
Class B1 counter
Activation 模式
Activation 模式 Escalation
Activation 模式 Deescalation/ Healing
Freeze Frame 0x00
Extended 数据 Record 0x90
Aging
OBDonUDS
Legislated FreezeFrame storage for OBDonUDS
J1939 specific functionality
Read DTC
Composite Malfunction Indicator Lamp Status
Composite Red Stop Lamp Status
Composite Amber Warning Lamp Status
Composite Protect Lamp Status
DTC 数据 acqusition
Clear DTCs
DM31
Malfunction Indicator Lamp
Red Stop Lamp
Amber Warning Lamp
Protect Lamp
J1939 lamp status
FreezeFrame
SPNs in ExpandedFreezeFrame
诊断 Readiness
Monitor Performance Ratio
Interaction with other 软件模块
Interaction with 软件 Components (SW-C)
Interaction with 诊断 Clients
Parallel event 存储 access
Accessing 诊断 fault 存储
Access DTCs and Status Information
Access event related 数据
Clear 诊断 information
控制 DTC setting
Asynchronous Dcm operations
Interaction with J1939 诊断管理器 (J1939)
Interaction with 功能 Inhibition 管理器 (FIM)
Interaction with NVRAM 管理器 (NvM)
Initialize NvM 数据
Interaction with Default 错误 Tracer (Det)
Required 数据 by the Dem 模块
Scaling information on 服务接口
Version check
错误分类
Development 错误
Runtime 错误
Production 错误
Extended Production 错误
API 规范
Imported 类型
类型定义
Dem 数据类型
Dem_ComponentIdType
Dem_ConfigType
Dem_EventIdType
Dem_EventStatusType
Dem_DebouncingStateType
Dem_DebounceResetStatusType
Dem_UdsStatusByteType
Dem_IndicatorStatusType
Dem_MonitorDataType
Dem_MonitorStatusType
Dem_DTCKindType
Dem_DTCFormatType
Dem_DTCOriginType
Dem_DTCRequestType
Dem_DTCTranslationFormatType
Dem_DTCSeverityType
Dem_RatioIdType
Dem_DTRControlType
Dem_InitMonitorReasonType
Dem_IumprDenomCondIdType
Dem_IumprDenomCondStatusType
Dem_J1939DcmDTCStatusFilterType
Dem_J1939DcmSetClearFilterType
Dem_J1939DcmSetFreezeFrameFilterType
Dem_J1939DcmLampStatusType
Dem_J1939DcmDiagnosticReadiness1Type
Dem_J1939DcmDiagnosticReadiness2Type
Dem_J1939DcmDiagnosticReadiness3Type
Dem_EventOBDReadinessGroupType
Extension to Std ReturnType
功能定义
Dem_GetVersionInfo
接口 ECU 状态管理器 <=> Dem
Dem_PreInit
Dem_Init
Dem_Shutdown
接口 BSW 模块 / SW-Components <=> Dem
Dem_ClearDTC
Dem_ClearPrestoredFreezeFrame
Dem_GetComponentFailed
Dem_GetDTCSelectionResult
Dem_GetDTCSelectionResultForClearDTC
Dem_GetEventUdsStatus
Dem_GetMonitorStatus
Dem_GetDebouncingOfEvent
Dem_GetDTCOfEvent
Dem_GetDTCSuppression
Dem_GetEventAvailable
Dem_GetFaultDetectionCounter
Dem_GetIndicatorStatus
Dem_GetEventFreezeFrameDataEx
Dem_GetEventExtendedDataRecordEx
Dem_GetEventMemoryOverflow
Dem_GetNumberOfEventMemoryEntries
Dem_ResetEventDebounceStatus
Dem_ResetEventStatus
Dem_ResetMonitorStatus
Dem_RestartOperationCycle
Dem_PrestoreFreezeFrame
Dem_SelectDTC
Dem_SetComponentAvailable
Dem_SetDTCSuppression
Dem_SetEnableCondition
Dem_SetEventAvailable
Dem_SetEventConfirmationThresholdCounter
Dem_SetEventStatus
Dem_SetEventStatusWithMonitorData
Dem_SetStorageCondition
Dem_SetWIRStatus
Dem_InitAllNvmBlocks
Dem_InitAllNvmBlocksGetResult
接口 Dcm <=> Dem
Access DTCs and Status Information
Dem_GetTranslationType
Dem_GetDTCStatusAvailabilityMask
Dem_GetStatusOfDTC
Dem_GetSeverityOfDTC
Dem_GetFunctionalUnitOfDTC
Dem_SetDTCFilter
Dem_GetNumberOfFilteredDTC
Dem_GetNextFilteredDTC
Dem_GetNextFilteredDTCAndFDC
Dem_GetNextFilteredDTCAndSeverity
Dem_SetFreezeFrameRecordFilter
Dem_GetNextFilteredRecord
Dem_GetDTCByOccurrenceTime
Dem_SetDTCFilterByExtendedDataRecordNumber
Dem_SetDTCFilterByReadinessGroup
Access extended 数据 records and FreezeFrame 数据
Dem_DisableDTCRecordUpdate
Dem_EnableDTCRecordUpdate
Dem_GetSizeOfExtendedDataRecordSelection
Dem_GetSizeOfFreezeFrameSelection
Dem_GetNextExtendedDataRecord
Dem_GetNextFreezeFrameData
Dem_SelectExtendedDataRecord
Dem_SelectFreezeFrameData
Dem_GetNumberOfFreezeFrameRecords
DTC storage
Dem_DisableDTCSetting
Dem_EnableDTCSetting
OBD-specific Dcm <=> Dem 接口
Dem_DcmGetInfoTypeValue08
Dem_DcmGetInfoTypeValue0B
Dem_DcmReadDataOfPID01
Dem_DcmReadDataOfPID1C
Dem_DcmReadDataOfPID21
Dem_DcmReadDataOfPID30
Dem_DcmReadDataOfPID31
Dem_DcmReadDataOfPID41
Dem_DcmReadDataOfPID4D
Dem_DcmReadDataOfPID4E
Dem_DcmReadDataOfPID91
Dem_DcmReadDataOfOBDFreezeFrame
Dem_DcmGetDTCOfOBDFreezeFrame
Dem_DcmGetAvailableOBDMIDs
Dem_DcmGetNumTIDsOfOBDMID
Dem_DcmGetDTRData
Dem_DcmGetInfoTypeValue79
Dem_DcmReadDataOfPIDF501
接口 J1939Dcm <=> Dem
Access DTCs and Status Information
Dem_J1939DcmSetDTCFilter
Dem_J1939DcmGetNumberOfFilteredDTC
Dem_J1939DcmGetNextFilteredDTC
Dem_J1939DcmFirstDTCwithLampStatus
Dem_J1939DcmGetNextDTCwithLampStatus
DTC storage
Dem_J1939DcmClearDTC
Dem_J1939DcmSetFreezeFrameFilter
Dem_J1939DcmGetNextFreezeFrame
Dem_J1939DcmGetNextSPNInFreezeFrame
Reporting
Dem_J1939DcmSetRatioFilter
Dem_J1939DcmGetNextFilteredRatio
Dem_J1939DcmReadDiagnosticReadiness1
Dem_J1939DcmReadDiagnosticReadiness2
Dem_J1939DcmReadDiagnosticReadiness3
OBD-specific 接口
Dem_SetEventDisabled
Dem_RepIUMPRFaultDetect
Dem_SetIUMPRDenCondition
Dem_GetIUMPRDenCondition
Dem_RepIUMPRDenRelease
Dem_SetPtoStatus
Dem_ReadDataOfPID01
Dem_GetDataOfPID21
Dem_SetDataOfPID21
Dem_SetDataOfPID31
Dem_SetDataOfPID4D
Dem_SetDataOfPID4E
Dem_GetCycleQualified
Dem_SetCycleQualified
Dem_GetDTCSeverityAvailabilityMask
Dem_GetB1Counter
Dem_SetDTR
Expected 接口
Mandatory 接口
Optional 接口
Configurable 接口
接口 BSW 模块 / SW-Components <=> Dem
InitMonitorForEvent
DemTriggerOnComponentStatus
ClearDtcNotification
DemGeneralTriggerOnMonitorStatus
DemGeneralTriggerOnEventUdsStatus
DemTriggerOnEventUdsStatus
DemTriggerOnDTCStatus
DemTriggerOnMonitorStatus
EventDataChanged
ClearEventAllowed
ReadDataElement
GetFaultDetectionCounter
Scheduled functions
Dem_MainFunction
Runnable Entity MainFunction
服务接口
Implementation 数据类型
Dem_DataType
Dem_DataPrimitiveType
Dem_DataArrayType
Dem_DTCOriginType
Dem_DebouncingStateType
Dem_DebounceResetStatusType
Dem_DTRControlType
Dem_EventIdType
Dem_EventStatusType
Dem_DTCFormatType
Dem_InitMonitorReasonType
Dem_IumprDenomCondIdType
Dem_IumprDenomCondStatusType
Dem_MaxDataValueType
Dem_MonitorDataType
Dem_MonitorStatusType
Dem_IndicatorStatusType
Dem_PID21valueType
Dem_PID31valueType
Dem_RatioIdType
Dem_UdsStatusByteType
Dem_PID4DvalueType
Dem_PID4EvalueType
Sender-Receiver-Interfaces
DataServices_{数据}
Client-Server-Interfaces
CallbackClearEventAllowed
CallbackComponentStatusChanged
CallbackDTCStatusChange
CallbackEventDataChanged
CallbackEventUdsStatusChanged
CallbackGetFaultDetectCounter
CallbackInitMonitorForEvent
CallbackMonitorStatusChange
ClearDtcNotification
ClearDTC
DTCSuppression
DataServices_{数据}
DTRCentralReport
DiagnosticInfo
DiagnosticMonitor
DiagnosticMonitor_MonitorData
EnableCondition
EventAvailable
EventFailureCycleCounterThreshold
EvMemOverflowIndication
EventStatus
GeneralCallbackEventDataChanged
GeneralCallbackEventUdsStatusChanged
GeneralCallbackMonitorStatusChanged
GeneralDiagnosticInfo
GetDataOfPID21
IndicatorStatus
IUMPRDenominator
IUMPRDenominatorCondition
IUMPRNumerator
OperationCycle
PowerTakeOff
SetDataOfPID21
SetDataOfPID31
SetDataOfPID4D
SetDataOfPID4E
StorageCondition
Ports
CBClrEvt
CBDataEvt
CBFaultDetectCtr
CBInitEvt
CBStatusDTC
CBEventUdsStatusChanged
CBMonitorStatusChanged
CBStatusComp
ClearDTC
ClearDtcNotification
ControlDTCSuppression
EventAvailable
ControlEventFailureCycleCounterThreshold
DataServices_{数据}
DTR
EnableCond
Event
DiagnosticMonitor_MonitorData
EventStatus
EventInfo
GeneralCBDataEvt
GeneralCBMonitorStatusChanged
GeneralCBStatusEvt
GeneralEvtInfo
IndStatus
IUMPRDenominator
IUMPRDenominatorCondition
IUMPRNumerator
OpCycle
OverflowIndPrimaryMemory
OverflowIndUserDefinedMemory
PowerTakeOffStatus
GetDataOfPID21
SetDataOfPID21
SetDataOfPID31
SetDataOfPID4D
SetDataOfPID4E
StorageCond
时序图
ControlDTCSetting
Dem_ClearDTC
Dem_GetDTCByOccurrenceTime
Dem_GetNextExtendedDataRecord
Dem_DcmGetStatusOfDTC
Retrieving freeze frames
GetOBDFaultInformation
J1939DcmGetNextFilteredDTC
ReportDTCByStatusMask
FiM_DemTriggerOnEventStatus
ProcessEvent (示例)
Retrieving DTCs based on supported extended 数据 records
Retrieving DTCs assigned to a DTC readiness group
Retrieving stored snapshot records for all DTCs
配置规范
How to read this chapter
Containers and 配置 parameters
Dem
通用
DemGeneral
DemConfigSet
DemClient
DemDTCAttributes
DemEventParameter
DemMultiEventTriggering
DemComponent
DemDTC
DemGroupOfDTC
DemOperationCycle
DemIndicator
DemIndicatorAttribute
DemNvRamBlockId
OBD
DemGeneralOBD
DemObdDTC
DemRatio
DemDtrs
DemDtr
DemPidClass
DemPidDataElement
J1939
DemGeneralJ19139
DemJ1939FreezeFrameClass
DemSPNClass
Conditions
DemEnableCondition
DemEnableConditionGroup
DemStorageCondition
DemStorageConditionGroup
Event 存储
DemEventMemorySet
DemPrimaryMemory
DemUserDefinedMemory
Debouncing
DemDebounceAlgorithmClass
DemDebounceCounterBased
DemDebounceCounterBasedClass
DemDebounceTimeBased
DemDebounceTimeBasedClass
DemDebounceMonitorInternal
回调
DemCallbackClearEventAllowed
DemCallbackDTCStatusChanged
DemCallbackJ1939DTCStatusChanged
DemCallbackOBDDTCStatusChanged
DemCallbackGetFDC
DemCallbackEventDataChanged
DemCallbackEventUdsStatusChanged
DemCallbackMonitorStatusChanged
DemCallbackInitMForE
DemClearDTCNotification
Event related 数据
DemFreezeFrameClass
DemFreezeFrameRecordClass
DemFreezeFrameRecNumClass
DemExtendedDataClass
DemExtendedDataRecordClass
数据 elements
DemDataElementClass
DemDataElementInstance
DemDidClass
DemInternalDataElementClass
DemExternalCSDataElementClass
DemExternalSRDataElementClass
DemSRDataElementClass
DemSubElementInDataElementInstance
DemSubElementInImplDataElementInstance
DemDiagnosisScaling
DemAlternativeDataInterface
DemAlternativeDiagnosticDataElement
DemAlternativeDataType
DemTextTableMapping
发布信息
附录
不适用需求
Change history of AUTOSAR traceable items
Traceable item history of this document according to AUTOSAR Release R25-11
Added 规范 Items in R25-11
Changed 规范 Items in R25-11
Deleted 规范 Items in R25-11
Added Constraints in R25-11
Changed Constraints in R25-11
Deleted Constraints in R25-11
Traceable item history of this document according to AUTOSAR Release R24-11
Added 规范 Items in R24-11
Changed 规范 Items in R24-11
Deleted 规范 Items in R24-11
Added Constraints in R24-11
Changed Constraints in R24-11
Deleted Constraints in R24-11
Traceable item history of this document according to AUTOSAR Release R23-11
Added 规范 Items in R23-11
Changed 规范 Items in R23-11
Deleted 规范 Items in R23-11
Added Constraints in R23-11
Changed Constraints in R23-11
Deleted Constraints in R23-11

Specification of Diagnostic Event Manager (DiagnosticEventManager)¶