ECU module programming guide using FDRS

[Snakebitten]

I'm driving a Lightning now (it happens to already be in the shop - different thread and forum), but since these trucks and the last couple of years of the ICE 150 depend so much on SW it just shows how Ford is missing the mark. They've had 10 years to copy and study Tesla and they are still so far behind they can't even see the taillights. if you want to make excuses for them, we will always get what we already have.

They have a chance in '23 as they upgrade to the Android OS or one more as they completely revamp the EV version. Will see if they will compete or fold.

What excuses?

Just pointing out that there are modules that can't even be communicated with via current OTA, so you'd have to visit the dealership. And there may be an update that might only need to be applied if the vehicle is experiencing a particular symptom.

Tesla didn't exactly get off to a smooth start in their first year of their version OTA. And they aren't immune to issues either.

Sponsored

 

[JEB]

Until I add the license I'm not able to interact with the program at all. It just keeps giving me the 'unable to verify license' message. I've been cutting/pasting it as well as double checking to make sure there aren't any typos but no bueno.

Only thing I can think of is that the code you received is bad for some reason. If you are clicking Add License and getting an unable to verify message, I don’t know what to tell you. Did you buy it here?: http://www2.helminc.com/ngsm/login....4119969BB71E08853AE2&from=ford&src=motorcraft. If so, you can log in and retrieve your code and try again.

Did you by chance try the code on another computer? If you did, you have to release it on the other computer before you can reuse it. The code is attached to the computer, not the user.

 

[ryanc111]

Only thing I can think of is that the code you received is bad for some reason. If you are clicking Add License and getting an unable to verify message, I don’t know what to tell you. Did you buy it here?: http://www2.helminc.com/ngsm/login....4119969BB71E08853AE2&from=ford&src=motorcraft. If so, you can log in and retrieve your code and try again.

Did you by chance try the code on another computer? If you did, you have to release it on the other computer before you can reuse it. The code is attached to the computer, not the user.

Yep, that’s where I bought it. And if I go look in to my order history it shows that that license is still available so it doesn’t appear to have been attached anywhere yet.

I may try and scare up a different computer to see if I can get it to work there. Short of that I need to wait until business hours on Monday to get their assistance. Hopefully they will re-issue the license once the issue is resolved since this one will be expiring then.

Thanks for the assistance JEB, greatly appreciated.

 

[speedracercjr]

Yep, that’s where I bought it. And if I go look in to my order history it shows that that license is still available so it doesn’t appear to have been attached anywhere yet.

I may try and scare up a different computer to see if I can get it to work there. Short of that I need to wait until business hours on Monday to get their assistance. Hopefully they will re-issue the license once the issue is resolved since this one will be expiring then.

Thanks for the assistance JEB, greatly appreciated.

Do you happen to have a PiHole running on your network?

Mine was blocking the registration server and I had to white list that domain.

 

[Diligenthunter]

Other devices will not show up for me in FDRS device manager, not sure what I’m doing wrong or was there an update?

 

[JEB]

Other devices will not show up for me in FDRS device manager, not sure what I’m doing wrong or was there an update?

What VCI are you using? Did you run the installation program for it before running FDRS? You need to install the drivers before FDRS will recognize the device.

If you are using the Mongoose, you can download the set up program here: https://www.opusivs.com/support/downloads?hsLang=en. Then go to the support tab and make sure the drivers are working correctly. Then go back to FDRS and see if the Mongoose is now recognized.

 

[Diligenthunter]

What VCI are you using? Did you run the installation program for it before running FDRS? You need to install the drivers before FDRS will recognize the device.

If you are using the Mongoose, you can download the set up program here: https://www.opusivs.com/support/downloads?hsLang=en. Then go to the support tab and make sure the drivers are working correctly. Then go back to FDRS and see if the Mongoose is now recognized.

Using vcx nano, installed software and drivers for Vci.

 

[tonesto7]

What VCI are you using? Did you run the installation program for it before running FDRS? You need to install the drivers before FDRS will recognize the device.

If you are using the Mongoose, you can download the set up program here: https://www.opusivs.com/support/downloads?hsLang=en. Then go to the support tab and make sure the drivers are working correctly. Then go back to FDRS and see if the Mongoose is now recognized.

I think your missing the J2534 pass-through software

 

[Diligenthunter]

I think your missing the J2534 pass-through software

I installed the j2534 software during the install of VX manager.

 

[JEB]

I installed the j2534 software during the install of VX manager.

Run the Mongoose set up software I provided the link to. It has the drivers specific to the Mongoose. The VX Manager won’t get you the Mongoose drivers.

 

[JEB]

Using vcx nano, installed software and drivers for Vci.

Ah. I wouldn’t advise using the Nano, particularly if your truck has BlueCruise, but if that’s what you have you should take another read through the instructions. It sounds like you missed a step somewhere. I remember the Nano installation being less than straightforward. But @iceman77 did a good job of laying everything out.

 

[Diligenthunter]

Ah. I wouldn’t advise using the Nano, particularly if your truck has BlueCruise, but if that’s what you have you should take another read through the instructions. It sounds like you missed a step somewhere. I remember the Nano installation being less than straightforward. But @iceman77 did a good job of laying everything out.

I’ll uninstall everything and try again tomorrow.

 

[speedracercjr]

Your weekly reminder to turn off auto-updates:

https://www.f150gen14.com/forum/threads/screen-issues-on-12-inch-after.12075/

 

[mflynndelta]

Your weekly reminder to turn off auto-updates:

https://www.f150gen14.com/forum/threads/screen-issues-on-12-inch-after.12075/

wow after 30 days July 7th till Aug 7th finally my automatic downgrade OTA fianlly expired Thanks ford !

 

[JDPEagle]

After going through the aforementioned APIM update processes and procedures (and leaving the USB thumb drive in the console), the upgrade appeared to "kick-off" yesterday evening (after two days). Once the screen asked for the system restart, I shut down the truck, got out, locked the doors and went inside the house (while leaving the USB thumb drive undisturbed in the console). I returned 15-minutes later to restart the truck. To my total disappointment, nothing appeared to have changed; no SYNC version data, automatic update sliders greyed out, and no indication that the update was complete. I drove around for about 45 minutes in the event that things were still processing, but no joy.

Below is the "system updating" screen that I was watching prior to my complete heartbreak. Has this happened to anyone else?

Sponsored