Strange Scanner Reading

This site may earn a commission from merchant affiliate
links, including eBay, Amazon, Skimlinks, and others.

Joined
Dec 24, 2003
Threads
136
Messages
3,559
Fine folks, I recently got a good real time scanner that scans lots of lines of data and one line offered is an "Engine Load Percentage". I was surprise to see that the percentage posted is often 100% despite the fact that the rig is only at half throttle with much much more to go to get to redline. Despite my dutiful effort I could not coax the percentage past 100%. :D Is this normal? Thanks.
 
TTT - Someone's gotta have good experience with this, if it helps, the load was already at like 15% at idle! Seems strange to me that it would be working much at all at idle and also seems strange to me that when the rig is really just putting along (compare to WOT) it is reading 100%??? I'm :confused:
 
Ya I do.

Load, or "calculated load" was a demand by the government on an OBDII system that used a hot wire air flow meter.

The alternative was a MAP, manifold absolute pressure sensor and it gave a value to the manifold's pressure that could be displayed.

However with the use of a MAF sensor that wasn't possible. So the government made the auto manufacturers calculate the load on the engine.

Here they were very open to how the manufacturers did this. On Ford's it's actually possible to be in the negative on load. This happens when decending a hill where one would be engine braking.

On our Toyotas, WOT would normally be at 85% load. Now that you are forced inducted the load will go way above 100%.

From my research all Toyotas run in the 15% range on idle and 85% on WOT in stock form.

From what I can tell Load has no bearing on anything other than satisfying the government.
 
From what I can tell Load has no bearing on anything other than satisfying the government.


Cool, thanks LT, you aren't saying the gov-ment's gonna give me higher taxes on this are ya? :D :flipoff2: :D
 
Fine folks, I recently got a good real time scanner that scans lots of lines of data and one line offered is an "Engine Load Percentage". I was surprise to see that the percentage posted is often 100% despite the fact that the rig is only at half throttle with much much more to go to get to redline. Despite my dutiful effort I could not coax the percentage past 100%. :D Is this normal? Thanks.

Since 100% load means "that's all there is" it is logical to assume the software designers of your scanner (or maybe Toyota in the OBD-II interface) didn't set up the variable to display a larger number. Kinda like a full glass of water. When it is 100% full, it is full.

-B-
 
Kinda like a full glass of water. When it is 100% full, it is full.

-B-

My cup runeth over then?!? :D Still I'd like to know if as another tuning diagnostic, this, dialed in properly, could reveal where to look to get more gains in power or torque? I think that the start to that answer is figuring out is it toyota's OBD system or the scanner's OBD system that is tapping out at one hundred % ??? Or, if it is actually another "gov-ment" assigned variable it is prolly useless anyway and requires active avoidance of any attention?!? :flipoff2: So is it really a perfect percentage of actual real-time load vs. possible real-time output, OR, is it a reference to something totally separate from that and therefore really meaningless? Still, :confused: :cheers:
 
from what I've read it was common to use the MAP reading in identifying clogged cats and the government wanted something similar for a vehicle with a MAF. So it was more of a diagnostic tool than anything else.

This ties into my MAF project.

If you read that last thread you'd know that my load value at WOT was higher with the freer flowing MAF.

I've been talking with another member and we've come to a couple of ideas on it.

1. Because there is a restriction on my MAF on the inlet it forces the air to travel at a greater speed through that section and doesn't have enough time to slow before hitting the sensor to get an accurate reading. This would explain why it's more naticable at higher RPMs.

2. The freer flowing MAF is doing exactly what I want it to do. It's allowing more air to enter the system and the higher load value is correct for that greater flow.

3. It's a combination of both.

One thing is for sure, I drove the truck around for 20 minutes and several restarts and the ECM was happy as a clam and never threw a code. A few WOT hill climbs were thrown in as well.

With my next Generation I'll be removing the inlet restriction. This will clear up the understanding of what is going on. If the load then mimics the stock MAF then the restriction was the issue. If the load stays the same of increases slightly then the MAF works and I should be getting better performance out of the engine.
 
This ties into my MAF project.

If you read that last thread you'd know that my load value at WOT was higher with the freer flowing MAF.

I've been talking with another member and we've come to a couple of ideas on it.

1. Because there is a restriction on my MAF on the inlet it forces the air to travel at a greater speed through that section and doesn't have enough time to slow before hitting the sensor to get an accurate reading. This would explain why it's more naticable at higher RPMs.

2. The freer flowing MAF is doing exactly what I want it to do. It's allowing more air to enter the system and the higher load value is correct for that greater flow.

3. It's a combination of both.

One thing is for sure, I drove the truck around for 20 minutes and several restarts and the ECM was happy as a clam and never threw a code. A few WOT hill climbs were thrown in as well.

