I sent a AEM wideband output hyperterm txt file sent to your email address for possible future implementation.

 

Yep, I got the mail, I'm hoping to put something together for it to get into the next release. Since I have no way of testing it, I'll have to wing it for the AEM.

 

What do I need to download to extract it?

 

Is there any keystroke that can start and stop logging, or do I have to always click the button?

2 things that would make logging while driving much easier -

Some big box like EvoScan that shows green when logging
Making it so that you can hit a key like spacebar to start and stop.


THANKS

 

I haven't added a start/stop shortcut, It never occurred to me simply because I start the logger then let it run for long periods of time, the way the data is collected I can easily match it and correlate it.

Same with an indicator if its running or not.. I'll make sure I put something into the 1.6 release, though 1.6 will have a dashboard so you'll clearly know its running. It will hopefully be configurable to show whatever parameters your logging.. I want to do a minor rewrite so the logger is always connected and running, and the dashboard is where you start and stop the logger, but this is taking a bit more work as I had inadvertantly created some dependencies on the file writes in my earlier code.

My original code was written with a small display and touch screen in mind, so I was using the button (touching it with my finger)

 

FWIW you shouldn't really be starting and stopping the logging while driving.. Maybe its better the way it is, as it requires someone to stop and look at what their doing. Like I said in my previous post, I start it, then let it run for my entire drive, including pulls and stop and go driving..

capturing all of this data is critical to a good tune as drivability is just as important as power.. It forces me to collect all of the data and I can look at it later and review my entire experience.

Then again, I use Data Log Lab pretty heavily as its graphical representation of the data makes it very easy to pick out pulls from stop and go driving. I can see it being a nightmare with Excel, but Excel is probably the worst tool to use for analyzing this type of data unless you've create worksheets that automatically ingest the data and create useful views.

 

I also use DLL but its a little annoying to have such big files. Sometimes it is nice to just have different runs in different files.

I will test the program with my ZT2 and MAP sensor when I get a chance and I'll let you know if I encounter the same kind of problems that others have with the ZT2.

 

I cannot get v1.5 to work with my Zeitronix .....The minute I start logging the program crashes and just shuts down. I have to re-launch the application only to have the issue re-occur.

FWIW -- I am able to run Evoscan .97 and log my AFRs, so I doubt I have a port or data conflict issue.

Mellon -- You stated that you are getting v1.5 to work with your ZT2, would you please expand on your PC setup, as well as your process to log?

MJ -- I just saw the post on Aktivematrix and will try not closing the window and see if that solves the problem. Thanks

 

So far, there have only been 3 or 4 users out of 200 downloads who have reported a problem like what your describing. I really don't know what to do to help you or to fix it since I cannot reproduce it on anything I own. I really can't say if its a widespread problem as the only reports of problems have been the few of you.

There has to be a common thread, but so far I cannot see any other than (I think) you guys are using a physical hardware port, and a few other things..

The problem is you need to try the program on a different machine altogether, then if the problem persists need to let me know what they have in common (applications installed, etc..)

 

I don't have a wb02 setup with mine yet. I have a LM-1

 

MJ -- I know there are a ton of downloads, but is there anyone that confirm it is working with the ZT2 to log AFR and boost? I thought Mellon had it working but he just confirmed that it is with the LM1. Thanks

 

I have been testing it on a ZT2 for weeks, thats why I find the problems you are having odd, if there was a bigger problem with the wideband (both the TurboXS and Zt2 share almost identical code) then I'm certain it would be more than 4 people.. At least I hope so..

Since I've been using it with both the UTEC/Tuner and the ZT2, and its never died on several laptops I'm running, I just can't reproduce the error.

And the ZT2 logger actually passes *ALL* of the data from the ZT2 to Mitsulogger, so if you have the EGT, Boost, RPM, USER, etc.. all hooked up, you will see them all. (even if you don't hook them up, their logged, but you just don't add them to the mitsulogger.txt definition for data log lab)

If your not seeing it in DLL, it just means the definition doesn't have the required entry for it to be viewed..

 

See, thats the problem with software development.. The only feedback you get from anyone is with people who either want you to change something, or who have a problem.. so its hard to get any metrics as what is working perfectly as the people without any problems, you generally never hear from until they get itchy for a new feature or version.

 

I thought it wasnt compatiblwith the LM-1?

 

It doesnt currently support the LM-1 or LC-1.. He replied to an earlier post where he was under the impression he had a ZT2 and his reply later was that he was running mitsulogger with the LM-1 logging software side by side.