Search results

I only have 1 file on the USB; MU5T-10F906-FDA.VBF which is what F120 should be and is based on what I posted above.

Yes, I just checked FORScan and show 14 blocks

@Jesse-Infotainment below is my IPC info, F113 (Assembly) is off. Any concern with that? <NODEID> 720 <F110>DSML3T-1A292-CCE</F110> <F111>ML3T-14F094-CAB</F111> <F113>ML3 T-10849-CCM</F113> <F120>MU5T-10F906-FDA</F120> <F17F>1PB11BFK</F17F> <F188>MU5T-10F906-FCA</F188>...

Have you looked at what Jesse suggested after you did the PMI?

I saw that as well and again makes me think that the speed issue is the problem with Network Scans and the NANO, FDRS and the FD-CANBUS speed...

Neither can I, I get the message "Cannot reach FDRS servers"

@Jesse-Infotainment , I'll add this to the doc... thx for the update. Question, what adapter did you use to see this issue?

Interesting... my laptop has USB3 on all 3 ports so this brings to question, what is @tonesto7 UCDS specs? I've looked into specs of the Mongoose and they show USB3 cables for the device so this is something else that may lead to the speed issue with the NANO...

FYI SSM 50383 - 10 Jan 2022 - 2021 F-150/Mustang Mach-E - Over-The-Air (OTA) Failed Message In The Center Touchscreen / SYNC Software Does Not Download From The USB Some 2021 F-150/Mustang Mach-E vehicles may display OTA Update Not Successful messages on the vehicle’s center touchscreen. Also...

I decided to get the Mongoose and it'll be here on Wednesday, I am not going to touch the truck or use FDRS until then and hope that the corruption clears up when the truck phones home to the servers. I have until 3/20 to return the Nano since I purchased it from Amazon so there will be time to...

While in the toolbox click the All tab then click on TDM on the left side you should see a new tab show with TRM as it's label now click on TRM - Programmable Module Installation (PMI) then Download and run. Go through the prompts as if you already installed a new module and report back if that...

Wondering? Speed issue?

You should be able to but not tested. Files will be used only when you click on Run

Interesting, can you Message me the exact process so I can test and update the doc? Edit: Don't you mean the BCM (BodyCM)?

You're now thinking what I I'm thinking! I just messaged @tonesto7 to see what his port settings are and to do some more testing with changes that may help things out... You're not adding to complexity ;)

He is still getting corruption but not on the level the Nano has...

Not 100% sure at this point but, the Nano works fine with FORScan so I'm still thinking it's FDRS. Still investigating...

I'm still in the mindset that it's FDRS and how it's handling the J2534 protocol and not specific to the Nano but all J2534 devices. I just spoke with a friend who's a Master Ford Tech and he believes it may be speed related and how fast/slow the data is sent. Lastly, FORScan see the modules...

All, the corruption is back so... disregard the prior post.

What step are you at?