No, this is not unilogger, this is just a fixed up version of Mitsulogger with some minor bug fixes and enhancements.

This version is compatible with 64 bit versions of XP, Vista, and has been tested and works with Windows 7, both 32 bit and 64 bit.

As usual, this is a zip file, extract it to a convenient location and run the mitsulogger.exe program

This version of mitsulogger is still only compatible with FTDI based cables, That means FTDI Serial adapters, with home built cables, VAG-COM KKL Cables, and my favorite Tactrix Openport 1.3 cables.

I do not intend to include Openport 2.0 support in this application in its current state. I honestly don't have the resources to develop and test it (Access to CAN Bus Mitsubishi ECU's and the time to build bench harnesses) There is also no reference code available at the moment to help me quickly enable support, I just don't have the time to spend "Figuring it out"

What has changed:

- No longer utilizes VBScript or its deprecated OCX file to evaluate formulas. It uses a free evaluation library source that I found. It works, and does the job.

- Unfortunately Innovate Wideband support has been removed. This is due to an incompatibility with 64 bit OS's and the Innovate SDK (which hasn't been updated in almost 5 years) Please send your e-mail to them about it, not much I can do but develop my own MTS libraries (which had always been the intention, but never materialized)

- Many minor performance and other bug fixes have been addressed. I know I've missed a few, but I've been out of the loop for awhile.

- International users have requested several times to have a configurable log delimiter as their regionalisation settings use a comma as a decimal identifier. You can now use any printable character (or if your creative, a tab or other keyboard extended character)


Please be aware that this version has not been heavily tested as I do not currently have the ability to do much testing.

A little background on my decision to release this version.

First, 64 bit Os's are becoming very common, and several components utilised by mitsulogger are no longer supported, or do not work properly with Vista, Windows 7, etc. Most of the issues are specifically related to UAC or just 64 bit compatibility.

The newest versions of my software that has been in development are no longer using .NET, they are all Native Code, and operate pretty standalone (Delphi based) with very few dependencies, they are also cross platform compatible due to the development environment I'm using.

I hate having to consider code obfuscation or some sort of protection just to release a product that is immediately reverse engineered. I have gone out of my way to use code sources that are widely available and give credit where its due in the source code. I will make this source code available if there is enough interest.

I want to thank everyone for their support over the years, and apologize for taking this long just to get something out there. Life has a funny way of changing your priorities, and my current career, family, and other things just doesn't afford me the time I once had to contribute at the level I had been.

Yes, I still have my Evo (It hasn't been drivable in 2 years, first was some ignition/EFI issue I had tracked down, and the car had been seriously abused when it was shipped from NY to Texas, resulting in needing a transmission rebuild and new clutch, I cannot afford to have it fixed, and even after all I've contributed, I still cannot get a shop to help me out and get the car back together in a way I can afford)

Not many of you guys know, but there have been a few things going on in my life that have prevented me from being really active, having very young kids and relocating to Texas has been a big reason. But in 2007 I was also involved in a Motorcycle accident which prevented me from being able to work on my own car, now that I'm "healed" I no longer have the facilities to do it, plus ongoing issues from my accident and other medical problems that have cropped up over the years have made my car hobby a very low priority (Plus in general too difficult or uncomfortable to do the work myself)

This is no excuse for leaving you guys hanging for as long as I have. So consider this a quick gift and a hearty "Thank you".

I'll be back!

(The File is attached to this post! You must be logged in to see it)

File replaced with BUGFIX 2 release

I need feedback from users who have been using the software, if its running okay or not. I had not had the opportunity to test this version as well as I might have in the past. But it has worked fine on everything I've tried here in the "Lab"

uploaded a "Bugfix" version that I think should fix an issue where there is a blank/Null value returned from the ECU (Due to suspended logging or a timeout) and would crash the application.
This may not fix the problem of slow logging or other logging issues due to hardware shock protection however it should handle it more gracefully.

Thanks to the folks who were able to point me in the right direction.

I'm not sure "why" they were getting the error, but now it will handle the error better. I suspect there is some lag in the driver, serial port, or something causing there to be no buffered data. I had not been able to reproduce the error though.

Bugfix 2 posted

This addresses ONLY errors thrown when improper or null data is returned from the openport cable.

It catches the error, but also handles hex conversion a little better so its unlikely to happen in the first place.

