FORScan - software to enable/disable features in your truck
03-09-2017, 01:03 PM
#7111
Getting ready to try and install my Lariat cluster this weekend. I have already saved my current IPC setting to load to the new cluster. After that do I need to do anything else? I thought I remember seeing something on the spreadsheet about cruise control for people upgrading from XLT to Lariat cluster? Do I need to make that change to get cruise control back or should it be there when I load my IPC setting? Also I shouldn't have a problem following the process to add Engine and Transmission temps above the gauges after that? Finally does the Lariat cluster come default with the navigation directions inside the cluster or is that something I have to add. Thank you in advance!
03-09-2017, 01:13 PM
#7112
Junior Member
Getting ready to try and install my Lariat cluster this weekend. I have already saved my current IPC setting to load to the new cluster. After that do I need to do anything else? I thought I remember seeing something on the spreadsheet about cruise control for people upgrading from XLT to Lariat cluster? Do I need to make that change to get cruise control back or should it be there when I load my IPC setting? Also I shouldn't have a problem following the process to add Engine and Transmission temps above the gauges after that? Finally does the Lariat cluster come default with the navigation directions inside the cluster or is that something I have to add. Thank you in advance!
03-09-2017, 01:25 PM
#7113
I bought the terminal remover that Livin suggested, though now that I've done it, probably didn't need to do that. Took me until the 2nd or 3rd pin to realize what exactly needed to be done. I was going about it all wrong (inserting the blade all the way in, then trying to pull the wire out). It's actually much easier. If you look at the front of the connector with the plastic protector removed, right above the pin you'll see a little black tab. Gently push that up, then pull out the wire.
Great suggestion provided us older folks can even see the little black tab.
BTW - That's the same procedure I used.
03-09-2017, 02:28 PM
#7114
Senior Member
My IP Cluster shows direction of next turn, how far away it is, name of street I'm to turn on and the speed limit where I'm at. If I have that screen up and I'm navigating to someplace.
Last edited by Livoniabob; 03-09-2017 at 02:30 PM.
03-09-2017, 03:25 PM
#7115
Junior Member
03-09-2017, 07:29 PM
#7117
Cut the belt chime off following the directions on page 40 of the manual. The one point that the manual fails to mention yet required is you need to be sitting in the seat when performing the action. Thans for the direction/info
03-09-2017, 11:40 PM
#7118
It's my first day
Originally Posted by packrat1969
Yeah, I know. The pictures sort of got out of hand. The weird part is that I cannot see the inline pictures here from my XP laptop, but they show up just fine on my Android tablet. The attachment pics are there in both machines... DOH!
Thanks for the tip on the Connection settings, but I beat you to it. Shortly after I took that pic they were changed. I got tired of having FORScan take it's time probing ports it couldn't use. I still have no idea why the Bluetooth option is not available if one is using an aftermarket BT dongle. The software doesn't treat WiFi hardware the same way. It could be that it has to do with the different versions of Bluetooth. The unit I have is an old GBU421, which is BT 2.1, not the latest.
As for the APIM data, I set up Notepad as the default viewer shortly after I began checking out what was actually in an .ABT file. I like having the ability to edit the data ahead of time, and outside of FORScan. I see nothing wrong with the data in the file. It is all in the proper range (see below). I also had the same file error when I attempted to restore my BdyCM. I discovered this Monday when I started troubleshooting the whole failed restore process. 39 views of my query in the FORScan.org forums, so far, but 0 replies.....
;Block 1
7D001012A2A04060037
7D001020089060482EF
;Block 2
7D0020155530103C44A
7D0020202028000005F
7D002030000DC
;Block 3
7D003010000010300DF
;Block 4
7D004010100000100DE
7D004020001DE
;Block 5
7D005011A681A683D1E
7D005025432
;Block 6
7D00601805E
;Block 7
7D00701470033000059
7D007020000029A007C
7D00703005656940021
7D00704C8AA
Thanks for the tip on the Connection settings, but I beat you to it. Shortly after I took that pic they were changed. I got tired of having FORScan take it's time probing ports it couldn't use. I still have no idea why the Bluetooth option is not available if one is using an aftermarket BT dongle. The software doesn't treat WiFi hardware the same way. It could be that it has to do with the different versions of Bluetooth. The unit I have is an old GBU421, which is BT 2.1, not the latest.
As for the APIM data, I set up Notepad as the default viewer shortly after I began checking out what was actually in an .ABT file. I like having the ability to edit the data ahead of time, and outside of FORScan. I see nothing wrong with the data in the file. It is all in the proper range (see below). I also had the same file error when I attempted to restore my BdyCM. I discovered this Monday when I started troubleshooting the whole failed restore process. 39 views of my query in the FORScan.org forums, so far, but 0 replies.....
;Block 1
7D001012A2A04060037
7D001020089060482EF
;Block 2
7D0020155530103C44A
7D0020202028000005F
7D002030000DC
;Block 3
7D003010000010300DF
;Block 4
7D004010100000100DE
7D004020001DE
;Block 5
7D005011A681A683D1E
7D005025432
;Block 6
7D00601805E
;Block 7
7D00701470033000059
7D007020000029A007C
7D00703005656940021
7D00704C8AA
Quick question: when you setup Notepad as the default program to open the file did it add a hidden .txt file extension to your .abt file name.
Go enable hidden file extensions in windows XP folder options and see if that uncovers anything.
03-10-2017, 01:22 AM
#7119
Airborne_Ape,
Not a bad suggestion for something to check, but no. No file extensions were added to the .abt files. The files were never saved with Notepad, just viewed. When I first created them with FORScan, I made sure they were all write-protected. Just in case I did something stupid--and oh yeah, just in case anyone's thinking to suggest it, yeah, I am gonna check and see if it's the write-protection status that messed things up. I wouldn't expect FORScan to require the files to be write-enabled if it was just reading them, but I've seen weirder things.
Anyways, for as long as I can remember, exposing all of the file extensions is one of the first things I do in Windows Explorer. I'm beginning to wonder if this is just a WinXP issue. Is anyone else using WinXP, or is everyone Win7 and up?
When I get some time this weekend, I dump my FORScan directory over to a Win7 laptop, install FORScan and see if it changes anything. By changing the OS/PC will I need a different extended license? Is each license machine-specific?
Not a bad suggestion for something to check, but no. No file extensions were added to the .abt files. The files were never saved with Notepad, just viewed. When I first created them with FORScan, I made sure they were all write-protected. Just in case I did something stupid--and oh yeah, just in case anyone's thinking to suggest it, yeah, I am gonna check and see if it's the write-protection status that messed things up. I wouldn't expect FORScan to require the files to be write-enabled if it was just reading them, but I've seen weirder things.
Anyways, for as long as I can remember, exposing all of the file extensions is one of the first things I do in Windows Explorer. I'm beginning to wonder if this is just a WinXP issue. Is anyone else using WinXP, or is everyone Win7 and up?
When I get some time this weekend, I dump my FORScan directory over to a Win7 laptop, install FORScan and see if it changes anything. By changing the OS/PC will I need a different extended license? Is each license machine-specific?
03-10-2017, 06:21 AM
#7120
Old Fart
Airborne_Ape,
Not a bad suggestion for something to check, but no. No file extensions were added to the .abt files. The files were never saved with Notepad, just viewed. When I first created them with FORScan, I made sure they were all write-protected. Just in case I did something stupid--and oh yeah, just in case anyone's thinking to suggest it, yeah, I am gonna check and see if it's the write-protection status that messed things up. I wouldn't expect FORScan to require the files to be write-enabled if it was just reading them, but I've seen weirder things.
Anyways, for as long as I can remember, exposing all of the file extensions is one of the first things I do in Windows Explorer. I'm beginning to wonder if this is just a WinXP issue. Is anyone else using WinXP, or is everyone Win7 and up?
When I get some time this weekend, I dump my FORScan directory over to a Win7 laptop, install FORScan and see if it changes anything. By changing the OS/PC will I need a different extended license? Is each license machine-specific?
Not a bad suggestion for something to check, but no. No file extensions were added to the .abt files. The files were never saved with Notepad, just viewed. When I first created them with FORScan, I made sure they were all write-protected. Just in case I did something stupid--and oh yeah, just in case anyone's thinking to suggest it, yeah, I am gonna check and see if it's the write-protection status that messed things up. I wouldn't expect FORScan to require the files to be write-enabled if it was just reading them, but I've seen weirder things.
Anyways, for as long as I can remember, exposing all of the file extensions is one of the first things I do in Windows Explorer. I'm beginning to wonder if this is just a WinXP issue. Is anyone else using WinXP, or is everyone Win7 and up?
When I get some time this weekend, I dump my FORScan directory over to a Win7 laptop, install FORScan and see if it changes anything. By changing the OS/PC will I need a different extended license? Is each license machine-specific?
I never used notepad either.
I have since bought a cheap W7 laptop and am using that.
I could maybe do some testing for you on the WinXP if you think it would help you. If you are going the W7 route it might be a waste of time.
And yes you will need a new license with each computer as is relies on the hardware id. But it is pretty quick since you already have a license. You don't have to wait for the registration process.