User Guide ECUsim™ 2000 Multiprotocol Software Configurable OBD-II ECU Simulator
Information contained in this document is subject to change without notice. Trademarks are property of their respective owners. Copyright © 2013 OBD Solutions. All rights reserved. Printed in the United States of America.
Table of Contents 1.0 Overview ................................................................................................................ 4 1.1 General Features .................................................................................................. 5 1.2 Package Contents................................................................................................ 5 2.0 User Interface .......................................................................................................
1.0 Overview ECUsim 2000 is a small, lightweight, entry level benchtop simulator that can be used for testing and development of OBD hardware and software. It supports all legislated OBD protocols, fixed and user adjustable parameter IDs (PIDs), diagnostic trouble codes (DTCs), freeze frames, VIN, and many other SAE J1979 services. The unit has five knobs assigned to common PIDs, a “fault event” button, and indicator lights for power, connection, and MIL (Malfunction Indicator Light).
1.
2.0 User Interface ECUsim 2000 can be used as a stand alone simulator, or in conjunction with a PC. It features a number of interface elements, shown in the diagram in the next section. 2.
1. 2. 3. 4. 5. 6. 7. 8. 9. Power LED Link LED The function of this LED depends on the protocol in use: a. ISO 9141-2 and ISO 14230-4 protocols: the LED is on while at least one ECU is initialized. The LED dims when an OBD message is received. b. J1850 and CAN protocols: the LED blinks when an OBD message is received. Malfunction Indicator Light Knobs assigned to the five commonly used Mode 1 PIDs. Fault button When pressed, the following happens: a. Set MIL and number of stored DTCs (Mode 1, PID 01) b.
3.0 Basic Operation ECUsim 2000 comes with protocols unlocked according to the selection you’ve made when placing the order, and is ready to be used out of the box. 3.1 Setup To set up the simulator, follow these steps: 1. 2. 3. 4. Use the configuration DIP switch to set the desired options. Plug the power supply into an available electric outlet. Plug the 12 volt end of the power supply into the power jack of the simulator. Connect the OBD connector of your OBD tester or OBD interface to the DLC. 3.
4.0 UART Communication ECUsim 2000 features a USB connection. On a Windows or Linux PC, the drivers create a virtual COM port which allows communication using any suitable serial port terminal (e.g., HyperTerminal). 4.1 Installing USB Drivers To communicate with the ECUsim 2000, make sure it is powered on, and connect it to any available USB port. If the operating system does not find & install the drivers automatically, you can download them from FTDI’s website. FTDI Virtual Com Port Drivers http://www.
5.0 Software Configuration On startup or reset, the PIM prints the welcome banner that looks similar to this: STS2000 v3.1.5 (C) 2013 OBD Solutions > The PIM is now ready to accept user commands. 5.1 Supported Commands For a list of supported commands, see the ECUsim Programming Manual that can be found on the ECUsim 2000 product page, at: http://ecusim.com/2000 6.0 Advanced Operation This section describes the operation of the simulator in different protocol modes.
6.2 ISO 14230-4 (Fast Init) After switching to the ISO 14230-4 protocol with fast init option, the simulator will print the following status message: It will not respond to any requests until the bus is initialized. After a successful initialization sequence, the simulator will print: At this point, the virtual ECUs will start responding to OBD requests.
messages have either 11-bit or 29-bit headers. So a typical 11-bit exchange would appear as follows: Rx: Tx: Tx: Tx: 7DF 7E8 7E9 7EA 01 41 41 41 00 00 BE 1B 30 13 00 88 18 00 10 00 00 08 00 10 Same exchange on 29-bit CAN: Rx: Tx: Tx: Tx: 18DB33F1 18DAF110 18DAF118 18DAF128 01 41 41 41 00 00 BE 1B 30 13 00 88 18 00 10 00 00 08 00 10 Monitoring can be turned off using the MON 0 command to increase the refresh rate. To enable monitoring again, issue MON 1. 6.
7.0 Virtual ECUs There are three virtual ECUs: Engine Control Module (ECM), Transmission Control Module (TCM), and Anti-lock Braking System module (ABS). The ECUs support both physical and functional addressing, as specified in the SAE J2178, Part 1 and ISO 15765-4 documents.
7.1 Engine Control Module (ECM) The following summarizes modes, PIDs, and Infotypes supported by the PCM. 7.1.
21 2F 33 40 42 46 Distance Traveled While MIL is Activated Fuel Level Input Barometric Pressure Supported PIDs 41-5F Control Module Voltage Ambient Air Temperature fixed 03E8 1000 km fixed fixed 80 64 50.2% 100 kPa fixed 44000000 fixed 2EE0 12 V fixed 3C 20°C 7.1.1.
7.1.2 ECM: Mode 2 When the user generates a malfunction event, the following freeze frame is stored: PID Description Hex Value 00 02 05 0C 0D Supported PIDs 01-1F DTC that Caused F.F. Storage Engine Coolant Temperature Engine RPM Vehicle Speed Sensor 48180000 0100 8C 4E20 78 7.1.3 Scan Tool Display P0100 100°C 5000 rpm 120 km/h ECM: Mode 3 When the MIL is on, Mode 3 reports six DTCs: 7.1.
7.1.5 ECM: Mode 7 When the MIL is on, Mode 7 reports four pending DTCs: 7.1.6 P0107 P0207 P0307 C0307 ECM: Mode 9 The following infotypes are supported: Infotype 00 01 02 03 04 05 06 0A Description Supported Infotypes VIN Message Count* VIN Calibration ID message count* Calibration ID CVN Message Count* CVN ECUNAME Scan Tool Display 1G1JC5444R7252367 JMB*36761500 1791BC82 ECU1-EngineControl *Message count infotypes are not supported in ISO 15765-4, per SAE J1979. 7.1.
7.2 Transmission Control Module (TCM) The following summarizes modes, PIDs, and Infotypes supported by the TCM. 7.2.1 TCM: Mode 1 PID Description Fixed/Variable Hex Value 00 Supported PIDs 01-1F Monitors/DTC Count/MIL Engine Coolant Temperature Engine RPM fixed 88180010 fixed* 00000000 variable, knob #1 00 to FF All monitors not supported -40°C to +215°C variable, knob #2 Vehicle Speed Sensor OBD Type variable, knob #3 0000 to FFFF 00 to FF 0.00 to 16383.
7.2.4 TCM: Mode 7 When MIL is on, Mode 7 reports two DTCs: P0102 U1600 7.3 ABS Control Module (ABS) The following summarizes modes, PIDs, and Infotypes supported by the ABS. 7.3.1 ABS: Mode 1 PID Description Fixed/Variable Hex Value 00 Supported PIDs 01-1F Vehicle Speed Sensor OBD Type fixed 00080010 variable, knob #3 00 to FF 0 to 255 km/h fixed 01 OBD-II (CARB) 0D 1C 7.3.2 Scan Tool Display ABS: Mode 4 Issuing Mode 4 request performs the following operations on the ABS: 7.
8.0 Firmware Updates The simulator features a bootloader, which allows the user to update the device’s firmware in the field through the USB port. Updates are posted on the ECUsim internet product page as they become available. Once you download the update, follow the steps to update the simulator: 1. 2. 3. 4. Extract the contents of the ZIP file to a folder on your computer. Run StnFirmwareUpdater.exe. Select the COM port associated with the ECUsim.
Appendix A: Specifications Dimensions Weight Power OBD Protocols PC Port Operating Temperature Operating Humidity Storage Temperature Storage Humidity 5.0 x 3.0 x 1.12 in (127 x 76.2 x 28.4 mm) 2.5 oz (70.
