When an engine will not start, runs badly or throws a warning, the fastest way to the answer is to ask the ECU what it sees. RM-Tuner's Diag pages show the state of every sensor and function at a glance, the fault codes the ECU has stored, and, step by step, how the ECU turns air and mixture target into an injector pulse.
This page explains each one and how to use them to find a fault.
Open Diag → Diagnostics & tools. The pages read the ECU live, so connect to the ECU first.
Three columns show everything at once:
Green is fine, red needs looking at. The picture was taken on a bench ECU with no crank sensor or wideband connected, which is why those read Failure, and why the fuel pump is off with the key on: the ECU primes the pump, then stops it until the engine turns.
Using it. If the engine will not start, look here first: a crank sensor failure, a key-in that reads off, or a fuel pump that never comes on point straight at the cause.
The ECU stores a fault code when it detects a problem: a sensor out of range, a protection acting, a knock limit reached. Each code shows its number, its description and, in Fault detail, what it means. Read again reads the codes from the ECU; Clear fault codes erases them once the cause is fixed.
The ECU records which faults occurred, not when or how often. To find out when, keep Log on protection(s) on for the SD card (see Datalogging), or clear the codes and watch which come back.
Fuel calculation shows, live, every step from the air to the injector pulse:
In the picture the engine is stopped at key-on: the required fuel of 13.79 ms, the 62.8 % VE cell and a 179 % after-start enrichment give a base fuel of 15.85 ms, but the fuel time is 0 because the engine is not turning, so only the dead time (0.73 ms) is shown.
Using it. When the mixture is wrong and you cannot see why, read this page at that operating point. A coolant correction far from 0 points at the coolant sensor or its table; a long-term trim of +15 % means the fuel table is lean there; an after-start enrichment still active long after starting points at its table. See Fuelling settings for how the fuel is calculated.
Hardware test opens a window that drives the ECU's outputs one at a time, with the engine stopped, so you can check each one is wired to the right place and works before the first start:
The test works only while the engine is stopped: the moment the ECU sees any engine speed, it stops the test and closes the window.
Test injectors with the fuel pump off or the fuel rail empty, and ignition outputs with the coils disconnected from the plugs or the plugs grounded: an injector held open floods the cylinder, and a spark with fuel present can ignite it.
An engine needs three things to run: air, fuel at the right moment and a spark at the right moment. Both moments come from the trigger, so most faults are found fastest by checking in this order: the trigger, then the fuel, then the spark. The Diag pages show each one.
| Symptom | Where to look, in order |
|---|---|
| Cranks but does not start | 1. Status: the crank sensor reads Ok and the engine speed shows while cranking (about 150–300 rpm). No speed: the crank sensor, its wiring or the trigger inputs. 2. The Trigger analyzer: a capture while cranking shows whether the ECU finds the gap and the cam, and keeps its sync. 3. The fuel pump runs while cranking, and Fuel calculation shows an injector pulse. 4. Hardware test: fire an ignition output with the plug out and grounded, and check for a spark |
| Starts, then dies | The cranking and after-start fuel (Cold start and warm-up), the idle opening (Idle control), and the fuel pressure |
| Rich or lean at one operating point | Fuel calculation at that point: which correction is far from 0. A large long-term trim means the fuel table is wrong there |
| Misfires under load | The coil dwell, the spark plugs and their gap, and the coils. A capture in the Trigger analyzer under load shows whether the sync is lost at high speed |
| Hesitates or stumbles on the throttle | Acceleration enrichment, and a log of the lambda through the stumble |
| Power cut or a warning while driving | Status → Protections and Fault codes: which protection acted. With Log on protection(s) on, the SD card has the log of the moment (see Datalogging) |
| A sensor reads Failure | The sensor's wiring and its calibration page. A sensor that reads Failure only sometimes is usually a connector or a broken wire that moves with the engine |
Log what you see. An intermittent fault rarely shows itself while you watch. Start a log, drive until it happens, and press Event in the Logger (or Ctrl+Shift+M) at the moment: the mark makes the moment easy to find in the log afterwards.
Status: check the crank sensor, the key-in and the fuel pump. Then look at the fault codes, and at the live engine speed while cranking.
Fix the cause, then press Clear fault codes on the Fault codes page with the ECU connected.
With the engine stopped, the ECU calculates the fuel but does not inject. The fuel time appears once the engine turns.
Contact customer support at [email protected].
Related pages: Datalogging · Live data · Firmware update · Fuelling settings