TurboXS Love.. Mitsulogger 1.5

[MalibuJack]

See the Mitsulogger thread in the ECUFlash forum, but here's a taste of a plugin I am developing for Mitsulogger, additionally it will be released as a standalone logger for people not interested in logging the ECU and only logging UTEC or Tuner Data.

[MalibuJack]

BTW UniLogger will be replacing Mitsulogger, and you can choose what plugins you run, therefore you can have a UTEC with any of the supported widebands and create logs for it, and anything else that gets a plugin..

[EvoTech]

Man this will really be helpful for those that do not have a utec tuner but do have another wideband. Can you incorperate the ECU data into the UTEC logs with this? From your experience can you give us a brief summary of your expereinces in the differences you have seen in the ECU data vs. the UTEC data? Say knock counts for example.

[thebluesky]

Will the plx m-500 be supported?

[MalibuJack]

In v2.0 (Unilogger) Probably, at this time in the v1.5 maintainance release, probably not unless PLX can get me bench hardware or an emulator since with the bench hardware I can write the code in a few days, without a bench setup, it can take several weeks to get working right.

Also, if its a USB device I think it uses an FTDI chip, so it requires a bit more coding to prevent conflicts with the two.

[MalibuJack]

Originally Posted by EvoTech

Man this will really be helpful for those that do not have a utec tuner but do have another wideband. Can you incorperate the ECU data into the UTEC logs with this? From your experience can you give us a brief summary of your expereinces in the differences you have seen in the ECU data vs. the UTEC data? Say knock counts for example.

in v1.5 it won't, what v1.5 will do is make all of the logged data available for use in the Mitsulogger files as special requests.

In v2.0 the aggregator is the main portion of the application, all of the logged devices are plugins, therefore you can select items from any of the plugins that are to be logged. The format will not be the same as the UTEC as it has some dependencies that I can't work around with formatting and data rate that would confuse DLL, But I will include a definition file, hopefully something that can generate an appropriate definition file for use with your preferred data items. (I'm going to work with DLL at some point so this can happen more transparently with a little less confusion) In the future, I'm hoping that people will contribute plugins to offer some useful functionality within the application, such as Graphing and Dashboards.

Would you believe thanks to the timing of the release of the Tactrix cable, and my removal of the UTEC, I didn't get any logs of the two running at the same time to see if there was any particular observation I could make.

What I do know is the UTEC logs at a much slower data rate relative to the MUT protocol, however the UTEC data is usually more accurate due to the the clipping and interpolation MUT is forced to make to accomodate its protocol. I would like to take some time with some logs side by side, and see how close the timing and other values are between the two..

ECU Timing will best be viewed from the ECU's perspective, Knock Sum is also better read from the ECU as its knock discretion protocols are way more complex than the UTEC, the UTEC knock threshold settings are "Fairly" close to what stock would see, but it uses a different method for determining it and therefore there are some discrepencies.

MAF values are better logged through the UTEC, same with any other sensor data as its likely more accurate coming from the sensor directly.

Since I've had the tactrix cable and good logging, I had also been using the ECU+ (which I swap between the UTEC and ECU+ depending on what project i"m experimenting with) But the ECU+ has a very high sample rate for data, and is therefore a really good compliment for the MUT logging. But I can see any piggyback that can output good logs to be of huge value.

The key is that the MUT logger, regardless of your choice in tuning devices, is going to be where you want to monitor ECU specific behavior as it will give you an indication of what makes it happy or not, much better than relying on inferrential data that had been gathered before anyone really could get this before.

[Ultimate CC]

sweet deal jack...ill have to try it out once i figure out whats up with my evo...

[MalibuJack]

I forgot to update this thread awhile back..

Anyway, the UTEC logger is actually a tool that can be run standalone, although I don't really recommend it..

HOWEVER, This is where things get interesting, since all of the components are shared, I can add support at some point in the future for additional widebands not just the TunerPro..

So, you will have a dropdown in the UTEC/Tuner logger to use a different wideband, and another similar window comes up for the third party logger.. In turn, this component also runs within Mitsulogger so if you add the UTEC/Tuner in the dropdown..

So you have a "chain" of devices running, in an upcoming version you will open the Mitsulogger, drop down UTEC/Tuner, then in UTEC/Tuner you can add AEM Wideband.. And the entire log is right there..

its a bit hard to explain, but UTEC guys don't have to be married to a TurboXS tuner any longer, and your only limited to how many USB/Serial ports you can use on your Laptop. (I Use a Keyspan 4 port Serial adapter for USB with no issues)

[BoostN]

Great news Jack, especially since just recently got a killer deal on a utec and tuna for the evo (currently use them on my WRX). I also have the Zeitronix WB, and like smaller size and display. Guess I can sell the tuna? Decisions, decisions.....lol

[MalibuJack]

I have a bit more work to do in order to get both the UTEC and a third party wideband to log in the same logs.. I will probably address this as soon as I can.

you will be able to log MUT, UTEC, and Wideband simultaneously in the near future, and I will release a standalone UTEC logger with third party wideband support also. It is specifically for the Mitsubishi UTEC because the headers were hard coded, so I need to spend some time "Fixing" it so the headers are correct for any UTEC, thats the hold up.

Mitsulogger and the Standalone UTEC logger will log UTEC and Tuner at the same time if their daisychained like their supposed to be. But It will do more in the future when I have some time to address it.

[BoostN]

Thanks, I have the utec/tunapro daisy chained in my WRX mounted in the din slot. just more eye candy for a theif (evo is my daily drive) Meh, the glovebox is fine too. LOL

I'm going to use the Perrin EBCS with the utec, I did this when the perrin first came out couple years ago on my bugeye vf22 setup. I loved the ease of tuning the boost and interpolating the boost according to TPS. I can't understand why most the "tuners" I've run into have the owners take it off and return the stock selenoid and TXS bleeder. UNLESS they don't have maps in there library for the perrin.
I actually prefer this over my AVCR. that way when you 'turn on the meth' you just switch maps, not switch maps, and then adjust boost.

Sorry to go slightly off topic, but do you think the Perrin would respond well enough to use on a built 530whp (GT35R) set up on my subie(utec). I was told it would not work by Clark, but then again he said he never did try it.
Thanks Jack. Just let me know if you want me to test anything out for ya.
Peace
Mike

[BoostN]

BTW, mitsulogger 1.5 alpha is the one I should grab?
My pc is asking me for a .net framework v2.o 50727. So I found a site to download it and got over my head. Whats this

Quick Start Guide for DB2
Quick Start Guide for Oracle
Quick Start Guide for SQL Server
Quick Start Guide for Sybase

its asking me what one I want to use with it.
thanks

maybe you have a better link then http://www.datadirect.com/downloads/...FR6AWAodwl6LUw or somthing

[MalibuJack]

Go to microsoft website and download the .NET 2.0 Framework.. I think they also have 3.0 available for download and that will work also.