Need pointing out in BLE-Android application.
in Cyton
I'm about to implement an android application that can send and receive data from the Cyton-32-bit board.
I'm aware that the RFduinoBLE is much slower than the RFduinoGZLL used in the serial communication between the Board and the USB dongle.
So, i'm not going to send the recorded data in the time of recording to the android device, Instead i'm going to write the data on the SD card and send back the file to the android device after the recording is done.
I just need pointing out to the right direction of where i'm going to start with, and what parts am i going to edit or re-implement in both the OpenBCI-32-library and the Board's RFduino radio module code.
I'm aware that the RFduinoBLE is much slower than the RFduinoGZLL used in the serial communication between the Board and the USB dongle.
So, i'm not going to send the recorded data in the time of recording to the android device, Instead i'm going to write the data on the SD card and send back the file to the android device after the recording is done.
I just need pointing out to the right direction of where i'm going to start with, and what parts am i going to edit or re-implement in both the OpenBCI-32-library and the Board's RFduino radio module code.
Thanks in advance.
Comments
The WIFI Shield solution is not preferred in our situation, not because of the budget but because of the nature of our application,
The solution we decided to implement is much simpler than the one in the link you kindly provided, ours will be simply limited to the following:
1- The RFduino chip on the board (Device) will get a triggering signal from the Android device which uses BLE.
2- The RFduino in turn will make the ChipKit MC start recording from the desired channels with the desired sampling frequency and write directly to the SD card without sending anything to the RFduino.
- It might seem a bad UX waiting for the file to have the data recorded on it, closed and then sent back to the android device,, but the nature of the single recording session in our application will not exceed the limits of one to three seconds. So, it won't be that bad.
So, if i'm wrong please please correct me, what we'll have to edit or re-implement in our situation is:
- The OpenBCI_32bit & OBCI32_SD libraries.
Thanks in advance
I'll take the USB solution in consideration surely, i haven't thought of this before actually :"D