MindWave Mobile 2 and Acquisition server problems

Come here to discuss about OpenViBE in general!
Post Reply
Stan49
Posts: 2
Joined: Sun Oct 13, 2019 5:10 pm

MindWave Mobile 2 and Acquisition server problems

Post by Stan49 »

Hi,
I have browsed the forum without finding any definitive answer to my problem.
All the attempts I made to connect the MindWave Mobile 2 headset to the OpenVibe acquisition server (changing COM port number, reinstalling Thinkgear connector ...) lead to the same messages :

Code: Select all

Scanning COM ports 1 to 16 ...
The driver was unable to find any valid device on serial port COM1 to COM16
Connection failed ...
The MWM2 device works very well with other dedicated software on my PC with the same BT interface (not at the same time obviously).
All ideas to help solving my issue ?
Thank you very much for your help.
Regards

Thibaut
Posts: 264
Joined: Wed Oct 31, 2018 9:14 am

Re: MindWave Mobile 2 and Acquisition server problems

Post by Thibaut »

Maybe, For some device if you are already connected with an application you can't find them with an other (simultaneously).
Thibaut

Kilo_17SSK
Posts: 3
Joined: Fri Oct 11, 2019 9:13 am

Re: MindWave Mobile 2 and Acquisition server problems

Post by Kilo_17SSK »

Okay, good to know for us newbies; so, the Mindwave Mobile 2 is compatible with OpenViBE, right?

Stan49
Posts: 2
Joined: Sun Oct 13, 2019 5:10 pm

Re: MindWave Mobile 2 and Acquisition server problems

Post by Stan49 »

I would not say that ! Until now, I have not managed to establish a connection between my Mindwave Mobile 2 headset and Open Vibe ! Despite the fact I have used 2 different BT adapters, I still get the same error message "The driver was unable to find any valid device on serial port COM1 to COM16".

Thibaut
Posts: 264
Joined: Wed Oct 31, 2018 9:14 am

Re: MindWave Mobile 2 and Acquisition server problems

Post by Thibaut »

You have here : http://openvibe.inria.fr/supported-hardware/ the list of drivers. If you are the second maybe the difference is toohigh for the previous driver.... Without different helmet it's difficult to implement and debug drivers...
Thibaut

Post Reply