Programming Procedure
Programming Procedure
Determination Process
Programming software uses a feature known as the "Determination Process". It is necessary to perform the determination process correctly and follow all prompted instructions.
DME Programming required as a direct result of a service action or recall will be covered in the specific SI Bulletin. Each bulletin could have different procedures due to the specific DME being reprogrammed. The differences can cause unique messages to display in the DIS/MoDiC. Always read the SI Bulletin thoroughly and become familial with the possible unexpected display messages before attempting any programming.
Prior to programming, a Technician should review the vehicle history file to see if any previous programming was performed. There may be a program added to the current EPROM that will not be recognized by the determination process or the View programming will not include the previous addition.
The determination process is used in all programming procedures:
- Customer Service Measures.
- Exchange control unit.
- Exchange EPROM.
With the DIS/MoDiC connected to the old control module through the diagnostic link, the software interrogates the old control module for proper identification.
It also recognizes any updates that have been added previously to the old EPROM.
When the determination information is stored in the DIS/MoDiC memory, the programming software:
- Suggests updates for the connected control module (Customer service Measure)
- Provides the part number for the replacement - Basic Control Module
- EPROM
- Reuses the data when the replacement control module or EPROM is programmed as long as the DIS/MoDiC is not used for another purpose after the determination process.
There are two determination methods: automatic and manual.
Automatic: The software performs this automatically. During the automatic determination the VIN is displayed.
If the VIN matches the connected vehicle press the "Yes" button.
If the VIN does not match the connected vehicle the installed control module may have been previously replaced. Press the "No" button. Manually enter the correct VIN from the vehicle and press "Yes".
The software compares the electronic part number of the installed EPROM with a list of replacements. This is a part number for a replacement basic control module or an EPROM depending on the procedure being performed.
There are two columns of part numbers in the display. The left column is new basic control modules and the right column is remanufactured basic control modules. Always order using the part number from the right column. Proceed with the reprogramming procedure covered further on.
If the MoDiC displays the message "No Substitute found" continue on to a manual determination.
Manual determination is performed by pressing "No" to the displayed question, "Is the faulty control module still in the car".
Manual: A manual determination must be performed if:
- The control module cannot communicate with the DIS/MoDiC.
- The software does not recognize the DME identification data.
- The DIS/MoDiC cannot find a replacement number stored in memory during an automatic determination.
Manual determination is carried out by entering:
- Part number of the basic programmable control module.
- VIN of the vehicle.
- Part number of the factory programmed control module.
These numbers are found on the I.D. label of the DME control module.
The DIS/MoDiC will display the part numbers for the replacement part. Order the component using the MoDiC supplied part number (only use number
in right column) and proceed with the reprogramming procedure.
If the display states: "No Programming data available for this SG version.", or "Incorrect part number for programmed control unit?" Double check the control module label for an incorrect VIN. This control module could have been incorrectly programmed in a previous programming campaign or control module replacement.
If after both the automatic and manual determinations have been performed and the message "No Substitute found" is still displayed the following maybe the cause:
- A part number supersession has occurred since the programming software was issued (thoroughly review the Service Information bulletin for alternative part numbers to be entered).
- The currently installed control module was incorrectly programmed in a previous programming procedure.