Oakstone
Well-known member
- Joined
- Sep 10, 2022
- Threads
- 25
- Messages
- 273
- Reaction score
- 145
- Location
- Victoria, BC Canada
- Vehicles
- 22 F-150 PB XLT 302A
- Thread starter
- #1
Heya,
I am about to embark on the FORSCAN adventure for the first time. I have seen instructions that go two ways. One is to go to all AS BUILT modules in the truck and back them all up one at a time. The other is to go to Index - FordServiceInfo.Com (motorcraftservice.com) enter your VIN and download a .ab file.
I have done the latter and have the .ab file saved. Is that enough for me to start making FORSCAN changes without going through the long process of backing up every module individually?
My thought process is to back up only the modules I'm going to make changes in (along with notes in a spreadsheet), so I can restore an individual module if I want to, but have the .ab file as a general backup.
I will totally do "every AS BUILT" if that's the best practice, but figured if I could save some time and still be protected, I'd do the more incremental way.
Thoughts?
Thanks!
I am about to embark on the FORSCAN adventure for the first time. I have seen instructions that go two ways. One is to go to all AS BUILT modules in the truck and back them all up one at a time. The other is to go to Index - FordServiceInfo.Com (motorcraftservice.com) enter your VIN and download a .ab file.
I have done the latter and have the .ab file saved. Is that enough for me to start making FORSCAN changes without going through the long process of backing up every module individually?
My thought process is to back up only the modules I'm going to make changes in (along with notes in a spreadsheet), so I can restore an individual module if I want to, but have the .ab file as a general backup.
I will totally do "every AS BUILT" if that's the best practice, but figured if I could save some time and still be protected, I'd do the more incremental way.
Thoughts?
Thanks!
Sponsored