I'm having trouble downloading it, any tips?

 

^^Me too. I have it downloaded and I have the winrar to extract it. I can extract it and it works. But as soon as I close it I have to extracted it again and so on. If I try to move the shortcut to the desktop (mitsulogger) I get an error when I try to open it

 

You have to extract it somewhere... Like a directory where you'll remember where it is.

Otherwise every time you open it with winrar, you'll lose the temporary directory it creates.

 

It saves the settings every time their updated.. Of course, the exit button is there for a reason, but the final settings are saved when the form unloads, so it doesnt matter how its closed. I'll take a quick look and see if I forgot to do that with the two injector related fields, as those are the oldest of the parameters.

 

Ok I guess I am a little computer illiterate. Directory meaning like my documents? Or somewhere different?

 

mj doing it as always

 

i just used winrar to extract it to the folder i had the 1.0 version(on my desktop) and ran it like i do the old version. so now i have the option to use either or.

 

Mitsulogger supports AEM wideband?

 

I am interested in the AEM as well. I would think this would be the easiest to incorporate as it just dumps the AFR to the COM port it is plugged into.

Any thoughts on this MJ?

~Zach

 

well, i was unable to get it to work. when i select the zt2 wideband, the new wideband window pops up, and wont allow me to connect. i am sure i selected the right com port and verified the zt2 is working properly through the zeitronix software. i am using a usb to connect the ecu flash cable and a serial port for the zt2.
any suggestions?

 

Just somewhere convenient. A directory is a folder on your computer, its just a method of organizing stuff.

 

After seeing what the logs look like, it should be fairly easy to add support for it, and I'll try to add it into the next release. I can't guarantee it will work until someone gets a chance to test it. But It should be a no-brainer. It looks to be one of the easiest of all the widebands to add support.

 

Are you getting any sort of error? I need more specific information on what is happening.

By not allowing you to connect, do you mean the button is greyed out? Or when you start logging with mitsulogger nothing happens? The application disables that button when its launched through Mitsulogger as mitsulogger handles the connections already, I am probably going to have to hide the button as I have gotten a comment from someone else who had a similar problem, but in their case they were indeed talking about the greyed out button they couldn't press. In reality all of those windows are seperate applications that could run independent of Mitsulogger, even though their consolidated for Mitsulogger (to simplify things for you guys)

If its working properly, when you initially using the mitsulogger connect/Start Logger it will start streaming data.

Early on I had a minor problem with my USB-Serial device, Turns out when I looked up the port in the device manager, there were two of the same com port.. One was for bluetooth, and the other was my USB-Serial device. I disabled the one I didn't need for bluetooth and it started working.

I figure you probably have tried this several times already so normally would suggest trying to reconnect a few times.

This shouldn't make a difference, but make sure the car is already running for a few before you start the logger. Sometimes the ZT2 takes a few seconds to start streaming data (This is rare, and I only see it because I have one on my bench)

Knowing that it works with the zeitronix software means its probably just a port conflict or something simple. .NET's RS232 (Serial) implementation has some glitches that I'm starting to notice, especially when it comes to using com ports that are enumerated, especially if there are duplicate port names as it will use the first one it sees. I'm not exactly sure why its different for other apps.

I'm stuck in a catch22 when trying to implement the serial interfaces, as one method thats built into .NET only enumerates physical hardware serial devices, and the other enumerates ALL of the ports, but duplicates overwrite eachother which makes it a bit difficult to isolate the right one.

 

I stand corrected.. I found a small glitch that I somehow overlooked, when the form is closed its supposed to call the same shut-down routines as when the exit button was clicked. I had commented out this one line at some point in testing and forgot to put it back. I fixed it, but thanks for noticing as I would have missed it otherwise.

In the process, I also noticed that a user could accidentally close the wideband window when its supposed to remain open, so I disabled that, and hid the wideband connect button as its disabled by Mitsulogger, as to not cause confusion. I'm too accustomed to the app that I started realizing that many of the problems reported could be due to those simple UI things.

 

I'm also considering compiling the application to native code, or to embed .NET 2.0 This may increase the size of the application significantly and slow down the app startup. Since I haven't gotten many recent .NET questions I have to assume this is no longer really an issue.

The big problem with creating native code is the potential for it not to work right in 64 bit Windows OS's, where it currently runs fine because .NET is implemented in each of those natively.