ND MX-5 OBD PID List: All 332 Requests That Answer
The ND MX-5’s engine computer and instrument cluster answer 332 OBD requests: 60 standard Mode 01 PIDs, 5 Mode 09 info types, and 267 Mazda-specific service 0x22 identifiers (203 on the engine computer at 7E0, 64 on the instrument cluster at 720).
Only 21 of the 267 Mazda identifiers had been published for the MX-5. The other 246 are new for the MX-5. They include commanded generator voltage, target idle speed, intake cam timing, A/C pressure and an octane adjust ratio on the engine computer, and the odometer, an ignition-on timer and what are likely the four tire sensor IDs on the cluster. Of the 246, 65 mirror standard Mode 01 and Mode 09 data, about 105 match a name published for another Mazda or a Ford, and about 75 have no public name anywhere.
The list covers both modules end to end. It comes from a read-only sweep of every identifier from 0000 to FFFF on a 2.0 L manual car in November 2026, 130,640 results in all, leaving out only a few identity identifiers such as the VIN. Automatics and other model years may answer a slightly different set; How the scan worked has the details.
Cross-checked against a second ND. A public raw scan of a 2025 MX-5 RF (ND3, 2.0 L, a different calibration) covers the engine computer’s 03xx, 09xx and DAxx ranges. Comparing bytes between the two cars separates constants and fixed targets, which are identical on both, from measurements and learned values, which differ.
The names are Ford’s. Most public names for the new engine identifiers come from OBDb signal sets for other Mazda models, and those entries match OBDb’s Ford sets word for word. A Ford F-150 answers 37 of the same engine identifiers. None of them is in OBDb’s Mazda MX-5 set, so each one is tested here: the published scaling is applied to the idle reading and compared with the second ND and with Mazda’s workshop manual for the SkyActiv-G Mazda3, which lists the same parameters without identifier numbers. Each row carries a confidence rating, and the names that fail the test have their own table.
Requests are written the way an ELM327-style adapter sends them: 010C is Mode 01 PID 0C, and 221310 is service 0x22 (read data by identifier) for identifier 1310. Byte counts exclude the positive-response prefix (41 plus the PID, or 62 plus the identifier). For background, see Wikipedia on OBD-II PIDs and UDS, and OBD adapters and apps for the ND for hardware.
Mazda identifiers already published for the MX-5: 21 answer
Section titled “Mazda identifiers already published for the MX-5: 21 answer”These have a public MX-5 source and answer as published. Names and scalings are in the sources linked in each row.
| Request | Module | Bytes | Public name | Source |
|---|---|---|---|---|
221310 | 7E0 | 2 | Engine oil temperature | OBDb Mazda MX-5, with 2016, 2020 and 2021 test fixtures |
22091A | 7E0 | 2 | Throttle position, desired (degrees) | OBDb Mazda MX-5, ND-year fixtures |
22093C | 7E0 | 2 | Throttle position, actual (degrees) | OBDb Mazda MX-5, ND-year fixtures |
220301 | 7E0 | 2 | Manifold pressure sensor voltage | OBDb Mazda MX-5, ND-year fixtures |
220914, 220915 | 7E0 | 2 each | Accelerator pedal sensor voltage 1 and 2 | OBDb Mazda MX-5 |
220917, 220918 | 7E0 | 2 each | Throttle sensor voltage 1 and 2 | OBDb Mazda MX-5 |
2216E8 | 7E0 | 2 | Alternator duty | OBDb Mazda MX-5 |
2216E9 | 7E0 | 2 | Alternator voltage | OBDb Mazda MX-5 |
2261B1 | 720 | 1 | Fuel quantity (liters) | OBDb Mazda MX-5, ND-year fixtures |
222A05–222A08 | 720 | 1 each | Tire pressure, sensors 1–4 | gitgc’s ND2 investigation (US 2020 and 2021 2.0 L cars) |
222A0A–222A0D | 720 | 1 each | Tire temperature, sensors 1–4 | OBDb Mazda MX-5, 2020 and 2021 fixtures |
Three notes on this table:
- Oil temperature.
221310stands in for Mode 01 PID5C, which is rejected. No source says whether the ECU measures the value or models it. - Tire numbering. No source maps sensors 1–4 to wheel positions.
222A09is rejected, so the pressure and temperature blocks are four identifiers each. - Oil pressure. OBDb’s MX-5 set also names
220415as oil pressure. It answers with 2 bytes, but it is left out of the table until a sensor is shown to be behind it.
One more identifier has a public source for another Mazda: 2203DC, desired fuel rail pressure in Pelican’s Mazda 2 parameter reference. It answers with 2 bytes, and in three sessions its value stayed within 1 % of Mode 01 PID 23 (fuel rail pressure) read in the same session: 04B7 against 04B3, 03E8 against 03EF, 03E8 against 03ED.
Published identifiers that do not answer
Section titled “Published identifiers that do not answer”| Request | Module | Result | Published for |
|---|---|---|---|
22C901, 22C902 | 720 | 7F 22 31 | Packed tire pressure and temperature in OBDb’s Mazda MX-5 set |
2261D0, 2261D1, 226180, 226185, 22EE11, 22EE12, 22EEFD, 22D936, 22D937, 22404C | 720 | 7F 22 31 | Other 720 entries in OBDb’s Mazda sets |
221746, 221410, 2216CD–2216CF, 22A211 | 7E0 | 7F 22 31 | Knock retard, injection pulse width, cam timing and clutch switch in OBDb’s MX-5 set, filtered to 2015 and earlier (NC) |
22280A, 22F470 | 7E0 | 7F 22 31 | Brake pressure and manifold pressure in agronick’s Mazda 3 list |
221E1C, 221E12, 221E24, 221EC7, 221EE4 | 7E1 | No reply after about 0.44 s | Automatic transmission values; expected on a manual car |
7F 22 31 is the negative response “request out of range”: the module does not know the identifier.
New engine-computer identifiers that look like live values
Section titled “New engine-computer identifiers that look like live values”All are on 7E0 (replies on 7E8). “Idle reading” is the raw reply with the engine idling at 730–790 rpm, the car stationary and the accelerator untouched. “Check” applies the published scaling to that reading and compares the 2025 RF scan (“second ND”). Confidence levels are defined under How the scan worked.
Names and scalings are the Ford definitions that OBDb’s sets for other Mazdas carry, unless the row names another source.
| Request | Bytes | Idle reading | Public name | Published scaling | Check | Confidence |
|---|---|---|---|---|---|---|
220304 | 2 | 701B, 7003, 6FF7 | Commanded generator voltage. Mazda’s Mazda3 manual has a generator output voltage item, ALTT V, an internal value of about 14 V at idle, with no identifier number | × 0.000488 V | 14.01, 13.99, 13.99 V against a measured supply of 13.6–13.9 V. Changed between sessions. The second ND gives 14.02 V | Medium-high |
220308 | 2 | 0308, 02F5, 02DD | None found. The Mazda3 manual has a target engine speed item, ARPMDES, with no identifier number | None | As integers 776, 757, 733 on a warming engine. Mode 01 rpm in the same three sessions, 8–12 s earlier, was 784, 759, 732. The second ND reads exactly 750, which favors target idle speed over measured speed | Live: medium-high. Target idle: low-medium |
22032B | 1 | 00 | Accelerator pedal position | ÷ 2 % | 0 % with the pedal released. The second ND’s author confirmed ÷ 2 by driving and found it duplicates Mode 01 PID 49 | Medium-high |
220318 | 2 | 0185 | Intake cam timing, actual | ÷ 16 degrees | 24.3°. The second ND gives 24.6° | Medium |
22031C | 2 | 0188 | None found | None | Within 1 % of 220318, and byte-identical on the second ND while 220318 differs, as a target would be. Possibly desired intake cam timing | Low-medium |
220319 | 2 | 0000 | Exhaust cam timing, actual | ÷ 16 degrees | 0 on both cars at idle | Medium |
220317 | 2 | 0000 | Exhaust cam solenoid duty. The Mazda3 manual’s one cam duty item, VT_EX_DUTY, reads about 0 % at idle | × 0.00305 % | 0 on both cars, as the manual expects at idle | Medium |
22035F | 2 | 0359 | Rear oxygen sensor voltage | ÷ 1024 V | 0.84 V. Mode 01 PID 15 gave 0.885 V a minute earlier. The second ND gives 0.07 V; both sit inside a narrowband sensor’s range | Medium |
220202 | 1 | 00 | Number of stored trouble codes | Count | 0. Also answers on 720 | Medium |
22038E | 2 | 0A8F | Evaporative (fuel tank vapor) pressure sensor voltage, a Ford definition in OBDb’s Ford F-150 set and other Ford sets | ÷ 1000 V (Ford). The Mazda 3 entry, ÷ 5.005, does not fit | 2.70 V; the second ND gives 2.61 V | Name medium, scaling low-medium |
220324 | 2 | 012A | High-pressure fuel rail sensor voltage | ÷ 204.6 V | 1.46 V on both cars. The Mazda3 manual’s sensor curve does not match, so the ND may use a different sensor range | Low-medium, unresolved |
220393 | 2 | 0207 | A/C compressor pressure | × 0.29 psi | 150 psi; the second ND gives 163 psi. High for a system at rest. A/C state was not recorded | Low-medium; see the note below |
229800 | 2 | 0461 | A/C pressure sensor voltage | ÷ 1024 V | 1.09 V | Low-medium; see the note below |
22099B | 2 | 0000 | A/C compressor state | Flag | 0 | Low-medium |
2203B9 | 2 | 0000 | Cooling fan duty in OBDb’s Mazda sets; “fan speed, desired” in its Ford sets | Not recorded | 0 on both cars | Low-medium |
2203BA | 2 | 01E3 | Ambient air temperature sensor voltage | × 0.00489 V | 2.36 V; the second ND gives 2.23 V | Low-medium |
22057D | 1 | 76 | Ambient temperature (alternate) | ÷ 2 − 40 °C | 19 °C, while Mode 01 PID 46 read 26 °C | Low-medium |
221166 | 2 | 087D | Evaporative purge | × 100 ÷ 32768 % | 6.6 % | Low-medium |
2203E8 | 2 | 072A | Octane adjust ratio. A SkyActiv PID sheet shared by a Mazda3 turbo owner calls it knock control, with the same scaling | ÷ 16384 | 0.11; the second ND gives 0.27. A learned value would differ between cars like this | Low-medium |
2203EC | 2 | 0000 | Ignition correction, cylinder 1. Sources disagree on the sign | ÷ 512 degrees | 0 on both cars at idle. 2203ED–2203EF are rejected, so there is no four-cylinder set | Low-medium |
220304 and 220308 were read in three sessions and changed between them. The other rows are single idle readings.
A/C pressure. The published scalings for 220393 and 229800 cannot both be right if the ND’s pressure sensor resembles the Mazda3’s. On the Mazda3 manual’s sensor curve, 1.09 V is roughly 97 psi, while 220393 reads 150 psi.
Published names that do not fit
Section titled “Published names that do not fit”| Request | Bytes | Published name (Ford definition in OBDb’s Mazda sets unless noted) | Why it does not hold |
|---|---|---|---|
220316 | 2 | Intake cam solenoid duty, × 0.00305 % | 0CCD (10.0 %) on both cars. An identical reading on two cars suggests a fixed default, and Mazda’s SkyActiv-G manual lists no intake duty item |
221279 | 2 | Intake air temperature sensor voltage, × 5 ÷ 1023 V | 00CC gives 1.0 V. The Mazda3 manual’s sensor curves give 2.2–3.1 V at the 29–30 °C that Mode 01 reported |
22DA01 | 1 | One bit is “oil pressure solenoid valve open” (OBDb Mazda 2) | 02 on both cars. The published bit is clear at idle, when the Mazda3 manual says the solenoid is on |
22053B | 39 | Catalyst-damaging misfire counts per cylinder | The reply is three 8-byte records and 15 zero bytes. Read by the published layout, a healthy car would show misfires |
220378 | 2 | Generator control, × 0.00305 % | 0000. The Mazda3 manual’s field coil duty item reads about 42 % at idle |
220700 | 4 | Intake temperature fault (1 byte) | 4 bytes here |
22D900 | 1 | A/C pressure (2 bytes, Mazda 2) | 1 byte here |
22DAB6 | 7 | Per-cylinder misfire averages (Mazda 2) | The reply has the layout of a memory address and size |
New identifiers on the instrument cluster (720)
Section titled “New identifiers on the instrument cluster (720)”The module at 720 (replies on 728) is the instrument cluster. An MX-5 ND forum thread on tire pressures says so directly, a 2017 Mazda6 owner edits FORScan address 720-04-25 in the instrument cluster module, and OBDb labels 720 as the cluster on Ford and Mazda. Ford uses the same address for its instrument panel cluster in public FORScan sheets for the Ranger and Bronco. Confidence: high.
Mazda’s workshop manual for the Mazda3 and Mazda6 lists exactly five instrument cluster snapshot items: TOTAL_TIME, TOTAL_DIST, IC_VPWR, AAT and PWR_MODE_KEY. The manual gives no identifier numbers. The five are matched to 22DD00, 22DD01, 22DD02, 22DD05 and 22DD06 by position only, in the order the identifiers answer. A FORScan log from a 2012 CX-5 shows the same five item names.
| Request | Bytes | Idle reading | Public name | Published scaling | Check | Confidence |
|---|---|---|---|---|---|---|
22DCE1 | 2 | 0965 | Ignition-on timer (OBDb CX-30, for a different module) | Seconds | 2405 s, within about 5 s of the elapsed time since start | Medium-high |
22D111 | 1 | 89 | Module supply voltage (OBDb, other Mazda modules). Mazda’s cluster PID table for the Mazda6 has a power supply voltage item, VPWR | ÷ 10 V | 13.7 V, inside the 13.6–13.9 V the adapter measured in that session | Medium |
22DD01 | 3 | Not published | Mazda: TOTAL_DIST, total distance (matched by position). OBDb: odometer | Kilometers | Equals Mode 01 PID A6 (odometer, 0.1 km) divided by 10 and truncated. 7E0 returns the same three bytes for 22DD01 | High |
22DD00 | 4 | Not published | Mazda: TOTAL_TIME, cumulative elapsed time since the vehicle was completed (matched by position). 7E0 answers 22DD00 too, and the Mazda3 manual compares the engine computer’s snapshot time with the cluster’s | Not published. FORScan prints seconds in the CX-5 log | The 7E0 and 720 readings, taken about 39 hours apart, differ by an amount that fits a shared 0.1 s count to within minutes | Name medium-high; unit unresolved |
22DD02 | 1 | 36 | Mazda: IC_VPWR, instrument cluster supply voltage (matched by position) | ÷ 4 V (OBDb, other Mazda modules) | 13.5 V against 13.6–13.9 V measured | Name medium-high, scaling low-medium |
22DD05 | 1 | 37 | Mazda: AAT, ambient temperature (matched by position) | − 40 °C (OBDb, other Mazda modules) | 15 °C. No reference reading from that session | Name medium-high, scaling low-medium |
22DD06 | 1 | 07 | Mazda: PWR_MODE_KEY, power mode key state (matched by position) | Value-to-state mapping not published | 07 with the engine running. No second state was sampled | Name medium |
22DCE2 | 1 | FF | 12 V battery state of charge (OBDb CX-30, for a different module) | None | FF reads as “not available” | Unknown |
222A00–222A03 | 4 each | Not published | None found | None | Constant across four reports, and directly before the pressure identifiers. The same 16 bytes sit inside 22DE00. Likely the four registered tire sensor IDs | Medium-high |
Standard Mode 01 PIDs: 60 answer, 6 are rejected
Section titled “Standard Mode 01 PIDs: 60 answer, 6 are rejected”The engine computer’s support masks are 0100 → FE 3F A8 13, 0120 → A0 07 F0 11, 0140 → FE D0 8C 85 and 0160 → 6B 08 00 01. Every PID a mask claims answered. Names are the SAE J1979 names as listed in Wikipedia’s PID table, which also gives the standard formulas.
| PID | Bytes | J1979 name |
|---|---|---|
00, 20, 40, 60, 80, A0 | 4 each | Supported-PID masks |
01 | 4 | Monitor status since codes cleared |
02 | 2 | Freeze-frame trouble code |
03 | 2 | Fuel system status |
04 | 1 | Calculated engine load |
05 | 1 | Engine coolant temperature |
06 | 1 | Short-term fuel trim, bank 1 |
07 | 1 | Long-term fuel trim, bank 1 |
0B | 1 | Intake manifold absolute pressure |
0C | 2 | Engine speed |
0D | 1 | Vehicle speed |
0E | 1 | Timing advance |
0F | 1 | Intake air temperature |
10 | 2 | Mass air flow rate |
11 | 1 | Throttle position |
13 | 1 | Oxygen sensors present |
15 | 2 | Oxygen sensor 2 (bank 1): voltage and short-term trim |
1C | 1 | OBD standard the vehicle conforms to |
1F | 2 | Run time since engine start |
21 | 2 | Distance traveled with the malfunction lamp on |
23 | 2 | Fuel rail gauge pressure |
2E | 1 | Commanded evaporative purge |
2F | 1 | Fuel tank level |
30 | 1 | Warm-ups since codes cleared |
31 | 2 | Distance traveled since codes cleared |
32 | 2 | Evaporative system vapor pressure |
33 | 1 | Barometric pressure |
34 | 4 | Oxygen sensor 1: equivalence ratio and current (wideband) |
3C | 2 | Catalyst temperature, bank 1 sensor 1 |
41 | 4 | Monitor status this drive cycle |
42 | 2 | Control module voltage |
43 | 2 | Absolute load value |
44 | 2 | Commanded equivalence ratio |
45 | 1 | Relative throttle position |
46 | 1 | Ambient air temperature |
47 | 1 | Absolute throttle position B |
49 | 1 | Accelerator pedal position D |
4A | 1 | Accelerator pedal position E |
4C | 1 | Commanded throttle actuator |
51 | 1 | Fuel type |
55 | 1 | Short-term secondary oxygen sensor trim, bank 1 |
56 | 1 | Long-term secondary oxygen sensor trim, bank 1 |
59 | 2 | Fuel rail absolute pressure |
5E | 2 | Engine fuel rate |
62 | 1 | Actual engine torque, percent |
63 | 2 | Engine reference torque |
65 | 2 | Auxiliary inputs and outputs supported |
67 | 3 | Engine coolant temperature, sensors A and B |
68 | 7 | Intake air temperature sensors |
6D | 11 | Fuel pressure control system |
8E | 1 | Engine friction torque, percent |
9D | 4 | Engine fuel rate (mass) |
9E | 2 | Engine exhaust flow rate |
A4 | 4 | Transmission actual gear |
A6 | 4 | Odometer |
Six commonly requested PIDs return 7F 01 12 (sub-function not supported), and the support masks leave them clear:
| PID | J1979 name | What answers instead |
|---|---|---|
0A | Fuel pressure (gauge) | 23 and 59 (rail pressure) |
14 | Oxygen sensor 1 (bank 1), narrowband voltage | 34 (wideband ratio and current) |
24 | Oxygen sensor 1: equivalence ratio and voltage | 34 |
5C | Engine oil temperature | 221310 |
5D | Fuel injection timing | None found |
61 | Driver’s demand torque, percent | 62 (actual torque) |
Mode 01 is mirrored at 22F400 + PID
Section titled “Mode 01 is mirrored at 22F400 + PID”22F4xx answers for exactly the 60 PIDs that answer in Mode 01 and rejects the rest, including the six above. Every reply length matches. 27 of the 60 payloads were byte-identical; the other 33 are values that move, read about 36 minutes apart on a warming engine.
The mirror adds no data. Mode 01 is the cheaper route because the engine computer accepts six PIDs per Mode 01 request and three identifiers per 0x22 request.
Mode 09: five info types answer
Section titled “Mode 09: five info types answer”| Request | Bytes | Content | Mirror |
|---|---|---|---|
0900 | 4 | Support mask | 22F800 |
0904 | 16, after a count byte | Calibration ID, ASCII PG5XEB000PEP6010 on the scanned car | 22F804 |
0906 | 4, after a count byte | Calibration verification number | 22F806 |
0908 | 56, after a count byte | 28 two-byte in-use performance counters | 22F808 |
090A | 20, after a count byte | ECU name, ASCII ECM, -EngineControl | 22F80A |
Each 22F8xx reply equals the Mode 09 reply with the leading item-count byte removed. Info types 03, 05, 07, 09 and 0B are rejected. 0901 and 0902 (the VIN) were never requested, and neither were the other 22F8xx identifiers.
Request limits and timing for tool authors
Section titled “Request limits and timing for tool authors”Measured through an OBDLink MX+ (STN2255 firmware 5.10.3) on the 500 kbit/s diagnostic CAN bus, with the adapter’s ATST64 timeout.
| Behavior | Engine computer 7E0 | Instrument cluster 720 |
|---|---|---|
| Mode 01 PIDs per request | 6, the J1979 maximum on CAN | Not applicable |
| Unsupported PID inside a multi-PID request | Left out of the reply; the rest are answered | Not applicable |
Service 0x22 identifiers per request | 3 work. 4 or more need a multi-frame request and were not tested | 2 |
| One request over the limit | Not tested | Any 3-identifier request returns 7F 22 31, even with three identifiers that answer singly |
| Median reply time, single request | 56–60 ms | 56–60 ms |
| Median reply time, batched request | 60 ms for 3 identifiers | 61–65 ms for 2 identifiers |
Batched negatives on 720. A tool that sends three identifiers to 720 gets “request out of range” for identifiers the module supports. Probe with known-good identifiers before trusting a batched negative.
Throughput. The link carried about 10 requests per second (26,489 requests in 2,629 s in the second session). In recorded drives a reply took about 55 ms, each change of target module between 7E0 and 720 cost another 70–100 ms, and the link delivered 7.8–10.2 requests per second.
Absent modules. Requests to the automatic-transmission address 7E1 end in NO DATA after 0.43–0.45 s on a manual car, so each one costs as much as four or five answered requests.
Negative responses. The scan recorded 130,640 results. Apart from the positives, every 0x22 identifier returned 7F 22 31, with one exception: 22FDF0 on 7E0 returned 7F 22 22 (conditions not correct), so it exists but is locked in the default session.
Identifiers to keep out of shared logs
Section titled “Identifiers to keep out of shared logs”Several replies identify the individual car. Strip them before posting a log or contributing to a public dataset.
| Request | Module | What it holds |
|---|---|---|
0902, 22F190 | 7E0 | VIN by standard definition. Never requested in this scan |
22F106 | 720 | A 264-byte block of 8-byte tagged records. It contains the VIN as three short ASCII pieces in separate records |
22DE00 | 7E0 | A 128-byte block that includes a 17-character VIN-shaped run |
01A6, 22F4A6, 22DD01 | 7E0, 720 | Odometer |
222A00–222A03, 22DE00 | 720 | Likely tire sensor IDs |
22DD00, 22DB70–22DB73 | both, 720 | Clock-like counters and what may be event timestamps |
0131, 0121, 0908 | 7E0 | Distance and usage counters |
Split VIN. A scrubber that looks for 17 consecutive VIN characters does not catch a VIN split across records. Treat the whole reply as identity data.
Identification and part numbers
Section titled “Identification and part numbers”Part numbers and the calibration ID are shared by cars with the same parts. Date-shaped and version-shaped bytes are described by shape only.
“Ford name” is the description in a published list for a Ford telematics unit (module_did_desc.json). The list describes Ford modules, so the names are Ford’s. “NOS” is Ford’s term for the network operating software, the CAN software stack.
| Request | Module | Bytes | Content | Ford name |
|---|---|---|---|---|
22F188 | 7E0 | 24 | ASCII PG5X-188K2-B | Vehicle manufacturer ECU software number, which is also the ISO 14229 name |
22F111 | 7E0 | 24 | ASCII PYFB-188K1-, zero padded | ECU core assembly number |
22F112 | 7E0 | 24 | ASCII PG5X-18881-B | None found |
22F113 | 7E0 | 24 | ASCII PX43-18881- | ECU delivery assembly number |
22F110 | 7E0 | 24 | All zero | Subsystem-specific diagnostic specification part number |
22F163 | 7E0 | 1 | 03 | Diagnostic specification version |
22F166 | 7E0, 720 | 4 | Decimal-digit nibbles, date- or version-shaped | NOS message database #1 version |
22DA9E | 7E0 | 260 | A short header, the calibration ID text also returned by 0904, then zero padding | None found |
22F188 | 720 | 24 | ASCII NF7A-554K2-A | Vehicle manufacturer ECU software number |
22F111 | 720 | 24 | ASCII NF8B-554K1-0 | ECU core assembly number |
22F113 | 720 | 24 | ASCII NF8B-55430-0 | ECU delivery assembly number |
22F159 | 720 | 3 | Decimal-digit nibbles, version-shaped | NOS CAN driver version |
22F15A | 720 | 3 | Version-shaped | NOS OSEK network management version |
22F15B | 720 | 3 | Version-shaped | NOS network management junior version |
22F15C | 720 | 3 | Version-shaped | NOS interaction layer version |
22F15E | 720 | 3 | Version-shaped | NOS network/transport layer version |
22F15F | 720 | 10 | Version-shaped | NOS generation tool version |
22F160 | 720 | 3 | Version-shaped | NOS diagnostic version |
22F161 | 720 | 3 | Version-shaped | NOS CAN communication layer version |
22F106 | 720 | 264 | Tagged records; identity and configuration | Vehicle configuration parameters |
22D100 | 7E0, 720 | 1 | 01 | Not in the list. In common Ford and Mazda usage this is the active diagnostic session, 01 being the default session |
PG5X begins both the software number and the calibration ID, so those belong together.
The long tail: answered, meaning unknown
Section titled “The long tail: answered, meaning unknown”These identifiers return a positive reply and have no public name that fits. An all-zero reply at idle may be a live value that happened to be zero. Car-specific counts and configuration-shaped values are described without their bytes.
“Second ND” compares the 2025 RF scan. “Same” means byte-identical on both cars, which marks a constant or a fixed target. “Varies” means the two cars differ, as a measurement or a learned value would. “No data” means that scan did not list the identifier.
Engine computer 7E0: 03xx–05xx
Section titled “Engine computer 7E0: 03xx–05xx”| Request | Bytes | Idle reading | Second ND | Note |
|---|---|---|---|---|
220314 | 2 | 0766 | Varies slightly | Possibly live |
22034E | 2 | 0283 | Varies slightly | |
220357 | 2 | 0114 | Varies | |
220366 | 2 | 0064 | Varies by 1 | A value that sits near 100 |
22036C | 2 | 0068 | Varies | |
2203A1 | 1 | 54 | Varies slightly | |
2203BD | 2 | E425 | Varies | The name and scaling published for other Mazdas give nonsense on both cars |
220367 | 2 | 03A0 | Same | Constant-shaped |
2203A2 | 1 | 6F | Same | Constant-shaped |
2203B5 | 2 | 13FF | Same | Constant-shaped |
2203A9 | 4 | C0000000 | Same | Flag-shaped: two top bits set |
2203AC | 2 | 00FF | Same | |
220389 | 4 | 00000000 | One bit differs | Flag word |
22030B | 1 | 00 | Same | Zero in three sessions |
220321 | 2 | 0000 | Same | |
220326, 2203AB | 1 each | 00 | Same | |
22035D, 2203AD | 4 each | 00000000 | Same | |
220416 | 4 | 00000000 | No data | Ford definition in OBDb: one bit is the low oil pressure switch |
220424 | 2 | 13F9 | No data | |
22042F | 1 | 00 | No data | |
220594 | 2 | 3FE7 | No data | |
220316, 220378, 22053B | 2, 2, 39 | See the table of names that do not fit |
Engine computer 7E0: scattered identifiers
Section titled “Engine computer 7E0: scattered identifiers”| Request | Bytes | Idle reading | Note |
|---|---|---|---|
220700 | 4 | 00800000 | Flag-shaped |
22091B | 1 | FF | Unchanged in three sessions, and the same on the second ND. Next to the accelerator and throttle identifiers 220914, 220915, 220917, 220918 and 22091A |
221E04 | 4 | 00000000 | A Torque list for the Ford Focus ST (docs/ford_pids.txt) calls 1E04 “In Gear”, with no solved equation. Zero in neutral is consistent, but four bytes is not a one-byte flag. Low confidence |
221E03, 22C1A3 | 4 each | 40000000 | Flag-shaped; the two replies are identical |
224133 | 4 | 01000000 | Flag-shaped |
22202D | 1 | 19 | |
22C105 | 1 | 01 | |
22C126 | 1 | 33 | |
22D002 | 2 | 1FFF | A Ford F-150 answers this identifier too |
22D993 | 1 | 4F | |
22EFC3 | 1 | 08 | |
221279 | 2 | 00CC | See the table of names that do not fit |
221167, 221985, 22202F, 22C19E, 22D900 | 2, 1, 1, 1, 1 | Zero | |
222B00, 2261A5 | 4 each | 00000000 | |
22C1A1 | 7 | Not published | |
22D980, 22D981 | 4 each | Not published | |
22D983, 22D984 | 32 each | Not published | Compound records. 22D984 starts with six 8000 words, a common way to store signed values centered on zero |
22FD10, 22FD11 | 2 each | Not published | Equal the 15th and 16th counters of the 0908 reply in the same report. Two adjacent matches could still be coincidence. A Ford F-150 answers both identifiers too |
Engine computer 7E0: DAxx, DBxx, DExx
Section titled “Engine computer 7E0: DAxx, DBxx, DExx”In OBDb’s sets for other Mazdas, published names in this range cover timing chain elongation, battery internal resistance and misfire totals, none of which answer. The second ND also answers 22DABA, which the scanned car rejects.
| Request | Bytes | Idle reading | Second ND | Note |
|---|---|---|---|---|
22DA01 | 1 | 02 | Same | See the table of names that do not fit |
22DA85, 22DA86 | 1 each | 83, 82 | Vary slightly | |
22DA93 | 1 | 12 | Varies | |
22DA99 | 2 | Not published | Varies | Small integer |
22DAA8 | 2 | 0184 | Varies | |
22DAB3 | 9 | Not published | Varies | |
22DAB4 | 1 | 00 | Differs (FF) | |
22DA9F | 48 | Not published | Same structure, different counts | Sixteen 3-byte values; car-specific counts |
22DA8B, 22DA8C, 22DA8D | 4 each | 00000491, 00000190, 0000FFFF | Same | Constants |
22DA9B | 2 | 0064 | Same | Constant-shaped |
22DAA0 | 4 | 00008000 | Same | Constant |
22DAA6 | 4 | 64646464 | Same | Constant: four bytes of 100 |
22DAA7, 22DAB8 | 1 each | 00 | Same | |
22DA8E–22DA91 | 7 each | 24, a 4-byte value, a 2-byte value | Same layout and region, one size differs | Memory-region descriptors; see below |
22DAB6, 22DB04–22DB07 | 7 each | 24, a 4-byte value, a 2-byte value | No data | Memory-region descriptors |
22DAB5 | 32 | Not published | No data | Eight 4-byte values; counter-shaped |
22DA00, 22DA81, 22DA82, 22DA87–22DA8A, 22DB0D | 1 each | 00 | No data | |
22DA83, 22DA84, 22DA94, 22DA95 | 2 each | 0000 | No data | |
22DB0A | 4 | 00000000 | No data | |
22DE00 | 128 | Not published | No data | Identification block, mostly FF padding. The Ford list calls DExx “direct configuration” |
22DE01 | 128 | Not published | No data | Four bytes, then zeros |
Memory-region descriptors. Nine identifiers return 24, then four bytes, then two bytes. In ISO 14229, 0x24 is the format byte for “4-byte address, 2-byte size” in read-memory requests. Read that way, the values are addresses from 0x40038000 to 0x4003E010 with sizes 0x0060 and 0x1B48, and the first pair is exactly contiguous. The second ND returns the same layout in the same region on a different calibration, which supports the reading. The meaning is still a hypothesis. The service that would use them, 0x23 (read memory by address), was never sent.
Instrument cluster 720
Section titled “Instrument cluster 720”No source names any of these. Mazda’s cluster PID table for the Mazda6 lists items without identifier numbers that could sit behind the status bytes, among them the parking brake switch, the reverse gear switch, the DSC OFF switch and the TPMS set switch.
| Request | Bytes | Idle reading | Note |
|---|---|---|---|
220202 | 1 | 00 | OBDb names this “number of DTCs” on 7E0 |
224002 | 1 | 01 | Status-shaped |
2261B0 | 1 | 07 | Unchanged in two sessions. Next to fuel quantity 2261B1 |
224003, 2261B4, 2261C5, 227140, 22DB62, 22DB80 | 1 each | 00 | 2261B4 unchanged in two sessions |
222005, 222A24 | 4 each | 00000000 | |
22DB60 | 2 | 0000 | |
226005 | 4 | Not published | |
22DB61 | 4 | Not published | Settings-shaped |
22DB7A | 4 | Not published | |
22DCE0 | 2 | Not published | |
22DB70–22DB73 | 10 each | Not published | Four used slots of a ten-slot table. Each starts with a 4-byte value below 22DD00, in descending order, so they could be timestamps of recent events |
22DB74–22DB79 | 10 each | All zero | Unused slots of the same table |
22DE00 | 44 | Not published | Ford list: direct configuration. Embeds the sixteen bytes of 222A00–222A03 |
22DE01 | 5 | Not published | Ford list: direct configuration. Overlaps bytes 7–11 of 22DE00 except for one bit |
22DE02 | 1 | 01 | Ford list: direct configuration |
How the scan worked
Section titled “How the scan worked”The car. A 2.0 L ND MX-5 with the manual transmission, scanned through an OBDLink MX+ in November 2026.
Read-only requests. The scan sent Mode 01 requests, the non-identifying Mode 09 info types, and service 0x22 reads in the default diagnostic session. It sent no session control, security access, write, routine, input/output control, memory read, or trouble-code read or clear request.
Coverage. Every identifier from 0000 to FFFF on 7E0 and on 720, except identity identifiers that were deliberately never requested: F190 (VIN), F18B, F18C, F198–F19D, and F8xx other than the five listed above. Those are absent from the tables because they were skipped, not because they were rejected.
Conditions. Parked, engine idling at 746–790 rpm at session starts, 13.6–13.9 V at the adapter. The sweep took about 93 minutes in two sessions. The engine had been running about a minute when the first session began, so it warmed up during the sweep.
Readings. Each identifier was read once at idle, and identifiers were read minutes or days apart. Repeat readings exist for 220304, 220308, 22030B, 22091B and 22F188 on 7E0, and for 222A00–222A03, 2261B0, 2261B4 and 22F188 on 720. Scaled values were compared with Mode 01 and with the adapter’s supply voltage, not with a separate instrument.
The second ND. The 2025 RF scan is another owner’s idle scan of a different model year and calibration. A value that is byte-identical on both cars is a constant or a fixed target; one that differs is a measurement, a learned value or car-specific data.
Two modules. The sweep covered 7E0 and 720. The car’s other modules are not in this list, and a full sweep should not be assumed harmless on them.
Confidence levels. “High” means bytes from independent requests agree, as with the odometer, or several independent sources agree, as with the module at 720. “Medium-high” means a repeat reading or the second ND supports the row. “Medium” and below mean a name borrowed from another model gives a plausible number at idle. A row moves to “high” once the identifier has been logged next to a known signal while the car is driven or a switch is operated.
Other data on the car. OBD requests are one route to vehicle data. Meters shows 80 values on the factory screen without an OBD adapter, from vehicle data already available to Mazda Connect. For choosing between a phone app and a dedicated logger, see track day data logging.
Sources and licenses
Section titled “Sources and licenses”- OBDb signal sets Mazda-MX-5, Mazda-2, Mazda-3, Mazda-6, Mazda-CX-5, Mazda-CX-30, Mazda, Ford-F-150 and SAEJ1979, read on 2026-11-14 and licensed CC BY-SA 4.0. Public names, request identifiers and published scalings are cited from them; the datasets are not reproduced.
- drewid74/2024-nd3-mazda-obdii, a raw service
0x22range scan of a 2025 MX-5 RF Club (ND3, 2.0 L) at idle, for every “second ND” comparison. No license is stated; individual readings are cited as facts. - Mazda’s workshop manual for the Mazda3 (BM) and Mazda6 (GJ), read on third-party mirrors: PCM inspection, SkyActiv-G, PCM on-board diagnostic test, instrument cluster PID table and instrument cluster on-board diagnostic. The manual is Mazda’s copyright and covers other models. It supplies item names and typical values, with no identifier numbers.
- tonesto7/fordpass-scriptable (GPL-3.0), identifier descriptions for a Ford telematics unit, for the Ford names of the
F1xxandDExxidentifiers. - radiohound/obd-discover (MIT), the identifier numbers a Ford F-150 answered, with no names or values.
- donour/racepi (GPL-2.0), a Torque PID list for the Ford Focus ST, for
221E04. - mazdas247 forum posts: a SkyActiv PID sheet thread from CX-5 and Mazda3 owners, which republishes the same names without per-car testing; a FORScan log from a 2012 CX-5 2.0; and a 2017 Mazda6 FORScan post.
- mx5-nd-forum.de, “TPMS data through OBD / ECU”, about the MX-5 ND, for the module at
720. - gitgc/mx5-miata-nd2-obd-can (MIT) for the tire pressure requests.
- agronick’s Mazda 3 PID list for
22280Aand22F470. - Pelican’s Mazda 2 parameter reference for
2203DC. - python-OBD’s command definitions for Mode 01 reply lengths.
- ISO 14229-1 identifier ranges and SAE J1979 definitions are cited from general knowledge of the standards and were not checked against their text.
Related: OBD adapters and apps for the ND covers hardware, and the FORScan mod list covers module configuration, which is a separate job from reading live data.