When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
The instructions are very good. Get a teenager. They're not afraid of any kind of computer. Only xgauge that gave me problems is the BOOST indication. I tried youtube but no help on programming video.
Here's a link with all the codes. The instructions for programming are at the bottom. https://www.ford-trucks.com/forums/a...8&d=1319030874
Also, there is a video on YouTube one of our members posted awhile back. Just search for ScanGauge.
just to add for anybody who lands here looking to buy a 6.0L, you don't have to be in any particular vehicle to program the ScanGauge, just anything newer than 1996 that has the OBDII port to power it up. You can then program stuff that won't be there in that vehicle, to make it ready for a test drive.
So, your sayin you could sit in a truck at work,(or wherever) 96 or newer, plug in the ScanGauge and input the codes you need, then when you get off work slap it in your truck and it's ready to go.......hmmm good point!
preeecisely. If you know about this stuff in advance, you should buy the ScanGauge, program in at least the EOT (fWT is already there for ECT) and have it ready for your test drive. No need to take time at the truck programming in the XGauges, that can be done on any vehicle with a port.
FICM volts and IPR and ICP would probably also be real good to know before you buy.
The only hitch I can think of is you need to take the truck for half an hour at least, to give it 20 minutes of highway to do the test right.
it does have a speed display and it is adjustable, but that doesn't affect the dash speedo. You can compare your GPS or timed speed to what the SG shows and adjust to match. Then your actual speed is shown on the SG. It should be fairly simple to learn how far off the dash speedo is and be able to tell your true speed. For example my dash speedo is consistently 2mph higher than actual, so I learn to drive at 67 when I'm aiming for 65.
Also it is more than just a monitor in that it does have the ability to clear codes. I've never seen any to try it and from my reading apparently there are some codes it won't show?
They planned ahead for certain operating conditions where a parameter can be outside acceptable values for a short period of time, or for whatever reason not be a "hard" fail and not turn on the CEL. If it see one of these codes, it goes in memory. If after a few drive cycles it doesn't see it again it forgets it and you never know it happened. If it does see again before it's dropped it logs the second failure. On the third time the error is seen it becomes a hard fail and the CEL comes on. Reading "pending" codes is looking at the list of logged errors that advent turned on the CEL yet.
Also, it works the other way around. If you unplug your EGR valve and it sets a Cel, when you plug it in the CEL goes out. You can still retrieve the EGR codes for several drive cycles.
They planned ahead for certain operating conditions where a parameter can be outside acceptable values for a short period of time, or for whatever reason not be a "hard" fail and not turn on the CEL. If it see one of these codes, it goes in memory. If after a few drive cycles it doesn't see it again it forgets it and you never know it happened. If it does see again before it's dropped it logs the second failure. On the third time the error is seen it becomes a hard fail and the CEL comes on. Reading "pending" codes is looking at the list of logged errors that advent turned on the CEL yet.
Also, it works the other way around. If you unplug your EGR valve and it sets a Cel, when you plug it in the CEL goes out. You can still retrieve the EGR codes for several drive cycles.