Results 1 to 7 of 7

Thread: Can't connect to RR fix

  1. #1
    Lifetime Member
    Join Date
    Oct 2005
    Posts
    551

    Default Can't connect to RR fix

    Posting for future reference...because by next week I will have forgotten.

    When I tried to connect I got the RR USB device not found message. I could connect the FlashScan scanner to the RR and log. If I tried to flash through the FlashScan I got the bootloader rejected/PCM locked message.

    Seemed like an issue with the RR and FlashScan drivers. I tried uninstalling/reinstalling all USB devices and even tried installing the RR before FlashScan as suggested on here with no effect on the problem.

    I wondered if there was a conflict with the USB/Serial adapter driver I had installed to connect to my LC1s for a firmware reflash, as the RR is also USB/Serial. I had issues getting that adapter to work as well. There were no ports showing in the Device Manager when the RR was connected.

    I used FTClean to clean any references to FTDI drivers off my system, connected the RR and specified the RR drivers for the reinstall, then connected the FlashScan and specified the EFILive drivers. Everything is back to functioning properly now. Will probably have to go through the same process if I ever need to use the USB/serial adapter again.

    So, if anyone has similar issues, ensure that you use FTClean before reinstalling your USB devices. Just following the update driver or uninstall/reinstall process may not work.
    2017 Camaro SS, 2014 Ram 2500 4x4 Cummins 6.7L, 2004 Chevy Avalanche Z71 4̶X̶4̶(now 2WD), 5870lb race weight, 10.93@ 124, Twin TVS1900s, Twin Throttle, 429 LSX, 4L80E, custom 14 bolt rear, V2, R̶o̶a̶d̶R̶u̶n̶n̶e̶r̶(dead), COS3......
    Gettin' the Groceries

  2. #2
    Lifetime Member mr.prick's Avatar
    Join Date
    Nov 2006
    Posts
    3,195

    Default

    Were you trying to flash through the DLC like a "standard" PCM?
    The bootloader rejected/PCM locked message will pop up if you try this.
    You can't flash the RR through the DLC it must be done directly via USB.

    Were you using a USB/Serial converter with the RR?
    If there was a problem with USB connection the error will be
    "No RoadRunner USB device can be found"
    512k RoadRunner Firmware 12.14R
    FlashScan V2 Bootblock V2.07.04 Firmware V2.07.22 EFILive V7.5.7 (Build 191) V8.2.1 (Build 181)
    LC-1 WBO2

    _________________________________________________

  3. #3
    Lifetime Member
    Join Date
    Jul 2007
    Posts
    376

    Default

    Quote Originally Posted by DrX View Post
    Posting for future reference...because by next week I will have forgotten.

    When I tried to connect I got the RR USB device not found message. I could connect the FlashScan scanner to the RR and log. If I tried to flash through the FlashScan I got the bootloader rejected/PCM locked message.

    Seemed like an issue with the RR and FlashScan drivers. I tried uninstalling/reinstalling all USB devices and even tried installing the RR before FlashScan as suggested on here with no effect on the problem.

    I wondered if there was a conflict with the USB/Serial adapter driver I had installed to connect to my LC1s for a firmware reflash, as the RR is also USB/Serial. I had issues getting that adapter to work as well. There were no ports showing in the Device Manager when the RR was connected.

    I used FTClean to clean any references to FTDI drivers off my system, connected the RR and specified the RR drivers for the reinstall, then connected the FlashScan and specified the EFILive drivers. Everything is back to functioning properly now. Will probably have to go through the same process if I ever need to use the USB/serial adapter again.

    So, if anyone has similar issues, ensure that you use FTClean before reinstalling your USB devices. Just following the update driver or uninstall/reinstall process may not work.
    Thanks for the info. I'm a RR user and a Moates programmer for other devices. Did you check to see if Window's FTDI Driver was in VCP or Native(Virtual Com Port) mode and that the EFI Software settings matched?

    If you look in the windows device manager, look for something like the following:

    The following is an example of another MOATES (RR LIKE) FTDI based DEVICE in VCP Mode: . If your not in VCP mode, the driver is NATIVE (using ftd2xx.dll) and windows will only see a connection under Universal Serial Bus Controllers otherwise will look like this:

    GENERIC_DEVICE 1.2.Q FT232R USB UART A2002lgT 04036001 02D177C1
    Ports (Com & LPT)
    Caption: USB Serial Port (COM8)
    DeviceID: FTDIBUS\VID_0403+PID_6001+A2002LGTA\0000
    Manufacturer: FTDI
    Name: USB Serial Port (COM8)
    Service: FTSER2K
    ClassGUID: {4D36E978-E325-11CE-BFC1-08002BE10318}
    Status: OK

    Universal Serial Bus Controllers
    Caption: USB Serial Port (COM8)
    DeviceID: FTDIBUS\VID_0403+PID_6001+A2002LGTA\0000
    Manufacturer: FTDI
    Name: USB Serial Port (COM8)
    Service: FTSER2K
    ClassGUID: {4D36E978-E325-11CE-BFC1-08002BE10318}
    Status: OK
    07 Silverado DMax Classic
    02 Z06 LS3 416, 805rwhp, TFS245, Wiseco, Callies Crank/Rods, Iskendarian Lifters, Crower Rockers, FAST102/90, ATI Damper, 1-7/8 Kook's LT, QkTime Shield,Tolle-Fab 8pt
    Old Engine: 1/4mile = 9.6/146 New Engine:?

    EFI Live Tune/Scan v7.5.27, EFI Live Scan and Tune v8.2.23, build 276, BootBlock 2.07.06, FirmWare 2.07.52, 512K RoadRunner (12.14.R), Innovate Serial LC2x2


    COS5/12212156 For 2002 Z06 Manual Vette

  4. #4
    Lifetime Member
    Join Date
    Oct 2005
    Posts
    551

    Default

    Quote Originally Posted by mr.prick View Post
    Were you trying to flash through the DLC like a "standard" PCM?
    The bootloader rejected/PCM locked message will pop up if you try this.
    You can't flash the RR through the DLC it must be done directly via USB.
    That is likely correct, just thought I would give it a try.

    Quote Originally Posted by mr.prick View Post
    Were you using a USB/Serial converter with the RR?
    If there was a problem with USB connection the error will be
    "No RoadRunner USB device can be found" .
    The RR was showing up as a USB/serial converter in the device manager. I had reccently installed a separate USB/serial converter to flash the LC1's, one of which has gone bonkers again today. The converter was not connected concurrently with the RR.
    2017 Camaro SS, 2014 Ram 2500 4x4 Cummins 6.7L, 2004 Chevy Avalanche Z71 4̶X̶4̶(now 2WD), 5870lb race weight, 10.93@ 124, Twin TVS1900s, Twin Throttle, 429 LSX, 4L80E, custom 14 bolt rear, V2, R̶o̶a̶d̶R̶u̶n̶n̶e̶r̶(dead), COS3......
    Gettin' the Groceries

  5. #5
    Lifetime Member
    Join Date
    Oct 2005
    Posts
    551

    Default

    Quote Originally Posted by TFZ_Z06 View Post
    Thanks for the info. I'm a RR user and a Moates programmer for other devices. Did you check to see if Window's FTDI Driver was in VCP or Native(Virtual Com Port) mode and that the EFI Software settings matched?

    If you look in the windows device manager, look for something like the following:

    The following is an example of another MOATES (RR LIKE) FTDI based DEVICE in VCP Mode: . If your not in VCP mode, the driver is NATIVE (using ftd2xx.dll) and windows will only see a connection under Universal Serial Bus Controllers otherwise will look like this:

    GENERIC_DEVICE 1.2.Q FT232R USB UART A2002lgT 04036001 02D177C1
    Ports (Com & LPT)
    Caption: USB Serial Port (COM8)
    DeviceID: FTDIBUS\VID_0403+PID_6001+A2002LGTA\0000
    Manufacturer: FTDI
    Name: USB Serial Port (COM8)
    Service: FTSER2K
    ClassGUID: {4D36E978-E325-11CE-BFC1-08002BE10318}
    Status: OK

    Universal Serial Bus Controllers
    Caption: USB Serial Port (COM8)
    DeviceID: FTDIBUS\VID_0403+PID_6001+A2002LGTA\0000
    Manufacturer: FTDI
    Name: USB Serial Port (COM8)
    Service: FTSER2K
    ClassGUID: {4D36E978-E325-11CE-BFC1-08002BE10318}
    Status: OK
    There was no "Ports" heading in the Device tree when the RR was connected. Now there is.

    There was a "Ports" heading when I connected the USB/serial adapter that I used with the LC1's.
    2017 Camaro SS, 2014 Ram 2500 4x4 Cummins 6.7L, 2004 Chevy Avalanche Z71 4̶X̶4̶(now 2WD), 5870lb race weight, 10.93@ 124, Twin TVS1900s, Twin Throttle, 429 LSX, 4L80E, custom 14 bolt rear, V2, R̶o̶a̶d̶R̶u̶n̶n̶e̶r̶(dead), COS3......
    Gettin' the Groceries

  6. #6
    Lifetime Member
    Join Date
    Jul 2007
    Posts
    376

    Default

    Quote Originally Posted by DrX View Post
    There was no "Ports" heading in the Device tree when the RR was connected. Now there is.

    There was a "Ports" heading when I connected the USB/serial adapter that I used with the LC1's.
    You may only need to check the VCP Box if a different port number was assigned.

    My Computer->View System Information->Hardware->Device Manager->
    Universal Serial Bus Controllers->Right click properties on device->Advanced->
    Check VCP Box.


    07 Silverado DMax Classic
    02 Z06 LS3 416, 805rwhp, TFS245, Wiseco, Callies Crank/Rods, Iskendarian Lifters, Crower Rockers, FAST102/90, ATI Damper, 1-7/8 Kook's LT, QkTime Shield,Tolle-Fab 8pt
    Old Engine: 1/4mile = 9.6/146 New Engine:?

    EFI Live Tune/Scan v7.5.27, EFI Live Scan and Tune v8.2.23, build 276, BootBlock 2.07.06, FirmWare 2.07.52, 512K RoadRunner (12.14.R), Innovate Serial LC2x2


    COS5/12212156 For 2002 Z06 Manual Vette

  7. #7
    Lifetime Member
    Join Date
    Oct 2005
    Posts
    551

    Default

    Quote Originally Posted by TFZ_Z06 View Post
    You may only need to check the VCP Box if a different port number was assigned.

    My Computer->View System Information->Hardware->Device Manager->
    Universal Serial Bus Controllers->Right click properties on device->Advanced->
    Check VCP Box.
    No port was assigned. I will keep that in mind.
    2017 Camaro SS, 2014 Ram 2500 4x4 Cummins 6.7L, 2004 Chevy Avalanche Z71 4̶X̶4̶(now 2WD), 5870lb race weight, 10.93@ 124, Twin TVS1900s, Twin Throttle, 429 LSX, 4L80E, custom 14 bolt rear, V2, R̶o̶a̶d̶R̶u̶n̶n̶e̶r̶(dead), COS3......
    Gettin' the Groceries

Similar Threads

  1. can not connect
    By Jetmech in forum General (Diesel)
    Replies: 10
    Last Post: November 29th, 2010, 08:31 AM
  2. Help please trying to connect
    By 5.7senator in forum EFILive V4
    Replies: 2
    Last Post: November 21st, 2009, 10:02 AM
  3. V1 won't connect
    By chrisr in forum FlashScan V1
    Replies: 3
    Last Post: August 24th, 2008, 11:08 PM
  4. cant connect
    By mickkk in forum Duramax LLY
    Replies: 9
    Last Post: December 21st, 2006, 09:40 AM
  5. HELP: Can't Connect
    By tdzee in forum Tips and tricks
    Replies: 7
    Last Post: May 26th, 2005, 12:40 PM

Posting Permissions

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