MotoTune:FAQ:Using Mototune with Development vs. Production Control Modules

Fundamental Question:

What is the difference in functionality and calibration process, when using a production (PROD) type module versus a development (DEV) type module?

A development module (of the same hardware iteration) is identical to a production module, except it contains a ‘piggyback’ RAM/EEPROM circuit. The purpose of this circuit is to allow ‘real time’ calibration changes and development.

This addition is relatively expensive, so it is only applied to modules that need it. Most development is performed on development modules, and the standard Motohawk process assumes their use.

In the case where you need to do work with a production module, it is certainly not a problem. It does have some limitations and minor differences in the software build process, described below.

Limitations:

• A production module cannot support ‘real time’ changes in Mototune, or other calibration tool. Changes must be made ‘offline’, and re-flash the calibration. You can however, use Mototune to view and record output data.

Build Differences:

• When using a production module, a unique Motohawk build is required. In the ‘Target Definition’ block of the current model, under the memory layout pull down menu, PROD, or DEV+PROD must be selected to obtain a build for a production module. If you select DEV+PROD, two .SRZ filesets will be produced with a build, one with a _DEV added to the filename, and another with a _PROD added. A production module build will only program into a production module. A development module build will only program into a development module.