Page 1 of 3 123 LastLast
Results 1 to 20 of 48

Thread: LM MPScan Fail

  1. #1
    Boost, it's what's for dinner... Turbo Mopar Staff Aries_Turbo's Avatar
    Join Date
    Dec 2005
    Location
    Warsaw, NY
    Posts
    8,838

    LM MPScan Fail

    OK.... i bought robs SCI adapter. I had a FTDI usb cable from mouser from a few years ago (never used.... in anti static bag still) and i soldered it to RC servo connectors and matched the colors up to the silkscreen on robs adapter.

    i installed the drivers from the MPSCAN thread and connected the FTDI cable to my netbook. installed correctly.

    fresh MPSCAN install and let it update.

    went out to car. plugged adapter into SCI plug (that successfully read my OTC scanner) and plugged FTDI usb cable into laptop... shows up as com14 in windows 7.

    turned key on. fuel pump primed.

    opened mpscan. i set up a profile for my car previously (LM selection, com14, saved) setup a few gauges, etc.

    clicked logging after opening profile.

    it gave me the "Unable to open/setup port. Try turning key off and then back on." error.

    i did that. no dice.

    i closed the program. tried another usb. checked windows for com14.

    tried again.

    turned the car off and on. tried starting it, etc.

    no combination allowed it to connect and log.

    any tips/tricks etc?

    Quote Originally Posted by turbovanman
    This one is easy, I have myself to blame, I rush things, don't pay attention to gauges when I should, change to much stuff at once then expect miracles, the list is endless.

  2. #2
    Boost, it's what's for dinner... Turbo Mopar Staff Aries_Turbo's Avatar
    Join Date
    Dec 2005
    Location
    Warsaw, NY
    Posts
    8,838

    Re: LM MPScan Fail

    btw, i may try connecting directly to the old school connection that i made to the MCU in the LM for my old serial/TTL adapter that would let me log to winlog (risen's plugin) with the laptop native serial port if i cant get robs adapter to work.

    my end goal is making adapters to run a SMEC on my LM harness and run the adapter/ftdi/flash module on that. this is just an intermediate step.

    Brian

    Quote Originally Posted by turbovanman
    This one is easy, I have myself to blame, I rush things, don't pay attention to gauges when I should, change to much stuff at once then expect miracles, the list is endless.

  3. #3
    Supporting Member Turbo Mopar Contributor
    Join Date
    Jun 2006
    Location
    Spearfish SD
    Posts
    2,038

    Re: LM MPScan Fail

    brian - post up the two log files, mpscanport.txt and mpt2coms.txt. also, i assume it shows the port settings in the lower left corner of the screen? lastly, you may want to try connecting the ftdi tx/rx lines together directly to see if you can send and receive data over the ftdi cable. the data won't make sense but other than it should echo back the locations you are sending. mptune has an option btw under the com port settings to test whether the ftdi cable works.
    Last edited by wowzer; 07-30-2015 at 10:34 PM.
    89 Voyager LE, 2.5T2 - rest in peace
    87 Charger Shelby T2 (2.4 conversion in process)

  4. #4
    Boost, it's what's for dinner... Turbo Mopar Staff Aries_Turbo's Avatar
    Join Date
    Dec 2005
    Location
    Warsaw, NY
    Posts
    8,838

    Re: LM MPScan Fail

    hmmmm..... at what location are these two files to be located?

    yeah it shows com14 and the LM baud rates at the lower left corner.....

    obviously not a knock on you but i figured if i posted up we could work out some more potential bugs.

    Quote Originally Posted by turbovanman
    This one is easy, I have myself to blame, I rush things, don't pay attention to gauges when I should, change to much stuff at once then expect miracles, the list is endless.

  5. #5
    Supporting Member Turbo Mopar Contributor
    Join Date
    Jun 2006
    Location
    Spearfish SD
    Posts
    2,038

    Re: LM MPScan Fail

    they should be under "C:\Users\(username)\AppData\Roaming\MPScan"

    i'm looking for new opportunities to work on mpscan so fire away
    89 Voyager LE, 2.5T2 - rest in peace
    87 Charger Shelby T2 (2.4 conversion in process)

  6. #6
    Boost, it's what's for dinner... Turbo Mopar Staff Aries_Turbo's Avatar
    Join Date
    Dec 2005
    Location
    Warsaw, NY
    Posts
    8,838

    Re: LM MPScan Fail

    Ok I'll look in a bit. I'm away from my car but I have my netbook with me.

    Quote Originally Posted by turbovanman
    This one is easy, I have myself to blame, I rush things, don't pay attention to gauges when I should, change to much stuff at once then expect miracles, the list is endless.

  7. #7
    Boost, it's what's for dinner... Turbo Mopar Staff Aries_Turbo's Avatar
    Join Date
    Dec 2005
    Location
    Warsaw, NY
    Posts
    8,838

    Re: LM MPScan Fail

    Quote Originally Posted by wowzer View Post
    brian - post up the two log files, mpscanport.txt and mpt2coms.txt. also, i assume it shows the port settings in the lower left corner of the screen? lastly, you may want to try connecting the ftdi tx/rx lines together directly to see if you can send and receive data over the ftdi cable. the data won't make sense but other than it should echo back the locations you are sending. mptune has an option btw under the com port settings to test whether the ftdi cable works.
    Quote Originally Posted by mpscanport
    mpscan ver - 2.0.2.8
    Microsoft Windows 7 Ultimate - 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 FTFVTQWP is available - initport
    setting port baud rate to 976
    ftdi open successful on COM14 -usbportinit
    using protocol LM:0
    attempt to change ecu baud rate to 7812
    Sending byte 18
    Received byte 0
    Sending byte 18
    Received byte 39
    Changing mpscan baud rate to 7812
    Sending byte 18
    Received byte 0
    Sending byte 18
    Received byte 0
    Sending byte 18
    Received byte 128
    Sending byte 18
    Received byte 0
    usbsethibaud failed - usbportinit
    ftdi open unsuccessful - usbportinit
    Sending byte 254
    Received byte 128
    Sending byte 254
    Received byte 0
    can't open ftdi port - usbportinit
    Unable to open/setup port. - ctlrecord_click
    Quote Originally Posted by mpt2coms
    -Comport analysis for mpscan version 2.0.2.8
    -Locating ports on computer-
    name:USB Serial Port (COM14) deviceid:FTDIBUS\VID_0403+PID_6001+FTFVTQWPA\0000
    number of ftdi devices found - 1
    ftdi port num:COM14 serial num:FTFVTQWP
    Inverted tx:False Inverted rx:False
    Latency is set to:16
    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
    found them.

    i didnt do the cable test yet as its at home and im 6hrs away.

    ill try it later if those logs dont make sense.

    thanks

    brian

    brian

    Quote Originally Posted by turbovanman
    This one is easy, I have myself to blame, I rush things, don't pay attention to gauges when I should, change to much stuff at once then expect miracles, the list is endless.

  8. #8
    Supporting Member Turbo Mopar Contributor
    Join Date
    Jun 2006
    Location
    Spearfish SD
    Posts
    2,038

    Re: LM MPScan Fail

    brian - did you make sure you inverted the rx/tx lines on the ftdi chip using the ftprog utility? based on the log above it does not look like it....
    89 Voyager LE, 2.5T2 - rest in peace
    87 Charger Shelby T2 (2.4 conversion in process)

  9. #9
    Boost, it's what's for dinner... Turbo Mopar Staff Aries_Turbo's Avatar
    Join Date
    Dec 2005
    Location
    Warsaw, NY
    Posts
    8,838

    Re: LM MPScan Fail

    I thought with robs adapter I didn't have to do that or am I mistaken?

    Quote Originally Posted by turbovanman
    This one is easy, I have myself to blame, I rush things, don't pay attention to gauges when I should, change to much stuff at once then expect miracles, the list is endless.

  10. #10
    Visit www.boostbutton.com... Turbo Mopar Contributor ShelGame's Avatar
    Join Date
    Dec 2005
    Location
    Whitmore Lake, Michigan, Unite
    Posts
    9,918

    Re: LM MPScan Fail

    No, you do.



    Was the engine running when you tried to connect?Or just key-on?



    I beleive the LM and T2 SMEC (probably '88 T1 SMEC, too) start ending error codes out when you key on (everytime?). So, if the engine isn't running, you may need to wait a few seconds until the error code stream stops.
    https://db.tt/SV7ONZpQ
    Rob Lloyd
    '89 Daytona C/S

    2.5 T1 Auto
    13.24 @ 100.5mph
    NHRA #3728 AF/S

    boostbutton.com
    tuning wiki

  11. #11
    Boost, it's what's for dinner... Turbo Mopar Staff Aries_Turbo's Avatar
    Join Date
    Dec 2005
    Location
    Warsaw, NY
    Posts
    8,838

    Re: LM MPScan Fail

    Quote Originally Posted by ShelGame View Post
    No, you do.



    Was the engine running when you tried to connect?Or just key-on?



    I beleive the LM and T2 SMEC (probably '88 T1 SMEC, too) start ending error codes out when you key on (everytime?). So, if the engine isn't running, you may need to wait a few seconds until the error code stream stops.
    Gotcha. OK I'll do that when I get home. Oops.

    is it if it's connected directly to the lm mcu I don't have to invert? My old ttl to serial setup is soldered to the processor of my lm. But my serial to usb adapter doesn't like the odd baud rate.

    I think I tried it both running and key on.

    Quote Originally Posted by turbovanman
    This one is easy, I have myself to blame, I rush things, don't pay attention to gauges when I should, change to much stuff at once then expect miracles, the list is endless.

  12. #12
    Boost, it's what's for dinner... Turbo Mopar Staff Aries_Turbo's Avatar
    Join Date
    Dec 2005
    Location
    Warsaw, NY
    Posts
    8,838

    Re: LM MPScan Fail

    Quote Originally Posted by ShelGame View Post
    No, you do.
    I should have known that I had to invert.... I looked at your board and was like "unless rob is doing some weird pull up/pull down resistor/diode deal, there are no where near enough components on this board to invert these signals.

    Thanks.

    Brian

    Quote Originally Posted by turbovanman
    This one is easy, I have myself to blame, I rush things, don't pay attention to gauges when I should, change to much stuff at once then expect miracles, the list is endless.

  13. #13
    Visit www.boostbutton.com... Turbo Mopar Contributor ShelGame's Avatar
    Join Date
    Dec 2005
    Location
    Whitmore Lake, Michigan, Unite
    Posts
    9,918

    Re: LM MPScan Fail

    Quote Originally Posted by Aries_Turbo View Post
    I should have known that I had to invert.... I looked at your board and was like "unless rob is doing some weird pull up/pull down resistor/diode deal, there are no where near enough components on this board to invert these signals.

    Thanks.

    Brian
    Yeah, its one if the main reasons to use the FTDI chip - you can invert Rx and Tx in software...
    https://db.tt/SV7ONZpQ
    Rob Lloyd
    '89 Daytona C/S

    2.5 T1 Auto
    13.24 @ 100.5mph
    NHRA #3728 AF/S

    boostbutton.com
    tuning wiki

  14. #14
    Boost, it's what's for dinner... Turbo Mopar Staff Aries_Turbo's Avatar
    Join Date
    Dec 2005
    Location
    Warsaw, NY
    Posts
    8,838

    Re: LM MPScan Fail

    ok, i inverted the tx and rx. i didnt do the thing that can reduce latency yet though.

    started the car.

    connected mpscan and hit record. it was showing rpm as ~500rpms which seems low. map was jumping around all over the place as was knock volts and knock retards for each cyl were going all over the place as well.

    coolant temp was pretty steady but would jump around at times. it was raising steadily and i dont have a fan on the rad right now so i shut it off.

    then i tried to reconnect and it wouldnt connect. tried restarting the car and then reconnecting and it wouldnt connect.

    i didnt try to unplug usb or restart mpscan as the car was getting hot.

    when i was done with the first log, i hit stop and shut down the program... i was thinking that hitting stop would save the log but i guess im wrong as i cant find the log anywhere and when try to have mpscan open the log it has nothing in the default directory.

    im thinking this program should auto save the logs as it creates them. or at least auto save on exit or upon stopping the logging..... unless i did something wrong.

    ill try tomorrow or the next day. making some shrouding for my rad fan right now so i can install it.

    Brian

    Quote Originally Posted by turbovanman
    This one is easy, I have myself to blame, I rush things, don't pay attention to gauges when I should, change to much stuff at once then expect miracles, the list is endless.

  15. #15
    Supporting Member Turbo Mopar Contributor
    Join Date
    Jun 2006
    Location
    Spearfish SD
    Posts
    2,038

    Re: LM MPScan Fail

    I'll look at that option when I get back into town. It's Sturgis rally 75 th so I went on vacation for the week! !

    - - - Updated - - -

    Post the log file again
    89 Voyager LE, 2.5T2 - rest in peace
    87 Charger Shelby T2 (2.4 conversion in process)

  16. #16
    Boost, it's what's for dinner... Turbo Mopar Staff Aries_Turbo's Avatar
    Join Date
    Dec 2005
    Location
    Warsaw, NY
    Posts
    8,838

    Re: LM MPScan Fail

    I'll try again tonight and post fresh logs too.

    The current log shows some fails which may help.

    Quote Originally Posted by turbovanman
    This one is easy, I have myself to blame, I rush things, don't pay attention to gauges when I should, change to much stuff at once then expect miracles, the list is endless.

  17. #17

    Re: LM MPScan Fail

    Same issue I was having. Tried to use the Android software with a bridge/mate for the USB FTDI cable to a micro USB cable, still no dice.

    I cannot find the file you've mentioned in the Roaming path, but here are the details of the other. Also attaching the error I received when trying to connect. I would definitely like help on this. I ordered the cable from Rob and will be testing this on the Lancer. If it works on the Lancer, then I will assume there is something either with the Ostrich or my wiring of the FTDI cable as to why it won't connect. I may also pull the FTDI cable off the GLHS and compare it to the one I will be getting this week.

    ftdi_error.txt

    trying to open port COM15 - ctlrecord_click
    got a good port back - ctlrecord_click
    try to open port COM15 -initport
    COM15 is a legit port -initport
    usb is available on COM15 -initport
    usb ftdi serial number AEYWRHTI is available - initport
    setting port baud rate to 976
    ftdi open successful on COM15 -usbportinit
    using protocol LM
    attempt to change ecu baud rate to 7812
    Sending byte 18
    Received byte 1
    Sending byte 18
    Received byte 0
    Changing mpscan baud rate to 7812
    Sending byte 18
    Received byte 128
    Sending byte 18
    Received byte 128
    Sending byte 18
    Received byte 128
    Sending byte 18
    Received byte 128
    usbsethibaud failed - usbportinit
    ftdi open unsuccessful - usbportinit
    Sending byte 254
    Received byte 0
    Sending byte 254
    Received byte 128
    can't open ftdi port - usbportinit
    Unable to open/setup port. - ctlrecord_click
    [SIZE="3"] [B]Jon Trotter[/B][/SIZE] [B]1985[/B] Dodge Shelby Charger, Currently decommissioned [B]1987[/B] Shelby GLHS, #937 [B]1987[/B] Shelby Lancer, #628 [QUOTE=Reeves;587010]I can be ready. Please send pics of wife. _____DodgeZ add comments here______[/QUOTE]

  18. #18
    Boost, it's what's for dinner... Turbo Mopar Staff Aries_Turbo's Avatar
    Join Date
    Dec 2005
    Location
    Warsaw, NY
    Posts
    8,838

    Re: LM MPScan Fail

    ok. i tried again tonight. last night before bed, i lowered the latency to the minimum (1ms)

    i always stared the car and then the program and it worked every time.

    i always saved the log files this time lol.

    when it connected the 1st and the 2nd time, i copied the connection log files.

    im not logging a ton of stuff either. i still dont have the cooling fan hooked up so i didnt run it that long.

    im still getting crazy data that doesnt make sense and that my otc scanner doesnt get when logging.

    i also noticed another weird phenomenon.... if im logging, the rpm is lower and the car is sometimes leaner. when i hit "stop" to stop the logging, the afr gets richer and the rpm rises and then drops back down.

    here are my files for tonights test.

    https://www.dropbox.com/s/rx615ppgws...klogs.zip?dl=0

    Brian

    Quote Originally Posted by turbovanman
    This one is easy, I have myself to blame, I rush things, don't pay attention to gauges when I should, change to much stuff at once then expect miracles, the list is endless.

  19. #19
    Visit www.boostbutton.com... Turbo Mopar Contributor ShelGame's Avatar
    Join Date
    Dec 2005
    Location
    Whitmore Lake, Michigan, Unite
    Posts
    9,918

    Re: LM MPScan Fail

    Quote Originally Posted by Aries_Turbo View Post
    ok. i tried again tonight. last night before bed, i lowered the latency to the minimum (1ms)

    i always stared the car and then the program and it worked every time.

    i always saved the log files this time lol.

    when it connected the 1st and the 2nd time, i copied the connection log files.

    im not logging a ton of stuff either. i still dont have the cooling fan hooked up so i didnt run it that long.

    im still getting crazy data that doesnt make sense and that my otc scanner doesnt get when logging.

    i also noticed another weird phenomenon.... if im logging, the rpm is lower and the car is sometimes leaner. when i hit "stop" to stop the logging, the afr gets richer and the rpm rises and then drops back down.

    here are my files for tonights test.

    https://www.dropbox.com/s/rx615ppgws...klogs.zip?dl=0

    Brian
    What binary file are you using? Sounds like the RAM locations are wrong.
    https://db.tt/SV7ONZpQ
    Rob Lloyd
    '89 Daytona C/S

    2.5 T1 Auto
    13.24 @ 100.5mph
    NHRA #3728 AF/S

    boostbutton.com
    tuning wiki

  20. #20
    boostaholic
    Join Date
    Nov 2006
    Location
    Rochester, New York, United St
    Posts
    1,148

    Re: LM MPScan Fail

    Quote Originally Posted by Aries_Turbo View Post
    im still getting crazy data that doesnt make sense and that my otc scanner doesnt get when logging.

    i also noticed another weird phenomenon.... if im logging, the rpm is lower and the car is sometimes leaner. when i hit "stop" to stop the logging, the afr gets richer and the rpm rises and then drops back down.
    I noticed that on my car as well. It's like every 10th sample is bad or something.

    Same with the idle and AFR. If I unplug the computer or just stop logging the idle with jump up about 500rpm and take a few seconds to settle down.

Page 1 of 3 123 LastLast

Similar Threads

  1. MPScan
    By wowzer in forum EFI Tuning
    Replies: 572
    Last Post: 11-14-2023, 09:56 PM
  2. MPScan RPM
    By wheming in forum EFI Tuning
    Replies: 9
    Last Post: 08-25-2015, 09:07 PM
  3. What to log-MPScan
    By 22shelby in forum EFI Tuning
    Replies: 1
    Last Post: 06-02-2013, 08:08 AM
  4. MPScan and USB to SCI cable
    By 88lebaron1 in forum EFI Tuning
    Replies: 7
    Last Post: 03-18-2013, 10:19 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •