MPScan

[wowzer]

i actually bought the rn240 if i remember since it was a complete unit that had the rs232 connector as well as being powered by an external source. i'm sure one of you electronics geeks could make a cheaper unit using the actual bluetooth module. you will also need a ttl converter to connect to the ecu, just like the old days. what would be nice is a unit that uses a rn module incorporated with an inverter (max232?) all in one nice package.

[Aries_Turbo]

If you did just the RN module without the serial converter wouldn't it just be ttl straight to Bluetooth?

[wowzer]

i'm meant to say a ttl inverter. the ftdi cable allows you to invert the tx and rx signals. the rn module needs to use a separate ttl inverter. i think i got my original kit around 2005 (jay maybe?) and another from rob some time ago i believe. there's probably a cheap unit on ebay somewhere or maybe someone here still makes them.

[Force Fed Mopar]

Screenshot

[wowzer]

hmm - it all looks ok. does mptune still allow you to read/write bins? do you have anything else plugged into your usb ports?

[Force Fed Mopar]

Yeah MPTune still works, and no just have the FTDI hooked up when I try to log.

[wowzer]

wonder if something broke in the last update. i'll hook up my system tonight and try it. does mptune show the same com port number and settings?

anybody else having problems with this last update?

[iangoround]

I'm getting the same unable to open/setup port error. I thought maybe it was some setting I had wrong, but the logworks plugin works fine with my logic module.

[Force Fed Mopar]

wonder if something broke in the last update. i'll hook up my system tonight and try it. does mptune show the same com port number and settings?

anybody else having problems with this last update?

When I plug the Burn2 up it says "Burn1/2 found on Port Com 6". It always works fine. I don't have MPTune loaded when I'm trying to log though.

[wowzer]

mpscan should use the same port as mptune (assuming you use the same ftdi cable!) i assume your burn2 has its own ftdi cable.

[Force Fed Mopar]

The Burn2 just uses a regular USB cable. To log in the car I have an FTDI board that has the wires running to the diag plug under the hood on one side, and a regular USB cable plugs into the other side. Board has red and green lights on it.

[iangoround]

Here's what I've got:

using an FTDI cable with leads soldered to the appropriate pins inside the LM, I can get it to start logging about 25% of the time. If it works, it works fine. If I stop logging and try to start again, it comes up with the "unable to open/setup com port" error. If MPScan isn't the first program to try using the com port after starting the computer, it gives me the error and I can fix it by restarting the computer. Sometimes when it gives the error, unplugging the cable and swapping USB ports while MPScan is open will fix it, however that only works once per computer boot. Every once in a while cycling the key on the car will allow it to work, but only if I get the error on initial startup.
.
Also, none of the actuator tests seem to work for me. In fact, usually when I try them I come up with an unhandled exception. I can't pull error codes either. This is the error that comes up with the actuator test:

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

