GrannySShifting

iTrader: (10)

Reporting 18-20 degrees timing, starting with a stock 99-00 file. Following the MAF/RPM it should have been looking up between 26-32 degrees timing. Wasnt showing knock on 4 or the 5 runs, and it showed same timing regadless.

If you throw a P0327 or the other knock sensor code I know it will read in that table, and the car had thrown that code two times before over a long time period though. Cleared the codes, and they havent been back since, but still reporting timing in the pits.

Richard@WCCH

iTrader: (3)

Have you checked the "timing vs coolant temp" table? It was added to version 1.31.

Richard

GrannySShifting

iTrader: (10)

It was normal, 195 degrees

Bink

Flashing the PCM with Edit should put you back to 100% use (factor) of the High Octane Table. Go to Eng Cal -> Ignition -> Knock learn -> Min RPM. Set Min RPM to a value you'll not see- say 6800 RPM for example. This will hold it in the high Octane Table......scan and check your values for Spark Advance.


You might want to increase your rate of decay (Knock), also. Eng Cal-> Ignition-> Knock Retard -> Decay vs RPM - set it @ 128, all cells. FWIW.

joel

GrannySShifting

iTrader: (10)

i know i cna FORCE it to run in High Octane table, but really dont want to bandaid, want to know why it is.

JxxxOxxxE

iTrader: (1)

If I remember, there are quite a few things that can reduce timing...What was you IAT at the time? Just look through all the parts in EDIT, you will come across different tabs that can reduce the timing....

GrannySShifting

iTrader: (10)

Yeah the IATvsRPM stuff is what i woudl normally look at first, but it was 35 degrees out when we were dynoing and the bay door 15 foot away is open. i had a jacket on so I HOPE IATs werent 45 deg. celsius

Bink

Purpose isn't to FORCE it into the high Octane table.It's diagnostic -you're eliminating "knock learn", high and low octane tables. Then you can evaluate timing reference. Does it then drop into the Base Spark Idle and drive tables? FWIW.

joel

GrannySShifting

iTrader: (10)

as long as its reading over 1% tps it should never be in the closed throttle tables right, its soley off of TPS correct?

Bink

Not always - the PCM can reference the Base Spark tables at any Throttle position. Fortunately it doesn't seem to normally do this.

There are instances where it (the PCM) will chase the timing to the lowest timing value available- regardless of the table "name". I don't know how it does it, but it can be followed by testing with Edit changes and subsequent scans. I've seen it with my Z06 along with a fueling issue - just so you know I'm not blowing internet smoke here.

I believe it was a post by NoGo (He is The MAN) where it was stated that default states were present and the PCM would chase timing advance to the lowest table value.

Hope this helps some. Good Luck. FWIW.
joel

GrannySShifting

iTrader: (10)

Hmm I wonder if he knows when/wehre/why it would do this

Bill Bowling

iTrader: (6)

What do you think of changing both the decay and min rpm even if you are not having any problems?

BowlingSS

Bink

Personally, I wouldn't increase the min learn value - unless for tuning or diagnostic purposes. I was told by a "PCM Guru" to increase my knock decay value to 128 - so I did. He said stock value was very slow.
joel