Jmendoza
Well-known member
- First Name
- JORGE
- Joined
- Nov 16, 2022
- Threads
- 2
- Messages
- 52
- Reaction score
- 50
- Location
- Washington
- Vehicles
- 2021 f150 Lariat
Unless your on sync version 22293 rev 610. Prob will have another APIM update.
Sponsored
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
PCM and CCM.
cparuch
Member
I'm not on that version and my hope was that there were more updates available but they were showing last week. I'd hate to spend another $50 on the two day license if they aren't showing.
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
Hopefully Santa will bring you a mongoose ?
Looks like something is going on updates are not being released becasue you are still on an OLD Gateway version. My question would be if you had anything done at the dealer and they possibly did not PMI it OR the nano is sending back corrupted info and the servers do not know what to do with it.
That was part of the reason people stopped using the nano is it would corrupt AS build data.
You may try a couple of network scans but it probably wont help. Ive seen A LOT of issues witht he nano as of late.
Sponsored
cparuch
Member
I did have 22B08 done in September. After that, I had a few OTA updates but it stalled at 2.7.4. Any suggestions on my next steps. I have no issue getting the mongoose if that may fix the issue. Last time it was at the dealer, they refused to do any of the updates and didn't seem to have any clue what I was talking about. I'm at a loss at this point.
Your gateway is way behind. For whatever reason they are not releasing the next update. I cant sit here and gicve you a 100% guarantee the mongose will resolve it but there is something preventing the release and from what I know and have seen the Nano corrupts that data submitted to ford. If ford gets a inaccurate file submission it will prevent a update release
So I have confidence the mongoose is the correct move. Its safer that is for sure
this is how your as build looks to ford right now.. some of it
1>JX7T-14C302-GA</F121><F124>ML3T-14C303-FDE</F124><F188>JX7T-14C302-BS</F188><F18C>M7AF519632</F18C></NODEID><NODEID>730<F10A>ML34-14D007-BGH</F10A><F110>DSM849-AL L34-3F9</F110><F111>ML34-14F079-AC</F111><F113>ML34-3F964-BN</F113><F124>ML34-14D004-BM</F124><F188>ML3V-14D003-BC</F188></NODEID><NODEID>732<F110>DSML3P-7P427-AG</F110><F111>ML3P-7P474-AC</F111><F113>ML3P-7P427-AJ</F113><F124>ML3P-7P471-AK</F124><F167>18031910</F167><F188>ML3P-7P470-AK</F188><F18C>03262021TN052801</F18C></NODEID><NODEID>733<F10A>ML3T-14C651-AF</F10A><F110>DSML3T-18C612-AD</F110><F111>ML3T-14F165-BD</F111><F113>ML3T-18C612-BE</F113><F188>ML3T-18D619-BC</F188></NODEID><NODEID>737<F10A>ML3T-14C635-HH</F10A><F110>DSML3T-14B321-CB</F110><F111>ML3T-14F136-YC</F111><F113>ML3T-14B321-YD</F113><F141>000000AA434835</F141><F142>000000AE648945</F142><F143>C100E723353400</F143><F144>C6C37ABD2DA700</F144><F145>C6C37ABD3B4900</F145><F146>42423030363339333434333230300000</F146><F14B>41344333443837333132363400000000</F14B><F14D>42423030363339333434333230300000</F14D><F14E>00000000000000000000000000000000</F14E><F14F>00000000000000000000000000000000</F14F><F150>00000000000000000000000000000000</F150><F188>ML3T-14C028-CA</F188><F18C>3019169634470000</F18C><F190>1FTEW1EP2MFA81165</F190></NODEID><NODEID>740<F10A>MU5T-14C637-AS</F10A><F110>DSMU5T-14B531-AL</F110><F111>MU5T-14F142-BG</F111><F113>MU5T-14B531-BL</F113><F160>100400</F160><F161>090001</F161><F188>MU5T-14C064-BM</F188><F18C>374455009HB</F18C></NODEID><NODEID>741<F10A>MU5T-14C639-AS</F10A><F110>DSMU5T-14B533-AM</F110><F111>MU5T-14F144-BG</F111><F113>MU5T-14B533-BL</F113><F159>060500</F159><F160>100400</F160><F161>090001</F161><F188>MU5T-14C108-BM</F188><F18C>37445500XVB</F18C></NODEID><NODEID>751<F111>ML38-EB T-14G09</F111><F113>ML3T-15K619-JA</F113><F188>ML3T-14G090-CA</F188></NODEID><NODEID>754<F110>DSMU5T-14HJX7T-18074-AAX</F110><F111>MU5T-14H089-AAK</F111><F113>MU5T-14H074-AAS</F113><F120>MU5 T-14H090-ADG</F120><F121>MU5T-14H090-BAY</F121><F16C>MU50-AAG T-14H100-AAJ</F16C><F17F>1TV150RE</F17F><F188>MU5T-14H085-DJ</F188><F18C>ENMHF21105074051</F18C></NODEID><NODEID>760<F10A>PL34-14C602-PDA</F10A><F110>DSML34-2C219-AJ</F110><F111>ML34-14F065-AD</F111><F113>ML34-2C219-AL</F113><F169>ML34-2D335-AS</F169><F17F>1CL05RN4</F17F>
All of those spaces are a problem. The mongoose doesnt have that issue.
Rineland
Well-known member
Would someone be willing to check for module updates for my VIN?
1FTEW1EP3MFA75486
I know the Mongoose is the preferred adapter, but I'm really just looking to perform the latest APIM update and it's not really worth the cost of the Mongoose. The nano on the other hand... is tempting at that cost. Researching this thread it seems the nano will work fine for an APIM update as long as I'm careful to not perform a network scan in FDRS and I don't have to program the CCM before the APIM update is eligible.
Thanks!
1FTEW1EP3MFA75486
I know the Mongoose is the preferred adapter, but I'm really just looking to perform the latest APIM update and it's not really worth the cost of the Mongoose. The nano on the other hand... is tempting at that cost. Researching this thread it seems the nano will work fine for an APIM update as long as I'm careful to not perform a network scan in FDRS and I don't have to program the CCM before the APIM update is eligible.
Thanks!
dolsen
Well-known member
Read the post just above yours and think about the comment in bold again. I am not saying you will have issues, but I believe it is worth the money to get the Mongoose.
That's my 2 cents anyways
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
...and FDRS does a network scan as soon as you connect....so how were you going to get around that?
Sponsored
speedracercjr
Well-known member
While I'm not condoning it, you can technically connect via VIN lookup first, then hook up your Nano and install a module that way. Odds are at some point you'll mess up though and a network scan will be completed and send dirty data to Ford.
Rineland
Well-known member
If this is the case, why is the adapter still listed as a viable choice with explicit instructions on how to work around its issues (i.e. opening FDRS before connecting and manually entering the VIN to collect As Built Data from the cloud vs. connecting the cable and performing a network scan).
Also, I was under the impression the APIM update is through a USB stick plugged into the port near the HVAC controls and that the data isn't programmed via the nano adapter. If I don't have any predecessor modules that need to be updated before the APIM update, would I not just be able to update the APIM via USB?
Rineland
Well-known member
This was my understanding based on what I read and why I was asking for available module updates. My truck received 3.5.2 so I’m not expecting there to be a ton of updates and was hoping to be able to just do the latest APIM. But before spending the money on the nano I figured I’d ask in this forum what’s showing for updates on my truck. If there are other modules that need updating then I’d skip the whole nano idea and either wait for the OTA or pony up for the mongoose if Ford can’t seem to get it together in a timely fashion. The mongoose is a big spend and unless I find some other Gen 14 owners near me to spread the cost, I’ll probably just become very very patient for an OTA.
speedracercjr
Well-known member
do whatever floats your boat, just know you’ll likely be in a worse spot after the update if you get caught by the nano corruption.
Rineland
Well-known member
I guess that’s another aspect that maybe I haven’t read enough of the forum to have all the info yet. But, I thought the nano corruption was limited to the data that gets sent to Ford via FDRS (hence avoiding the network scan workaround?), it does not impact the as built data in the truck. Is that valid? Or has it been determined that corrupt data could be written to the truck as a result of using the nano? In which case, yeah, the nano gets a big NO from me.
Sponsored
