Help troubleshooting MPScan

[wheming]

Having some trouble with MPScan.
I was having connection issues last Nov or so before dropping MeanMini off at Brian's shop.
Now that she is back, I am trying to get some logs so i can make some tuning adjustments.
I am getting errors that say failed to connect and to cycle the key off-on. But, it does not work, and then when I click record again it closes MPScan abruptly.

Here is the port log:
mpscan ver - 2.0.3.3 (3/4/2016 1:15:21 PM)
Microsoft Windows XP Professional - Win32NT
trying to open port COM17 - ctlrecord_click
got a good port back - ctlrecord_click
try to open port COM17 -initport
COM17 is a legit port -initport
usb is available on COM17 -initport
usb ftdi serial number BBS3XE4O2J is available - initport
[usbportinit] setting port baud rate to 7812
ftdi open successful on COM17 -usbportinit
using protocol SMEC T1:1
attempt to change ecu baud rate to 62500
Sending byte 18
Received 0 byte(s): 0
Read confirm byte failed (status:0 - count:0)
Sending byte 18
Received 0 byte(s): 0
Read confirm byte failed (status:0 - count:0)
Sending byte 18
Received 0 byte(s): 0
Read confirm byte failed (status:0 - count:0)
Sending byte 18
Received 0 byte(s): 0
Read confirm byte failed (status:0 - count:0)
usbsethibaud failed - usbportinit
ftdi open unsuccessful - usbportinit
Sending byte 254
Received 0 byte(s): 0
Read confirm byte failed (status:0 - count:0)
Sending byte 254
Received 0 byte(s): 0
Read confirm byte failed (status:0 - count:0)
can't open ftdi port - usbportinit
Unable to open/setup port. - ctlrecord_click


Here is the Coms:
-Comport analysis for mpscan version 2.0.3.3 (3/4/2016 1:12:23 PM)
-Locating ports on computer-
name:USB Serial Port (COM17) deviceid:FTDIBUS\VID_0403+PID_6001+BBS3XE4O2JA\000 0
name:Communications Port (COM1) deviceid:ACPI\PNP0501\4&61F3B4B&0
number of ftdi devices found - 1
ftdi port num:COM17 serial num:BBS3XE4O2J
Inverted tx:True Inverted rx:True
Vcp driver loaded:True
Latency is set to:16
checking to see if usb port number COM17 is a moates device
Moates device not located on this port
default com port set to:COM17

I'm wondering if it is a bad cable?
Is that baud rate change correct?

I did try MPScan on Slugmobile and it made a log, but don't know if it was some sampling issue as it looked like several duplicated readings.

Any help from the smart folks is appreciated. Was hoping to possibly race this Sunday, if I can get some logs and make some adjustments tomorrow.

[wheming]

How can you get to what's in this error report?


I just tried the other cable I had, and same problem. I updated all the setup files, and still same problem.
Here is the port log 9you can see the different cable, shows port 14):
mpscan ver - 2.0.3.3 (3/4/2016 6:09:02 PM)
Microsoft Windows XP Professional - Win32NT
trying to open port COM14 - ctlrecord_click
got a good port back - ctlrecord_click
try to open port COM14 -initport
COM14 is a legit port -initport
usb is available on COM14 -initport
usb ftdi serial number BBVGDESB is available - initport
[usbportinit] setting port baud rate to 7812
ftdi open successful on COM14 -usbportinit
using protocol SMEC T1:1
attempt to change ecu baud rate to 62500
Sending byte 18
Received 1 byte(s): 18
Changing mpscan baud rate to 62500
Sending byte 242
Received 1 byte(s): 242
Byte 242 was sent 1 times to make the change.
usb ftdi
Successfully opened port - ctlrecord_click

And the Coms:
-Comport analysis for mpscan version 2.0.3.3 (3/4/2016 6:08:24 PM)
-Locating ports on computer-
name:USB Serial Port (COM14) deviceid:FTDIBUS\VID_0403+PID_6001+BBVGDESBA\0000
name:Communications Port (COM1) deviceid:ACPI\PNP0501\4&61F3B4B&0
number of ftdi devices found - 1
ftdi port num:COM14 serial num:BBVGDESB
Inverted tx:True Inverted rx:True
Vcp driver loaded:False
Latency is set to:2
checking to see if usb port number COM14 is a moates device
Moates device not located on this port
default com port set to:COM14

[ShelGame]

VCP Driver loaded: false

I think this is the issue.

Go here -- http://www.boostbutton.com/turbonato...id=cable_setup

About halfway down, look for the section called "Setup the USB to SCI cable". You'll need to open Windows Device manager and force it to load the VCP driver.

[wheming]

That is setup. Just Checked both cables.

and just tried again, and mpscan just closed out as soon as I hit record.

mpscan ver - 2.0.3.3 (3/4/2016 7:44:36 PM)
Microsoft Windows XP Professional - Win32NT
trying to open port COM17 - ctlrecord_click
got a good port back - ctlrecord_click
try to open port COM17 -initport
COM17 is a legit port -initport
usb is available on COM17 -initport
usb ftdi serial number BBS3XE4O2J is available - initport
[usbportinit] setting port baud rate to 7812
ftdi open successful on COM17 -usbportinit
using protocol SMEC T1:1
attempt to change ecu baud rate to 62500
Sending byte 18
Received 1 byte(s): 18
Changing mpscan baud rate to 62500
Sending byte 242
Received 1 byte(s): 242
Byte 242 was sent 1 times to make the change.
usb ftdi
Successfully opened port - ctlrecord_click


-Comport analysis for mpscan version 2.0.3.3 (3/4/2016 7:43:16 PM)
-Locating ports on computer-
name:USB Serial Port (COM17) deviceid:FTDIBUS\VID_0403+PID_6001+BBS3XE4O2JA\000 0
name:Communications Port (COM1) deviceid:ACPI\PNP0501\4&61F3B4B&0
number of ftdi devices found - 1
ftdi port num:COM17 serial num:BBS3XE4O2J
Inverted tx:True Inverted rx:True
Vcp driver loaded:True
Latency is set to:16
checking to see if usb port number COM17 is a moates device
Moates device not located on this port
default com port set to:COM17

[wowzer]

send me your mpc file you are trying to work with and i'll see if i can recreate this issue. your last post looks like it connected properly. for mpscan to bomb out light that without an error is very weird. also, look in the same directory the coms logs you posted above were in and see if there is a file called mptapperr.txt. i'm curious if there is and what it may say.

[wheming]

Thanks Morris. I'll be back at the house this afternoon and i'll post it. I don't remember seeing another text file, but i will look.

[wowzer]

wayne - sent you an email.

[wheming]

Not exactly sure what i did, but i just got a successful connect and log.

Will update more in a bit.

[wheming]

MPScan has been kind of spotty for me. Today it worked when i tried it. The other day after i posted it was working i had trouble connecting again.

Not sure if it is something wrong with my laptop or what. But i got some run logs today.