Dreaded knock.... cant seem to get my tune right

[WeathermanShawn]

O.K..now I get it!

Man, you guys are smart..Now what up with his tune?.

Thanks (I mean it..not being sarcastic..)..

[Chevy366]

Ha , already on another OS Android (phone) , so cant view his tune and log .
Will leave that to you , "grasshopper" . ;-)
Just so I dont get in trouble, grasshopper was what was used by a priest to describe a young student in Kung Fu TV series. :-)

[WeathermanShawn]

Dopey:

So far, the main issue I see is that you are running Open-Loop..but you have not defaulted the MAF C2901-C2904..Since you have B0120 set to 4000 RPM, you are running Open-loop, but you are not running OLMAF or SD. Basically, it is impossible to do.

This is verified by the fact that you are still running off the High-Octane Spark Table.

You either need to default the MAF (SD-Tune), or set B0120 to 400 RPM (OLMAF), or set B4205 to stock Temp Values (Closed-Loop). I would imagine that your airflow values are jumping all over the place, and hence your Spark values are just as erratic. If you get the Tune parameters set correctly, you will find your fuel and spark values will fall in line.

Thats my take. Good luck..

Edit: Dopey..maybe its the new forum look or I just need clarification. Is this a Custom OS? That may require some further investigating (on my part) concerning closed-vs open-loop parameters. I.E., my answer is premised on a non-custom OS tune..If it is custom..then it I would have to rethink my review..

Thanks..

[WeathermanShawn]

Ha , already on another OS Android (phone) , so cant view his tune and log .
Will leave that to you , "grasshopper" . ;-)
Just so I dont get in trouble, grasshopper was what was used by a priest to describe a young student in Kung Fu TV series. :-)

Yea, I got you. I am old enough to remember the T.V. series..

[voda1]

Dopey:

This is verified by the fact that you are still running off the High-Octane Spark Table.

Thanks..[/I][/COLOR]

What info tells you that?

[WeathermanShawn]

Attachment 8136Attachment 8137Attachment 8138

Attachment 8141Attachment 8140Attachment 8139

I linked his DYNCYLAIR PID to both the High & Low Octane Chart.

His log shows he is running off his High-Octane Spark..I just do not know what type of Tune he is running. A Custom OP will let you do what he is trying to do..

Does not explain the KR. Could be airflow..fuel..and even summer IAT's. It it kinda all over the place.

Anybody else see anything?

[voda1]

I linked his DYNCYLAIR PID to both the High & Low Octane Chart.

How do you link them?

[WeathermanShawn]

In the EFILive Tune Tool, I check the following (see attachment)..

There are a few other rules..I think you want your Pids and Tune Units to be the same..I.E. Metric etc..There have been a few recent posts (Tips and tricks)..but that is how I do it.

In this case, DYNCYLAIR (g/s)..is how I tracked it..

[joecar]

I've been busy, but I'll catch up on this thread later tonite.

[Dopey]

wow! I definately did not expect this many replies so soon, haha.

Sorry, I posted it up late last night and forgot to include the OS its COS3 01290003 I believe (hence I didnt think any of those MAF paramaters were applicable). But it would be music to my ears if it was something so simple

I am wanting to run OLSD and ditch the 02's (and keep the wideband in permanently). One thing I noticed, is I had set B3601 to 14.7 after reading about the AutoVE being skewed by the W02 having a different lambada value vs the tune, however I just re-opened it and it has gone back to 14.68 Im guessing this is the bit depth used to store this variable? I have checked that there are no instances that the commanded is Lambada in b3647 so it should not enter semi-OLSD.

I have re-attached the .ctd as a .tun file just in case any one else is having issues (I have changed the default program for .ctd to the Tune tool, let me know if anyone wants screen caps on how to do this in Win7).

*Edit*
A bit more info, I also thought it was not using the low spark tables, but I dont know why? Ambient temps were around ~16*C (60*F for some) during the log last night.
Also, I have disabled BKR by zeroing out B6212 so I dont think it has anything to do with that either... I have gone back to the base tune so many times, I may have left something out... Although I did get the tune done by a respected tuner here who has got nothing but rave reviews from others, so theoretically it should have the correct settings in the base tune.