Fuel Delivery

Gold ChapterATLAS-FUELDELI-0117Template 2.2

P0562

System Voltage Low

P0562 — System Voltage Low — covers Vehicle Electrical and Charging System.\n\nThe controller evaluates module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation. The control module determines that system supply voltage…

SeverityHigh
DriveabilityA low-voltage condition can cause stalling, no-start, module resets, false DTCs, transmission/throttle faults, and loss of electrical functions. Diagnose promptly and avoid driving if charging voltage is unstable or the battery warning is active.
Diagnostic Time1.0-3.0 hours
Typical Cost$100-$3,000+ depending on proven cause and vehicle
Atlas StatusGold Chapter
Reviewed2026-08

Diagnostic Snapshot

Most Common Cause: weak/discharged battery or poor battery connectionEngine Damage Risk: Varies by root cause. Low-voltage, cooling-fan, severe fuel/throttle, timing, lubrication, or exhaust restriction faults can create significant secondary risk; manufacturer-specific P1xxx risk must be judged from the exact OEM definition and symptoms.Safe to Drive: A low-voltage condition can cause stalling, no-start, module resets, false DTCs, transmission/throttle faults, and loss of electrical functions. Diagnose promptly and avoid driving if charging voltage is unstable or the battery warning is active.Professional Scan Tool: Strongly recommended; manufacturer-enhanced data and OEM definitions are essential for P1xxx and materially improve all rows in this packMechanical Test Recommended: Yes — use an independent physical test whenever scan/electrical data indicates a real fan, EGR, throttle, exhaust-pressure, charging, fuel, airflow, or other system-response problemDIY Difficulty: Advanced DIY / Professional preferred

Atlas Academy

Learn the System

Before diagnosing this code, it helps to understand the system behind it.

Read Understanding Fuel Delivery Systems

Technical Summary

P0562 — System Voltage Low — belongs to Vehicle Electrical and Charging System. The control module determines that system supply voltage remains below its calibrated operating expectation after the required enable conditions are satisfied.

The controller evaluates module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation. The diagnostic goal is to identify the exact failed layer: system voltage/power, signal/control circuit, sensor or actuator, prerequisite data, mechanical response, or controller.

First move: test battery state and charging-system output under load, then voltage-drop the module power and ground paths while reviewing freeze-frame voltage and companion undervoltage DTCs.

Freeze-frame and companion DTCs are critical because undervoltage, fail-safe operation, temperature, load, and manufacturer-specific enabling logic can radically change the diagnostic direction.

Do not invent universal voltage, current, resistance, duty-cycle, pressure, or correlation values. OEM service information takes priority, and for P1xxx codes the OEM definition itself is mandatory.

Driveability: A low-voltage condition can cause stalling, no-start, module resets, false DTCs, transmission/throttle faults, and loss of electrical functions. Diagnose promptly and avoid driving if charging voltage is unstable or the battery warning is active.

What You'll Learn

  • Correct handling of P0562
  • Exact standardized or manufacturer-specific status
  • Monitor/enabling logic
  • Ranked causes
  • Freeze-frame clues
  • Live-data patterns
  • Loaded circuit tests
  • Physical verification
  • Repair confirmation

Think Like a Technician

Treat P0562 as a monitor statement, not a parts request. Start by proving the correct definition—especially for P1xxx—then reproduce the failure. Separate electrical capability, data plausibility, and physical response. Require a second independent form of evidence before replacing an expensive component or module.

What This Code Means

P0562 is listed as System Voltage Low.

The control module determines that system supply voltage remains below its calibrated operating expectation after the required enable conditions are satisfied.

The controller monitors module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation.

The DTC identifies a failed monitored relationship, not an automatically failed component.

System Overview

Vehicle Electrical and Charging System diagnosis compares controller command/input with loaded electrical behavior, related scan data, and physical system response. For manufacturer-specific P1xxx codes, the OEM definition is part of the diagnostic test itself because the same numeric code can represent different monitored systems on different vehicles.

Why This Code Sets

