There is no drop down menu to choose from JDM, OMNI or GM MAP Sensors. You have to go on the actual xlm and manually change the scaling used. I think thats what the OP refering too. Default is JDM 3 Bar MAP right?

 

Whats up with that block tuning?? Is it only for testin out this timing issue?

If its not, thats some major block tuning


If your trying to use evoscan's maptracer, then dont use log 1byte load, as the maptracer wont work correctly with 1byte load. (unless you modify the evoscan data file to make it work)

 

When can we expect 88591715?

 

Problem fixed.

I did a log this morning using 1Byte Load and my load was down by roughly 2-3 load cells compared to the 2Byte Load.

2Byte load at peak tourque = 280 tapering to 230ish at redline.

Same tune, just logging 1Byte load.
Load at peak tourque = 255 tapering down to 213 at redline.

(I am situated at 5500feet above sea leavel, so not sure if that causes a bigger difference between the two)

So I rescaled my load sites to my 1Byte Load that I was logging, and now it logs my ignition timing basically spot on to what is in my map, when using 1Byte Load.

Still out in some cells by one point, especially during spool up, but I can live with that.

 

ahh 5000feet will make a big difference for load raw vs load compensated

 

Is there a way to compensate for this?
Like changing the formula in Evoscan, at a guess?

 

Hi all,

Ok, now i am very confused.

i am on the v7 tephra 88850715 rom and found that by 2 byte load is a good 10% above the load the ecu is using (verified from my timing logs) and seanv has the same issue (who posted above here)

But:
I live at 5500ft so i think i need to have at least the baro comp active.

my MUT table are set at: MUT00 = 6b42 and MUT 01 = 6b43 = raw 2byte load - correct?

do i change them to 6b50/51(baro+temp) or 6b48/49 (baro)? am i understanding the +2, +4, +6 for the load+baro and load+baro+temp correctly?

will this bring my logs more inline with the maps or do i need to go 1byte? and can 1byte do baro+temp?

living at 5500ft we need to get it closer as 10% off (330load vs 300load) is a big difference.

also on the 9653 rom (dads car) do i make the MUT00 /01 to 898a/b (1byte?) or 8988/9 for baro+t (2byte)? - very confused

i want to either log corrected (temp+baro) 2byte or 1byte load.

also is the mut table purely for logging or does the ecu use it for output . i.e. if we change altitude, will the ecu compesate for it if i am using the raw 1byte mut numbers?

I live at 5500ft, so compensated would be best (I assume)

what does the ecu use for 88850715 rom for output of timing and afr. does it use raw load+baro+temp or just raw load?

Mike

 

is there ability to log -20 of timing for JDM evo 7,evo 8 ecu's with this rom ?

 

Use 1 byte, it will match up and you will be able to log more items per cycle.

The MUT table items you are logging are purely for output to a logger.

 

I notice the same thing. I think what is really missing are the mods to log boost via JDM MAP. I did not see the tables that set the required values for the sensor, only the scalings are on the xlm. The tables like the ones below are missing on the xlm but I do not know the address for this ROM. They are not in MRFred original thread. Where did you get them? I am not sure if the values required for JDM3Bar are already in the ROM or if they need to be modified to the correct values.

<table name="MAP Scaling" category="MAPSensor" address="????" type="2D" level="1" scaling="uint8">
<table name="MAP Output" address="????" type="Y Axis" elements="9" scaling="Volts16"/>
</table>

<table name="MAP Fault Trig: Mid VE Max #1" category="MAPSensor" address="????" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Fault Trig: Mid VE Min #1" category="MAPSensor" address="????" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Fault Trig High VE #1" category="MAPSensor" address="????" type="1D" level="1" scaling="Volts16"/>

<table name="MAP vs MAF Baro" category="MAPSensor" address="????" type="1D" level="1" scaling="uint16"/>

 

It simply doesn't for me on 96530706.

Example at 6000':

1byte vs. 2byte baro+temp

216.0 , 177.19
232.8 , 189.06
247.2 , 201.88
264.0 , 214.38
279.6 , 225.94
291.6 , 232.5
296.4 , 232.19
295.2 , 230.94
291.6 , 227.19
285.6 , 223.75


That's a _big_ difference.

d

 

Any update on 90550001 v7

 

^^ I cant hardly wait too!

 

They are in the thread where applicable. As said many times earlier: you don't need them on an VIII because you are only logging the channel, you don't need to make any modifications to the rom.


I meant it will match up to the load row in your map.

EDIT: Yest I meant column. Details details!

 

You mean the load column? RPM is indicated by the row.

It doesn't match, at least not for me. The compensated load looks like it is being used for table look ups. I'm not hitting the 290 load cell in my example. I'm hitting the 230 load one.

d

EDIT: maybe this dicussion should migrate over the 1byte load thread. As it is, I don't really see the point in using 1 byte load if it is LOAD_RAW. It's way, way off the load values used for lookups in my application.