Module Programming: Programming

1. NOTE: If a new module is being installed, install the new module before carrying out the following procedure.
   • If replacing the module do not  connect the new module to a Wi-Fi network before completing the scan tool module replacement programming as it may cause programming concerns.
   • This programming procedure deletes any phones that are paired with the SYNC system when programming the APIM.
   • To prevent time-out errors and minimize programming time, a wired internet connection is strongly recommended when programming.
   • Make sure the FDRS version and patch software levels are up to date.

   Connect a battery charger to the vehicle and select the low charge setting. The negative battery charger lead must be connected to a clean chassis ground, not  the negative battery post.

2. Connect the diagnostic scan tool to a power supply. The length of time required for programming may extend past the duration of the diagnostic scan tool.
3. Connect the diagnostic scan tool to the DLC.
4. Log into FDRS.
5. Identify/enter the vehicle being programmed on FDRS.
6. NOTE: Vehicle information is automatically retrieved by the diagnostic software and a Network Test is run. Vehicle identification data appears on the screen when this is complete.

   Click 'Read VIN from Vehicle' or manually enter the VIN.

7. NOTE: Available modules are shown on the LH side of the screen, and available procedures are listed on the RH side of the screen. Modules that are communicating are highlighted in green.

   Select Toolbox tab.

8. NOTE: If a module is integrated within another module, both modules will automatically program during this process. For example, if the ACM is selected, the DACMC (if integrated with the ACM) is also programmed.

   From the list on the LH side of the screen, select the module that requires a programming procedure to be completed.

9. There are 3 types of module programming available:
   • Programmable Module Installation (PMI) 

     --When the module is replaced, this type of programming carries out the required provisioning (restores software for newly installed hardware).

   • Module configuration 

     -- Downloads configuration data to the module. The module may also be programmed, depending on current software level, when this option is selected.

   • Software Update 

     -- Updates the module and any currently installed applications to the latest software levels. This option is not available if the module is already at the latest level.

10. From the list on the RH side of the screen, select PMI Software Update or Module Configuration.
11. NOTE: Do not disconnect the VCM from the DLC during the module programming process unless directed by the diagnostic scan tool on-screen prompts.

    Follow all on-screen instructions carefully.

12. After programming is complete, "Programming has been successfully completed" displays.

1. Connect a battery charger to the vehicle 12v battery. Set the charger to maintain 12.6 - 13.6 volts.
2. Connect the VCM II, VCMM or later level to the vehicle DLC and the diagnostic scan tool USB port.
3. Log into FDRS.
4. NOTE: Vehicle information is automatically retrieved by the diagnostic software and a Network Test is run. Vehicle identification data appears on the screen when this is complete.

   Click 'Read VIN from Vehicle' or manually enter the VIN.

5. NOTE: Available modules are shown on the LH side of the screen, and available procedures are listed on the RH side of the screen. Modules that are communicating are highlighted in green.

   Select Toolbox tab.

6. NOTE: If the module is already at the latest software level, the software update application will not be available in the diagnostic scan tool.

   If replacing the module, download and run the PMI. If the module is not being replaced but is receiving a software update in accordance with a TSB or service publication, download and run the software update application for the target module.

7. Follow the on-screen prompts to complete the PMI
8. On-screen prompts are displayed to inform that a USB is required to complete the process.
9. Follow the on-screen instructions to download the required software to the USB memory device and upload to the vehicle though the vehicle USB port.
10. Once the USB memory device is connected to the media hub or USB port, the software update will automatically install. The USB memory device transfers the data through the USB cable to the APIM. The APIM transfers the data to the GWM where it is distributed to the receiving module over the Ethernet network.
11. It is advised that the USB memory device remain connected to the vehicle for a minimum of 2 minutes after the progress bar displayed on the vehicle display screen has reached 100%, to ensure the upload has completed fully.
12. If an error occurs during the USB programming process an error message is displayed on the vehicle display screen indicating an error has occurred and displays an error number relating to the type of error that occurred. REFER to the Error Condition Table below for a description and action to be taken, if an error message is displayed.

Error Condition Table