Looking to record OBD2 data from your vehicle?
This guide provides an overview of OBD2 logging, highlighting the key benefits and practical applications. You can also access sample OBD2 data (speed, RPM, etc.) collected from an Audi A4.
Unlike many OBD2 dongles and scanners, the CANedge empowers you to log and process your car’s data on your terms. It comes with 100% free software and APIs, including browser-based dashboards:
Discover why the CANedge is ideally suited for CAN and OBD2 data logging and telematics applications.
Quick Tip: Watch our 4-minute introductory video to get started!
Article Contents
products contact us
Understanding OBD2 Data Logging
Let’s quickly recap the fundamentals of OBD2 systems.
OBD2 provides a standardized set of parameters (OBD2 PIDs) that can be easily recorded and decoded across a wide range of vehicles.
Logging OBD2 data involves these three straightforward steps:
- Configure your OBD2 logger: Specify the OBD2 PIDs you want to record.
- Connect to your car: Use an OBD2 adapter to connect the logger to your vehicle’s OBD2 port and begin logging.
- Extract and decode data: Retrieve the SD card from the logger and use free OBD2 data logging software and APIs to decode the recorded data.
For more detailed instructions, refer to the FAQ section below or our comprehensive documentation:
CLX000 OBD2 guide CANedge OBD2 guide
Top 4 Advantages of OBD2 Data Logging
OBD2 data logging offers a versatile way to gather insights from virtually any car. Here are four key benefits:
1. Driver, Vehicle, and Part Optimization
OBD2 data enables you to monitor and refine driving habits, optimize vehicle performance, and even fine-tune your car. For Original Equipment Manufacturers (OEMs), this data is invaluable for assessing the real-world performance of prototype components under various driving conditions.
2. Diagnostics for Intermittent Issues
Some car problems occur sporadically while driving, making them difficult to diagnose during routine servicing. OBD2 data logging allows you to capture data around the time of an event, providing crucial insights for troubleshooting elusive problems that don’t present themselves in the workshop.
3. Enhanced Car Fleet Management
Implementing OBD2 WiFi telematics across a vehicle fleet unlocks numerous advantages. These include in-depth driver behavior analysis, optimizing fuel consumption to reduce costs, minimizing breakdowns through proactive maintenance, ensuring regulatory compliance, streamlining dispute resolution, and facilitating predictive maintenance strategies.
4. Data Control and Tailored Integration
Using an OBD2 WiFi logger gives you complete control over your raw time-series data. You can extract data via SD card or automatically upload it to your own server. This open approach allows for seamless custom integration using open APIs and ensures your data is accessible and manageable according to your specific needs.
Considering which of these benefits aligns with your OBD2 data logging objectives? We’re here to help with free consultation!
Contact us
Introducing the CANedge OBD2 Data Logger
The CANedge CAN bus data logger offers optional GPS/IMU, WiFi, and 3G/4G connectivity, making it an excellent choice for OBD2 fleet telematics and advanced data logging applications.
PLUG & PLAY
Ready to log data right out of the box. Operates standalone and seamlessly connects your vehicle data to your server infrastructure.
PRO SPECS
Features extractable 8-32 GB SD card, dual CAN/LIN channels, CAN FD support, zero data loss recording, 50 µs RTC, error frame detection, and MF4 logging format.
COMPACT
Small form factor at just 8 x 5 x 2 CM, robust aluminum enclosure, 100G shock resistance, and configurable 5V power output.
WIFI/LTE
Effortlessly push data via WiFi or 3G/4G to your designated server. Enhanced with end-to-end security and Over-The-Air (OTA) updates.
GNSS + 3D IMU
Integrated GPS/IMU for precise location and motion data. Achieves 3x accuracy through sensor fusion, capturing position, speed, distance, and more.
INTEROPERABLE
Leverage free and open-source software/APIs. Supports MF4 to ASC/CSV conversion, DBC integration, Python libraries, and browser-based dashboards.
learn more
Free OBD2 Data Logging Software Example: Custom Dashboards
The CANedge simplifies the creation of free, customized browser dashboards for visualizing your OBD2 data and setting up real-time alerts. This powerful feature is part of our commitment to providing accessible Obd2 Data Logging Software Free of charge.
For applications requiring location data, you can seamlessly integrate GPS/IMU data by using a CANedge equipped with GNSS/IMU.
Explore the capabilities with our online playground or delve deeper with our dashboard introduction.
playground dashboards intro
Download the ‘OBD2 Data Pack’
Eager to start working with real OBD2 data?
Download our comprehensive ‘data pack’, which includes:
- Our OBD2 DBC file
- 25+ car DBC files (reverse engineered)
- 100+ MB of data from 10+ vehicles
download now
OBD2 Data Logging Use Case Examples
Here are practical examples of how the CANedge can be effectively used for logging OBD2 data in various scenarios.
OEM Vehicle Part Field Testing
Need to efficiently log CAN/OBD2 field data from vehicles in real-world conditions?
For OEMs conducting late-stage field tests of prototype equipment, collecting OBD2 and CAN data from multiple vehicles over extended periods (e.g., months) is crucial. The CANedge1 is ideally suited for this purpose due to its compact size, plug-and-play simplicity, and ease of pre-configuration. Data can be collected periodically and seamlessly analyzed using industry-standard CAN tools or our free asammdf GUI/API.
canedge1
Vehicle Telematics (OBD2 + GNSS/IMU + 3G/4G)
Looking to establish OBD2 telematics solutions for on-road vehicle fleets?
The CANedge3 excels in this area, capable of uploading recorded OBD2 data via 3G/4G using your own SIM card. This enables near real-time wireless OBD2 data transfer from vehicles to your private cloud server. The OBD2 data can be automatically processed using our open APIs, which include OBD2 DBC decoding support. CANedge3 devices also support over-the-air updates for streamlined management. Furthermore, the integrated GPS/IMU in the CANedge3 adds valuable data streams such as position, speed, trip distance, acceleration, and attitude to your telematics data.
canedge3
Case Study: OBD2/CAN Telematics Implementation
Discover how Volkswagen utilizes the CANedge2 to log both OBD2 and raw CAN data to an SD card, and automatically push this data to their self-hosted server for in-depth analysis.
“The CANedge2 allowed us to get up and running quickly with flexible configuration options, and the support was exceptional!“
learn more 100+ case studies
Accessing OBD2 Data from an Audi A4
Below, you can download sample OBD2 data collected using the CANedge from an Audi A4.
We also encourage you to download our free obd2 data logging software and explore the process of decoding raw OBD2 data yourself.
Raw OBD2 Decoded OBD2 Software
Frequently Asked Questions (FAQ)
The OBD2 protocol (SAE J1979) defines a range of standardized vehicle data parameters that you can log. However, the specific OBD2 data supported varies between car models, with older vehicles often supporting fewer parameters.
Here are some common standard OBD2 parameters that are frequently available:
-
Fuel system status
-
Engine load
-
Coolant temperature
-
Fuel trim
-
Fuel pressure
-
Intake manifold pressure
-
Engine RPM
-
Vehicle speed
-
Intake air temperature
-
MAF air flow rate
-
Throttle position
-
Air status
-
Oxygen sensor status
-
Runtime since engine start
-
Distance with MIL on
-
Fuel tank level input
-
System vapor pressure
-
Absolute load value
-
Hybrid battery pack life
-
Engine oil temperature
-
Engine fuel rate
-
Torque
-
VIN
-
Various DTCs
For more detailed information, consult the OBD2 PID Wiki page or the SAE J1979 standard.
To convert raw OBD2 data from a CANedge OBD2 data logger into meaningful physical values (km/h, rpm, etc.), you need a database of decoding rules and suitable OBD2 software.
We provide a 100% free OBD2 DBC file for this purpose. It encompasses the majority of standardized Mode 01 (Service 01) OBD2 PID decoding rules, as documented on resources like the OBD2 PID Wiki page.
The OBD2 DBC file utilizes extended multiplexing for efficient OBD2 decoding. To learn more, refer to our DBC intro and our OBD2 intro, where we explain how to interpret raw CAN frames with OBD2 responses.
You can load your raw OBD2 data and the OBD2 DBC file into our free obd2 data logging software tools, such as asammdf or our OBD2 dashboard integrations. This allows you to visualize decoded OBD2 parameters like Speed, Engine Speed, MAF, and Fuel Level.
A key advantage of this approach is the ability to easily modify the OBD2 DBC to include additional proprietary OBD2 PIDs. You can also combine the OBD2 DBC with proprietary CAN DBC files to enable comprehensive CAN and OBD2 car data logging.
What is UDS?
The Unified Diagnostic Services protocol (UDS, ISO 14229-1) is a communication protocol used within automotive ECU communication. A UDS diagnostic tool can send request messages on the CAN bus to retrieve information from specific ECUs. While OBD2 is designed for on-board diagnostics during vehicle operation, UDS is intended for off-board diagnostics when the vehicle is stationary.
How to Make UDS Requests over ISO-TP (ISO 15765-2)
Requesting OBD2 PIDs is relatively straightforward: An OBD2 scan tool or OBD2 data logger sends a specific CAN frame (the OBD2 request), and if the car supports the PID, it responds with a single CAN frame. In contrast, UDS requests may involve transport protocol requests. For example, using UDS service 0x22 to request data by identifier can involve a multi-frame communication sequence:
- A ‘UDS data logger’ sends a request frame specifying the service ID (SID) and data identifier (DID) of interest.
- The car responds with a first frame containing the SID, DID, total message length, and initial payload bytes.
- Shortly after, the UDS logger acknowledges with a flow control frame.
- The ECU then sends consecutive frames with the remaining message payload.
Therefore, logging UDS data requires a UDS tool capable of sending custom CAN frames and flow control frames. Furthermore, the obd2 data logging software free must be able to reconstruct multi-frame UDS responses to extract and decode the payload.
UDS and OBD2 Extended PIDs for Car Data Logging
The UDS service ID (SID) and data identifiers (DID) are sometimes combined into an ‘extended OBD2 PID’, such as 0x220101. Recording UDS data via service 0x22 requests is used to access car data beyond standard service 01 OBD2 PIDs. For example, some electric vehicles provide State of Charge (SoC%) data through UDS requests under service 0x22.
Using the CANedge as a UDS Data Logger
The CANedge can be configured to send UDS requests. This involves sending a request frame and incorporating a flow control frame within a specified timeframe. When configured correctly, this initiates the full sequence of UDS responses. The resulting log files with UDS responses can be analyzed in tools like CANalyzer (by converting MF4 data to Vector ASC) for decoding. Alternatively, multi-frame UDS response data can be processed using our free Python CAN bus API, potentially to populate a Grafana UDS dashboard. Our github API examples include UDS response data and a UDS DBC file for decoding State of Charge (SoC%) from a Hyundai Kona EV. For more information, see our article on EV data loggers or contact us.
Will OBD2 Data Logging Work with My Car?
Most likely, yes. OBD2 is the predominant on-board diagnostics standard for cars and light trucks. It has been mandatory in the USA since 1996 and in the EU since 2003 (where it’s known as EOBD, essentially the same).
However, even with OBD2 support, logging desired data isn’t guaranteed. OBD2 parameter support varies by vehicle model (brand/year). Older cars often have limited support for real-time parameters like speed and RPM. Some manufacturers are also restricting OBD2 data access to control vehicle data. While most cars use CAN for OBD2 communication, older US cars (pre-2008) or certain EU brands might use different protocols.
Note: Check your car’s OBD2 connector for “metal pins” in CAN High (pin 6) and CAN Low (pin 14) – see our OBD2 connector illustration (red pins). If unsure, send us a picture for verification.
There are 5 OBD2 signal protocols:
- ISO 15765 (CAN): Dominant, required in all US vehicles since 2008.
- SAE J1850 (VPW): Ford Motor Company standard.
- SAE J1850 (PWM): General Motors standard.
- ISO 9141-2: Used by Chrysler and some EU/Asian vehicles.
- ISO 14230 (KWP2000): Primarily used by EU manufacturers.
The CANedge/CLX000 supports CAN-based OBD2. Contact us if you’re unsure about your car’s compatibility.
For a preliminary protocol check, you can use this resource: OBD2 compatibility (cars). For a basic understanding, see our OBD2 intro.
You can also use an OBD2 logger to check supported Mode 01 OBD2 parameter IDs in your car by requesting ‘Supported PIDs’ parameters (IDs 00, 20, 40, 60, 80, A0, C0). Analyze the response data bytes to determine PID support (see the Wikipedia OBD2 PID article for details).
OBD2 vs. J1939 Data Logging
OBD2 data logging is generally for cars and light trucks. For heavy-duty vehicles (trucks, tractors, excavators, etc.), J1939 data logging is typically required. J1939 is a standardized protocol in most heavy-duty vehicles, enabling data decoding across brands, similar to OBD2. A J1939 DBC file is needed for decoding J1939 data. The CANedge/CLX000 can also function as a J1939 data logger.
Which OBD2 Data Logger is Right for Me?
Both CANedge and CLX000 data logger series can be used for OBD2 data logging.
For SD card logging, the CANedge series is recommended – it’s optimized for logging and is the 2nd generation of the CLX000. For auto-uploading log files to your server, the CANedge2 is ideal, particularly for OBD2 telematics and OBD2 dashboards.
If real-time OBD2 data streaming via USB to your PC is needed, the CLX000 series, like the CL2000, is recommended.
Contact us for personalized guidance in choosing the best fit for your use case.
Can I Stream OBD2 Data in Real-Time?
Yes, the CLX000 series allows real-time streaming of raw CAN and OBD2 data via USB – see our OBD2 streaming intro.
Raw CAN vs. OBD2 Data Logging
Connecting a CAN logger like CANedge or CLX000 to your car’s OBD2 port will typically begin recording raw CAN bus data by default. This raw CAN data is broadcasted by vehicle sensors for internal communication.
Logging raw CAN data might be preferred if you are the OEM and have the CAN database (DBC file) to decode it. Otherwise, decoding raw CAN data involves car hacking and reverse engineering, although partial databases might be available online from projects like opendbc.
For non-OEM users, OBD2 protocol is generally the primary data collection method. Most modern cars use CAN bus for OBD2 communication. OBD2 data is “on-request,” unlike raw CAN data. To log OBD2 data, you send specific custom CAN frames to request data, and the car may respond if the PID is supported.
Types of OBD2 Devices
The OBD2 device market is extensive. Here are the main categories:
OBD2 Scanners: Used by mechanics for diagnostics, identifying malfunction indicator lamp (MIL) causes, reading and clearing diagnostic trouble codes (DTCs). OBD2 Bluetooth and WiFi scanners offer smartphone access to diagnostic codes.
OBD2 Dongles: Small, low-cost, user-friendly Bluetooth OBD2 readers for consumers. They provide real-time vehicle performance data via smartphone apps, ideal for plug-and-play consumer use, but with limited flexibility. Often based on ELM327 microcontrollers.
OBD2 Data Loggers: Record OBD2 time-series data to SD cards in standalone mode (no PC/app needed). Data is extracted via USB or SD card for later analysis. The CANedge1 is a CAN bus data logger that functions as an OBD2 data logger.
OBD2 WiFi/LTE Loggers: OBD2 data loggers with WiFi or 3G/4G data transfer capabilities. The CANedge2/CANedge3 log OBD2 data to SD cards and auto-transfer it to servers (cloud or self-hosted) via WiFi/LTE, suitable for OBD2 telematics and OBD2 dashboards for fleet data visualization.
OBD2 Interfaces: CAN interfaces that also stream OBD2 data to PCs via USB in real-time. The CLX000 series supports USB streaming of OBD2 data via SavvyCAN.
Will the OBD2 Logger Drain My Car Battery?
In most cases, no.
Typically, CANedge devices connected via the OBD2 connector will power on/off with the ignition, as the OBD2 port often uses the IGN power supply. This prevents battery drain when the car is off.
However, in some vehicles, the OBD2 connector’s power supply is directly battery-wired, potentially keeping the CANedge powered even when the car is off. Power drain from the logger is minimal (<2W), but for extended periods of vehicle inactivity, it’s advisable to verify the logger’s power state.
Check if the logger’s LEDs are lit 15-20 minutes after turning off the car. If LEDs are off, the CANedge is off.
If the CANedge/CLX000 remains on and the vehicle is off for long durations, disconnect the device. Alternatively, configure the CANedge to start/stop transmitting based on CAN data patterns linked to ignition status. A DB9-DC splitter cable and DC-cigarette receptacle adapter can power the CANedge via the cigarette power supply, which is typically ignition-linked. See CANedge Docs for details.
Can I Log GPS Data with OBD2 Data?
While some cars have built-in GPS, accessing this data via OBD2 or proprietary CAN is usually not possible. For practical GPS logging alongside OBD2 data, use a CANedge with GNSS/IMU. This allows synchronized recording of GNSS/IMU data with CAN/OBD2 data from your car via Channel 1.
Ready to start logging OBD2 data from your car?
Get your CANedge today!
Buy now Contact us
Recommended for You
CANEDGE1 – PRO BLACK BOX LOGGER
CANEDGE2 – PRO CAN IoT LOGGER
[