TSB 24-2012 - Drive Mode Not Available Message / Defaults to Normal Mode While Driving

[Mach-Lee]

The fix for the "Drive Mode not available" message is available. It involves a SYNC (APIM) update, but needs to be coordinated with other modules including the GWM, TCU, and IPC. These four modules should have been updated in the 6.2.1, 6.1.0, 6.3.0, and 6.8.0 OTAs. Additionally, 2021 vehicles will also need an IPMA module update (no OTA yet), which triggers additional coordinated modules including PSCM, CCM, and CMR. All said, this could take a decent chunk of time to do all the updates.

Hopefully dealers are not sticklers about needing to reproduce this message. Just give them this TSB.

TECHNICAL SERVICE BULLETIN Drive Mode Defaults To Normal Mode While Driving And Drive Mode Not Available Message Displays In The Center Display Screen With Or Without DTC U0253 Stored In The ABS Module	24-2012 12 January 2024​
Model: Ford 2021-2023 Mustang Mach-E Markets: Canada, USA Summary Issue: Some 2021-2023 Mach-E vehicles may exhibit the drive mode default to normal mode while driving and Drive Mode Not Available message displays in the center display screen with or without DTC U0253 stored in the ABS module. This may be due to the software in the APIM. To correct the condition, follow the Service Procedure steps to reprogram the APIM. NOTE: The APIM software update that addresses the symptom listed in this bulletin may have been sent via Ford Power-Up software updates delivered over-the-air (OTA) to connected vehicles that have automatic updates enabled through the center display screen. Enter the VIN in PTS and check the OTA Dashboard under the Connected Vehicle tab for OTA update history. If an update to the APIM has successfully completed recently and the customer is reporting the symptoms are no longer present, this article may not apply. Action: Follow the Service Procedure to correct the condition on vehicles that meet all of the following criteria: • 2021-2023 Mustang Mach-E • Drive mode defaults to normal mode while driving • Drive Mode Not Available message displays in the center display screen Parts Service Part Number Quantity Description BAGM-H3​ If Needed​ Battery If Needed indicates the part is not mandatory. Warranty Status: Eligible under provisions of New Vehicle Limited Warranty (NVLW)/Service Part Warranty (SPW)/Special Service Part (SSP)/Extended Service Plan (ESP) coverage. Limits/policies/prior approvals are not altered by a TSB. NVLW/SPW/SSP/ESP coverage limits are determined by the identified causal part and verified using the OASIS part coverage tool. Labor Times Description Operation No. Time 2021-2023 Mustang Mach-E: Reprogram The Appropriate Modules As Required By The Software Update And Service Procedure (Do Not Use With Any Other Labor Operations) MT242012​ Actual Time​ Repair/Claim Coding Causal Part: 14G670 Condition Code: 04 Service Procedure NOTE: Ask the customer to bring their spare key fob to assist in the FDRS programming. The time required to complete this procedure will vary depending on several factors including the number of module software updates required, available internet bandwidth, USB flash drive variability, and the potential that CAN flashing (software update via the DLC with FDRS) may be required. It is recommended to connect to the internet with an ethernet cable and use a USB 3.0/3.1 capable flash drive when performing software updates. 1. Start an FDRS session and navigate to Toolbox tab > Datalogger > body control module (BCM) and select the BATT_SOC PID. Verify the PID reads 50% or higher. If SOC is less than 50%, charge the battery then navigate back to Toolbox tab > BCM > Reset Battery Monitor Sensor Learned Values application. Perform the BMS reset. (1). If the battery is unable to achieve an 50% SOC then a new battery may be required. Use the Rotunda GRX-3590 or DCA-8000 testers to verify if replacement is required. If the battery is replaced, fully recharge the new battery. Then disconnect the Rotunda charger and perform a BMS reset using the FDRS scan tool. 2. Reconnect the battery charger and set it to maintain a vehicle voltage of 12.6-13.6 volts. A low battery SOC while performing a software update to any module may result in a repeat Restart Required message in the vehicle's center display screen or a message on the FDRS saying Part Number Validation Failed or DID Validation Failed. 3. Are there any updates available for the GWM? (1). Yes - proceed to Step 4. (2). No - this article does not apply. Refer to WSM, Section 415-00. 4. Perform the Module Software Updating Procedures outlined below for the GWM, TCU, APIM and IPC. Perform a network test after each software update using the latest software level of the FDRS scan tool. This will refresh the list of modules that have available software updates based current module software levels. Continue performing software updates to the GWM until all available software updates for those modules are complete. If any error conditions are experienced during programming, refer to WSM, Section 418-01A > General Procedures > Module Programming for the Error Condition Table. 5. For 2021 vehicles only, perform the IPMA Software Updating Procedure. When performing the IPMA software update, additional modules receive software updates. Depending on vehicle features, the coordinated software update includes the IPMA, PSCM, CCM and/or CMR. (1). Reprogram the IPMA using the latest FDRS software level. Follow all on-screen instructions carefully to complete all coordinated module software updates. (2). Perform the FDRS Image Processing Module A (IPMA) Alignment procedure. (3). Perform the appropriate FDRS camera alignment procedure. (4). For vehicles equipped with 360 degree cameras, perform the IPMA - 360 Degree View Camera Alignment procedure. (5). For vehicles not equipped with 360 degree cameras, perform the IPMA - Pro Trailer Backup Assist Camera Alignment procedure. This procedure should be performed on all vehicles without 360 degree cameras, even if the vehicle is not equipped with PTBA. 6. For 2021 vehicles only, perform the Module Software Updating Procedures again outlined below for the GWM, TCU and APIM. Module Software Updating Procedure The following instructions apply when performing a software update on any of the following modules: • GWM • TCU • APIM • IPC NOTE: A 32GB or larger USB flash drive is required for software updates. Make sure the USB flash drive being used is formatted correctly. To see the available drives, hold down the Windows icon keyboard key and press the E keyboard key. Right click on the USB flash drive and select Properties. If File System under the General tab is not exFAT, the drive must be formatted. To format the USB flash drive: • Right click on the USB flash drive • Select Format, select exFAT for the File System • Select Default Allocation Size for the Allocation Unit Size • De-selecting Quick Format is not necessary and results in a lengthier operation 1. Using the FDRS, begin module programming by selecting the SW Updates tab. Download and run the application for the desired module. Follow all on-screen instructions carefully. 2. When prompted, connect the USB flash drive to the FDRS. 3. When prompted by the FDRS, safely remove/eject the USB flash drive from the personal computer (PC), turn the vehicle to KOER. Connect the USB flash drive to the media hub to install the software update. The update starts automatically and may take 10 minutes or longer to complete. NOTE: It may take up to 5 minutes for the vehicle to recognize the USB flash drive with software update. 4. When center display screen prompts to restart the vehicle: (1). Turn the vehicle off. (2). Wait 10 minutes. (3). Turn the vehicle to KOER. (4). Leave the USB flash drive inserted into the vehicle, until the vehicles infotainment display screen states programming successful. NOTE: It may take up to 5 minutes before the center display screen displays the Update Successful pop-up. After 5 minutes if Successful pop-up is not shown on the vehicle's center display screen, remove the USB flash drive and select YES on the FDRS Was The USB Update Successful prompt ( FDRS verifies if the module software update was successfully installed on the module). 5. Continue following the FDRS prompts to complete GWM, TCU, APIM and IPC software update.

