Rybar

iTrader: (11)

Have been having an on going rattling noise problem, trying to see if my car is detonating but don't know what to look for in this scan I did.

Please someone take a look and let me know what you see.

See related thread:

https://ls1tech.com/forums/general-m...69-camaro.html

Thanks,
Ryan

sreve

iTrader: (3)

Did a couple quick scrolls thru it, saw a bunch of idle time.
Is the thermostat stuck open? not much more than 120F coolant temp.
O2s seem to stay below 450mv which account for the really lean fuel trims.
Are the O2 heaters working?

Rybar

iTrader: (11)

Hey thanks for looking. I'm kind of scared to go wot too much. But I did for like 1-2 seonds just after the 7 and 9 minute marks.

Thermostat is new and have no clue if the O2 heaters are working.

I did notice at wot the KR goes to full, does this mean it's detonating??

sreve

iTrader: (3)

Ok it looks differnt now i was looking at the table display and it was not changing much graphs seem to work, making everything in my last post null & void. Beta issue?

Rybar

iTrader: (11)

Here's a second scan file and DTC file

ctd

iTrader: (1)

I think the best would for you to drop the car with me, very nice!

Looked at your last log, there is no knock in the rpm range you hear the noise. The only knock occurring in the log is when you first begin accelerating from a dead stop. The worst is frame #12069, 3* of KR @ 2418 rpm, then you will see 1* of KR @ frame #12071 @ 1795 rpm then it tappers down to 0* by frame #12111 @ 2844 rpm. Then is pretty much the same pattern & always out of the range of your noise. Your tuner can easily fixed this although it is not your problem as described.

Rybar

iTrader: (11)

Strange because I did a couple short wot blasts just after the 7 minute and 9 minute marks on Scan 1 and scan 2 at 7:50, 21:00 and 21:30 and the KR goes full blast up to 10.

ctd

iTrader: (1)

I only viewed your last scan, just did another quick look.........sorry.

Post a screen shot of what you say.

Rybar

iTrader: (11)

Hey thanks for your reply. I now see the most KR I had was about 3.9

I think you are right, this noise seems to be something mechanical rather than detonation.

These screenshots of the KR may help:

ctd

iTrader: (1)

I went & had look at the first log after viewing your screen shots. The higher rpm knock was not on the second log. I'm very sure you are hearing the knock as your TPS drops as soon as the the KR appears. You have good ears?

So we are back to you dropping the car with me for a while!

Your first log shows what you are hearing at the RPM you describe....easy tuning fix......are you set up for WB?

Rybar

iTrader: (11)

I don't have a WB but could purchase one again. Used to have the Innovate LM1 but sold it after the dyno tune.

If you could get rid of this noise I'd lend you the car to drive no problem.

ctd

iTrader: (1)

OK I'm sure it's safe to assume you have not made any tuning changes?

Please post the tune, are you comfortable with making suggested changes to the tune?

I'm guessing the noise you are hearing maybe referred to as "pinging" not detonation as you suggested in your original post.

Rybar

iTrader: (11)

No changes were made, but I'm open to all suggestions.

I'll attach the tune. Pinging/detonation is not the same thing??

ctd

iTrader: (1)

Nope.

ctd

iTrader: (1)

Spent some time looking at you two logs & your tune. My suggestion just to verify that it is pinging that you are hearing, would be to copy from the Knock Histo in both logs, then Paste Special Subtract to the main timing map.

If that solves the noise you are hearing then you can decide on the more permanent solution.

My other question is, does it drive properly at lower speeds?

I'm sending you a PM with my email address if you need some help with making the changes I've suggested.

Frost

iTrader: (45)

Why copy the whole KR histo and subtract it? That's gonna carry a bunch of garbage with it into the spark map. You have the root of the KR event but then it holds on after the knock and then decays. All of that time after the initial hit shows up in the histogram it's populating, but there was originally only one spot that was the offender...