Hey guys. I've been out of the forums for a while now, and I was just wondering if anyone has figured out how to tell what load cell the ecu is in at any given time. I know most of the load calculations that are out there, but I'm looking for the actual load cell that the ecu is using. Thanks.

 

The actual load cell that the ECU is using is close to the calculated load value. That's the best most of us can do. I'd suggest doing a bit more reading as there are at least 3 or 4 threads on this exact topic.

 

Yes, I know that there are many other posts on this topic. However, although the calculated values discussed in these threads may be close and/or the best available method, I really would like to be able to see what the ecu is actually using. I heard some talk a few months ago about people doing research on the command to get this reading from the ecu. I was just curious as to if anyone has gotten any farther with this yet.

 

Yes JCSBanks and Malibu have posted several times about this....but it was for the IX...

 

Look for the 2-byte load thread. It has the best currently available option.

-Paul

 

Thanks alot, I'll check it out

 

Found it.

Damn, after listening to those guys discuss the topic I think I will jam a screw driver in my eye because I feel so dumb and naive.

Great read, I just wish I had a little more knowledge on the programming side of things.

 

I fell the same way when I read posts from these two. I try do hard to follow, but then I give up and stop reading.

I will just wait and see what the end result is.

 

what ecu are you running? I can mod your rom to display 2-Byte ECU Load in EvoScan if its an evo7/8

 

I have an 8. That would be increadible if you could do that, but to be honest with you, I'm not sure I quite understand what "2-byte" load is. I know there's 8 bits in a byte and so on, but will 2-byte load display all load values from 0-320?

 

I know how you feel!

MB

 

oh yeah I take for granted that people know bits and bytes

1byte = 8bits = 0->255 decimal

because load wants fractions of a decimal those 255 are broken into fractions. 5/8ths to be exact.
i.e each 1 decimal = 0.625 Load

Load = 0->159 3/8ths (159.375)

now we want to know a lot more LOAD than that. so we need 2 bytes.

2bytes = 16bits = 0->65536 at 5/8ths resolution, will give us LOAD as at 0->40960

which is plenty large enough for any Turbo vehicle lol

Once I have released EvoScan 0.98 with easy Power graphing and Easy Alarms, I'll add a facility to patch Evo7/8 ROMS to output 2 byte LOAD.

 

Anyone thought of just changing the divisor so the load is still one byte to the 1C variable, but the scaling is altered?

 

That actually would be better IMO because you could double the resolution easliy. So where is that scaling byte?

 

The problem is by doubling the range, your reducing the resolution..

But its not that important at low loads, and the higher loads really only have to be numerically close, its not hard to figure out where it goes after that point.