DIAG GOLD← CAN Bus Playbook
Tesla Network Map
Tesla uses a proprietary architecture combining an Ethernet backbone with CAN segments. Early Roadster (2008-2012) used more conventional CAN architecture, derived from the Lotus Elise platform. Model S/X and Model 3/Y use an Ethernet backbone with CAN sub-buses for powertrain, chassis, and body systems. Tesla does not publish traditional service information to independents; network details are largely reverse-engineered. The OBD-II DLC is present but provides limited access; meaningful diagnostics require Tesla Toolbox software with authentication.
Testing values and scope patterns are universal — they live on the main CAN playbook. This page is what's specific to Tesla: the buses, where the terminators live, and what breaks. Tap any era to explore it — network map, testing guide, failure patterns.
2008-2012
Roadster (Lotus-based platform)
Conventional automotive network architecture; Tesla does not publish OEM service information for this platform
| Bus | Speed | Carries | DLC access | Terminators live in |
|---|---|---|---|---|
| CAN bus (factory name unconfirmed) | — | Powertrain, battery management, charging · Roadster architecture derived from Lotus Elise platform with Tesla electric drivetrain integration; limited public documentation available | — | not independently confirmed |
Explore this era ⤢
2012-present
Model S/X and Model 3/Y (Ethernet backbone with CAN segments)
Ethernet backbone connects the central compute/media unit, Autopilot computer (if equipped), and gateway. Model 3/Y represent further integration with fewer discrete controllers. OBD-II DLC provides limited CAN access; advanced diagnostics require Tesla Toolbox or authorized tools.
| Bus | Speed | Carries | DLC access | Terminators live in |
|---|---|---|---|---|
| CAN bus (factory name unconfirmed) | — | Powertrain: drive inverter(s), battery management system, DC-DC converter, on-board charger · High-speed bus for critical drivetrain components | — | not independently confirmed |
| CAN bus (factory name unconfirmed) | — | Chassis: ABS/ESC, steering, suspension (where equipped) · Safety-critical chassis functions | — | not independently confirmed |
| CAN bus (factory name unconfirmed) | — | Body: door modules, seat modules, HVAC, body control · Lower-priority comfort and convenience functions | — | not independently confirmed |
GatewayCentral gateway module; connects Ethernet backbone to CAN segments
Explore this era ⤢What breaks on Teslas
MCU eMMC flash failure (older Model S/X)
Media Control Unit eMMC flash memory wears out from excessive logging, causing touchscreen failure, loss of backup camera, and gateway communication issues. Recall and coverage issued by Tesla; affected units upgraded to MCU2.
Gateway/central module failure causing network loss
Gateway or central compute module failure can cause complete loss of communication between subsystems, often manifesting as inability to charge or drive. Requires module replacement and Tesla authentication.
12V battery depletion causing cascading network faults
Tesla's 12V system is atypical (charged from the HV battery via DC-DC converter). A weak or failing 12V battery causes intermittent CAN communication faults, module brownouts, phantom faults, and cascading network errors, often misdiagnosed as network faults when the root cause is the 12V battery.
Aftermarket OBD-II / accessory devices causing faults
Third-party OBD-II dongles (insurance trackers, data loggers) and CAN-attached accessories can prevent proper sleep, drain the 12V battery, and cause communication faults or charging issues due to Tesla's aggressive power management and network security.
The bench — what to test with
Quality DVOM (Fluke 87V or similar) with a real manual 200-ohm range$40 basic meter genuinely does the resistance/voltage jobs; ~$300+ for a Fluke if you want reliable low-ohm accuracy and durability
Terminator resistance, CAN bias voltage, split-half short hunting, and the critical 12V-under-load check are all done with a good meter — most Tesla 'network' complaints resolve here without a scope.
12V load tester appropriate to the battery chemistry$30-150 (match method to lead-acid vs Li-ion 12V)
The 12V is the single most common root cause of phantom Tesla network faults, and rested voltage alone won't reveal a battery that collapses under load.
2-channel automotive scope (Pico 2204A / Hantek)~$150-1000; a cheap 2-channel unit is plenty for CAN work
The only way to see edge quality, reflections from bad termination, and intermittent framing during a wiggle test — the meter tells you a bus is broken, the scope tells you HOW.
Breakout box / module T-harness set$50-300 depending on connector coverage
Because Tesla's sub-buses hide behind the gateway and aren't at the DLC, tapping at the module is the only way to put a scope or meter on them without piercing wire.
CAN sniffer / logger (e.g., a CANtact-class interface or handheld)$20-150 for a basic USB CAN interface
Shows exactly which node IDs are present so you can tell 'one module gone' from 'a group gone past a break' — the single most useful topology-diagnosis view on any CAN segment.
Backprobe pin set and quality test leads$15-40
Every CAN measurement here depends on clean backprobing without piercing insulation; bad contact fakes opens and shorts that send you chasing ghosts.
Tesla Toolbox subscription + authorized interfaceSubscription-based; the only path to authenticated full-system access
The honest truth: body, chassis, coding, and Ethernet diagnostics on modern Tesla are gated behind VIN-specific authentication — no meter or generic scanner reaches them, so meaningful factory-level work requires this.
Scan-tool access
Tesla does not provide traditional factory scan tools or service information to independents. There is NO standard OBD-II port on Model 3/Y (EVs are exempt from the OBD-II mandate, which is an emissions rule) - the diagnostic connector hides behind the center console and needs a Tesla-specific adapter harness; Model S/X use their own connectors by era. Even with an adapter, standard protocols expose limited data: meaningful diagnostics require Tesla Toolbox with VIN-specific authentication. Third-party tools (with the right adapter) can read a useful subset.
Don't agree?
Send us your feedback — we're always looking to get better: [email protected]