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

2»

Comments

  • Ok. Final update. I installed older version. 3.0.1 stand-alone application on 64bit Windows 10 system on Lenovo Ideapad360. Used CSR dongle ordered from open BCI. Installed it with the CD that came with it. Used Zadig. Restarted the system with dongle in place. It installed windows update. It is working well now.

    Here are my observations.
    1) when you plug in CSR dongle, even without the installation with software, it does show as blue tooth device, but it seems that system has no access to it. So when you install the software, windows starts showing it as an independent blue tooth devise and you can inspect its com port and hardware configuration etc. You can also check if it 'sees' the ganglion. It sees, but it cannot connect, because there is no way to return the code from ganglion devise, as happens with other blue tooth devices. 

    2) Now when you change the driver with Zadig, you no more see the system recognizing it as blue tooth device and you cannot access its details. But i think  that first software installation is necessary for comport. Because when i tried without it , the GUI could see the ganglion but could not connect and gave comport error.

    3) After that you have to reboot the system which then runs windows update. I think at this time, the system recognizes the driver and adjusts the com port. 

    Thereafter it has been working fine, so far. I think the key change was using earlier version of HUB (3.0.1 which shows the cat icon in the system tray.)

    I hope this helps, 

    Thanks everyone for your support and feedback.

    KD
  • edited July 2018
    We eventually got it working by using the following:

    • an older version of OpenBCI GUI without the hub. We were using 3.3.2, but now we are using 2.2.1
    • We also gave the app administrator privileges and "run as administrator"
    • zadig 2.2
    • libusb-win32
    Thanks for the help everyone.
  • Hi everyone!

    As @wjcroft suggested, I gave the BLED112 a shot on windows!

    You
    can download the new alpha of the GUI v3.4.0-alpha.1 that comes with
    Hub v1.4.5 which has support for windows over hub. I was able to test on
    two windows machines running windows 10. Please let me know if you have
    any troubles!

    https://github.com/OpenBCI/OpenBCI_GUI/releases/tag/v3.4.0-alpha.1
  • Thanks for posting the alpha; I was just about to comment that I still could not get the Ganglion to interface with my Windows 10 computer and it worked! However, when I selected CSR BLE it found it... This makes me very puzzled as the prior versions would refuse to find the board via CSR saying that the drivers were not installed and giving me the same 412 error. What happened in this new version? Again, not connecting via BLED, but rather an official CSR dongle.
  • squadussquadus Los Angeles
    You will need to use an older alpha of the GUI. I got it working without the BLED and using the CSR instead. Cheers!
  • alirazaaliraza Islamabad
    edited September 2018
    Let me give the solution that worked for me and my friends ganglion devices. We simply installed electron hub version 1.3.2 and latest BCI GUI and it worked like a charm.  (Don't forget to say thanks)
  • Radha_openbciRadha_openbci United Kingdom
    Link for older versions:


    shifitng to an older version of bcihub 1.3.9 resolved my problems of ganglion not seen on open bci.

Sign In or Register to comment.