OBD2 Data Logger: Easily Record & Visualize Your Car Data

Looking to effortlessly record OBD2 data from your vehicle?

This introduction provides a concise overview of OBD2 logging fundamentals, highlighting the top 4 advantages and practical use cases. You can also download sample OBD2 data from an Audi A4 (including parameters like speed and RPM).

Unlike most OBD2 dongles and scanners, the CANedge empowers you to log and process your car’s data according to your preferences – utilizing 100% free software and APIs, such as browser-based dashboards:

Alt text: OBD2 telematics dashboard visualized in a browser, showcasing real-time car data and GPS tracking, highlighting a free and open-source solution for vehicle data monitoring.

Discover below why the CANedge stands out as the ideal choice for CAN and OBD2 data logging and telematics applications.

Tip: Begin by watching our concise 4-minute introductory video above!

How OBD2 Data Logging Works

Let’s quickly revisit the basics of OBD2:

OBD2 provides a standardized set of parameters (OBD2 PIDs) that can be recorded and easily interpreted across a wide range of vehicles.

Logging OBD2 data involves these 3 straightforward steps:

Configure your OBD2 logger with a selection of OBD2 PIDs.
Connect the logger to your car using an OBD2 adapter to initiate data recording.
Extract the SD card and decode the logged data using the free software or API.

For more detailed information, consult the FAQ section below or our comprehensive documentation:

CLX000 OBD2 guide CANedge OBD2 guide

Alt text: Diagram illustrating the OBD2 data logging process in a vehicle, showcasing the connection of an OBD2 logger to the car’s port, data recording of PIDs, and the use of software for data analysis, emphasizing vehicle data recording and odometer tracking.

Top 4 Benefits of OBD2 Data Logging

OBD2 logging allows you to gather data from virtually any car. Below are the key advantages:

Alt text: OBD2 data logger used for OEM part analysis, showing a black box logger in a car and a time-series graph representing benchmark data for part optimization and performance analysis.

Driver/Vehicle/Part Optimization

OBD2 data facilitates the monitoring and optimization of driving habits, as well as car tuning. OEMs can leverage this data to evaluate the real-world performance of new prototype components.

Alt text: OBD2 logger aiding in rare issue diagnostics, featuring a logger connected to a car, an SD card symbolizing data storage, and icons representing bug troubleshooting and diagnostic processes.

Rare Issue Diagnostics

Intermittent car problems might occur briefly while driving, but not during repair shop diagnostics. OBD2 data logging enables analysis of the data surrounding such events, aiding in effective troubleshooting.

Alt text: OBD2 data logger for vehicle fleet management, depicting cars and trucks with WiFi/3G/4G connectivity, illustrating applications in fleet tracking, insurance telematics, breakdown prediction, and fuel efficiency monitoring.

Car Fleet Management

OBD2 WiFi telematics at the fleet level supports various applications, including driver behavior analysis, fuel cost reduction, breakdown minimization, compliance monitoring, dispute resolution, and predictive maintenance.

Alt text: Open-source OBD2 data logger system interoperability, showcasing hardware components, open-source icons, and telematics applications, emphasizing data control and custom integration possibilities.

Data Control & Custom Integration

With an OBD2 WiFi logger, you record raw time-series data, which can be accessed via SD card or uploaded to your server. This facilitates seamless custom integration through open APIs.

Which of these benefits align with your OBD2 logging objectives? Contact us for a free consultation!

The CANedge OBD2 Data Logger

The CANedge CAN bus data logger offers optional GPS/IMU, WiFi, and/or 3G/4G capabilities, making it ideal for OBD2 fleet telematics:

Alt text: Plug & Play CAN Logger for easy use, depicting a simple setup connecting a vehicle to the cloud via LTE, emphasizing out-of-the-box functionality and standalone operation.

PLUG & PLAY
Log data immediately. Standalone operation. Connect your vehicle to your server effortlessly.

