Thanks Dave

 

I made sure that I had the factory MUT values the same in 04 and 33 but when I went to log them I got an error that said does not belong to datalog table or an error like that? Had that happen ever or I am just dumb?

 

no just check your evoscan xml, evocan isn't the most forgiving app

 

Got it working now, interesting stuff. It seems that those 2 show what the timing wants to be with modifiers, what it is going to allow, and then of course what it ends up at which we all log now. If I understand it right anyway.

 

yeah 04/33 are definitley timing related MUT's I just can't tell you exactly where/what they are for...

 

I messed around with these dynamic timing tables on friday. They do indeed work, but like JohnBradley said, not sure *exactly* what the strategy is for them.

From some logging it looked like it would take all the dynamic advance out if even 1 knock count happened.

Interesting stuff...

 

You guys got me interested enough that I'm looking through this code. I'm about half way through commenting it. Gotta stop for tonight. Might have something to say tomorrow night.

 

I too have logged the return to base timing if there is ANY knock. There must be a table/entry like "Knock Sum to reduce Octane Number" that we can adjust to affect this table.

The MUT requests 04 and 33 do show the timing as it could be and what it is.

If we could get Bez to find what processes are involved in this map- that would be great (hint, hint )

 

I agree a few of those maps look like cold start maps but that brings another question. What load would a MAF based car register during cold startup? I'm guessing not 101kpa like a speed density setup because the MAF has air moving accross it as soon as the starter turns. But I agree ign 1 looks like cold start.

 

So I am wondering if it drops timing at 1 knock if the high det map would cone into play at that point. Lets say that I have my low det set to advance 2* and it picks up 1 count so it goes to the base map for an undertermined amount of time. If while its counting (assuming this is how it is working) it gets another count maybe it goes to the high det map where you could have 1 degree pulled out. Keeps your timing in the sine wave that they tend to like that way as well.

Much more testing and logging needs to be done now. I have raised too many questions that I cant answer or answer well. Back to the drawing board I guess

 

Did some ROM snooping this afternoon. I think someone made a comparison to the Subie dyn adv system. It doesn't appear to work like that. Its either all or nothing. There is no graded increase.

For anyone tinkering with an Evo IX 88590015 ROM, bit #4 of RAM variable FFFF6BF6 is the toggle switch for enabling or disabling "dynamic ignition advance". Sub_22C48 is the subroutine where dynamic ignition advance is enabled/disabled. I've only looked briefly at the variables that control whether dyn ign adv is enabled or disabled. (The rabbit hole never ends.) Can't say anything yet except that it is disabled when the TPS is less than 17% (foot is off the gas pedal).

 

Yeah my comparison to the subaru was only based on apperances.

 

Okay so for anyone with the USDM 15 ROM that wants to experiment with this table here are the addresses-

<table name="Low Det Dynamic Advance" category="Timing" address="38f9" type="3D" level="1" swapxy="true" scaling="Timing">
<table name="Engine Load" address="6f2c" type="X Axis" elements="21" scaling="Load"/>
<table name="RPM" address="6efa" type="Y Axis" elements="20" scaling="RPM"/>
</table>

<table name="High Det Dynamic Advance" category="Timing" address="3749" type="3D" level="1" swapxy="true" scaling="Timing">
<table name="Engine Load" address="6f2c" type="X Axis" elements="21" scaling="Load"/>
<table name="RPM" address="6efa" type="Y Axis" elements="20" scaling="RPM"/>
</table>


I think that they have also been incorrectly labeled in some of the other ROMS as the boost enhancement tables (the 05 comes to mind). Please use at your own risk and understand that Bryan and I were only able to do some testing so your results may vary.

JB

 

To add some more confusion to this...

Tuned a 2006 Evo 9 with a FP3065 yesterday. Putting 1 to 2* in this table added no timing on a knock free WOT pull. I did it at the end of the tune just to see so I didn't try adding anymore timing then 2* as it was a customers car.

I found this odd, because I tried the same thing a day before on a Evo 9 with stock turbo and 1* in this table added 1* on top of the normal ign map.

Wondering now if Maf HZ is tied into this at all as the FP3065 was obviously flowing more air. Maf HZ was about 300-400 higher than the 9 with stock turbo.

 

There are quite a few variables that affect whether this dynamic advance maps are used. If you guys think there is value to implementing these maps, I could try to understand what these variables are.