Diagnostic Resources / Diagnostic guide

EV NETWORK ARCHITECTURE.

Follow battery, propulsion, charging and thermal messages across CAN FD, Ethernet, DoIP and LIN.

EV GUIDE19/24
⚠ TRAINING BOUNDARY

Use this guide to organize evidence. Vehicle-specific high-voltage access, measurements and component isolation require OEM procedures, appropriate qualifications, rated PPE and approved test equipment.

GUIDE PURPOSE

Diagnose the system—not one isolated value.

Confirm vehicle state, operating conditions and the full DTC record before clearing evidence or opening the high-voltage system.

01 / HOW IT WORKS

Theory and operation

A scan tool may reach an ECU through DoIP even when that ECU exchanges operating data on CAN FD; local pumps and valves commonly sit on LIN branches.

02 / WHAT TO CAPTURE

Diagnostic evidence

Save a complete topology scan, gateway routing status, bus-off counts, wake-up states and missing-module pattern before disconnecting anything.

03 / TEST STRATEGY

Safe diagnostic path

Identify the failed domain versus one local branch and test gateway power/routing before blaming every module that appears offline.

04 / STOP CONDITION

Boundary and common error

Do not apply 60-ohm CAN expectations to Ethernet, LIN, isolated battery daisy chains or point-to-point sensor links.

OEM DATA SETS THE LIMIT

Specifications, connector access, disable sequences, wait times and allowable tests vary by model and voltage architecture.

NEXT EV GUIDE / DIAGNOSTIC-RESOURCESEV Scan-Data Reference→