BMW 2DDA — No CAN Message from CAS

The DME expects cyclic CAS messages including terminal status and authorisation data. After approximately 400 ms with no messages once bus activity is active, this variant is set. This is the "CAS is offline" variant — often accompanied by a no-start condition because CAS authorisation is a prerequisite for engine operation on all CAS3/CAS4 vehicles.

• Crank-no-start or no-crank-no-start, depending on how severely CAS has failed
• Key may not be recognised
• Dashboard may show reduced function (no instrument cluster wake, limited functions)
• Comfort Access may fail (doors unresponsive, push-button-start not working)
• Diagnostic tools often cannot communicate with CAS at all

Ordered most to least likely for this failure mode:

1. Low battery or recent deep discharge — CAS is particularly sensitive to voltage events and many 2DDA complaints trace to battery condition
2. Water damage to the CAS module — the module is located near the steering column on E-series and has a known history of water ingress from A-pillar, firewall, or cabin leaks
3. Blown CAS fuse — check chassis-specific fuse locations (often in the glove box or cockpit fuse carrier)
4. CAS module internal failure after an overvoltage event (jump-start without correct procedure, alternator surge)
5. K-CAN / PT-CAN wiring fault between CAS and the rest of the bus

1. Test the battery first — thoroughly. Measure resting voltage, loaded voltage during cranking, and charging voltage. CAS is more voltage-sensitive than most modules. Replace or charge a suspect battery before further diagnostics.
2. Attempt CAS communication in ISTA/INPA. If CAS does not respond, treat as an offline module.
3. Check CAS fuses and power supply per the wiring diagram for the chassis. Verify B+ and relevant switched supplies at the CAS connector.
4. Physically inspect the CAS module for water damage. Remove trim as needed to access the module, check for corrosion or moisture at the connector and around the housing.
5. Measure CAN termination — both K-CAN (body) and PT-CAN (powertrain) as applicable on the chassis. Healthy readings are approximately 60 Ω on each network.
6. Inspect the KL30G relay and fuse as applicable — loss of KL30G can cause cascading communication failures involving CAS.

Correct the power, wiring, or module problem identified. For battery replacement always register the new battery via ISTA service functions or a capable aftermarket tool — an unregistered battery causes ongoing charging and electrical issues.

CAS replacement is not a simple swap: the CAS, DME, and at least one key must be synchronised. On modern BMWs, used CAS modules from other vehicles cannot be paired without cloning the original ISN. For CAS repair or cloning, use a qualified specialist. For new-CAS programming, refer to ISTA/P with the correct FSC data set.

After repair, clear all fault memory and verify a complete start cycle multiple times.

The DME receives CAS messages but either the terminal status message is missing from the expected set, or the data content is outside the plausible range. Detection window is around 500 ms. The CAS is generally online but its messaging is incomplete or inconsistent — often a partially-failing module or a specific signal path issue.

• Engine may start and run, then stall after a short period
• Intermittent no-start
• Warning lights on or dash messages about drivetrain or immobiliser
• Key recognition may work but start authorisation fails
• Accompanied by CAS-side codes — read both modules

Ordered most to least likely for this failure mode:

1. CAS module partial failure after a voltage event — certain internal functions degraded but the module still communicates
2. CAS to DME synchronisation lost — after DME, CAS, or key replacement without correct pairing
3. Terminal-status signal path issue — KL50 (start) or KL15 (ignition) wiring or relay problems
4. CAS software fault — can follow an interrupted coding or programming session
5. Wiring issue specifically affecting one of the terminal-status or torque messages

1. Read CAS fault memory. Look for terminal-status, ELV (electric steering lock), immobiliser, or internal CAS codes pointing to the specific subsystem involved.
2. Check for recent key/DME/CAS work. A synchronisation mismatch between CAS, DME, and keys produces plausibility-type faults. Use the CAS-DME synchronisation procedure in ISTA if applicable.
3. Verify battery and charging — marginal voltage events cause CAS-side partial failures.
4. Inspect KL30G relay on the junction box — degraded KL30G switching causes terminal-status signalling problems that reach the DME via this fault code.
5. Review any aftermarket electrical modifications that tap into ignition-switched wiring (alarms, remote starters, dashcams) — these can corrupt terminal-status signalling.

Repair the specific cause identified: re-synchronise CAS/DME if keys or modules have been changed; replace a failing KL30G relay; correct aftermarket wiring issues; replace a partially-failed CAS module via qualified repair or correct ISTA/P procedure.

For CAS-DME synchronisation, follow the ISTA service function exactly; partial or aborted procedures can leave the vehicle in a worse state. Refer to BMW ETK by VIN for part numbers on relays, CAS modules, and keys.

Clear codes on DME and CAS after repair and verify multiple successful start cycles.

The DME receives the CAS terminal-status message but the embedded alive counter or checksum is invalid over the detection window (approximately 200 ms — a tighter window than the plausibility check because terminal-status integrity is safety-critical). Indicates bus-level corruption or a CAS transmitter-side integrity fault.

• Intermittent start issues
• Warning lights cycling on/off
• Often accompanied by other modules reporting integrity errors if the cause is bus-level
• Can worsen with electrical load or temperature

Ordered most to least likely for this failure mode:

1. Bus-level corruption — damaged CAN wiring, bad ground reference on CAS or DME
2. CAS internal transmitter fault (partial electronics failure)
3. Poor connection at CAS or DME connector
4. Interference from aftermarket electrical modifications
5. Damaged terminating resistor (inside a module at the end of the bus)

1. Check whether other modules log checksum / alive-counter errors referencing CAS. Bus-level corruption usually produces multiple integrity faults across multiple receiving modules.
2. Measure CAN termination and inspect wiring — the same approach as for other checksum variants (~60 Ω at the OBD port, inspect wiring for damage).
3. Check CAS and DME ground paths — a bad ground on either end is a classic cause of checksum errors.
4. Audit aftermarket electrical installs that may be injecting noise onto the bus.
5. Inspect CAS connector for pushed pins, corrosion, or water damage.

Repair the wiring, grounding, or connector fault identified. If the issue is clearly inside the CAS module itself (no bus-level cause found, no other modules affected), the CAS is the suspect — repair or replacement requires the correct programming/synchronisation procedure as described for the other 2DDA variants.

Clear codes after repair and verify over multiple drive cycles and electrical loads.