ole.traupe wrote:Let me first state again, what a great device the BITalino is! It might solve most of our problems regarding wireless peripheral physiology for our wide-area motion capture lab.
Now, as we are planning to use it for scientific purposes, it would be very important to reliably and transparently deal with buffer overflow issues. To us there would be some good future ways to deal with this issue:
a) the option to choose between alternative behaviors of the BITalino via a flag (allow the discarding of samples: yes/no; with no eventually leading to sampling termination - the latter could be helpful for estimating Bluetooth module buffer size, or just for developing foolproof applications);
b) a sequence marker with a much larger scope (such as 12 or even 16 bit) being robustly significant over multiple seconds with respect to dropped samples, even with a 1000 Hz samplingrate
c) most preferable: an additional channel containing high-accurracy timestamps for each sample (seconds since start of sampling)
In the best of all BITalino worlds, all three measures would be combined to yield a highly fault-tolerant and interpretable bio-signal.
ole.traupe wrote:In that case I am really looking forward to the next edition!
Thanks also for your valuable suggestions. I will try and have a look at the second option for now. A sample (per second) count might already provide a good level of reliability on a sufficiently efficient recording machine.
Thanks also for your quick replies!
Code: Select all
*(word*)(frame+5) |= convADC10(chTable) << 2;
if (nChannels > 1)
*(word*)(frame+4) |= convADC10(chTable);
if (nChannels > 2)
*(word*)(frame+2) |= convADC10(chTable) << 6;
if (nChannels > 3)
*(word*)(frame+1) |= convADC10(chTable) << 4;
if (nChannels > 4)
*(word*)frame |= (convADC10(chTable) & 0x3F0) << 2;
if (nChannels > 5)
frame |= convADC10(chTable) >> 4;