im going to do two things to this rom.. test it out i wont personally touch your knock sensor settings

FAA bit 10 disabled and Im zeroing your IAT trims for now

give me 6 minuts

 

Its very common to raise the knock load threshold. Unless you wanna chase around cruise/tip in knock.

There no dangers to changing it the way I described. Just dont make the load values way too high.

The knock your seeing is probably not true detonation.

 

I whole heartedly agree, raise the threshold for knock detetection to 100 is in a lot of threads by guru's for newbs knock problems. you just gotta dig. The background noise multiplier is even said to be able to be raised 20% with minimal problems, but thats another day and another conversation.

Fireroasted, this rom is exactly what you uploaded EXCEPT iat vs ign trims are zeroed out , and faa 10 is disabled. try that! I would raise the knock detection load to 100 myself, but for political reasons I wont touch your knock control lololol

make a duplicate entry of your timing advance log entry in evoscan, except for request id instead of 06 replace it with a 33

 

OK, you guys rule.

I am going to try them separately to provide some feedback for others to read. First up I am flashing with the knock threshold modified and will do the same pulls and cruise as the above images.

Then, I will repeat with the ROM you edited, to provide timing map vs advance feedback.

 

honestly they all should be combined to get full effect and crispness boosted's knock detection threshold advice + the little things i did will make you a little more sane.

please dont forget there is timing trims that we dont even acknowledge or use and play a very minor role in transient throttle applications so a cell here or there being off can happen.

 

Got it. Finally, I will try both, as they are actually two different topics.

 

OK, I will be honest that I am not sure what differential I saw. So will try and post the results to learn something. Looks like I bumped into something I didn't pick up previously or properly.

The first log is just applying the below values as Boosted suggested.


Could you comment on what that 100 actually means at 2500RPM translated in a sentence. i.e. Don't consider any knock heard until 2500RPM reaches 100 load.

I ask it like that because I still had a couple of 1 counts under 100 load at that RPM, so I figured I didn't get how that table is working.

Secondly, here is a knock trace with the timing table. At about 100 load the knock values kick in. These are maximums, but they are consistent and actually more than the other day/night. If you look at those timing values would you expect to get knock there for 91? Or am I too lean there causing knock?


Third, with the Rats ROM edits and the above Threshold. I get essentially the same knock values, but no 4 or 5, but it looks the same. Here I show the timingadv, but with averages and that follows pretty well. however I checked several logs from earlier today and with averages set they seem to follow more or less.


Part of the challenge is that cruise tuning has lots of data, so it can have lots of exceptions, like a 23 for timing advance in a cell that is set for 13, but its an anomoly.

Rats, what exactly was done and why to the ROM. The periphery bit, what does it actually do, or turn off? Thanks for all the help!

 

Are you logging while decreasing throttle ? Try to isolate a few lines of the log where you go from 50-140 load. I usually pull 3* from my 100 load cell each 10 load for a couple columns.. its possible you're seeing phantom knock and I'm no pro but I think you could see a little better timing curve at transition. You may be a little aggressive there I forget that you're on 91. Usually with no load in the motor it doesn't matter as much

A 3* step per rpm cell is a bit much at low rpm. You could draw that out a little longer and not target quite as high adv in the highest rpm cell



Bit 10 turns off an unknown timing pull below 4000 rpm.

Iat vs timing which I zeroed out stops the ign advance from being trimmed based on iat

The knock threshold will ignore knock below that level.

 

By transition you mean about 100 load, correct. 'transition to boost'? Yup, 91, but the "lets see your fully tuned timing" thread has 91 guys that seem to have way more timing there compared to me, at least now, since I removed a good bunch this last week working on this cruise. OK, I have been assuming that part throttle and low load weren't as dangerous, but still trying to clean it up. I will take one iteration of that map and post in the timing thread finally, for this conversation.

Does everyone just turn that off, or only folks that have the logging issue you did?

For track duty I should probably turn this back on, as its a safety measure. Just turn it off for tuning so its not moving around on me too much, correct?

Can you explain why I would still be getting those counts in those RPMs under 100 load then?

 

I can't explain the knock sum below your threshold .

The iat vs ign trim is handy as a safety margin on track. Do you have that XML?

I think everyone should disable bit 10. It causes unnecessary timing alterations. It should remain disabled as far as I'm concerned.

A good test of your knock sensor would be to use the highest octane fuel you can get. Run your tank down, put 2-3 gallons of 100+ in. Your background noise multiplier may be the next step.

First of all determine if it is phantom. Then adjust the knock sensor settings. It sounds risky because it is. I increased the noise multiplier below 4000 rpm on mine. Jcsbanks suggested a 20% increase was still reasonable when he did his disassembly.

Det cans race fuel and patience

 

Nope. i don't see that in my setting. You have a tephra rom though, will the definitions be the same?

 

I don't run 8859, but yes the def is the same for tephra/stock ..Ill post it here tonight if you'd like

 

Fire, if you're chasing your tail on this, I would suggest making a set of det cans or investing in a set of retail ones. I get a lot of knock issues when I make pulls from 2500, but none from 2750 or 3k. I also have a lot of vibration during decel that happens right after passing 2750, come to find out this weekend it was from tie rod ends that need replaced.

 

Great, Thanks!, I would at least like to see/learn the setting so I can adjust when tuning.

When you say 'pulls from 2750', do you mean you part throttle until 2750 and then WOT and that is from 2750?

I can induce knock by accelerating at part throttle into high RPMs. This is what happens on track to balance the car mid corner on long sweepers. In gear, high RPM, not WOT.

When I do pulls for tuning I am at WOT, but I noticed this last week, at WOT I had lower knock counts than when partial TPS.

Yup, I am definitely in a circle mode. After the 'build' and everything the first logging was for injectors and those logs at cruise didn't knock at all. nothing. Now I have knock on lift off and seemingly at cruise. For months I thought it had to be mechanical something, but haven't found the smoking gun. When I reduced timing the knock counts reduced. Then days later without any changes they seemed to re appear about the same. The more or less 5* reduction at cruise was likely for nothing. ARG.

Det Cans, and then and a few gallons of 100+ will be two next troubleshooting steps on my list. For now I have to make it to Laguna Seca and back, leaving tomorrow.

 

WOT puls from 2750. I do get some partial throttle cel flashes on cornering, but that's due to the tie rod ends. I was doing the same thing you are, I added/subtracted fuel, added/subtracted timing, used higher octane fuels and still had issues. The last time I was on track, prior to tephra mods, I could tell in my afr how bad it would knock on occaision if I wasn't very smooth in my transitions on and off throttle.

Best case for you I guess is that it's drivetrain chatter the sensors is picking up. You have upgraded diffs?