Developers and installers · Free decoder

OBD-II PID Decoder & J1962 Pin Finder

Paste the bytes an OBD-II answer gives you and read the value. Build the request for any common PID. Find which J1962 pins carry power, ground and the bus before you touch the connector.

Runs in your browserFormulas with their sourceNot every vehicle answers

A full answer with 41 and the PID sets the PID by itself.

hex

A CAN line such as 7E8 04 41 0C 1A F8, the answer 41 0C 1A F8, or only the data bytes 1A F8.

Bytes are read as hexadecimal on this page.

Decoded valueService 01

Keep the decode with your integration notes

A report with the decoded value, the formula, the request message and the pin map.

Decoder report

Attach the decode to your integration file

  • Value, unit and formula for the PID
  • Request message and expected answer
  • J1962 pins for your bus and voltage
  • Every value you entered
Before you plug anything in

Check four pins with a multimeter

A quick meter check tells you whether the socket is standard and alive. It takes two minutes.

  1. Pin 16 to pin 4: battery

    With the key off you should read the battery voltage. It stays live when the vehicle is parked.

    Battery +
  2. Pins 4 and 5: ground

    Chassis ground and signal ground. Check both against the battery negative.

    Ground
  3. Pins 6 and 14: CAN high and low

    At rest both sit near the middle of the transceiver supply, typically about 2.5 V. A dead bus reads 0 V.

    CAN
  4. Ignition: not on J1962

    No standard pin carries ignition. Find an ignition source in the vehicle wiring instead.

    Ignition
Heavy trucks speak J1939

Many trucks and buses do not answer service 01 at all. Their engine data comes as J1939 messages. Use the J1939 decoder.

What is an OBD-II PID?

A PID is a number that asks the engine control unit for one value. In service 01 the ECU answers with 41, the PID and one to four data bytes, named A, B, C and D. A formula turns the bytes into a value.

Common PIDs and their formulas
PIDFormulaUnit
04 · Calculated engine load100 x A / 255%
05 · Engine coolant temperatureA - 40°C
0C · Engine speed(256 x A + B) / 4rpm
0D · Vehicle speedAkm/h
10 · Mass air flow rate(256 x A + B) / 100g/s
2F · Fuel tank level input100 x A / 255%
42 · Control module voltage(256 x A + B) / 1000V
5E · Engine fuel rate(256 x A + B) / 20L/h
A6 · Odometer(A x 2^24 + B x 2^16 + C x 2^8 + D) / 10km

How do you read a CAN answer?

On CAN, the answer comes from ID 7E8 for the engine. The first data byte is the length, then 41, the PID and the data. The rest is padding.

7E8 04 41 0C 1A F8 AA AA AA A = 0x1A = 26, B = 0xF8 = 248 rpm = (256 x 26 + 248) / 4 = 6904 / 41726 rpm

How is a request built?

A single-frame request has the length 02, the service 01 and the PID, padded to 8 bytes. Sent to 7DF, every ECU that supports the PID answers.

7DF 02 01 0D CC CC CC CC CC answer: 7E8 03 41 0D 3C ... -> 0x3C = 60 km/h

Which J1962 pins matter?

J1962 pins
PinRole
16Battery positive, 12 V on type A, 24 V on type B
4Chassis ground
5Signal ground
6CAN high, ISO 15765-4
14CAN low, ISO 15765-4
7K-line, ISO 9141-2 and ISO 14230-4
15L-line, ISO 9141-2 and ISO 14230-4
2SAE J1850 bus positive
10SAE J1850 PWM bus negative
1, 3, 8, 9, 11, 12, 13Manufacturer discretion

Assumptions and limits

  • Only well-documented service 01 PIDs are included. Manufacturer PIDs and other services are not decoded.
  • Not every vehicle answers every PID. Ask PID 00 first to see what the ECU supports.
  • Multi-frame answers, such as the VIN, are not reassembled here.
  • Pin roles are from the public summary of the standard. Your vehicle wiring diagram has the final word.
  • The page does not describe what any Tracom model reads from the OBD port.

Sources

Last checked 3 November 2026. The official SAE pages confirm what each standard covers. The formulas and pin roles sit in the paid text, so the first two links are secondary summaries: verify against the current official text before you rely on a figure.

Related Tracom solution

Engine data into the tracker, done the right way

Tracom designs tracking hardware for fleets of cars, trucks and machines. Ask which vehicle data inputs and accessories your device model supports before you plan an OBD or CAN connection.

  • Advanced configuration files. Keep the same data settings on every vehicle.
  • Second-by-second data. Record how the vehicle moves in fine detail.
  • SCMS portal. Manage device settings in one place.
  • Over-the-air update. Bring new firmware to devices in the field.
Questions

Questions about OBD-II PIDs and pins

Connecting engine data to a tracker? Contact Tracom.

Does every vehicle answer every PID?

No. The standard lists the PIDs, the vehicle maker chooses which ones the ECU supports. Request PID 00 to get the list for PIDs 01 to 20.

Can I power a tracker from pin 16?

Not necessarily. Pin 16 is battery positive and stays live when parked, but it shares a fuse with other circuits and a plug-in connection is easy to pull out. For a permanent install, follow the device installation guide.

Why does my truck not answer on 7DF?

Because many heavy vehicles use J1939 at 250 or 500 kbit/s instead of service 01. Look for J1939 messages on the bus instead.

Which padding byte should I use?

Any of them. The ECU ignores the padding. CC, 55, AA and 00 are all common in scan tools.

Is the data I paste sent anywhere?

No. The decoding runs in your browser. Your inputs reach our server only if you ask for the emailed report, and are then kept for up to 45 days.

What is Tracom's role here?

Tracom makes tracking hardware. This decoder explains the public OBD-II standard. It does not say what a given Tracom model reads, and it does not replace the vehicle maker's documents.

Related tools and templates

More vehicle data tools

Get the report

Enter your details and we will email you the file.

Use your real name so the file arrives addressed to you. Don't worry, we won't flood you with emails or calls.

Scroll to Top