OBD2 explained: What your car's data port really tells you on track

You finish the lap, roll back into the paddock, and pull off the helmet. The lap timer says you were two tenths off your best. But where did those tenths go? Was it the entry to turn three? Did you short-shift onto the back straight? Were you actually flat through the kink, or did you lift without noticing?

GPS and lap times tell you how fast. They don't always tell you why. And the frustrating part is that the answer is usually sitting right there in the car - the engine knows exactly what RPM it was turning, the throttle sensor knows how far down your foot was, the gearbox knows which gear you were really in. The car is already monitoring all of those systems in real time. OBD2 gives you a way to request some of that live data - and in some cases fault snapshots - while you drive.

Start with what the car already does. Your engine is run by a computer, the ECU, and to do its job it continuously reads sensors: crankshaft position, throttle angle, airflow, coolant temperature, oxygen in the exhaust, and dozens more. Some of them it reads very frequently. It's all happening every time you drive, just to keep the engine running.

OBD2 - On-Board Diagnostics, second generation, standardizes access to a core set of emissions-related diagnostic data, and many cars expose useful live channels through that same interface. It was mandated for emissions testing, so a mechanic could plug a scanner into any car and read it regardless of make or model. In Europe, EOBD became mandatory for most petrol passenger cars around 2001 and diesels around 2004, with some category-specific phase-ins; in the US, OBD-II has been required on most light-duty vehicles since the 1996 model year. The important consequence for us: nearly every car on a track day has the same port and answers the same core requests.

That port is the 16-pin OBD-II connector, usually under the dash within reach of the steering column. It provides standardized diagnostic access to the car's communication network - often modern CAN, sometimes older protocols - the same network the ECU uses to talk to the rest of the car.

Here's how a reading actually happens. You send a PID - a Parameter ID, which is just a short request code that means something specific, like "give me engine RPM." The ECU replies with a few raw bytes. Those bytes get decoded into a real number: PID 0C comes back as two bytes that, run through a fixed formula, become 6,400 RPM. Ask for PID 0D and you get vehicle speed; 05 gives coolant temperature; 11 gives throttle position. Each PID is one question with one decoded answer.

The piece in the middle is the adapter. Most consumer adapters speak the ELM327-compatible AT command set, the de facto language for this request-and-reply conversation - paired with a Bluetooth module that carries it to your phone. Your phone fires off PIDs, the adapter relays them to the car's diagnostic interface, the ECU answers, and the adapter passes the bytes back.

The key thing to understand: OBD2 doesn't add any sensors to your car. Every value you log was already being measured by the ECU to run the engine. OBD2 just lets you tap into it - and record it, lap after lap, while you drive.

A diagnostics port designed for emissions checks might not sound like a performance tool. But the same data that helps a mechanic chase a fault is exactly the data that helps a driver chase a tenth. Here's what Vetkuro reads off the port, and why each one matters once the lights go green.

RPM and vehicle speed. The foundation. Engine RPM shows your shift points, are you bouncing off the limiter before you grab the next gear, or short-shifting and falling out of the powerband? Vehicle speed off the ECU gives you a second opinion on your GPS trace, and overlaid on the track map it turns "I think I braked too early" into "I braked 15 metres too early."

Throttle and accelerator pedal position. This is where the driving really shows. How quickly do you get back to full throttle out of a corner? Are you smooth, or are you stabbing at the pedal mid-corner and upsetting the car? Throttle application is one of the clearest separators between a fast lap and a messy one, and it's invisible from the outside - but the car can report pedal or throttle position as a percentage, depending on what the ECU exposes.

Engine load, mass air flow and manifold pressure. How hard the engine is actually working. Useful for understanding power delivery, turbo behaviour, and whether the engine is breathing the way you'd expect down a long straight.

Temperatures - coolant, oil, intake air, catalyst. The reliability layer. A track session is brutal on a road car's cooling, and watching coolant and oil temperature climb across a stint is the difference between backing off in time and parking it on the grass with a blown head gasket. If you've ever wondered whether your car is overheating after three hard laps, this is how you find out - with numbers, not a hunch.

Transmission gear, where available. Some cars expose it directly, some require manufacturer-specific decoding, and some don't provide it at all - but when it's there, your data overlay shows which gear you were in at every point on track instead of you guessing from RPM later.

The session-health stuff - fuel level and trims, control module voltage, barometric pressure. The quiet background channels that tell you whether everything was healthy through the run, and give context to everything else.

Stack those channels next to your position on the track map, and a lap stops being a single number. It becomes a story you can read: brake here, downshift, back to throttle there, short on the exit, temperatures creeping up by lap five. That's the difference between knowing you were slow and understanding why.

t's worth being straight about what OBD2 is, because knowing its edges is how you get the most out of it. OBD2 is not a dedicated, hard-wired motorsport data acquisition system - the kind bolted into a race car that samples every channel at high frequency. It's something more useful for most of us: a real analysis layer you already have access to, in a car you already own, for the price of a small adapter.

Within that, a couple of things are worth understanding.

The protocol is request-and-response - your phone asks for a PID, the car answers, then on to the next. So channel rate is shared across everything you're logging: the more you ask for, the slower each one comes back. The answer is to prioritise, and that's exactly what Vetkuro does - it polls the channels that change fastest and matter most (RPM, speed, throttle and pedal) at the front of the queue, and fits slower-moving values like temperatures around them. You still get a clear, readable trace of your inputs and the engine's response.

Cars differ in what they share. OBD2 standardises the port and the core readings, but manufacturers expose extra channels in their own way. Gear position, for example, is reported differently from one brand to the next, and some cars don't offer it at all. You get whatever your particular ECU makes available - which on most modern cars is plenty.

The way to think about it: OBD2 is the engine-and-inputs layer, and it's at its best paired with high-rate GPS. Vetkuro's high-frequency GNSS nails position and speed around the lap; OBD2 adds what GPS can't see, what your right foot, the engine and the gearbox were doing at each of those points. For the vast majority of track-day drivers, that combination is more than enough to find real, repeatable time. And the best part is it's already in your pocket and under your dash, not in a six-figure garage.

The OBD adapters we support connect over Bluetooth Low Energy to that 16-pin port under your dash. No wiring, no installation - it plugs in, your phone finds it, and you're recording. Under the hood Vetkuro speaks the AT command set, handles the multi-frame responses the ECU sends back, and streams the channels into your session in real time.

And that's the key idea: OBD2 doesn't sit on its own. It's recorded alongside everything else , your GPS trace, your video, and now your heart rate into a single synchronised session. Stop recording, and the whole thing lands on the Vetkuro web platform, where you can scrub through the lap with speed on the trajectory, throttle traces, inferred braking points, sector times and your delta to your best.

This is data that used to be gatekept behind expensive, professionally installed systems. A standard port, an off-the-shelf adapter, and your phone is genuinely enough to start driving with the same kind of feedback the fast guys have always had.

The team at Vgate kindly sent us a set of their adapters to integrate into Vetkuro, and as of the latest release all three are fully supported. Thank you to Vgate for backing what we're building.

The three new additions:

• vLinker FD+ 
• vLinker BM+ 
• iCar Pro 2S

All of them connect over Bluetooth Low Energy, plug straight into your car's OBD-II port, and are detected automatically when you set up a session without manual configuration.

Update the app, plug in your adapter, and take it to your next track day. Then have a look at the data afterwards - I think you'll be surprised how much the car was trying to tell you all along.

• Get the app - App Store · Google Play
• Join the community - Discord

And if something doesn't work with your car or your adapter, tell us. That feedback is exactly how this list of six becomes seven.