Knock fix with Australian Fuel 98/100 RON

[Turdinator]

I know it is somewhere in this thread but my search fu is weak today. Can some one link me to where air intake temp is related to knock? On the stock tune with the same tank of fuel I saw my aim go from .35 with intake temps of ~110f one day to .85 the next with intake temps ~65f.

[Kodename47]

Originally Posted by Nardi330

quick questions regarding rescaling MAF using the tool developed by Kodename47 (thanks for creating the tool).

this is my first time doing this so sorry with the noob questions.

I have been reading the "usage" tab but i'm not sure how to use the tool.

- what is the "new maximum desired voltage" and "new minimum voltage"? how should i determine what values to use for these?

- "paste original MAF scale into the top table" means putting the value as the "MAF sensor scaling" inside the rom?

thanks in advance.

Are you using my spreadsheet or the one in @vgi's utility? Either way, you want to look at your logs and determine the lowest MAFv which will pretty much be at lowest idle and max MAFv will be at maximum RPM. Always allow for a margin of error at the top end. I think for NA you'll need no more than 4.25-4.35v

[steve99]

Originally Posted by Turdinator

I know it is somewhere in this thread but my search fu is weak today. Can some one link me to where air intake temp is related to knock? On the stock tune with the same tank of fuel I saw my aim go from .35 with intake temps of ~110f one day to .85 the next with intake temps ~65f.

see tune tweaks link below it in there

two table work togeather IAT COMPENSATION and IAT ACTIVATION

[Kodename47]

@steve99 I've had a look through my logs after re-reading the post about PEKC. I can see nothing to suggest that the ECU is retarding a different value to the FBKC values set, which is what the guys on Romraider were seeing. I have a few logs where the FBKC retard value are set to -0.7 and -1.05 and at no point does the retard value change from that.


Maybe setting the FBKC to retard a daft value like -2 degrees and then if it retards less then you know we have the PEKC tables, however I believe that the transient retard tables are there to overcome the issue that was there on the older ECUs.

[steve99]

Originally Posted by Kodename47

@steve99 I've had a look through my logs after re-reading the post about PEKC. I can see nothing to suggest that the ECU is retarding a different value to the FBKC values set, which is what the guys on Romraider were seeing. I have a few logs where the FBKC retard value are set to -0.7 and -1.05 and at no point does the retard value change from that.


Maybe setting the FBKC to retard a daft value like -2 degrees and then if it retards less then you know we have the PEKC tables, however I believe that the transient retard tables are there to overcome the issue that was there on the older ECUs.

you likely correct

what got me curious was a -2 flkc correction in one of my logs. just one -2 only for one tenth of a second fbkc. usually you get a few hits in the log at 10hz refresh and the max i got anywhere else was 0.6 . was probabably a logging glitch.

[efactor84]

I have some weirdness sinced the update to start doing data logging after my MAF Voltage issue was fixed by Shiv. My IAM yesterday was stuck at 1 with no movement; it doesn't matter what RPM or going WOT. This morning it was at .88 for the first time, which is weird. But, it doesn't move at all. Is that normal to see this kind of reading? Also, my Knock Correction is stuck at 0 degrees with no movement. I'm wondering if anyone has this kind of experience logging. Thanks

[zc06_kisstherain]

Originally Posted by efactor84

I have some weirdness sinced the update to start doing data logging after my MAF Voltage issue was fixed by Shiv. My IAM yesterday was stuck at 1 with no movement; it doesn't matter what RPM or going WOT. This morning it was at .88 for the first time, which is weird. But, it doesn't move at all. Is that normal to see this kind of reading? Also, my Knock Correction is stuck at 0 degrees with no movement. I'm wondering if anyone has this kind of experience logging. Thanks

I am noob but IAM at 1 is good.
try different fuel and see it goes back to 1

[efactor84]

Originally Posted by zc06_kisstherain

I am noob but IAM at 1 is good.
try different fuel and see it goes back to 1

I had mine just stuck at 1 yesterday and this morning when I start the car at .88 without moving. This is the first time I've seen my IAM move after numerous cycles. Does it constantly changes or remains steady? The knock correction is always at 0.00 degrees without moving. I'm trying to make sure my tablet is reading correctly without addressing any more issues to Shiv.

[zc06_kisstherain]

Originally Posted by efactor84

I had mine just stuck at 1 yesterday and this morning when I start the car at .88 without moving. Does it constantly changes or remains steady? The knock correction is always at 0.00 degrees without moving. I'm trying to make sure my tablet is reading correctly without addressing more issues to Shiv.

Usually it does not move at all. You are fine. I would try different fuel first.

[efactor84]

Originally Posted by zc06_kisstherain

Usually it does not move at all. You are fine. I would try different fuel first.

I appreciate for ensuring this. That .88 I'm guessing is because I have a low fuel tank. I use Shell 93OCT, which seems to be the optimal choice for reducing cricket noise and the rough idles for our cars. I haven't done much experience with Exxon or Sunoco yet. I'm avoiding BP because I always get the crickets from them and the rough idles.

[zc06_kisstherain]

Originally Posted by efactor84

I appreciate for ensuring this. That .88 I'm guessing is because I have a low fuel tank. I use Shell 93OCT, which seems to be the optimal choice for reducing cricket noise and the rough idles for our cars. I haven't done much experience with Exxon or Sunoco yet. I'm avoiding BP because I always get the crickets from them and the rough idles.

I used to use shell 93 but i switched to sunoco 93

[efactor84]

Originally Posted by zc06_kisstherain

I used to use shell 93 but i switched to sunoco 93

This morning on a cold start it was at .88 degrees. When I started driving, my IAM climb back up to 1, and it never once drop. So since the update from OpenFlash, my tablet is reading correctly with no more issues with CAL ID D00D. Appreciate for helping me out.

[BurnetRhoades]

@steve99, in the section where you mention the need to pull timing if FLKC exceeds -0.7, is that true for both under load and not, whether or not FBKC stays flat? So, for instance, pulling to ~7200 RPM, all is well, throttle is lifted and engine load drops, RPM immediately starts to fall and it's in this immediate area that FLKC pulls down, though without any FBKC pull.

I guess this is the opposite of "tip in" where I've read you say several times a little knock is unavoidable, but "tip out"(?), right after getting off throttle at high RPM, is this also normal or something that might need attention?

[steve99]

Originally Posted by BurnetRhoades

@steve99, in the section where you mention the need to pull timing if FLKC exceeds -0.7, is that true whether for both under load and not, whether or not FBKC stays flat? So, for instance, pulling to ~7200 RPM, all is well, throttle is lifted and engine load drops, RPM immediately starts to fall and it's in this immediate area that FLKC pulls down, though without any FBKC pull.

I guess this is the opposite of "tip in" where I've read you say several times a little knock is unavoidable, but "tip out"(?), right after getting off throttle at high RPM, is this also normal or something that might need attention?

yeah i dont think their is a tip out table , but their is a transient ignition retard table.

if the knock is less than -1 its likely fine, but their is a delay between when knock occurs and when it shows up in logs so sometimes you have to pull a bit of timing in the previous cells. ie tat knock your seeing may have actully occurred under load if its imediatly after throttle lift off.

but that is also what the transient retard tables do, howeverthey may not be defined in defs for your rom not sure