ECU module programming guide using FDRS

[Bob_Mac]

It's probably safe to do it that way since you haven't made the OTA updates yet, but there is a chance something could still be different. You an actually open those ABT files up in a text editor and see what the values were, and compare them to what is in for scan now.

There is a utility linked below that you can use to make the ABT files a little easier to read:

https://forscan.org/forum/viewtopic.php?t=10099

@FordConvert
It is NOT! Only revert the changes you made, do NOT do a full "Load All" and write all! Prior OTA updates may have made changes you're unaware of and this can make matters worse!

Sponsored

 

[MikeYQM]

Well crap...my IPMA failed it's update some point after 70% in the big block 1 of 2 portion of the update. No clue why. Voltage is at 13. Trying again (using a Mongoose)....

Failed again...Now I'm getting this:

How did you get past this?

 

[Sbdavis1]

For those Who were fortunate to get past 1.7.1 via OTA, should we revert our Forscan changes before anything else gets updated via OTA? I have anti-glare headlights, double honk disabled and cameras in motion via ForScan but don’t want any of that to mess up the updates supposedly coming via OTA.

 

[Ajzride]

I can say that my double-honk and cameras in motion don't appear to have messed anything up. But I think the Anti-glare is in the IPC, which is what has caused the headaches, so I would definitely undo those.

It appears that if you corrupted your IPC (as I have done) you will have to ship your IPC out for repair to recover. So roll back any IPC changes in Forscan to avoid that mess.

 

[Ajzride]

How did you get past this?

I believe myself and Platinum Peasant had that error and we changed laptops and it cleared up. uninstalling FDRS and deleting all data and re-installing might work as well. Be sure to release your license before you uninstall.

 

[MikeYQM]

I believe myself and Platinum Peasant had that error and we changed laptops and it cleared up. uninstalling FDRS and deleting all data and re-installing might work as well. Be sure to release your license before you uninstall.

It’s not me, it’s a ford tech who got stuck

 

[MikeYQM]

Can anyone run my vin for updates, please?

1FTFW1ED2MFB10996

 

[Ajzride]

Can anyone run my vin for updates, please?

1FTFW1ED2MFB10996

 

[heffer86]

I am up-to-date with my modules updates via FDRS. I got a Motorcraft PTS subscription (OASIS) to see if I am even being sent OTA updates so hopefully I don't need to do this forever. When I get into my vehicle data I get this message below. In the past it would populate all my data here. I have tried difference browsers and waited overnight. Still same result. Anyone else who has done updates tried tried the PTS site? If someone else has a PTS subscription and willing to try on their end let me know.

 

[christophers]

I can say that my double-honk and cameras in motion don't appear to have messed anything up. But I think the Anti-glare is in the IPC, which is what has caused the headaches, so I would definitely undo those.

It appears that if you corrupted your IPC (as I have done) you will have to ship your IPC out for repair to recover. So roll back any IPC changes in Forscan to avoid that mess.

My anti-dazzle lights were done in ForScan several weeks ago, and I did pre-1.7.1 all the way to BC with no issues.

EDIT: just because i didnt have issues doesn't mean you should follow my example take the time to do things the right, safe way and you will have minimal to no issues.

 

[ksimon123451]

I went through the process of trying to restore APIM with the new process Ford just released to kicking off the usb update from 1.7. I started it and went through till it asked me to connect the usb to the truck I said yes, I tried just using a USB C from my laptop to the USB C port on the truck as I dont have the adapter. It said that it cant find a connection so I aborted it. Then when I checked my version on the screen under settings it was no longer blank so I inserted the USB drive that has the APIM update and it started after 10 minutes. Don't know if it was a fluke but it worked for me.

 

[Ruffiano99]

Think it will be safe to attempt this new TSB with a nano?
nothing has worked for me yet. I made changes in forscan months ago… double honk, pedestrian sounder, global windows, i had messed around with cameras at speed but it never worked, i cant remember if i set that back to original values.

 

[RellIk&5]

It's been over a week for me since I applied my last batch of available updates. My rev is still 244. Can someone please check this vin to let me know if there is anything new aside from the GSM?

1FTFW1E86MKD74376

Thanks!

 

[christophers]

Think it will be safe to attempt this new TSB with a nano?
nothing has worked for me yet. I made changes in forscan months ago… double honk, pedestrian sounder, global windows, i had messed around with cameras at speed but it never worked, i cant remember if i set that back to original values.

Honestly, I wouldn't attempt anything with a Nano at this point.

 

[Ajzride]

It's been over a week for me since I applied my last batch of available updates. My rev is still 244. Can someone please check this vin to let me know if there is anything new aside from the GSM?

1FTFW1E86MKD74376

Thanks!

Still just the GSM for you.

Sponsored