BMW D9D690: Signal (object data, Automatic High Beam Assistant, 0x197) invalid, transmitter ADCAML/ADCAMM

D9D690 means the Automatic High Beam Assistant object-data signal transmitted by ADCAML/ADCAMM is invalid. The receiving FLM2 lighting variant stores this fault when message 0x197 arrives with unusable content or cannot be trusted. The code does not prove that the camera hardware has failed; operating conditions and the complete message path must be assessed together. What Does D9D690 Mean? D9D690 is Signal (object data, Automatic High Beam Assistant, 0x197) invalid, transmitter ADCAML/ADCAMM. The binding definition identifies the sending controller and message identifier, while the listed FLM2 variant indicates the receiving lighting context. This is a data-validity fault, not a direct bulb, headlamp motor, or high-beam output-circuit verdict. In practice, the system may disable automatic high-beam selection when dependable information about oncoming or preceding traffic is unavailable. Manual low and high beams can remain functional. Camera names and network topology vary by chassis, so confirm the installed equipment and controller variants from the VIN before applying a wiring or calibration procedure. Code: D9D690 Definition: Signal (object data, Automatic High Beam Assistant, 0x197) invalid, transmitter ADCAML/ADCAMM Module: FLM2 lighting receiver Key data: 0x197 object-data status Typical cause: invalid camera message or interrupted communication Severity: medium Note: confirm controller topology by VIN First save camera, lighting, and vehicle-network faults sharing the same timestamp; determine whether D9D690 is a consequence or the source. What Symptoms Does D9D690 Cause? The clearest symptom is that automatic high beam remains selected but does not raise the beam, or unexpectedly returns to low beam. The instrument cluster may show a limited driver-assistance function. A temporary event during rain, fog, frost, or dirty-glass conditions should be distinguished from a fault that repeats on every clear nighttime drive. • Automatic high beam appears enabled, yet no high-beam transition occurs on an empty dark road. • Function returning after the camera area is cleaned favors obstructed vision over permanent electronic failure. • Normal manual lamp control with only automatic selection missing largely excludes the main output circuit. • Camera communication faults timestamped with D9D690 carry more weight than an isolated bulb or driver fault. • Weather-dependent recurrence lets the stored freeze frame connect image quality with the triggering conditions. • Brief recovery after an ignition cycle followed by failure again points toward unstable message delivery. Why Does D9D690 Occur? D9D690 can begin with dirt, condensation, ice, or unsuitable film in the camera viewing area and extend to weak supply voltage, loose connectors, corrupted network data, or internal camera failure. Incorrect calibration after windshield work or incompatible coding after controller programming can also invalidate object data. Start with visible, inexpensive evidence before considering module replacement. • Dirt, condensation, ice, or unsuitable film ahead of the camera reduces usable image quality. • Weak battery voltage can wake camera and lighting controllers at different times during engine starting. • Loose or damp camera connections may make the 0x197 message intermittent or internally inconsistent. • Additional vehicle-network faults can deliver object data late, incomplete, or corrupted at the receiver. • Missing calibration after windshield replacement can make detected object positions unreliable for lighting decisions. • Incorrect coding or incompatible software levels can separate ADCAML/ADCAMM output from FLM2 expectations. • Internal camera or receiving-lighting-controller failure is considered only after the external paths are proven. How Do You Diagnose D9D690 with OBDThink? OBDThink is an independent BMW coding and diagnostics app and is not affiliated with BMW AG. Save the D9D690 freeze frame, mileage, and occurrence time, then run a complete scan of the camera, FLM2, and central body controllers. The objective is to determine whether 0x197 is invalid at its source or becomes invalid before reception. • 1. Scan every controller with OBDThink and preserve DTC records timestamped with D9D690. • 2. Confirm Automatic High Beam Assistant, ADCAML/ADCAMM, and FLM2 variants from the VIN equipment list. • 3. Clean the camera-side glass and inspect for cracks, misting, film, or obstructing accessories. • 4. Observe controller supplies during ignition wake-up and separate common undervoltage from communication failure. • 5. Monitor the 0x197 status data and distinguish a fixed invalid value from intermittent loss. • 6. Inspect camera and FLM2 connectors for moisture, weak connector pins, and movement-sensitive interruptions. • 7. If windshield work is documented, check the VIN-specified camera calibration procedure and completion status. • 8. After preserving evidence, clear the DTC memory and repeat a controlled nighttime function test. IF 0x197 is invalid at the source controller, THEN inspect camera visibility, calibration, and ADCAML/ADCAMM supply ELSE IF it is valid at the source but invalid at FLM2, THEN test the message path and receiver software ELSE IF D9D690 returns only under specific viewing conditions, THEN reproduce the glass and environmental influence The fastest split is comparing 0x197 status at the source and receiver during the same ignition cycle. How Is D9D690 Repaired? Repair follows the proven branch: cleaning the viewing area, correcting weak supply voltage, or repairing a connector should precede controller replacement. Windshield or camera-position changes require the specified calibration. Software and coding are addressed only after VIN compatibility is confirmed, while camera or FLM2 replacement remains the final, evidence-based step. • Low cost: Clean the camera viewing area and remove cabin moisture causing repeated condensation. • Low cost: Correct a weak battery, loose battery terminal, or unstable charging condition. • Medium cost: Repair damaged wiring, clean damp connectors, and replace a loose connector pin. • Medium cost: Recalibrate with VIN-compatible targets after the windshield or camera has been disturbed. • Medium cost: Align proven incompatible coding or software levels through the applicable BMW procedure. • High cost: Program and replace ADCAML/ADCAMM or FLM2 only when internal failure is demonstrated. A successful repair means D9D690 no longer occurs and automatic high beam behaves consistently during a controlled nighttime test. Can You Drive with D9D690? The vehicle can usually be driven cautiously if manual low and high beams operate normally, but do not rely on automatic high-beam assistance. Control the lamps manually at night and avoid dazzling approaching traffic. If manual lighting is also unavailable, the concern is no longer limited to driver assistance and nighttime driving should be postponed. Leaving the code unresolved for days can hide a broader camera, network, or undervoltage problem. Arrange diagnosis soon when D9D690 returns on every drive after the glass is cleaned. Stop safely if the lamps flicker, a burning odor appears, multiple electrical warnings develop, or exterior lighting goes completely dark. Do not drive at night without working manual low beams; park safely and have the lighting circuit inspected. What Questions Are Common About D9D690? Common questions concern immediate camera replacement, glass cleaning, and calibration. The definition describes invalid data and does not automatically condemn one component. These answers help separate a simple visibility or supply problem from a genuine controller fault before expensive parts are ordered. • Can dirty glass alone cause D9D690? Yes, blocked vision can invalidate object data. If it returns on clean glass, also test supply, communication, and calibration. • Should the camera be replaced immediately? No. Camera replacement is an expensive guess until 0x197 source status, supply, connectors, and VIN calibration are tested. • Is clearing the code a repair? No. Clearing creates a clean retest; repair is confirmed only when D9D690 stays absent during controlled nighttime operation. The strongest next step for D9D690 is preserving synchronized controller evidence and comparing 0x197 at the source with its state at the receiver. That split prevents a simple visibility or supply fault from becoming an unnecessary camera or lighting-controller replacement.