DCM versus DEM
Separate diagnostic communication from event qualification and stored fault information.
DCM handles diagnostic communication
DCM receives diagnostic requests through the configured communication path, manages protocol and session behaviour, dispatches services and produces responses. Applications or other BSW modules may provide the service's actual data or operation.
DEM manages diagnostic events
DEM receives event reports from monitors, applies configured event processing and manages diagnostic status and memory information. A reported failure is not identical to every DTC status bit becoming set. Debouncing, operation cycles and confirmation criteria affect the outcome.
Follow the status lifecycle
When a tester reports an unexpected DTC state, inspect the monitor report, debounce result, operation-cycle state and event-memory rules. DCM may expose the DEM data through a diagnostic service, but changing DCM alone may not fix event qualification.
Follow each transition
Monitor reports
A monitor provides an event result.
Conceptual sequence. Timing is slowed for learning; it is not a hardware measurement.
Your investigation
A monitor reports a prefailed event once, but no confirmed DTC appears. What assumptions should you avoid?
Reveal the investigation checklist
- Inspect debounce thresholds and direction.
- Check operation-cycle and confirmation requirements.
- Verify event-to-DTC mapping.
- Compare DEM state with the tester's requested status mask.
Which module primarily manages diagnostic events?
Answer the knowledge check correctly to complete this lesson.
Think through DCM versus DEM
Ask for an explanation, an automotive example or a question that tests your understanding.
Checking mentor availability…