re: Gazelle (GZLL) vs BLE (Bluetooth Low Energy). These are two completely different modes the RFduinos can communicate in. The OpenBCI firmware uses GZLL to achieve maximum possible data transmission

changes. There was a talk of a Bluetooth "Gazelle" mode for fastest possible raw data transmission. Can you elaborate what that is? http://docs.openbci.com/software/02-OpenBCI_Streaming_Dat

I'm assuming that you would like to stream the raw EEG channel data + counter value through the dongle. Then we need to modify the current customized firmware on the board to follow the protocol of th

default firmware uses a special Bluetooth "Gazelle" mode for fastest possible raw data transfer. The BLE mode has much lower throughput and cannot stream 8 channels of 24 bit samples at 250

It could be that the radio link (RFduino Nordic bluetooth/gazelle) between the mainboard and dongle is encountering interference from other Bluetooth devices. Can you try operating your equipment in d

Bluetooth v2 or v3 has MUCH higher throughput than the Bluetooth 4 / BLE (or Gazelle on the RFduino) currently used. You would bypass the firmware that is sending to the RFduino, and instead pass the

#include // using the Gazelle Stack

How is your question related to OpenBCI? OpenBCI does not use WiFi, but instead a proprietary protocol, called Gazelle. The dongle and mainboard communicate with this protocol.

The RFD22301 does have BLE Bluetooth Low Energy capability. But the OpenBCI firmware to do this does not yet exist. Also BLE on the RFD22301 is very very slow, at least with this device. So in BLE mod

http://openbci.com/forum/index.php?p=/search&Search=gazelle

The RFduino modules are limited to Bluetooth Low Energy (not currently used) and Gazelle (which is the Nordic proprietary protocol used by OpenBCI). Other Bluetooth hardware modules (v3.0) do support

@biomurph: Yes, I have followed the instructions on RFduino website. I will wait for your Gazelle instructions, since I experienced about 10% data loss with both the original 1.5.8 and the current 1.6

I will add a post here soon that will go over how to update the Gazelle library so those functionalities are available.

The RFduino modules can only run two versions of 'Bluetooth', BLE Bluetooth Low Energy, which is very slow; and GZLL, Gazelle, which is a proprietary Nordic protocol not available on other Bluetooth m

When you say "bluetooth RFduino 22301" are you referring to the RFduino's on our dongle or main board? The OpenBCI RFduino's do not use Bluetooth, but something called Gazelle from Nordic. B

be how much data could be squeezed over the Gazelle link. I think it could get up to 500SPS, and more with the right kind of buffering/compression.

The RFduino's (Nordic's nRF51822 SOC with RF Digital's Arduino environment) -- only do two types of radio link: Bluetooth Low Energy, OR Nordic's proprietary Gazelle protocol. The latter is what power

There is something happening under the RFduinoGZLL wrapper and inside the Nordic Gazelle stack that disrupts the serial connection when the RFduino is set up as a Device. 

The Gazelle stack allows for maximum of 32 bytes per packet. We reserve the first byte of each packet as a check-sum between the radios. The check-sum byte is added by the Device radio (on the OpenBCI

bytes over to the radio before thinking about Gazelle. I agree that there is comfort in knowing the radio transport is packet based, and you're right, the Host job is much easier. I'm doing error che