Integrate safe-work decisions, scan evidence, electrical testing and cross-system reasoning to prove Hybrid/EV root causes and verify repairs.
Safety boundary: Diagnostic reasoning course—not authorization for high-voltage service. Do not open HV circuits, defeat interlocks, probe unapproved points or improvise isolation. Follow current OEM procedures, specified equipment, PPE, waiting periods and qualification requirements.
A Hybrid/EV diagnosis begins by reproducing the complaint, identifying the vehicle operating state and deciding whether the next test stays in an ordinary low-voltage/data domain or crosses an HV-qualified-work boundary.
Foundation: identify the evidence category. Technician: compare command, permission and response. Deep: correlate cross-system evidence and defend root cause.
Identify HEV/PHEV/BEV architecture and the relevant energy path before choosing data. The same symptom can originate in battery permission, conversion, motor torque, thermal control, charging or low-voltage support.
Foundation: identify the evidence category. Technician: compare command, permission and response. Deep: correlate cross-system evidence and defend root cause.
Use network health, DTCs, freeze-frame and live data to see which controllers agree about the event. A code identifies a monitoring result or circuit concern; it does not automatically name the failed part.
Foundation: identify the evidence category. Technician: compare command, permission and response. Deep: correlate cross-system evidence and defend root cause.
Separate what the driver requested, what supervisory control permitted, what a component was commanded to do and what the vehicle actually did. These four layers prevent expensive guesswork.
Foundation: identify the evidence category. Technician: compare command, permission and response. Deep: correlate cross-system evidence and defend root cause.
Voltage drop, power/ground integrity, connector condition, reference circuits and communication faults can imitate high-cost Hybrid/EV component failures. Use the correct approved test method for the circuit domain.
Foundation: identify the evidence category. Technician: compare command, permission and response. Deep: correlate cross-system evidence and defend root cause.
Battery, inverter, motor, thermal, brake/regen, charging and 12-V systems interact. Correlate evidence across systems instead of stopping at the first abnormal value.
Foundation: identify the evidence category. Technician: compare command, permission and response. Deep: correlate cross-system evidence and defend root cause.
Repeat the original condition, confirm relevant DTC/data behavior, verify normal permissions and response, document before/after evidence and confirm no new safety or calibration requirement remains.
Foundation: identify the evidence category. Technician: compare command, permission and response. Deep: correlate cross-system evidence and defend root cause.
Define the exact symptom, conditions, READY/charge/drive state and whether the concern is repeatable.
Determine the work boundary before touching the vehicle; follow current OEM isolation, PPE and verification procedures when HV work is required.
Check module communication, DTC status, freeze-frame and event context before clearing evidence.
Compare SOC/SOH context, temperatures, isolation/precharge/contactor status and charge/discharge power permission.
Compare inverter/motor commands, rotor/phase evidence, torque request and actual propulsion or regeneration response.
Correlate cooling, temperature, charge permission, DC–DC support and thermal derates with the complaint.
Confirm 12-V support, powers, grounds, connectors and communication integrity before condemning expensive HV assemblies.
State symptom → evidence → failed function/root cause → repair → comparable-condition verification.
Select a normalized teaching state. Values are conceptual evidence indices, not OEM specifications or safe test thresholds.
Normal: permission, controls, conversion and vehicle response agree.
Multiple modules show low-voltage history; HV isolation data is normal, but control modules reset during the event.
Best evidence branch: Low-voltage power/ground support. Prove stable 12-V supply and module power integrity before condemning the traction battery or inverter.
SOC is adequate; pack temperature is high and BMS discharge-power permission falls while motor/inverter response follows the allowed limit.
Best evidence branch: Battery/thermal permission branch. The motor is responding to a reduced allowed-power envelope; find why battery capability is limited.
Battery permission and DC bus are available; torque is commanded, but rotor/phase/conversion evidence is abnormal and actual drive torque does not follow.
Best evidence branch: Motor/inverter/conversion branch. Use OEM-directed tests to separate position feedback, phase path and inverter control without invasive HV shortcuts.
Several controllers lose communication together while HV component temperatures and battery values remain plausible. A shared low-voltage/network disturbance aligns with the event.
Best evidence branch: Network/power-distribution branch. Correlated multi-module loss points away from replacing multiple HV components independently.
Recognizes HV boundaries, selects current service information and stops/escalates appropriately.
Reproduces and defines the exact operating state without changing evidence prematurely.
Chooses relevant DTC, freeze-frame, live-data and electrical evidence rather than parts guessing.
Uses approved, least-invasive tests and interprets command, permission and actual response correctly.
Correlates battery, conversion, thermal, network and low-voltage evidence into a defensible failed-function statement.
Repeats comparable conditions and records before/after proof, safety checks and required follow-up.