• Welcome to F150Lightningforum.com everyone!

    If you're joining us from F150gen14.com, then you may already have an account here!

    If you were registered on F150gen14.com as of April 16, 2022 or earlier, then you can simply login here with the same username and password!

Sponsored

ziptbm

Well-known member
Joined
Jan 4, 2023
Threads
7
Messages
72
Reaction score
33
Location
Michigan
Vehicles
'22 MME GT & '22 F150 Lightning Lariat ER
Yes.

That right panel comes off using the plastic turnlocks.
Frunk_PL6100.png


Lightning_Jump_Connections.png
Is there not a recommended ground point within the battery compartment in the middle back of the frunk?

I was just searching for recommendations on this exactly, so I was surprised to see that taking the dozen clips off was preferred to the sliding battery door.
 

ziptbm

Well-known member
Joined
Jan 4, 2023
Threads
7
Messages
72
Reaction score
33
Location
Michigan
Vehicles
'22 MME GT & '22 F150 Lightning Lariat ER
Alright, so I just made the plunge into FDRS and successfully got the date updated for my BC hands-free maps (I haven't tested by driving hands-free yet in this vehicle) and an APIM update to Revision 610.

However, I did run into several failures and made various attempts to overcome them, but have not been successful yet.

  1. PCM Update --> This contained a chain of updates and I noticed the following failures:
    1. 1st Attempt (connected via USB 3.0 Hub because GWM required USB)
      1. BECM
        1. Procedure Unsuccessful - FlashSoftware
        2. Security access failure
      2. GFM2
        1. Procedure Unsuccessful - Client received SOAP Fault from Server: SC-UE-UNKNOWN FSP ERROR OCCURRED
      3. SOBDMB
        1. Procedure Unsuccessful - MainUpdateProcess
        2. Failed to restore module configuration
      4. ABS
        1. Procedure Unsuccessful - MainUpdateProcess
        2. Failed to restore module configuration
      5. SOBDMC
        1. Procedure Unsuccessful - MainUpdateProcess
        2. Failed to restore module configuration
      6. PCM
        1. Procedure Unsuccessful - GetFlashActionPartNumbers
        2. Unable to obtain Flash Action part numbers!
    2. 2nd Attempt (removed USB 3.0 Hub after several re-attempts before)
      1. Many of the modules above updated, however the following still fail with the same errors as before.
      2. GFM2 --> shows still in SW Update Tab
      3. PCM -- does NOT show in SW Update Tab, but pops up when attempting to update GFM2
  2. TCU Update
    1. USB created fine, got the message to turn vehicle off and wait 10 min with door open, did this, returned and got update successful
    2. Then FDRS was validating after this and I got the same error as GFM2:
      1. Procedure Unsuccessful - Client received SOAP Fault from Server: SC-UE-UNKNOWN FSP ERROR OCCURRED

And now I'm getting "StatusCode 500, Error: VM-VM-UE-UNKNOWN FDSP ERROR OCCURRED" when trying to load my vehicle in FDRS. Sounds like these are related, so issues with FDRS? I'm glad I bought a 2 day pass if so....
 

Bandit216

Well-known member
First Name
John
Joined
May 19, 2021
Threads
13
Messages
168
Reaction score
328
Location
Alaska
Vehicles
Mach E GTPE, Lightning Lariat
The all lights out is an interesting feature.
It would be very useful when I need to run pro power on campground or at home.
Hmm. I was able to enable a lights out remote start capability using Forscan on my Mach E. It even sets the center screen to "calm" mode so you don't have outside lights off with a bright display on in the interior. Haven't tried looking for it on my Lightning.
 
  • Like
Reactions: GDN

Mike G

Well-known member
First Name
Mike
Joined
Jan 6, 2022
Threads
17
Messages
1,014
Reaction score
1,216
Location
N. AL, USA
Vehicles
2022 F-150 Lightning, 2023 Mach-E GT-PE
Alright, so I just made the plunge into FDRS and successfully got the date updated for my BC hands-free maps (I haven't tested by driving hands-free yet in this vehicle) and an APIM update to Revision 610.

However, I did run into several failures and made various attempts to overcome them, but have not been successful yet.

  1. PCM Update --> This contained a chain of updates and I noticed the following failures:
    1. 1st Attempt (connected via USB 3.0 Hub because GWM required USB)
      1. BECM
        1. Procedure Unsuccessful - FlashSoftware
        2. Security access failure
      2. GFM2
        1. Procedure Unsuccessful - Client received SOAP Fault from Server: SC-UE-UNKNOWN FSP ERROR OCCURRED
      3. SOBDMB
        1. Procedure Unsuccessful - MainUpdateProcess
        2. Failed to restore module configuration
      4. ABS
        1. Procedure Unsuccessful - MainUpdateProcess
        2. Failed to restore module configuration
      5. SOBDMC
        1. Procedure Unsuccessful - MainUpdateProcess
        2. Failed to restore module configuration
      6. PCM
        1. Procedure Unsuccessful - GetFlashActionPartNumbers
        2. Unable to obtain Flash Action part numbers!
    2. 2nd Attempt (removed USB 3.0 Hub after several re-attempts before)
      1. Many of the modules above updated, however the following still fail with the same errors as before.
      2. GFM2 --> shows still in SW Update Tab
      3. PCM -- does NOT show in SW Update Tab, but pops up when attempting to update GFM2
  2. TCU Update
    1. USB created fine, got the message to turn vehicle off and wait 10 min with door open, did this, returned and got update successful
    2. Then FDRS was validating after this and I got the same error as GFM2:
      1. Procedure Unsuccessful - Client received SOAP Fault from Server: SC-UE-UNKNOWN FSP ERROR OCCURRED

And now I'm getting "StatusCode 500, Error: VM-VM-UE-UNKNOWN FDSP ERROR OCCURRED" when trying to load my vehicle in FDRS. Sounds like these are related, so issues with FDRS? I'm glad I bought a 2 day pass if so....
It's Sunday morning and the Ford server is down for maintenance right now. Should be back up in an hour or so.
 

Sponsored

ziptbm

Well-known member
Joined
Jan 4, 2023
Threads
7
Messages
72
Reaction score
33
Location
Michigan
Vehicles
'22 MME GT & '22 F150 Lightning Lariat ER
It's Sunday morning and the Ford server is down for maintenance right now. Should be back up in an hour or so.
Thank you for the confirmation. It was online this AM as I updated a 2nd GWM this morning, but as I shared in our DM, it completely crashed in the middle of my APIM. I thought it was my computer, but I haven't been able to get connected back online in the last 20 minutes.
 

ytwytw

Well-known member
Joined
Jan 24, 2023
Threads
12
Messages
132
Reaction score
73
Location
Toronto, Canada
Vehicles
2023 F150 Lighting ER Lariat
@Mike G Can you please help to check if there are new updates for my VIN?
1FTVW1EV5PWG02527

I did a full upgrade a month ago, but at the time there are no APIM updates for me, hopefully there are the UI available for me... also modem updates.
 

Mike G

Well-known member
First Name
Mike
Joined
Jan 6, 2022
Threads
17
Messages
1,014
Reaction score
1,216
Location
N. AL, USA
Vehicles
2022 F-150 Lightning, 2023 Mach-E GT-PE
@Mike G Can you please help to check if there are new updates for my VIN?
1FTVW1EV5PWG02527

I did a full upgrade a month ago, but at the time there are no APIM updates for me, hopefully there are the UI available for me... also modem updates.
You do have that that Sync (APIM) update waiting on you. :cool:

That's it so far. After the APIM update you will see a GWM pop up.
 

Sponsored

Mike G

Well-known member
First Name
Mike
Joined
Jan 6, 2022
Threads
17
Messages
1,014
Reaction score
1,216
Location
N. AL, USA
Vehicles
2022 F-150 Lightning, 2023 Mach-E GT-PE
Does USB3 hard drive work? I have one that support up to 1000MB/s
Should be a USB 3.0 thumb drive formatted as exFat, default allocation block size, minimum capacity of 32GB. I have no idea if the truck's USB port can power a mechanical portable hard drive. I've never tried that. It would have to be formatted as exFat, I know that.
 

ytwytw

Well-known member
Joined
Jan 24, 2023
Threads
12
Messages
132
Reaction score
73
Location
Toronto, Canada
Vehicles
2023 F150 Lighting ER Lariat
Should be a USB 3.0 thumb drive formatted as exFat, default allocation block size, minimum capacity of 32GB. I have no idea if the truck's USB port can power a mechanical portable hard drive. I've never tried that. It would have to be formatted as exFat, I know that.
It's nvme SSD with USB 3.2 support, should be super fast.
Thanks for the info about exfat, otherwise I will do fat32 and getting problems
 

Sepi

Member
Joined
Feb 24, 2023
Threads
0
Messages
15
Reaction score
4
Location
California
Vehicles
Ford F-150 Lightning Platinum
This guide outlines steps to set up your computer and how to update software in your ECU modules using Ford OEM FDRS software

DISCLAIMER: I have updated many modules using the procedure below without any major issues and literally zero failures. That does not mean failure cannot happen. Flashing ECU modules is a dangerous operation. DO THIS AT YOUR OWN RISK! I will take no responsibility for any damage to your vehicle caused by the below described procedure

Tools you will need:

- Windows PC with 4GB RAM or greater, running Windows 10 or Windows 11
- VCI Interface preferably Mongoose-Plus J2534 (can be purchased from Amazon here)
or as an alternate (budget) solution VXDIAG VCX Nano (can be purchased from Amazon here)
- USB Flash drive 32GB or larger (must be formatted to exFAT)
- 12V Automotive Battery Charger/Maintainer (I used this one from Amazon)

Software you will need:

- Driver software for your VCI interface (steps outlined for each device below)
- Ford Diagnostic & Repair Software (commonly known as FDRS)

Installation and Setting up Mongoose-Plus J2534 interface:

NOTE: Follow the steps below ONLY if you own the Mongoose-Plus J2534 interface

1) Download the OPUS IVS driver for your Mongoose-Plus device from here.
2) Connect your Mongoose-Plus device to your PC and launch the installer. You should be presented by the following screen:

