No data stream on Processing GUI
Hi all,
I have literally just started with OpenBCI about a few days ago using it as an undergraduate research project.
At the beginning, the hardware worked fine and recorded data as expected. While playing with it on the Processing GUI, I might have pushed one of the buttons on the OpenBCI 32 bit board. The result is as I press "Start Data Stream" on the Processing OpenBCI GUI, no data is recorded. The channels just sit there unchanged as if I have never pressed anything at all. I suspect that it might be because of the "RST" button that resets the PIC.
I tried plugging the hardware onto another computer with the GUI installed and no data is recorded either. I can only suspect that the problem arises from the hardware but I am not sure what to do from here to fix this problem.
Anyone has any suggestion?
Thank you
N.
I have literally just started with OpenBCI about a few days ago using it as an undergraduate research project.
At the beginning, the hardware worked fine and recorded data as expected. While playing with it on the Processing GUI, I might have pushed one of the buttons on the OpenBCI 32 bit board. The result is as I press "Start Data Stream" on the Processing OpenBCI GUI, no data is recorded. The channels just sit there unchanged as if I have never pressed anything at all. I suspect that it might be because of the "RST" button that resets the PIC.
I tried plugging the hardware onto another computer with the GUI installed and no data is recorded either. I can only suspect that the problem arises from the hardware but I am not sure what to do from here to fix this problem.
Anyone has any suggestion?
Thank you
N.
Comments
---
Note: it’s important to plug in your Dongle before you
turn on your OpenBCI board. Sometimes, if the data stream seems broken,
you may need to unplug your USB Dongle and power down your OpenBCI
board. Make sure to plug your USB Dongle in first, then power up your
board afterwards.
Although what you suggest is something that I have tried while troubleshooting the hardware, I have to wonder if the problem has another source that's a lot more involved that I thought. I will try doing that again tomorrow since I am not sure whether I did that exact order.
I appreciate your time taken to answer my post nevertheless.