U130F – DC EVSE Communication Error (Hyundai)

Hyundai-specific code — factory diagnostic data

U130F means your Hyundai IONIQ 5 and the DC fast charger are not “talking” correctly during a DC charging session. In real life, the charger may refuse to start, stop mid-session, or charge at a reduced rate. According to Hyundai factory diagnostic data, this code indicates a DC EVSE Communication Error logged by the PCM (Powerline Communication Module). This is a manufacturer-specific Hyundai code, so the exact enable conditions can vary by platform. Treat it as a direction to test the charging communication path first. Do not assume a bad charger or a bad vehicle module without verification.

🔍Decode any Hyundai IONIQ 5 VIN — free recalls, specs & safety ratings — free VIN decoder with NHTSA data

U130F Quick Answer

U130F points to a communication failure between the vehicle and a DC EVSE during DC charging. Most confirmed causes involve the charge inlet connection, PLC communication integrity, or power/ground and wiring issues to the PCM.

What Does U130F Mean?

Official meaning (Hyundai-defined): U130F is defined as DC EVSE Communication Error. The PCM sets it when the vehicle cannot complete or maintain the required communication with the DC charger to authorize and manage DC charging. In practice, that means the vehicle and charger cannot negotiate charging correctly, so charging may not start or may stop unexpectedly.

What the module actually checks and why it matters: The PCM monitors the DC charging communication link used for EVSE-to-vehicle signaling. On Hyundai platforms this typically involves powerline-based signaling over the charge interface and coordinated messages with other controllers. The PCM expects valid communication within specific time windows and message patterns during the DC charge sequence. When those checks fail, the PCM records U130F to flag a suspected trouble area, not a confirmed failed part. Your diagnosis must prove whether the fault comes from the charger connection, wiring, power/ground integrity, or module logic.

Theory of Operation

During normal DC fast charging, the IONIQ 5 establishes a secure “handshake” with the EVSE. The vehicle verifies the plug connection, confirms safety states, and then exchanges control data so the charger can deliver the correct current and voltage. The PCM (Powerline Communication Module) supports this process by managing the communication channel used for DC charging coordination.

U130F sets when that handshake breaks down or never completes. The PCM sees missing, invalid, or unstable communication at a point where it expects clean, repeatable signaling. Poor terminal contact at the inlet, corrosion or damage in related wiring, weak power or ground to the PCM under load, or intermittent connector fit can all disrupt the communication long enough to trigger the code.

Symptoms

U130F typically shows up during DC fast charging attempts, and the symptoms often involve charger behavior and session stability.

• Scan tool DC-charge related modules or data may drop out intermittently during a charging attempt, or U130F resets quickly after clearing when you retry DC charging
• DC charging fail the EVSE refuses to start charging after plug-in and authentication steps
• Session stops charging begins, then stops unexpectedly within minutes
• Reduced rate the session runs but at an unusually low DC charging power level
• Charge warnings charging system warning messages appear during DC plug-in or shortly after start
• Multiple DTCs additional charging or network-related codes may set alongside U130F
• Repeatable by location the complaint occurs consistently at one charger or one connector style but not others

Common Causes

• Charging-session handshake timeout: The PCM sets U130F when the DC charger and vehicle fail to complete the required communication steps in time.
• Dirty, wet, or damaged DC charge inlet pins: Contamination changes contact resistance and signal quality, which disrupts EVSE-to-vehicle communication.
• Loose or backed-out charge inlet connector terminals: Poor terminal tension creates intermittent opens that look like a “no signal” or erratic link to the PCM.
• Harness damage between the charge inlet and PCM: Chafing or pinched wiring can create an open, short-to-ground, or short-to-battery on communication-related circuits.
• Low 12V system voltage during charging attempt: The PCM and related gateway logic can drop offline or reset, which breaks the EVSE communication session.
• High-resistance PCM power or ground connection: Corrosion at grounds or power feeds can pass a static check but fail under load, causing module resets and lost communication.
• Related network DTCs affecting coordination: A CAN communication fault or module offline condition can block the PCM from completing the DC charging negotiation.
• EVSE equipment or connector fault: A station-side communication or connector issue can prevent successful message exchange, leading the PCM to log U130F.
• PCM software logic issue or internal fault: After you prove power, ground, network integrity, and inlet wiring, the PCM can still fail to process the EVSE communication correctly.

Diagnosis Steps

You need a scan tool that can access Hyundai EV/charging data and run a full network scan. Use a quality DVOM, a test light, and back-probing tools. Have contact cleaner and basic terminal tools ready. If you suspect a CAN issue, use a breakout or access point for bus testing. Plan to perform voltage-drop tests under load.