The P0562 monitor becomes eligible after VIN-specific voltage, key/engine state, temperature, load, plausibility, and system prerequisites are satisfied. It evaluates module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation. The DTC stores when the monitored relationship remains outside the calibrated expectation for the required duration/sample count. Exact limits are application-specific.

Common Symptoms

  • Check Engine Light
  • Driveability or electrical change possible
  • Reduced power or emissions impact possible
  • Intermittent operation possible
  • System-specific warning may appear

Most Likely Causes

  • 1. weak/discharged battery or poor battery connection
  • 2. generator/alternator output or control fault
  • 3. high resistance in battery cables, grounds, fuse links, or module feeds
  • 4. excessive electrical load or parasitic/charging-system problem
  • 5. belt/tensioner or mechanical generator-drive issue where applicable
  • 6. module voltage-sense or controller fault after charging system proof

Common Vehicles

This standardized OBD-II DTC is used on applications that implement the relevant monitor. Component architecture and exact diagnostic procedure vary; confirm support and layout by VIN.

Freeze Frame Clues

  • Battery/system voltage
  • Engine RPM
  • Vehicle speed
  • Calculated load
  • Coolant temperature
  • Commanded and actual component state
  • Related sensor/actuator feedback
  • Charging voltage/current where relevant
  • Companion DTCs
  • Fail-safe or monitor state

Live Data Expectations

Graph module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation with RPM, load, system voltage, temperature, and related independent/redundant data. Reproduce freeze-frame and look for the first command, signal, supply, correlation, or physical response that stops agreeing with the expected state. VIN-specific normal values take priority.

Typical Verification Tests

  • Confirm P0562 absent current/pending
  • Repeat original freeze-frame condition
  • Load-test repaired circuit
  • Graph related signals/commands for stable agreement
  • Use bidirectional/OEM functional test where supported
  • Verify physical system response
  • Complete required reset/relearn/programming
  • Verify normal driveability and readiness

Before You Condemn

  • Confirm exact VIN-specific DTC definition
  • Save full scan/freeze-frame
  • Verify battery/charging/module voltage
  • Inspect wiring/connectors/terminal tension
  • Check shared powers/grounds/references
  • Graph related data
  • Perform loaded/dynamic circuit testing
  • Verify physical system response
  • Check bulletins/software/calibration
  • Repeat enable condition after repair

Before Replacing Parts

Confirm System Voltage Low, preserve full scan/freeze-frame, and test battery state and charging-system output under load, then voltage-drop the module power and ground paths while reviewing freeze-frame voltage and companion undervoltage DTCs. Prove system voltage, powers/grounds, shared circuits, component assignment, and physical response before replacement.

Diagnostic Workflow

  1. Confirm P0562; save current, pending, history, freeze-frame, readiness status, and the complete module scan before clearing anything.
  2. Verify the exact definition — System Voltage Low — against VIN-specific service information; this step is mandatory for manufacturer-specific P1xxx codes.
  3. Review OEM wiring, connector views, component location, enabling criteria, monitor logic, bulletins, calibration notes, and functional tests for Vehicle Electrical and Charging System.
  4. Verify battery condition, charging voltage, module powers/grounds, ignition feeds, and shared fuse/relay/reference circuits under load.
  5. Perform the first targeted check: test battery state and charging-system output under load, then voltage-drop the module power and ground paths while reviewing freeze-frame voltage and companion undervoltage DTCs.
  6. Inspect connectors and harnesses for corrosion, moisture, heat damage, chafing, pin push-out, terminal spread, poor routing, and recent repair disturbance.
  7. Graph the monitored relationship: module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation.
  8. Reproduce freeze-frame safely and note key/engine state, RPM/load, temperature, speed, command state, voltage, and any heat/vibration dependence.
  9. Test the affected power, ground, signal, control, relay, solenoid, motor, or reference circuit dynamically using loaded voltage drop, current, waveform, or approved test load as appropriate.
  10. Compare scan feedback with an independent or redundant measurement so a biased sensor or incorrect module interpretation is not mistaken for a physical failure.
  11. Use bidirectional controls or OEM functional tests where supported and safe; compare commanded state with electrical feedback and actual component/system response.
  12. Check shared/prerequisite systems because one voltage, reference, ground, network, airflow, fuel, exhaust, or mechanical fault can create multiple codes.
  13. For intermittent faults, manipulate the harness and reproduce temperature/vibration/load while graphing or scoping the circuit; static continuity can miss the failure.
  14. Before condemning the PCM/ECM/TCM or another module, prove stable powers/grounds, terminal tension, external loads, circuit capability, network integrity, and current software/calibration.
  15. Repair only the wiring, connector, sensor, actuator, mechanical, charging, calibration, or controller fault supported by documented testing.
  16. Complete required resets/relearns, repeat the original monitor enable condition, and verify P0562 remains absent current and pending with normal system operation.

