On the note about MM Clients not logging at a high enough rpm.
I'm just reviewing my logs for the 4500 rpm cruise.

I KNOW this morning the RPM gauge was reading 4500 rpm - 5000 rpm ....
And I've got a **** tonne of rpm readings below 4500 rpm ..... I'm guessing its the vehicle rpm gauge and not the AP.
Where I'm going with this is users may well think they are in the + 4500 rpm range but they aren't due to the RPM Gauge accuracy.

Thoughts?

 

^^^ Ok forget that, I was looking at the wrong log file.

Still .... how accurate is the RPM Gauge?

 

The stock tach reads 300 - 500 RPM below reality.

 

That is precisely why the instructions MM gives for datalogging with his tuning service say to look at the RPM on the AP, and not on the cars tachometer. Those were the instructions they might not have been following.

 

They have started to ignore the "instructions instructions" as well...

 

Time for the instructions instructions seminar seminar you were discussing before...

 

^^^^ LOL
I've owned my AP for sooo long I've not gone back to see the instructions or the instruction instructions.
Honestly (really) its almost too dumb'd down. Over simplification in itself can cause complexities ....
but wow what a write up.

 

As per our last web session I've been doing some MAF calibrations.
I've stayed off the juice to avoid messing up my LTFT, however this got me thinking.

1) When I hit the juice, I'm in open loop. This impacts the HEGO readings. However in Open Loop STFT is always 0% (unless you're Cobb then its -0.16 lol). Therefore no amount of juice should impact my LTFT as long as I remain in open loop, yes?

 

Yes

 

Awesome, Thanks Kane

Running out to the garage now to heat my bottle on the BBQ!
w00t

 

OK, yet another outstanding session. Only one more left! I think I'll need another 4 sessions.

I'm pretty much convinced to meet my target date of a complete FI tune by August 25 I'm going to get the tuning service from The Professional (MM, of course) and build from there. Means I need to get the turbo in in probably by mid July or earlier. EEK!

I'm going to try to find some program that can scroll the data logs like a tape. Using a blowed-up chart in OpenOffice.org works but is not convenient. (No better in excel, btw.) Maybe a macro that changes the chart's row ranges on-the-fly. I'll check on MegaSquirt's log viewing tools.

 

I can't believe how much information I've been able to learn from these webinars.
Absolute must for any backyard mechanic wanting to do things on his own.

I've been compiling notes on the training in order to post a full review ....

 

OK, that was easy:
http://www.ideasandsolutions.biz/MegaLogViewer/

Says it can view any CSV file. Too late to try it tonight...

Edit: OK so I lied. It works with AP logs. You have to edit the title of the first column in the CSV to be "Time", then it works. Very cool.

 

^^^^ Nice find...
Thanks for the info!

 

Nice Bill thanks. I cant get the ya ya ya ya aya aya ya ya Boom out of my head wtf lol.

 

Yeah, I think it will be very handy. I think a bit more tweaking to the AP's CSV files will line things up better and maybe even make it possible to use some calculated fields like HP and TQ. It even allows custom calculated fields.

Maybe get a thread started here or on Cobb's forums about using it. I'd like Cobb to be aware what their customers are doing to work-around the lack of a graphical log viewer. They might think it's cool and help us use it better. Saves them the trouble and might help them sell more APs.

 

^+1 to everybody

 

Playing with it now.
I haven't decided if it is worth $25 yet.

 

Paying is optional. It's just nagware.

Since it's not really designed to be used with our logs and has some flaws like tiny "gauges" and weird x-axis behavior (could be PEBKAC), I'm leaning towards living with the nags. If I find I can make some tweaks and really get some good use out of it, I'll certainly pay. If we approach the maker and ask for tweaks to make it more useful for us and they comply, I'll absolutely pay.

 

^ Agreed.

 

Hey Jeff what was the name of the OBDII scanner you were talking about from the guy in AZ?

 

The two names that come to mind are "Autotap" and "Autoenginuity".

 

Irritating that we can't see the LTFT tables directly. Would save a lot of tooling around wasting gas...

Hey Jeff, had a chance to look for that pipe yet? (Impatient, sorry.)

 

More software. This looks interesting: http://www.scantool.net/obdwiz/

It can graph logs. Not sure if it can load other logs and play them back yet.

Might find it's way into my carPC regardless.

 

And so apparently there are ways to read the the LTFT and many other Mazda-specific tables in the ECU, it just takes a different OBD-II interface and about $160 in software...

http://www.palmerperformance.com/sup...a_enhanced.php

Linked from:
http://www.scantool.net/software/sca...cs-add-on.html