Bluetooth LE C++ interaction


#1

I am trying to establish a bluetooth connection of a Muse 2016 headband with by PC using C++.
So far I was able to discover the device (headband) and list all available services, including address, characteristics, and descriptor.
Now, I would like to know what I have to send to the device in order to get the connection and what address stands for which value.
Hence, my question is: Is there some kind of interface description for the headband?


#2

You can use the LibMuse SDK for Windows 10 to connect to a Muse 2016 headband with C++. It provides an API to connect and others to receive the data of various types. It is available at: http://developer.choosemuse.com/sdk/developer-sdk-windows


#3

Interaxon haven’t documented it, but you can check here to look at someone who already figured it out:


#4

Thanks for the answers. I’m not that familiar to python (and to bluetooth).
So, I’ll try my best with C++.
Here is a list of what I get when connecting to the headband:
My question is, what kind of Characteristic I need to send to the headband to start communication?

GATT
Service: {00001801-0000-1000-8000-00805F9B34FB}
0 Service Changed
Characteristic: {00002A05-0000-1000-8000-00805F9B34FB}
Descriptor: Client Characteristic Configuration : {00002902-0000-1000-8000-00805F9B34FB}
GAP
Service: {00001800-0000-1000-8000-00805F9B34FB}
0 Device Name
Characteristic: {00002A00-0000-1000-8000-00805F9B34FB}
1 Appearance
Characteristic: {00002A01-0000-1000-8000-00805F9B34FB}
2 Peripheral Preferred Connection Parameters
Characteristic: {00002A04-0000-1000-8000-00805F9B34FB}
Service: {0000FE8D-0000-1000-8000-00805F9B34FB}
0
Characteristic: {273E0001-4C4D-454D-96BE-F03BAC821358}
Descriptor: Client Characteristic Configuration : {00002902-0000-1000-8000-00805F9B34FB}
1
Characteristic: {273E0008-4C4D-454D-96BE-F03BAC821358}
Descriptor: Client Characteristic Configuration : {00002902-0000-1000-8000-00805F9B34FB}
2
Characteristic: {273E0009-4C4D-454D-96BE-F03BAC821358}
Descriptor: Client Characteristic Configuration : {00002902-0000-1000-8000-00805F9B34FB}
3
Characteristic: {273E000A-4C4D-454D-96BE-F03BAC821358}
Descriptor: Client Characteristic Configuration : {00002902-0000-1000-8000-00805F9B34FB}
4
Characteristic: {273E000B-4C4D-454D-96BE-F03BAC821358}
Descriptor: Client Characteristic Configuration : {00002902-0000-1000-8000-00805F9B34FB}
5
Characteristic: {273E0002-4C4D-454D-96BE-F03BAC821358}
Descriptor: Client Characteristic Configuration : {00002902-0000-1000-8000-00805F9B34FB}
6
Characteristic: {273E0003-4C4D-454D-96BE-F03BAC821358}
Descriptor: Client Characteristic Configuration : {00002902-0000-1000-8000-00805F9B34FB}
7
Characteristic: {273E0004-4C4D-454D-96BE-F03BAC821358}
Descriptor: Client Characteristic Configuration : {00002902-0000-1000-8000-00805F9B34FB}
8
Characteristic: {273E0005-4C4D-454D-96BE-F03BAC821358}
Descriptor: Client Characteristic Configuration : {00002902-0000-1000-8000-00805F9B34FB}
9
Characteristic: {273E0006-4C4D-454D-96BE-F03BAC821358}
Descriptor: Client Characteristic Configuration : {00002902-0000-1000-8000-00805F9B34FB}
10
Characteristic: {273E0007-4C4D-454D-96BE-F03BAC821358}
Descriptor: Client Characteristic Configuration : {00002902-0000-1000-8000-00805F9B34FB}


#5

Look at line 166 here:


#6

The protocol that part where it will be going to know the the things which need the very interesting part which will be going to Epson error code 0x69 guide for the Bluetooth LE C++ interaction to get the access data