My 2 byte load is way off, i am hiting as high as 262 but the load calc just shows 199 i know the load calc its low but i have just a test pipe and a drop in, i have only changed the timing map but only one degree on some places and the mivec map which is not generating those loads.

please any ideas to get it in place

 

anybody???

 

you know even with 2-byte load, if I see knocking at this RPM/load, I make adjustments to 1 lower/1above that point anyways. So people really should just not bother with it and use calc load and just make adjustment to 1 higher and 1 lower. maybe even 2 high/lower.
thats my 2 cents

 

I know i cant be in the exact cell but by my timing maps the 2 byte load is off by 80 on the top and 20 in the low values so if there is a good way to have it correct i wold apreciate

 

What makes you think that the calc load is correct and the 2-byte is wrong? The 2-byte peak of 262 is much more reasonable than the load calc value of 199.

-Paul

 

never heard of 2-byte bing 60+ off. usually its like 10-20 tops. Something definetly is wrong.
what ROM do you got.

 

i have the 88590015 and it is way off, i can see these on the timing maps, the load calc its close to the real timing at that load-rpm, and the 2 byte its 60 "load" over the timing at that rpms

 

talk to the man about your particular ROM and how you went about setting up the 2-byte.

 

Log airflow then perform the following math to doublecheck both load calc and 2 byte.

hz/rpm*852=load approx

If its closer to the 2 byte then you know something else is off and if its closer to the load calc then you know something is wrong there. With the 2 byte MUT requests I have found it is either on or not. Things like battery voltage(alternator) and i/j affect load calc so its really influenced by alot of other variables. Even 2 byte load has modifiers as was covered in another thread.

 

How high is your boost spiking at?

 

I Am Spiking At 19 19.5 With Autometer New Nexus With Electronic Map Sensor Which Is Suposed To Be Very Acurate

 

i think my 2 byte is way farther off than the load calc, in timing maps the actual timing on the logs its closer to the load calc than to de 2 byte

example

log

rpm 5031
2 byte 241.563
load calc 180.657
t adv. 12

map shows

--------180 200 220 240 260 280
H. O. 1 10 --9 -- 6 -- 2 -- -1 -- -1
H. O. 2 11 --9 -- 7 -- 4 -- 1 -- -2
H. O. 3 10 -- 8 -- 7 -- 4 -- 1 -- 1

Knok is not present and octan level is 100%
in other logs the load calc fals litle lower than actual timing but 2 byte is way higher