Mitsulogger v1.6 Beta 3 ***RELEASED***
Mitsulogger v1.6 Beta 3 ***RELEASED***
http://www.aktivematrix.com/forum/viewtopic.php?p=2245
SUPPORTED WIDEBANDS:
TurboXS UTEC / Tuner(pro) Combo
TurboXS Tuner(pro)
Zeitronix ZT2
Innovate Widebands (and all MTS protocol products)
AEM Wideband Gauge
There were a few big fixes:
- Improved performance of the logger.
- Fixed Zeitronix logger so it shouldn't crash when RPM signal is present.
- Wideband data is no longer incomplete on occasion, no longer drops data.
- If AFRMap or InjLatency values are unselected for logging, custom requests no longer show up with XXX, proper error handling has been implemented eliminating the need.
- If you had more than 99 Logger items total, program would crash, increased this limit to 300 This should allow all the requestID's you could ever want, plus custom requests.
- If you shut down app with [x] instead of Exit, settings will now be saved properly
- Removed [x] button from Wideband logger windows to prevent users from inadvertantly closing them.
New Features:
- Innovate support ALL Wideband and Logging devices that use the MTS protocol
- Auto-Detect all FTDI devices, openport devices automatically selected. Compatible FTDI devices can be manually selected (and will be added to autodetection as people report what cables work) No more compatibility/logger problems if a serial port using an FTDI chip is detected before the Openport Cable.
- Error messages are shown in the status window, error codes in logging will no longer break/crash logger (They will show up in place of the entry that triggered the error)
(Division by Zero is a good example) but a bad formula will now get a descriptive error to help you debug your custom requests or calculations.
- Added support for the AEM Wideband, Thanks www.nolimitmotorsport.com for providing the AEM Wideband.
- I added a rudimentary dashboard that will start evolving into something a bit more elaborate as time permits. Don't expect much, this is just some test code that happened to make it into the release because I forgot to disable it.
- Logger window and dashboard stay in foreground when logger is running.
- One-Button logging, hitting enter will start and stop logging.
- RequestID's now can read any number of bytes for a response
- Custom requests use "--" instead of "FF" freeing up the FF value if its ever used or needed.
- Added formatting to output data
- RAW (Raw output of response to RequestID)
- INT (Rounded Integer value)
- HEX (Responses are converted to Hex, multibyte responses shown!)
- BIN (Bitmapping/Binary expression of response, one or more bytes, great for status flags)
- Injector Latency values interpolated by battery voltage from 11v and 14v values entered (more accurate load calculations!) This actually is done as a custom request called Latency which is then used in the LOAD custom request.
- Any request created, can be used as part of any other evaluation (this has always been the case, but nobod knew it could be done)
- Window can now be resized to your liking, dashboard follows the main window and will resize accordingly.
There is a ton more stuff that I forgot to include in the release documentation.
If you use DatalogLab, you might have to update the Mitsulogger.txt file to reflect some newly available columns that you may decide to use (Innovate products specifically since they have different names depending on your configuration)
***BEFORE I GET SUPPORT ISSUES***
1) You must have your openport (Tactrix) or other FTDI based drivers installed.
2) .NET 2.0 or 3.0 MUST BE INSTALLED
3) If you get an error when trying to use Innovate logging, you will have to run the "Installinnovate.bat" file to register a file required. (You do not need logworks installed, but if you do mitsulogger won't conflict with anything)
4) Make sure the cables are connected and your wideband is powered up before trying to log, otherwise it won't connect and may time out.
5) I wanted to repeat this one, CUSTOM REQUESTS in requestID.xml have had their ID changed from "FF" to "--" so it won't ever conflict with a possible FF request.
6) Multibyte responses are even easier to configure, if your expecting a 2 byte response from a special request, you use a value of 3 instead of 2.. This is to support all of the new Live Tuning features (that you will start seeing evolve in releases starting with 1.7)
SUPPORTED WIDEBANDS:
TurboXS UTEC / Tuner(pro) Combo
TurboXS Tuner(pro)
Zeitronix ZT2
Innovate Widebands (and all MTS protocol products)
AEM Wideband Gauge
There were a few big fixes:
- Improved performance of the logger.
- Fixed Zeitronix logger so it shouldn't crash when RPM signal is present.
- Wideband data is no longer incomplete on occasion, no longer drops data.
- If AFRMap or InjLatency values are unselected for logging, custom requests no longer show up with XXX, proper error handling has been implemented eliminating the need.
- If you had more than 99 Logger items total, program would crash, increased this limit to 300 This should allow all the requestID's you could ever want, plus custom requests.
- If you shut down app with [x] instead of Exit, settings will now be saved properly
- Removed [x] button from Wideband logger windows to prevent users from inadvertantly closing them.
New Features:
- Innovate support ALL Wideband and Logging devices that use the MTS protocol
- Auto-Detect all FTDI devices, openport devices automatically selected. Compatible FTDI devices can be manually selected (and will be added to autodetection as people report what cables work) No more compatibility/logger problems if a serial port using an FTDI chip is detected before the Openport Cable.
- Error messages are shown in the status window, error codes in logging will no longer break/crash logger (They will show up in place of the entry that triggered the error)
(Division by Zero is a good example) but a bad formula will now get a descriptive error to help you debug your custom requests or calculations.
- Added support for the AEM Wideband, Thanks www.nolimitmotorsport.com for providing the AEM Wideband.
- I added a rudimentary dashboard that will start evolving into something a bit more elaborate as time permits. Don't expect much, this is just some test code that happened to make it into the release because I forgot to disable it.
- Logger window and dashboard stay in foreground when logger is running.
- One-Button logging, hitting enter will start and stop logging.
- RequestID's now can read any number of bytes for a response
- Custom requests use "--" instead of "FF" freeing up the FF value if its ever used or needed.
- Added formatting to output data
- RAW (Raw output of response to RequestID)
- INT (Rounded Integer value)
- HEX (Responses are converted to Hex, multibyte responses shown!)
- BIN (Bitmapping/Binary expression of response, one or more bytes, great for status flags)
- Injector Latency values interpolated by battery voltage from 11v and 14v values entered (more accurate load calculations!) This actually is done as a custom request called Latency which is then used in the LOAD custom request.
- Any request created, can be used as part of any other evaluation (this has always been the case, but nobod knew it could be done)
- Window can now be resized to your liking, dashboard follows the main window and will resize accordingly.
There is a ton more stuff that I forgot to include in the release documentation.
If you use DatalogLab, you might have to update the Mitsulogger.txt file to reflect some newly available columns that you may decide to use (Innovate products specifically since they have different names depending on your configuration)
***BEFORE I GET SUPPORT ISSUES***
1) You must have your openport (Tactrix) or other FTDI based drivers installed.
2) .NET 2.0 or 3.0 MUST BE INSTALLED
3) If you get an error when trying to use Innovate logging, you will have to run the "Installinnovate.bat" file to register a file required. (You do not need logworks installed, but if you do mitsulogger won't conflict with anything)
4) Make sure the cables are connected and your wideband is powered up before trying to log, otherwise it won't connect and may time out.
5) I wanted to repeat this one, CUSTOM REQUESTS in requestID.xml have had their ID changed from "FF" to "--" so it won't ever conflict with a possible FF request.
6) Multibyte responses are even easier to configure, if your expecting a 2 byte response from a special request, you use a value of 3 instead of 2.. This is to support all of the new Live Tuning features (that you will start seeing evolve in releases starting with 1.7)
Last edited by MalibuJack; Mar 26, 2007 at 07:02 PM.
Evolving Member
Joined: Jul 2005
Posts: 366
Likes: 0
From: Dubai, UAE
MJ, it seems to work fine in demo mode (I'm at work, so I won't be torture testing it till later), but here are some suggestions:
1. Would be nice to have a big green blinking indicator so I know when I can hit WOT
2. Does 1.6b3 include automatic start of logging when WOT is detected?
3. Resizing is nice, but would be nice if one could maximize the screen
4. Would also be nice to have a button that is mapped to the default log directory so that users don't have to reopen that directory all over again (this should be quite simple to do)
5. Mitsulogger does not remember the last 'szie' it was set to. Keeps reverting back to the stock size
Will post more feedback later. I'm very much into UIs so my apologies are due if I'm not focusing on the 'really important stuff'
1. Would be nice to have a big green blinking indicator so I know when I can hit WOT
2. Does 1.6b3 include automatic start of logging when WOT is detected?
3. Resizing is nice, but would be nice if one could maximize the screen
4. Would also be nice to have a button that is mapped to the default log directory so that users don't have to reopen that directory all over again (this should be quite simple to do)
5. Mitsulogger does not remember the last 'szie' it was set to. Keeps reverting back to the stock size
Will post more feedback later. I'm very much into UIs so my apologies are due if I'm not focusing on the 'really important stuff'
Last edited by ghoonk; Mar 27, 2007 at 06:48 AM.
MJ,
first time using your work.
I'm way happy, even a aol type guy can make it work.
although with the limited time I had, the large wideband box display bounced from the list of innovate inputs to nothing in rapid fashion*. I'm sure it was my hurried attempt to log something before it got past my bedtime.
*this was my botched install of the installinnovate file, just need to install it before you try logging.
first time using your work.
I'm way happy, even a aol type guy can make it work.
although with the limited time I had, the large wideband box display bounced from the list of innovate inputs to nothing in rapid fashion*. I'm sure it was my hurried attempt to log something before it got past my bedtime.
*this was my botched install of the installinnovate file, just need to install it before you try logging.
Last edited by nothere; Mar 28, 2007 at 06:17 AM.
Did you have the openport cable plugged in? Was it plugged into the car and the ignition is turned on? It initializes the interface unless there is no cable detected, then it goes to demo mode.
If your just looking to test it without it hooked up, you can check the demo mode box.
I'm surprised people always complain about trivial UI issues when the program is a data logger..
there is no WOT logging at the moment, but I never honestly found a need for it, the same with an indicator that its running.. I did "forget" to change the color of the button when the logger was connected and running as a clear indicator that it was running (if the RPM value changing wasn't enough indication)
I'm guessing the message for the openport cable is from the logworks plugin, since the plugin uses a channel and of course it won't initialize if soemthing else (mitsuloger) is already running.. If you can, disable the logworks plugin, I actually didn't even realize it would complain. This was actually the original reason I didn't want to implement the innovate developers kit. Since there is a dependency on Logworks, I'm fairly certain the logworks plugin might have to be disabled. You have to send me a screenshot of the error though. Mitsulogger makes very limited use of dialog boxes for errors, but you have to be very specific what they are when they do show up.
Settings are always saved on exit, there aren't too many settings you'd need to change regularly unless you worked on several cars regularly (this is an upcoming feature BTW)
Sorry if I seem a bit testy, I am just surprised about UI complaints for a free program.
Just like anything else, The testing I did was with what i had access to. So I know it works for the LC1 and LM1, as you add additional channels, there is no easy way to test it without the simulator tool that never showed up (I'm assuming there was a problem e-mailing me the file as i never got it from Joe) It never occurred to me to set up the plugin for the openport cable in logworks to see what would happen.
Also, mitsulogger remembers all of its settings such as log directory, you should never have to go back and set that again unless you install a new version, or the program is shut down unexpectedly before it ever saved its settings.
If your just looking to test it without it hooked up, you can check the demo mode box.
I'm surprised people always complain about trivial UI issues when the program is a data logger..
there is no WOT logging at the moment, but I never honestly found a need for it, the same with an indicator that its running.. I did "forget" to change the color of the button when the logger was connected and running as a clear indicator that it was running (if the RPM value changing wasn't enough indication)
I'm guessing the message for the openport cable is from the logworks plugin, since the plugin uses a channel and of course it won't initialize if soemthing else (mitsuloger) is already running.. If you can, disable the logworks plugin, I actually didn't even realize it would complain. This was actually the original reason I didn't want to implement the innovate developers kit. Since there is a dependency on Logworks, I'm fairly certain the logworks plugin might have to be disabled. You have to send me a screenshot of the error though. Mitsulogger makes very limited use of dialog boxes for errors, but you have to be very specific what they are when they do show up.
Settings are always saved on exit, there aren't too many settings you'd need to change regularly unless you worked on several cars regularly (this is an upcoming feature BTW)
Sorry if I seem a bit testy, I am just surprised about UI complaints for a free program.
Just like anything else, The testing I did was with what i had access to. So I know it works for the LC1 and LM1, as you add additional channels, there is no easy way to test it without the simulator tool that never showed up (I'm assuming there was a problem e-mailing me the file as i never got it from Joe) It never occurred to me to set up the plugin for the openport cable in logworks to see what would happen.
Also, mitsulogger remembers all of its settings such as log directory, you should never have to go back and set that again unless you install a new version, or the program is shut down unexpectedly before it ever saved its settings.
Last edited by MalibuJack; Mar 27, 2007 at 08:15 AM.
BTW... PLEASE Post bug reports in the mitsulogger forum on aktivematrix.. Start a new thread for a bug if you have to.
Please don't post them in this thread, or in the ECUFlash subforum here, unless its discussing using a feature or something that documents the software a little better, as its not the appropriate place for discussing my software.
Please don't post them in this thread, or in the ECUFlash subforum here, unless its discussing using a feature or something that documents the software a little better, as its not the appropriate place for discussing my software.
Last edited by MalibuJack; Mar 27, 2007 at 08:34 AM.
Trending Topics
Yep thats it, just change the dropdown to AEM for wideband, set the com port for the port AEM Wideband is plugged into, make sure the cable is hooked up from the AEM to the Computer...
I keep forgetting that both AEM and Innovate support are new for Mitsulogger.
I had the AEM support done for some time that I had thought it was already in an earlier release. This release got held up for awhile, but i wanted to get it out so I could freeze the current code to support some major revisions.
I had the AEM support done for some time that I had thought it was already in an earlier release. This release got held up for awhile, but i wanted to get it out so I could freeze the current code to support some major revisions.
I was able to crash it once:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at MitsuLogger.x751922eb1bfae5fb.x9019a79b966d57d0(Ob ject xe0292b9ed559da7d, EventArgs xfbf34718e704c6bc)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndPr oc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
MitsuLogger
Assembly Version: 1.6.2640.35940
Win32 Version: 1.6.2640.35940
CodeBase: file:///C:/Documents%20and%20Settings/Matt/Desktop/Car%20Stuff/Mitsulogger%20v1.6%20Beta%203/MitsuLogger.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
AxInterop.MSScriptControl
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/Matt/Desktop/Car%20Stuff/Mitsulogger%20v1.6%20Beta%203/AxInterop.MSScriptControl.DLL
----------------------------------------
Interop.MSScriptControl
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/Matt/Desktop/Car%20Stuff/Mitsulogger%20v1.6%20Beta%203/Interop.MSScriptControl.DLL
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
I started logging, waited a few seconds, stopped logging, deselected some parameters that I didn't want to log, tried to start logging again then it crashed. This was with the ZT-2 input enabled.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at MitsuLogger.x751922eb1bfae5fb.x9019a79b966d57d0(Ob ject xe0292b9ed559da7d, EventArgs xfbf34718e704c6bc)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndPr oc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
MitsuLogger
Assembly Version: 1.6.2640.35940
Win32 Version: 1.6.2640.35940
CodeBase: file:///C:/Documents%20and%20Settings/Matt/Desktop/Car%20Stuff/Mitsulogger%20v1.6%20Beta%203/MitsuLogger.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
AxInterop.MSScriptControl
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/Matt/Desktop/Car%20Stuff/Mitsulogger%20v1.6%20Beta%203/AxInterop.MSScriptControl.DLL
----------------------------------------
Interop.MSScriptControl
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/Matt/Desktop/Car%20Stuff/Mitsulogger%20v1.6%20Beta%203/Interop.MSScriptControl.DLL
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
I started logging, waited a few seconds, stopped logging, deselected some parameters that I didn't want to log, tried to start logging again then it crashed. This was with the ZT-2 input enabled.
Mixmaster, thanks for the bug report but you have to send it to me on Aktivematrix, never saw that one before but I know what probably caused it. It has nothing to do with the wideband logging, but just that you unselected items that were selected previously. Although I've never gotten that error before doing something similar.
EDIT: I was able to reproduce your error, I know exactly what it is..
What I would do for the time being is not de-select items that you have logged already. I'll hopefully have this and possibly other bugfixes addressed.
EDIT: I was able to reproduce your error, I know exactly what it is..
What I would do for the time being is not de-select items that you have logged already. I'll hopefully have this and possibly other bugfixes addressed.
Last edited by MalibuJack; Mar 27, 2007 at 03:31 PM.