General Information
DME Control Module Programming
DME programming is used to change a "basic control unit" into a "programed control unit" by writing operating instructions onto a blank EPROM. Programming is also used to update an existing DME program by writing additional instructions that compliment the existing software. Programming is used on DME M3.X variants.
Storage of Programming Data
In it's unprogrammed basic state, the EPROM only contains "resident data". The resident data provides control module/EPROM identification to the programming software prior to programming.
When programmed, the EPROM is filled with the required characteristic maps (ignition timing, injection etc), control module constants, Identification data, etc.
When is programming necessary?
Programming an engine control module is necessary when:
- Installing a replacement basic control module
- Recall or Service Action campaign: This falls into one of the following categories:
- Program update to existing program
- Complete programming procedure after EPROM replacement.
Programming a replacement basic control module
Control modules are received from the parts department in the basic state (EPROM loaded only with resident data). These control modules require programming using the DIS/MoDiC and the latest programming software.
Programming Update
Updates are referred to as "Customer Service Measures" in the programming software. The existing program in the control module is amended with an updated program. This new data changes various operations of the existing control programming. Program updates write the new data in a reserved section of the EPROM. The location of the old data is overwritten with instructions for the DME to search the reserved section in the EPROM when the function is required.
Because of limited space on the EPROM, program updating can only be done one time.
The DIS/MoDiC will display the message "Measure not applicable to the control module version" if update has already been done or the DME is factory updated