Overview
What the DME controls
Fuel injection (including the high-pressure fuel pump on direct-injection engines), ignition timing, VANOS variable valve timing, Valvetronic variable valve lift (where equipped), throttle body control, idle air control, and the engine’s emissions strategy. The DME also runs the OBD-II readiness monitors.
Target address
0x12 (18 decimal) on KWP2000 over K+DCAN. On F/G-series with UDS, the DME is on the same target address (0x12) but at the UDS service layer.
What Beemuu reads
Fault memory (0x14 clear, 0x19 read), live data (RPM, coolant, IAT, MAF, fuel trim, O2 sensor voltages, short-term and long-term fuel trim, ambient pressure, battery voltage, throttle position), VIN (DID F190 on F/G-series, KWP 0x1A 0x90 on E-series).
Service functions on the DME
CBS engine-oil reset, battery registration, Valvetronic adaptation, DPF regeneration (on the N57/M57/B47/B57 diesels). The CLAUDE.md v0.14.4 refresh preserves the routine IDs as unverified per the project audit.
Why E-series and F/G-series feel different
E-series DME runs MSV/MSD80/MSV70 firmware (depending on engine); F/G-series DME runs MEVD17 or DME 8.x. Same conceptual responsibilities; very different firmware behaviour at the detail level. Beemuu abstracts most of this away, but the parameter catalog differs by engine family.
FAQ
What is DME?
Digital Motor Electronics. The engine control module.
What is the DME target address on KWP2000?
0x12 (18 decimal). Beemuu probes this address as part of a vehicle scan.
Can I read live data from the DME?
Yes. Beemuu’s Live Data tab reads RPM, coolant, IAT, MAF, fuel trim, O2 voltages, and more from the DME. The available parameters depend on the engine profile; the project ships 10 production-engine profiles.