Knock retarding without knock counts

[budwizer]

Delco u could be onto something.. Didn't have much to do with building of the motor.. Just asked him about it.. Seems the exhaust may be hitting the "high energy" sump!
I shall suss it and get back to everyone..

Vl still out of curiousity can u post an example of setting up the bkrtd settings maybe even in the advanced tuning document?

Thanks, will keep u updated!
Andrew.

[VL400]

Vl: So i setup the msg6 and it is logging knock counts however with the knock counter it doesn't seem to be incrementing at all. It stays at 0, what settings does it need. And is there and is there any examples around of setting up burst knock retard?

Should just need to open the flashtool, connect to the ECU, then under Binary functions open the 12P message editor. The 8th item can be changed to 'Knock Counter' instead of the default 'Knock'. The standard message 6 ADX can be used without any changes, instead of seeing a delta knock count value for a 12.5ms period (which is easy to miss) it shows the raw counter value that will increment each time there is knock. It tests ok on the bench but its hard to get it to just increment a few counts...

Counter.png (13.36 KiB) Viewed 3009 times

Vl still out of curiousity can u post an example of setting up the bkrtd settings maybe even in the advanced tuning document?

The advanced guide has some info about each item and how it works but I always have it disabled as it ends up just making throttle response a bit mushy.

[budwizer]

Well in the flashtool i tried adding both of the bkrtd and the knock counting however neither seemed to work in the logging.. The bkrtd would sometimes show a constant 171 or 150 in different logging sesions but it wasn't enabled so im not worried but coyld there be a conflict between knock an knock counting as they were both in it.

As for my issue we made some progress, massaged the sump away from the extractors..
Still knocked a bit but didn't seem as frequent. So thanks delco for that..
But with the other knocking it is showing i removed 10 degrees on timing from 1600-2400 in the 80-100kpa areas..And that seemed to remove all knock.. And didn't show any more no matter what we tried.
Am i right in thinking that the fact that the plenum space is alot bigger due to the come manifold that the tip-in spark or other offset removal isn't enough?
I did try increasing the ae-rpm table but it didn't seem To react fast enough and just at the start of the commanded 12.5 afr the wideband was still leanish at the start.
Sorry if its a bit jumbled,
So what im asking is what offset whether it be time or spark should i edit to possibly remove more timing just as the tps gets a stab?
Or other potential thoughts on my issue?
Thanks, Andrew.

[VL400]

Well in the flashtool i tried adding both of the bkrtd and the knock counting however neither seemed to work in the logging.. The bkrtd would sometimes show a constant 171 or 150 in different logging sesions but it wasn't enabled so im not worried but coyld there be a conflict between knock an knock counting as they were both in it.

There wont be any conflicts, you can even have multiple bytes in the data frame defined as the same thing if you wanted.

Did you add the BKRTD and knock counter as new items or replaced existing? If you added them as new items the message 6 frame would then be two bytes larger, did you setup the TunerPro listen message to the new size when adding them in?

I setup a proper test with a generator and it steps through nicely with some knock pulses. Starts at 0, counts to 255 and resets like it should. I dont have a running vehicle to test this on though.

Counter.png (35.65 KiB) Viewed 3000 times

[budwizer]

No i don't think I setup tuner pro to listen to 2 extra bytes.. However i shall suss it out and do some logging for you and ensure it works..

Will just have to figure out this knock issue.. Am what i hypothesize about a larger plenum size and the offsets for the rpm/spark retard aren't large enough as they wouldn't be able to account for the extra air/leanness?

What adjustments can be made to adjust this?

[festy]

To work out if it's false knock or not you could try setting 'ESC params - coolant temp enable' to 150 and then log knock counts. If it's real knock then you should see the counts increase a lot (no KR to cancel the knocking), but if it's false knock you'd still only see a couple of knocks in the logs like you do now.