crcain

For a JDM X I'll see for example 200 load, 4000 rpm and 10 degrees advance. But if I look at the high octane ign map, 200 load, 4000 rpm is not 10 degrees. In fact it's more like 250 load and 4000 rpm where 10 degrees would be.

I've repeated this many times and it seems adding about 40-50 to the load allows me to find where in the map I am. I'm use EvoScan beta19.

I just installed 2.6 non beta. I notice there is two load values in some of the mode23 data item presets. If IATS > stuff. Is there two or more suspected load values out there and we're not sure why? Is this normal for my load to be way, way off?

Eventually in tuning my friends car, he started hitting 250-260 load from EvoScan log at around 26 psi but the ignition timing logged told me that internally the ECU must have been seeing more like 310 load.

Any ideas?

GST Motorsports

iTrader: (8)

Which load are you logging? Fuel / mivec / timing ?

crcain

I'm logging the only load available which is just "load". This is a data item for the preset for JDM RS 2008 which is request ID: 2380873A

To be honest, I guess I need to try the other request ID's for loads in the other EvoScan presets. We actually found that the JDM RS preset worked quite well, so used it, even though his car is a GSR. The normal 2008 JDM preset did not work well at all (not many items logging right).

Thanks for replying Bryan.. can you shed some light on why the X's have different loads for fuel / mivec / timing? This is the first I've heard of it.

I guess one of my problems is my buddy is on a more obscure JDM rom id.. is it possible for me to switch him to a USDM rom id? Failing that, is it safe for me to assume that if I see 10 degrees at 4k rpm in the EvoScan log, and the load is 200, but in fact the timing map shows 10 deg / 4krpm at 250 load, that indeed load is at 250? Also, for an Evo Red and other bolt ons at 26 psi would a load a bit over 300 be normal?

GST Motorsports

iTrader: (8)

Ah I see now that Evoscan shows only one load for JDM Evo 10. I've never looked at the JDM parameters in EvoScan before. I would imagine that parameter is off then.

tephra

iTrader: (6)

Same as CT9A - ie there is a temp compensated load, baro compensated, and baro+temp compensated.

Different systems (MIVEC/Timing/Fuel/Boost) use different loads.

At most they will only deviate from each other by 20 points

crcain

Ok so I switched my friend to 52360018 from 52360016.

In making this switch I switched to the EvoScan data item preset of 2008 JDM Evo X where as with 52360016 the RS version was what worked.

We also disabled some of the codes he was getting (thanks Tephra!).

With all those changes, the datalogged load/rpm/timing seemed to be matching the timing map very well.

So... I don't know what fixed this issue, but it was fixed so just wanted to update/resolve this thread. My guess is the load values were correct before, but there must have been an ignition trim being applied for some unknown reason.