New Vehicle-Wide Programming for Software Updates

With its enhanced capacity and ability to manage technology complexity, the GM Vehicle Intelligence Platform (VIP) electrical architecture offers the capability of managing over 100 electronic control modules. When necessary, software updates to control modules are required for repairs as well as enhancements to vehicle functions. As opposed to programming a number of control modules individually to address several conditions, the new Vehicle-Wide Programming (VWP) feature of SPS3 allows multiple modules to be programmed during the same programming event by selecting a single button. (Fig. 1)

 

Fig. 1

 

Vehicle-Wide Programming is now available on some GM vehicles, including 2022-2024 HUMMER EV; 2023 Colorado, Canyon; 2023-2024 LYRIQ; 2024 XT4, Blazer EV, Silverado EV and Sierra EV. It provides the ability, via a single selection within Techline Connect, to first identify the modules that need updating and then proceed to updating the applicable modules (with some exceptions). The updating of modules is completed in parallel instead of forcing technicians to update one module at a time, providing a more streamlined approach that reduces the number of required steps needed for programming several modules as well as the time needed by technicians to complete repairs.

Before beginning Vehicle-Wide Programming on a vehicle, consider the following:

• Vehicle-Wide Programming should only be performed when directed by Service Information, a related Bulletin or applicable Field Action.
• Vehicle-Wide Programming will only work with a wired MDI2 connection. It is also necessary to remove any wireless dongles from the computer being used as these will not allow Vehicle-Wide Programming to be selectable. If Vehicle-Wide Programming is not selectable with a wired MDI2, confirm it shows disconnected in SPS2 and then (if needed) exit out of SPS2 and log in again.
• If a control module needs to be replaced, the new module should be programmed first following Service Information instructions prior to Vehicle-Wide Programming.
• Vehicle-Wide Programming does not support A11 Radio Reprogramming with USB and SPS.

Programming Tips

To complete a Vehicle-Wide Programming event, after entering a job card number, select the blue Start Vehicle-Wide Programming button on the screen.

The green car icons under the Vehicle-Wide Programming column indicate the control modules that are supported by Vehicle-Wide Programming. (Fig. 2) All other control modules must be programmed individually as done previously if required as part of vehicle servicing. No setups/configurations or key provisioning are needed with Vehicle-Wide Programming.

 

Fig. 2

 

Once the Vehicle-Wide Programming process has begun, several graphs will show the progress of retrieving current software data from the vehicle and the latest software data from GM, along with the file downloading progress and programming progress. (Fig. 3)

 

Fig. 3

 

After the Vehicle-Wide Programming process is finished, the Vehicle-Wide Programming Summary report will indicate any other modules needing separate programming. (Fig. 4) While it is saved automatically, it is recommended for technicians to print/capture anything noted as failed or out of date before exiting the screen. It’s also advised to check the VCU separately as it is currently not included in Vehicle-Wide Programming.

 

Fig. 4

 

Warranty Claims

The warranty claim code will be displayed with details of a completed, partial, or failed programming event. (Fig. 5) The first 3 digits of the code identify if the event was successful.

• A completed event (VPY) indicates that all control modules were successfully programmed or skipped. Skipped control modules indicate that the module is up to date and no further programming is needed. Blocked control modules (VPB) were already up to date and no programming was attempted.
• A partial event (VPP) indicates that at least one control module failed to program. Failed control modules will be highlighted in red.
• A failed event indicates that all control modules failed to program.

 

Fig. 5

 

TIP: If a failed programming event occurs, Vehicle-Wide Programming should be repeated one time prior to using SPS2 to program the affected module(s). A separate warranty code will be displayed.

To avoid warranty transaction rejections, the warranty claim code provided on the Warranty Claim Code screen must be recorded on the job card. The programming receipt(s) also should be printed or saved at the time of programming. (Fig. 6)

 

Fig. 6

 

Refer to Bulletins #24-NA-113 and #24-NA-132 for additional information.

Thanks to Chris Henley and David Rase