Home
What's new
Latest activity
Authors
Store
Latest reviews
Search products
Forums
New posts
Search forums
What's new
New posts
New listings
New products
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Log in
Register
Cart
Cart
Loading…
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Change style
Contact us
Close Menu
Forums
Cobra Forums
2013-14 Shelby GT500
Diagnostic software and tools to repair and maintain our shelby GT500'S: Ford IDS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="JAJ" data-source="post: 16674981" data-attributes="member: 131874"><p>It took me a bit of time to reply because I was trying to figure out how I could give you a reply that was actually helpful. If you look at other forums like M6G there are long threads on how to use Forscan. For what you're doing, it's relatively easy as far as using it is concerned. The problem is figuring out what digits you have to change in order to fix a mismatched VIN.</p><p></p><p>The VIN is stored as a set of hexadecimal characters - hex is a counting system that computers use that counts to 16 rather than 10. Computers love it, but it gives people headaches. In the file that Forscan edits, the hex characters that represent the VIN are not in a nice row - they're usually spread across multiple rows. </p><p></p><p>Now, I've been messing with Forscan for the last five years and I've found some really useful resources out there. If you Google "Forscan for Explorer" you'll find some charts with the hex values for various modules in the Explorer. Thing is, the charts work for Mustangs as well as Explorers - same electronic modules, same code. So, to find out how to change the VIN in the module you're just updated, find the module in the table for the Explorer, find which strings of data contain the VIN and use Forscan replace the wrong VIN with the correct one. The easiest way to get the correct letters for your VIN is to make a backup copy of the module as-built file before you start. It'll have the right VIN, so it's just a matter of updating those few strings to fix the mismatch.</p><p></p><p>How's that - clear as mud, no doubt.</p></blockquote><p></p>
[QUOTE="JAJ, post: 16674981, member: 131874"] It took me a bit of time to reply because I was trying to figure out how I could give you a reply that was actually helpful. If you look at other forums like M6G there are long threads on how to use Forscan. For what you're doing, it's relatively easy as far as using it is concerned. The problem is figuring out what digits you have to change in order to fix a mismatched VIN. The VIN is stored as a set of hexadecimal characters - hex is a counting system that computers use that counts to 16 rather than 10. Computers love it, but it gives people headaches. In the file that Forscan edits, the hex characters that represent the VIN are not in a nice row - they're usually spread across multiple rows. Now, I've been messing with Forscan for the last five years and I've found some really useful resources out there. If you Google "Forscan for Explorer" you'll find some charts with the hex values for various modules in the Explorer. Thing is, the charts work for Mustangs as well as Explorers - same electronic modules, same code. So, to find out how to change the VIN in the module you're just updated, find the module in the table for the Explorer, find which strings of data contain the VIN and use Forscan replace the wrong VIN with the correct one. The easiest way to get the correct letters for your VIN is to make a backup copy of the module as-built file before you start. It'll have the right VIN, so it's just a matter of updating those few strings to fix the mismatch. How's that - clear as mud, no doubt. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Cobra Forums
2013-14 Shelby GT500
Diagnostic software and tools to repair and maintain our shelby GT500'S: Ford IDS
Top