Strange 1 byte Load Error Logging 9417 V7
Strange 1 byte Load Error Logging 9417 V7
I am getting strange logs out of an 03 EVO 8 with Tephra V7 9417 rom, I am logging 1 byte load and right as the car hits peak load around 300 the readings drop to random low numbers and the car bucks. Here is a creen shot of my log:

Any ideas?
If you are at high rpm like 5k rpm and step on it the car takes off and runs hard. If you start from a stop or roll in first and step on it the car is fine. If you put it in 3rd or 4th and step on it from 3k it builds boost fine but right before it hits peak load it cuts out and the only strage things in the logs are these drops in load. I still see drops in load even when the car runs fine. Please help

Any ideas?
If you are at high rpm like 5k rpm and step on it the car takes off and runs hard. If you start from a stop or roll in first and step on it the car is fine. If you put it in 3rd or 4th and step on it from 3k it builds boost fine but right before it hits peak load it cuts out and the only strage things in the logs are these drops in load. I still see drops in load even when the car runs fine. Please help
My 1 byte load formula in evoscan shows 1.2*x, my rom also shows 1.2 under the 2byte to 1byte load factor. My load does match the normal load read out until that maxes at 160. Do I need to change this to see higher then 300 load?
The boost limit table under main map boost control settings is at 225% whatever that means. Where else should I check for a boost or load limit in this rom? I am running an AEM Tru Boost so I don't use the ECU for boost control.
The boost limit table under main map boost control settings is at 225% whatever that means. Where else should I check for a boost or load limit in this rom? I am running an AEM Tru Boost so I don't use the ECU for boost control.
225% = max 225 load 
It still cuts fuel if you go over this load limit, regardless of how you are controlling boost.
As far as the 1b load reading goes....this is straight from the V7 thread that is literally a few threads below this one today...
2byte to 1byte load factor
- simple divide routine to convert 2byte load into a 1byte field and then Evoscan will convert back to 2byte.
- MATCH you LoadFactor in ECUFLASH to the SAME as your Eval in evoscan
- MaxLoad is loadfactor * 255, ie a loadfactor of 1.2 will allow a Max Loggable Load of 306, 1.3 = 331... etc (choose an appropriate loadfactor based on your existing max load)

It still cuts fuel if you go over this load limit, regardless of how you are controlling boost.
As far as the 1b load reading goes....this is straight from the V7 thread that is literally a few threads below this one today...
2byte to 1byte load factor
- simple divide routine to convert 2byte load into a 1byte field and then Evoscan will convert back to 2byte.
- MATCH you LoadFactor in ECUFLASH to the SAME as your Eval in evoscan
- MaxLoad is loadfactor * 255, ie a loadfactor of 1.2 will allow a Max Loggable Load of 306, 1.3 = 331... etc (choose an appropriate loadfactor based on your existing max load)
That did the trick, 1.4 load multiplier got me 360 load reading ability and I raised the boost limit from 225% to 315% which is the highest it will go. I hit 350 load at 24 psi and ran smooth. I am still not sure what that boost limit represents but that must have caused the bucking. Thanks!
It represents load. There is also timer that is probably letting you overshoot to 350 load without it cutting fuel. Most V7 roms have 2 fuel cut tables. The 2nd will let you go higher than 315.
Thread
Thread Starter
Forum
Replies
Last Post
ptm5070
General Engine Management / Tuning Forum
0
Dec 18, 2014 09:06 AM







