How to Record OBD2 Data: A Comprehensive Guide for Car Enthusiasts and Professionals

Do you want to record OBD2 data from your car?

This guide provides a comprehensive overview of OBD2 data logging, detailing its key benefits and practical applications. We’ll also provide sample OBD2 data (speed, RPM, etc.) from an Audi A4 for your reference.

Unlike many generic OBD2 dongles and scanners, the CANedge empowers you to log and analyze your vehicle’s data on your terms, offering 100% free software and APIs, including browser-based dashboards:

Discover why the CANedge is the ideal solution for CAN and OBD2 data logging and telematics in the sections below.

Tip: Watch our 4-minute introductory video above to quickly grasp the essentials!

Understanding OBD2 Data Logging

Let’s begin with a brief recap of OBD2 basics.

OBD2 (On-Board Diagnostics II) provides a standardized set of parameters, known as OBD2 PIDs, that can be easily recorded and decoded across a wide range of vehicles. This standardization simplifies accessing crucial vehicle performance and diagnostic information.

To record OBD2 data, the process generally involves three straightforward steps:

Configuration: Set up your OBD2 data logger with a list of specific OBD2 PIDs you wish to capture. This selection determines the type of data you will record, such as speed, RPM, engine temperature, and more.
Connection: Connect the configured OBD2 logger to your vehicle using an OBD2 adapter. This connection is typically found under the dashboard and provides access to the vehicle’s data network. Once connected, the logger begins recording data as you drive.
Extraction & Decoding: After driving, extract the data from the logger, usually via an SD card. Utilize free software or APIs to decode the raw data using OBD2 standards and DBC files, transforming it into readable and analyzable formats.

For more detailed instructions, refer to our comprehensive guides:

CLX000 OBD2 guide
CANedge OBD2 guide

Top 4 Benefits of OBD2 Data Logging

Recording OBD2 data offers numerous advantages for various applications. Here are four key benefits:

1. Driver, Vehicle, and Part Optimization

OBD2 data provides valuable insights for optimizing driving habits, fine-tuning vehicle performance, and assessing prototype part performance. For instance, fleet operators can monitor driver behavior for fuel efficiency, while OEMs can benchmark new components against field performance data. Analyzing parameters like speed, acceleration, and engine load helps in identifying areas for improvement and efficiency gains.

2. Rare Issue Diagnostics

Intermittent vehicle problems can be challenging to diagnose during standard repair shop visits. By recording OBD2 data continuously while driving, you capture data around the occurrence of a rare issue. This recorded data allows for in-depth analysis of vehicle parameters leading up to, during, and after the event, helping to pinpoint the root cause that might not be evident during static diagnostics.

3. Car Fleet Management

Implementing OBD2 telematics across vehicle fleets enables significant operational improvements. Recording OBD2 data facilitates driver behavior analysis for safety and efficiency, reduces fuel costs through optimized driving patterns, minimizes breakdowns via proactive maintenance alerts, ensures regulatory compliance, aids in dispute resolution, and supports predictive maintenance strategies to preemptively address potential failures.

4. Data Control & Custom Integration

Utilizing an OBD2 WiFi logger grants you complete control over your data. By recording OBD2 data in raw time-series format, you can extract it via SD card or upload it to your own server. This approach supports custom integration through open APIs, allowing you to tailor data processing and visualization to your specific needs without reliance on proprietary platforms.

Interested in exploring how OBD2 logging can benefit your specific use case? We’re here to help!

Introducing the CANedge OBD2 Data Logger

The CANedge CAN bus data logger is engineered for advanced OBD2 data capture and telematics applications. It offers optional GPS/IMU, WiFi, and 3G/4G connectivity, making it an ideal solution for OBD2 fleet telematics and in-depth vehicle analysis.

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, 50 µs RTC, error frame logging, and MF4 file format.

COMPACT: Measuring only 8 x 5 x 2 CM, encased in a robust aluminum enclosure, 100G shock resistance, includes 5+ LEDs, and configurable 5V power output.

WIFI/LTE: Offers data push via WiFi or 3G/4G to your server with end-to-end security and Over-The-Air (OTA) updates for device management. E2E security.

GNSS + 3D IMU: Built-in GPS/IMU provides 3x accuracy through sensor fusion, capturing position, speed, distance, acceleration, and more.

INTEROPERABLE: Comes with free open-source software/APIs, supports MF4 to ASC/CSV conversion, DBC integration, Python libraries, and customizable dashboards.

Learn more about CANedge

Visualize Your Data: OBD2 Dashboard Examples

With CANedge, creating custom, free browser dashboards to visualize your recorded OBD2 data and set up alerts is straightforward.

Enhance your data insights by combining OBD2 parameters with GPS/IMU data using a CANedge equipped with GNSS/IMU.

Explore our online playground or delve deeper with our dashboard introduction:

Playground
Dashboards intro

Get Started with the ‘OBD2 Data Pack’

Eager to work 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