Sponsored

 

[Neil4Real]

Is the missing PSCM bulletin still posted? I had the PSCM update appear yesterday in FDRS, seems to be resolved?

 

[Mach-Lee]

Is the missing PSCM bulletin still posted? I had the PSCM update appear yesterday in FDRS, seems to be resolved?

It’s been resolved.

 

[Moeyjar]

Glad they have finally acknowledged the issue, and already have a fix for this being deployed.

 

[Logal727]

Haven't seen this in a while after some recent updates, but maybe just luck since looks like I may be missing a big part of it atm.

 

[kennethjk]

thanks for the info

Is it TSB-24-2021

or TSB-24-2012

 

[voxel]

Haven't seen this in a while after some recent updates, but maybe just luck since looks like I may be missing a big part of it atm.

Same. It appeared after an OTA update - primarily trying to drive in Unbridled and it switching back to Engaged.

Haven't seen it in months.

 

[Mike G]

So what rev of the APIM actually fixed this problem?

"-EL"? (AKA Sync 1049)
"-EM"? (AKA Sync 1058)

Or was it some earlier version?

 

[TheSeg]

TSB's like these are why I wish I could download the car.

No FRDS or hooking up backup battery. Just a unified download package, a USB stick or external hard drive of decent quality, and a properly working Level 2 charger hooked up to the car. No guess work or incorrect order of operations. Just plug in power as normal, plug in the USB stick, and initiate the process. Once complete, everything's up to patch with no guess work.

An end-user can do this, which means the service center can do this. Less active people hours working on the car and greatly reduced margin of error. I know the current engineering of Ford's EV platform doesn't allow for this, but I'll still bring it up in hopes of fixing this in the future.

 

[Ravensfan1996]

Haven't seen this in a while after some recent updates, but maybe just luck since looks like I may be missing a big part of it atm.

Mine also. Im up to 6.7 and have ‘21 Premium and havent seen it in months. got it like 2 days this summer then nothing since.

 

[Electric Goat]

Is there any way to fix this on a 2021 without installing the "piece of sh*t" 6.8.0 update that actually breaks the drivers display and takes away features that I find valuable?


Fortunately, I'm not seeing the drive mode error very much these days. I'll see it maybe once a month.

 

[phil]

Glad they have finally acknowledged the issue, and already have a fix for this being deployed.

"already"? How many months did this take? I don't think "already" is the right word here.

I am good with "finally", however.

 

[azerik]

Yet another one to add to the list, my dealer will be thrilled.

 

[awp0]

"Normal mode"?

 

[Mach-Lee]

Is there any way to fix this on a 2021 without installing the "piece of sh*t" 6.8.0 update that actually breaks the drivers display and takes away features that I find valuable?

Don't think so, all this stuff works together so it has to be a specific set of versions that play nicely with each other. Otherwise you get weird bugs from untested configurations.

"Normal mode"?

Normal mode = Engage

Sponsored