Vehicle-Wide Programming Update for EVs

Vehicle-Wide Programming (VWP), which allows multiple control modules to be programmed during the same event, is no longer required to be performed on EV models as part of a service visit to a dealership, or prior to sale or delivery, including Pre-Delivery Inspection (PDI).

Effective July 1, 2026, Vehicle-Wide Programming should only be performed on 2022-2026 HUMMER EV models, 2023-2026 BrightDrop models, LYRIQ; 2024-2026 Blazer EV, Equinox EV, Silverado EV, Sierra EV, OPTIQ; 2025-2026 ESCALADE IQ; 2026 VISTQ; and 2027 Bolt models when a specific concern requires a software update for at least one module, or the customer requests a software update while the vehicle is covered under the New Vehicle Bumper-to-Bumper Limited Warranty. (Fig. 6)

TIP: Dealerships should not submit an unrequested VWP update as warranty on pre-sale or post-sale vehicles, except Cadillac CELESTIQ. Refer to Bulletin #24-NA-132 for claim submission information.

 

Fig. 6

 

Since EVs contain a significant number of control modules that may require software updates, technicians should always diagnose the specific conditions on a vehicle and follow the appropriate Service Information diagnostics prior to performing Vehicle-Wide Programming to ensure that current and history DTC information is captured.

VWP Tips

Vehicle-Wide Programming will only work with a wired MDI 2 connection. Remove any wireless dongles from the computer being used as these will not allow VWP to be selectable. If VWP is not selectable with a wired MDI 2, confirm it shows disconnected in SPS and then (if needed) exit out of SPS and log in again.

On the SPS screen, start a VWP event by clicking the blue button. After identifying the modules to program, an SPS page will open and VWP will begin. (Fig. 7)

 

Fig. 7

Once complete, the VWP Summary report will list all modules that are up to date and indicate any other modules needing separate programming. Any failures will be shown in red. If a failed programming event occurs, VWP should be repeated twice prior to using SPS to program the affected module.

If any module is replaced, program and set up the single module first in SPS prior to Vehicle Wide Programming.

For additional information on Vehicle-Wide Programming, refer to Vehicle-Wide Programming and Setup in the Service Information and Bulletin #24-NA-113.

Bulletin #24-NA-143 provides more information about the latest VWP policy for EVs.

 

– Thanks to John Sauer

TAC and TCSC Phone Support to Require CX Connect Case Number
Fuel Pump Power Control Module Internal Short

4 Comments

  1. Eric Webster says:

    vehicle wide programming should be done on all vehicle when they come in due to the fact that so many updates are needed and if customer satisfaction is your top priority?

  2. Andrew G. Kalipetis says:

    LUIS AND JERRY ARE 100% CORRECT. VWP SHOULD BE PART OF EVERY SERVICE VISIT ON THE EV’S WHETHER THE CUSTOMER REQUESTS IT OR NOT. IF OUR FOCUS IS A QUALITY PRODUCT AND CUSTOMER RETENTION, WHY SHOULDN’T WE GIVE OUR CUSTOMERS THE BEST POSSIBLE EXPERIENCE?
    ALSO, IN MY EXTENSIVE EV EXPERIENCE, I HAVE YET TO HAVE AN OTA SUCCESSFUL WHEN IT’S PROMPTED BY “UPDATE AVAILABLE” MESSAGE WHEN A VEHICLE IS PUT INTO PARK. THIS HAPPENS NUMEROUS TIMES AND EMBARRASINGLY HAPPENS OFTEN JUST AFTER YOU HAVE DONE VWP.
    WE NEED TO GET BACK TO BEING “THE STANDARD OF THE WORLD”, NOT PLAY FOLLOW THE LEADER.

  3. Sending out new EV vehicles without being programmed with the latest software is asking for trouble. Do you know how many EV’s have returned with various complaints shortly after purchasing the vehicle for issues such as radio, body electronics etc etc. ? I can very well tell you as well as many other techs I know and not to mention all of other ones out there that work on them. A vehicle will come in for service and then return a month later with another issue and looking again, 10+ modules show software updates available after just being fully up to date the previous month.

  4. Jerry Pinnelli says:

    Vehicle wide fixes SO many issues it should be part of every PDI and it should be done whenever they come in for work. Stopping this just creates unhappy customers with repeat trips to the dealership. Maybe when you actually figure out how to push OTA updates without locking things up it won’t be necessary, but for now I think you’re just setting us up for complaints.

Leave a Reply

Your email address will not be published. Required fields are marked *

*