1647049166155.png


3) Hit Install to start the installation process, when prompted, activate the device!

1647049226735.png


Installation and Setting up VXDIAG VCX Nano interface:

NOTE: Follow the steps below ONLY if you own the VXDIAG VCX Nano interface

1) Download the latest VX Manager installer from here.
2) Start VX Manager installation, when prompted select PASSTHROUGH - J2534

NOTE: Your AV might flag certain driver files as malware, this is however a false alarm. You may need to add these files to your AV exclusion list in order to complete the installation

Untitled.png


NOTE: Do not select FORD/MAZDA - IDS. Using this IDS emulation can brick your ECU module during the update process (learned the hard way)

3) Connect VCX Nano device to your PC using the supplied USB cable and launch VX Manager. The tool should recognize the device. If there is a device firmware available, update the device firmware

VXDIAG.png


FDRS Software Installation

1) Download and install FDRS software from here. You will need a license to run this software and can be purchased here (2-day FDRS license cost $50)
2) Launch FDRS, you will be prompted to enter the license that you have just purchased.
3) Register an account (if you don't have one) on Motorcraft website here.
4) Log into FDRS using your Motorcraft credentials. Make sure you select Non-Dealer Motorcraft as User Type

LOGIN.png


5) Connect your VCI device to your truck's ODBII port and connect the USB cable to the PC running FDRS. Once FDRS Device Manager pops up, make sure you select Other Device, in the drop-down dialog:

