Tuning saga.. tuner said possible bad PCM?
#42
![Default](https://ls1tech.com/forums/images/icons/icon1.gif)
This is the rate at which knock retard is removed in the absence of further knock. The higher this value is the faster knock retard will be removed.
#43
![Default](https://ls1tech.com/forums/images/icons/icon1.gif)
hi again - i made some changes and the KR improved but i'm still seeing it.
Saturday 2.13 change –
• reduced knock sensitivity from stock 1998 to stock 2004 z06..
• increased decay rate table to .25
• the Cold Power Enrich Enable TPS Threshold vs. RPM. Back to stock (from 10% my tuner).
Sunday 2.14 – as mentioned in this thread, timing seemed high in low rpms. So decreased timing in lower RPMS (just Copied stock z06 in lower areas)
Monday 2.15 change - raised Knock Sensor Level vs. Tip In TPS Copied from stock z06 file. I should have done this at same time as the saturday 2.13 change (knock sensitivity) but didn't know. I have no log files of this yet as i just figured out. I wonder if this would have an effect
New tune attached, as well as log file from yesterday. all pulls in 4th. the first 2 bursts were clean with no KR but the final burst in the log shows 3 instances of KR with the last going up to 1.7.
Thoughts?
Also why is it referencing the low octane table? I separated each table by 2 degrees.
Saturday 2.13 change –
• reduced knock sensitivity from stock 1998 to stock 2004 z06..
• increased decay rate table to .25
• the Cold Power Enrich Enable TPS Threshold vs. RPM. Back to stock (from 10% my tuner).
Sunday 2.14 – as mentioned in this thread, timing seemed high in low rpms. So decreased timing in lower RPMS (just Copied stock z06 in lower areas)
Monday 2.15 change - raised Knock Sensor Level vs. Tip In TPS Copied from stock z06 file. I should have done this at same time as the saturday 2.13 change (knock sensitivity) but didn't know. I have no log files of this yet as i just figured out. I wonder if this would have an effect
New tune attached, as well as log file from yesterday. all pulls in 4th. the first 2 bursts were clean with no KR but the final burst in the log shows 3 instances of KR with the last going up to 1.7.
Thoughts?
Also why is it referencing the low octane table? I separated each table by 2 degrees.
#44
10 Second Club
iTrader: (26)
![Default](https://ls1tech.com/forums/images/icons/icon1.gif)
ok yes it says same thing in hp tuners... how much to pull after knock has STOPPED. so i changed as per your suggestion. see attached. right?
This is the rate at which knock retard is removed in the absence of further knock. The higher this value is the faster knock retard will be removed.
This is the rate at which knock retard is removed in the absence of further knock. The higher this value is the faster knock retard will be removed.
#45
10 Second Club
iTrader: (26)
![Default](https://ls1tech.com/forums/images/icons/icon1.gif)
hi again - i made some changes and the KR improved but i'm still seeing it.
Saturday 2.13 change –
• reduced knock sensitivity from stock 1998 to stock 2004 z06..
• increased decay rate table to .25
• the Cold Power Enrich Enable TPS Threshold vs. RPM. Back to stock (from 10% my tuner).
Sunday 2.14 – as mentioned in this thread, timing seemed high in low rpms. So decreased timing in lower RPMS (just Copied stock z06 in lower areas)
Monday 2.15 change - raised Knock Sensor Level vs. Tip In TPS Copied from stock z06 file. I should have done this at same time as the saturday 2.13 change (knock sensitivity) but didn't know. I have no log files of this yet as i just figured out. I wonder if this would have an effect
New tune attached, as well as log file from yesterday. all pulls in 4th. the first 2 bursts were clean with no KR but the final burst in the log shows 3 instances of KR with the last going up to 1.7.
Thoughts?
Also why is it referencing the low octane table? I separated each table by 2 degrees.
Saturday 2.13 change –
• reduced knock sensitivity from stock 1998 to stock 2004 z06..
• increased decay rate table to .25
• the Cold Power Enrich Enable TPS Threshold vs. RPM. Back to stock (from 10% my tuner).
Sunday 2.14 – as mentioned in this thread, timing seemed high in low rpms. So decreased timing in lower RPMS (just Copied stock z06 in lower areas)
Monday 2.15 change - raised Knock Sensor Level vs. Tip In TPS Copied from stock z06 file. I should have done this at same time as the saturday 2.13 change (knock sensitivity) but didn't know. I have no log files of this yet as i just figured out. I wonder if this would have an effect
New tune attached, as well as log file from yesterday. all pulls in 4th. the first 2 bursts were clean with no KR but the final burst in the log shows 3 instances of KR with the last going up to 1.7.
Thoughts?
Also why is it referencing the low octane table? I separated each table by 2 degrees.
As far as why its referencing the low octane table, its probably because of the octane scalar pushing it towards the low table. Basically the PCM does a blend between the high and low octane table from 0-100% depending on how much knock the engine has seen over X amount of time. If you've had so much knock, real or false, the octane scalar will move entirely towards the low octane table. Theres actually a PID for this something like gm.scalar or something like that that you can log to see it.
Can you zoom in on those pulls, your MAF curve looks super busy and not smooth at all.
#46
![Default](https://ls1tech.com/forums/images/icons/icon1.gif)
hi - those 3 bursts are all in 4th gear.
is the busy MAF graph indicative of .... ?
Is there something i can reset to make it look at high octane table again?
also i read there is a table that makes that scalar go quicker back to high octane but not sure where its located.
is the busy MAF graph indicative of .... ?
Is there something i can reset to make it look at high octane table again?
also i read there is a table that makes that scalar go quicker back to high octane but not sure where its located.
#47
10 Second Club
iTrader: (26)
![Default](https://ls1tech.com/forums/images/icons/icon1.gif)
hi - those 3 bursts are all in 4th gear.
is the busy MAF graph indicative of .... ?
Is there something i can reset to make it look at high octane table again?
also i read there is a table that makes that scalar go quicker back to high octane but not sure where its located.
is the busy MAF graph indicative of .... ?
Is there something i can reset to make it look at high octane table again?
also i read there is a table that makes that scalar go quicker back to high octane but not sure where its located.
As far as getting the scalar back to the high octane table, the only thing that ever worked for me was driving the car and lots of part throttle over 2k rpms. I could log the car and literally watch the octane scalar move towards 100% high octane table while giving it part throttle. It can take a little while but itll move that way. Of course, if you got WOT again and pick up a bunch of knock itll go right back down.
#49
Moderator
iTrader: (4)
Join Date: Jul 2014
Location: My own internal universe
Posts: 10,446
Received 1,838 Likes
on
1,146 Posts
![](https://ls1tech.com/forums/images/ranks/ls1tech10year.png)
![Default](https://ls1tech.com/forums/images/icons/icon1.gif)
Your MAF calibration curve has a lot of up and down to it. There are areas where increased frequency is showing decreased airflow. Highlight the entire MAF table and hit the polynomial smoothing button one time only.
Under Airflow-->dynamic change the "dynamic Air Filt" value to 0.1758, which is the stock 1999 setting.
Those two changes should smooth out the MAF response a bit
Under Airflow-->dynamic change the "dynamic Air Filt" value to 0.1758, which is the stock 1999 setting.
Those two changes should smooth out the MAF response a bit
#50
![Default](https://ls1tech.com/forums/images/icons/icon1.gif)
thanks
![Happy](https://ls1tech.com/forums/images/smilies/LS1Tech/gr_stretch.gif)
#51
Moderator
iTrader: (4)
Join Date: Jul 2014
Location: My own internal universe
Posts: 10,446
Received 1,838 Likes
on
1,146 Posts
![](https://ls1tech.com/forums/images/ranks/ls1tech10year.png)
![Default](https://ls1tech.com/forums/images/icons/icon1.gif)
**** I forgot you're MAF only. Same screen there is a MAF filter. Multiply it by 90% (0.9). Lower filter numbers smooth out signals. Higher filter numbers react faster.
You should really do the poly smoothing on your MAF curve too
You should really do the poly smoothing on your MAF curve too
#53
Moderator
iTrader: (4)
Join Date: Jul 2014
Location: My own internal universe
Posts: 10,446
Received 1,838 Likes
on
1,146 Posts
![](https://ls1tech.com/forums/images/ranks/ls1tech10year.png)
#56
![Default](https://ls1tech.com/forums/images/icons/icon1.gif)
notice "WOT Entry Max Airflow" is disabled. ok to remain disabled? I see its disabled in stock 2004 z06 as well. But in z06 file, "MAF Airmass Filt" is lower than my setting, at .0898. Which means it reacts slower like you want (I think)?
Last edited by 2MCHPWR; 02-17-2016 at 10:36 AM.
#58
Moderator
iTrader: (4)
Join Date: Jul 2014
Location: My own internal universe
Posts: 10,446
Received 1,838 Likes
on
1,146 Posts
![](https://ls1tech.com/forums/images/ranks/ls1tech10year.png)
#59
Moderator
iTrader: (4)
Join Date: Jul 2014
Location: My own internal universe
Posts: 10,446
Received 1,838 Likes
on
1,146 Posts
![](https://ls1tech.com/forums/images/ranks/ls1tech10year.png)
#60
Moderator
iTrader: (4)
Join Date: Jul 2014
Location: My own internal universe
Posts: 10,446
Received 1,838 Likes
on
1,146 Posts
![](https://ls1tech.com/forums/images/ranks/ls1tech10year.png)
![Default](https://ls1tech.com/forums/images/icons/icon1.gif)
Yes. This should slow down the MAF response time a bit
I've never messed with this setting. if I don't know what it does, I leave it alone.
Exactly. Since that is a stock setting, it should be fine to use that instead. That was my stock VE correction filter setting, so I know it' s safe
notice "WOT Entry Max Airflow" is disabled. ok to remain disabled? I see its disabled in stock 2004 z06 as well.
But in z06 file, "MAF Airmass Filt" is lower than my setting, at .0898. Which means it reacts slower like you want (I think)?