************** Exception Text **************
System.ArgumentException: Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection.
at System.IO.Ports.SerialPort.Read(Byte[] buffer, Int32 offset, Int32 count)
at MPScan.frmDRBAtm.EcuInterface(Byte[] bytestosend)
at MPScan.frmDRBAtm.btnStart_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.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.O nMessage(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.5466 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
MPScan
Assembly Version: 2.0.0.0
Win32 Version: 2.0.1.5
CodeBase: file:///C:/Program%20Files%20(x86)/MP%20Suite/MPScan/MPScan.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
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.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.5420 built by: Win7SP1
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
C1.C1Flash.2
Assembly Version: 2.0.20113.87
Win32 Version: 2.0.20113.87
CodeBase: file:///C:/Program%20Files%20(x86)/MP%20Suite/MPScan/C1.C1Flash.2.DLL
----------------------------------------
gzay8beh
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
FTD2XX_NET
Assembly Version: 1.0.10.0
Win32 Version: 1.0.10.0
CodeBase: file:///C:/Program%20Files%20(x86)/MP%20Suite/MPScan/FTD2XX_NET.DLL
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
fot2g-3x
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.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.

This one popped up when I clicked the "open" icon in the toolbar after closing and reopening the program:

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

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at MPScan.ScanMain.OpenToolStripMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Obje ct key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(Event Args e)
at System.Windows.Forms.ToolStripItem.HandleClick(Eve ntArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(M ouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventIntera ctive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(Event Args e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEven tArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(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.5466 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
MPScan
Assembly Version: 2.0.0.0
Win32 Version: 2.0.1.5
CodeBase: file:///C:/Program%20Files%20(x86)/MP%20Suite/MPScan/MPScan.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
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.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.5420 built by: Win7SP1
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
C1.C1Flash.2
Assembly Version: 2.0.20113.87
Win32 Version: 2.0.20113.87
CodeBase: file:///C:/Program%20Files%20(x86)/MP%20Suite/MPScan/C1.C1Flash.2.DLL
----------------------------------------
lus1csek
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
FTD2XX_NET
Assembly Version: 1.0.10.0
Win32 Version: 1.0.10.0
CodeBase: file:///C:/Program%20Files%20(x86)/MP%20Suite/MPScan/FTD2XX_NET.DLL
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.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.

[iangoround]

Oh yeah, I've found that if there is more than one FTDI device on the computer it gives the same "unable to open/setup com port" error even if you've selected the correct com port in the setup. The usb-serial convertor I use for my LC-1 confuses it for some reason.

[wowzer]

i'll try to spend some time with it this weekend. sorry. don't know why it would quit working.

the actuator stuff has never been tested. i started working on it using my smecstim but never really completed the testing nor hooked it up on my charger or van. i should have disabled the menu options but didn't. i did buy a drb 2 some time back and hope to capture it's protocol with my saleae analyzer later this summer. and, i think the LM protocol is a little different. i only set up the smec stuff at this point for the actuator stuff.

[iangoround]

I just realized I wasn't running the latest version of .net on that machine. I've updated it but haven't gone back out to the garage to see if it makes anything play nicer.

[wowzer]

force fed / iangoround - are you still having issues?

i tried it this morning on my smecstim using both a win7 and win xp machine and it seemed to work ok. the main thing is to 1) have the ftdi cable plugged in before starting mpscan, 2) make sure the vcp option in the driver is set 3) confirm which com port the ftdi cable is really on and 4) make sure you select that com port in the com port settings screen.

i have some logic in mptune that keeps track of plugging/unplugging a usb cable. i'll look at adding that to mpscan. i did plug in my burn2 which also uses the ftdi cable and it can cause confusion if you do not select the correct com port in the settings screen. since we do not force users to create a unique id for their ftdi cable i cannot automatically differentiate which ftdi cable is the one to use for mpscan. that is why you need to make sure you select the right com port. the lc1, hptuners, burn2 etc use device specific names that their software can identify.

lmk.

[Force Fed Mopar]

I'll try it again and report back.

[wheming]

I tried out MPScan and it was working for me.
Then I downloaded the update and ran it again. Worked again. I did need to start up and and verify com port and like you said the cable needs to be connected first. Before opening MPScan.

Now I just need to get through some of the setup literature/posts to get my gauges set up properly.

[wowzer]

.....
Now I just need to get through some of the setup literature/posts to get my gauges set up properly.

it is a bit overwhelming at first. the main thing is to get the ram locations set up properly, e.g. decimals, display min/max, etc. then its just a matter of creating a "layout" using the ram location file you created and saving that layout. you should be ready to go after that.

if you do set up a gauge type and customize it, there is an option when you right click on the gauge to save it as the default style. that way, the next time you add that gauge type it should initially set it up using your custom settings.

[wheming]

it is a bit overwhelming at first. the main thing is to get the ram locations set up properly, e.g. decimals, display min/max, etc. then its just a matter of creating a "layout" using the ram location file you created and saving that layout. you should be ready to go after that.

if you do set up a gauge type and customize it, there is an option when you right click on the gauge to save it as the default style. that way, the next time you add that gauge type it should initially set it up using your custom settings.

Ok, I think that is the tidbit I missed. I used an imported .lst for my ram locations but I didn't do anything to that file. I need to go back and adjust min/max's in that table for them to have the proper displayed scale? I was right clicking on gauges to try and adjust but couldn't see anything that would do it.
I'll give that a look.
I've got a layout/dashboard saved, I just need to scale my gauges properly.

The wideband selection on adding a gauge is grayed out. I thought we could import the wideband? Or is it not set up for a wideband connected to the same laptop using another usb port? When trying to do so, I select the proper com port but what would be the "save setup" button just says "button1". I thought I had the most up to date rev.
Am I missing a driver or something?