U058A
Invalid Data Received From DC/AC Converter Control Module B
Causes
- Corrupted or malformed CAN/serial messages from DC/AC Converter Control Module B
- Power supply or ground fault at the converter control module
- Damaged wiring, poor connector contact, or water intrusion on harness to module B
- Bus termination, wiring short or high electrical noise on CAN/communication lines
- Software mismatch, firmware bug, or incomplete module reflash
- Intermittent module fault or internal controller failure
Symptoms
- Malfunction Indicator Lamp (MIL) or warning message related to inverter/drive system
- Reduced drive power, limp-home mode, or limited vehicle performance
- Inability to charge, start electric drive, or unpredictable inverter behavior
- Erratic or missing status data from converter B on a scan tool
- Multiple communication-related U-codes present
What to check
- Read and record all stored DTCs and freeze-frame data with a capable scan tool
- Check for other module faults (powertrain, gateway, battery management) that may affect communications
- Verify ability to communicate with Converter Control Module B using a scanner (explicit data and diagnostic responses)
- Visually inspect connectors, seals and wiring for damage, corrosion, pin push-out or water intrusion
- Measure module supply voltage and ground integrity at the module connector (with key/off and key-on as required)
- Monitor CAN/communication bus activity and idle voltages with a multimeter; use an oscilloscope to confirm message waveforms and termination
Signal parameters
- CAN message ID(s) from Converter Control Module B and expected frequency (e.g., periodic status messages 5–100 Hz depending on signal)
- Expected CAN bus recessive and dominant voltages (approx. 2.5 V idle per node, differential ~0 V/2.5 V depending on system) — verify per vehicle spec
- Typical module supply voltage range (e.g., 9–16 V on vehicle 12 V systems) and stable ground
- Common status/data fields: converter output current, output voltage, temperature, state-of-charge/status bits — values must be within manufacturer ranges
- Checksum/CRC or message counter fields — must increment/validate per protocol
- Message timing intervals and timestamp consistency (no long gaps or jitter beyond spec)
Diagnostic algorithm
- Connect a diagnostic scan tool, read all active/pending/historic DTCs and capture freeze-frame and event data.
- Check for related communication DTCs (gateway, BMS, inverter A) and note sequence/timing of code set events.
- Attempt live-data communication with Converter Control Module B. Note which parameters are invalid, out-of-range, blank, or flagged with parity/checksum errors.
- Visually inspect module connector and wiring harness for damage, corrosion, bent pins or moisture. Repair any physical defects and re-check.
- With vehicle powered as required and HV systems disabled per manufacturer procedure, verify module supply voltage and ground at the connector. Repair poor power/ground and retest.
- Check CAN bus physical layer: measure bus voltages, check for proper termination resistance (~60 ohms total) and look for short to battery/ground using insulated test methods. Use an oscilloscope to view message waveforms and confirm correct message IDs and timing.
- If bus messages are present but data fields are invalid, capture raw CAN frames and compare message contents to expected format (byte layout, counters, CRC).
- Review software/firmware calibration versions for Converter Control Module B and related modules. Reflash or update per manufacturer instructions if a mismatch or known bug exists.
- After repairs or updates, clear codes and perform a road/functional test to verify the fault does not return and that live-data values remain valid.
- If wiring, power and software are confirmed good and the module still sends invalid data, consider replacement of Converter Control Module B and re-test. Follow manufacturer procedure for module programming and initialization.
- Caution: follow all high-voltage safety procedures if accessing HV inverter/converter components; only qualified technicians should perform HV work.
Likely causes
- Loose or corroded connector pins at Converter Control Module B
- Low or intermittent module supply voltage or ground
- CAN bus wiring damage or missing termination resistor
- Module firmware mismatch after a software update or replacement
- Internal controller malfunction in the DC/AC converter module
Fault status
Similar codes
Brands with available manuals
The library contains 7,723 repair and diagnostic manuals. Choose a brand to open the full manual tree by year, model and trim.
U058A
Invalid Data Received From DC to AC Converter Control Module “B”
Causes
- Corrupted or malformed CAN/serial messages from DC/AC Converter Control Module B
- Power supply or ground fault at the converter control module
- Damaged wiring, poor connector contact, or water intrusion on harness to module B
- Bus termination, wiring short or high electrical noise on CAN/communication lines
- Software mismatch, firmware bug, or incomplete module reflash
- Intermittent module fault or internal controller failure
Symptoms
- Malfunction Indicator Lamp (MIL) or warning message related to inverter/drive system
- Reduced drive power, limp-home mode, or limited vehicle performance
- Inability to charge, start electric drive, or unpredictable inverter behavior
- Erratic or missing status data from converter B on a scan tool
- Multiple communication-related U-codes present
What to check
- Read and record all stored DTCs and freeze-frame data with a capable scan tool
- Check for other module faults (powertrain, gateway, battery management) that may affect communications
- Verify ability to communicate with Converter Control Module B using a scanner (explicit data and diagnostic responses)
- Visually inspect connectors, seals and wiring for damage, corrosion, pin push-out or water intrusion
- Measure module supply voltage and ground integrity at the module connector (with key/off and key-on as required)
- Monitor CAN/communication bus activity and idle voltages with a multimeter; use an oscilloscope to confirm message waveforms and termination
Signal parameters
- CAN message ID(s) from Converter Control Module B and expected frequency (e.g., periodic status messages 5–100 Hz depending on signal)
- Expected CAN bus recessive and dominant voltages (approx. 2.5 V idle per node, differential ~0 V/2.5 V depending on system) — verify per vehicle spec
- Typical module supply voltage range (e.g., 9–16 V on vehicle 12 V systems) and stable ground
- Common status/data fields: converter output current, output voltage, temperature, state-of-charge/status bits — values must be within manufacturer ranges
- Checksum/CRC or message counter fields — must increment/validate per protocol
- Message timing intervals and timestamp consistency (no long gaps or jitter beyond spec)
Diagnostic algorithm
- Connect a diagnostic scan tool, read all active/pending/historic DTCs and capture freeze-frame and event data.
- Check for related communication DTCs (gateway, BMS, inverter A) and note sequence/timing of code set events.
- Attempt live-data communication with Converter Control Module B. Note which parameters are invalid, out-of-range, blank, or flagged with parity/checksum errors.
- Visually inspect module connector and wiring harness for damage, corrosion, bent pins or moisture. Repair any physical defects and re-check.
- With vehicle powered as required and HV systems disabled per manufacturer procedure, verify module supply voltage and ground at the connector. Repair poor power/ground and retest.
- Check CAN bus physical layer: measure bus voltages, check for proper termination resistance (~60 ohms total) and look for short to battery/ground using insulated test methods. Use an oscilloscope to view message waveforms and confirm correct message IDs and timing.
- If bus messages are present but data fields are invalid, capture raw CAN frames and compare message contents to expected format (byte layout, counters, CRC).
- Review software/firmware calibration versions for Converter Control Module B and related modules. Reflash or update per manufacturer instructions if a mismatch or known bug exists.
- After repairs or updates, clear codes and perform a road/functional test to verify the fault does not return and that live-data values remain valid.
- If wiring, power and software are confirmed good and the module still sends invalid data, consider replacement of Converter Control Module B and re-test. Follow manufacturer procedure for module programming and initialization.
- Caution: follow all high-voltage safety procedures if accessing HV inverter/converter components; only qualified technicians should perform HV work.
Likely causes
- Loose or corroded connector pins at Converter Control Module B
- Low or intermittent module supply voltage or ground
- CAN bus wiring damage or missing termination resistor
- Module firmware mismatch after a software update or replacement
- Internal controller malfunction in the DC/AC converter module
Fault status
Similar codes
Manual library for HYUNDAI
Browse 371 HYUNDAI manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.
HYUNDAI
-
HYUNDAI: 2023
-
Elantra
-
Elantra N
-
Kona N
-
Tucson
- Hybrid Blue
- Hybrid Limited
- Hybrid SEL Convenience
- Limited, Eng CD G4EN, 4WD
- Limited, Eng CD G4EN, FWD
- Limited, Eng CD G4KN, 4WD
- Limited, Eng CD G4KN, FWD
- N Line, Eng CD G4EN, 4WD
- N Line, Eng CD G4EN, FWD
- N Line, Eng CD G4KN, 4WD
- N Line, Eng CD G4KN, FWD
- Plug-In Hybrid Limited
- Plug-In Hybrid SEL
- SE, Eng CD G4EN, 4WD
- SE, Eng CD G4EN, FWD
- SE, Eng CD G4KN, 4WD
- SE, Eng CD G4KN, FWD
- SEL, Eng CD G4EN, 4WD
- SEL, Eng CD G4EN, FWD
- SEL, Eng CD G4KN, 4WD
- SEL, Eng CD G4KN, FWD
- XRT, Eng CD G4EN, 4WD
- XRT, Eng CD G4EN, FWD
- XRT, Eng CD G4KN, 4WD
- XRT, Eng CD G4KN, FWD
-
-
HYUNDAI: 2022
-
Elantra N
-
Kona N
-
Veloster N
-
HYUNDAI: 2021
-
Veloster N
-
HYUNDAI: 2020
-
Palisade
-
Veloster N
