Vehicle simulator

The complete vehicle in software, top to bottom. Every ECU answers diagnostic requests the way the real one does, from the same vehicle definitions, so diagnostic software can be developed and tested without a vehicle.

  • Simulates the whole vehicle, every ECU in it, not a single unit.
  • Built from the vehicle definitions: each ECU's identification, data streams, trouble codes and actuator tests.
  • For development, automated testing and training.

Standards

  • ISO 22901-1 ODX
  • ISO 14229 UDS
  • ISO 15765 CAN, CAN FD
  • ISO 13400-2 DoIP

Reference hardware

The simulator is licensed as software. It runs on off-the-shelf hardware that you buy from any distributor:

  • Raspberry Pi 5 (4 GB), with the official 27 W power supply and active cooler.
  • Waveshare 2-CH CAN FD HAT for CAN and CAN FD.
  • The Raspberry Pi's own Ethernet port for DoIP.
  • A J1962 (OBD-II) female socket, wired to CAN on pins 6 and 14 and to Ethernet for DoIP.
  • A 12 V supply on pin 16, so a diagnostic tool powers up as it does in a car.

Raspberry Pi is a trademark of Raspberry Pi Ltd.

Questions about Vehicle Simulator: contact@vehiqlabs.com

Where Vehicle Simulator fits

Your diagnostic application

MCD

MCD-3D server to ISO 22900-3. Loads the vehicle's ODX data and runs its diagnostic services.

D-PDU API

The standard interface to ISO 22900-2 between diagnostic software and the VCI.

Vehicle communication interface (VCI)

Embedded

A lightweight diagnostic runtime with vehicle definitions. It runs in the vehicle, on a phone, anywhere.

CAN, CAN FD and DoIP

The vehicle and its ECUs

Vehicle Simulator

A complete vehicle in software. Every ECU answers as the real one does.