BMW CB9517: Signal (control, deactivation, electric fuel pump, crash, 0x19B) invalid, transmitter ACSM

CB9517 is “Signal (control, deactivation, electric fuel pump, crash, 0x19B) invalid, transmitter ACSM.” A receiving control unit records it when the crash-related pump-shutdown message from ACSM is absent, implausible, or inconsistent with the vehicle state. The code describes network information, not proof that the fuel pump itself has failed. What Does CB9517 Mean? CB9517 means a receiver cannot trust the 0x19B command that tells the electric fuel-pump system whether crash deactivation is requested. ACSM originates that safety status after evaluating restraint and impact information. The receiving module checks message validity, timing, and state coherence rather than measuring fuel pressure directly. In practice, diagnosis must distinguish a genuine stored crash event, interrupted communication, low-voltage history, and incompatible coding. A vehicle repaired after an impact may retain crash information even when wiring is intact. Conversely, a no-start without crash history can point toward network reception, ACSM power, or module configuration rather than a damaged pump. Code: CB9517 Definition: Signal (control, deactivation, electric fuel pump, crash, 0x19B) invalid, transmitter ACSM Module: receiving vehicle control unit / transmitter ACSM Key data: ACSM crash status and electric fuel-pump enable state Typical cause: invalid or missing crash-deactivation message Severity: high after a collision or with fuel leakage Note: the DTC does not by itself condemn the electric fuel pump First compare ACSM crash status with the receiver’s pump-enable state; this separates a real safety command from a communication fault. What Symptoms Does CB9517 Cause? CB9517 can accompany a crank-no-start because the electric fuel pump remains inhibited, but it may also exist only as a stored network code. The decisive observations are whether ACSM reports a crash state, whether the pump enable command changes, and whether other receivers lose the same 0x19B message simultaneously during the recorded event. • Engine cranks normally while measured low-pressure fuel delivery remains absent despite an otherwise valid start request. • Fuel-pump enable status stays inhibited although ACSM live data shows no current crash condition after key-on. • Several receiving modules store the same missing 0x19B message at an identical mileage and voltage snapshot. • A recently repaired collision vehicle retains restraint crash status and refuses normal electric-pump activation after assembly. • The code appears during undervoltage events, while pump operation returns normally after stable battery support is connected. • ACSM communication disappears from the network scan together with other restraint-related status values and identification data. Why Does CB9517 Occur? CB9517 occurs when the crash-deactivation information cannot be validated, not simply when fuel pressure is low. Start with event history and supply voltage, then inspect ACSM communication and the relevant network path. Only after those checks should coding, internal module failure, or an actual crash-triggered safety state become the primary explanation. • A weak battery interrupted ACSM transmission while the receiver captured an invalid 0x19B status during starting. • A genuine collision event stored crash deactivation and kept the electric fuel-pump enable request in its safe state. • ACSM power or ground was lost, preventing the restraint controller from broadcasting a coherent crash-control message. • Network wiring damage near repaired bodywork corrupted message delivery without directly damaging the electric fuel pump. • Replacement ACSM or receiving-module coding does not match the vehicle order, creating an implausible safety-state interpretation. • An internal ACSM or gateway communication defect persists after verified supplies, wiring, coding, and crash history checks. How Is CB9517 Diagnosed with OBDThink? Use OBDThink to save the complete scan, stored freeze frame data, system voltage, and mileage before clearing stored fault codes. Compare ACSM crash status with the electric fuel-pump enable state in the receiving module. OBDThink is an independent BMW coding and diagnostics app and is not affiliated with BMW AG. • 1. Record CB9517 occurrence mileage, voltage, and status before changing battery support or clearing stored fault codes. • 2. Scan ACSM, gateway, and fuel-pump control modules; note which receivers report the same 0x19B failure. • 3. Read ACSM crash and restraint deployment status, then compare it with documented collision and repair history. • 4. Observe the electric fuel-pump enable request during key-on and cranking without commanding unsafe forced activation. • 5. Stabilize battery voltage and repeat the scan; disappearing communication codes identify a supply-related event pattern. • 6. Verify ACSM power and ground under load when its identification or live data intermittently vanishes. • 7. Inspect repaired body areas for pinched network wiring, disturbed connectors, moisture, or incomplete connector locking. • 8. Confirm module coding against the VIN only after crash status, supplies, and physical communication paths pass testing. IF ACSM reports an active crash state AND the pump-enable request remains inhibited, THEN follow the BMW crash-repair and release procedure. ELSE IF ACSM is unreachable AND several receivers lose 0x19B together, THEN load-test ACSM power, ground, and the network path. ELSE IF communication returns with stable battery support, THEN investigate the undervoltage event before replacing any module. ELSE compare VIN-specific coding and software integration across ACSM, gateway, and the receiving controller. The fastest distinction is state versus transport: a valid crash state with an inhibited pump is different from a missing ACSM message across several receivers. How Is CB9517 Repaired? Repair follows the branch proven by scan data. Restore voltage or communication first, complete documented collision work when ACSM genuinely reports a crash state, and correct coding only when hardware paths test normally. Replacing the electric fuel pump does not repair an invalid 0x19B message unless separate tests prove that pump hardware also failed. • Appropriate: charge and test the battery, then correct unstable supply connections that interrupted ACSM communication. • Appropriate: reseat and repair verified damaged connector pins or network wiring near the documented body repair. • Moderate: complete BMW-specified crash-system service and authorized reset procedures after all deployed components are repaired. • Moderate: encode the replacement ACSM or receiver correctly when VIN comparison proves configuration inconsistency. • High: replace a gateway only after repeatable message loss remains with confirmed power, ground, and wiring integrity. • High: replace ACSM only when its internal communication defect is confirmed and crash-service requirements are satisfied. After repair, CB9517 no longer occurs, ACSM remains reachable, and the pump-enable state agrees with the verified non-crash vehicle condition. Can You Drive with CB9517? Do not drive if CB9517 follows a collision, restraint deployment, fuel odor, visible leakage, or repeated engine stalling. The pump-deactivation message is part of crash safety logic, so bypassing it or forcing pump operation can create fire risk. A workshop should inspect the vehicle before any road test under those conditions. If the code is historical, the car starts normally, no crash state is active, and no fuel leak exists, a short trip for diagnosis may be reasonable. Still, save the evidence promptly because intermittent ACSM power or network loss can return and inhibit starting without warning. Stop immediately after a collision, with fuel odor, leakage, or stalling; never bypass crash-related pump deactivation. What Questions Are Frequently Asked? The following answers clarify why CB9517 can remain after collision repair, why clearing it is not a diagnosis, and when the pump itself deserves testing. The stored states and cross-module message pattern matter more than the presence of a single code in one receiver. • Does CB9517 prove the electric fuel pump is defective? No. It identifies invalid crash-deactivation information; test pump hardware separately only after message validity and enable status are established. • Can CB9517 be cleared after a battery change? It may clear if undervoltage caused the event, but returning 0x19B errors require supply and network diagnosis rather than repeated erasure. • Why does CB9517 remain after collision repair? ACSM crash status, incomplete restraint work, configuration, or damaged communication wiring can remain unresolved even when exterior panels look finished. Preserve the scan before erasing anything, compare ACSM crash status with the receiving module’s pump-enable state, and let that evidence choose between collision service, electrical repair, or coding correction.