Labor & Inspection Checklist

  • Full scan/freeze-frame saved
  • VIN-specific DTC definition confirmed
  • Wiring diagram reviewed
  • Battery/module voltage verified
  • Connectors/harness inspected
  • Shared circuits checked
  • Live-data graph captured
  • Loaded electrical/physical test completed
  • Relearn/service procedure completed
  • Pending-code/readiness verification completed

Common Repairs

  • Repair proven wiring/connector fault
  • Repair shared power/ground/reference/relay circuit
  • Replace sensor/actuator/module only after testing proves failure
  • Correct proven mechanical/charging/system fault
  • Perform required reset/relearn/programming
  • Replace control module only after external proof

Common Parts

  • Connector/terminal repair materials
  • Harness repair materials
  • System-specific sensor/actuator/relay/module when proven faulty
  • Battery/charging components where applicable
  • PCM/ECM only after external proof

Shop Notes

P0562 diagnostic boundary: System Voltage Low. The control module determines that system supply voltage remains below its calibrated operating expectation after the required enable conditions are satisfied.

Monitor focus: module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation. Preserve freeze-frame before clearing because the original enable condition determines the correct test direction.

Best first move: test battery state and charging-system output under load, then voltage-drop the module power and ground paths while reviewing freeze-frame voltage and companion undervoltage DTCs.

Loaded-circuit rule: continuity alone does not prove a power, ground, motor, solenoid, relay, or actuator circuit can carry current. Use loaded voltage drop/current testing where appropriate.

Reality-check rule: compare module data with physical operation or an independent measurement. A plausible PID is not proof that the component actually moved, the charging system actually supplied current, or the mechanical system responded.

Shared-circuit rule: identify common references, grounds, fuses, relays, splices, network messages, and power stages before replacing multiple components.

Intermittent rule: heat, vibration, and system voltage can expose terminal resistance and internal faults that disappear during static bay testing.

Controller rule: module replacement is last. Prove external loads, powers/grounds, circuit capability, terminal fit, network health, and calibration/software first.

Verification rule: after repair, recreate the original enable state and confirm P0562 stays absent pending while the monitored relationship remains valid.

Driveability/safety: A low-voltage condition can cause stalling, no-start, module resets, false DTCs, transmission/throttle faults, and loss of electrical functions. Diagnose promptly and avoid driving if charging voltage is unstable or the battery warning is active.

P0562 advanced diagnostic note 1: Evaluate module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation under the original operating condition. Use a second form of evidence—loaded electrical testing, redundant scan data, physical movement, charging output, pressure/flow, or OEM functional test—before replacing hardware. Exact thresholds and component assignments must come from VIN-specific service information.

P0562 advanced diagnostic note 2: Evaluate module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation under the original operating condition. Use a second form of evidence—loaded electrical testing, redundant scan data, physical movement, charging output, pressure/flow, or OEM functional test—before replacing hardware. Exact thresholds and component assignments must come from VIN-specific service information.

P0562 advanced diagnostic note 3: Evaluate module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation under the original operating condition. Use a second form of evidence—loaded electrical testing, redundant scan data, physical movement, charging output, pressure/flow, or OEM functional test—before replacing hardware. Exact thresholds and component assignments must come from VIN-specific service information.

