That would be fairly odd if thats true but I'm not sure.

what I can see is its not in the normal timing space as it were. The routine that subtracts timing due to knock is on the other side. So this routine would be in a completely different space.

The second value is in some sort of default space where the value is set instead of going through the normal timing adjustment routine. It resets all the ATU stuff and slams in that value into the timing after knock ram space.

 

Probably was a bored Mitsu engineer with a month of lag time.

 

I wonder if we can set the lowerbound timing in the idle area to help dial in idle with the SAS Mode feature. I'm not sure if this setting you found would take priority and override that table though.

 

Are you sure that it locks the timing at 5deg and doesn't just lock it at whatever is set on the crank pulley?

Andy

 

It definitely does something to the timing its just in another direction than the typical timing route.

 

Is that XML good foor 94170015?

Wanna see results for this...

 

Definitely not the address for 9417 is much different.

 

Ight ill stay posted.

Thanks

 

Would you be fine with testing it could be dangerous if your not carefully watching everything.

 

9417 Locations:
<scaling name="IgnTimingECUa" units="deg" toexpr="61-x*90/256" frexpr="(61-x)*256/90" format="%.1f" min="-30" max="50" inc="1" storagetype="uint16" endian="big"/>
<table name="Ignition Timing Default" address="247E6" type="1D" level="1" scaling="IgnTimingECUa"/>
<table name="Ignition Timing Default 2" address="25912" type="1D" level="1" scaling="IgnTimingECUa"/>

 

I would test it, but im currently deployed. So theres no way i cant

 

What is the Table called?

 

I'll do it....what do you need me to log. I'm using 9417..

I'm running big cams. And I've found it difficult to dial in a decent idle while using SAS.

Let me know. I have all day tomorrow to get you some useful data

 

Well change it to something else like 6 degrees and log timing when cranking. Then attempt timing when SAS is enabled and see what happens. If it logs or not.

If its not raising the base timing up we could trying something more extreme like 8 degrees and with SAS activated it should idle noticably higher.

 

Ignore me, I'm talking rubbish... If it just set it to whatever was set on the crank signal then you would have no way of ever being able to set the crank pulley in the 1st place.

I've just checked through my Evo 3 disassembly and it is actually set in the CAS part of the code although the values are different to 'normal' timing values as they are referenced to around 60 degrees BTDC IIRC and it is set as two multplied values rather than a single figure.

I'll be playing with my E3 tomorrow so I can change some of the values and see if it affects it and if it does then I can post up the code routine so you can compare it with the later ECU code and see if anything looks familiar.

Andy