Startup error in openBCI_GUI under Windows10

newdendritenewdendrite USA
edited January 2017 in OpenBCI_GUI
I'm trying to run openBCI_GUI under 64-bit Windows10 with the new Ganglion board.  On startup, this message appears:

A JavaScript error occurred in the main process
Uncaught Exception:
Error: LIBUSB_ERROR_NOT_SUPPORTED
  at Error(native)
  at Device.usb.Device.open(  ... followed by a list of files.

The FTDI drivers are installed.
The version of Java is current.
The CSR 4.0 dongle is being used, and this error occurs both when its driver (from the CD) is installed and when it is uninstalled.

I'm able to successfully run the GUI under Processing with this Ganglion board on a Mac/Sierra machine, but no success with Windows10, which is the OS which must run this Ganglion.

What next steps are suggested?

Thanks,
Michael



Comments

  • wjcroftwjcroft Mount Shasta, CA
    Michael, thanks.

    Mentioning @Conor and AJ Keller @pushtheworld. (Guys, who is the best contact for V2 GUI issues?) I don't have Windows 10 handy here at the moment. The fact that you succeeded with Mac says our hardware is working.

    Are you sure you need the BLE dongle, most newer Windows 10 laptops have BLE built in? TWO BLE devices on the same machine might confuse the OS.

    William


  • pushtheworldpushtheworld
    edited January 2017
    newdendrite

    As soon as the docs come back online (?) I will post a link to the tutorial you need to follow. 

    You need to download the zadig tool and install the WinUSB driver on your CSR 4.0 device.

    Follow this youtube video on how to use the zadig tool.

    All compatiable USB drivers can be found here: https://github.com/sandeepmistry/node-bluetooth-hci-socket#windows

  • newdendritenewdendrite USA
    @wjcroft

    I'm running on a 2-year-old Thinkpad T540p.  The LMP version for its native BT hardware shows BT 4.0 compatibility (LMP version 6.1280).  Device manager shows it working properly.

    I originally tested the openBCI_GUI without the BLE dongle, and it produced these same errors.

    Best regards,
    Michael
  • pushtheworldpushtheworld
    edited January 2017
    @newdendrite

    Since we are small team, 1 person, and are dependent on other's writing the low-level BLE drivers. Windows is a disaster when it comes to consistent hardware so we must ship the dongle in order to ensure compatibility. 

     I just wrote some instructions for you to get it working with the dongle:

    Best of luck!
  • newdendritenewdendrite USA
    @pushtheworld

    I can appreciate the challenges of being a team of of one -- so am I.  And I'm working with limited resources.  Solutions I've seen from openBCI such as buying a new computer are unrealistic.  IMHO, BT LTE is was not a good design decision.  It seems to have prevented the project from delivering its originally-advertised sample rates.  But we are all stuck with it now.

    I have experience with using the zadig tool for setting up amateur radio SDR applications under Windows, and frankly it has been a disaster there.  But I will give it a try.

    Thanks,
    Michael
  • pushtheworldpushtheworld
    edited January 2017
    @newdendrite ;

    "IMHO, BT LTE is was not a good design decision." It for sure has it's positive and negatives. The board only draws 15mA, which is pretty incredible for what the board is doing. 

    I have trouble on my Mac Book Air with BLE, can't figure out why.

    Using the zadig tool has been a pleasure for me, at least with the included CSR dongle.


  • newdendritenewdendrite USA
    I'm happy to report that the zadig driver install and the CSR dongle solved the Windows 10 issue.  OpenBCI_GUI is running smoothly.  Thanks for the excellent zadig instructions.

    I have no clue as to why the internal BLE hardware is non-functional on the Thinkpad.  BTW, the dongle and GUI continue to work regardless of whether Bluetooth is set ON or OFF in the settings screen.

    Not sure what your MacBook Air issues may be, but just for the record, everything seems to work well on the mid-2014 MacBookPro machine here.

    I'm looking forward to seeing what we can do with the Ganglion.

    Thanks again,
    Michael
  • pushtheworldpushtheworld
    @newdendrite I'm so pleased to hear zadig worked well for you too! Using it with the external Dongle seems to leave the internal driver alone which is nice. 

    I'm really not sure what the issue is with my MacBook Air, it just drops packets. I ran a virtual linux environment on my mac, and no dropped packets. I even ran a similar Macbook Air and there was no problem! I can connect, scan and disconnect, but I dropped packets like flies.

    I'm excited to see what you acomplish too!
Sign In or Register to comment.

© Vanilla Keystone Theme 2026