P2513 — Event Data Recorder Request Circuit Low

The diagnostic trouble code P2513 indicates an issue related to the Event Data Recorder (EDR) request circuit, specifically a low voltage or signal problem. This code generally suggests that the vehicle’s system is not receiving the expected signal from the EDR request, which could be linked to wiring, sensors, or the module itself. It’s important to understand that labels for this code may vary between different vehicle manufacturers, so always refer to specific OEM documentation for precise terminology.

—

Manufacturer variations for trouble code P2513

The P2513 code can be labelled differently depending on the vehicle’s manufacturer. Since OEMs often have proprietary terminology, the same fault may be represented under varying codes or labels, which makes cross-referencing essential during diagnosis. Here are some of the known variation labels:

• Ford: P2513 — Event Data Recorder Request Circuit Low
• Honda: code may be related to CAN Bus or data recorder circuit errors, not explicitly labeled as P2513
• Volkswagen / Audi / Skoda / Seat: May refer to similar data request circuit issues under generic CAN communication fault codes
• Other brands: Variations might include codes indicating issues with vehicle data logging or communication modules

—

What does trouble code P2513 mean?

P2513 signifies that the Electronic Control Unit (ECU) — the vehicle’s main computer — has detected a low voltage or weak signal in the circuit responsible for requesting or communicating with the Event Data Recorder (EDR). The EDR is a safety feature that records critical vehicle data, especially during a crash. When the ECU notices that the circuit signal is below expected levels, it triggers this diagnostic trouble code.

Essentially, the system monitors the integrity of the communication circuit. If it observes a recurring weak or missing signal, it sets the code. Typical causes include wiring issues, faulty modules, or power supply problems. The appearance of this code often coincides with other communication or data-related fault codes and may occur during routine diagnostics or as part of a vehicle’s self-test procedure.

—

Severity and risks of trouble code P2513

The P2513 fault is generally considered to have a moderate severity. While it does not usually interfere with the core driveability of the vehicle, it could compromise the functionality of the Event Data Recorder, which plays a crucial role during vehicle crash scenarios. If the recorder cannot properly log data, it might affect safety and accident investigations. Moreover, this code can sometimes be indicative of broader communication issues within the vehicle’s network.

Can the vehicle be driven? Yes, in most cases, the vehicle remains drivable, but it is advisable to diagnose and repair the fault promptly to ensure all safety systems function correctly and to prevent potential further circuit issues.

—

Symptoms of trouble code P2513

Often, the P2513 code does not present with clear or immediate symptoms, making it a rather subtle fault that may go unnoticed unless diagnosed via OBD scanner. However, some typical signs include:

• Warning lights on the dashboard, such as the ABS or vehicle safety systems indicator
• Intermittent or no recording of crash or event data
• Communication errors appearing in the vehicle’s data bus
• Malfunction indicators related to data logging or vehicle safety modules

It’s worth noting that in many cases, this fault is discovered during routine diagnostics or when a technician checks for stored fault codes during repairs. So, if your vehicle exhibits any of these symptoms, a proper checkup is recommended.

—

Most likely causes of trouble code P2513

The P2513 fault is commonly caused by issues related to weak or disrupted electrical signals in the data request circuit. Several causes are more prevalent than others, especially in vehicles where data communication systems are complex and sensitive:

1. Damaged or corroded wiring: Faulty wiring, connector corrosion, or loose connections in the EDR request circuit are often the primary causes.
2. Faulty wiring harness or connectors: Frayed cables, broken pins, or poor connections can lead to weak signals.
3. Failed or malfunctioning EDR control module: A fault within the event data recorder control unit or associated modules can cause low voltage signals.
4. Power supply issues: Low voltage supply to the requesting module or EDR system due to battery or alternator problems.
5. CAN bus communication errors: Network issues affecting signal integrity, such as bus overloads or damaged network wiring.

—

How to diagnose trouble code P2513

Diagnosing P2513 requires a systematic approach, combining visual inspection, live data analysis, and electrical tests. The goal is to identify the source of the low request signal or communication breakdown effectively.

1. Visual inspection: Check the wiring loom, connectors, and pins related to the EDR request circuit for damage, corrosion, or disconnection.
2. Scan the vehicle for codes: Use a compatible diagnostic scanner to verify all related codes and retrieve live data for the specific circuit voltages and signals.
3. Test circuit continuity: Perform an electrical continuity test on the wiring harness to ensure there are no open circuits or shorts.
4. Check voltage supply: Measure the voltage at the circuit connector to confirm correct power levels and signal presence.
5. Inspect the control modules: If wiring and power are good, test or replace the EDR control module or handle with OEM-specific diagnostic tools.
6. Network diagnostics: Use a diagnostic tool capable of analysing the vehicle’s CAN bus network to identify communication faults.

—

Possible repairs for trouble code P2513

Once the root cause is identified, repairs may range from simple to complex. Below is a list of potential corrective actions:

• Repaired or replaced damaged wiring and connectors: This is a basic repair that requires minimal expertise.
• Cleaning or reseating connectors: Ensuring good contact can resolve intermittent issues and is a straightforward task.
• Replacing faulty modules: The Event Data Recorder or related control units requiring professional handling, often involving programming or coding to OEM specifications.
• Battery and charging system check: Ensuring the vehicle’s electrical system supplies stable voltage—sometimes a simple battery or alternator repair suffices.
• Network diagnostics and repairs: Fixing CAN bus wiring or replacing damaged nodes should be performed by experienced technicians.

—

Vehicles commonly associated with trouble code P2513 in Europe

P2513 is more frequently observed in certain vehicle brands, especially those with complex electronic systems and advanced safety modules. In Europe, vehicles from the following brands and engine families are more likely to present this fault:

Ford: Focus, Fiesta, Kuga, Mondeo (especially with advanced driver-assistance systems)

Honda: Civic, CR-V, Accord (notably models with advanced data systems)

Volkswagen Group: Golf, Passat, Tiguan, Skoda Octavia, Seat Leon (in vehicles with complex CAN bus communication systems)

Noteworthy that the issuance of this code does not appear to be model or engine-specific but rather linked to vehicles with integrated data recording and communication systems.

—

Frequent mistakes with trouble code P2513

Diagnosing and repairing P2513 involves some common pitfalls that can lead to misdiagnosis or incomplete repair. Being aware of these mistakes can save time and prevent unnecessary part replacements.

• Ignoring the wiring inspection: Assuming only the control module is faulty without verifying wiring integrity can lead to incomplete repairs.
• Replacing modules without testing: Swapping parts based solely on code appearance without proper electrical testing may not resolve the issue and could restore the fault temporarily.
• Overlooking the vehicle’s electrical system: A weak battery or failing alternator can cause voltage fluctuations that trigger the code. Always ensure electrical system health.
• Misinterpreting the code: Assuming that P2513 relates only to the request circuit when it may be indicative of a broader network issue.

—

Quick FAQ — trouble code P2513

Q1: Can this code disappear on its own?
A1: It is unlikely for the code to clear itself unless the underlying issue is resolved. Temporary voltage drops may sometimes cause the fault to appear intermittently, but persistent problems will usually trigger a stored fault code.

Q2: Can I keep driving?
A2: Yes, but with caution. While core driveability may not be affected, the issue could impact safety systems or recording capabilities. It is recommended to diagnose and repair the fault promptly.

Q3: Why does the code return after clearing?
A3: The root cause, such as wiring damage, faulty module, or electrical supply issues, has not been resolved. Until the underlying problem is fixed, the code will likely reappear.