KevinP
Active member
Sorry I feel stupid after the amount of time I have spent reading this thread I don’t have a clue how to do a config…
Sponsored
Sponsored
RellIk&5
Well-known member
- First Name
- Wayne
- Joined
- Jan 25, 2022
- Threads
- 8
- Messages
- 186
- Reaction score
- 96
- Location
- Las Vegas, NV
- Vehicles
- 2021 F150 XLT Black Widow
I finally finished my IPC update. As soon as it finished, I got the GWM and then the APIM updates. Now sitting at 22095 Rev 421 like everyone else. Unfortunately, I don't have any new cards so I'm not sure if I got the rear camera in motion like everyone else.
In fdrs it’s under PMI. Apim configuration
KevinP
Active member
Ok, that ran pretty quick and did not seem to give me any errors. I guess I will see tomorrow if Blue cruise is active or not.
Thanks Jesse for your help and contributions to this thread!
No problem.. I’ll look in and see but you will have blue cruise for sure
Sponsored
drkCrix
Member
USB stick formatted in exFat with the files installed as directed. If this works will I need to do anything further for updates? Or just let OTA take care of things?
Cheers,
Chris
Some reason teh APIM config isnt updating. We may manually have to do it with FOrscan
Airborne_Ape
Well-known member
- First Name
- Chad
- Joined
- Mar 19, 2021
- Threads
- 1
- Messages
- 123
- Reaction score
- 163
- Location
- Atlantic Canada
- Vehicles
- 2010, 2014, 2017, 2021 F150
Not sure who already has this. I stumbled across the USB update error chart for our trucks. WSM Section 418-01A revision April 2022. Maybe it can help some people.
Sponsored
Mike G
Well-known member
- First Name
- Mike
- Joined
- Jan 6, 2022
- Threads
- 1
- Messages
- 511
- Reaction score
- 382
- Location
- N. AL, USA
- Vehicles
- 2022 F-150 Lightning, 2023(J1) Mach-E GT-PE
Select the APIM on the left side panel, then select the Download (then Run) option for "APIM - Reset the SYNC Module [APIM]" on the right side panel. Normally at the end of the BC procedure (21G01) you do this step twice. See below:Ran FRDS today and it showed a new APIM update. Loaded it successfully and I am now at SYNC Version 22095 Revision 421.
Am I going to be blue cruising? FDRS does not show anymore updates for me. Do I need to do a master reset? Instructions in 21G01 say to do one through FDRS main menu but I could not figure out how to do it and did not see it anywhere in FDRS.
Mike
Last edited:
Mike G
Well-known member
- First Name
- Mike
- Joined
- Jan 6, 2022
- Threads
- 1
- Messages
- 511
- Reaction score
- 382
- Location
- N. AL, USA
- Vehicles
- 2022 F-150 Lightning, 2023(J1) Mach-E GT-PE
Select the APIM in the left panel. Select Download and then Run on the APIM Config item in the right panel.
Mike
Airborne_Ape
Well-known member
- First Name
- Chad
- Joined
- Mar 19, 2021
- Threads
- 1
- Messages
- 123
- Reaction score
- 163
- Location
- Atlantic Canada
- Vehicles
- 2010, 2014, 2017, 2021 F150
U-2100: initial configuration not complete
I found a way to resolve erroneous initial configuration not complete DTC's with ForScan. It is known to appear after software updates for those who have modified as built data, but may also appear for owners with stock configurations. It can appear for various reasons, but the circumstance detailed below is seemingly common.
I've seen modules replaced because of these faults (since it blocks updates). Perhaps you can save some time by tring these steps.
My understanding of this fault is that some modules rewrite default as built parameters after particular updates and they fail for whatever reason which then corrupts them.
If you are stuck with a persistent U-2100 or similar DTC after an OTA or FRDS update which states: initial configuration not complete, it can be cleared but it takes more steps than usual.
-------------------------------
The ForScan Way:
As built configurations do not need to be returned to default to clear this error.
In ForScan go to > Configuration and programing > Module X Module Configuration (As Built) > Restore All (nothing changes) > Write All > Yes Force Rewrite all current values > Follow on screen steps.
After successful forced as built rewrite > back out of module configuration tab > go to service functions tab > under service procedures select the module(s) you rewrote > perform a module reset action > follow on screen steps.
When done > select the GWM > perform a module reset action > follow on screen steps.
This accomplishes is a forced rewrite of the custom as built data and forced reboot of the module with undesirable DTCs. Rebooting the GWM is simply to ensure the in-vehicle handshake is re-established before final steps.
In ForScan > back out of the service functions tab > go to DTC Tab > Reset DTC's > follow on screen steps.
Initial configuration not complete DTCs for the target ECU will now disappear.
Note 1: Attempting to restore a known-good as built backup will fail. I believe the nature of this error is some sort of checksum fault in the as built data on the module.
Note 2: Uncleared DTC's will prevent future OTA's from completing in target modules as per the WSM. Therefore, it is important to try to clear / resolve DTC's when any are present so that future updates can complete.
-------------------------------
The FRDS way:
I haven't personally tried to resolve this type of issue with FRDS yet, but I have read this response from the hotline after another tech ran into a nearly identical situation.
Recovery PMI process
Connect FRDS to the vehicle and begin a session.
Physically disconnect FRDS from the vehicle then initiate PMI for the desired module.
Keep the FRDS session active.
Let FRDS fail to connect.
Reconnect the VCM to the OBD.
Instruct FRDS the original module is not available.
The PMI process will then proceed.
It will clear the fault by rewriting the original ECU as if it is a new replacement.
-------------------------------
After the FRDS session I suggest disconnecting all 12V vehicle power sources for a minute to ensure all modules reboot otherwise there may be a new DTC for ethernet disconnected.
Pro Power equipped vehicles have an extra 12V auxiliary battery under the passenger rear seat.
After the U code is cleared updates from Over The Air or FRDS can resume as intended.
I found a way to resolve erroneous initial configuration not complete DTC's with ForScan. It is known to appear after software updates for those who have modified as built data, but may also appear for owners with stock configurations. It can appear for various reasons, but the circumstance detailed below is seemingly common.
I've seen modules replaced because of these faults (since it blocks updates). Perhaps you can save some time by tring these steps.
My understanding of this fault is that some modules rewrite default as built parameters after particular updates and they fail for whatever reason which then corrupts them.
If you are stuck with a persistent U-2100 or similar DTC after an OTA or FRDS update which states: initial configuration not complete, it can be cleared but it takes more steps than usual.
-------------------------------
The ForScan Way:
As built configurations do not need to be returned to default to clear this error.
In ForScan go to > Configuration and programing > Module X Module Configuration (As Built) > Restore All (nothing changes) > Write All > Yes Force Rewrite all current values > Follow on screen steps.
After successful forced as built rewrite > back out of module configuration tab > go to service functions tab > under service procedures select the module(s) you rewrote > perform a module reset action > follow on screen steps.
When done > select the GWM > perform a module reset action > follow on screen steps.
This accomplishes is a forced rewrite of the custom as built data and forced reboot of the module with undesirable DTCs. Rebooting the GWM is simply to ensure the in-vehicle handshake is re-established before final steps.
In ForScan > back out of the service functions tab > go to DTC Tab > Reset DTC's > follow on screen steps.
Initial configuration not complete DTCs for the target ECU will now disappear.
Note 1: Attempting to restore a known-good as built backup will fail. I believe the nature of this error is some sort of checksum fault in the as built data on the module.
Note 2: Uncleared DTC's will prevent future OTA's from completing in target modules as per the WSM. Therefore, it is important to try to clear / resolve DTC's when any are present so that future updates can complete.
-------------------------------
The FRDS way:
I haven't personally tried to resolve this type of issue with FRDS yet, but I have read this response from the hotline after another tech ran into a nearly identical situation.
Recovery PMI process
Connect FRDS to the vehicle and begin a session.
Physically disconnect FRDS from the vehicle then initiate PMI for the desired module.
Keep the FRDS session active.
Let FRDS fail to connect.
Reconnect the VCM to the OBD.
Instruct FRDS the original module is not available.
The PMI process will then proceed.
It will clear the fault by rewriting the original ECU as if it is a new replacement.
-------------------------------
After the FRDS session I suggest disconnecting all 12V vehicle power sources for a minute to ensure all modules reboot otherwise there may be a new DTC for ethernet disconnected.
Pro Power equipped vehicles have an extra 12V auxiliary battery under the passenger rear seat.
After the U code is cleared updates from Over The Air or FRDS can resume as intended.
Last edited:
RellIk&5
Well-known member
- First Name
- Wayne
- Joined
- Jan 25, 2022
- Threads
- 8
- Messages
- 186
- Reaction score
- 96
- Location
- Las Vegas, NV
- Vehicles
- 2021 F150 XLT Black Widow
So for a non BC, non 360 XLT 302a with 8" cluster, the latest updates do not enable backup camera in motion or add any additional cards to support the backup camera in motion. Frankly, I don't see anything new in any of the Sync menus or on my IPC as a result of the latest updates.
speedracercjr
Well-known member
Argh, it's been over a month since I got 2.8.2 pushed to me and still no 2.8.3. Not that I'm missing any features but it's annoying that the OTA's aren't coming again. Looks like a weekend of FDRS to get caught up since the last time.
Sponsored
