A PID, or Parameter ID, is a standardized code that your car’s computer uses to report specific pieces of engine and vehicle data. When you plug a scan tool into the diagnostic port under your dashboard, PIDs are the language it speaks to pull up live readings like engine speed, coolant temperature, vehicle speed, and dozens of other measurements. Every car sold in the U.S. since 1996 uses the OBD-II diagnostic system, and PIDs are the backbone of how that system communicates.
How PIDs Work
Think of a PID as a specific question you ask your car’s engine control unit (ECU). Each PID has a hexadecimal code number, and when a scan tool sends that code to the ECU, the computer responds with the corresponding data. PID 0C, for example, asks for engine RPM. PID 0D asks for vehicle speed. PID 05 requests coolant temperature. The exchange happens in milliseconds, and most scan tools cycle through multiple PIDs several times per second to give you a real-time dashboard of what’s happening inside your engine.
The raw data comes back as a hexadecimal string, which is essentially a compact number format computers prefer. Your scan tool or app automatically converts that into something readable: degrees, RPM, miles per hour, or percentages. You never see the raw hex unless you’re doing something advanced. The conversion follows standardized formulas defined by the SAE (Society of Automotive Engineers), so a PID for coolant temperature returns the same format whether you’re driving a Ford or a Toyota.
Standard vs. Manufacturer-Specific PIDs
OBD-II defines a set of standard PIDs that every compliant vehicle must support. These cover the basics: engine load, coolant temperature, fuel system status, intake air temperature, throttle position, and oxygen sensor readings. Any generic scan tool can read these from any OBD-II vehicle.
Beyond the standard set, manufacturers add their own proprietary PIDs for data specific to their systems, like transmission fluid temperature, turbo boost pressure, or battery state in hybrids. These manufacturer-specific PIDs aren’t publicly documented in most cases, which is why professional-grade tools from companies like Snap-on or software like Forscan can read data that a basic code reader can’t. Some hobbyists and mechanics actively work to decode these custom PIDs for popular vehicle platforms.
Common PIDs and What They Tell You
The most frequently used PIDs fall under Mode 01, which is the real-time data mode. Here are the ones you’ll encounter most often:
- Engine RPM (PID 0C): How fast the engine is spinning, reported in revolutions per minute.
- Vehicle Speed (PID 0D): Your speed in kilometers per hour (scan tools typically convert to mph for you).
- Coolant Temperature (PID 05): The temperature of your engine coolant, useful for spotting overheating or a stuck thermostat.
- Calculated Engine Load (PID 04): A percentage showing how hard the engine is working relative to its maximum capacity.
- Throttle Position (PID 11): How far open the throttle is, expressed as a percentage.
- Intake Air Temperature (PID 0F): The temperature of air entering the engine, which affects fuel mixture calculations.
- Mass Air Flow Rate (PID 10): How much air is flowing into the engine, reported in grams per second or pounds per minute depending on your tool’s settings.
- Short-Term Fuel Trim (PID 06): Real-time adjustments the ECU is making to the fuel mixture, shown as a percentage above or below the baseline.
- Long-Term Fuel Trim (PID 07): The average fuel mixture adjustment over time, which reveals ongoing trends rather than momentary corrections.
Diagnostic Modes Beyond Live Data
PIDs are organized into diagnostic modes, each serving a different purpose. Mode 01 is live data, the one most people use. Mode 02 pulls “freeze frame” data, which is a snapshot of what every sensor was reading at the exact moment a trouble code was triggered. This is enormously useful for diagnosing intermittent problems, because it shows you conditions like engine speed, coolant temp, and load at the precise instant something went wrong.
Mode 03 retrieves stored diagnostic trouble codes (DTCs), which are the codes behind your check engine light. Mode 09 provides vehicle identification information like your VIN. There are additional modes for clearing codes, requesting oxygen sensor test results, and running component tests, but Modes 01 through 03 cover what most DIY users need.
How to Access PIDs
The most common way to read PIDs is with an ELM327-based adapter, a small device (usually $15 to $50) that plugs into your car’s OBD-II port, located under the dashboard near the steering column. These adapters connect to your phone or laptop via Bluetooth, Wi-Fi, or USB. Apps like Torque (Android), OBD Fusion (iOS), or desktop software like Forscan handle the communication and display the data in gauges, graphs, or tables.
When you first connect, the adapter queries your ECU to find out which PIDs your vehicle supports. Not every car supports every standard PID. The ECU responds with a binary string where each bit represents a specific PID, flagged as either active or inactive. Your app reads this response and only shows you the PIDs your car actually reports. From there, you can monitor live data, log it for later review, or check for trouble codes.
Professional scan tools from brands like Autel or Snap-on do the same thing but add access to manufacturer-specific PIDs, bidirectional controls (like commanding a component to activate for testing), and deeper module access beyond the engine. The underlying PID communication works the same way.
Using PIDs for Troubleshooting
Fuel trim PIDs are among the most powerful diagnostic tools available through a basic scan tool. Short-term fuel trim shows what the ECU is doing right now to adjust the air-fuel mixture. If it’s consistently adding fuel (a positive percentage), the engine is running lean, which could point to a vacuum leak, a weak fuel pump, or a dirty mass air flow sensor. If it’s pulling fuel (a negative percentage), the engine is running rich, possibly from a leaking fuel injector or a faulty oxygen sensor.
Long-term fuel trim reveals the same trend over time. If long-term trim has drifted 15% or more in either direction, something is significantly off and a trouble code will likely follow. By catching these shifts early through PID monitoring, you can identify problems before they trigger a check engine light or cause further damage.
Coolant temperature and intake air temperature PIDs help verify sensor accuracy. If your coolant temperature PID reads 190°F while driving but your temperature gauge shows normal, the sensor and gauge agree. If the PID shows an implausible number, like -40°F on a warm day, you’ve likely found a failed sensor. Some scan tools display temperature in Fahrenheit or Celsius and let you toggle between the two, which is worth checking so you don’t misread a value.
The Shift to SAE J1979-2
The original PID communication standard, SAE J1979, has been the foundation of OBD-II diagnostics for decades. Newer vehicles are transitioning to an updated protocol called SAE J1979-2, which expands the data available through the diagnostic port and changes how some of the communication is structured. California’s Bureau of Automotive Repair implemented regulations supporting the updated protocol as of July 2024, and inspection systems are being updated to handle vehicles using the newer standard.
For most car owners, this transition is invisible. Your scan tool or app will need a firmware or software update to communicate with J1979-2 vehicles, and most major tool manufacturers are already rolling those out. The core concept remains identical: PIDs are still standardized codes that request specific data from the vehicle’s computer. The newer standard simply adds more of them and uses a more modern communication format.