help kr* problem

[joecar]

This is also not the problem, but I would set D0961, D0962 to 100% all across...

if you need to adjust part throttle downshift timing, edit the PT upshift/downshift tables (under Shift at VSS).

[blackbeast ss]

BBSS,

This is not be the problem, but do set the out-of-range tables to in-range values (use max-1 or min-1) and save the file:

how do i do that....thanks joecar

[joecar]

Questions:

- can you hear it knocking...?
- did it start showing up immediately as a result of the stall/trans install...?
- check that your spark plug gap is correct (and suitable for boost);
- check your spark plugs for carbon fouling;
- check your PCV plumbing and intake manifold for evidence of oil;
- check/clean your MAF sensor;

If you ran 114 then the knock may not be fueling related...

Observations:
- your wideband indicates you are running richer than commanded...
- you have boost, and your MAP sensor only goes to 1 bar;
- your MAF sensor is getting up there (481 g/s), it's approaching the PCM's limit.
- your OS doesn't support boost (altho it supports ethanol).
- your timing B5913 seems high for boost.
- the second WOT run in "log correct afr pid.efi", FUELSYS momentarily goes to CL during WOT (on the upshift) and this seemed to induce KR (see pic)... I don't understand why it went CL on the upshift?
- the first WOT run in the same file, show low/medium load knock, leads me to think it's not due to fueling (see list of items above);

I though a looser stall "softened" the load on the motor...
if that it the case, then the PCM is looking up timing for a lower load...
you should maybe reduce your timing tables B5914/B5913.

If you log GM.DYNCYLAIR (2 channels) we can reference B5914/B5913 easier...
but if you do this remove 1 other pid (like IBPW2 (it seems to follow IBPW1 always)) to keep channel count at 24 or less.

[joecar]

how do i do that....thanks joecar

In the tables listed as OOR, see the cells marked with blue dog-ear corners, take note of the values, enter some value that is in range (like min+1 or max-1), do this on all OOR cells, then save file, exit tunetool...

then re-open tunetool, go to those same tables and insert the old values back in those cells, save file, exit tunetool, reopen and verify no out-of-range messages.

Explanation: when the tunetool sees an OOR value, it displays the closest of min or max... when you then enter min or max, the tunetool thinks you did not edit the cells (since it compares what you entered to what it was displaying)... so you have to enter something different and save/exit, reopen and enter your proper min or max... little bit tricky.

[blackbeast ss]

Questions:

- can you hear it knocking...?
- did it start showing up immediately as a result of the stall/trans install...?
- check that your spark plug gap is correct (and suitable for boost);
- check your spark plugs for carbon fouling;
- check your PCV plumbing and intake manifold for evidence of oil;
- check/clean your MAF sensor;

If you ran 114 then the knock may not be fueling related...

Observations:
- your wideband indicates you are running richer than commanded...
- you have boost, and your MAP sensor only goes to 1 bar;
- your MAF sensor is getting up there (481 g/s), it's approaching the PCM's limit.
- your OS doesn't support boost (altho it supports ethanol).
- your timing B5913 seems high for boost.
- the second WOT run in "log correct afr pid.efi", FUELSYS momentarily goes to CL during WOT (on the upshift) and this seemed to induce KR (see pic)... I don't understand why it went CL on the upshift?
- the first WOT run in the same file, show low/medium load knock, leads me to think it's not due to fueling (see list of items above);

I though a looser stall "softened" the load on the motor...
if that it the case, then the PCM is looking up timing for a lower load...
you should maybe reduce your timing tables B5914/B5913.

If you log GM.DYNCYLAIR (2 channels) we can reference B5914/B5913 easier...
but if you do this remove 1 other pid (like IBPW2 (it seems to follow IBPW1 always)) to keep channel count at 24 or less.

- can you hear it knocking...?no kind of hard with the exaust
- did it start showing up immediately as a result of the stall/trans install...?yes
- check that your spark plug gap is correct (and suitable for boost);new plus gapped to 0.35 tr6
- check your spark plugs for carbon fouling;good
- check your PCV plumbing and intake manifold for evidence of oil;checked and its fine
- check/clean your MAF sensor;cleaned maf last week...


about the riches and think my wideband sensor is bad i need to replace it that started to happend about two months ago and i wasnt getting any knock ok i will do another log with that pid

[blackbeast ss]

ok heres 2 more logs with the pid you requested.......i hit more kr*in these to logs only cahnges i did were fixed the out of range and d0961 d0962.......and the wide band it self is reading mid to low 11 afr on my gage but on efilive its not reading correctly its going as low as 8.9 afr so my wideband is fine

[driver456]

Check and make sure your header's or exhaust isn't banging against anything.................Paul

[joecar]

Thinking Out Loud (TOL):

I think the cylinder airmass may be wrong and the PCM is looking up the wrong timing.

Also, in those two logs (20, 21), there are 3 instances where the PCM enters CL momentarily during WOT (causing AFR to spike to stoichiometric) and KR registers shortly thereafter.

[joecar]

I though a looser stall "softened" the load on the motor...
if that it the case, then the PCM is looking up timing for a lower load...
you should maybe reduce your timing tables B5914/B5913.

I think maybe this is what is happening.

[blackbeast ss]

I think maybe this is what is happening.

how much timming do you think i should take out?