Im not sure if its a result of the new algorithms that Jack said are being used or if there is something else going on.

But all my logs yesterday where below the 180 load column. No knock, engine warmed up, boost the same as previous logs which showed higher load, same road used for the run.

If mitsulogger is indeed more accurate, perhaps my previous logs where off and i am actually running in such a low load area.....what would you suggest to adjust to bring the car back to "normal" range?

 

what boost are you running?

180 load is around 14 pounds give or take

 

gauge is reading 23psi

 

Hmm the evoscan .98 and .99 has a max load of 160 also.

 

ECULoad will only read to 160 or so.. Its a limitation in the output of the ECU..

In mitsulogger there is something called LOAD that is calculated, however there are a few things that you must do for it to calculate properly..

1) AFRMAP value must be enabled for logging
2) InjPulseWidth must be enabled for logging
3) Battery (battery voltage) must be enabled for logging
4) Latency (Custom request) Must be enabled to interpolate Latency values from battery voltage
5) Load Must be enabled (obviously)

Additionally if you have aftermarket injectors, you must enter the injector scale value into Mitsulogger that was entered into the Rom that was flashed into your car. This also applies to the 11v and 14v voltage latency values.

Without those values, it will NOT be accurate, in some cases you will get division by zero errors periodically (it shows in the logs and log window) but won't kill the logger.

But I suspect your looking at the ECULoad value, which will never go above 160.


Also.. I added the Evoscan load calculation formula into Mitsulogger called LOADALT, its disabled by default, in this formula it only works accurately with a completely stock voltage latency value, you can use this to compare how much the load calculation is altered when you have altered your latency values.

 

Its actually a dramatic difference when you go from a stock injector size, to something like 660 as its a greater than 20% difference. But I inadvertantly put "injectorscale" as a variable in the Loadalt formula, it should be 513 instead.

 

i was using the maptracer utility...so i guess i cant use that thing anymore huh?

 

The map tracer should still work fine with Mitsulogger, nothing changed from that aspect as long as your load doesn't go above 260 (and your maps arent scaled above it.

Your problem now may just be that you either disabled something or changed a setting.

 

i havent changed a thing since installing mitsulogge....whatever the default settings where i ran with....


Still on stock turbo, injectors, no cams...

 

Okay cool..

I made some changes about how the injector latency is handled, basically it uses a sliding value for the latency based on the settings in the program, and the battery voltage reported. I have run it along side the Evoscan calculation to be certain that its no more than a few 100ths different between the two (Evoscan works similarly, but uses fixed values in its formula)

Did you disable any items when you started logging? You need AFRMAP, InjPulseWidth, and Battery enabled in order for the calculation to work properly.

The values will be more accurate, probably about 10-20% lower than it was originally reporting and that could be what your seeing.

I'm just surprised to see loads of about 160-180 at peak boost if thats what your claiming. It might not be anything wrong, but I don't know what your accurate boost is, nor much else about your car.

 

Engine...
Forge BOV
Forge MBC
Injen Intake/upper pipe/lower pipe
Ebay Intercooler
Walbro 255
10.5 Hotside(ported)
Ported Exhaust Manafold
DC Downpipe w/cat delete
Buschur SCCA Cat-back
Ingalls Torque Dampener


That is the engine mod list....boost gauge is tapped at the intake manafold & is an autometer manual gauge....reading 23-24psi.

What does such a low load range indicate to you?