HC05 Bluetooth 2.0 driver for OpenBCI_GUI and Cyton + Daisy
trunidom
Switzerland
Hi all,
we build the openbci hardware for our self but without the WIFI_Shield.
Instead we decided to use the HC05 Bluetooth V2.0 board.
https://github.com/BigCorvus/OpenBCI_Bluetooth2adapter
Now the hardware is produced and we upload the firmware and bootloader to the PIC microcontroller.
We have connected the HC05 board to the computer via FTDI but the device is not visible in the OpenBCI_GUI. The COM port is visible, but it is not possible to recognize the bluetooth module.
We know the Bluetooth low energy part is made for RFD22301 (RFDuino) modul / dongle.
Do anybody of you have a driver or code extension for the OpenBCI_GUI???
Or do anybody know where and how to implement a Bluetooth driver for HC05 on the GUI?
Thank you very much and best regards
Dominique
Comments
Dominique, hi.
Rather than attempting to adapt the GUI to your specialized hardware, have you considered writing a small Python or C program to output LSL, LabStreamingLayer? This would allow your hardware to steam to all the various apps that support LSL, such as OpenViBE, Matlab, EEGLAB, NeuroPype, etc.
https://github.com/sccn/labstreaminglayer/wiki
You can control all the various features of the Cyton using the SDK commands,
https://docs.openbci.com/docs/02Cyton/CytonSDK
https://docs.openbci.com/docs/02Cyton/CytonDataFormat
If you use Python, there are already hooks there for streaming LSL,
https://github.com/OpenBCI/pyOpenBCI
https://github.com/OpenBCI/OpenBCI_Python [older repo]
Regards, William
Thank you William for your reply
Programing a small driver with python would be our plan B if it is to hard to adapt the OpenBCI_GUI.
Today I installed the Processing IDE and changed the baudrate to match the HC05 chip. I receive a output message in the console that it was sucessful to open the port. But now I've some trouble to adapt the Java code for the communication protocol from RFduino to HC05 radio.
If anybody has some experience with the HC05 modul, please let me know.
Thanks and regards
Dominique
If you do some searching here on the forum, (Google Advanced Search button in right column) -- you can find some other posts by people who have replaced the RFduino with some other type of connection or radio.
Generally the two RFduinos add some extra framing characters (for each radio packet) on the stream coming into the GUI. So you need to replicate this functionality to parse that stream.
The latest RFduino code also has special function characters (sent by the GUI) to do the Autoscan and set radio channel functions. You can ignore these of course.