fed up with knock control
Oct 16, 2008, 07:19 PM
#33
Many stock ECU's are plagued with this issue. We asked Tephra over a year ago if there was access to this rpm ignore, to no avail.
I have seen a car or two that was so severe that I told them to sell it.
I have an OEM block back in the car and it still does it on my 96940011 with Cosworth M2, INJEN intake.
I have seen a car or two that was so severe that I told them to sell it.
I have an OEM block back in the car and it still does it on my 96940011 with Cosworth M2, INJEN intake.
Oct 16, 2008, 10:28 PM
#37
i would like to disable it below a certain rpm, reason being that my knock is load independent
if possible i would still like to see the knock sums throughout the rev range, but that is a secondary concern
maybe enable knock control only when exceeding a certain load and rpm
if possible i would still like to see the knock sums throughout the rev range, but that is a secondary concern
maybe enable knock control only when exceeding a certain load and rpm
Oct 16, 2008, 10:40 PM
#38
1. Certain load and RPM
2. Still able to log actual knock count no matter the settings
3. Also be able to set knock retard ceiling, example: ignore (do not pull timing) for knock counts 6 and below
If I had to pick two it would be #2 and #3
If I had to pick one it would be #3
Oct 16, 2008, 11:43 PM
#41
Right well I think I have found the piece of code that controls what todo with IgnAdv when knock is encountered....
It's not immediately obvious to me how it works, but we can hook in at the top of routine and add in whatever conditions we want.
Obviously this wont affect the OctaneLevel stuff (yet) so if you hit more than 6 twice it will still start reverting to low octane maps. However it should stop timing from being pulled.
I want to keep the conditions as simple as possible, so let me think about the best combination of those..
edit - Incidentally I *may* have found the code that controls the max ign retard (ie -10) - I will fiddle with this and see if I can log -20 or something
It's not immediately obvious to me how it works, but we can hook in at the top of routine and add in whatever conditions we want.
Obviously this wont affect the OctaneLevel stuff (yet) so if you hit more than 6 twice it will still start reverting to low octane maps. However it should stop timing from being pulled.
I want to keep the conditions as simple as possible, so let me think about the best combination of those..
edit - Incidentally I *may* have found the code that controls the max ign retard (ie -10) - I will fiddle with this and see if I can log -20 or something
Last edited by tephra; Oct 16, 2008 at 11:50 PM.
Oct 17, 2008, 04:42 AM
#42
Evolved Member
iTrader: (26)
Join Date: Oct 2005
Location: Pittsburgh
Posts: 1,712
Likes: 0
Received 0 Likes
on
0 Posts
My wishlist:
1. Certain load and RPM
2. Still able to log actual knock count no matter the settings
3. Also be able to set knock retard ceiling, example: ignore (do not pull timing) for knock counts 6 and below
If I had to pick two it would be #2 and #3
If I had to pick one it would be #3
1. Certain load and RPM
2. Still able to log actual knock count no matter the settings
3. Also be able to set knock retard ceiling, example: ignore (do not pull timing) for knock counts 6 and below
If I had to pick two it would be #2 and #3
If I had to pick one it would be #3
Oct 17, 2008, 05:27 AM
#45
Evolved Member
iTrader: (5)
Join Date: Dec 2003
Location: NW Georgia
Posts: 1,378
Likes: 0
Received 0 Likes
on
0 Posts
I'll add a +1 to Razorlab's post...
Last edited by Dyno4mance; Oct 17, 2008 at 05:36 AM.