BMW fault 2DD8 - No message from AFS
P320A · P320B · P320C
Description
2DD8 is logged by the DME when it stops receiving valid CAN messages from the AFS (Active Front Steering) module. The DME uses AFS data for torque coordination during active steering interventions. When AFS communication is lost, the steering system falls back to a fixed ratio with conventional assist.
This code has 3 variants with different causes and fixes. Pick the one your scanner reported.
2DD8 / P320A Alive counter / checksum error
The DME receives AFS CAN frames but either the rolling alive counter is not incrementing correctly or the checksum validation fails. This variant combines two related integrity checks on the torque-request message flowing from AFS to DME. Typically indicates either a failing AFS transmitter or data corruption on the bus path.
Symptoms (4)
- "Active Steering fault" or "drive control system" warning.
- Steering effort feels abruptly different as the system falls back to a fixed ratio.
- Fault can be intermittent, often appearing after startup.
- Often accompanied by codes from AFS or DSC.
Common Causes (4)
- Water damage to the AFS module. AFS modules are mounted in locations prone to water ingress from clogged plenum drains or door membrane leaks.
- Corroded connector at the AFS module.
- Bus-level noise or ground issues corrupting the checksum.
- AFS internal software or firmware fault, usually accompanied by AFS-side codes.
Diagnosis Steps (4)
- Read fault memory, noting active vs. stored status. Scan AFS directly. If AFS reports water-related or internal hardware faults, the module itself is the likely cause.
- Physically inspect the AFS module for water damage. Remove trim as needed and check the module and its connector for moisture, corrosion, or tide marks.
- Check the AFS fuse per the wiring diagram and inspect the connector and harness for damaged pins, corrosion, or chafed wiring.
- If the module and wiring look clean, the issue may be an AFS software fault. Re-flashing AFS with the correct software can resolve it.
Resolution
If the AFS module is water-damaged, replace it and program and code the new module, then run the AFS initialization (steering-angle calibration and motor-position teach-in). Address the water-ingress source before refitting: clean clogged drains, check weatherstrips, inspect carpet for moisture. Clear all related faults across DME, AFS, and DSC after repair.
2DD8 / P320B Timeout
The DME expects cyclic torque-related messages from AFS. When no messages are received within the monitoring window after terminal 15 activates, this variant sets. The AFS is offline: it has lost power, is not on the bus, or the bus path between AFS and DME is broken.
Symptoms (4)
- Active Steering fault message.
- Steering feels fixed with no speed-variable ratio.
- Fault tends to persist rather than being intermittent.
- ISTA and INPA often cannot communicate with AFS at all.
Common Causes (4)
- Blown or missing AFS fuse. Sometimes removed by a previous owner to disable a failing system.
- Water damage to AFS module causing complete failure, or unplugged connector.
- Broken CAN wiring between AFS and the network.
- AFS power-supply wiring fault (B+ or ground at the module).
Diagnosis Steps (4)
- Read fault memory and attempt to communicate with AFS directly. If AFS does not respond, the module is effectively offline. Proceed as a power or communication problem.
- Check the AFS fuse per the wiring diagram. Verify B+ and ground at the AFS connector with a multimeter.
- Inspect the AFS module for water damage. Check the module and connector for moisture, corrosion, or tide marks.
- Check CAN wiring between AFS and the bus. Bus termination should read approximately 60 ohms at the OBD port with the network asleep.
Resolution
Replace fuses, repair wiring, or replace a failed AFS module as identified. After any AFS replacement, program and code the module, then run the AFS initialization procedure via ISTA. Fix the underlying water ingress before refitting a new module. Clear codes on DME, AFS, and DSC after repair.
2DD8 / P320C Plausibility error
The DME receives AFS messages with valid counter and checksum, but the torque-request value is outside the range the DME considers plausible for the current vehicle state. The AFS side is operational and transmitting cleanly, but its calculated outputs do not agree with the DME's model.
Symptoms (4)
- Active Steering fault with intermittent or persistent warning.
- Steering may behave strangely: incorrect effort at certain speeds, off-center feel, or pulling.
- Often triggered by steering-angle calibration issues.
- Can follow suspension, steering, or alignment work.
Common Causes (4)
- Steering-angle sensor out of calibration or reporting invalid data.
- AFS internal motor position not initialized, common after module replacement or battery disconnect.
- Torque sensor in the AFS rack producing incorrect data from corroded wiring.
- Mismatch between AFS variant coding and the physical hardware after a module swap.
Diagnosis Steps (4)
- Read AFS fault memory. Look for steering-angle, motor-position, plausibility, or torque-sensor codes inside AFS.
- Run the AFS initialization procedure via ISTA (steering-angle sensor calibration and motor-position teach-in). Many plausibility faults clear after a proper initialization.
- Check the steering column switch cluster (SZL), which contains the primary steering-angle sensor. SZL issues commonly cascade to both AFS and DSC.
- Inspect AFS rack wiring for chafed insulation. Verify coding and VIN match the fitted module if AFS was recently replaced.
Resolution
Address the root cause inside AFS. Run the ISTA initialization for steering-angle and motor-position. Replace SZL, torque sensor, or AFS rack components as needed. After any AFS or SZL replacement, re-run the full initialization sequence. Clear codes on DME, AFS, DSC, and SZL after repair.