Seeing 2-3 degrees difference in timing mp vs log.
Oct 16, 2012, 12:37 PM
#46
On 05-06s, you can do it two ways. You can use Evoscan. Or when you switch map using the TPS method, the CEL flashes fast when on alt maps, slow when on reg maps.
Yes, which he noticed after logging 2byte load.
Oct 30, 2012, 03:32 PM
#52
I am having a similar issue I believe. I am backing into it, because I am still showing occasional 3-4 even 7 counts of knock during cruise. I worked down the timing to show only 1-2 the other night, and then today its essentially back to 3-4 occ 7. I have what is likely considered timing going too low between 50-100 load now.
When I tried to reconcile the timing map and my timing, even with 1-2 counts I was off as rats mentioned, and like 10isace.
I guess the logic is that some of us 'may' be using incorrect loads when logging and therefore changing the wrong cells, like 10isace mentioned.
So, what is the appropriate Load to log for non tephra evo 9? I see 3 load records in my evoscan, and I don't think I have modified them in anyway. I use 2 byte.
Here is my evoscan load related items. I thought the default caption of this load being 'degraded' was interesting. Does that mean anything relevant?
Here is a sample trace from my lunch run. The popup data was intersting, and part of this I suspect. It states 15 degrees timing in the trace, but interpolated 11.9, which matches my map.
Here is the knock max values. These are much higher today than just last night, as I was tuning with 1s and 2s, no more.
When I tried to reconcile the timing map and my timing, even with 1-2 counts I was off as rats mentioned, and like 10isace.
I guess the logic is that some of us 'may' be using incorrect loads when logging and therefore changing the wrong cells, like 10isace mentioned.
So, what is the appropriate Load to log for non tephra evo 9? I see 3 load records in my evoscan, and I don't think I have modified them in anyway. I use 2 byte.
Here is my evoscan load related items. I thought the default caption of this load being 'degraded' was interesting. Does that mean anything relevant?
Here is a sample trace from my lunch run. The popup data was intersting, and part of this I suspect. It states 15 degrees timing in the trace, but interpolated 11.9, which matches my map.
Here is the knock max values. These are much higher today than just last night, as I was tuning with 1s and 2s, no more.
Oct 30, 2012, 04:12 PM
#54
Sorry, I didn't get it then. I think you noted to raise the threshold of the knock sensor to just ignore the knock going on. Here its happening beyond that 100 load value.
"
The weird timing thing that Rats disabled and fixed his issue is available on all IX ROMs.
You should raise your knock load table up to 100+, to alleviate your cruise knock issue.
"
Can you give me an example of what I should have changed to try your solution?
Here are the tables I have.
"
The weird timing thing that Rats disabled and fixed his issue is available on all IX ROMs.
You should raise your knock load table up to 100+, to alleviate your cruise knock issue.
"
Can you give me an example of what I should have changed to try your solution?
Here are the tables I have.
Oct 30, 2012, 04:21 PM
#55
Fireroasted, look in peripherery bits FAA, make bit 10 = 0. Haveyou done that?
bit 10 effects under 4000 rpm. thats where I see your knock
are you logging mut33 for timing map? same formula as timing adv
I try to log only the increasing load or throtte situations and steady state. There is a plethora of timing modifiers that we dont tune, such as trailing throttle timing etc.
bit 10 effects under 4000 rpm. thats where I see your knock
are you logging mut33 for timing map? same formula as timing adv
I try to log only the increasing load or throtte situations and steady state. There is a plethora of timing modifiers that we dont tune, such as trailing throttle timing etc.
Last edited by 211Ratsbud; Oct 30, 2012 at 04:26 PM.
Oct 30, 2012, 04:53 PM
#57
Sorry, I didn't get it then. I think you noted to raise the threshold of the knock sensor to just ignore the knock going on. Here its happening beyond that 100 load value.
"
The weird timing thing that Rats disabled and fixed his issue is available on all IX ROMs.
You should raise your knock load table up to 100+, to alleviate your cruise knock issue.
"
Can you give me an example of what I should have changed to try your solution?
Here are the tables I have.
"
The weird timing thing that Rats disabled and fixed his issue is available on all IX ROMs.
You should raise your knock load table up to 100+, to alleviate your cruise knock issue.
"
Can you give me an example of what I should have changed to try your solution?
Here are the tables I have.
The Knock Sensitivity Load Threshold table. Make the 2500,3K and 3500 cells 100 load, then taper to it to 80 at 5000
Oct 30, 2012, 04:56 PM
#58
Fireroasted, look in peripherery bits FAA, make bit 10 = 0. Haveyou done that?
bit 10 effects under 4000 rpm. thats where I see your knock
are you logging mut33 for timing map? same formula as timing adv
I try to log only the increasing load or throtte situations and steady state. There is a plethora of timing modifiers that we dont tune, such as trailing throttle timing etc.
bit 10 effects under 4000 rpm. thats where I see your knock
are you logging mut33 for timing map? same formula as timing adv
I try to log only the increasing load or throtte situations and steady state. There is a plethora of timing modifiers that we dont tune, such as trailing throttle timing etc.
On the MUT33. Sorry, I don't know. That MUT stuff is an area I don't yet completely understand unless very simple and clear directions are given in a post I just follow. Here is the evoscan item on that value from my screenshots.
Last edited by fireroasted; Oct 30, 2012 at 05:00 PM.
Oct 30, 2012, 05:08 PM
#60
Sorry, cross posting a bit, as your answering while i was typing my response to rats. I completely understand with your above example. Thanks 
I will also try that tonight. Is that common, and is there danger in turning down the 'listening' of the knock sensor?
Or said differently is there rationale that supports the knock we are seeing in my logs isn't actually knock, but just engine noise repeating at certain loads while cruising without any measurable changes in throttle or load.
I have adjusted timing down by nearly 5 degrees in that cruise area and at first it seemed to indicate that was working as all my logs were reducing the counts. Then it just seemed to come back. Is that the definition of not really knock?
I guess I am just nervous about telling the knock sensor different math to listen for and damaging something, because its knocking, but the ECU is not correcting because it doesn't believe its knock based on the formula I changed.
I will also try that tonight. Is that common, and is there danger in turning down the 'listening' of the knock sensor?
Or said differently is there rationale that supports the knock we are seeing in my logs isn't actually knock, but just engine noise repeating at certain loads while cruising without any measurable changes in throttle or load.
I have adjusted timing down by nearly 5 degrees in that cruise area and at first it seemed to indicate that was working as all my logs were reducing the counts. Then it just seemed to come back. Is that the definition of not really knock?
I guess I am just nervous about telling the knock sensor different math to listen for and damaging something, because its knocking, but the ECU is not correcting because it doesn't believe its knock based on the formula I changed.