Vlad Soare
Well-Known Member
- Joined
- Jan 21, 2020
- Threads
- 65
- Messages
- 3,168
- Reaction score
- 2,879
- Location
- Bucharest, Romania
- First Name
- Vlad
- Vehicle(s)
- 2020 Mustang GT 6MT
Thanks, JC. I did a search on the F150 forum and found this:
At first glance this looks correct, because my own As-Built data has an E at that spot (which seems to match my car's current configuration, I mean I actually do have everything active except autolock). So I guess I should change that E to F.
But then someone else said that if you change that digit, then you should also change the final one, because that's a checksum. Going from E to F is an increase by 1, so the final digit should also be increased by 1. In my case there's an 8 there, so I take it I should make that a 9.
I've never seen this mentioned before, but it does make sense. Should we calculate and update the last digit every time we do a change?
Edit: never mind that. It seems that ForScan will complain about the checksum being incorrect and will correct it automatically.
At first glance this looks correct, because my own As-Built data has an E at that spot (which seems to match my car's current configuration, I mean I actually do have everything active except autolock). So I guess I should change that E to F.
But then someone else said that if you change that digit, then you should also change the final one, because that's a checksum. Going from E to F is an increase by 1, so the final digit should also be increased by 1. In my case there's an 8 there, so I take it I should make that a 9.
I've never seen this mentioned before, but it does make sense. Should we calculate and update the last digit every time we do a change?
Edit: never mind that. It seems that ForScan will complain about the checksum being incorrect and will correct it automatically.
Sponsored
Last edited: