hexandboost

home / articles / custom fault codes on a factory ecu

Build series · Diagnostics

Giving new hardware real fault codes on a factory Honda ECU

When you add a turbo to a car that never had one, the computer has no idea the new parts exist. If a boost sensor fails or the wastegate stops answering, nothing tells the driver. I wanted my additions to be diagnosed the way Honda diagnoses its own parts.

The gap nobody talks about

A factory car watches every sensor it depends on. Unplug one and within seconds the check-engine lamp is on, a code is stored, and the engine has switched to a safe fallback.

A modified car usually loses that. The new boost sensor, the wastegate, the controller driving it: none of them existed when the ECU's software was written, so none of them are monitored. The first sign of a problem is the car behaving badly.

On my turbo Civic Rebirth the non-turbo ECU had no boost or wastegate codes at all. So I added them.

Four new codes, using standard numbers

I used the industry-standard code numbers for each fault, so that any workshop's scan tool describes the problem correctly:

  • P0045, boost control circuit. The wastegate controller has stopped talking to the ECU, or never started after key-on.
  • P2563, boost control position. The wastegate is not moving when commanded, or its position sensor is giving a bad reading.
  • P0236, boost pressure sensor. The boost sensor is out of range or implausible.
  • P0234, overboost. Reserved and wired in, but not active with the current controller firmware.

These are not messages on a laptop. They are stored by the factory ECU through the same process Honda uses to confirm and remember its own faults.

How a fault travels

My wastegate controller reports its health to the ECU fifty times a second. If it flags a problem, or simply goes silent, code I added inside the ECU watches for the fault to persist for about a second before believing it, and for several seconds of health before forgiving it. That stops a single glitch from lighting the dash.

The ECU also checks its own boost sensor for sense. With the engine stopped, the boost sensor and the barometric sensor are measuring the same air, so they must agree. When I unplugged the boost sensor to test this, it floated at 73 kPa against 101 kPa of real atmosphere, which is exactly the kind of lie the check exists to catch.

What the driver sees

The check-engine lamp comes on, within about a second of key-on for most of these faults, before the engine is even started. After three healthy starts the lamp goes out by itself, and the code stays in memory as history, just as a factory code would.

Reading the code without a scan tool

A lamp tells you something is wrong. I wanted the car to say what.

With the ignition on and the engine off, hold CANCEL on the cruise stalk for three seconds.

  • On the tachometer. The first version, on the car from 12 November 2026, spelled each code with the needle: one digit at a time, the needle pointing at that many thousand rpm. My first attempt moved too fast to read. The needle "just wandered around". I slowed it to two seconds per digit and added a sweep between codes.
  • On the i-MID screen. From 13 November the code appears on the car's own display, and SET and RES step through the stored codes. Getting the screen to refresh for each code took its own round of work, because that display only redraws at certain moments.
  • Clearing. Press MAIN three times within two seconds. The tachometer makes one full sweep to confirm. Clearing codes this way does not wipe what the engine has learned.

In my test video the needle reads P0113 and P0102 and a scan tool shows the same two codes. After clearing from the stalk, the scan tool reports none.

Proof it works on the real thing

I tested by unplugging sensors on the car. Pulling the manifold pressure sensor put its code on the needle and on the i-MID. Pulling the boost sensor set the new codes with the lamp on.

What is not right yet

  • The place I chose to store P0045 is also read by one of Honda's own summary codes, so every P0045 currently brings a P0607 with it. The correction is built and waits for the next flash.
  • One of the new codes showed on the car but did not appear on my scan tool on the first try, and I have not yet confirmed how every brand of tool labels them.
  • The overboost code is in place but cannot fire until the controller firmware that reports it is confirmed on the car.

Why bother

Because this is the difference between a car with parts added and a car that was engineered. If my wastegate fails on a customer's car in two years, I want any mechanic with a basic scan tool to plug in and read "boost control circuit", and I want the engine to have already protected itself. The driver's side of this is covered in fault codes on the dash, no scan tool needed.

By Haris, Hex and Boost.

Have a car the usual tools cannot touch?

Tell me the car, the engine, the gearbox and what you want it to do. I reply to every serious enquiry.