Case Studies 09

CASE STUDY: 09
Designing a Simple CAN Bus Diagnostic Tester Using LT Spice

  1. Introduction

    Modern vehicles rely heavily on CAN (Controller Area Network) communication for ECU-to-ECU data exchange. While professional scan tools and oscilloscopes are invaluable, there is still a strong need for simple, quick, and non-intrusive diagnostic tools that can be used directly at the vehicle harness.

    This case study documents the complete journey of designing and validating a passive CAN Bus activity tester using LTspice, starting from a conceptual idea inspired by DIY circuits found online, and ending with a working, simulated design that is safe for real-world automotive use.

    Problem Statement

    During routine diagnostics, the following quick checks are often required:

    • Is CAN communication present or dead?

    • Are CANH and CANL switching correctly?

    • Is there real differential activity on the bus?

    • Can this be checked without loading the bus or using expensive equipment?

    Many simple CAN tester circuits exist on social media, but:

    • Their correctness is often questionable

    • Component values are rarely justified

    • Bus-loading risks are not considered

    Objective:
    Design a safe, high-impedance CAN diagnostic tester with visual indication, and validate it through simulation before hardware fabrication.

    Design Goals

    The tester should:

    1. Detect CANH activity

    2. Detect CANL activity

    3. Detect true differential bus activity

    4. Draw negligible current from the CAN bus

    5. Work without a microcontroller or CAN transceiver

    6. Be simple enough for DIY fabrication

    Conceptual Approach

    CAN Voltage Basics (Automotive High-Speed CAN)

    StateCANHCANL
    Recessive (Idle)~2.5 V~2.5 V
    Dominant~3.5 V~1.5 V

    Key insight:

    True CAN activity exists only when CANH and CANL move in opposite directions simultaneously.

    This formed the basis for a differential activity detector using passive components.

    Circuit Architecture

    The design consists of three sensing paths:

    1️⃣ CANH Indicator Path

    • CANH → 220kΩ → LED → GND

    • LED lights when CANH rises above idle

    2️⃣ CANL Indicator Path

    • CANL → 220kΩ → LED → GND

    • LED lights when CANL falls below idle

    3️⃣ Differential Activity Path (Key Feature)

    • CANH → 470kΩ → diode → 470kΩ → CANL

    • LED conducts only when voltage difference exists

    This third path ensures:

    • No response during idle

    • Response only during dominant bits

    • Clear visual indication of bus activity

    Why High-Value Resistors?

    ResistorPurpose
    220kΩLED current limiting
    470kΩDifferential sensing with minimal loading

    Total bus loading is in microamp range, making the tool safe even on sensitive networks.

    LTspice Simulation Setup

    Voltage Sources (CAN Emulation)

     
    V1 CANH 0 PULSE(2.5 3.5 2m 1u 1u 2m 8m) V2 CANL 0 PULSE(2.5 1.5 2m 1u 1u 2m 8m)

    This accurately emulates:

    • CAN idle

    • Dominant bit transitions

    • Repetitive data frames

    Diode Model Used

     
    .model DLED D(Is=1n N=2 Vfwd=1.8)

    This represents a typical LED behavior and ensures simulation accuracy.

    Transient Analysis Command

     
    .tran 0 50m 0 100n

    • 50 ms window → multiple CAN frames visible

    • 100 ns max step → clean square edges

    Simulation Results

    Observed Waveforms

    • CANH (Green): Pulses between 2.5 V and 3.5 V

    • CANL (Blue): Pulses between 2.5 V and 1.5 V

    • Differential Node (Red): Active only during dominant bits

    ✔ Idle state correctly shows no differential activity
    ✔ Dominant bits produce clear differential pulses

    Key Validation Outcome

    The differential LED responds only when CANH ≠ CANL.

    This confirms:

    • The circuit detects real bus activity

    • No false triggering during idle

    • The design logic is electrically sound

    Practical Diagnostic Use Cases

    This tester can immediately reveal:

    • Dead CAN bus

    • One wire missing (CANH or CANL)

    • Short to ground / short to battery

    • Partial communication activity

    • Intermittent bus faults

    All without a scan tool or oscilloscope.

    Lessons Learned

    1. Never trust social media circuits blindly

    2. Simulation prevents real-world damage

    3. High-impedance design is critical for CAN

    4. Differential logic can be implemented passively

    5. LTspice is an excellent validation tool for automotive diagnostics

    Conclusion

    This project successfully demonstrates how a simple, passive CAN diagnostic tester can be designed, simulated, and validated using first principles.

    The final circuit is:

    • Safe

    • Simple

    • Effective

    • DIY-friendly

    • Suitable for real automotive diagnostics

    This approach bridges the gap between theory, simulation, and practical workshop tools.

Translate »