C1360 – ESP Irreversible error (Hyundai)

Hyundai-specific code — factory diagnostic data

C1360 means the vehicle has a stability-control related fault that the system treats as non-recoverable. You may lose or limit ESC/traction functions, and some driver-assist features may reduce capability. On the Hyundai IONIQ 5, this often shows up as multiple warnings after a restart or during wet, slippery conditions. According to Hyundai factory diagnostic data, C1360 indicates an ESP Irreversible error. This is a Hyundai-defined, manufacturer-specific code, and the exact detection logic can vary by platform and software. Treat it as a direction to verify power, grounds, communications, and plausibility inputs before replacing parts.

🔍Check Hyundai recalls and safety ratings for your vehicle — free VIN decoder with NHTSA data

C1360 Quick Answer

C1360 on Hyundai indicates an ESP Irreversible error. The ADAS_D (ADAS Driving) module logged a stability-control fault it cannot clear by normal self-checks, so you must verify power/ground, network health, and related sensor data.

What Does C1360 Mean?

Official definition: C1360 on Hyundai means ESP Irreversible error. In plain terms, the vehicle’s stability system detected an internal or external condition that it considers “not trustworthy,” so it limits or disables ESP-related functions to stay safe. In practice, that can reduce stability control, traction control, and some ADAS behaviors that depend on yaw/acceleration and brake intervention data.

What the module actually checks: the ADAS_D (ADAS Driving) module does not “see” ESP directly. It evaluates ESP status, availability, and plausibility through network messages and shared sensor data. The system expects consistent, timely signals and valid self-test results. Why it matters: this DTC points to a suspected trouble area, not a confirmed failed part. Per SAE J2012-DA guidance, you must identify the root cause with testing. Start with power/ground integrity under load, then network integrity, then plausibility of shared inputs.

Theory of Operation

Under normal conditions, Hyundai’s ESP function uses brake hydraulic control, wheel speed inputs, steering angle, and vehicle motion sensing. The ABS/ESC controller calculates yaw and slip. It then commands brake pressure and torque reduction to keep the vehicle stable. Other modules, including ADAS_D (ADAS Driving), rely on that “vehicle dynamics truth” to support features like stability-dependent warnings and intervention limits.

C1360 sets when the system flags an “irreversible” condition. That usually means the controller cannot validate its self-checks or the supporting data stream. A brief glitch may set a different intermittent code. An “irreversible” error tends to latch until the fault no longer exists and the module confirms stable operation. Power dips, ground voltage drop, corrupted CAN messages, or implausible dynamics signals can all trigger this logic on the IONIQ 5 platform.

Symptoms

Drivers and technicians usually notice stability and ADAS changes first.

• Scan tool ADAS_D and/or brake/ESC modules may show current DTCs, “not available” data fields, or intermittent module list dropouts
• Warning lamps ESC/traction warnings, and sometimes ADAS-related warnings depending on feature set
• Reduced assist Driver-assist features may limit operation when stability data looks unreliable
• Traction change Increased wheel spin or reduced traction control intervention on slippery surfaces
• Stability change Less corrective braking feel during aggressive turns or evasive maneuvers
• Restart behavior Warning clears after key cycle, then returns after driving or after a self-test sequence
• Multiple codes Companion chassis or communication codes may appear in several modules

Common Causes