A big thanks, I'll test this over the next few weeks as I'm due to get my time sharing the car with the ex-wife! Cheers Jack, wish I could help you get back in your Evo in some way.

MB

Thanks for the kind words.. I'm glad someone posted in this thread simply because I haven't gotten ANY feedback on the new version (or posts in this thread) I thought there was actually something preventing people from posting.

I really always liked how well Mitsulogger (ALWAYS) worked compared to everything else available.

Unfortunately the lack of innovate support screws me. I know a lot of people have moved away from their stuff in recent history for many reasons, but I still have an Innovate LC-1 / XD-1 in the evo and subsequently need to log it.

I'm sure this will still be useful though for many things. (So thank you)


If there is anything I can do to help with the car situation... let me know. I'll do what I can.

Well, the car situation isn't really something anyone can help with, I either have to fix it properly, or sell it to someone who wants to fix it, and not lose too much on the deal.

Anyway, Its unfortunate that I had to remove Innovate logging. The truth is the developer API component they distribute has not been updated, its a VB6 OCX file which doesn't work in 64 bit vista, and its "Iffy" on 32 bit vista installs (as is any VB6 based component)

The path of least resistence in creating a fairly rapid release was to take my existing code and "fix the glitches" but the Innovate logger would require a complete rewrite, with very little programming info (what they supply on the protocol info is good, but I would have preferred them to supply a VB.NET module to their MTS.DLL) Until they have something I can use, there's little I can do. Well, I could write the library myself, but as my car is out of commission, and I don't have an Innovate product in my car, there's not much motivation to attempt that.

I'm getting through these things a little bit at a time. so it may happen at some point. But not until I get a chance to talk with them and get something worth working with from them.

malibujack,

I have been using this with a Zeitronix ZT2 and so far have not had any problems...

I am a complete newb, so I have a few newb questions.

Is there a way to log Tephra v5.10 1byte Load? I have been trolling the boards with very little luck.

Second, what is the best way to utilize the data once logged? IE, is there a good graphing program? I can't get your logs to work within EvoScan and EvoScan goes goofy when I try to log with the wideband attached.

Thanks in advance.

Dan

You just need the requestID and scaling formula and add it to the requestid.xml file.

I use data log lab www.dataloglab.com to work with the files, it takes a little work to get the data imported but once you get a template that works (I include one that should work with the common requestid's that was contributed by a user for an earlier version of mitsulogger)

Logs generally aren't compatible with Evoscan, early on, I had attempted to create files that were interchangeable and compatible with both apps, unfortunately they have since diverged and the files have changed.

Zeitronix logging has always worked, once you start logging boost levels over 26psi is when there may be some issues (as reported by other users) this is a known bug, but of course, wasn't discovered until people routinely ran boost levels that high.

I downloaded and installed the file and can't open it on my 64 bit vista laptop. It allows me use the AEM logger for my AFR's but cannot use mitsulogger itself. Any help on this?

the only times mitsulogger might fail are a missing component (.NET 2.0 or greater) or a missing openport driver.

Since your running Vista x64 its unlikely a .NET issue, so I'd probably guess its a driver issue.

What version openport cable are you using? Mitsulogger is not currently compatible with the openport 2.0 cable. It does work with FTDI based openport cables, Vag-Com KKL cables, and serial cables with FTDI controller chips.


There is currently no version of mitsulogger that works with the openport 2.0 cable. You also don't mention what year Evo you have, but its not really relevent.

OH! Another possibility is the decimal placeholder should be the period, not the comma. When I wrote the software I never took internationalization into account. I've attempted to modify the software to accomodate it, but have not been able to test it.

i'm not too sure off the top of my head right now what version cable i'm running but it is not the 2.0. I'm currently running 64 bit vista and the program had trouble loading. I installed the same version on my gf's computer and it loaded no problem, I attempted to log my idle which is did, but once I attempted to log with the wideband it would attempt to log and after about 3 seconds would say "mitsulogger had encountered a problem" not sure what issue i'm having exactly right now. Any feedback would be greatly appreciated.

I have an 06 evo IX

make sure the proper port is set for the AEM logger.. If it works standalone, it should work fine from within the app (make sure the right com port is set when its launched from Mitsulogger, its entirely possible its not saving the setting from running it standalone.)