A module that will not answer a scan tool cannot be programmed in a remote session, because a session reaches it over the same network the scan tool uses. As of October 2026 that makes a genuinely silent module mail-in bench work — $250 for the unlock and clone services we publish, with physical repair quoted by our sister lab — but most modules reported as dead are not, and five checks with a meter separate the two before you ship anything.
Our own flash page states the rule in one sentence: a module that no longer communicates is a bench job, not a session. This post is how to find out which side of that line you are on.
Why the distinction decides the service
We sell three kinds of work, and communication is the fact that sorts them.
A remote session runs the manufacturer's application on our side through your pass-thru device. Every operation it performs — reading, programming, configuring — is a conversation over the vehicle network. No answer, no conversation.
A file service needs you to have read the module's contents with your own tool. Many of those reads are taken on the bench with the module opened or connected directly, so a module that is silent in the car can sometimes still be read out of it.
Bench work is a technician powering the module on a bench, reading it by whatever access the hardware allows, and cloning or recovering it by hand. Physical repair of a failed board goes to our sister lab, Auto Module Lab, which shares our technicians and bench.
Booking a session for a module that turns out to be silent wastes the appointment. Mailing in a module that turns out to be healthy wastes a week and leaves the real fault in the car. The checks below take less than an hour and prevent both.
First: is it one module or all of them?
Before touching a meter, connect a scan tool and attempt to reach every module on the vehicle, not just the one you suspect.
| What answers | What it points to | Next step |
|---|---|---|
| Nothing at all | The diagnostic connector, the scan tool, or the network as a whole | Check 1 and Check 2 |
| Everything except one module | That module, or its own power, ground or branch of the network | Check 3 and Check 4 |
| Several modules missing, all on one network | A network fault, or one module holding the network down | Check 2 and Check 5 |
| The module answers but logs an internal fault | The module is alive | Not a no-communication fault — see below |
That table does half the diagnosis. The single most common mistake is to test only the engine computer, find it silent, and conclude it has failed — on a vehicle where nothing was answering.
Check 1: the diagnostic connector itself
The sixteen-pin connector under the dash is defined by a standard, and a few of its pins are the same on every vehicle. Pin 16 is battery positive. Pins 4 and 5 are grounds. On vehicles that use CAN for diagnostics, pins 6 and 14 are the two data lines.
With the ignition on, measure pin 16 against pin 4 and against pin 5. You should see battery voltage on both. A scan tool that will not power up, or powers up and finds nothing, is very often a blown fuse feeding pin 16 — on many vehicles it shares a fuse with the accessory socket.
Look at the connector as well. Pins pushed back into the housing, corrosion, or an aftermarket device spliced in behind it account for a surprising share of total no-communication complaints.
Check 2: network resistance
A high-speed CAN network is terminated at each end with a resistor of about 120 ohms. Two of them in parallel measure about 60.
Disconnect the battery and wait for the modules to go to sleep. Then measure resistance between pins 6 and 14 at the diagnostic connector.
- About 60 ohms: both terminators are in circuit and the pair of wires is continuous between them. The network is physically intact.
- About 120 ohms: one terminator is missing from the circuit. Either a module containing one is unplugged or failed, or a wire is open between the connector and one end.
- Near zero: the two lines are shorted together.
- Open circuit: the connector is not reaching the network at all.
Treat those as typical figures, not guarantees. Some vehicles place the diagnostic connector behind a gateway, so the pins you are measuring see only a short diagnostic segment and not the network the engine computer lives on. Check the wiring diagram for the vehicle before drawing a conclusion from the number.
On vehicles with a security gateway, remember too that the gateway restricts writing, not reading; it is not the reason a module is silent. Our security gateway post covers what it does and does not block.
Check 3: power at the module
A module with no power is indistinguishable from a dead one at the diagnostic connector. It takes a meter at the module's own connector to tell them apart.
From the wiring diagram, identify every power feed to the module. Most engine computers have more than one: a permanent battery feed, an ignition-switched feed, and often a feed through a main relay that the computer itself controls. Measure each one at the module connector with the connector plugged in and the circuit loaded, back-probing where you can. A feed that reads battery voltage with the connector unplugged and collapses under load is a high-resistance fault, and an open-circuit reading will not find it.
Check the fuses by measuring across them, not by looking at them.
Check 4: ground at the module
Grounds fail more quietly than power feeds. A ground that has corroded at the body or was left loose after other work can pass enough current to light a lamp and not enough to run a processor.
Measure voltage drop on each ground pin with the module powered: one meter lead on the module's ground pin, the other on battery negative. A good ground shows a very small reading. A reading that rises when loads are switched on is a ground that is not doing its job.
This check matters most after any repair that disturbed the engine bay. Our U0100 guide covers the case where communication was lost immediately after an engine computer was changed — and a ground strap left off during the swap is high on that list.
Check 5: is something else holding the network down?
One faulty module can silence a whole network by driving the data lines when it should be listening. The symptom is several modules missing at once, sometimes intermittently.
With the scan tool connected and watching, unplug modules on the affected network one at a time. If communication with the rest returns the moment a particular module is unplugged, that module — or the wiring to it — is the cause, and the module you first suspected was a victim.
Water is the usual reason. A module in a wet footwell or under a leaking windscreen fails in exactly this way, and our water-damaged ECU guide covers what can be recovered from one.
Reading the result
If the diagnostic connector has power and ground, the network measures correctly, the module has every power feed and a clean ground under load, nothing else is disturbing the network, and the module still does not answer — the module is the fault, and it is bench work.
If any of those checks failed, repair that first and try again. A large share of “dead” modules come back to life when a fuse is replaced or a ground is cleaned.
“The modules that arrive on our bench and power up perfectly are the most frustrating jobs we do. Nothing was wrong with them. The fault is still in the car, three states away, and now the car has no computer in it either.” — Bench desk, ECU Flash Cartel
When the module answers but complains
A module that communicates and logs a fault about itself is alive. That is a different problem from silence, with different routes.
An internal processor or memory fault — P0606 is the generic powertrain example — means the module ran a self-test and failed it. Our P0606 guide covers what can be done, and the answer sometimes is a software update in a session, not a replacement.
Network codes logged by other modules — U0100 for lost contact with the engine computer, U0073 for a network that is off, U0121 and U0140 for the brake and body modules — tell you which module the others cannot hear. They do not tell you why. Fault codes follow the structure in SAE J2012, and the U prefix means network, not module failure. Our DTC index sorts the common codes into module, network, configuration and sensor causes, and the free DTC lookup explains individual ones.
What the bench can do with a silent module
Once a module is confirmed dead in the car, three outcomes are possible on the bench, in descending order of how often they apply.
Its data can be read even though it will not run. The processor may have failed while the memory that holds the vehicle's identity, immobiliser data and configuration is intact. That data can be moved to a replacement unit — a clone — so the replacement arrives already matched to the car. Mail-in clone work is $250, and our clone, IMMO-OFF and virgin comparison explains when cloning is the right choice.
It can be recovered. A module that went silent during an interrupted write is often not damaged at all. Its software is incomplete. Our interrupted flash recovery post covers that case, and it is one of the better outcomes: the hardware is fine.
Nothing can be read. Then the route is a replacement programmed from scratch, which returns the job to a session once a communicating module is fitted — and to the immobiliser question, since a new module has to be married to the vehicle. A swapped ECU that won't start is usually at that step.
Which access level reaches a silent module's memory depends on the family. Our bench, boot and OBD read methods guide sets out what each level can reach, and why the bench reaches further than the diagnostic connector ever does.
Before you ship
If the checks point to the module, three things make the bench job faster and cheaper.
- Photograph the label and the connectors before removal, and note the VIN.
- Send a description of the checks you did and their results. Knowing that power, ground and network were verified in the car tells the technician where not to look.
- Pack it properly. A module that survived the car and dies in a padded envelope is not rare. Our packing guide covers it.
And do not buy a replacement first. A replacement fitted to a vehicle with an undiagnosed power or network fault will be exactly as silent as the original, and will need programming on top.
Standards and the legal position
The diagnostic connector and the services available through it are standardised so that independent repairers can do this work at all. Programming through a pass-thru device rests on SAE J2534, and the generic diagnostic services a scan tool uses are defined in SAE J1979.
We do not provide emissions defeat, delete files, or services intended to bypass emissions laws. Our services exist for tuning preparation, diagnostics, repair, motorsport, and off-road use where legally permitted. Customer is responsible for confirming legal use in their location and application.
Repairing or replacing a failed engine computer restores the vehicle to its certified configuration. The federal Clean Air Act governs what is written into that computer afterwards, whoever writes it.
The short version
A session needs a module that answers; a silent one is bench work, with our published mail-in clone at $250. Before deciding, check whether anything else answers, check power and ground at the diagnostic connector, measure the network resistance with the battery disconnected, test every power feed and ground at the module under load, and unplug modules one at a time if several are missing. If the module has everything it needs and still says nothing, it is a bench job: send us the label and your results and we will tell you which route applies. If any check fails, fix the car first, and do not book a session or ship anything until it is repaired.