CSR (Windows 10 or Linux): "Failed to start Ganglion BLE..." / "Code 412 Error: TypeError..."

edited July 2018 in Ganglion
1. connect USB dongle
2. Win10 installs driver automatically (BTHUSB) - you can turn bluetooth on/off now and search for devices, but in the GUI you get "Failed to start Ganglion BLE Driver"
3. use zadig to install WinUSB driver

Problem:

Device is now listed under "USB devices" in the "device manager". Under devices there is no more option to turn on/off bluetooth. Therefore you cannot follow the following instructions.

Make sure your computer’s Bluetooth feature is turned on. Select LIVE (from Ganglion) from the first drop down
http://docs.openbci.com/Tutorials/02-Ganglion_Getting Started_Guide#ganglion-getting-started-guide-start-using-the-openbci-gui-connect-the-gui-to-your-ganglion-board

Error messages remains: "Failed to start Ganglion BLE Driver"
«1

Comments

  • Also tried:

    http://openbci.com/forum/index.php?p=/discussion/comment/8275/#Comment_8275

    a.) using different USB ports

    b) restarting

    1. close gui
    2. close hub
    3. deactivate csr8510
    4. activate again
    5. start hub 
    6. start gui

    same error
  • Also tried installing CSR Harmony Wireless Software Stack the and b) and zadig +b) 

    no luck
  • QozQoz UCSD
    I'm having the EXACT same problem as you. I've tried just about everything and I can't solve this. I'm continuing a project on the Ganglion that I successfully conducted a few months ago before reformatting my harddrive, which is frustrating.
    image
    image


  • I will try to get it running on secondary linux machine IMO. yeah, frustrating
  • QozQoz UCSD
    My system dual boots into Ubuntu 16.04 and I couldn't get it running on there either, so I wish you the best of luck.
  • wjcroftwjcroft Mount Shasta, CA
    Mentioning AJ @pushtheworld, Joel @biomurph, @Conor, and @openbci.

    AJ gave me some flak for saying this before... So I'm hesitant to mention this. But the latest GUI / Hub supports the BLED112 dongle. This particular dongle is what Jarek uses with BioEra. And Jarek never even considered the complexities of the CSR dongle / Zadig approach. It might be that the BLED112 dongle offers more stability and ease of setup, without requiring any unusual driver installations -- since it represents itself as a serial port.

    AJ's objection is that we need to continue to promote the CSR / Zadig solution because it has the most history and number of users. And is being sold in the OpenBCI store. However there IS a sub community of users that have had considerable difficulty with the CSR dongle. It might be appropriate to encourage those users to try the BLED112.

    Regards,

    William

  • edited May 2018
    [original thread titled: "Failed to start Ganglion BLE driver"]

    Running Ganglion board with Surface Pro 4 running Windows 10. Bought a BLE adapter from local store, installed ZaDig as instructed and installed driver. Downloaded OpenBCI hub and GUI, extracted files to Program Files, ran as administrator aaaand nothing. I get error message "Failed to Start Ganglion BLE driver". Ran Ganglion board on wife's Macbook Pro with zero issues. Detection of board was quick and painless. What am I doing wrong here? Are there extra drivers I need to install? 

    This whole product/project is amazing and I've collected some really cool data so far; I'd just like to do it on my own computer without stealing the missus' poot poot.

    Thanks for the help!
  • William,

    I will plan to add BLED112 windows/linux dongle support when i get back into town next week. Seems there a number of people who want it :)

    Thanks for driving feedback!

    AJ

  • wjcroftwjcroft Mount Shasta, CA
    AJ, thanks.

    I also merged the other thread from @colloquialoatmeal, into this existing thread. It seems in this thread alone we have now have three users struggling with the CSR / Zadig dongle approach.

    The "Failed to start Ganglion BLE driver" message seems to be showing up more.

    Regards,

    William

  • I ordered a dongle with the CSR chip and should have it soon. I will report back when I get it.
  • QozQoz UCSD
    As an update, I did manage to get everything working.

    First, I reinstalled the CSR Harmony Drivers from a CD (luckily I found it lying around my lab since there doesn't seem to be anything available online).

    Then, I went into 'services.msc' via 'run' and right clicked anything with Bluetooth infront of it and clicked start:
    imageimageimage

    Then, I use zadig to reinstall the WinUSB drivers:
    image

    Then, I turn on my Ganglion.

    Then, I open up OpenBCI Hub (version 1.3.9) as an admin

    Then, I launch Processing as an admin and load up my OpenBCI GUI sketch (version 3.3.1)

    And finally after hours of debugging, my Ganglion is detected:
    imageimage

    Not sure if this works on the latest version of the hub. Hope this helps.

  • Hi I'm still struggling with the same (or a very similar) problem.

    I finally got the CSR Harmony Software and reinstalled it first.
    I reinstalled the WinUSB driver via Zadig, as explained.

    I reinstalled again OpenBCI_GUI, version 3.3.1.
    And reinstalled OpenBCIHub, v1.4.2 (which is said to be the one to used with the GUI v3.3.1 ).
    (I also tried with the OpenBCIHub version that comes with the GUI v3.3.1 , but the result was the same : dont work.)

    I plugged the CSR 4.0 dongle into a USB 2.0 port.
    Opened OpenBCIHub as administrator.
    Turned on the OpenBCI board (the LED was blinking. ).
    Opened OpenBCI_GUI as administrator.
    And again: NOTHING was found in BLE Devices.

    Here are some questions :
    [ more specifically @ Qoz in response to the post above]: 
    Thank you for your "debug tutorial" above, but I have two questions on what you have done:

    1)   I went into 'services.msc'.  I see that the following services are properly running: 
    "CSR OBEX
    Service"
    Service Bluetooth
    CSR
    Service audio Bluetooth CSR 
    Service Bluetooth Switcher

    I also see
    "Bluetooth driver management",  but when I start it, a message tells me that the
    processus starts and immediately closes. 
    Don't know if it is normal or if it could be related.
    So, please can you remember please if this process was starting in your case, or if you started any other services (than the ones I mentionned above) ?

    2) you said  "Then, I launch Processing as an admin and load up my OpenBCI GUI sketch (version 3.3.1),  And finally after hours of debugging, my Ganglion is detected."

    I know nothing about "Processing", but
    it seems like you debugged a program (i.e. a "sketch") in
    "processing".   How is it
    possible to call OpenBCI_GUI  from a program.  Do you know a link where it is explained ?

    Maybe I could try to do the same, but with python. Don"t know if it is possible.

    Anyways, thank you very much to anybody for any kind of help or even any response .
  • Hi @FGL you should be able to run the standalone application.

    This is really strange that you are not finding any devices! I wish this was not the case.

    The steps you took should be able to work fine.

    Did you hit start scan a couple times? Is your ganglion flashing with a blue light?

    Thanks,

    AJ
  • Hi guys, 

    I have tried almost every solution mentioned above for past 48 hours. It has been frustrating an exasperating.
    Nothing has worked.
    I have new Lenovo ideapad 320 with Windows 10 system.
    I have got CSR dongle from openBCI. It came with the CD, from which I installed the CSR harmony software. When installed, I see the dongle as a USB , and it can also detect the ganglion board, through the Bluetooth app. But it does not connect. 
    As soon as install the driver through Zadig, I stopped seeing CSR as Bluetooth device at all .It shows as USB device.
    In either cases, installing or not-installing Zadig driver, finally the GUI gives the same error- Failed to start ganglion BLE driver. 

    Please provide me with some solution that may work.

    Thanks, 

    Kiran
  • I'm in the same boat, after quite a bit of troubleshooting, following the various forum threads:  Failed to start ganglion BLE driver.
  • wjcroftwjcroft Mount Shasta, CA
    edited June 2018
    AJ @pushtheworld, any thoughts on the "Failed to start ganglion BLE driver" messages that several users are seeing? Is it possible that Microsoft installed some kind of OTA update to Windows 10 that is causing incompatibility with Zadig or some other element of the driver chain?

    On May 29 in this thread (above) you mentioned, "I will plan to add BLED112 windows/linux dongle support when i get back into town next week. Seems there a number of people who want it :)". Do you feel BLED112 support is stabile enough to recommend now? It might offer some hope to these users encountering the Failed message.

    Also mentioning @openbci and @biomurph

    Regards,

    William

  • biomurphbiomurph Brooklyn, NY
    @pushtheworld didn't you get the BLED112 working? Can you replicate the issue?
  • QozQoz UCSD
    What versions of the OpenBCI GUI and Hub are people using? I was never able to get things working on the latest version of the Hub and used an older one, and have been using the May 2018 version of the GUI to acquire data using the CSR that came with my Ganglion.
  • edited June 2018
    I'm working on a new hub version that uses the built in bluetooth hardware, is there anyone here that can use this? I need testers!
  • As in, use the built in Bluetooth hardware in Windows? I am running Windows 10 and could definitely use this! How would I test it?

  • wjcroftwjcroft Mount Shasta, CA
    AJ, that sounds cool. At the same time, I thought one rational for using a bluetooth dongle on Windows, was that the PC (Windows and Linux) built-in hardware base was so variable (so many different BLE chips and drivers) -- that a single solution would be unlikely. Even on Mac, I understand that there are a certain (very few) models that cannot use the built-in BLE chip. Which is why you wrote the BLED112 support (?)

    Also (as Larry Janow pointed out to us), there are still Windows 7 users, especially in larger corporate, educational environments. Window 7 machines are much less likely to have BLE hardware, and have no OS support for BLE at all.

    So the BLED112 dongle does indeed look like more of a universal solution, if it is reliable.

    Regards, William

  • @pushthworld. I will be happy to try anything. I also got a BLED112 dongle. But still not resolved the issue. I am using windows 10, 64bit system.

    Thanks, 

    Kiran
  • I keep getting this error- 

    "Code 412 Error: TypeError : Cannot read property 'state' of undefined"

    Is anyone else having same problem?

    KD
  • kirandivakar when I try to connect the ganglion via CSR 4.0 dongle to a computer running Windows 10. 

    I get the same exact error: "Code 412 Error: TypeError : Cannot read property 'state' of undefined"

    I tried on two separate windows PCs and had the issue.

    The board connects just fine with a mac using built in BLE.
  • wjcroftwjcroft Mount Shasta, CA
    I just logged this on the Hub issues page. Feel free to add or elaborate on your own circumstances.


  • @Matt16 and @kirandivakar which version of the Hub are you running?

    Does running an older hub and GUI version solve the problem?

    Thanks!

  • @pushtheworld Which older version I should try? 

    Kiran
  • wjcroftwjcroft Mount Shasta, CA
    See above posts in thread, @Qoz knows what Hub version worked for him. You could PM him.

  • Ok. I tried 3.0.1. That worked, in the sense that Ganglion device appears in search. But is unable to connect. It says comport error??


  • QozQoz UCSD
    I used versions 1.3.9 of the Hub and 3.3.1 of the GUI. If somebody could find a link for this older Hub that would be wonderful; I couldn’t find one myself, just luckily had an old version on a hard drive.

    Might also be worth compiling the GUI yourself in Processing. I do this since I had problems with certain features with the provided binary which were resolved when I compiled it myself.

    Good luck to everyone. I spent weeks debugging so I know how frustrating it can be. I hope this problem is resolved for everybody shortly.
Sign In or Register to comment.