it does not make the OpenBCI appear under devices as it shows on the video.

Question

it does not make the OpenBCI appear under devices as it shows on the video.

lisasmirnova opened this issue 4 years ago · 13 comments

it does not make the OpenBCI appear under devices as it shows on the video. I just wonder what did I do wrong.
Re - https://www.youtube.com/watch?v=1jlf233CVig
No matter what I do following instructions - the OpenBCI not connected to the neuromore

Answer 1 · 2020-08-11T08:59:56.000Z

Hi @lisasmirnova - which version of the OpenBCI are you using / trying to connect?

Answer 2 · 2020-10-25T19:27:37.000Z

I am facing the same issue.
Could you fix it?

Answer 3 · 2021-01-07T05:16:22.000Z

Hi @hilsbos, I am facing the same issue - I just upgraded to v5.0.2 of the OpenBCI_GUI, and just using Cyton (without Daisy), and I'm running on the OS X on the neuromore v1.4.7.

I've also opened the OpenBCI_GUI to confirm that the connection between my device is there, but for some reason is still not showing up in the neuromore studio.

Thanks again for all the great work - really excited to use the platform to work on an art project using brainwaves once solved.

Answer 4 · 2021-03-11T02:19:03.000Z

When I do an ls /dev/tty.* My Cyton shows up as /dev/tty.usbserial-DM0258NR. Is Neuromore specifically looking for a device named 'OpenBCI' instead of 'usbserial'?

Answer 5 · 2021-03-14T01:38:16.000Z

Also when starting Neuromore from the CLI, I get an error when trying to "Search for devices":
Failed to load the library: udev, supported version(s): 1 and 0
I suspect this might have more to do with Neuromore not being able to locate the OpenBCI device?
Maybe @hilsbos might be able to confirm/deny if I'm on the right track...?

Answer 6 · 2021-03-16T21:40:59.000Z

Looks like udev is specific to linux? Maybe @cyberjunk would have some insight as well. He seems to have contributed a lot to the OSX functionality in #41 .

Answer 7 · 2021-03-17T07:53:40.000Z

Hi, we're about to release a new OpenBCI integration shortly that should make those issue obsolete.

Answer 8 · 2021-03-18T00:52:50.000Z

Hi, we're about to release a new OpenBCI integration shortly that should make those issue obsolete.

Thanks for the reply! Looking forward to it!

Answer 9 · 2021-06-16T01:21:01.000Z

The new version supports multiple OpenBCI devices. You can access them for now under the Brainflow or Cyton device nodes. Please provide us feedback of the new release!

Answer 10 · 2021-07-28T17:57:30.000Z

Hello,

I am having the same issue where my Cyton board is not recognized in the Neuromore application. Was this issue resolved? The drivers all seem to be working properly since the OpenBCI GUI works and I changed the latency to 1 ms. Was wondering if anybody resolved this issue?

Answer 11 · 2022-04-19T10:37:38.000Z

Hi @hilsbos, I am facing the same issue - I just upgraded to v5.0.2 of the OpenBCI_GUI, and just using Cyton (without Daisy), and I'm running on the OS X on the neuromore v1.4.7.

I've also opened the OpenBCI_GUI to confirm that the connection between my device is there, but for some reason is still not showing up in the neuromore studio.

Thanks again for all the great work - really excited to use the platform to work on an art project using brainwaves once solved.

can you connect cyton with neuromore studio on the Mac OSX ?

Answer 12 · 2022-11-01T16:21:49.000Z

Hello. I have a similar problem.
I purchased CYTON + DAISY BIOSENSING BOARDS (16-CHANNELS) and it is well recognized within the openbci program.
However, in Neuromore Studios, 'no active devices' is displayed and the waveform of the brain waves is not recognized.
I've been trying to figure out a way with this problem for a few days, but I don't know why.

Answer 13 · 2023-02-09T15:50:48.000Z

Looks like cyton via brainflow is working when a single channel is selected as input however the EEG(all channels) input does not seem to be working. This is on a macOS 13.1 neuromore v1.6.0. When I tested on windows the cyton(not brainflow) EEG input worked fine out of the box - seems to be more of an issue on macOS for some reason.