In reality, I haven't seen a true load table yet, where each value for load, would directly correlate to a column in the map, allowing you to tailor the load to what your car is capable of.. The closest thing I've seen in the current definitions is the MAF Scaling table..

Ultimately you end up tricking the ECU with altering the MAF size value, you would need to alter a table or value specific to what the max expected load is and that would scale the map accordingly, I'm sure theres a setting for that.. Only I haven't seen it yet (duhh, I completely missed the obvious)

 

The scalings setting in the definition is what mathematically turns the hex numbers into load values, but are you referring to actually altering those cells directly? It occurred to me you might have been referring to that, only the ignition and fuel tables use two different regions of rom memory for that.. It actually never occurred to me to try to alter the cells for the values in the axis..

 

Yeah, I had to go back and look at your screen shots before I realized that you revised the load column data cells directly.. although you altered them torepresent higher load values, I'm not certain if that actually does anything other than change the values shown... I Just assumed it was the scaling formula that was altered..

 

Do this... Set boost to something like 14 PSI (just to be conservative for a minute..

Use a bone stock rom file and try this.

Record the ignition timing you'd do at 4500 RPM. With a conservative timing map, you eliminate the chance of the knock filter affecting this.

Say that value is 8 degrees BTDC.

Now, say that was the 240% column.

Set the 300% value (IIRC the right most column in the high octane IT map) to something like 350, and horizontally interpolate from 200 to 350. Now the 240 column you were just in should really be reading a higher number, and that would effectively push the interpolated 240 value one column to your left (to a higher timing value in that column).

Repeat your run.

You're going to see that the timing value at 4500 is now what you had in that newly referenced 240% column.

Obviously, as you mentioned, you need ot do this column scaling for all 2 dimensional maps in question.

Jorge (RiftsWRX)
www.ProjectWRX.com

 

Yeah it clicked after I looked at it the third time.. At first I was trying to figure out what the heck was going on then I double checked the Definition itself and remembered that the row data is actually in the ROM, and the scalings portion was what gave it a human readable value.

 

Thank you Jorge! It would be nice if more "tuners" sharred they're experience and methods with the endusers as Jorge does. I understand business is business but you gotta hand it to Jorge, most tuners would rather keep this info for them selves! Jorge you really went above and beyond here and i really appreciate it. I'll buy the next round!

 

Just a little update. The car is uber fast. On a cold tire i have traction problems in first gear from a roll. Second gear is no different!!! About 500miles since the tune and no signs of knock or anything!!! woot!

 

I think scailing portion is actaully in the rom also. I was able to read it back after I load the numbers.
Anyway, I moved the last column load scale to 300%. But I didn't notice the significant change in my timing values( although, in recent run, I think I noticed something when I moved more to 304% but I am not sure) . I am going to try 400%

 

so what I get from this is that the load #s at the top of the coloums are actualy stored in the ecu and referanced by the ecu in determining what cells to derive its targets from.

and what some here including myself thought (that the row and collum tags were for human only and not used by the ecu at all and scaling those #s would only change our referance and not how the ecu reads the map) was wrong?

 

Nah the scaling I'm referring to is in the XML file, if you open the table, then hit edit, then look at the scalings dropdown or button to the right of it.. Those are actually in the XML file..

WHat was confusing me was the number on top, just looked like someone altered the formula which would have done nothing but changed the numbers in the program.. But altering the data in the top row would result in changing the the values in the load table, but it never clicked that the data was used by anything other than for display.. It wasn't until I looked closer at the row data and the location, and found a subroutine that calls it, that it actually made sense to me.
I honestly don't know how I ever overlooked that.

 

I'm still confused, have we confirmed that we can increase the scaling of the ECU maps or not?

 

Ok, I am confused too. what are we talking about here? I was talking about the top row load scale values that starts from 0 and ends at 260 from fuel and timing table. And those do actually get written to the rom and it seems to change the load scale.
I just finished the testing. I changed that 260 to 400.
For the first time, I saw the timing values landed toward at 240 around 4000 rpm. It used to go below whatever I set for 260. May be it was the good weather today and absent of knock. I dont' know yet. But If I repeat this over and over I will be convinced that we can increase the load so that we are not limited to 260%.

 

Good deal! Glad to see that things are starting to pan out! Now all you guys need is a cohesive way to log that value in with your normal data stream, and you'll be golden!

Jorge (RiftsWRX)
www.ProjectWRX.com

 

Cool, Seems alittle low for 100 octane.

 

That would be golden Jorge (nice to see you here having enjoyed all your posts on NASIOC where I post as john banks)... I'm getting timing number on my JDM ECU that tally with 160% load at 1.4 bar boost...