+1

 

what about a cross of the two.

a 3d subtractor table with RPM/LOAD on the axis.

So basically the same as the current % table, but using a subtractor instead.

That way you can cancel out "known" knock, but anymore will trigger ign retardation.

 

I think thats the safest way. I think we all know that a lot of users would have just set a good portion of their map to 0% or close to it anyways.

So is there a way we can log the actual knock and the KS that the ECU is seeing with the 3D subtractor map editing the value? Maybe a way to choose whether the CEL flash on knock feature can be optioned to show actual KS or the edited KS?

 

-0 or 100% :P

 

Yea dude this is what we need. We need to set the threshold of what RPM we want the ecu to start reading knock. Wether it be 2k, 3k , 3,300 or so on.
That would be perfect!!

 

Would it be possible to have a min. knock count for pulling ignition timing table? (Just a box that you enter a knock value) That way if you want it to ignore a certain knock count and not pull any timing it will and above that # it looks at the knock the same and pulls ignition timing the same.

Then have way we can completely disable knock at certain load/rpm areas on a map like for part throttle areas etc...

 

yeah ok - so instead of a subtractor we have a "ignore ks below this number" table

 

well with the above quoted example it would be ignore knock ABOVE a certain value

 

Yeah - because I hate the fact my IX pulls 1 degree for every count of knock so the random 1-3 counts at wot is annoying because its so inconsistent pull to pull sometimes. So if we can just have a way to completely ignore a value of knock and under that value it could help a lot. So if its set at "3" it would ignore 3-2-1 counts and 4 would pull timing as always (just an example).

That is what I am kinda looking for in a tunable knock system along with ignoring low load / part throttle knock.

 

If by subtractor the code will work such that:

Example1 : You have the value of 4 plugged into the load/rpm cell that the car is on right now. You get a knock sum of 2. The ecu acts like no knock is occuring (but the user can still log that 2 knock sums are being reported before your code makes things right).

Example2: You again have 4 pluged into the load/rpm cell the car is on right now. The stock code reads 6 real knock counts, but with your code pulls timing such that it is 2 knock counts. Again the user can log both the stock knock sums and the knock sums after your code makes things right.

The 3d table would take care of people with "phantom" knock when cruising on the highway. If they see a random 14 counts when cruising at say 60% load and 3000rpm's they can plug 14 into those lower load cells and the car won't fall on its face anymore.

I think this is the best overall solution that would take care of many issues people are having. The phantom knock guys can take care of their low load and low rpm cruising knock that isn't real. Stroker guys/gals can take care of the extra noise that the stroker makes while not reducing the saftey feature of pulling large amounts of timing when knock really gets out of hand.

 

So a 3d table (load/rpm axis's) that has a "ignore knocksum below this value".

So if you said ignore anything below 4KS and you logged 3KS then that would basically mean 0KS, but if you logged 8KS then you would get a 8KS affect...

 

I'm torn between the two ways it would respond to the KS after the 'ignore' value has been exceeded. Either it subtracts the 'ignore' value or it uses the actual KS value once the 'ingore' value has been exceeded.

If I had it set to "4", and I got an actual KS of 10, would I rather have the ECU react to it as a full 10 KS or 6 KS (actual KS minus the ignore value). I think I'd prefer to do it the way you just described Dave.

 

Exactly what i was hoping for......

So really the part throttle areas you could set it to max (36) and it would ignore all knock and at wot you could set it up to whatever knock counts you want to ignore. Above that knock value it is treated the same and you dont have to worry about how it will react to higher counts of knock in important areas.

 

Yeah, I'm not concerned as much in low load areas if I truely have a KS of 6 or something but when I have a KS of 10 at peak load I certainly want the ECU to do its thannng. I like this layout the best because if I want the ECU to pull timing at 7k rpm even with a KS of 3 I can.

 

i think ignore is better than subtractor.

If you are ignoring 4KS and you suddenly get 8KS then there is probably something wrong. You don't want that 8KS to turn into 4KS.

From a safety point of view ignore is better.