BMW 31A2 — Message: Stationary Loads/Consumers
- Severity
- Informational
- Module
- DME
- OBD-II Code
- U1169
Description
BMW hex code 31A2 is a CAN bus communication fault stored by the DME (Digital Motor Electronics). It indicates that the DME has stopped receiving a CAN message related to the status of stationary electrical loads and consumers in the vehicle. This message is used by the DME to factor electrical load information into idle speed control, alternator load management, and fuel consumption calculations.
The DME monitors for a cyclic CAN message carrying the current status of stationary electrical consumers (heated seats, rear window defroster, HVAC blower, auxiliary heater, etc.). When this message is absent for more than 25.5 seconds with terminal 15 on and battery voltage above 11.0 V, the DME sets this fault. The SETZBEDINGUNG references an OBD sensor, indicating this message is also tied to an OBD-related monitoring function that relies on electrical load data for emissions calculations.
31A2 - U1169: Message: Stationary Loads/Consumers - Lost communication
Symptoms
No warning lights or Check Control messages are triggered by this fault. The driver is unlikely to notice any change. The DME may default to a fixed electrical load estimate for idle speed and alternator regulation, which can result in a slightly higher or less stable idle when heavy electrical consumers are active. OBD readiness monitors that rely on accurate electrical load reporting may not complete, potentially causing emissions test failures.
Common Causes
Source module fault. The module broadcasting electrical load status (varies by platform — often the JBE, BDC, or power management module) may have an internal fault or software issue. Check the source module for stored faults.
Gateway routing issue. This message typically originates from the body CAN network and is routed to the powertrain CAN by the central gateway (JBE/BDC/ZGW). A miscoded or faulty gateway can block the message. This is especially common after a gateway module replacement or software update.
CAN bus wiring fault. Physical damage to the CAN-High or CAN-Low wires, corroded connector pins, or a broken termination resistor can prevent the message from reaching the DME. Since this is a cross-domain message (body to powertrain), the fault could be on either CAN segment or at the gateway.
Low battery voltage. The monitoring conditions require battery voltage above 11.0 V. If the battery is marginal, the source module may drop offline intermittently, triggering this fault during high-load electrical situations (cold start with heated seats, lights, and HVAC all active).
Missing module or incorrect VO coding. If the DME software expects this message from a module that is not installed or was removed (e.g., after a retrofit or equipment change), the fault will be set every drive cycle. Correcting the vehicle order (FA) to match actual equipment resolves this.
Diagnosis Steps
Full vehicle scan. Read fault codes from all modules. Look for communication faults stored in other modules — particularly the JBE, BDC, ZGW, or power management module. If multiple modules report lost messages on the body CAN network, the issue is with the shared bus or gateway. If only the DME reports this fault, the problem is likely specific to the source module or the gateway routing for this particular message.
Identify the source module. The message relates to stationary electrical loads. On E-series vehicles this is typically broadcast by the JBE (Junction Box Electronics). On F/G-series vehicles it may come from the BDC (Body Domain Controller) or a dedicated power management module. Check the source module for faults and verify it is functioning and communicating on its local CAN bus.
Check the gateway. Read faults from the ZGW/JBE/BDC gateway function. Verify the gateway is coded to route this message to the powertrain CAN. If the gateway was recently replaced, reprogrammed, or updated, message routing tables may need to be re-established via VO coding.
Check battery health. Measure resting battery voltage (should be above 12.4 V) and charging voltage with engine running (13.8–14.4 V). If the battery is weak, replace it and register the new battery via ISTA before proceeding with further diagnosis.
Measure CAN bus resistance. With battery disconnected, measure CAN-High to CAN-Low at the OBD port. Expected: 60 Ω. If the value is significantly off, use the isolation method (disconnecting modules one at a time) to identify the source of the resistance anomaly.
Clear and monitor. After addressing the root cause, clear all faults and run the vehicle with ignition on for at least 30 seconds (beyond the 25.5-second detection threshold). Re-scan to confirm 31A2 does not return.
Resolution
If the source module is faulty, replace or reprogram it as needed — consult RealOEM with your VIN for the correct part number. If the gateway is not routing the message correctly, recode the gateway via VO coding in ISTA or E-Sys. If CAN bus wiring is damaged, repair the affected harness section. If the fault is spurious (DME expects a message from a module not present in the vehicle), correct the vehicle order (FA) to match actual equipment. A weak battery should be replaced and registered. Clear all faults from all modules after any repair.