Skip to content
Miatafy
Search Miatafy

Find something for your Miata.

Good places to start

    Buy ScreenTune
    Menu

    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.

    RequestModuleBytesPublic nameSource
    2213107E02Engine oil temperatureOBDb Mazda MX-5, with 2016, 2020 and 2021 test fixtures
    22091A7E02Throttle position, desired (degrees)OBDb Mazda MX-5, ND-year fixtures
    22093C7E02Throttle position, actual (degrees)OBDb Mazda MX-5, ND-year fixtures
    2203017E02Manifold pressure sensor voltageOBDb Mazda MX-5, ND-year fixtures
    220914, 2209157E02 eachAccelerator pedal sensor voltage 1 and 2OBDb Mazda MX-5
    220917, 2209187E02 eachThrottle sensor voltage 1 and 2OBDb Mazda MX-5
    2216E87E02Alternator dutyOBDb Mazda MX-5
    2216E97E02Alternator voltageOBDb Mazda MX-5
    2261B17201Fuel quantity (liters)OBDb Mazda MX-5, ND-year fixtures
    222A05–222A087201 eachTire pressure, sensors 1–4gitgc’s ND2 investigation (US 2020 and 2021 2.0 L cars)
    222A0A–222A0D7201 eachTire temperature, sensors 1–4OBDb Mazda MX-5, 2020 and 2021 fixtures

    Three notes on this table:

    • Oil temperature. 221310 stands in for Mode 01 PID 5C, 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. 222A09 is rejected, so the pressure and temperature blocks are four identifiers each.
    • Oil pressure. OBDb’s MX-5 set also names 220415 as 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.

    RequestModuleResultPublished for
    22C901, 22C9027207F 22 31Packed tire pressure and temperature in OBDb’s Mazda MX-5 set
    2261D0, 2261D1, 226180, 226185, 22EE11, 22EE12, 22EEFD, 22D936, 22D937, 22404C7207F 22 31Other 720 entries in OBDb’s Mazda sets
    221746, 221410, 2216CD–2216CF, 22A2117E07F 22 31Knock retard, injection pulse width, cam timing and clutch switch in OBDb’s MX-5 set, filtered to 2015 and earlier (NC)
    22280A, 22F4707E07F 22 31Brake pressure and manifold pressure in agronick’s Mazda 3 list
    221E1C, 221E12, 221E24, 221EC7, 221EE47E1No reply after about 0.44 sAutomatic 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.

    RequestBytesIdle readingPublic namePublished scalingCheckConfidence
    2203042701B, 7003, 6FF7Commanded 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 V14.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 VMedium-high
    22030820308, 02F5, 02DDNone found. The Mazda3 manual has a target engine speed item, ARPMDES, with no identifier numberNoneAs 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 speedLive: medium-high. Target idle: low-medium
    22032B100Accelerator pedal position÷ 2 %0 % with the pedal released. The second ND’s author confirmed ÷ 2 by driving and found it duplicates Mode 01 PID 49Medium-high
    22031820185Intake cam timing, actual÷ 16 degrees24.3°. The second ND gives 24.6°Medium
    22031C20188None foundNoneWithin 1 % of 220318, and byte-identical on the second ND while 220318 differs, as a target would be. Possibly desired intake cam timingLow-medium
    22031920000Exhaust cam timing, actual÷ 16 degrees0 on both cars at idleMedium
    22031720000Exhaust 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 idleMedium
    22035F20359Rear oxygen sensor voltage÷ 1024 V0.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 rangeMedium
    220202100Number of stored trouble codesCount0. Also answers on 720Medium
    22038E20A8FEvaporative (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 fit2.70 V; the second ND gives 2.61 VName medium, scaling low-medium
    2203242012AHigh-pressure fuel rail sensor voltage÷ 204.6 V1.46 V on both cars. The Mazda3 manual’s sensor curve does not match, so the ND may use a different sensor rangeLow-medium, unresolved
    22039320207A/C compressor pressure× 0.29 psi150 psi; the second ND gives 163 psi. High for a system at rest. A/C state was not recordedLow-medium; see the note below
    22980020461A/C pressure sensor voltage÷ 1024 V1.09 VLow-medium; see the note below
    22099B20000A/C compressor stateFlag0Low-medium
    2203B920000Cooling fan duty in OBDb’s Mazda sets; “fan speed, desired” in its Ford setsNot recorded0 on both carsLow-medium
    2203BA201E3Ambient air temperature sensor voltage× 0.00489 V2.36 V; the second ND gives 2.23 VLow-medium
    22057D176Ambient temperature (alternate)÷ 2 − 40 °C19 °C, while Mode 01 PID 46 read 26 °CLow-medium
    2211662087DEvaporative purge× 100 ÷ 32768 %6.6 %Low-medium
    2203E82072AOctane adjust ratio. A SkyActiv PID sheet shared by a Mazda3 turbo owner calls it knock control, with the same scaling÷ 163840.11; the second ND gives 0.27. A learned value would differ between cars like thisLow-medium
    2203EC20000Ignition correction, cylinder 1. Sources disagree on the sign÷ 512 degrees0 on both cars at idle. 2203ED–2203EF are rejected, so there is no four-cylinder setLow-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.

    RequestBytesPublished name (Ford definition in OBDb’s Mazda sets unless noted)Why it does not hold
    2203162Intake 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
    2212792Intake air temperature sensor voltage, × 5 ÷ 1023 V00CC 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
    22DA011One 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
    22053B39Catalyst-damaging misfire counts per cylinderThe reply is three 8-byte records and 15 zero bytes. Read by the published layout, a healthy car would show misfires
    2203782Generator control, × 0.00305 %0000. The Mazda3 manual’s field coil duty item reads about 42 % at idle
    2207004Intake temperature fault (1 byte)4 bytes here
    22D9001A/C pressure (2 bytes, Mazda 2)1 byte here
    22DAB67Per-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.

    RequestBytesIdle readingPublic namePublished scalingCheckConfidence
    22DCE120965Ignition-on timer (OBDb CX-30, for a different module)Seconds2405 s, within about 5 s of the elapsed time since startMedium-high
    22D111189Module supply voltage (OBDb, other Mazda modules). Mazda’s cluster PID table for the Mazda6 has a power supply voltage item, VPWR÷ 10 V13.7 V, inside the 13.6–13.9 V the adapter measured in that sessionMedium
    22DD013Not publishedMazda: TOTAL_DIST, total distance (matched by position). OBDb: odometerKilometersEquals Mode 01 PID A6 (odometer, 0.1 km) divided by 10 and truncated. 7E0 returns the same three bytes for 22DD01High
    22DD004Not publishedMazda: 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’sNot published. FORScan prints seconds in the CX-5 logThe 7E0 and 720 readings, taken about 39 hours apart, differ by an amount that fits a shared 0.1 s count to within minutesName medium-high; unit unresolved
    22DD02136Mazda: IC_VPWR, instrument cluster supply voltage (matched by position)÷ 4 V (OBDb, other Mazda modules)13.5 V against 13.6–13.9 V measuredName medium-high, scaling low-medium
    22DD05137Mazda: AAT, ambient temperature (matched by position)− 40 °C (OBDb, other Mazda modules)15 °C. No reference reading from that sessionName medium-high, scaling low-medium
    22DD06107Mazda: PWR_MODE_KEY, power mode key state (matched by position)Value-to-state mapping not published07 with the engine running. No second state was sampledName medium
    22DCE21FF12 V battery state of charge (OBDb CX-30, for a different module)NoneFF reads as “not available”Unknown
    222A00–222A034 eachNot publishedNone foundNoneConstant across four reports, and directly before the pressure identifiers. The same 16 bytes sit inside 22DE00. Likely the four registered tire sensor IDsMedium-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.

    PIDBytesJ1979 name
    00, 20, 40, 60, 80, A04 eachSupported-PID masks
    014Monitor status since codes cleared
    022Freeze-frame trouble code
    032Fuel system status
    041Calculated engine load
    051Engine coolant temperature
    061Short-term fuel trim, bank 1
    071Long-term fuel trim, bank 1
    0B1Intake manifold absolute pressure
    0C2Engine speed
    0D1Vehicle speed
    0E1Timing advance
    0F1Intake air temperature
    102Mass air flow rate
    111Throttle position
    131Oxygen sensors present
    152Oxygen sensor 2 (bank 1): voltage and short-term trim
    1C1OBD standard the vehicle conforms to
    1F2Run time since engine start
    212Distance traveled with the malfunction lamp on
    232Fuel rail gauge pressure
    2E1Commanded evaporative purge
    2F1Fuel tank level
    301Warm-ups since codes cleared
    312Distance traveled since codes cleared
    322Evaporative system vapor pressure
    331Barometric pressure
    344Oxygen sensor 1: equivalence ratio and current (wideband)
    3C2Catalyst temperature, bank 1 sensor 1
    414Monitor status this drive cycle
    422Control module voltage
    432Absolute load value
    442Commanded equivalence ratio
    451Relative throttle position
    461Ambient air temperature
    471Absolute throttle position B
    491Accelerator pedal position D
    4A1Accelerator pedal position E
    4C1Commanded throttle actuator
    511Fuel type
    551Short-term secondary oxygen sensor trim, bank 1
    561Long-term secondary oxygen sensor trim, bank 1
    592Fuel rail absolute pressure
    5E2Engine fuel rate
    621Actual engine torque, percent
    632Engine reference torque
    652Auxiliary inputs and outputs supported
    673Engine coolant temperature, sensors A and B
    687Intake air temperature sensors
    6D11Fuel pressure control system
    8E1Engine friction torque, percent
    9D4Engine fuel rate (mass)
    9E2Engine exhaust flow rate
    A44Transmission actual gear
    A64Odometer

    Six commonly requested PIDs return 7F 01 12 (sub-function not supported), and the support masks leave them clear:

    PIDJ1979 nameWhat answers instead
    0AFuel pressure (gauge)23 and 59 (rail pressure)
    14Oxygen sensor 1 (bank 1), narrowband voltage34 (wideband ratio and current)
    24Oxygen sensor 1: equivalence ratio and voltage34
    5CEngine oil temperature221310
    5DFuel injection timingNone found
    61Driver’s demand torque, percent62 (actual torque)

    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.

    RequestBytesContentMirror
    09004Support mask22F800
    090416, after a count byteCalibration ID, ASCII PG5XEB000PEP6010 on the scanned car22F804
    09064, after a count byteCalibration verification number22F806
    090856, after a count byte28 two-byte in-use performance counters22F808
    090A20, after a count byteECU name, ASCII ECM, -EngineControl22F80A

    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.

    BehaviorEngine computer 7E0Instrument cluster 720
    Mode 01 PIDs per request6, the J1979 maximum on CANNot applicable
    Unsupported PID inside a multi-PID requestLeft out of the reply; the rest are answeredNot applicable
    Service 0x22 identifiers per request3 work. 4 or more need a multi-frame request and were not tested2
    One request over the limitNot testedAny 3-identifier request returns 7F 22 31, even with three identifiers that answer singly
    Median reply time, single request56–60 ms56–60 ms
    Median reply time, batched request60 ms for 3 identifiers61–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.

    Several replies identify the individual car. Strip them before posting a log or contributing to a public dataset.

    RequestModuleWhat it holds
    0902, 22F1907E0VIN by standard definition. Never requested in this scan
    22F106720A 264-byte block of 8-byte tagged records. It contains the VIN as three short ASCII pieces in separate records
    22DE007E0A 128-byte block that includes a 17-character VIN-shaped run
    01A6, 22F4A6, 22DD017E0, 720Odometer
    222A00–222A03, 22DE00720Likely tire sensor IDs
    22DD00, 22DB70–22DB73both, 720Clock-like counters and what may be event timestamps
    0131, 0121, 09087E0Distance 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.

    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.

    RequestModuleBytesContentFord name
    22F1887E024ASCII PG5X-188K2-BVehicle manufacturer ECU software number, which is also the ISO 14229 name
    22F1117E024ASCII PYFB-188K1-, zero paddedECU core assembly number
    22F1127E024ASCII PG5X-18881-BNone found
    22F1137E024ASCII PX43-18881-ECU delivery assembly number
    22F1107E024All zeroSubsystem-specific diagnostic specification part number
    22F1637E0103Diagnostic specification version
    22F1667E0, 7204Decimal-digit nibbles, date- or version-shapedNOS message database #1 version
    22DA9E7E0260A short header, the calibration ID text also returned by 0904, then zero paddingNone found
    22F18872024ASCII NF7A-554K2-AVehicle manufacturer ECU software number
    22F11172024ASCII NF8B-554K1-0ECU core assembly number
    22F11372024ASCII NF8B-55430-0ECU delivery assembly number
    22F1597203Decimal-digit nibbles, version-shapedNOS CAN driver version
    22F15A7203Version-shapedNOS OSEK network management version
    22F15B7203Version-shapedNOS network management junior version
    22F15C7203Version-shapedNOS interaction layer version
    22F15E7203Version-shapedNOS network/transport layer version
    22F15F72010Version-shapedNOS generation tool version
    22F1607203Version-shapedNOS diagnostic version
    22F1617203Version-shapedNOS CAN communication layer version
    22F106720264Tagged records; identity and configurationVehicle configuration parameters
    22D1007E0, 720101Not 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.

    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.

    RequestBytesIdle readingSecond NDNote
    22031420766Varies slightlyPossibly live
    22034E20283Varies slightly
    22035720114Varies
    22036620064Varies by 1A value that sits near 100
    22036C20068Varies
    2203A1154Varies slightly
    2203BD2E425VariesThe name and scaling published for other Mazdas give nonsense on both cars
    220367203A0SameConstant-shaped
    2203A216FSameConstant-shaped
    2203B5213FFSameConstant-shaped
    2203A94C0000000SameFlag-shaped: two top bits set
    2203AC200FFSame
    220389400000000One bit differsFlag word
    22030B100SameZero in three sessions
    22032120000Same
    220326, 2203AB1 each00Same
    22035D, 2203AD4 each00000000Same
    220416400000000No dataFord definition in OBDb: one bit is the low oil pressure switch
    220424213F9No data
    22042F100No data
    22059423FE7No data
    220316, 220378, 22053B2, 2, 39See the table of names that do not fit

    Engine computer 7E0: scattered identifiers

    Section titled “Engine computer 7E0: scattered identifiers”
    RequestBytesIdle readingNote
    220700400800000Flag-shaped
    22091B1FFUnchanged in three sessions, and the same on the second ND. Next to the accelerator and throttle identifiers 220914, 220915, 220917, 220918 and 22091A
    221E04400000000A 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, 22C1A34 each40000000Flag-shaped; the two replies are identical
    224133401000000Flag-shaped
    22202D119
    22C105101
    22C126133
    22D00221FFFA Ford F-150 answers this identifier too
    22D99314F
    22EFC3108
    221279200CCSee the table of names that do not fit
    221167, 221985, 22202F, 22C19E, 22D9002, 1, 1, 1, 1Zero
    222B00, 2261A54 each00000000
    22C1A17Not published
    22D980, 22D9814 eachNot published
    22D983, 22D98432 eachNot publishedCompound records. 22D984 starts with six 8000 words, a common way to store signed values centered on zero
    22FD10, 22FD112 eachNot publishedEqual 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

    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.

    RequestBytesIdle readingSecond NDNote
    22DA01102SameSee the table of names that do not fit
    22DA85, 22DA861 each83, 82Vary slightly
    22DA93112Varies
    22DA992Not publishedVariesSmall integer
    22DAA820184Varies
    22DAB39Not publishedVaries
    22DAB4100Differs (FF)
    22DA9F48Not publishedSame structure, different countsSixteen 3-byte values; car-specific counts
    22DA8B, 22DA8C, 22DA8D4 each00000491, 00000190, 0000FFFFSameConstants
    22DA9B20064SameConstant-shaped
    22DAA0400008000SameConstant
    22DAA6464646464SameConstant: four bytes of 100
    22DAA7, 22DAB81 each00Same
    22DA8E–22DA917 each24, a 4-byte value, a 2-byte valueSame layout and region, one size differsMemory-region descriptors; see below
    22DAB6, 22DB04–22DB077 each24, a 4-byte value, a 2-byte valueNo dataMemory-region descriptors
    22DAB532Not publishedNo dataEight 4-byte values; counter-shaped
    22DA00, 22DA81, 22DA82, 22DA87–22DA8A, 22DB0D1 each00No data
    22DA83, 22DA84, 22DA94, 22DA952 each0000No data
    22DB0A400000000No data
    22DE00128Not publishedNo dataIdentification block, mostly FF padding. The Ford list calls DExx “direct configuration”
    22DE01128Not publishedNo dataFour 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.

    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.

    RequestBytesIdle readingNote
    220202100OBDb names this “number of DTCs” on 7E0
    224002101Status-shaped
    2261B0107Unchanged in two sessions. Next to fuel quantity 2261B1
    224003, 2261B4, 2261C5, 227140, 22DB62, 22DB801 each002261B4 unchanged in two sessions
    222005, 222A244 each00000000
    22DB6020000
    2260054Not published
    22DB614Not publishedSettings-shaped
    22DB7A4Not published
    22DCE02Not published
    22DB70–22DB7310 eachNot publishedFour 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–22DB7910 eachAll zeroUnused slots of the same table
    22DE0044Not publishedFord list: direct configuration. Embeds the sixteen bytes of 222A00–222A03
    22DE015Not publishedFord list: direct configuration. Overlaps bytes 7–11 of 22DE00 except for one bit
    22DE02101Ford list: direct configuration

    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.

    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.