Alt text: High-performance CAN Bus Data Logger with professional specifications, listing features like extractable 8-32GB SD card, dual CAN/LIN channels, CAN FD support, zero data loss, 50 µs RTC, error frame logging, and MF4 file format.

PRO SPECS
Extractable 8-32 GB SD. 2xCAN/LIN. CAN FD. Zero data loss. 50 Î¼s RTC. Error frames. MF4.

Alt text: Compact and rugged small CAN Bus Data Logger and LIN analyzer, highlighting dimensions of 8x5x2 cm, 100G shock resistance, robust aluminum enclosure, 5+ LEDs, and configurable 5V power output.

COMPACT
Only 8 x 5 x 2 CM. 100G shock rating. Robust aluminum enclosure. 5+ LEDs. Configurable 5V power out (CH2).

Alt text: Secure vehicle fleet telematics with WiFi and 3G/4G, illustrating data push to a server and emphasizing end-to-end security and over-the-air update capabilities for robust fleet management.

WIFI/LTE
Push data via WiFi or 3G/4G to your server. E2E security. OTA updates.

Alt text: GNSS GPS IMU data capture, showcasing a GNSS/IMU sensor unit and highlighting 3x accuracy through sensor fusion, enabling position, speed, distance, and more data logging.

GNSS + 3D IMU
Built-in GPS/IMU. 3x accuracy via sensor fusion. Position, speed, distance & more.

Alt text: Interoperable open-source API and free CAN Bus software, featuring icons for software files, MF4 and MDF formats, and emphasizing free open-source tools, MF4 to ASC/CSV conversion, DBC support, Python API, and dashboard integration.

INTEROPERABLE
Free open-source software/APIs. MF4 to ASC/CSV. DBC support. Python. Dashboards.

learn more

Software Example: OBD2 Dashboard for Your Cars

With the CANedge, setting up complimentary, personalized browser dashboards to visualize your OBD2 data and configure alerts becomes straightforward.

You can also integrate your OBD2 data with GPS/IMU data by utilizing a CANedge equipped with GNSS/IMU.

Explore our online playground or delve deeper into our introductory guide!

playground dashboards intro

Get the ‘OBD2 Data Pack’

Interested in experimenting with actual OBD2 data?

Download our ‘data pack’ which includes:

Our OBD2 DBC
25+ car DBCs (reverse engineered)
100+ MB of data from 10+ cars

download now

Alt text: OBD2 data pack graphic, a transparent box containing data files and car icons, symbolizing a comprehensive collection of OBD2 data resources for download.

Use Case Examples

Below are practical examples of how the CANedge can be applied for OBD2 data logging.

OEM Field Testing of Vehicle Parts

Do you need to log CAN/OBD2 field data from vehicles in operation?

As an OEM, you might require late-stage field evaluations of prototype equipment. This often involves collecting OBD2 and CAN data from multiple vehicles over extended periods, such as months. The CANedge1 is perfectly suited for this, given its compact size, plug-and-play simplicity, and easy pre-configuration. Data can be collected periodically and analyzed using your preferred CAN tools or the free asammdf GUI/API.

canedge1

Alt text: OBD2 data logger in OEM field testing, illustrating a car undergoing testing with an OBD2 logger connected, focusing on OEM development, field tests, and data collection for prototype equipment evaluation.

Alt text: OBD2 for vehicle fleet management in trucks and cars, depicting various vehicles with 4G connectivity, highlighting OEM telematics applications for fleet tracking and data management.

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

Are you looking to implement OBD2 telematics for on-road vehicle fleets?

The CANedge3 can upload recorded OBD2 data via 3G/4G using your SIM card. This enables near real-time wireless OBD2 data transfer from on-road vehicles to your cloud server. OBD2 data can be automatically processed using open APIs (including OBD2 DBC decoding support), and CANedge3 devices can be updated over-the-air. Furthermore, the CANedge3 integrates a GPS/IMU, adding location, speed, trip distance, acceleration, and attitude data to your dataset.

canedge3

Case Study: OBD2/CAN Telematics

