Loading... Please wait...
)
Arduino-Compatible OBD-II CAN-Bus ECU Simulator with Teensy 3.2
Product Description
Free Shipping Within the United States!
The OBD-II CAN-Bus ECU simulator uses the Arduino-compatible Teensy 3.2 module (included). It helps test the OBDII interface and write diagnostic software. ECU PIDs parameters are adjustable via menu options.
Hardware Features
- Teensy 3.2 module (installed)
- Teensy pre-programmed with ECU simulator firmware
- 250 or 500 kb/s CAN speed
- Open source firmware
- Large 2.8" Color TFT screen (320 x 240 pixels).
- Female OBDII socket with 12 VDC supply voltage to interface
- Menu navigation wheel.
- 12 VDC external PSU (included - UK 3pin mains plug)
- Micro SD card socket
- Lasercut acrylic baseplate
- Firmware Features
- SAE standard J1979. PIDs partially implemented. Mode 01, 02, 03
- Adjustable PID parameters via menu options:
- Engine RPM
- Throttle position
- Vehicle speed
- Coolant temperature
- MAF airflow sensor
- O2 sensor voltages
- Setting and clearing Diagnostic Trouble Codes (DTC)
- Open source firmware, other PIDs can be added
Documents
Automotive Diagnostic Systems: Understanding OBD-I & OBD-II
For more than 30 years, cars and trucks have carried onboard diagnostics (OBD), which monitor and adjust major systems, including engine, drivetrain, fuel, and more. Many think that repairing or tuning the current system (OBD- II) is a black art or a computer science, and that there is no way to diagnose and fix computer control-system problems at home with affordable tools. But, that is simply not true.
OBD expert, tuner, and author Keith McCord explains system architecture, function, and operation. He shows you how to use a hand-held scanner, connect it to the port connector in the car, and interpret the data. But most importantly, he shows you a practical, analytical, and methodical process for tackling a problem, so you can quickly trace its actual source and fix the root cause and not just the symptom. Automotive Diagnostic Systems includes definitions of diagnostic trouble codes and a table of common DTCs.
McCord reveals the intricacies of diagnosing the system, the importance of fixing component DTCs first, one- and two-trip codes, how the PCM erases DTCs, and how you can have DTCs stored in memory with no MIL on, among many other common issues. As a result, you learn how to resolve a range of common OBD-II problems, such as engine misfires, shorts and opens, out-of-tune fuel trims, dead catalysts, emissions leaks, low voltages, failed oxygen sensors, and much more. But it also covers fuel injectors, ignition systems, chassis sensors, and various other sensors and actuators.
