What Is a Cold Test on an Evinrude EMM?

If you have had an Evinrude E-TEC, FICHT, or DI Engine Management Module recovered or replaced, you may have heard a technician mention a "cold test." It sounds like something you would do to a running engine, but it is not. A cold test is a step inside the EMM programming process, and understanding it makes the whole recovery process much clearer.

What a cold test actually is

A cold test is the baseline state that the Evinrude software loads onto an EMM during recovery, replacement, or reprogramming. Before the module can be matched to a specific engine, it has to be brought to a known, clean starting point. Loading the cold test is how the software puts the module into that state. Think of it as a factory-fresh baseline: the module is alive and consistent, but it is not yet tied to any particular engine.

Because it is a starting point rather than a finished configuration, a module that only has the cold test on it is not ready to run your engine. It is the equivalent of a blank form: correct and standardised, but with none of your engine details filled in yet.

Why the cold test comes first

The order of operations matters. When an EMM is recovered, or when a replacement module is prepared, the Evinrude diagnostic software first loads the cold test to establish that baseline, and then it writes the stored EDF (Engine Data File) back onto the module. The cold test comes first for a reason: you want a predictable foundation before you layer engine-specific data on top of it.

Writing the EDF back is the step that restores the module original serial number, software, and settings. Once the EDF is written, a new or recovered EMM behaves exactly like the one it replaced. Skip that second step, and you are left with a module sitting at the cold-test baseline with no idea which engine it belongs to.

The EDF is what personalises the module

The cold test and the EDF are two halves of the same job. The EDF stores engine-specific data, including values such as injector coefficients, that make the module match your exact engine. The cold test gives the module a clean baseline, and the EDF gives it your engine identity.

This is why the EDF is so valuable, and why it is worth reading and saving before any work begins. If the EDF is preserved, a recovered or replacement module can be brought back to a proper baseline with the cold test, and then personalised again with your engine own data. You can read more about that file in our EDF explainer.

Why this is a specialist step

A cold test is a low-level procedure, not a menu option a typical owner runs at home. It is done with the Evinrude diagnostic software together with the diagnostic and bootstrap cables. The diagnostic cable handles normal communication with the module, while the bootstrap cable is what puts the EMM into recovery mode so the baseline can be loaded in the first place.

Getting this right means having the correct software, the correct cables, and the correct order of operations: baseline first, then the engine own data written back afterwards. Done carefully, the customer never sees any difference. The module simply works the way it always did.

Get your EMM handled properly

If your Evinrude EMM needs recovery, repair, or reprogramming, let a specialist do the cold test and EDF steps correctly the first time. See our EMM repair service to get started.