Alt text: Volkswagen logo case study using CANedge, featuring the VW logo and CANedge product, representing a case study on OBD2 and CAN telematics solutions implemented by Volkswagen.

Discover how Volkswagen utilizes the CANedge2 to log OBD2 and raw CAN data to an SD card, and automatically push this data to their self-hosted server for analysis.

“The CANedge2 allowed us to get up and running quickly with solid configuration options – and the support was exceptional!“

learn more 100+ case studies

Alt text: OBD2 telematics WiFi data logger illustration, showing a Volkswagen vehicle transmitting data wirelessly to a server, representing a use case for WiFi-enabled OBD2 data logging in vehicle telematics.

Alt text: OBD2 MDF4 Data Logger Pro CANedge2, showcasing a dashboard visualization of RPM, Speed, and Throttle data, highlighting the professional capabilities of the OBD2 data logger for detailed vehicle performance analysis.

OBD2 Data from an Audi A4

You can download OBD2 samples from the CANedge below.

You can also download the free open-source OBD2 software and explore the process of decoding raw OBD2 data.

Raw OBD2 Decoded OBD2 Software

FAQ

The OBD2 protocol (SAE J1979) defines a standardized set of vehicle data parameters that you can log from your car. However, the OBD2 data supported varies across different car models, with older cars 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 details, refer to the OBD2 PID Wiki page or the SAE J1979 standard.

To convert raw OBD2 data from a CANedge OBD2 data logger into physical values (km/h, rpm, etc.), you need a database of decoding rules and appropriate OBD2 software.

For this purpose, we offer a 100% free OBD2 DBC file, which includes most of the standardized Mode 01 (Service 01) OBD2 PID decoding rules, as found on resources like the OBD2 PID Wiki page.

The OBD2 DBC file uses extended multiplexing for OBD2 decoding. Learn more in 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 software tools (e.g., asammdf or our OBD2 dashboard integrations). This allows you to visualize your decoded OBD2 data, such as Speed, Engine Speed, MAF, Fuel Level, etc.

A key benefit of this approach is the ease of modifying 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 into 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 data logger sends a specific CAN frame (the OBD2 request), and if supported, the car 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 involves a more complex communication flow:

A ‘UDS data logger’ sends a request frame specifying the service ID (SID) and data identifier (DID).
The car responds with a first frame containing the SID, DID, total message length, and initial payload bytes.
The UDS logger acknowledges with a flow control frame.
The ECU 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. Software tools must also 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. Service 0x22 UDS requests are used to access car data beyond standard service 01 OBD2 PID requests. For example, some electric vehicles provide State of Charge (SoC%) data via UDS requests under service 0x22.

Using the CANedge as a UDS Data Logger

The CANedge can be configured to send UDS requests by transmitting a request frame and a flow control frame within a specified time. This triggers the full UDS response sequence. Log files with UDS responses can be analyzed in tools like CANalyzer (by converting MF4 data to Vector ASC) for decoding. Alternatively, process multi-frame UDS response data using our free Python CAN bus API to, for example, push parameters to 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 EV data logger article or contact us.

Is My Car OBD2 Compatible?

Most likely, yes. OBD2 is standard for on-board diagnostics in most cars and light trucks. It has been mandatory in the USA since 1996 and in the EU since 2003 (EOBD, essentially the same).

However, OBD2 support does not guarantee access to all desired data. Parameter support varies by vehicle model (brand/year), with older cars often having limited real-time parameter support like speed and RPM. Some car manufacturers are also restricting OBD2 data access for better data control. While most cars use CAN for OBD2 communication, older US cars (pre-2008) or some EU brands might use other protocols.

Note: Check your OBD2 connector for “metal pins” at CAN High (pin 6) and CAN Low (pin 14) to confirm CAN logger compatibility, as illustrated in our OBD2 connector diagram (red pins). If unsure, send us a photo.

There are 5 OBD2 signal protocols:

