Mazda · 2006–2015

MX-5 Miata NC: every channel it can give you

15 channels are already mapped from public vehicle data. 10 more chassis and driver channels are on the car, waiting for GAINS discovery. Plus 25 Hz GPS and a motion sensor in the dongle itself.

CAN (ISO 15765)Stability control: Optional (DSC) from 2012Manual / AutomaticMZR LF 2.0 I4
25channels
15 Data stream
10 To discover
6 Built into the dongle
OBD-II portCAN (ISO 15765)Fast, data stream capable
Internal CAN busYesWhere the chassis modules talk
GatewayNone: data stream at the portBetween the car's bus and the port
Stability control · ABSOptional (DSC) from 2012ABS: Standard

Channels

Every channel the NC is expected to give, by group. Filter by how it arrives.

Driver inputs

Steering angle Data stream
Accelerator pedal Data stream
Throttle position Data stream
Brake pressure Data stream
Brake pedal switch Data stream
Clutch pedal Data stream
Gear To discovergearbox

Wheels and chassis

Wheel speed, front left Data stream
Wheel speed, front right Data stream
Wheel speed, rear left Data stream
Wheel speed, rear right Data stream
Vehicle speed Data stream
Yaw rate To discoverstability control (DSC) · if fitted
Lateral g To discoverstability control (DSC) · if fitted
Longitudinal g To discoverstability control (DSC) · if fitted

Engine

Engine RPM Data stream
Intake air temperature Data stream
Fuel level Data stream

Temperatures and pressures

Oil temperature To discoverengine (if the car measures it) · if fitted
Oil pressure To discoverengine (if the car measures it) · if fitted
Coolant temperature Data stream
Gearbox temperature To discoverautomatic / dual-clutch gearbox · if fitted

Stability systems

ABS active To discoverABS
Traction control active To discoverstability control (DSC) · if fitted
Stability control active To discoverstability control (DSC) · if fitted

Built into the dongle, on every car

GPS speed and position 25 Hz
Lap, sector and delta times computed
Lateral and longitudinal g motion sensor
Yaw rate motion sensor
Heading and altitude GPS
Combined g (friction circle) computed

How the data gets out

Where the NC's sensors live and how GAINS reaches them.

Car's internal CAN busEngineDSCSteeringDashOBD-II · CANTelemetry Dongle Pro plugs into the OBD-II port

Listen at the OBD-II port

The car's own data stream reaches the OBD-II port, so discovery only listens: it matches each value to your steering, pedals, GPS and motion.

Telemetry Dongle Pro

Discovery on your MX-5 Miata

The 10 channels marked “To discover” are learned once, from your car, then added for every NC owner.

  1. Plug in and identify

    The dongle finds the bus speed by listening only, reads the VIN and matches the car's data pattern to our database.

    about 1 min
  2. Guided steps, parked

    The app walks you through each control for a few seconds: wheel lock to lock, brake light then firm, throttle (engine off), clutch, every gear, handbrake, stability-control button. The dongle records what changes on the car's data stream.

    about 5 min
  3. Module read

    With the car parked, the dongle asks each module (ABS, gearbox, body) which values it can report. Read-only requests: nothing is written or changed.

    about 5–10 min, automatic
  4. Short drive

    A normal drive with a few stops, steady speeds and turns. The dongle matches unknown values against its 25 Hz GPS and motion sensor to find wheel speeds, yaw rate and g-forces.

    10–15 min
  5. Results

    Matched channels appear in the app. Anything that needs a closer look is checked by us and added later; you get a notification, and every owner of the same car gets the channel too.

    most right after the drive

First time: about 25–30 minutes, once per car. Times are estimates until measured on real cars. Discovery only listens and reads: it never writes to the car, clears codes or bypasses security.

Published CAN IDs

Community definitions for the NC: expected values, not yet confirmed by our own logs.

Show 17 signals
ChannelCAN IDStart bit · lengthByte orderScale · offsetUnit
Steering angle0x8123 · 16 (signed)Motorola (BE)1 · 0deg
Brake pressure0x857 · 16 (signed)Motorola (BE)1 · 0raw
Engine RPM0x2017 · 16Motorola (BE)0.25 · 0rpm
Vehicle speed0x20139 · 16Motorola (BE)0.01 · -100kph
Accelerator pedal0x20155 · 8Motorola (BE)0.5 · 0%
Throttle position0x20063 · 8Motorola (BE)0.392157 · 0%
Brake pedal switch0x20048 · 1Intel (LE)1 · 0bool
Clutch pedal0x2319 · 1Intel (LE)1 · 0bool
Coolant temperature0x24015 · 8Motorola (BE)1 · -40degC
Intake air temperature0x24039 · 8Motorola (BE)1 · -40degC
engine load0x2407 · 8Motorola (BE)0.392157 · 0%
Coolant temperature0x4207 · 8Motorola (BE)1 · -40Cel
Fuel level0x4307 · 8Motorola (BE)0.392156 · 0%
Wheel speed, front left0x4B07 · 16Motorola (BE)0.01 · -100kph
Wheel speed, front right0x4B023 · 16Motorola (BE)0.01 · -100kph
Wheel speed, rear left0x4B039 · 16Motorola (BE)0.01 · -100kph
Wheel speed, rear right0x4B055 · 16Motorola (BE)0.01 · -100kph

Full details and sources: Mazda MX-5 Miata data by year.

FAQ

Can I log steering angle and brake pressure on a MX-5 Miata NC through the OBD-II port?

Yes, expected on the data stream. A standard OBD2 scan tool won't show them because they aren't standard OBD2 values.

What OBD-II protocol does the MX-5 Miata NC use?

CAN (ISO 15765). Its engine, stability and dash modules also share an internal CAN bus.

How long does discovery take on a NC?

The first time, about 25–30 minutes, once per car (estimate): guided steps while parked, a read-only module check and a short drive. After that the dongle recognises the car when you plug in.

Channel lists combine public vehicle data from the open-source community with the equipment this generation is known to carry. “Expected” and “To discover” channels are not yet confirmed by our own logs, and equipment varies by market, trim and year. Vehicle names identify the cars only; GAINS is not affiliated with Mazda. Specifications are pre-release and may change before launch.