OBD2 Logger: Easily Record & Visualize Your Car Data

Want to effortlessly record OBD2 data from your vehicle?

This guide introduces the fundamentals of OBD2 logging, highlighting the top 4 advantages and practical applications. You can even download sample OBD2 data from an Audi A4, encompassing parameters like speed and RPM.

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

Discover below why the CANedge stands out as the ideal Obd2 Logger for CAN and OBD2 data logging and telematics solutions.

Tip: Begin with our 4-minute introductory video featured above!

Understanding OBD2 Data Logging

Let’s start with a quick recap of OBD2 basics.

OBD2 provides a standardized set of parameters known as OBD2 PIDs. These parameters are consistent across most vehicles, making data recording and decoding straightforward.

Logging OBD2 data involves three simple steps:

Configure your OBD2 logger: Select the OBD2 PIDs you wish to record.
Connect to your vehicle: Use an OBD2 adapter to connect the logger to your car’s OBD2 port and initiate logging.
Extract and decode data: Retrieve the SD card from the logger and use free software/APIs to decode the recorded data.

For detailed instructions, refer to the FAQ section below or consult our documentation:

CLX000 OBD2 guide CANedge OBD2 guide

Alt text: OBD2 data logger setup diagram showing connection to vehicle, data recording, and software analysis.

Top 4 Benefits of Using an OBD2 Logger

OBD2 logging enables data collection from virtually any car. Here are the key advantages:

Alt text: OBD2 logger used for OEM part analysis and performance benchmarking.

Driver, Vehicle, and Part Optimization

OBD2 data empowers you to monitor and refine driving habits, as well as optimize vehicle performance. Original Equipment Manufacturers (OEMs) utilize this data to assess the real-world performance of new prototype components.

Alt text: OBD2 logger aiding in diagnosing intermittent car issues using SD card data.

Diagnostics for Intermittent Issues

Transient car problems that occur while driving may not be present during service checks. OBD2 logging allows you to analyze data captured around the time of an event, facilitating effective troubleshooting.

Alt text: OBD2 logger for fleet management, improving fuel efficiency and reducing breakdowns.

Enhanced Fleet Management for Cars

OBD2 WiFi telematics at a fleet level provides valuable insights for driver behavior analysis, fuel efficiency improvements, breakdown reduction, regulatory compliance, dispute resolution, and predictive maintenance.

Alt text: Open source OBD2 logger system for custom telematics integration and data control.

Data Control & Custom Integration

With a WiFi-enabled OBD2 logger, you gain control over raw time-series data. This data can be extracted via SD card or wirelessly uploaded to your server, enabling seamless custom integration through open APIs.

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

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:

Alt text: Plug & Play CAN logger connecting vehicles to cloud servers, easy to use.

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

Alt text: High-performance CAN logger specs with large SD card, dual CAN/LIN, and error frame detection.

PRO SPECS
Extractable 8-32 GB SD card. Dual CAN/LIN channels. CAN FD support. Zero data loss. 50 µs RTC. Error frame capture. MF4 format.

Alt text: Compact and rugged CAN bus data logger, small form factor with robust enclosure.

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

Alt text: Secure WiFi/LTE CAN bus logger for vehicle telematics, enabling E2E security and OTA updates.

WIFI/LTE
Push data via WiFi or 3G/4G to your server. End-to-end security. Over-the-air (OTA) updates.

Alt text: GNSS GPS IMU data integration in CAN logger for position, speed, and distance tracking.

GNSS + 3D IMU
Integrated GPS/IMU. 3x accuracy via sensor fusion. Captures position, speed, distance, and more.

Alt text: Open source CAN bus software and APIs for data analysis and dashboard creation.

INTEROPERABLE
Free open source software/APIs. MF4 to ASC/CSV conversion. DBC support. Python integration. Dashboard examples.

learn more

Software Example: OBD2 Dashboard for Your Vehicles

The CANedge simplifies the creation of free, customized browser dashboards to visualize your OBD2 data and set up alerts.

Enhance your OBD2 data with GPS/IMU information by using a CANedge equipped with GNSS/IMU.

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

playground dashboards intro

Get the ‘OBD2 Data Pack’

Want hands-on experience with real OBD2 data?

Download our ‘data pack’ which includes:

Our OBD2 DBC file
25+ car DBC files (reverse-engineered)
100+ MB of data from 10+ vehicles

download now

OBD2 Logger Use Case Examples

Below are practical scenarios illustrating 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 real-world conditions?

As an OEM, late-stage field testing of prototype equipment is crucial. This often requires OBD2 and CAN data from multiple vehicles over extended periods, such as months. The CANedge1 is perfectly suited for this due to its compact size, plug-and-play ease, and simple pre-configuration. Data can be collected periodically and analyzed using your preferred CAN tools or the free asammdf GUI/API.

canedge1

Alt text: OBD2 logger used in OEM field testing for prototype vehicle equipment.

Alt text: OBD2 logger for vehicle fleet management in trucks and cars, OEM telematics applications.

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

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

The CANedge3 can wirelessly transmit recorded OBD2 data via 3G/4G using your SIM card. This enables near real-time OBD2 data transfer from vehicles to your cloud server. OBD2 data can be automatically processed using open APIs (including OBD2 DBC decoding support), while CANedge3 devices support over-the-air updates. Furthermore, the integrated GPS/IMU in the CANedge3 adds valuable data like position, speed, trip distance, acceleration, and orientation.

canedge3

Case Study: OBD2/CAN Telematics

Discover how Volkswagen leverages the CANedge2 to log both OBD2 and raw CAN data to an SD card, while also automatically pushing data to their self-hosted server for analysis.

“The CANedge2 allowed us to get up and running quickly with robust configuration options – and the support was outstanding!”