P0562 advanced diagnostic note 4: Evaluate module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation under the original operating condition. Use a second form of evidence—loaded electrical testing, redundant scan data, physical movement, charging output, pressure/flow, or OEM functional test—before replacing hardware. Exact thresholds and component assignments must come from VIN-specific service information.

P0562 advanced diagnostic note 5: Evaluate module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation under the original operating condition. Use a second form of evidence—loaded electrical testing, redundant scan data, physical movement, charging output, pressure/flow, or OEM functional test—before replacing hardware. Exact thresholds and component assignments must come from VIN-specific service information.

P0562 advanced diagnostic note 6: Evaluate module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation under the original operating condition. Use a second form of evidence—loaded electrical testing, redundant scan data, physical movement, charging output, pressure/flow, or OEM functional test—before replacing hardware. Exact thresholds and component assignments must come from VIN-specific service information.

P0562 advanced diagnostic note 7: Evaluate module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation under the original operating condition. Use a second form of evidence—loaded electrical testing, redundant scan data, physical movement, charging output, pressure/flow, or OEM functional test—before replacing hardware. Exact thresholds and component assignments must come from VIN-specific service information.

P0562 advanced diagnostic note 8: Evaluate module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation under the original operating condition. Use a second form of evidence—loaded electrical testing, redundant scan data, physical movement, charging output, pressure/flow, or OEM functional test—before replacing hardware. Exact thresholds and component assignments must come from VIN-specific service information.

P0562 advanced diagnostic note 9: Evaluate module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation under the original operating condition. Use a second form of evidence—loaded electrical testing, redundant scan data, physical movement, charging output, pressure/flow, or OEM functional test—before replacing hardware. Exact thresholds and component assignments must come from VIN-specific service information.

P0562 advanced diagnostic note 10: Evaluate module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation under the original operating condition. Use a second form of evidence—loaded electrical testing, redundant scan data, physical movement, charging output, pressure/flow, or OEM functional test—before replacing hardware. Exact thresholds and component assignments must come from VIN-specific service information.

P0562 advanced diagnostic note 11: Evaluate module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation under the original operating condition. Use a second form of evidence—loaded electrical testing, redundant scan data, physical movement, charging output, pressure/flow, or OEM functional test—before replacing hardware. Exact thresholds and component assignments must come from VIN-specific service information.

P0562 advanced diagnostic note 12: Evaluate module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation under the original operating condition. Use a second form of evidence—loaded electrical testing, redundant scan data, physical movement, charging output, pressure/flow, or OEM functional test—before replacing hardware. Exact thresholds and component assignments must come from VIN-specific service information.

P0562 advanced diagnostic note 13: Evaluate module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation under the original operating condition. Use a second form of evidence—loaded electrical testing, redundant scan data, physical movement, charging output, pressure/flow, or OEM functional test—before replacing hardware. Exact thresholds and component assignments must come from VIN-specific service information.

Technician Notes

Exact title used: System Voltage Low.\n\nFault interpretation: the control module determines that system supply voltage remains below its calibrated operating expectation after the required enable conditions are satisfied.\n\nMonitor focus: module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation.\n\nFirst move: test battery state and charging-system output under load, then voltage-drop the module power and ground paths while reviewing freeze-frame voltage and companion undervoltage DTCs.\n\nUse VIN-specific component assignments, circuit design, thresholds, and relearn procedures.

Mechanic's Tip

For P0562, follow definition → enable conditions → input/command → loaded circuit → feedback → physical response. With P1xxx codes, never skip the VIN-specific definition step.

Common Mistakes

  • Using a P1xxx definition from the wrong manufacturer
  • Replacing the named part from the code alone
  • Ignoring freeze-frame and companion DTCs
  • Using universal electrical specifications
  • Relying on continuity instead of loaded testing
  • Skipping physical verification
  • Condemning control module before external proof

