It has been a great while since I used Mitsulogger however I have had issues getting Evoscan to log data accurately in Windows 7. Can anyone point me to the files or specifically the mods. required to run JDM map and output to DLL? If I remember there are modifications required to allow logging of JDM and maybe some changes required for DLL. Thanks I realize this has been covered and I stink at searching.

PS nice to see you posting again MJ it is safe to say you have been missed

 

Here you go^^

https://www.evolutionm.net/forums/ec...tructions.html

Logging Boost in EvoScan/Mitsulogger

MAP sensors do not know the local atmospheric pressure. To log boost in psig (what all boost gauges show and what people always use to discuss boost values), the conversion formula for the logging program needs to have an offset for your local atmospheric pressure. The general formula for the JDM Evo 9 MAP sensor is:

0.19347*x-b

where b is the local atmospheric pressure. The local atmospheric pressure is affected strongly affected by altitude. For example the pressure at sea level is 14.7 psi, but at 5000 ft, the pressure is 12.2 psi. That's a big difference when you want to log boost. Use this table of altitude vs pressure to determine the offset pressure for your formula:

altitude (ft) local atmospheric pressure (psi)
0 14.7
500 14.4
1000 14.2
1500 13.9
2000 13.7
2500 13.4
3000 13.2
3500 12.9
4000 12.7
4500 12.5
5000 12.2
6000 11.8
7000 11.3
8000 10.9

*For example*, if you are living at 750 ft, then you'd want to use 14.3 psi as your offset, and the formula would be

0.19347*x-14.3

In the following instructions, please use your formula in place of the words FORMULA HERE.

For EvoScan 0.99+, the MAP logging definition in the Data.xml file should be changed to:

<DataListItem DataLog="Y" Color="" Display="JDM MAP" LogReference="JDMMAP" RequestID="38" Eval="FORMULA HERE" Unit="psig" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-15" GaugeMax="35" ChartMin="-15" ChartMax="35" ScalingFactor="1" Notes=""/>

To log boost in psi in Mitsulogger, the MAP logging definition should be changed to:

<Request LogReference="JDMMAP" RequestID="38" Eval="FORMULA HERE" Unit="psig" Logged="y" Response="2"/>

 

I am not trying to log wideband, I don't have a wideband yet.

in the demo mode, I see values moving fast, but now think about it, don't think it's work, the logs it generates just odd values

Only one USB device plugged in, which is my tactrix cable. the logger detects my Openport 1.3 Mitsubishi

 

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidCastException: Conversion from string "&h" to type 'Double' is not valid. ---> System.FormatException: Input string was not in a correct format.
at Microsoft.VisualBasic.CompilerServices.Conversions .ParseDouble(String Value, NumberFormatInfo NumberFormat)
at Microsoft.VisualBasic.CompilerServices.Conversions .ToDouble(String Value, NumberFormatInfo NumberFormat)
--- End of inner exception stack trace ---
at Microsoft.VisualBasic.CompilerServices.Conversions .ToDouble(String Value, NumberFormatInfo NumberFormat)
at Microsoft.VisualBasic.Conversion.Int(Object Number)
at MitsuLogger.Mitsulogger.LogMUT()
at MitsuLogger.Mitsulogger.StartLogger()
at MitsuLogger.Mitsulogger.Button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(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.3074 (QFE.050727-3000)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
MitsuLogger
Assembly Version: 2.0.3437.30866
Win32 Version: 2.0.3437.30866
CodeBase: file:///C:/Program%20Files%20(x86)/Mitsulogger/Mitsulogger%202.0%20Release/MitsuLogger.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
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.3053 (netfxsp.050727-3000)
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.3053 (netfxsp.050727-3000)
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.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
UtecTunerLogger
Assembly Version: 1.5.0.0
Win32 Version: 1.5.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/Mitsulogger/Mitsulogger%202.0%20Release/UtecTunerLogger.EXE
----------------------------------------
ZeitronixZT2Logger
Assembly Version: 1.5.0.0
Win32 Version: 1.5.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/Mitsulogger/Mitsulogger%202.0%20Release/ZeitronixZT2Logger.EXE
----------------------------------------
AEMLogger
Assembly Version: 1.6.0.0
Win32 Version: 1.6.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/Mitsulogger/Mitsulogger%202.0%20Release/AEMLogger.EXE
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
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.3074 (QFE.050727-3000)
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.

 

^ok! it looks like it's Mitsulogger string to number conversion problem but it can also be a windows globalization/culture issue too. I recalled encounting similar issue in my .NET programming tasks before. Do you happen to run windows version for country other than US (English)?

 

hey malibu jack nice to see u back.
i kinda got the same problem as fugiwara. i'm running vista home premium (64bit) and getting the same error. i'm goin to try running as admin and see what happens.

 

tried runnin as admin, connectin the cable to the laptop before openin mitsulogger and same prob.

 

I am using US (English) version of vista 64 bit home edition.

Thanks for letting me and MJ know, at least now I am not the only one.

does evoscan works for you?

 

The demo mode generates RANDOM VALUES, its intended to test the formulas, not simulate anything.

 

Yes, that makes more sense now.. By chance did you guys modify the requestid.xml file, to enable one of the hex mode requests, or enable them in the listview? It'll help me track it down.. its one of the few things I don't think I tested.

 

I cannot reproduce the error, however at least I have an idea where its happening.. I'm thinking the error is due to a null value being returned instead of a numeric, &h is an implicit "hex" string, however if its just &h and not &h0 or whatnot, it will throw that error.. Since it has never happened in the past, in any previous version that I can recall, I have an idea where its happening. It was careless programming in my part as I'm not trapping error conditions in all areas of the program.

I don't think the issue is O/S version related so its likely going to happen on other OS versions too.

 

I posted a bugfix version, the bug fix addresses the lack of error handling in that routine, however It may not fix the logging issue (if its slow, or returning zeroes or whatnot.

I would look at your laptop's configuration, as the Interrupt routines are impacted by the Hard Drive Shock protection, if it suspends writing to the disk, it might also suspend data reads over the USB bus or cause things to queue up. Unfortunately you may have to disable disk shock protection (kind of a catch 22) if you continue to have a logging problem. I suspect you might have the same problem with Mitsulogger as you are with Evoscan (too many samples or not enough) when that happens.

 

ok I am going to install the bug fix version.

you think it might has to do w/ shock protection? but I was just testing the logger while the car is idling and the program just shut off in about 5 seconds. the car wasn't even moving.

 

One thing I noticed that Mitsulogger is not in the "programs and feature" folder, in another word, I don't have to go there to uninstall the program, unlike the ecu flash if I want to uninstall it I have to go there to properly uninstall it.

 

evoscan works (2.6 beta 11) but i'm unable to log my wideband (aem)