learn more 100+ case studies

Alt text: OBD2 telematics system illustration with WiFi data logger and Volkswagen use case.

OBD2 Data Example from an Audi A4

Download OBD2 data samples recorded with the CANedge below.

You can also download our free open-source OBD2 software to experience the process of decoding raw OBD2 data firsthand.

Raw OBD2 Decoded OBD2 Software

FAQ – OBD2 Logger

The OBD2 protocol (SAE J1979) defines a range of standardized vehicle data parameters available for logging. However, the specific OBD2 data supported varies across car models, with older vehicles often supporting fewer parameters.

Here are some common standard OBD2 parameters:

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 logger into meaningful values (km/h, rpm, etc.), you need a database of decoding rules and suitable OBD2 software.

We provide a 100% free OBD2 DBC file which includes the majority of standardized Mode 01 (Service 01) OBD2 PID decoding rules, similar to those found on the OBD2 PID Wiki page.

The OBD2 DBC file utilizes extended multiplexing for OBD2 decoding. For further information, see 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, such as asammdf or our OBD2 dashboard integrations. This allows you to visualize decoded OBD2 data like Speed, Engine Speed, MAF, Fuel Level, and more.

A key advantage of this approach is the ability to easily modify the OBD2 DBC to incorporate 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 for ECU communication in vehicles. While OBD2 is designed for on-board diagnostics during vehicle operation, UDS is intended for off-board diagnostics when the vehicle is stationary. UDS diagnostic tools can send request messages over the CAN bus to retrieve information from specific ECUs.

How to make UDS requests over ISO-TP (ISO 15765-2)

Requesting OBD2 PIDs is relatively straightforward: an OBD2 scan tool or OBD2 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 may involve the following 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.
Shortly after, the UDS logger acknowledges with a flow control frame.
The ECU then sends consecutive frames with the remaining payload.

Therefore, logging UDS data requires a UDS tool capable of sending custom CAN frames and flow control frames. The software must also 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. Service 0x22 UDS requests are used to access car data beyond standard OBD2 PIDs. For instance, 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 timeframe. This initiates the full sequence of UDS responses. The resulting log files can be analyzed using tools like CANalyzer (by converting MF4 data to Vector ASC) or processed using our free Python CAN bus API to 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 the dominant 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 is known as EOBD, essentially the same standard).

However, OBD2 support doesn’t guarantee access to all desired data. Vehicle models vary in supported OBD2 parameters, with older cars often having limited support for real-time parameters like speed and RPM. Some manufacturers are also restricting OBD2 data access to control vehicle data better. While most cars use CAN for OBD2 communication, older US cars (pre-2008) and some EU brands may use other protocols.

Note: Check your OBD2 connector for “metal pins” in positions 6 (CAN High) and 14 (CAN Low) – see our OBD2 connector illustration (red pins). If unsure, send us a picture for verification.

There are five OBD2 signal protocols:

ISO 15765 (CAN): Predominant, mandatory 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): Primarily used by EU manufacturers.

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

You can also perform a rough protocol check for your car here: OBD2 compatibility (cars). For a basic overview, see our simple intro to OBD2.

With an OBD2 logger, you can verify 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 logger vs J1939 logger

OBD2 logging is generally for cars and light trucks. For heavy-duty vehicles like trucks, tractors, and excavators, you typically need to log J1939 data. J1939 is a standardized protocol in most heavy-duty vehicles, enabling data decoding across brands, similar to OBD2. Decoding J1939 data requires a J1939 DBC file, and the CANedge/CLX000 can also function as a J1939 data logger.

Which OBD2 logger should I choose – CANedge or CLX000?

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

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

For real-time OBD2 data streaming via USB to your PC, the CLX000 series, such as the CL2000, is recommended.

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 data vs OBD2 data logging

Connecting a CAN logger like CANedge or CLX000 to your car’s OBD2 port will, by default, record raw CAN bus data (in most cars). This raw CAN data is broadcasted by car sensors for internal communication.

OEMs may want to log raw CAN data as they understand the CAN IDs and data bytes and possess CAN databases (DBC files) for decoding. For non-OEMs, decoding raw CAN data requires car hacking and reverse engineering. Partial databases for specific car models may be found online from projects like opendbc.

For most users, OBD2 protocol is the primary data collection method. Today, OBD2 communication is predominantly CAN bus-based. Unlike raw CAN data, OBD2 data is “on-request.” Logging OBD2 data involves sending custom CAN frames into the vehicle’s CAN bus, essentially requesting specific data. The car responds if the requested OBD2 PID is supported.

Types of OBD2 devices

The market offers various OBD2 device types:

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

OBD2 Dongles: Small, low-cost, user-friendly Bluetooth OBD2 readers for consumers. They offer 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 or app needed). Data is extracted via USB or SD card for later analysis. 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 capabilities. The CANedge2/CANedge3 log OBD2 data to SD cards and auto-transfer data to servers via WiFi/LTE, ideal 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 enables USB streaming of OBD2 data to PCs via SavvyCAN.

Will the OBD2 logger drain my car battery?

In most cases, no.

Typically, CANedge and similar loggers power on/off with the ignition as the OBD2 port usually uses the IGN power supply. This prevents battery drain when the car is off.

However, in some vehicles, the OBD2 port power supply is directly battery-wired, potentially keeping the CANedge powered on when the car is off. Power drain is minimal (

To check if your logger turns on/off with your vehicle, observe the LEDs after turning off the car for 15-20 minutes. If LEDs are off, the CANedge is off.

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

Can I log GPS data with an OBD2 logger?

While your car might have built-in GPS, accessing this data via OBD2 or proprietary CAN data is often not feasible. 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

[