P2512
Event Data Recorder Request Circuit LowP2512 is a generic OBD-II powertrain diagnostic trouble code: Event Data Recorder Request Circuit Low. It is logged by the engine control unit when the powertrain monitor detects that a specific fault threshold has been exceeded — typically resulting in the malfunction-indicator lamp (MIL / check-engine light) being illuminated.
What P2512 means
P2512 is set when the ECM/PCM detects a low voltage condition on the circuit that carries the Event Data Recorder (EDR) trigger request signal. The EDR, sometimes referred to as a crash data recorder or black box, is triggered by a dedicated circuit input to the ECM that signals a significant deceleration or impact event. When this input circuit is shorted to ground or the signal voltage is below the expected idle-state level, the ECM logs P2512.
The trigger circuit typically originates from an airbag control module or a dedicated crash sensor module. A low circuit condition may indicate a wiring fault between the airbag/crash module and the ECM, a fault within the triggering module itself, or a genuine trigger event that the circuit has not recovered from correctly. In most cases this is an electrical or wiring fault rather than evidence of an actual crash event.
While this code does not directly affect engine performance, it indicates the EDR trigger system may not function correctly in a genuine crash event, which has regulatory and safety implications. Additionally, the underlying wiring fault may be shared with other safety-related systems. Investigation should focus on the signal circuit continuity and the condition of the originating module before clearing the code.
Common causes
Most-frequently reported root causes when P2512 is logged.
-
1
Short to ground on the EDR request signal wire between the ECM and the triggering module.
-
2
Failed airbag control module or crash sensor module with an output shorted low.
-
3
Damaged wiring harness in the area of the firewall or under-dash routing.
-
4
Corroded or loose connector at the ECM EDR input pin.
-
5
Residual fault condition following a genuine crash event where the circuit did not reset.
-
6
Water intrusion into the airbag module or related connector causing a leakage path to ground.
Symptoms drivers notice
How to diagnose P2512
A typical diagnostic flow when this code is present.
-
1
Record all DTCs across all modules, paying particular attention to concurrent airbag or SRS codes.
-
2
Inspect the wiring harness from the ECM EDR input pin to the airbag or crash module for damage, chafing, or moisture intrusion.
-
3
Disconnect the triggering module and measure the voltage on the ECM input wire; if it rises to a normal reference level, the fault is in the module or its direct wiring.
-
4
Check the connector at both ends of the EDR signal circuit for corrosion or pushed-back pins.
-
5
Consult vehicle history for any recorded crash events that may have triggered the circuit and not been properly reset.
-
6
If wiring and connectors are intact, test the output of the crash/airbag module per the manufacturer service procedure.
-
7
Repair the identified circuit fault and verify the code does not return on a full drive cycle.
Vehicles where we've handled P2512
Platforms in our catalogue with confirmed P2512 coverage.
Related powertrain codes
Frequently asked questions
Does P2512 mean my vehicle was in a crash?
Not necessarily. P2512 is a circuit low fault that can result from a wiring or connector issue without any crash having occurred. Review vehicle history and the airbag module for crash event records to determine if an actual event took place.
Can I clear P2512 myself with a basic OBD-II scanner?
A generic scanner can clear the code, but it will return if the underlying circuit fault is not repaired. Additionally, any concurrent airbag codes require a specialist SRS scanner to read and clear safely.
Will P2512 affect my airbag deployment?
The fault is on the EDR request input to the ECM, not the airbag firing circuit. However, because the fault originates near safety-restraint wiring, any concurrent SRS codes should be investigated to ensure airbag function is not compromised.
Is P2512 common after a battery disconnect or jump-start?
It can occur if the battery event caused a voltage transient that set the code. If the circuit is physically intact, the code may clear and not return after a normal drive cycle.
Disabling P2512 in software
RaceTune can permanently disable P2512 — and any other OBD-II diagnostic trouble code — on every ECU family we support. The monitor is disabled inside the ECU itself, so the fault stops being logged: the warning light stays off and the engine never enters limp mode for this code. The change is tied to your exact software version.
ECUs with a P2512 disable in our catalogue
Confirmed coverage from our recipe database — we support many more families. Upload your file and our identifier will match it automatically.
- Bosch EDC17C50 verified 1 software version
Software modifications affect emissions compliance and are not road-legal in many jurisdictions. RaceTune service files are intended for motorsport, off-road, and export use.
Got P2512 in your scan?
Upload your ECU file — we'll identify the exact software version and confirm whether a disable is available for your car.
Upload your file