Forscan applications
#501
Member
#503
The FORScan Guy
I emailed the developers about the PIDs in APIM that should be stated that they are for Sync 2 and not Sync 3. They were ready to implement a change that would distinguish what is shown to Sync 2 vs Sync 3 people based on year of the truck, but apparently some 2016 models can still have Sync 2 so they're working on another way; either auto-detection or simply naming the PIDs listed as for Sync 2/3. I submitted them log & dump files from my FORScan at their request so they can try to implement some kind of auto-detection.
#504
Old Fart
I emailed the developers about the PIDs in APIM that should be stated that they are for Sync 2 and not Sync 3. They were ready to implement a change that would distinguish what is shown to Sync 2 vs Sync 3 people based on year of the truck, but apparently some 2016 models can still have Sync 2 so they're working on another way; either auto-detection or simply naming the PIDs listed as for Sync 2/3. I submitted them log & dump files from my FORScan at their request so they can try to implement some kind of auto-detection.
Do you know of a way to print out or export the "as built" file to a human readable so that I can compare what I should have vs what I have now?
Or even someway of retrieving my profile I created prior to making any changes?
I would like to return things as they were if possible even it means losing the heated/cooled seats.
I had no problem with the double honk as that was entered via hex.
#505
I own a 2014 Escape with sync II. What exactly is FORSCAN? God knows I read this wrong when Is aw the thread. Go ahead and shoot me for being that guy~
#506
Senior Member
iTrader: (14)
I appreciate that. Hopefully that will help others avoid some future issues.
Do you know of a way to print out or export the "as built" file to a human readable so that I can compare what I should have vs what I have now?
Or even someway of retrieving my profile I created prior to making any changes?
I would like to return things as they were if possible even it means losing the heated/cooled seats.
I had no problem with the double honk as that was entered via hex.
Do you know of a way to print out or export the "as built" file to a human readable so that I can compare what I should have vs what I have now?
Or even someway of retrieving my profile I created prior to making any changes?
I would like to return things as they were if possible even it means losing the heated/cooled seats.
I had no problem with the double honk as that was entered via hex.
#507
Old Fart
The following users liked this post:
SCORGE (06-15-2016)
#508
The FORScan Guy
I appreciate that. Hopefully that will help others avoid some future issues.
Do you know of a way to print out or export the "as built" file to a human readable so that I can compare what I should have vs what I have now?
Or even someway of retrieving my profile I created prior to making any changes?
I would like to return things as they were if possible even it means losing the heated/cooled seats.
I had no problem with the double honk as that was entered via hex.
Do you know of a way to print out or export the "as built" file to a human readable so that I can compare what I should have vs what I have now?
Or even someway of retrieving my profile I created prior to making any changes?
I would like to return things as they were if possible even it means losing the heated/cooled seats.
I had no problem with the double honk as that was entered via hex.
After you return all your modules to the default values, save each as-built module when you're in there with the "save all" button at the bottom of the module and call each one something like BCM-original, APIM-original so you can easily revert in the future.
#509
Old Fart
#510
Just from surfing the thread I assumed it was just something for Sync. seems to be a high-speed OBDII scanner. interesting...