1. Confirm U130F and record DTC status as pending or confirmed. Save freeze frame data and note ignition state, vehicle speed, and any related network or charging DTCs. Freeze frame shows conditions when the code set. Use a scan tool snapshot later to capture live data during a repeated charge attempt.
2. Run a full network scan and verify the PCM appears online. If the scan tool cannot communicate with the PCM, shift focus to module power, ground, and network integrity before charging diagnosis. Check for other U-codes that identify additional modules dropping off the network.
3. Check fuses and power distribution that feed the charging control and network circuits. Inspect the fuse blades and the fuse box terminals for heat damage. Do this before probing the PCM connector. A cracked fuse element can pass continuity and still fail under load.
4. Verify PCM power and ground with voltage-drop testing under load. Command a related function if the scan tool allows it, or perform the test during an attempted charging session. Keep ground drop below 0.1V with the circuit operating. Do not rely on ohms checks or unloaded voltage alone.
5. Inspect the DC charge inlet area closely before meter work. Look for bent pins, discoloration, moisture tracks, or signs of overheating. Confirm the inlet locks correctly and the connector seats fully. Any physical defect can interrupt the EVSE communication sequence.
6. Check the inlet and PCM connectors for terminal fit and corrosion. Perform a light tug test on suspect wires and inspect for backed-out terminals. Verify connector seals and water intrusion paths. Repair terminal issues before chasing network theory.
7. Use the scan tool to monitor charging-related data PIDs during a plug-in attempt. Watch for state changes such as “EVSE detected,” “DC request,” “communication status,” and any flags that indicate a handshake step failed. Compare behavior with a known-good station if available to separate vehicle faults from EVSE faults.
8. If the issue appears intermittent, reproduce it and capture a scan tool snapshot during the failure. A snapshot helps when freeze frame lacks detail or the fault sets after the initial plug-in. Correlate the moment of dropout with 12V voltage, module resets, or network errors.
9. Check for wiring faults between the charge inlet and PCM using targeted circuit tests. Perform continuity checks only after you isolate the circuit and follow service information for pin identification. Then load-test the suspect circuits with a test light or resistor load to find high resistance. An “open circuit” often shows up only with load applied.
10. If you suspect a CAN-related contributor from the network scan, test the CAN bus correctly. With ignition OFF and the battery disconnected, measure resistance between CAN+ and CAN- at an accessible connector and expect about 60 ohms on a healthy bus. With ignition ON, check bias voltage and expect about 2.5V on CAN+ and CAN- to ground. Take voltage readings with ignition ON because bias voltage does not exist with the circuit asleep.
11. Clear codes and verify the repair with a controlled DC charging attempt. Confirm the PCM completes the communication steps and U130F does not return as pending. Re-scan all modules after the test to ensure no secondary U-codes remain. If U130F returns immediately on key-on, treat it as a hard fault and re-check power, ground, and connector integrity.

Professional tip: Treat the FTB suffix as a diagnostic direction, not a part verdict. If your scan report shows a “no signal” style subtype, prioritize opens, terminal fit, and module resets. If it points toward short-to-ground or short-to-battery, isolate the harness and inspect for chafe points near the inlet and along body pass-throughs. Verify every fix with a repeatable plug-in test and a post-repair network scan.

Possible Fixes

• Clean and dry the DC charge inlet and correct any pin fitment issues found during inspection.
• Repair or replace damaged terminals, seals, or connector bodies at the charge inlet or PCM, then confirm proper terminal tension.
• Repair harness damage between the inlet and PCM, including chafed insulation, pinched sections, or water-intrusion corrosion.
• Restore 12V power integrity by correcting poor fuse box connections, failing power feeds, or high-resistance grounds verified by voltage-drop testing.
• Resolve related network faults first, including CAN open/short conditions, before condemning charging components.
• Update PCM software or replace the PCM only after you prove correct power, ground, and communication circuit integrity and the fault repeats with known-good EVSE equipment.

Can I Still Drive With U130F?

You can usually drive a Hyundai IONIQ 5 with U130F set, because this code targets DC fast-charging communication, not basic propulsion control. Treat it as a charging-system fault first. The practical risk shows up when you need DC fast charging and the car refuses to start or maintain a session. Avoid depending on a public DC charger until you diagnose it. If the warning indicators stack up with other network or high-voltage related codes, stop and diagnose before further trips. A communication fault can hide a power, ground, or connector issue. That kind of root cause can also create other intermittent module problems.

How Serious Is This Code?

U130F ranges from an inconvenience to a trip-ending charging problem. If the only complaint involves DC fast charging, the issue mainly affects charging access and time. Severity increases if the PCM (Powerline Communication Module) drops communication repeatedly during a charge attempt. Repeated failures can strand the vehicle away from AC charging options. Treat the code as more serious if you also see multiple U-codes, low-voltage battery warnings, or modules that reset. Those clues point to a network integrity or power supply problem. Fix those first because they can affect many systems beyond charging.

Common Misdiagnoses

Technicians often blame the charging station and stop testing too early. A bad EVSE does happen, but U130F can set from the vehicle side. Another common mistake involves replacing the charge inlet, charge port door parts, or the PCM without proving the circuit. Corrosion in the inlet area and terminal drag can create brief dropouts that look like “EVSE communication loss.” Shops also miss low-voltage power faults. A weak 12-volt battery, loose grounds, or a high-resistance fuse feed can destabilize network modules under load. Avoid wasted spending by confirming power, ground, and connector integrity before any module decision.

Most Likely Fix

The most frequent confirmed repair direction involves correcting a physical connection problem that interrupts DC EVSE communication. Start with the charge inlet and its connectors for moisture, corrosion, heat damage, or pin fit issues. Next, verify stable power and ground to the PCM (Powerline Communication Module) under load, not just with a key-on voltage check. If wiring and terminals test good and the fault repeats with known-good charging equipment, update software or reprogramming becomes the next logical step on Hyundai platforms. Only after those checks should you consider module replacement, followed by required setup steps.

Repair Costs

Network and communication fault repairs vary by root cause — wiring/connectors are often the source, but module-level repairs or replacements can be significantly more expensive.