Tools Used During Diagnosis

  • Manufacturer-enhanced graphing scan tool
  • Digital multimeter
  • Oscilloscope/current clamp where appropriate
  • Backprobe/terminal tools
  • Battery/charging tester
  • VIN-specific OEM service information
  • Bidirectional controls
  • System-specific mechanical test equipment

Manufacturer Notes

The base DTC title is standardized, but component architecture, enabling criteria, thresholds, fail-safe behavior, and test procedures vary by manufacturer. Confirm VIN-specific service information.

Customer Explanation

Your vehicle stored P0562: System Voltage Low. The computer found a specific problem in the vehicle electrical and charging system system. The code does not automatically mean the named part needs replacement; the circuit and actual system response must be tested.

Frequently Asked Questions

What does P0562 mean?

P0562 is System Voltage Low. The standardized definition identifies the monitored circuit or relationship, but exact component design, thresholds, and enable logic still vary by vehicle.

Does P0562 automatically mean the named component is bad?

No. The code identifies a failed monitor. Wiring, powers/grounds, shared circuits, prerequisite sensors, mechanical response, software, and controller faults can produce the same DTC.

Can I drive with P0562?

A low-voltage condition can cause stalling, no-start, module resets, false DTCs, transmission/throttle faults, and loss of electrical functions. Diagnose promptly and avoid driving if charging voltage is unstable or the battery warning is active.

What should be checked first?

Test battery state and charging-system output under load, then voltage-drop the module power and ground paths while reviewing freeze-frame voltage and companion undervoltage dtcs.

Why is freeze-frame important?

It captures voltage, temperature, RPM, load, speed, command state, and companion data when the monitor failed. That helps reproduce intermittent, heat-, load-, or voltage-dependent faults.

What live data is most useful?

Graph module supply voltage, battery voltage, generator command/output, charging current/load, ignition feeds, module grounds, and voltage stability during cranking and operation with RPM, load, battery voltage, temperature, and relevant companion PIDs. Look for the first electrical, data, or physical relationship that stops agreeing with the expected operating state.

Can low voltage cause multiple unrelated-looking codes?

Yes. Low system voltage can reset modules, distort sensor references, reduce actuator authority, and interrupt communication. P0562 in particular should be resolved before diagnosing many secondary electrical DTCs.

Should I use universal voltage, current, or resistance values?

No. Exact limits, circuit architecture, and enable criteria vary. VIN-specific service information is mandatory for P1xxx codes and still takes priority for standardized P0/P2 codes.

When is professional equipment justified?

A manufacturer-enhanced graphing scan tool is strongly recommended. Bidirectional controls, oscilloscope/current testing, battery/charging analysis, and OEM service information may be required.

How is the repair verified?

Repeat the original enable condition, verify the monitored circuit and physical response are stable, complete required relearns/service procedures, and confirm P0562 remains absent current and pending.

Related Atlas Resources

Continue with Atlas electrical, charging, EGR, throttle/pedal, exhaust-pressure, fuel-delivery, and manufacturer-specific diagnostic chapters.

Diagnostic Confidence

High when the exact VIN-specific monitor is identified and the failure is reproduced with independent electrical/data/physical evidence; Medium when intermittent or manufacturer documentation is incomplete

Related Codes

Project Atlas Feedback

Was this article helpful?

Needs Improvement
Save Up to 80% on Automotive Parts

Working on this repair?

Create a professional estimate in minutes.

Email it to your customerTrack labor and partsConvert it into an invoiceKeep a complete repair history
Start Free PistonCMS Account

Project Atlas

Chapter Status

Editorial StatusAtlas Certified
Last Reviewed2026-08
Template Version2.2
Related Academy GuideUnderstanding Fuel Delivery Systems

Why Trust This Guide?

Updated regularlyWritten for working techniciansPractical diagnostic processBuilt for mobile mechanics and independent shopsMaintained by PistonCMS

Built by mechanics. Improved by mechanics.

This guide is maintained for working mechanics, mobile technicians, fleet maintenance professionals, and independent repair shops.