Practical Use Cases for OBD2 Data Logging

Below are real-world examples illustrating how CANedge is used for recording OBD2 data in diverse applications.

OEM Field Testing of Vehicle Parts

Need to record CAN/OBD2 field data from vehicles in operation?

For OEMs conducting late-stage field tests of prototype equipment, recording OBD2 and CAN data over extended periods across multiple vehicles is crucial. The CANedge1 excels in this scenario due to its compact, plug-and-play design and easy pre-configuration. Data can be periodically collected and analyzed using standard CAN tools or the free asammdf GUI/API.

CANedge1 Details

Vehicle Telematics (OBD2 + GNSS/IMU + 3G/4G)

Looking to establish OBD2 telematics for on-road vehicle fleets?

The CANedge3 enables wireless OBD2 data transfer via 3G/4G using your own SIM card. This allows for near real-time transmission of recorded OBD2 data from vehicles to your cloud server. Data processing can be automated via open APIs, including OBD2 DBC decoding. CANedge3 devices also support over-the-air updates and integrate GPS/IMU for location, speed, and motion data.

CANedge3 Details

Case Study: OBD2/CAN Telematics Implementation

Discover how Volkswagen utilizes the CANedge2 to record OBD2 and raw CAN data onto SD cards and automatically push data to their self-hosted server for comprehensive analysis.

“The CANedge2 allowed us to get operational rapidly with flexible configuration options, and the support was exceptional!”

Learn more
Explore 100+ case studies

Accessing OBD2 Data from an Audi A4

Download OBD2 data samples recorded with CANedge below.

You can also download our free open-source OBD2 software to practice decoding raw OBD2 data.

Raw OBD2 Data
Decoded OBD2 Data
Free Software

Frequently Asked Questions (FAQ)

The OBD2 protocol (SAE J1979) standardizes access to a variety of vehicle data parameters. However, the specific OBD2 data supported varies by vehicle, with older models often supporting fewer parameters.

Here are some common standard OBD2 parameters typically 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 details, consult the OBD2 PID Wiki or the SAE J1979 standard.

To decode raw OBD2 data from a CANedge OBD2 data logger into physical units (km/h, rpm, etc.), you need a database of decoding rules—an OBD2 DBC file—and compatible OBD2 software.

We offer a 100% free OBD2 DBC file that includes most standardized Mode 01 OBD2 PID decoding rules, similar to those listed on the OBD2 PID Wiki page.

This OBD2 DBC file utilizes extended multiplexing for effective OBD2 decoding. Learn more in our DBC intro and OBD2 intro, where we explain interpreting raw CAN frames with OBD2 responses.

You can load your raw recorded OBD2 data and the OBD2 DBC file into our free software tools like asammdf or our OBD2 dashboard integrations to visualize decoded OBD2 data such as Speed, Engine Speed, MAF, and Fuel Level.

A key advantage of this approach is the flexibility to modify the OBD2 DBC to incorporate proprietary OBD2 PIDs. You can also combine it with proprietary CAN DBC files for comprehensive CAN and OBD2 car data logging.

What is UDS?

The Unified Diagnostic Services protocol (UDS, ISO 14229-1) is used for ECU communication in vehicles. While OBD2 is for on-board diagnostics during vehicle operation, UDS is designed for off-board diagnostics when the vehicle is stationary, enabling deeper diagnostic and configuration capabilities.

How to Make UDS Requests over ISO-TP (ISO 15765-2)

Requesting OBD2 PIDs is straightforward; a single request frame typically yields a single response frame. UDS requests, however, may involve multi-frame communication using transport protocols. For example, a UDS service 0x22 data request involves:

A ‘UDS data logger’ sending a request frame with a service ID (SID) and data identifier (DID).
The car responding with a first frame containing SID, DID, total message length, and initial payload.
The UDS logger acknowledging with a flow control frame.
The ECU sending subsequent consecutive frames with the remaining message payload.

Recording UDS data requires tools capable of sending custom CAN frames and managing flow control frames. Software must also reconstruct multi-frame UDS responses to decode the payload.

UDS and OBD2 Extended PIDs for Car Data Logging

UDS service IDs and data identifiers are sometimes combined into ‘extended OBD2 PIDs,’ like 0x220101. Service 0x22 UDS requests can access vehicle data beyond standard OBD2 PIDs. For instance, electric vehicles may provide State of Charge (SoC%) data via UDS service 0x22.

Using CANedge as a UDS Data Logger

CANedge can be configured to send UDS requests by transmitting a request frame and a flow control frame within milliseconds. Log files with UDS responses can be analyzed using tools like CANalyzer (by converting MF4 to Vector ASC) or processed via our free Python CAN bus API for parameters like State of Charge, visualized on a Grafana UDS dashboard. Our GitHub API examples include UDS response data and a UDS DBC file for decoding Hyundai Kona EV SoC%. More details are available in our EV data logger article or by contacting us.

Is My Car OBD2 Compatible?