• Low system voltage during initialization: A weak 12V supply or a voltage dip during key-on can corrupt ESP self-check logic and trigger an “irreversible error” flag in ADAS_D.
• High-resistance power or ground to the ADAS_D or brake/ESP network: Corrosion, a loose fastener, or a damaged splice can pass a static voltage check but fail under load, which causes internal monitoring to declare a non-recoverable fault.
• CAN communication integrity fault between ADAS_D and stability control: Noise, intermittent opens, or shorts on the CAN wiring can break message timing and plausibility, leading the module to stop trusting ESP status data.
• Connector water intrusion at ADAS/ABS-related harness points: Moisture wicks into terminals and raises resistance, which creates intermittent resets and corrupted data during ESP checks.
• Aftermarket wiring or accessory load on shared circuits: Added devices can backfeed or overload an ignition or battery feed, which disrupts module boot-up and sets irreversible internal error logic.
• Module software mismatch or incomplete programming: A missed calibration, wrong variant coding, or interrupted update can leave the module with invalid configuration data and trigger the irreversible error condition.
• Intermittent internal module fault in the ADAS_D or related ESP controller: An internal memory or processor fault can set a permanent-style error, but you must prove clean power, ground, and network first.
• Harness damage near high-movement or pinch areas: A rubbed-through section can intermittently short to ground or power, which forces the controller to log a non-recoverable ESP error event.

Diagnosis Steps

Use a scan tool that can access Hyundai ADAS_D (ADAS Driving) data, run a full network scan, and view freeze frame. Have a quality DMM, a test light or load tool, and back-probe pins. Keep wiring diagrams and connector views for the IONIQ 5 platform. Plan to perform voltage-drop tests under load and a basic CAN integrity check.

1. Confirm C1360 and record all DTCs from every module. Save freeze frame for C1360 and note battery voltage, ignition state, vehicle speed, and any network-related companion codes. Freeze frame shows conditions when the fault set. Use a scan-tool snapshot later to catch intermittent drops during a road test.
2. Check whether ADAS_D appears in a full network scan and communicates reliably. If the module drops offline, treat it as a power/ground or network integrity problem first. Document any U-codes or power-supply codes that point to the same event.
3. Inspect the 12V battery condition and charging system operation. Look for recent jump-start history, low voltage events, or loose battery terminals. A low-voltage boot event often triggers irreversible-style errors on Hyundai systems.
4. Check fuses and power distribution before probing any ECU connector. Verify all related fuses for continuity and for power on the correct side with the circuit energized. Do not stop at a visual fuse check.
5. Verify ADAS_D power and ground under load using voltage-drop testing. Load the circuit with the module connected and operating. Measure ground drop from the module ground pin to battery negative and keep it under 0.1V. Next, measure power-feed drop from battery positive to the module power pin while loaded. High drop proves resistance in wiring, splices, or connectors.
6. Inspect connectors and harness routing for ADAS_D and the stability control/ABS network path. Look for water intrusion, fretting, bent pins, poor terminal tension, and aftermarket splices. Focus on areas with movement, sharp brackets, and known pinch points. Repair terminal fit or corrosion before any module conclusions.
7. Use the scan tool to check live data and status related to ESP operation. Watch for module resets, “not available” ESP states, or implausible status transitions. Compare the time stamps of any related DTCs to see which module complained first.
8. Perform targeted circuit checks for any related FTB subtype when available (example: -81 decoded via SAE J2012DA as a standardized fault-type byte). Use the subtype to guide your test direction. If the subtype indicates “erratic/intermittent,” prioritize wiggle testing, connector pin fit, and voltage-drop during vibration. If it indicates “open circuit” or “short,” isolate and test the suspect branch with the harness disconnected.
9. Check CAN integrity if you have any network symptoms or companion U-codes. With ignition OFF and the 12V battery disconnected, measure resistance between CAN+ and CAN- at an accessible module connector. A healthy network reads about 60 ohms. Then switch ignition ON and check CAN bias voltage to ground at the same point. You should see about 2.5V bias on both lines. Only take bias readings with ignition ON.
10. Clear DTCs and perform a controlled key-cycle and road test. Recheck for pending versus confirmed status. Many faults require repeat detection before the code stores, while hard power or network faults often return immediately at key-on. If C1360 returns, repeat voltage-drop and wiggle tests while capturing a scan-tool snapshot to correlate the fault with a voltage or communication event.
11. If all power, ground, and network tests pass, verify software and configuration status. Confirm the correct variant coding and check for incomplete updates using Hyundai service procedures. Only after you prove clean inputs, stable power/ground, and reliable network should you consider an internal module fault.

