SNIP_CLASSIC_DEM_SECTION_7_7_1_Event_status_management

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] Upstream requirements: RS_Diag_04067 ⌈The 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).⌋ [SWS_Dem_01333] ⌈The API Dem_SetEventStatusWithMonitorData shall have the same functionality as Dem_SetEventStatus with the only difference that it provides further parameters with data to store in an event related data.⌋ 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). Figure 7.14: Example for using Dem_SetEventStatus [SWS_Dem_00331] Upstream requirements: RS_Diag_04179 ⌈The Dem module shall provide the capability to reset the failed status of an event without reporting a passed result (refer to Dem_ResetEventStatus).⌋ 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 Upstream requirements: RS_Diag_04067 ⌈The function Dem_ResetEventStatus 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.⌋ 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] Upstream requirements: RS_Diag_04067 ⌈The 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).⌋ [SWS_Dem_01390] Behavior of Dem_ResetMonitorStatus ⌈The function Dem_ResetMonitorStatus shall set the monitor status bit 0 (TestFailed) to 0 and reset the Dem-internal debounce algorithm to initial values if configured.⌋ Note: The function Dem_ResetMonitorStatus does not change the UDS status byte and does not clear the pre-stored freeze frame. [SWS_Dem_01401] ⌈The function Dem_ResetMonitorStatus shall return E_NOT_OK, if the monitoring was already tested this operation cycle (monitor status byte, bit 1 set to 0).⌋ [SWS_Dem_00051] Upstream requirements: RS_Diag_04067 ⌈If the API Dem_GetEventUdsStatus is called, the Dem shall provide the current event status byte of a specific event.⌋ 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] Upstream requirements: RS_Diag_04068 ⌈The Dem shall provide a function Dem_GetDebouncingOfEvent () that reports the debounce status of an event. The outparameter ‘DebouncingState’ 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.⌋ The Dem supports a configuration per event to forbid to reset the event in the same operation cycle. [SWS_Dem_01208] Upstream requirements: RS_Diag_04151 ⌈If the configuration parameter DemEventRecoverableInSameOperationCycle 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.⌋ Note: Debouncing is done independently from the value DemEventRecoverableInSameOperationCycle. The FDC can reach -128 independently from the setting of DemEventRecoverableInSameOperationCycle. [SWS_Dem_01209] Upstream requirements: RS_Diag_04151 ⌈The Dem shall perform the configured debouncing independently from the setting of the configuration parameter DemEventRecoverableInSameOperationCycle. 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).⌋ [SWS_Dem_01250] Upstream requirements: RS_Diag_04165 ⌈If DemMultiEventTriggering is configured and any of the APIs: • Dem_SetEventStatus • Dem_ResetEventStatus • Dem_PrestoreFreezeFrame • Dem_ClearPrestoredFreezeFrame • Dem_ResetEventDebounceStatus is called with an EventId that is referenced by DemMultiEventTriggeringMasterEventRef of a DemMultiEventTriggering, for each DemMultiEventTriggeringSlaveEventRef 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 DemMultiEventTriggeringSlaveEventRef.⌋ [SWS_Dem_01339] Upstream requirements: RS_Diag_04165 ⌈The Dem shall not support calls of • Dem_SetEventStatus • Dem_ResetEventStatus • Dem_PrestoreFreezeFrame • Dem_ClearPrestoredFreezeFrame • Dem_ResetEventDebounceStatus with an EventId that is referenced by any of the DemMultiEventTriggeringSlaveEventRef in container DemMultiEventTriggering or by DemStorageConditionReplacementEventRef. These events are exclusively used for internal triggering. The behavior of the Dem is undefined if any of those APIs are called in this situation.⌋