01-02 Confirmed

MAP sensor circuit high voltage

The manifold pressure sensor read too high, as if the circuit is open or shorted to the reference voltage, and stayed that way long enough to count.

Manufacturer: Honda
Platform: PGM-FI (Keihin, Renesas M32R)
Models: CBR600RR
Years: 2003-2022
Subsystem: MAP (manifold pressure) sensor
Hex: 0x0102

Confirmed. Confirmed: how the ECU detects this was traced in the firmware and matches the standard Honda meaning of the code.

What it means

Same MAP sensor check as 01-01, but here the signal sat above the high limit. An open signal or ground wire floats the reading high, so this is reported as a high-voltage circuit fault.

Conditions

Detection conditions

The ECU reads the MAP sensor and compares it against a normal range.

Sets the fault when

The signal stays above the high limit long enough to rule out brief noise.

Clears the fault when

Fix the underlying problem, then clear the stored codes with a diagnostic tool or the manufacturer’s reset procedure. If the fault is still present, the code returns the next time the ECU detects it.

Parts involved

Manifold absolute pressure (MAP) sensor
Its signal, ground, and reference wiring

Symptoms & likely causes

Possible symptoms

FI (check-engine) light on
Incorrect fuelling and poor driveability

Likely causes

Open MAP signal or ground wire (reading floats high)
MAP signal shorted to the reference voltage
Failed MAP sensor

Diagnostic guidance

A high-voltage fault usually means an open signal or ground, or a short to the reference. Confirm the reference and ground before replacing the sensor.

How the ECU decides

A simplified view of the logic behind this code: a short C snippet with a plain-English summary. It shows the real decision the ECU makes without the low-level detail.

The ECU checks each sensor against a normal high and a normal low value. A brief spike is ignored; only a reading that stays out of range long enough counts as a real fault. Too low sets the "-01" (low) code, too high sets the "-02" (high) code.

C How an out-of-range sensor sets a code

1// A sensor reading outside its normal band, held long enough to be real.
2if (reading < low_limit || reading > high_limit) {
3    bad_count++;               // ignore brief electrical noise
4    if (bad_count >= limit)
5        set_fault();           // low -> "-01", high -> "-02"
6} else {
7    bad_count = 0;             // back in range: no fault
8}

Reverse-engineered interpretation · CBR600RR ECU reverse-engineering analysis

When the ECU confirms a fault, it saves the code and turns on the FI (check-engine) light. For a serious fault it also runs the engine on safe default values (limp-home) so you can still ride, with the light on.

C How a confirmed fault is stored

1// Once a fault is confirmed, remember it and warn the rider.
2if (fault_confirmed) {
3    store_code(code);      // kept until the codes are cleared
4    fi_light = ON;
5    if (fault_is_serious)
6        limp_home = ON;    // safe defaults so you can ride home
7}

Reverse-engineered interpretation · CBR600RR ECU reverse-engineering analysis

Related codes

Sources

Every technical claim on this page traces to the research below. Source labels are sanitized; no local research paths are exposed.

firmware

2005-2006 Honda CBR600RR ECU firmware

Factory PGM-FI firmware for the 2005-2006 CBR600RR. Primary source of truth.
analysis

Firmware fault-code table extraction

Reads the list of codes the ECU can store directly out of each firmware.
reference

HondaECU project (open-source Honda ECU tool)

Community reference mapping Honda PGM-FI codes to their meanings.
analysis

CBR600RR ECU reverse-engineering analysis

Independent analysis of how the ECU detects, stores, and reports faults.

Content version 1.0.0 · last reviewed 2026-07-14

All major 01 codes Full DTC index