Professional tip: Treat “irreversible error” as a consequence, not a part diagnosis. Hyundai modules will lock in this status when they see a critical event during boot-up or message validation. Use voltage-drop under load and a snapshot during a wiggle test to catch the moment it fails. That approach prevents unnecessary ADAS_D or stability control module replacement.

Possible Fixes

• Repair power or ground path resistance: Clean and tighten grounds, repair damaged wiring, and correct splice or terminal issues proven by voltage-drop testing.
• Restore stable 12V supply: Service the 12V battery connections, correct charging concerns, and eliminate key-on voltage dips that match the freeze frame data.
• Repair CAN wiring or connector faults: Fix opens, shorts, water intrusion, or terminal fit problems that disrupt ESP-related message flow.
• Remove or correct aftermarket electrical loads: Rewire accessories to proper power sources and eliminate backfeed or overload on shared ignition/battery circuits.
• Update or correct module software/configuration: Complete programming and verify variant coding after you confirm stable power and network integrity.
• Replace the failed module only after verification: Consider ADAS_D or a related controller only when power, ground, and communication tests prove stable and the code persists.

Can I Still Drive With C1360?

You can usually drive the Hyundai IONIQ 5 with C1360 stored, but you must treat it as a safety-system fault. Hyundai labels this as an ESP Irreversible error, so the vehicle may reduce or disable stability control functions. The ADAS_D (ADAS Driving) module may also limit driver-assist features that depend on ESP status. Plan for longer stopping distances on slick roads. Avoid aggressive steering inputs and hard braking. If the brake warning, ESC warning, or multiple ADAS warnings stay on, drive only as needed and head to diagnosis. If the pedal feel changes, the vehicle pulls, or warnings multiply quickly, stop driving and tow it.

How Serious Is This Code?

C1360 ranges from inconvenient to serious, based on what else fails with it. When it acts alone and clears after a key cycle, it often points to a temporary integrity problem. That can include low voltage or a brief network drop. When it stays current, Hyundai treats “irreversible error” as a controller-level integrity concern. The system may lock out ESC, traction control, or related brake-assist logic. On the IONIQ 5, that also affects ADAS behavior and warning strategy. Do not assume a module failure. Verify power, grounds, and network health first. If you replace any ADAS or brake-related module, expect calibration or initialization before you can safely rely on driver-assist features again.

Common Misdiagnoses

Technicians often replace parts because the text sounds final. “Irreversible” does not prove a bad module. It describes what the ADAS_D module decided after its self-check. The most common miss is skipping a loaded power and ground test. A clean voltage reading with no load proves nothing. Another frequent error involves ignoring network DTCs in other modules. A brief CAN fault can trigger this code, then disappear. Shops also confuse this with a wheel speed sensor issue and start replacing sensors. Hyundai will usually log separate sensor or plausibility codes for that. Avoid wasted spending by capturing a full vehicle health report, checking freeze frame, and verifying ADAS_D power, grounds, and communication before any replacements.

Most Likely Fix

The most commonly confirmed repair direction involves restoring stable module power, ground, and network integrity. Start with a battery and charging system check, then perform voltage-drop tests on the ADAS_D power and ground circuits under load. Next, inspect connector fit, water intrusion signs, and terminal tension at the ADAS_D module and related junctions. If other modules log communication faults, diagnose the CAN wiring and termination health before blaming ADAS_D. Only after those checks pass should you consider module software updates, initialization procedures, or module replacement. After any module repair, confirm the fix with a road test that allows ESC and ADAS functions to re-run their self-checks. Enable criteria vary by Hyundai system, so follow service information.

Repair Costs

Repair cost depends on whether the confirmed root cause is wiring, connector condition, a sensor, a module, or the labor needed to diagnose the fault correctly.