Hey Guys,

Do you get that feeling that sometimes your car just feels crap?

If you look at your timing logs you will see that "sometimes" timing doesn't match whats in the maps.

If you log MUT06 (normal timing) and MUT33 (timing from the maps) you will see a discrepancy... The difference between MUT33 and MUT06 is MUT06 has all the Ign Corrections applied (air temp, coolant temp, baro etc etc)

However there is one "weird" correction that gets applied, not really sure what it does... I have sent MrFred the details so hopefully we can understand it soon.

FAA bit 10 (ie 0x0400) controls whether this "weird" correction is applied or not.

As soon as I disable FAAbit10 my timing for low load stuff goes straight to whats in the map... (Other corrections - airtemp,coolant etc are STILL applied).

I have looked through the code and FAAbit10 ONLY affects this so it seems fairly safe to disable.

One word of WARNING - perhaps lower your timing if you are running a LOT as as soon as you disable this bit the timing will jump up anywhere between 3* and 8*...

I am too busy atm to post up graphs to show you, but please feel free to log MUT33 and see for yourself (use the same EvoScan line, just change 06 to 33 and log both together...)

Cheers
D.

 

First reply. WOOT. :-) Seriously though, I haven't looked at disassm yet, but I think I know which correction you are talking about. I recall looking at one subroutine that was giving me a headache, so I moved on. :-) I'll try to take another look tonight after I finish up revising my closed loop wideband patch.

 

Isnt bit 10 the one that was labeled cold start ign retard? Or is that bit 9? Gotta go look at my notes now.

I know that I disabled one or the other and the cold start timing now matches the maps. 54 instead of 56.

 

11 = EGR
9 = ColdStart Retard
10 = Make car run good all the time

lol

 

I just looked and realised I lost

Oh well, only way to get smarter is to learn and remember

 

Seems like either way I must have turned it off though...unless I am now losing at binary.

54D8= 101010011011000 ?

 

Use the blobbits in EcuFlash.

You have it turned on.

 

I have noticed timing areas that don't match up even without knock. What would be the reason for this?

 

There are a bunch of Ign Trims going on for various things:
Air Temp
Coolant Temp
Barometer
This Weird one.. Not really sure what its for, all I know is it pulls timing unnecessarily..

If you log MUT06 vs MUT33 you can see the trims in affect (MUT33 is timing from the map, MUT06 is final timing)

 

this is a IX thing right?

 

mmmm dont know.

best way to tell:
LOG MUT33 along side MUT06 (same EvoScan formula)
Warm up car
go for a short drive, just part throttle stuff

review the logs - you should see that between 1500rpm and 3000 rpm there is a deviation between 33 and 06 - ranges from 3* and 8*

If you do see it - then go ahead and disable the bit and then relog and see if MUT06 lines up with MUT33...

I would guess its Evo7-9 wide...

 

I will try logging the map timing vs. the corrected timing on my VIII tomorrow.

So how exactly do I go about disabling this "bit10" thingy?lol

 

glad you asked Jamie...Tephra is talking that Matrix stuff again.

I haven't touched the MUT tables since doing the 3d mut tables. The first number is on the Y axis? and the second number is on the X? or vice versa?

 

you dont need to touch the MUT table at all, stock MUT33 is uncorrection IgnAdv...

FAA bit10 is one of those perephery bits - dont worry about that for the time being, just verify MUT06 and MUT33 are different

 

ok. Is 0 on the Y axis 6 on the X axis? Thanks for verifying