Page 1 of 1
Configuration problems bci2000 + Enobio3G
Posted: 10 Feb 2014, 06:28
by dklober
Hi,
I'm trying to use the Enobio Headset with bci2000 and Mu Rhythm but I encounter some problems.
After executing the CursorTask_Enobio3G.bat all the required programs are started. At that moment the System Log shows me the first warning, which i don't understand. I tried to google the warning but i didn't get any helping answer. When I push the 'Set Config' button I'm getting the other 4 warnings and the window with the timeout appears. How can I fix the warnings / problems?
Thank you in advance.
Daniel
Re: Configuration problems bci2000 + Enobio3G
Posted: 10 Feb 2014, 19:45
by boulay
Some of those warnings seem to be debug messages rather than warnings.
What happens when you click start?
Re: Configuration problems bci2000 + Enobio3G
Posted: 11 Feb 2014, 07:18
by dklober
When I click start the only thing that happens is the following line in the System Log.
2014-02-11T13:14:53 - Operator started operation
Re: Configuration problems bci2000 + Enobio3G
Posted: 11 Feb 2014, 09:00
by boulay
That sounds pretty normal. And the Timeout window never changes its display?
Can click on config, then turn on the option to visualize raw signals? I think it's under the Visualize tab. I'm sorry I'm on a mac and can't check right now.
Then press Set Config again. This should pop up a new window that plots the incoming data. Do you see anything here? Does it look like you're getting EEG? If it does, then it seems like everything is working.
Re: Configuration problems bci2000 + Enobio3G
Posted: 11 Feb 2014, 09:34
by dklober
If i open the 'Visualize Tap' and scroll down to the 'Source Signal' box the checkbox 'visualize raw brain signal' is already marked.
The timeout window doesn't change at all.
Is there something else to do to connect the Headset with bci2000 than entering the MAC address into the 'Source Tap'?
Re: Configuration problems bci2000 + Enobio3G
Posted: 11 Feb 2014, 11:15
by boulay
I just looked at the source code for the ENOBIOADC and I can confirm that several of the warning messages you see are nothing but debug messages. The messages that concern me, however, are the ones that say "The device is not open. Please open the device before sending another command." As best as I can tell, these messages are being generated by the Enobio API. You're not actually connected to the Enobio device, and you aren't actually receiving data.
I'm sorry I can't help you with the Enobio device. I've never used one and I don't have access to one to test. I was just hoping I could help you narrow down the problem and help you further if your problem turned out to to be unrelated to Enobio.
Make sure you read through the
documentation for the EnobioADC. If you still can't get it to work, then also available on that page are e-mail addresses to the authors of the module whom you should contact.
Good luck,
Chad