ISO 15765 (CAN): Dominant, required in US vehicles since 2008.
SAE J1850 (PWM): Ford Motor Company standard.
SAE J1850 (VPW): General Motors standard.
ISO 9141-2: Used by Chrysler and some EU/Asian vehicles.
ISO 14230 (KWP2000): Mainly used by EU manufacturers.

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

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

With an OBD2 logger, you can also check supported Mode 01 OBD2 parameter IDs by requesting ‘Supported PIDs’ parameters (IDs 00, 20, 40, 60, 80, A0, C0). Analyze the response data bytes bit-by-bit 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), J1939 data logging is typically needed. J1939 is a standardized protocol in most heavy-duty vehicles, enabling data decoding across brands, similar to OBD2. A J1939 DBC file is required to decode J1939 data, and the CANedge/CLX000 can also function as a J1939 data logger.

CANedge vs CLX000 for OBD2 Logging

Both CANedge and CLX000 data logger series can be used as OBD2 data loggers.

For SD card logging, the CANedge series (2nd generation of CLX000) is recommended, optimized for logging. For auto-uploading log files to your server, the CANedge2 is ideal, especially for OBD2 telematics and OBD2 dashboards setups.

For real-time OBD2 data streaming via USB to your PC, the CLX000 series, like the 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 vs OBD2 Data Logging

Connecting a CAN logger like CANedge or CLX000 to your car via OBD2 connector typically starts recording raw CAN bus data by default. This raw CAN data is broadcasted by car sensors for internal communication.

Logging raw CAN data might be preferred if you are the OEM and have CAN databases (DBC files) to decode it. Otherwise, decoding raw CAN data requires car hacking and reverse engineering. Partial databases for some car models may be available online from projects like opendbc.

For non-OEM users, OBD2 protocol is usually the primary option for data collection. Almost all cars use CAN bus for OBD2 communication. OBD2 data is “on-request,” unlike raw CAN data. Logging OBD2 data involves sending custom CAN frames to request specific data, and the car may respond if the OBD2 PID is supported.

OBD2 Device Types

The market offers numerous OBD2 device types:

OBD2 Scanners: Used by mechanics for diagnostics, identifying and clearing diagnostic trouble codes (DTCs). OBD2 Bluetooth and WiFi scanners offer convenient smartphone access to diagnostic codes.

OBD2 Dongles: Small, low-cost, user-friendly Bluetooth OBD2 readers for consumers, providing real-time vehicle performance data via smartphone apps. They are plug-and-play but offer limited flexibility, often using an ELM327 microcontroller.

OBD2 Data Loggers: Record OBD2 time-series data to SD cards in standalone mode (no PC/app needed). Data is later extracted via USB or SD card. The CANedge1 is a CAN bus data logger usable as an OBD2 data logger.

OBD2 WiFi/LTE Loggers: OBD2 data loggers with WiFi or 3G/4G data transfer, like CANedge2/CANedge3, log OBD2 data to SD cards and auto-transfer it to servers via WiFi/LTE, ideal for OBD2 telematics and creating OBD2 dashboards for fleet data visualization.

OBD2 Interfaces: CAN interfaces like CLX000 can also serve as OBD2 interfaces, enabling real-time USB streaming of OBD2 data to PCs via SavvyCAN.

Does the Logger Drain Car Battery?

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

However, some vehicles might have OBD2 connector power directly connected to the battery, potentially keeping the CANedge on when the car is off. Logger power drain is minimal (

Verify logger on/off behavior by checking LEDs 15-20 minutes after turning off the car. If LEDs are off, CANedge is off.

If CANedge/CLX000 stays on and the vehicle is off for extended periods, disconnect the device or configure CANedge to start/stop transmitting based on CAN data patterns linked to ignition status. Alternatively, use a DB9-DC splitter cable and DC-cigarette receptacle adapter to power CANedge via the cigarette power supply, typically ignition-linked. See CANedge Docs for details.

Can I Log GPS Data with OBD2 Data?

While your car might have built-in GPS, extracting data via OBD2 or proprietary CAN data is rarely possible. We recommend using a CANedge with GNSS/IMU to record GNSS/IMU data synchronized 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

[