OpenBCI "Clipping" Issue
Hello,
I’m practising with the Cyton board (firmware version 3.1.1) to assess its signal quality (for now without daisy).
In principle, I’m interested in using only the WiFi Shield (firmware version 2.0.5), but I experience the following issue also with Bluetooth and both with and without SD card.
As it is shown in the picture below (and even more clearly in the videos linked later), sometimes the signal seems to clip and remains stuck until I shake the board or move the cables. In addition, this behaviour changes from acquisition to acquisition, and in some rare cases, it self-recovers without the need of shaking the board.
From my tests (acquisitions of a single ECG bipolar channel as presented in the Cyton tutorial, see videos for configuration), it seems to happen when I move rapidly towards the board (in this case it happens all the times) or when I move the limbs (but not always, for long intervals it doesn’t happen even if I move a lot even the cables. Of course, there’s the expected introduced noise, but no clipping).
Note that I’m testing the board with movements because they will be part of my experiments. Motion artefacts are expected… I will deal with them somehow, but I cannot deal with such long clipping intervals (seconds) especially because most of the times the board doesn’t self-recover.
What I really don’t understand is where this behaviour originates and why sometimes the board works perfectly while immediately after, with the same movements, it does not. My guess is that it is something happening in the ADS1299, but I really cannot spot the source (I don’t have strong electronics experience but I read the datasheet various times and I have no clue), especially considering that to solve the issue I have to move the board (and sometimes it doesn’t even work and I have to do it many times).
Can you give me some hints? Some possible explanations? Solutions?
NOTE1: I experience this issue with two different Cyton boards with the same firmware version (I don’t think it’s a firmware problem).
NOTE2: As the picture shows, it is not actually clipping, because there is an interval (slightly before the 300000th sample) with values that exceed the value experienced during the issue (and also the “clipping” value is not perfectly constant as can be seen from the linked file, but still seems to be clipping from the below image of the induced recovering beginning). I’m really confused.
NOTE3: If I start an impedance test on the channel when the board is stuck (and is not self-recovering) it gives 0 ohms as if it senses it as RAILED.
NOTE4: In the wires configuration of the acquisition in the videos the BIAS pin is not used (and removed along with SRB2 in the hardware configuration of the OpenBCI_GUI), however, I also tried with it included and placed somewhere in the arm and I experienced the very same behaviour.
VIDEO1: https://youtu.be/pMo8fFcve2k
VIDEO2: https://youtu.be/0_1MC4NCrAo <— here the issue is very clear
VIDEO3: https://youtu.be/V74JwBSiQOw <— more stable behaviour
RECORDED FILE (VIDEOS): https://drive.google.com/file/d/1i52-bKucMiHU-eFBH8eBMFllATtTQvzO/view?usp=sharing
Some notes and reasoning on the videos:
- In this specific acquisition, it always self-recovered from the clipping (in other acquisitions it did not). Actually, in this acquisition, it never seems to actually clip, but rather to have a large swing in amplitude. (this might be the difference from self-recover w.r.t. no self-recover, need to investigate further)
- As can be seen at the beginning of VIDEO1 (until minute 00:50), moving the legs (and consequently the wires), feet and hands does not produce the clipping, even manually moving the wires does not. This is the intended behaviour. The issue happens at minute 00:50 when I rapidly move (but not so much in the end) closer to the desk a couple of times. Then again no issue even moving until minute 01:54 when a couple of usual leg movements generate the issue. Then same movements no issue until the end of the video.
- The first interval of VIDEO2 presents the issue due to slight leg movements again (until minute 01:22). Then no issue during manual movement of the wires (this puzzles me).
- VIDEO3 has a more stable behaviour (just one instance of the issue) even if it was acquired immediately after VIDEO2.
Thank you in advance for your support. I'm planning new acquisitions to try to constrain the problem trying to get more insights, so if you have any suggestion please feel free to reply.
Comments