Bonk DTC docs
11-01 Strongly inferred

VS sensor no signal

The ECU saw no vehicle-speed signal when it expected one. This is the standard Honda meaning for the code.

Manufacturer
Honda
Platform
PGM-FI (Keihin, Renesas M32R)
Models
CBR600RR
Years
2003-2022
Subsystem
Vehicle speed sensor
FI-light blink
1 long, 1 short
Hex
0x1101
Saw 11-01 as 1 long, 1 short on the FI light? Decode a blink pattern →
All major 11 codes How blink codes work

Strongly inferred. Strongly inferred: the standard Honda meaning is well established, but exactly how this ECU handles it internally is inferred rather than fully confirmed.

What it means

The vehicle speed sensor sends a stream of pulses as the bike moves. This code sets when the ECU expects those pulses (for example while rolling) but does not count any.

Conditions

Detection conditions

  • The ECU expects speed pulses but counts none under conditions that should produce them.

Sets the fault when

  • No speed signal is seen while it is expected.

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

  • Vehicle speed sensor
  • Its signal wiring

Symptoms & likely causes

Possible symptoms

  • FI (check-engine) light on
  • Speed-based features (like a gear indicator) may not work

Likely causes

  • Speed sensor signal wire open or shorted
  • Failed speed sensor
  • Connector fault

Diagnostic guidance

This is about missing pulses, not a voltage range: check the sensor output and wiring for continuity.

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.

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 
// Once a fault is confirmed, remember it and warn the rider.
if (fault_confirmed) {
    store_code(code);      // kept until the codes are cleared
    fi_light = ON;
    if (fault_is_serious)
        limp_home = ON;    // safe defaults so you can ride home
}
Reverse-engineered interpretation · CBR600RR ECU reverse-engineering analysis

Questions about code 11-01

What does Honda code 11-01 mean?
The ECU saw no vehicle-speed signal when it expected one. This is the standard Honda meaning for the code.
Which motorcycles does code 11-01 apply to?
It is documented here for the Honda CBR600RR (2003-2022). Other Honda models may use the same display code with a different meaning, so confirm against your model.
Can I still ride with code 11-01?
It depends on the fault. Code 11-01 relates to the Vehicle speed sensor. If the bike runs poorly or a safety-related system is affected, avoid riding until it is checked. The FI light stays on until the fault is fixed and the codes are cleared.
What should I check first for code 11-01?
This is about missing pulses, not a voltage range: check the sensor output and wiring for continuity.

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

Decode a blink pattern All major 11 codes Full DTC index