With my next Generation I'll be removing the inlet restriction. This will clear up the understanding of what is going on. If the load then mimics the stock MAF then the restriction was the issue. If the load stays the same of increases slightly then the MAF works and I should be getting better performance out of the engine.

Yup, I did read it, understanding it, not so sure, but...

I dont think that it is number 1 - assuming that this measurement actually means anything; IOW if the "restriction" you refer to was "stock", wouldn't the measurements thereforth be "stock" ???

I do think that it is number 2 - I think that you simply increased the capacity at each and every measurement point and therefore also increased the measured percentage of real time capacity vs. real time output. I sort of assumed number 2 all along but what was surprising was the fact that your percentage went up within normal measurement range and mine is way out of our normal measurement range ... so much so that the measurement is now useless to me ... You would think that true measurements of real time capacity vs. real time output would be an amazingly useful tuning variable ... I'm just trying to get some use out of it and sorry to say that 100% when the rig is essentially loping along is not really so useful!

Ohh, Because I dont think that it is number 1, I also dont think that it is number 3 either. Anyways, I find this fascinating so any insight is welcommed!

:cheers: :cheers: :cheers:
 
I'm curious if Toyota equates 100% to the point where the manifold reaches atmosphere. On a normally aspirated engine this would never happen.

I think the load value is good for what I'm doing to get an idea of how my changes are effecting it but that's about all.

Hmm, very interesting, so yer sayin whenever the turbo overcomes pressure at the atmospheric level and then actually pressurizes the system above the atmospheric level (boost) that is the measurement measured here? If so then that tends to suggest that the scanner only goes to the 100% but the engine management must make further readings past that point which would also have to correlate proportionately to other systems or else every other system would be running beyond regular capacity? I would think that would suggest every system is really running "open" and always trying to catch up. Whereas I actually suspect that everything is equitably working, and, working together well too. If this is the case is there any conversion I can run to make this metric really mean something to me tuning wise? Thanks. :cheers:
 
One thing to remember is the load value is a calculated one. It takes the reading from the MAf and I believe the RPMs of the engine and calculates it. The ECM knows the displacement of the engine and how much air at any given RPM it could possible take in.

There isn't any definitive read out there that I cold find on how Toyota calculates this, or any other manufacturer, but this is what I was lead to believe.

I don't see the load value as anything useful in tuning our systems.

Once I get my MAF done I'll probably install a wide band and further eval the unit by monitoring the exhaust.
 
landtank One thing to remember is the load value is a calculated one. It takes the reading from the MAf and I believe the RPMs of the engine and calculates it. The ECM knows the displacement of the engine and how much air at any given RPM it could possible take in.

That's my current understanding too. In your scanner it may be that it's software is not allowing you to see above 100% load, not sure. In Landtanks new setup I see idle and up to 1/2 throttle readings (STF trim and LTF trim) as important comparisons with the "new MAF" vs the old MAF assemblies.

Landtank, I wonder if we could use a feeler guage and the throttle plate assembly to plot/compare load values on the old vs. new sensors. I am curious if the sensor's output curves are similar. I see the largest gain with the new sensor at WOT and throttle sensitivity. Call you later this weekend.

Any one else with a supercharger/turbo have a OBD-II scanner for data collection?

:beer:
 
Turbocruiser, Can you do datalogging at 3000+ rpm's under boost? I am looking for knock events and engine timing advance ie "retarding" in the datalogs.

Thanks:beer:
 
Last edited:
Turbocruiser, Can you do datalogging at 3000+ rpm's under boost? I am looking for knock events and engine timing advance ie "retarding" in the datalogs.

Thanks:beer:

Well, CD, I played around alot today and actually never recorded any real knock events, the scanner is supposed to show knock events but did not show any at all. I pushed pretty hard too up to about 4400 rpms and almost WOT, I'll play around alot more little later but for now my only obvious conclusion is I'm not knocking. HTH

:cheers: :cheers: :cheers:
 
Great news!

From my point of view, you have no fuel calculations issues (to lean) at high rpm, with "100 load calculation" cool. That info may help me later. Are you able to post or PM the datalogs? I am interested in them.

Thanks
:popcorn:
 
Great news!

From my point of view, you have no fuel calculations issues (to lean) at high rpm, with "100 load calculation" cool. That info may help me later. Are you able to post or PM the datalogs? I am interested in them.

Thanks
:popcorn:

Yes, one thing that I'm sure of is it is running rich at WOT, that's one reason why I wanna get a wideband O2 guage and tie that to the computer somehow; I'm convinced that the way to the higher horsepower is actually little less gas (and little more air - which is why LT's MAF mods might help here too) at specific points through the powerband ... I know that is not intuitive as such but I'm convinced that is the way to work the "next steps towards perfect power." We'll see. :cheers: :cheers: :cheers:
 
Back
Top Bottom