I am trying to help with programing on a piece of software that reads the OBD interface and it works perfectly on a 2004 Toyota Corolla but cannot read the MAF data from the Insight. The suggestion was that the ECM is not reporting the MAF data, but I kind of doubt that. I think we are doing something wrong in the interface impedance's.
Any help would be appreciated.
__________________
Jim Isbell
2000, 5 speed, 250,000 miles
"If you are not living on the edge, well then,
you are just taking up too much space."
I thought about before as well, but that's not the whole picture:
Imagine a car going up a steep hill, but very slowly,
The injector duty is high due to the high load, but...,
The car is moving slowly, so not covering very much distance,
Since distance is low, MPG would also be low
Opposite scenario:
Now the car is coasting down a hill, and moving briskly,
Injector duty cycle is almost nil,
Distance moved is high,
Therefore MPG should be high
So the ScanGauge has to use at a minimum, injector duty cycle AND distance covered.
Well if it has rpm, injector duty and road speed it can use those for an estimate of fuel burn.
Whether injector duty is taken as % open which is influenced by rpm or just raw ms values.
Injector duty will never be high at low rpm, even at full throttle. The engine revolution time is much longer so you never get close to a high duty (%) at those revs.
Fuel cut should always give infinite MPG if you have no injector duty but a road speed.
Quote:
Originally Posted by 3-Wheeler
I thought about before as well, but that's not the whole picture:
Imagine a car going up a steep hill, but very slowly,
The injector duty is high due to the high load, but...,
The car is moving slowly, so not covering very much distance,
Since distance is low, MPG would also be low
Opposite scenario:
Now the car is coasting down a hill, and moving briskly,
Injector duty cycle is almost nil,
Distance moved is high,
Therefore MPG should be high
So the ScanGauge has to use at a minimum, injector duty cycle AND distance covered.
The scion xa was an economy car made for teenagers by toyota, It flopped.
For some reason I was unable to get a vacuum reading when I used a scan guage2.
The scan gauge 1 and 2 was a magic device that read the stuff in the odb2 port. You had to enter the engine size to get accurate mpg. It read 9999 when engine braking. It also gave a hp rating and cost per mile if you set the fuel tank size and price of fuel when fill up. It also gave instant and average mpg.
Quote:
Originally Posted by JimIsbell
I dont know the car you are talking about, why is it "needless to say it did not display a vacuum or map"?
Does that explain why the Insight does not have MAP?
The load indicator DOES work on the insight as well.
I am trying to help with programing on a piece of software that reads the OBD interface and it works perfectly on a 2004 Toyota Corolla but cannot read the MAF data from the Insight. The suggestion was that the ECM is not reporting the MAF data, but I kind of doubt that. I think we are doing something wrong in the interface impedance's.
Any help would be appreciated.
Jim can you post/send me any software code for this project?
The AutoGuide.com network consists of the largest network of enthusiast-owned enthusiast-operated automotive communities.
AutoGuide.com provides the latest car reviews, auto show coverage, new car prices, and automotive news. The AutoGuide network operates more than 100 automotive forums where our users consult peers for shopping information and advice, and share opinions as a community.
Need Information on the OBD-II interface.
