SNIP_CLASSIC_DEM_SECTION_7_4_7_Suppress_DTC_output

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) controls the availability of the DTC suppression functionality [SWS_Dem_00915] Upstream requirements: RS_Diag_04220 ⌈The Dem shall suppress a DTC if all related events of this DTC are not available.⌋ 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 Upstream requirements: RS_Diag_04220 ⌈In 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.⌋ [SWS_Dem_01101] Upstream requirements: RS_Diag_04220 ⌈A 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 • 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_J1939DcmReadDiagnosticReadiness2 • Dem_J1939DcmReadDiagnosticReadiness3 • Dem_SelectFreezeFrameData • Dem_SetDTCFilter • Dem_SelectExtendedDataRecord • Dem_SetDTCFilterByExtendedDataRecordNumber • Dem_SetDTCFilterByReadinessGroup ⌋ Note: This means, the (external) reporting (e.g. DTC number, UDS status, DTC extended data records, DTC statistical data, IUMPR, ...) of the DTC is suppressed. [SWS_Dem_01102] Upstream requirements: RS_Diag_04220 ⌈DTC suppression shall not stop event processing of the corresponding DTC.⌋ 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 conditions should be used in addition. [SWS_Dem_01307] Functionality of Dem_GetDTCSuppression Upstream requirements: RS_Diag_04220 ⌈If Dem_GetDTCSuppression is called, the Dem shall return the DTC suppression status in the output parameter SuppressionStatus. A value of TRUE means that the DTC was suppressed by a call of Dem_SetDTCSuppression with SuppressionStatus = TRUE, a value of FALSE means, that the DTC is currently not suppressed.⌋ [SWS_Dem_01315] Upstream requirements: RS_Diag_04220 ⌈If Dem_SetDTCSuppression is called the Dem shall set the suppression status of the selected DTC to value of the parameter SuppressionStatus.⌋ 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_SetDTCSuppression. Dem_GetDTCSuppression only evaluates this suppression state.