Also, I am assuming this can be used much similar to the Evoscan but, works through ECUflash cables? When will it be able to log widebands and MAP sensors for boost. Presumably it is only a matter of time.

 

Correct, over time it will be possible to log with almost anything.. Those are planned features in v2 which is very modular, coincidentally I do plan on adding ECU+ logging in the near future.

Mitsulogger (and Evoscan) are limited by the data available from the ECU, therefore at the moment, the stock ECU's data is clipped and therefore not entirely accurate under the levels of load a typical Tuned evo might see. The ECU+ is vastly superior for logging that data. I use both, and the fact that the ECU+ interfaced easily with my wideband means that the data is available within ECU+ along with unclipped data.

If the ECU+ had live MUT-II logging in its logs for trims, Knock Sum, and calculating load from RPM an MAF Frequency using its unclipped data, I would be using that as my sole logger. But for the time being, I use both my tool and ECU+

In fact, the main reason that Mitsulogger (and Log Analyzer for Evoscan) converted/logged data in seconds from start, was to keep the data roughly correlated to ECU+ logs. I frequently line up the time stamps in both (using Data log lab and the ECU+ software) and compare the data using MAF frequency, boost, AFR, timing in ECU+ and Knock Sum, Fuel trims, etc.. in Mitsulogger


The good news is that I wrote Mitsulogger to be very flexible, from its calculations, to what it can log, to the types of components it can log (in v2)

In fact, MitsuLogger v2 that will come around at some point in the future, has the MUT reader, seperated from the logger, gui, and editing functions, simply because I am interested in creating a flexible tool capable of using all sorts of different devices to consolidate data consistently into one place. Additionally if you like video, one of the planned modules is a video capture with some log data overlayed, and embedded timestam synchronized with the logging, and another module for GPS location, these are obviously for logging in race conditions where you need this sort of data in an on-board computer (I have other things in the works too)

But this thread is about v1, and its specifically a MUT protocol logger, capable of reading any request from the ECU, and manipulating it however required to get data you can use.

The v1 code is actually very different than v2 at this point, and although up until this week, the code between the two could be moved back and forth as bug fixes are found, as of this week, the mut portion operates seperately from the logger and is mostly new code.

 

I am considering switching from the ECU+ to the ECUflash as I like the idea of actually being able to change parameters in the OEM ECU rather througha piggyback system. I was concerned with the datalogging capabilities of either the EvoScan or your baby, the Mitsulogger.

It sounds like both are inferior to the ECU+ logging capabilities so I am not quite sure what to do at this point. I really like the fact though that the ECUflash allows parameter changes directly in the ECU so, I think I am going to take the plunge and switch, although I may just keep the ECU+ for now for logging capabilities only until the Mistulogger can capture as well as or better than the ECU+.

I see you are running the ECU+ as well on top of the ECUflash and do this for logging purposes mainly. I assume than that you simply leave the fuel and timing maps at zero across the board and make the changes through the ECUflash?

Will it come a time when the Mitsulogger is just as good as the ECU+ logging capabilities? I assume it will but, just takes sometime.

The Mitsulogger works through the ECUflash cable, correct. I would just simply open the Mitsulogger software and it will run that way, correct?

 

This is a little off topic but, to get started I need to buy the ECUflash cable, download the software. Then download the ROM and I can get started, right? Is there a necessity to mess with the Immobilizer code or is it simply a good idea to just right it done just in case something goes screwy?

Also, are the values in that are entered in the ECU+ software able to be transfered over to the ECUflash? Or does the ECUflash make charges, such as fuel in an air to fuel ratio rather minus or plus fuel? Does the same go for timing?

Thanks for the info I just want to do some research before taking the plunge

 

Unless the ECU can log more accurately (which it cannot without modifying its rom) any MUT logger, mine or any other, will never be able to log as well as the ECU+

I feel that the ECU+ is a HUGE advantage to have on the car along with being able to reflash the ECU, I can tune the car really well using Mitsulogger and ECU+ Logging, I can get the tune worked out in the Stock ECU, along with the drivability that you can never get without reflashing, and there's a level of fine-tuning you can get with the ECU+ that you just can't do with a reflash.

They really compliment eachother really well, I wouldn't remove it from your car to replace it with reflashing, I would tune with the tools, reflash the ECU, and fine-tune with the ECU+

 

BTW There is some rumor that the ECU+ will be able to log with the MUT protocol also, and won't require the Tactrix cable for logging.

 

So, keep the ECU+ for logging capabilities and use the ECUflash to tune the car? I am assuming that the parameter changes would be done within the ECUflash and that the ECU+'s parameters should be kept at zero then?

What would be the advantage of using the MUT interface vs. what the ECU+ already logs?

 

Thats what I'm saying.. Use the ECU+ to fine tune troublesome issues such as needing tweaks to timing, or adjusting the airflow curve to closer match your fuel maps.

But yes, use the ECU+ for logging, and other things, such as, Big cams sometimes have trouble with the stock MAF at idle, you can fix that very easily in the ECU+ by clamping the idle MAF frequency at 35hz or whatever you need..

The ECU+ logging and MUT logging are complimentary.. The ECU+ can log parameters you cannot get out of the MUT protocol, for instance an unclipped MAF frequency, and Accurate speed and rpm readings.. the MUT protocol has data not available in the ECU+ (Currently) which is the O2 feedback value (short term fuel trim), and the Long Term fuel trims (Low Mid High), Octane number (Knock trim), and Knock Sum (immediate knock count) among a few other useful parameters.

 

MJ,

This guy posted a log that has -14 timing in the upper rpm. I thought that you would like to se it.

https://www.evolutionm.net/forums/sh...d.php?t=231124

 

Yeah, most people will get that error on occasionally until they download the new file that will fix it, I will post tonight..

 

MJ, Sorry for the Jeopardy like questions I just really fascinated with the ECUflash because of having such a low cost it has unreal potential.

I have been looking for something like this and just recently was talking to a customer of mine after doing an install who had the ECUflash and EvoScan. I wasn't that impressed with the EvoScan but, the ECUflash I was.

I also have a Pocketlogger, which is also very useful for logging but nothing like the ECU+. I would like to get rid of the ECU+ being that I am restricted on what power adders I can run in STU so I am pretty much at my limit. The 2 main areas I would concentrate on is fuel/timing maps and boost and rev limit.

I will never run cams, bigger turbo or anything like that, at least not in the forseeable future.

I guess I should just take the plunge and buy the ECUflash cable, download the software and await V2 of the Mistulogger. I am sure it will log what I am after especially once you add the wideband functionality.

Will the wideband logging be included in V2?

Thanks for your help and keep your comments coming

 

Mitsulogger v1 (Release A) posted on aktivematrix, it replaces the old v1.0 download..

PLEASE DOWNLOAD THE NEW VERSION, it eliminates the data glitch that people are seeing as -14 degrees in their timing column.

Also, if someone wants to spend some time with the load calculation, I've discovered its off by about 20% or so.. (115% calculated is actually 140 or so..)

The way to fix it is to look at ECULoad and Load, ECULoad clips over 160 but you can see that under load it is off by about 20% when it ramps (not at idle or cruise, it will be off because of closed loop)

 

MJ, I tried launching he V1A logger software but my laptop needed to locate a program to run the software since it is a .rar file. I am not very computer literate when it comes to that type of stuff.

My laptop is running XP home edition with Office '03. That being said what do I need to do to run this?

 

you need to download winrar, its a compressed file like a zip.. I think you can download it from www.rarlabs.com put all the files in a single directory (or right-click on the file and extract to a directory after you install winrar)

 

Thanks, I'll give this a shot.