Shop OBEX P1 Docs P2 Docs Learn Events
ELEV-8 v3 driver issue in Windows7 ? — Parallax Forums

ELEV-8 v3 driver issue in Windows7 ?

balbarobalbaro Posts: 10
edited 2016-04-27 16:12 in General Discussion
I'm using Windows7 32bit , i installed SimpleIDE as mentioned in the assembly guide.
But my OS does not recognize the flight board , i get a "Flight Controller A3" in the popup and then "USB serial converter"
in the device list but no virtual com port is created.
Tried installing the Parallax USB drivers with no difference ?
I'm i missing something ?



My apologies if this is posted in a wrong section.

Comments

  • VonSzarvasVonSzarvas Posts: 3,450
    edited 2015-12-26 10:01
    You seem to have done everything correctly!

    Some ideas...

    Do you have admin rights to install the com port?

    The Flight Controller A3 popup indicates windows has detected a rev A3 Board ok. Seems something has failed after that.

    Reboot needed?

    You could also try the ftdi utility to clean up your com ports. Cdmuninstaller I believe they call it. Or, try with an older ftdi driver, such as this one:
    CDM 202.08.28 WHQL
    Find it in the ftdi drivers archive at the ftdi homepage.

    Does any of that help?
  • @balbaro,

    Have you had any luck with this? Can you try another computer? I run Windows 7 fine, but it's 64 bit. You can uninstall the drivers, and install fresh ones. Also, there have been some problems reported with using USB 3.0 ports. Try all the USB ports you have.
  • balbarobalbaro Posts: 10
    edited 2015-12-27 06:25
    Thanks Publison and VonSzarvas.

    Well, i tried 2 other computers with a fresh OS installation Windows7 64 bit and a windows10 64bit, exactly the same symptons.
    Uninstalled with CDMUninstaller and reinstalled various CDM driver versions several times.

    What is strange is once i have connected and disconnected the flight board the OS doesent recognize my Eddie board anymore seems i have to uninstall and reinstall the CDM driver.
    Could there be something wrong with my flight board ?

    This is with a fresh install of Windows10 64bit.
    SimpleIDE is installed with drivers.

    After driver uninstallation

    20kx3ba.jpg

    After any version of CDM driver installation

    2ikwju9.jpg

    I'm using a USB2.0 port.

    PS cannot seem to find version 202.08 anymore do.The oldest i could find is 208.30 on the ftdi download page.1
  • balbarobalbaro Posts: 10
    edited 2015-12-27 07:13
    Gush, i'm really starting to believe there is something wrong with that flight board.

    On my windows7 32 bit

    I uninstalled all devices with a hardware ID of 403, this are all the devices wich uses the ftdi drivers.

    I then installed the latest ftdi driver CDM v2.10.00 WHQL Certified
    I installed and connected succesfully a Parallax Education board.
    I installed and connected sucessfully my Eddie control board.
    I installed and connected succesfully a Xbee USB stick, wich also uses the ftdi drivers.
    I failed to connect the Flight board same symptons, USB serial converter and no virtual com port.
  • VonSzarvasVonSzarvas Posts: 3,450
    edited 2015-12-27 07:43
    Before we get too deep, some other simple ideas to check...

    - Make sure you plug directly to the computer (ie. NOT into a HUB, and not using an USB extension cable)

    - Is your USB cable capable of powering higher current devices. Try another cable- perhaps a good quality one from a tablet or mobile phone.

    - Is your PC overloaded. To test, try unplugging some other USB stuff.


  • Oh, boy, that does look like a problem with the board itself. Have you tried it on a different computer system?
  • Michael - I regularly plug mine in through a hub AND a USB extension cable, and have no issues with either, or both together. It does sound like an issue with the board to me too.
  • VonSzarvasVonSzarvas Posts: 3,450
    edited 2015-12-27 20:35
    Those cable / hub tests are to exclude other factors from the equation in terms of diagnosing this issue, so would be useful to try. Yes, the right size cable and powered hub would normally be OK, but we don't know what the user has set-up.

    @balbaro

    As the Flight controller board name appears in Windows, but then fails to negotiate, it could still be a driver issue, or a couple of setup things...

    One is the Flight Controller might be transmitting to the PC during USB activation, stopping proper first-time negotiation. You can prevent this by ensuring the Flight Controller does NOT have external power connected when plugging into the USB port. Unplug that ELEV-8 battery!!

    Another is that the Max Bus Power request fails. Hence the idea first to ensure the cables are good, and also to unplug other USB devices which may be loading the USB bus.



    If all that fails to solve, then I will get a replacement board dispatched and the faulty one collected for diagnosis. Obviously that takes time, so I'd rather not delay getting your system working if we can find a solution by working through some steps.


  • VonSzarvasVonSzarvas Posts: 3,450
    edited 2015-12-27 08:44
    Before anything, I would uninstall any existing USB drivers, then download the latest version from here:

    http://www.ftdichip.com/Drivers/VCP.htm

    Currently: 2.12.10 WHQL Certified (Windows, 2015-11-23)


  • balbarobalbaro Posts: 10
    edited 2015-12-27 13:01
    Before anything, I would uninstall any existing USB drivers, then download the latest version from here:
    Currently: 2.12.10 WHQL Certified (Windows, 2015-11-23)

    Ok I used CDMUninstaller to remove the driver, reboot, install CDM v2.12.10 WHQL Certified reboot
    Did this twice, once with and once without Lipo connected.
    Cable is a 1 meter good quality, no hub.

    Port is USB 2.0 i have no USB 3.0 on this mini-itx card.

    The only other USB port used at the moment is my Keyboard/Mouse adapter.

    I received this dialog when scanning for devices in FT_Prog

    24qojlf.jpg






  • I will PM you about arranging a replacement
  • Just wanted to let know here that there is nothing wrong with this Flight Controller board.
    I must have misconnected something,dunno if its the ESC or the Radio RX, i reconnected everything and the board was recognized within 10 seconds.
  • @balbaro

    Thanks for following up! It's great to hear you've sorted things out, but I'm sorry about the troubles, and do let us know if you ever figure out what happened that lead to the connection issues.

    Cheers,
    -Kyle
Sign In or Register to comment.