View Single Post
Old 07-14-2014, 02:44 PM   #15 (permalink)
jcp123
Just cruisin’ along
 
jcp123's Avatar
 
Join Date: Jul 2009
Location: Rochester, NY
Posts: 1,183

Beater Echo - '00 Toyota Echo
90 day: 42.67 mpg (US)

Hondizzle - '97 Honda Civic DX
Team Honda
90 day: 46.55 mpg (US)

Shaggin Waggin - '14 Chrysler Town + Country
90 day: 22.56 mpg (US)
Thanks: 66
Thanked 200 Times in 170 Posts
Sorry. PIDs = parameter IDs. Strictly speaking, this is any data read directly from any sensor on the vehicle by the computer. Examples would be throttle position, ignition timing, coolant temperature, and the like. I use the term more loosely to include anything a UG or SG would display, including numbers calculated from those raw sensor inputs like MPG, engine load, and the like.

ScanGauge on its own has 16 "things" or PIDs it can display (xgauge capability is completely different, based on advanced "mode 6" diagnostics, and will be ignored for now. It is best for ASE master technicians and advanced ecomodders). UG can support up to 77 different "things" or PIDs to display. More data = better, because even if you don't understand how to use it now, you can always learn at some point.

Fuel trim is basically your computer's compensation for real world conditions. It shows how much % of fuel it has to add or subtract from the computer's baseline, pie-in-the-sky, ideal conditions programming. As a budding DIY mechanic, it is a really good basic piece of information to use in diagnosing problems. Even pro technicians will usually use it as the first thing they look at after check engine light trouble codes to help diagnose a lot of running problems, especially where misfires are concerned.
__________________



'97 Honda Civic DX Coupe 5MT - dead 2/23
'00 Echo - dead 2/17
'14 Chrysler Town + Country - My DD, for now
'67 Mustang Convertible - gone 1/17
  Reply With Quote