# Log OBD2 Mode 1 OBD2 generally focuses on emission control and supports a broad range of standard parameter IDs (PIDs) that can be logged across most vehicles. ### 'How to' - with ReXgen? The OBD data can be easily logged using any ReXgen logger from Influx with the ReXdesk software. ### Periodic CAN/CAN FD Transmission Create a new project.
Drag and drop the 'Periodic Transmission' tool to the 'Output' area of the configuration window.
If you have not configured the same in the logging area, click the CAN bus icons and set the CAN bus properties.
To initiate OBDII Mode1 data logging, users must configure periodic transmission with OBD requests to the ECU.
* **Ident**: specifies if the identifier is for "request messages" or "response messages." * **ID 7DF** - OBD2 message identifier for a standard 11-bit. **Note:** In some cases, the user will need to use physical rather than functional addressing. * **ID 7E8** - main engine or ECU response identifier. * \***Linked**: lets you link the message(s). * \***Period**: Specify the Period of transmission. * \***Delay**: Specify the delay in transmission. * **CAN 0/CAN 1/CAN 2/CAN 3**: Option to choose the transmission bus. * **Type**: CAN message (Standard/Extended). * **DLC**: Data Length Code (0-64). (\* - define only if/when needed) * **Data**: * **Request data message** –
* **Response data message** –
**Length:** Specifies the length of bytes (after it) containing valid data. For example, in the request message
'02' specifies that the Engine or ECU must respond to the mode 01 and PID 0A codes in the next two bytes. Similarly, for the response message
'04' specifies that the Engine or ECU response lies in the next four bytes, mode '01' request is replaced with '41' for responses and the PID code 0A's data is in the next four bytes '23 E6' (hex values). **Mode:** specifies the diagnostic services described in the latest OBD-II standard SAE J1979 (this document is made explicitly for Mode 1). **PID:** these are the standard OBD-II PIDs as defined by SAE J1979. * 0A - Fuel pressure * 05 - Engine coolant temperature * 0C - Engine speed * 0D - Vehicle speed #### Decoding data values for the PIDs: For example, if the output data looks like this
Then,
Similarly, all the hex data values need to be decoded according to their respective PID formulas ([Click for detailed list](https://en.wikipedia.org/wiki/OBD-II_PIDs)) \*For Heavier vehicles that use extended 29-bit CAN identifiers with bit rates 250K or 500K, the OBDII PID identifier is 18DB33F1 instead of 7DF. Also, the response ID is 18DAF1XX, where 'XX' varies according to various OEMs, as it is up to them to determine what CAN ID they assign for ECUs. ## Decode data using DBC: This method exports only specific messages/signals from the RAW data using a DBC file. The user will need to assign the DBC to the specific CAN Bus. Click on the 'Internal Storage.'
The window below will open.
Select the data logs and click on Download;
Select the 'Advanced' option and open the 'Export data' window below. Choose the output format (.mf4/.mat/.csv). Choose the time format (Only applicable to .csv format). The user can choose the 'Merge' option if multiple data logs are to be exported. Specify the output location to save the exported data. Click 'Process'.
Click on the 'load DBC file' icon.
Drag and drop the required DBC messages/signals to the corresponding bus.
{% hint style="info" %} #### Note: * ReXdesk supports PGN-based exports when J1939 DBC is imported. {% endhint %} Click 'Process'. ReXdesk will process the RAW data and save the decoded data to the location specified during step 3. #### Sample dbc file {% file src="" %} #### Sample csv file {% file src="" %} [Video Tutorial](https://youtu.be/8XSEYJRXnGQ)