Select Drew Technologies Inc. - Mongoose-Plus Ford2 if you own the Mongoose-Plus VCI device

1647049312011.png


Select VXDIAG - J2534 if you own the VCX Nano device

DEVMANAGER.png


After this you should be greeted with this screen, meaning you are ready to go!

The icons at the bottom should be all green with battery voltage shown

VINREAD.png


Running Network Test (Initial Scan)

WARNING: DO NOT RUN NETWORK SCAN IF YOU OWN VCX NANO DEVICE AS IT WILL CAUSE AS-BUILT DATA CORRUPTION. GO -> HERE <- FOR MORE INFORMATION AND HOW TO PROCEED WITH MODULE SW UPDATE IF YOU OWN THIS DEVICE

NOTE: if you own the Mongoose-Plus device, it is safe to proceed

1) Turn Ignition On, Engine Off
2) Click Read VIN from vehicle
3) Click Go to initiate Network Scan

Once completed a new tab called Toolbox will appear at the top of your FDRS screen:

SWUPDATE.png


On the left hand side you will see all modules detected on your truck. The ones that responded positively will be marked green. On the right hand side notice the SW Updates tab. Head over here to see all available SW updates for your modules.

Module SW Update Procedure

WARNING: DO NOT UPDATE THE CCM MODULE USING THE VCX NANO DEVICE. READ APPENDIX V FOR DETAILS