Most cars and light trucks are OBD2 compatible, especially in the USA (since 1996) and EU (EOBD since 2003). However, OBD2 data availability varies by vehicle model, with older cars often supporting fewer parameters. Some manufacturers are also restricting OBD2 data access. While most cars use CAN for OBD2, older US models or some EU brands may use other protocols.

Check your OBD2 connector: Ensure “metal pins” are present at CAN High (pin 6) and CAN Low (pin 14). Refer to our OBD2 connector illustration (red pins). If unsure, send us a photo.

OBD2 Signal Protocols include:

ISO 15765 (CAN): Predominant since 2008 in the USA.
SAE J1850 (PWM & VPW): Ford and GM standards.
ISO 9141-2: Chrysler and some EU/Asian vehicles.
ISO 14230 (KWP2000): Primarily EU manufacturers.

CANedge/CLX000 supports CAN-based OBD2. Contact us if you’re unsure about your car’s compatibility.

For a protocol check, see: OBD2 compatibility (cars). For basics, see our OBD2 intro.

You can also use an OBD2 logger to check supported Mode 01 OBD2 PIDs by requesting ‘Supported PIDs’ parameters (IDs 00, 20, 40, 60, 80, A0, C0) and analyzing the responses (see Wikipedia OBD2 PID).

J1939 vs OBD2 for Data Logging

OBD2 is typical for cars and light trucks. For heavy-duty vehicles (trucks, tractors, etc.), J1939 is commonly used. J1939 is a standardized protocol for heavy-duty vehicles, similar to OBD2 for light vehicles. Decoding J1939 data requires a J1939 DBC file. CANedge/CLX000 can also function as a J1939 data logger.

CANedge vs CLX000 for OBD2 Data Logging

Both CANedge and CLX000 series loggers can record OBD2 data.

For SD card logging, CANedge is recommended as it’s optimized for logging. For auto-uploading log files, CANedge2 (CANedge2 on Amazon) is ideal for OBD2 telematics and OBD2 dashboards.

For real-time OBD2 data streaming via USB to a PC, the CLX000 series, like CL2000, is recommended.

Can I Stream OBD2 Data in Real-Time?

Yes, the CLX000 series supports real-time streaming of raw CAN and OBD2 data via USB. See our OBD2 streaming intro.

Raw CAN Data vs OBD2 Data Logging

Connecting a CAN logger like CANedge to your OBD2 port will default to recording raw CAN bus data in most vehicles. This raw data is used for internal vehicle communication.

OEMs may use raw CAN data with proprietary CAN databases (DBC files). For non-OEMs, decoding raw CAN data usually involves reverse engineering. Projects like opendbc may offer partial databases.

For most users, OBD2 is the primary method for data collection. OBD2 communication is request-based over CAN bus. Recording OBD2 data involves sending specific CAN frames to request data, and the vehicle responds if the PID is supported.

Types of OBD2 Devices

The OBD2 device market includes:

OBD2 Scanners: Used by mechanics for diagnostics, reading and clearing diagnostic trouble codes (DTCs). Includes Bluetooth and WiFi scanners for smartphone access.

OBD2 Dongles: Simple, low-cost Bluetooth OBD2 readers for consumers, often using ELM327 microcontrollers and smartphone apps for real-time data viewing. Limited flexibility.

OBD2 Data Loggers: Standalone devices that record OBD2 time-series data to SD cards without needing a PC or app. CANedge1 is an example.

OBD2 WiFi/LTE Loggers: OBD2 loggers with WiFi or 3G/4G for data transfer, like CANedge2/CANedge3, ideal for OBD2 telematics and OBD2 dashboards for fleet data visualization.

OBD2 Interfaces: CAN interfaces like CLX000 that also stream OBD2 data in real-time to a PC via USB, using software like SavvyCAN.

Does the OBD2 Logger Drain Car Battery?

Usually, CANedge turns on/off with the ignition via the OBD2 connector’s IGN power supply, minimizing battery drain.

In some vehicles, OBD2 power is directly battery-connected. CANedge power draw is minimal (<2W). To verify, check LEDs 15-20 minutes after turning off the car; no LEDs mean it’s off.

If it doesn’t turn off, disconnect for long periods or configure CANedge to start/stop transmitting based on CAN data patterns related to ignition status. Alternatively, use a DB9-DC splitter cable and cigarette lighter adapter for ignition-linked power. See CANedge Docs for details.

Can I Log GPS Data with OBD2 Data?

While cars may have built-in GPS, OBD2 or proprietary CAN data extraction is rarely possible. Use a CANedge with GNSS/IMU to record time-synced GPS/IMU data alongside CAN/OBD2 data.

Ready to Start Recording OBD2 Data?

Get Your CANedge Today!

Buy Now
Contact Us

Recommended for You

CANEDGE1 – PRO BLACK BOX LOGGER

CANEDGE2 – PRO CAN IoT LOGGER

CAN BUS INTERFACE: STREAMING OBD2 DATA WITH SAVVYCAN