Hmm, my ECULoad value clips at 100, not 160.

 

I am having some problems with the AEM logger, and am recieving Exception text on a regular basis. Not only that, but when it does log for a bit, the AFR values are jumbled in excel; and sometimes there will just be one value (usually 14.7) all the way down the entire spreadsheet, even though i know it changes throughout the pull.

I would appreciate if you would PM me with the best way to contact you in order to get you a couple logs so you can see what i am talking about. I will also try to PM you and send you an Email or something.

I will post the bug report like MixMaster did when i get home and get to pull it up again. Did you say you want that posted on Aktivematrix?

 

Now thats interesting..


Its possible you found a bug or I fat-fingered one of the requests, but I would need to see some of your logs (post them on Aktivematrix along with the bug info you've experienced in a new thread in the mitsulogger forum) Oddly enough, these items haven't changed at all in the new version.

 

Best bet is to post a new thread in the mitsulogger forum as I stated, attach as much info as you can so I can debug it as I go through different issues. There is a "Raw output" logger in the AEM Logger (as there are in all the wideband loggers) if you get garbled data in the raw output, its likely a problem with the serial connection itself. but I'll need to see the logs to be sure.

Oddly enough the AEM logger got the most testing and has the least amount of code associated with it.

 

I am testing the AEM Logger on my bench now with an ECU and all logging, I get no dropped data or anything garbled, tried it on two different machines.

The Debug output will sometimes be garbled because there is no handshake between the AEM and the serial port, but that data is discarded before it goes to the logger.

I even simulated different AFR's by using butane from a lighter to go from super-rich to super lean.

I think the error box your getting is the telltale.. I'm thinking its a buffer overrun or buffer underrun error. This happens with some serial ports that don't handle buffering well.

 

***IMPORTANT*** If anyone is having trouble with Innovate logging, It has to do with different versions of a file that conflicts with logworks.

If you find that your data doesn't log any values properly (its fixed at 0 or the lowest value it can read) Try overwriting the MTS.DLL file in the mitsulogger directory with the one that came with your version of logworks.

 

is anyone else having trouble accessing the aktivematrix website?

 

Had me worried there for a moment, its working fine.

 

yeah its working for me now

 

Thanks for providing this software. It's helped me do a lot already I see that the dash shows real-time rpms. Is it possible for it to also show (or show in place of rpms) another logged item? That would be awesome. Thanks again!

 

At the moment, no. The dash was the beginnings of a 2.0 plugin that I was experimenting with, which I left in this version as a little easter egg.

The 2.0 version of all of the plugins will be configurable. I haven't decided how much effort I am going to put into the dashboard as the entire architecture is designed for you guys to develop your own plugins to offer.

I have suspended development and releases on all of the mitsulogger versions for the time being because I don't have the time. But I'm hoping as I get more free time, I'll finish 2.0 as every aspect of the application works by using seperate components that can be mixed and matched. The intent was to have a specific mitsulogger (MUT) component, and the logger, dashboard, wideband, and other data analysis, display, etc tools implemented as seperate modules that can be instantiated several times each with its own configuration. There are a few reasons for this..

First, for wideband users, there are some guys starting to put widebands or EGT sensors in more than one location.. In my case, I want to run an Innovate Wideband, a TurboXS UTEC (without the tuner pro), and Mitsulogger and put the data in the same logs.

Additionally, there is a scriptomatic module that can be programmed to do anything, so you can add/create/share scripts to do anything that VBScript is capable of. This started out as the beginnings of an NMEA GPS tracking module.

Each module operates in its own thread, if something goes awry, you will only lose the data in the one module, and not foul up your entire logs with missing data. When a module registers itself, it registers a header, and data items.

Each module will have the ability to configure how you want to massage your data before its passed to the logger and dashboard modules.

This is as far as I had gotten before development was suspended.

 

Ok, sounds good. How should I go about developing a plugin for MitsuLogger? I was thinking of just using Excel to open the current log file and displaying maybe 2 real-time logged variables. Thanks!

 

I loved the new version of mitsulogger but iam having problem reading my afr.Its giving me a number of 7.25 but its reading 14.7 on my LC1.What am i missing here?TY

 

nm

 

Very cool, thanks for your support of the community!