COS 3 timing question

[CC&M]

I'm using 02020003 and have what is probably going to amount to a stupid question. No matter where I set the timing tables it will not go over 32 degrees of timing. I have raised the amount of timing in B5913, B5919 as well as zeroing out the tables I don't use. I have logged the EST_PID's and have not found any that are removing timing. I uploaded my .tun if anybody wants a look.

[joecar]

Post some logs.

[CC&M]

Here are a couple that I have done yesterday and day before.

[CC&M]

Logs are posted, anybody seen anything that resembles this? Would really like to get this solved.

[joecar]

Can you log GM.DYNCYLAIR and GM.EQIVRATIO also...?

I can't see what's wrong (other than LTFT's are large).

Fix the out of range values in A0012, A0013.

Try this experiment: set A0000 to Enable, set A0001 to 100%...

If you now get the correct timing, set A0000 to Disable and see what timing does.

[CC&M]

Thanks Joecar,
I'll try logging it to see what I get. I did have A0000 enabled at one point with A0001 at 50%. When it was like that it blended the tables perfectly. My LTFT is like that because it has a big percentage of E85 in it. I had a couple jugs left over after race season that I dumped into the pickup to use it up. I'll set A0013 and A0014 to lower values, they don't show up as out of range on my computer.

[joecar]

Oops, I meant GM.EQIVRATIO... I corrected its spelling in my post above.

[CC&M]

Joecar,
Here are a couple quick logs that I did earlier after I made the changes to A0000 and A0001. The timing still tops out at 32.5 even though the forced octane scaler is at 100%. Now I don't feel so bad that I haven't been able to find what is wrong. 0024.efi is a cruise type situation. 0025 is a full throttle run, or at least the best I could get on a wet road due to wheelspin.

[5.7ute]

Wouldnt hurt to log GM.ASPARK with those pids.

[CC&M]

Here are some more logs with adaptive spark logged. I have also logged the EST.PIDS in the past and come up with nothing conclusive either.

[5.7ute]

You should also be logging DYNCYLAIR_DMA in SD, not CYLAIR_DMA which is maf based.
Did it have this problem with a standard OS?

[joecar]

Here's what I think, my 2¢ "theory"...

your SPARKADV is dead-nuts perfectly flat at 32° under most conditions...

this is just not possible since the cylinder airmass will not be the same value always...

i.e. even under steady state conditions the cylinder airmass will show minor fluctuations...

this may be pointing to your cylinder airmass not being computed correctly from its source... for some reason or other...

but, having said all that, I'll still keep looking thru your files.

:)