I know that tephra has done some work on extending the ignition retard limit, but in the process of going through the ignition retard limit subroutine to understand what's happening, I think that there may be a way to more consistently approach -20 deg (or more). To start, I need someone (or a few people) to log a RAM variable during "launch conditions"

Evo 9 8859: FFFF6DC3
Evo 8 9653: FFFF8BF7

You'll have to write the value (e.g., 0x6DC3) to the MUT table and then setup a definition in the EvoScan Data.xml file.

 

M,

I am assuming we just need to use a timing alg for the EvoScan def?

 

Raw (eval="x") is fine.

 

I should be able to get something later today for you then.

 

Thank you!

 

I set MUT83 to 0x6DC3 and then setup evoscan to log requestID 83, that's it right? Or is there a better MUTXX value to use?

 

scheides,

Are you using LiveMap? I thought I remember seeing you post about using it.

If not, disregard, but if so, it's as easy as putting the RAM address in your RAM mut table and logging using the LiveMap app.

 

Nope, old-skool evoscan and restarts/reflashes here I don't do enough tuning to jump to livemap, but hey, it's winter--might find myself trying it out here soon

 

MUT83 is fine as you described, and then use Eval="x".

 

i will test... seeing i got 9653 and wanting to test my stat rev limiter

 

I couldn't get timing to go to -20, I'm using the off-the-shelf 96531706 rom, but that value stayed at 195 solid during all driving and bouncing off the launch control rev limiter.

 

I can't get mine to go past -10. Not that it would make a difference...I spin the heck out of the tires trying to launch this way. Sure is fun though.

 

Nice work mrfred, I see where you are heading, those tables are also an open point for me

 

Turns out I only had -20's in half of my map so timing was bouncing around. Set top half of map to -20's and re-ran (I called this value you're looking for RevLimContVar:



side note: is this high knock count normal?

 

After looking over the timing limit subroutine a little more last night, I'm beginning to think that those tables are not so valuable. Ultimately, that limit of #203 needs to be increased to #231 to allow -20 deg. People are reporting momentarily reaching -20 deg and then tapering down to around -15 to -10 deg. There is something going on that's pulling r2 down from 231. It must be that bit of math and comparison that takes place after constraining r2 to the limit value.

BTW, you saw that the final RAM value at the end of the subroutine only serves to monitor timing via MUT and OBD? Its the second-to-last RAM value that appears to be the timing value used by the ECU.