BMW D91410: CAS Receives Incorrect Drivetrain Message from DME/DDE

D91410 is an incorrect drivetrain 2 data message received by CAS from DME or DDE. CAS records the fault when message content fails its plausibility checks; this differs from a message that is simply absent. The first task is preserving the complete vehicle scan and the operating context before clearing anything. What Does BMW D91410 Mean? D91410 means CAS received drivetrain 2 data identified as message 230.0.2, but judged its content incorrect. The sender is DME on gasoline vehicles or DDE on diesel vehicles. The definition describes receiver, sender, and data quality; it does not by itself prove either control module has failed. In practice, CAS is alive enough to evaluate the telegram, while the reported drivetrain values or their timing are implausible. A complete scan can show whether DME/DDE is reachable and whether voltage, synchronization, gateway, or network faults occurred together. Module names and test plans can vary with chassis and integration level, so VIN-specific confirmation remains important. Code: D91410 Definition: Message (drivetrain 2 data, 230.0.2) incorrect, receiver CAS, transmitter DME / DDE Receiver: CAS Transmitter: DME / DDE Key distinction: message incorrect, not merely missing Severity: investigate promptly, especially with starting symptoms Note: confirm the VIN-specific module topology Do not interpret “incorrect” as “no communication.” First check whether DME/DDE remains reachable and whether companion faults report missing messages, undervoltage, or synchronization. What Symptoms Can BMW D91410 Cause? D91410 may appear with no obvious driving complaint, an intermittent starting delay, or a broader drivetrain warning. Its most useful symptom is the pattern across modules: CAS reports invalid drivetrain data while DME/DDE availability and related bus faults reveal whether the event was transient or persistent. Reproduce only safe operating conditions and compare fault timestamps before choosing a repair path. • CAS stores D91410 while DME/DDE still answers a complete scan, indicating invalid content rather than total silence. • Starting may hesitate after a low-voltage event, yet normal operation can return after the supply stabilizes. • A drivetrain or start-authorization warning can coincide with several communication faults recorded at one timestamp. • The code may remain historical after battery work, jump starting, programming, or an interrupted module wake-up. • Repeated active status after every ignition cycle points away from a single transient voltage disturbance. • Other receivers may flag the same DME/DDE telegram, strengthening evidence for sender data or network timing trouble. Why Does BMW D91410 Occur? D91410 occurs when CAS rejects drivetrain data sent by DME/DDE as implausible or incorrectly formed. Begin with event history and power quality because simultaneous undervoltage can corrupt communication without damaging a module. Persistent faults then require checks of module availability, connector condition, bus integrity, software compatibility, and only last of all internal CAS or DME/DDE hardware. • A brief supply drop during starting or wake-up disrupts message timing while both modules remain functional. • DME/DDE power or ground becomes unstable under load, allowing partial communication with unreliable drivetrain values. • Moisture, pin tension, or oxidation at a relevant control-module connector distorts network communication intermittently. • Bus wiring damage or an interfering control unit changes signal quality during a particular wake-up sequence. • Incompatible programming levels or incomplete coding leave CAS evaluating drivetrain data against mismatched expectations. • An internal CAS or DME/DDE defect produces persistently invalid telegram content after external causes are excluded. How Is BMW D91410 Diagnosed with OBDThink? Diagnose D91410 by preserving the complete scan, fault status, and available freeze frame before clearing stored evidence. OBDThink is an independent BMW coding and diagnostics app and is not affiliated with BMW AG. Supported live data varies by chassis, adapter, and module; use it to compare module presence and event context, then perform physical tests with the VIN-specific BMW wiring information. • 1. Save every module result, noting whether D91410 is active, stored, intermittent, and accompanied by timestamps. • 2. Confirm that CAS and DME/DDE both answer repeatedly through several ignition wake-up cycles without disappearing. • 3. Compare companion faults for undervoltage, missing telegrams, synchronization, or gateway resets at the same event. • 4. Observe supply history during starting; investigate a synchronized collapse across modules before testing data wiring. • 5. Load-test DME/DDE and CAS power and ground paths using the vehicle-specific wiring diagram and access points. • 6. Inspect relevant connectors for moisture, backed-out pins, fretting, or tension changes revealed by gentle movement. • 7. If power is stable, evaluate network integrity and isolate any module disturbing communication during wake-up. • 8. After correction, clear codes once and repeat cold start, warm restart, and complete vehicle scans. IF CAS and DME/DDE stay reachable AND D91410 followed a common supply drop, THEN correct the supply event first. ELSE IF multiple receivers reject the same drivetrain telegram while power remains stable, THEN test sender software and network integrity. ELSE isolate the CAS receiver path with the VIN-specific BMW test plan. The fastest distinction is cross-module agreement: one CAS complaint suggests a receiver-side path, while several receivers rejecting the same telegram shifts attention toward DME/DDE data or bus timing. How Is BMW D91410 Repaired? Repair follows the evidence uncovered during the synchronized scan and electrical checks. A historical voltage event needs supply correction and verification, not automatic CAS replacement. Connector or bus repairs come before programming, while module coding, software alignment, or hardware replacement is justified only when stable power and wiring have been demonstrated and the fault remains reproducible. • Low cost — restore battery charge and correct verified cable or ground resistance causing synchronized voltage drops. • Low cost — clean and secure affected connector pins only where inspection or movement reproduces communication changes. • Moderate cost — repair damaged bus wiring with the specified topology preserved, then retest wake-up behavior. • Moderate cost — complete interrupted coding or align compatible software levels using an appropriate BMW procedure. • High cost — replace CAS only after receiver-specific failure persists with stable power, network, and sender data. • High cost — repair or replace DME/DDE only when independent testing proves persistently corrupted transmitted information. After repair, D91410 no longer occurs through repeated cold starts, warm restarts, sleep cycles, and complete module scans. Can You Drive with BMW D91410? Driving may be possible when the engine starts normally, no red safety warning appears, and D91410 is only historical. However, CAS depends on valid drivetrain information for coordinated vehicle functions. Arrange diagnosis soon because an intermittent power or communication problem can progress into a no-start condition after the next shutdown. Avoid unnecessary trips until a complete scan separates an old voltage event from an active network fault. Stop and recover the vehicle if starting becomes unreliable, the engine stalls, major drivetrain warnings appear, or several modules repeatedly drop offline; continued cycling may erase the clearest event evidence. Stop driving after stalling, repeated no-starts, red warnings, or simultaneous module dropouts; arrange safe recovery and diagnosis. Which Questions Are Frequently Asked About BMW D91410? These answers clarify the three decisions that matter most: whether the message is missing, whether a battery alone explains the event, and whether module replacement is justified. The full vehicle scan and repeatability carry more diagnostic weight than the single D91410 entry. • Is D91410 a missing-message code? No. The API definition says CAS received an incorrect drivetrain 2 data message from DME/DDE. A separate missing-message fault changes the diagnostic direction, so preserve the exact wording and companion codes. • Can a weak battery cause D91410? A supply drop can disturb message timing and create a historical entry, but battery replacement is not proof. Compare timestamps, starting voltage behavior, and whether the code returns with stable supply. • Does D91410 mean CAS or DME/DDE must be replaced? No. Replacement comes only after power, grounds, connectors, network integrity, software compatibility, and repeat behavior identify a specific module as the source. Treat D91410 as a data-quality problem between a named sender and receiver, not as a parts verdict. Preserve the evidence, compare every module at the same event, and let repeated behavior determine whether supply, network, software, CAS, or DME/DDE deserves the next test.