If you don't mind my asking, did you ever try logging both yor LM-1 and Tactrix into LogWorks? I guess what I am asking is what particular features of Mitsulogger was the OpenPort plug-in for LogWorks missing?

I can't nec. do anything about it for LW-2, but the plug-ins all get tweaked for LW-3.

-jjf

 

The feedback I get from most people is that the app is just a simple logger that requires very little setup to get up to speed.. I had another few people mention that it has very low overhead on slower laptops. I don't think its a feature issue as both are so similar when it comes to logging data to disk with logworks having the advantage in graphing, and Mitsulogger is intentionally compatible with Data Log Lab as I decided not to re-invent the wheel

 

OOPS! YGPM..

 

Okay guys, I have good/bad news.. The issue some of you guys are experiencing is due to the RPM formula I'm using.. A workaround for the moment until I release a fixed version is to disconnect the RPM signal to the Zeitronix.. I never came across this issue because I had no way to test it. Hopefully jfitzpat gets me the utility he wrote and I can finish this up this weekend.

1.5 beta actually has some new features and several bug fixes (obviously since I released an alpha version for you guys to shake down) One of the new features is a rudimentary dashboard.. It will show RPM, Knock Sum AFR if available, and a few other useful items, the dashboard will also change color if you get knock...

I also set up a default keypress for the enter key, to start and stop the logger, the logger and dashboard also hover in the foreground when its running. I need some input on whether or not this is something you guys want, as this is something I thought was useful on my rig...

 

Oh, and I may change how the logging works now that there is a dashboard, it makes sense that the data stream is always connected and running, so I may change the function of the main button as a connect/disconnect and the logging will be done from the dashboard.. This way I can add threshold logging also if I wanted to later on.

 

Dashboard sounds sweet....Although I doubt I will ever look at it while driving, somehow others have the ability to look at their PCs and do WOT runs ....

With regards to the RPM issue, why would this affect only certain ZT2 users? I am still trying to understand why my Mitsulogger v1.5 is crashing (along with a few others), but nobody else (of the 400 downloads) reports any issues....Thanks MJ

 

I'm guessing its for two reasons.. The first is many aren't using a ZT2, the second is that many more probably don't have the RPM input hooked up as their just concerned with Boost, AFR, and EGT. Thats the ONLY logical answer I can think of. The good news is it should be fairly easy to fix now that I will be able to reproduce the problem.

At least the workaround for the time being is to disconnect the RPM input until I can release a new version.

 

I always wondered about the usefulness of the dashboard too.. Until I started tuning on a Dyno when I needed to see some data and couldn't see it easily.. I never look at anything when I'm logging my own car when road tuning..

 

Hey MJ -- Why / how is the RPM protocol different with v1.5 vs v1.0? The reason I ask is that I have no problems with Mitsulogger v1.0 (and log RPM in v1.0), so I am surprised there is an issue with v1.5. Is it because the HDD is getting RPM data from both the wideband and the ECU (Mistulogger) and having issues syncing?

I have my ZT2 tucked pretty securely, so I don't want to remove the RPM wire. I guess I'll just need to wait for the next release.

Thanks a ton for your help!

 

its not the RPM from the MUT, its the rpm calculation for the ZT2 has a bug in it.. If you don't use the ZT2 dialog, or you don't hook up the RPM signal to the ZT2, then the program works fine.. You don't have to disconnect it, just offering it as a workaround for those who really want to use the program with the wideband logger enabled until I can post a fixed version.

If you look at a log with Mitsulogger and the ZT2 enabled, you'll actually see 2 RPM columns, one is RPM (The MUT Log) the second is tRPM which is the value from the wideband. This was done so it won't conflict with log analysis tools.

Like I said, if you don't use the wideband features (Set the dropdown to none) you won't have a problem at all, but you wont get your wideband data. If you want to log your wideband along with the MUT logs, then you can either wait for a fixed version, or temporarily disconnect the RPM signal to the ZT2.. This was just an oversight because I had no easy way to test this particular input as its not physically installed in a car.

 

Jesus it never Fucking ENDS. I finally get it to extract after I download it and NOW I need a NEW version of .net framework v2.0.50727.

So I amnow download that crap onto my puter.


Also if you have a Wideband, how does it plug into the computer for it to read?

 

It does clearly say in several places that the .NET 2.0 stuff is required, I don't package it with the program because it makes a huge download when there aren't many people who still need to install .NET 2.0

Plugging your wideband in, either the Tuner Pro/UTEC or Zeitronix ZT2, is exactly the same as how you did it for your previous method.

Besides the comment being a little inappropriate, the issues your experiencing and questions your having have been covered several times in this and other threads. In some cases in the download description itself..

 

I got it to work, after some agrivation I got it to work.

 

is there datalogging support for the PLX m-300 using the NTK L1H1 wideband O2S? If so, how would one set this system up to log this O2S? Thanks!


CJ

 

As far as I know, the M series PLX devices only have an analog output.. Not something that can hook up to a computer. You can hook up the PLX to an ECU+ and log AFR along with other engine data (I love the ECU+ by the way)

But the short answer is No, mitsulogger does not work with the PLX M-300 Its actually a physical limitation of your wideband not being able to be hooked up to a PC without external third party devices.