Here are two back to back 3rd gear pulls. I just deleted all the extra stuff, and combined the two. I know that my laptop is a bit outdated and is struggling to handle Mistulogger (see the log entry secs..). Im using Mistulogger 1.5 because it doesnt crash as much as 1.6, due to my CPU being overworked. And I cant log my WB, but Ive added what I observed to the logs, and made it a linear pattern (Im sure its not 100% accurate, but for now its better than nothing). I hope there's enough info in it to get this thing straightened out.

My AEM WB shows 10.0 ALOT. Im sure it is probably richer than that. My goal is to be at 11.7 afr at spoolup, tapering to 11.0 at redline. Im running 20-21 psi, tapering to about 19 at redline. And Im on 91 oct. The current tune is an email flash that a got several months ago.

Anyhow, here is the log file. Any input is greatly appreciated.

CB

 

You would seem to be getting very high 2 byte load for 21psi boost are you sure the 2 byte mod has been done correctly, as your load column and timing are more in line with that boost. Is the K&N in your sig a panel or cone filter?

Personally, I'd look at why the 2 byteload v boost is like it is. Back the timing off until its knock free, get the AFRs where you want them, keeping an eye on knock then try advancing the timing whilst looking at knock and making sure AFRs don't move outside your target as you adjust timing.

MB

 

I will be vedry difficult to tune on such a low Refresh rate.

 

Thanks for the quick responses.

The K&N is a cone. I'll go back and check to make sure the 2 byte load mod was done right. Im assuming the 2 byte load should be closer to the "load", corrrect?

I know I need a better laptop. A couple months ago, logging more than I am here, it was at least twice as much data. Im not sure what happened. Maybe time for a format, or just pony up and buy a new one.

 

Reduce the number of items you log. Really only Knock, timing, RPM and TPS for a very basic out line.

You may want to consider going back to the stock intake untill you get a handle on the tune, though your fuel trims look OK, it might make the process a bit easier.

MB

 

I would love to. But the thing is, this is all Ive got. I bought the car with a few mods on it. It had a custom tune on it, but without knowing, I purchased an email tune to replace it, just to be on the safe side. The old one's fuel map is way different than the new, but timing is pretty much the same. Im thinking I might toss the old one back in it, just to see where I stand with it.

 

Wouldnt hurt too at all ^

 

I finally got some decent refresh rates with V1.6 last night in the garage with only Knock, RPM, 2 byte load, timing, and tps being logged. There was about .2-.3 sec in between log entries. I will add regular load to that list and see how the two compare. Once I start loggin the WB, I get about the same refresh rate as the first logs, above. But Im thinking I may do two logs, one with lots of data, and another with WB added just for some reference. Ran out of time last night, but will try to get back on it tonight.

Thanks guys.
CB

 

So here are two logs pasted beside each other. The one on the left obviously wasnt logging AFR. So I interpolated the afr from the log on the right. Im curious as to what is going on with the 160 load blip around 6700rpm...

 

I went back and checked the XML additions for Mistulogger, they look good. And the MUT table has been modified correctly. Would being at high elevation affect this at all? Im at roughly 6000' above sea level.

 

So Ive playing a little bit more. I disabled lean spool; and got my AFRs to around 11.4 or so at spool up, tapering to 10.9 at redline. And got my knock sum down to 3, for now. I had to pull a TON of timing. About what do you guys normally see for timing numbers at spool up to redline?

I obtained EvoScan last night, and did some idle logs in the driveway this morning. Im getting about .12 sec in between log entries, while logging my WB. Im pretty stoked. This afternoon I should have some time to tweak it some more.

Im still a little concerned that the 2 byte load I was seeing ML is not correct. Some of the load cells just werent making sense yesterday. The timing numbers shown in the log were not the same (WAAAY off) as my map. Im hoping that EvoScan will be a bit more accurate. I assume that if I log calculated load, that should be a good comparison of the two.

Im really interested in doing some comparison pulls, using the power/torque graphs. Any quick links you guys might have for setting everything up?