OBD Simulator Software to simulate and re-play a vehicle.
Contents OBD Simulator... 1 Software to simulate and re-play a vehicle... 1 Introduction... 3 Configuration... 4 Vector Hardware... 4 Start Simulator... 5 Defining an ECU... 6 ECU Definitions... 8 Static ECU Definitions... 8 Replay ECU definitions... 8
Introduction The Simulator is created as a tool to help with the development of the OBD software CAN Data Miner, but can be used for other tools as well. It is not complete and may have some limitations. Currently it s only supporting ISO 15765. To use this you will need a CAN interface and drivers from Vector. https://www.vector.com/vi_index_en.html In addition to this you will need to build some hardware on your own to interface between the OBD device and the CAN connector on the CAN interface.
Configuration Vector Hardware The Vector Hardware needs to be configured to support the application. The first time the application is started a configuration window will be displayed for the CAN hardware. Link the application ObdCanSimulator channels to the correct CAN interface. You can also use the Virtual CAN bus provided the application that you want to test using this simulator supports it. In that case you don t need any hardware.
Start Simulator When the simulator is first started it will look like the following: You can select the Vector CanCase/CanCard option and click Open to connect to the CAN bus. If all goes well the result shall be as follows: The following parameters can be adjusted: Frame Spacing Time between each frame sent on the CAN bus by the simulator. Adjusting this will change the latency of the simulator. Block Size The expected block size to report in a Flow Control message. Wait Time The expected wait time between frames to report in a Flow Control message. The Block Size and Wait Time parameters shall impact the peer to this application.
Defining an ECU Initially the simulator doesn t simulate any ECU at all; each ECU needs to be configured. This is done in the upper right part. Start with selecting the Functional Address, where two alternatives exists; 0x07DF and 0x18DB33F1. The first is for 11-bit addressing and the second is for 29-bit addressing. The next step is to select the physical ECU address. Initially it is the first from a default list depending on the Functional Address. If you don t have any specific need you can use the default. The third step is to select the Data Model. Here you can select either Static or Replay. The Static model will always return the same value for a specific Mode/PID combination while the Replay model allows you to replay raw data captured by the Can Data Miner application. When you click on the Add ECU button you will get a dialog where you can select the data model source. The Data Values tab allows control over the data and responses by the simulated ECU. For a static model the options are limited to the check boxes; Pad Data The data sent on CAN is padded to full CAN frame length with zeroes. Send Error Code at Invalid Mode/Service If a request for a mode/service is done an error response shall be sent (General Reject) if this is checked. If not checked the request is ignored and no response is sent. Send Error Code at invalid PID/Address If an invalid PID was requested an error response is sent. If not checked the request is ignored an no response is sent.
At the Communication tab a log of the most recent traffic can be seen: The Dir column contains information about the data direction and roughly OSI layer involved. This can be useful when trying to debug protocol deficiencies. The colors are following the value in the Dir column. The Clear Log button clears the communication log, which is useful when trying to analyze certain problems and not being disturbed by irrelevant data. The Remove Tab will remove the ECU tab.
ECU Definitions The Static models are text files while the Replay models are binary files. Static ECU Definitions The static files can be created using Excel, and then save them as MS-DOS text files (fields shall be separated by TAB character). The following columns shall exist: Mode: This shall contain the mode or modes (services) concerning the data separated by a comma. EchoPid: 1 = The PID shall be echoed in responses, 0 = The PID shall not be echoed in responses. The latter is the case for SSM data. PID: The PID value or data address accessed. (Address for SSM). A, B, C : The data fields, one byte per column. For Modes, PIDs and the available values please see SAE J1979-DA. (http://standards.sae.org/j1979da_201110/) Replay ECU definitions The Replay files are created by doing raw logging in CAN Data Miner. Only the modes/pids selected for logging are inserted into the log file. This means that if you want something complete you need to create a log file and check everything and take a run with your car first.