1) Head over to SW Updates tab in the FDRS Toolbox window.
2) If there are updates available, hit the Download button. The tool will download the necessary tools needed for the module update.
3) Once download completes the button turns green with a text "Run".

IMPORTANT: Before you proceed to the next step, connect your truck to external power supply (a good battery charger/maintainer as one listed above will do the job). DO NOT connect the negative (black) charger clamp directly to the battery monitoring sensor, it must be connected to an engine or chassis ground in order to bypass the BMS circuitry (see example here). Do not proceed unless you have solid 12.5V or more showing on your ODBII port.

4) Run the SW Update procedure and follow the on-screen prompts very carefully

Be patient, some modules take long time to update. This is especially true for IPMA module which takes almost 3 hours to complete. Therefore, it is very important to have your truck connected to external power supply (battery charger/maintainer)

NOTICE FOR FORSCAN USERS: FDRS will knock out your recent FORScan changes from your modules you are updating. It reloads your As-Built (AB) data at the end of the SW update procedure. Make sure you back-up your FORScan changes and load them back after you are done with SW updates. By time your FORScan changes get propagated to your AB data set on FORD servers, so this would not be an issue. This would only affect users performing FORScan changes and running module SW udate within short period of time. I am suspecting, that receiving OTA shortly after FORScan changes would have same effect.

If you have any questions or concerns feel free to reach out to me over DM. If I don't reply in time, reach out to other experts including, but not limited to @Jesse-Infotainment , @Bob_Mac, @JEB or @Snakebitten.

Also, I would strongly suggest to follow @Bob_Mac document, outlining the latest updates and shared knowledge related to this process. You can access his guide here.
Wondering if you have experience I had a failed update on 22nd of APIM from OTA. Took it in to the dealership today they tried to manually update APIM twice and failed both times. They said it was likely corrupted and they'd have to rewrite entire system. I saw in the guide there's a TSB saying GWM has to be updated prior to APIM not sure if dealership did this so I might call tomorrow to check. I was thinking at this point dealership told me they'd need it 8+ hours to do the update and only open M-F while I'm working that I might just buy the Mongoose and do this myself.
 

Sepi

Member
Joined
Feb 24, 2023
Threads
0
Messages
15
Reaction score
4
Location
California
Vehicles
Ford F-150 Lightning Platinum
Wondering if you have experience I had a failed update on 22nd of APIM from OTA. Took it in to the dealership today they tried to manually update APIM twice and failed both times. They said it was likely corrupted and they'd have to rewrite entire system. I saw in the guide there's a TSB saying GWM has to be updated prior to APIM not sure if dealership did this so I might call tomorrow to check. I was thinking at this point dealership told me they'd need it 8+ hours to do the update and only open M-F while I'm working that I might just buy the Mongoose and do this myself.
Apparently dealership saying GWM isn't needed it was already updated OTA... we'll see ordered cable today I can't leave my truck for 8+ hours with them in a work week.
Sponsored

 


 


Top