In short. The engine control module on an electronic diesel generator reads a dozen or more sensors, sets fuel quantity and timing for every stroke, governs speed, protects the engine and reports to the genset controller over a J1939 CAN link. A fault code tells you what the module measured, not what is broken; the sensor, wiring or supply may be at fault instead. Separating those in a fixed order is the whole of good ECM diagnosis.
What the module actually controls
On a mechanically governed engine the governor, the fuel pump and a handful of switches do everything. On an electronic engine those functions move into software. The module controls injection quantity and timing, rail pressure through the pump’s metering valve, boost on engines with a wastegate or variable geometry turbocharger, and exhaust gas recirculation and aftertreatment dosing on CPCB IV+ sets. It governs speed, normally isochronously at 1,500 rpm for 50 Hz, and applies the manufacturer’s protection map of warnings, derates and shutdowns. Its relationship with the fuel system is explained under common-rail fuel systems.
The genset controller in the panel does not replace the engine module. It starts and stops the engine, monitors the alternator, handles mains sensing and transfer, and reads engine data from the module over CAN. On a retrofit where an electronic engine was fitted to an older panel, the controller may still read its own senders, and the two can disagree. Knowing which device is reporting a value is the first question when a reading looks wrong.
The sensors and how they fail
| Sensor | Type and typical signal | What the module does if it fails | Typical failure signature |
|---|---|---|---|
| Crankshaft speed | Variable reluctance or Hall effect, pulses per tooth | Falls back to the camshaft sensor; no start if both are lost | Intermittent stall, cranks without starting, erratic rpm at idle |
| Camshaft position | Hall effect, one or few pulses per revolution | Runs on crank sensor with slower start | Long cranking, occasional misfire |
| Coolant temperature | Thermistor, resistance falls as temperature rises | Assumes a default and may disable protection | Reading stuck at an extreme, false high-temperature trip |
| Oil pressure | Piezoresistive, 0.5 to 4.5 V on a 5 V reference | Warning and possible shutdown by design | Reading at 0 or full scale, or drifting with engine temperature |
| Rail pressure | Strain gauge, 0.5 to 4.5 V | Limits fuelling, may shut down | Pressure codes with no smoke or power complaint |
| Boost pressure and air temperature | Combined pressure and thermistor | Limits fuel to avoid smoke | Black smoke under load, derate on load acceptance |
| Water in fuel | Conductivity probe in the separator bowl | Warning, then derate on some engines | Alarm that clears after draining the bowl |
| Exhaust temperature, NOx, DEF level | Thermocouples, electrochemical sensor, level and quality sender | Inducement derate on aftertreatment engines | Emission-related codes and progressive power loss |
Most analogue sensors share a 5 V reference and a sensor ground from the module, so a short on one sensor can generate codes on several unrelated ones. When three or four sensors fault together, suspect the supply or the harness first.
Reading fault codes properly
Codes on J1939 engines are expressed as a suspect parameter number, which identifies the measurement, and a failure mode identifier, which describes how it failed. “Voltage above normal” on a thermistor usually means an open circuit or an unplugged connector. “Data valid but above normal” on coolant temperature means the module believes the engine really is hot. The distinction decides whether you reach for a multimeter or a radiator hose.
Active codes describe the present. Stored codes with their occurrence counts and engine hours describe the past, and the freeze-frame data captured at the moment of the fault gives the load, speed and temperatures at the time. Download all of it before anyone clears codes, because an erased history is lost evidence. Our controller diagnostics service starts with that download.
A diagnostic order that avoids wasted parts
- Confirm the engine and module identity. Engine serial number, module part number and calibration version; a code list for the wrong variant is worse than none.
- Check the supply. Battery voltage at the module connector while cranking, not at the battery. A weak battery or corroded cable can let module voltage sag enough during cranking for a reset, which produces baffling intermittent codes. The DC side is covered under battery and starting system service.
- Check the grounds. Module ground, sensor ground and engine-to-frame bonding, each with a voltage drop of only a few tens of millivolts under load.
- Check the communication link. With power off, resistance across CAN high and low should be about 60 ohms, two 120 ohm terminators in parallel. Near 120 ohms means a missing terminator, which makes the controller show dashes or stale data intermittently; near zero means a short.
- Verify the sensor at its connector. Reference voltage present, ground present, signal plausible for the actual condition. A thermistor can be checked against a thermometer, a pressure sensor against a mechanical gauge.
- Only then condemn a component. Replace with the correct part for the engine serial number from controller and sensor spares, clear the code, and reproduce the original condition to prove the repair.
Calibration, parameters and who may change them
The module holds a calibration file from the engine manufacturer and a set of customer parameters such as speed droop, idle speed and which protection actions are enabled. The calibration defines the emission certification of the engine; altering it to gain power or to disable aftertreatment inducement removes the set from its certified condition under the CPCB regime and may void warranty. Customer parameters may be changed with the manufacturer’s service tool by someone trained to understand the consequences, and every change should be recorded with the old and new values. A module replaced without the correct calibration and injector trim codes will run, badly.
Remote monitoring
Because the engine data already exists on the CAN link, a modern controller can forward it to a remote platform, giving a facility manager hours, fuel level, battery voltage, coolant temperature and active codes on a phone. It does not interpret a code. Our note on communications and remote monitoring describes what is worth watching on a standby set.
Common mistakes
- Replacing the sensor named in the code without checking its connector, reference and ground; the new sensor shows the same code because the harness was the fault.
- Clearing codes before recording them; the freeze-frame data that would have explained an intermittent shutdown is gone and the fault returns during the next outage.
- Testing the battery with the engine stopped and finding it fine; the sag during cranking is what reset the module, and only a cranking test shows it.
- Letting an untrained person change parameters with a borrowed service tool; the set ends up with droop governing and frequency falls with load.
- Fitting a used module from a similar engine; the calibration and trim data do not match and the engine smokes, derates or fails to start.
What to send us
Send photographs of the engine nameplate, the module label if accessible, and the controller screen showing active and stored codes with occurrence counts. Tell us when the fault occurs and whether any wiring or panel work was done recently. A photograph of the battery terminals helps more than people expect. Send a service enquiry and we will suggest the checks to make before a visit is scheduled.
Questions engineers ask
What is the difference between the engine ECM and the generator controller?
The engine module lives on the engine and controls combustion, speed and engine protection. The generator controller lives in the panel and handles starting commands, alternator monitoring, mains sensing, transfer and alarms. On an electronic engine the controller reads engine data from the module over CAN rather than from its own senders, so a communication fault can look like an engine fault.
Can a fault code be present when nothing is wrong with the engine?
Yes. A chafed wire, a corroded connector, low cranking voltage or a missing CAN terminator will all generate codes on a healthy engine, which is why wiring and supply checks come before any component is condemned.
Why does the set lose power gradually after an emissions warning?
Engines built to current norms apply an inducement strategy when the aftertreatment cannot do its job, for example when the DEF tank is empty or a NOx sensor has failed. Power is reduced in steps to encourage repair. Clearing the code without fixing the cause brings the derate straight back.
Can I convert a mechanical engine to electronic control?
Not in any practical sense; the injectors, pump, sensors, wiring and calibration are an engineered package. What can be done is to fit a modern genset controller that reads the mechanical engine’s senders and adds remote monitoring. The two architectures are compared under mechanical versus electronic fuel systems.
Technical content reviewed by Srinivas Reddy, Managing Partner, Reddy Generators. Last updated 19 October 2026.