Hey guys. Sorry, I don't have much time to scan through everything, but does Mitsulogger log/show boost levels?

:beer;

 

It can only log the sensors that the ECU has access to.. On the USDM car, there is no "Boost sensor" (Map sensor) that can read boost. so the short answer is, no, not with the USDM sensors.

 

I finally got it working today. WOrks great. Now I am learning what all these numbers mean and whats good and whats not so good.

Thanks for a great product Malibu!

 

Thanks MJ.

 

hey MJ how do i get the program to run on my laptop? i have .net 2.0 installed and its just giving me this error:

the application failed to initialize properly (0x00000005). click on OK to terminate the application.

oh and on the boost question, is there no way to measure the boost levels? there isnt some type of conversion you can use or something of that nature?. what about off the boost control sil.

- shane

 

There is no way to log boost with the stock sensors, at least in the way you would want to. Load is really the only important factor when tuning the ECU though..

Have you installed the ECUFlash software yet, and the drivers, and plugged the cable in for the first time? Thats the most common reason for the error (the drivers not installed) Its not supposed to happen, but it does on some machines.

There is a slight possibility you are missing another component required for the app to work, but in general I wrote the app to have no dependencies other than what is already on most machines.

Another possibility is your launching the application from a network drive, although I doubt this applies, it does generate an error due to how .NET restricts launching of remote applications.

 

yeah i got ecuflash installed and all drivers installed properly. i've been using ecuflash for about a month now.

 

Okay then you might be missing a component from windows needed for the app to run.. But the error code you posted is too generic to diagnose from..

You might want to reinstall .NET 2.0 And I have noticed some problems on machines running windows 2000 missing the vbscript components required by the application (vbscript is used for evaluating the requestIDs)

 

jack any plans of adding a Check DTCs present and a Clear DTCs

 

Its not necessary, download the OBD Scantech tool from my site.. It works with the Tactrix cable, the version I posted should be .77 and supports com ports up to COM16 and has a dropdown for the tactrix cable.

 

I only see the .76 version.

 

Okay.. .77 should be posted in a few days after I verify it works with alternate port numbers..

The emulator I'm using for OBD-II isn't cooperating with any of my programs.. So I'm not sure if its the emulator.. Have to test it on an actual car.

 

any possible idea on when it will work with the turboxs tuner?

Thanks.

 

Just downloaded this logger. Can't wait to try it out! Great job, Jack

 

At the moment I have no urgent need to do it.. So I've been coding a bit in my free time as it permits..

Now that I got the OBD-II scantech source code (thanks to Isaac) I'm taking the software in a slightly different direction..

Everything is going to be a plugin, and logging is going to be the only built-in component, and it will be both XML and script based.. This will give a huge amount of flexibility, but requires a huge rewrite of some of the code I've already done.

The reason I did this was to make the plugin architecture more "Equalized" and work consistently, it will also allow me to convert plugins to run as standalone apps outside the framework..

I want to integrate both OBD-II functionality and MUT Logging into the application, but there is some architecture change that is needed to prevent you from accidentally trying to do both at the same time. By making the MUT pluggable, and the device access flexible (not require the Tactrix cable, but any Raw ISO cable) I can add support for native logging of OTHER types of japanese cars. This was specifically to accomodate the subaru diagnostic protocol also.

There's a sane reason for this.. Simply, to start with, data log lab will be officially supporting my logger (along with Evoscan, but I've been primarily contributing data and definition information for Mitsulogger, therefore in the future, it will be easier for me to create proper logs quickly by using this framework. Plus, it makes the tool more flexible for tuners who work on different vehicles. Additionally, I've gotten a few requests to create a simple dashboard for common and important values, this is being implemented as a seperate plugin that is linked to the logger portion, so it needs to operate independantly from the MUT logging component..

Plus I have now started doing R&D on logging/reflashing Ford EEC-V ECU's (building a supercharged Crown Vic as another project) so I will also leverage the framework for that too.