Problems to connect to my NeuroSky MindWave

jbopenvib · Post by **jbopenvib** » Wed Jun 20, 2012 2:10 am

Question about using NeuroSky MindWave in combination with OpenVibe

Goodmorning,

Yesterday I downloaded and installed OpenVibe (OV) (openvibe-0.14.1-svn3319-setup.exe) on my Windows 7 Ultimate PC.

I watched the introduction video and played around with OpenVibe to get acquinted with it.
I was impressed by the range of possibilities and the ease of use !

I also have bougt a NeuroSky MindWave set, which I have used now for a couple of weeks succesfully
But I want to have more control of the measurements and want to realize some projects of my own with it.
That was the reason for me to search for open source software such as OpenVibe.

However: although having read the documentation, searching through the OV forum and FAQ etc.
I was not able to connect my MindWave to OpenVibe.
(Although I did read in the OV forum a message from mmarchesi, dated Jan 31, 2012 4:42u.
who succesfully got the acquisition server working with MindWave, so it should work !)

The trouble starts in the openvibe-acquisition-server, where the driver for the NeuroSky MindWave
is not listed in the combo box for the available drivers.
So I cannot use the MindWave altogether it seems !

In the C:\Program Files\openvibe\bin directory I see there is the thinkgear.dll

Could you give me some guidance how to solve this problem!

Thank you in advance.

Regards,

Jan Bours
The Netherlands

Post by **lbonnet** » Wed Jun 20, 2012 9:29 am

Hi Jan and welcome,

The Neurosky driver is simply missing from the 0.14.1 installation package.
This release has been quite complex to handle and I forgot some pieces behind when building the Windows Installer.
Sorry for that...

The 0.14.2 (available right now) has the neurosky driver.

I tested it on a win7, using the bluetooth dongle and software provided with our Mindset.
The configuration is a bit tricky, as I have to pair the bluetooth device manually and activate the port COM on a low value (as requested by the user manual we have here).

My version of the device is quite old now, I suppose the installation procedure has changed with the Mindwave.

If you manage to get your device working, please let us know how here, so future user could have access to that information.
Especially if you confirm mmarchesi procedure.

Hope this helps,

Laurent-

jbopenvib · Post by **jbopenvib** » Wed Jun 20, 2012 2:08 pm

I just made a complete build of Open Vibe 0.14.2,
which ended as a succesful build.

But the MindWave (or MindSet) driver is still missing
from the driver list in the combo box of the Acquisition Server !

I hope you can help me with this problem !

An overview:

================================================================

20-06-2012

I did a complete, succesful build of OpenVibe 0.14.2 -
BUT NO NEUROSKY MINDWAVE IN ACQUISITION SERVER !!!!

- I used directory C:\WORK\OPENVIBE\REPOSITORY\(openvibe-0.14.2-svn3326-src\),
as is indicated in the instructions (no spaces allowed in the names)

- End product goes to C:\WORK\OPENVIBE\REPOSITORY\openvibe-0.14.2-svn3326-src\dist

- In the directory C:\WORK\OPENVIBE\REPOSITORY\openvibe-0.14.2-svn3326-src\dist\bin
there is NO ThinkGear.dll (NeuroSky MindWave) !
(which I think should be the case, can you confirm ?)

I copied the original ThinkGear.dll from my NeuroSky installation to
C:\WORK\OPENVIBE\REPOSITORY\openvibe-0.14.2-svn3326-src\dist\
Starting the Acquisition Server gives the same problem as before:
No NeuroSky MindWave driver in the combo box.

There are a couple of warnings when starting up the Acquisition Server:

[WARNING] No 'plugin object descriptor' found from [../bin/OpenViBE-plugins-matlab-dynamic.dll]
even if it looked like a plugin module

[WARNING] Registery key Software\VB and
VBA Program Settings\Brain Quick - System 98\EEG_Settings is not initialized

- The first message showing up when starting up the Acquisition Server
(just like any other component of OpenVibe by the way):

############################################################
##
##
## WARNING : Microsoft Visual Studio Common tools initialisation script not found ##
##
##
############################################################

- Do I have to make changes in win32-init_env_command.cmd for th NeuroSky MindWave,
as reading the INSTALL.TXT does suggest?

".. copying the windows skeleton to <win32-init_env_command> may not
be enough because of installation specifics such as Visual Studio paths and so on...
Script tweaking is required here

"

What changes would that be ?

- Do I have to make changes for my NeuroSky MindWave in openvibe.conf ?
(C:\WORK\OPENVIBE\REPOSITORY\openvibe-0.14.2-svn3326-src\dist\share)

In the original file openvibe.conf there settings like these:
AcquisitionServer_NeuroskyMindset_ESenseValues = false
AcquisitionServer_NeuroskyMindset_PowerBands = false
AcquisitionServer_NeuroskyMindset_BlinkStrength = false
AcquisitionServer_NeuroskyMindset_Blink = false

What changes would I have to make in openvibe.conf ?

================================================================

Post by **lbonnet** » Wed Jun 20, 2012 2:36 pm

I did a complete, succesful build of OpenVibe 0.14.2 -
BUT NO NEUROSKY MINDWAVE IN ACQUISITION SERVER !!!!

The build process can end successfully even if some modules where not compiled.

If you build OpenViBE from sources, the drivers are built only if the build process can find the various dependencies.
For example, the g.Tec driver needs the g.TEC API, the VAmp/FirstAmp driver needs the FirstAmp DSK, etc.
Some manufacturers gave us the authorization to build and package their DLL in the windows Installer version.
This is the case with Neurosky and this is why the driver is available in the Windows Installer version.

When compiling the Acquisition Server, the build log should look like this at start:

Code: Select all

Configuring and building openvibe-applications\acquisition-server\trunc ...

--   Found OpenViBE...
--     [  OK  ] lib C:/lbonnet/openvibe-repo/openvibe/trunc/lib/OpenViBE-dynamic.lib
--   Found OpenViBE-toolkit...
--     [  OK  ] lib C:/lbonnet/openvibe-repo/openvibe-toolkit/trunc/lib/OpenViBE-toolkit-dynamic.lib
--   Found OpenViBE module EBML...
--     [  OK  ] lib C:/lbonnet/openvibe-repo/openvibe-modules/ebml/trunc/lib/OpenViBE-module-EBML-dynamic.lib
--   Found OpenViBE module Socket...
--     [  OK  ] lib C:/lbonnet/openvibe-repo/openvibe-modules/socket/trunc/lib/OpenViBE-module-Socket-dynamic.lib
--   Found OpenViBE module System...
--     [  OK  ] lib C:/lbonnet/openvibe-repo/openvibe-modules/system/trunc/lib/OpenViBE-module-System-dynamic.lib
--   Found OpenViBE plugins global defines...
--   Found boost...
--   Found GTK+...
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/gtk-win32-2.0.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/gdk-win32-2.0.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/atk-1.0.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/gio-2.0.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/pangowin32-1.0.lib
--     [  OK  ] Third party lib C:/Program Files (x86)/Microsoft SDKs/Windows/v7.0A/Lib/Gdi32.Lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/pangocairo-1.0.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/gdk_pixbuf-2.0.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/pango-1.0.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/cairo.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/gobject-2.0.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/gmodule-2.0.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/gthread-2.0.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/glib-2.0.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/intl.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/gthread-2.0.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/glib-2.0.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/intl.lib
--     [  OK  ] Third party lib C:/lbonnet/openvibe-repo/dependencies/gtk/lib/zdll.lib
--   Found gUSBampCAPI...
--     [  OK  ] lib C:/Program Files (x86)/gtec/gUSBampCAPI/API/Win32/gUSBamp.lib
--   Found FirstAmp API...
--     [  OK  ] lib C:/Program Files (x86)/FaSDK/FirstAmp.lib
--   Found ThinkGear API...
--     [  OK  ] lib C:/Program Files (x86)/MindSet Development Tools/ThinkGear Communications Driver/win32/thinkgear.lib
--   Found Emotiv API...
--     [  OK  ] lib C:/Program Files (x86)/Emotiv Research Edition SDK_v1.0.0.4-PREMIUM/doc/examples/lib/edk.lib
--   Found OpenAL...
--   & Found ALUT...
--   & Found OGG...
--   & Found VORBIS...
--     [  OK  ] lib C:/lbonnet/openvibe-repo/dependencies/openal/libs/Win32/OpenAL32.lib
--     [  OK  ] lib C:/lbonnet/openvibe-repo/dependencies/freealut/lib/alut.lib
--     [  OK  ] lib C:/lbonnet/openvibe-repo/dependencies/libogg/win32/lib/release/libogg.lib
--     [  OK  ] lib C:/lbonnet/openvibe-repo/dependencies/libvorbis/win32/lib/release/libvorbis.lib
--     [  OK  ] lib C:/lbonnet/openvibe-repo/dependencies/libvorbis/win32/lib/release/libvorbisfile.lib
--     [  OK  ] Third party lib C:/Program Files (x86)/Microsoft SDKs/Windows/v7.0A/Lib/WS2_32.Lib
--     [  OK  ] Third party lib C:\lbonnet\openvibe-repo\scripts\..\dependencies\pthreads/lib/pthreadVCE2.lib
-- Configuring done
-- Generating done
-- Build files have been written to: C:/lbonnet/openvibe-repo/local-tmp/openvibe-applications/acquisition-server/trunc

In this example, you can see that I have on my computer all the dependencies I need to compile the drivers, including the Thinkgear API from Neurosky.
If you don't have it, the driver will simply failed to find this dependency and won't compile the driver.

So... download the Mindset Development Tools (MDT) 32bits on the Neurosky website, install it and the build process should find it automatically. If not, you can manually specify the path where to look for your MDT, in the file cmake-modules/FindThirdPartythinkgearAPI.cmake.
Line 12, the different possible paths are listed. Add yours if needed.

Code: Select all

FIND_PATH(PATH_ThinkGearAPI thinkgear.h PATHS 
     "C:/Program Files/MindSet Development Tools/ThinkGear Communications Driver/win32" 
     "C:/Program Files (x86)/MindSet Development Tools/ThinkGear Communications Driver/win32" 
     $ENV{OpenViBE_dependencies})

Once the build script finds the API, it can compile the driver.

Other option : install the windows installer version 0.14.2. Neurosky driver is included directly.

- Do I have to make changes in win32-init_env_command.cmd for th NeuroSky MindWave,
as reading the INSTALL.TXT does suggest?

Tweaking the build scripts is for experienced user. The Win32-init_env script can be configured to build the projects you need to (branches for example).
For more details please have a look at this post.

Do I have to make changes for my NeuroSky MindWave in openvibe.conf ?
(C:\WORK\OPENVIBE\REPOSITORY\openvibe-0.14.2-svn3326-src\dist\share)

It's up to you. These settings are accessible in the driver settings window. Changing the values in your configuration file will change the default option for these settings.

Hope this helps !

Laurent-

jbopenvib · Post by **jbopenvib** » Thu Jun 21, 2012 1:49 am

Connecting NeuroSky MindWave to OpenVibe - SUCCES 20062012 - OVERVIEW

Good news, after many hours of trying and trying:

I have succesfuly connected my NeuroSky MindWave headset
to the OpenVibe Acquisition Server !

To achieve that I have followed the 2 paths that you inducated:

-------------------------------------------------------------------------------------------------------------------
1 - Make a new (Windows 7)-build out of the most recent OpenVibe sourcefile
(OpenVibe version 0.14.2):

- Change the contents of the file FindThirdPartyThinkGearAPI.cmake
(in directory \openvibe-0.14.2-svn3326-src\cmake-modules)
So that the correct path to the NeuroSky's files for the MindWave (and MindSet)
thinkgear.dll, thinkgear.h, thinkgear.lib is being used !

- The make a new build of OpenVibe 0.14.2
by running win32-build.cmd, which resides in directory openvibe-0.14.2-svn3326-src\scripts.

This is a part of the buildmessages generated by the build proces, relevant to the MindWave:

...

Configuring and building openvibe-applications\acquisition-server\trunc ...

...

-- Found ThinkGear API...
-- [ OK ] lib C:/JB_DEVELOPMENT/NEUROSKY MINDWAVE/Developer Tools 2.1/Mind
Set Development Tools/ThinkGear Communications Driver/win32/thinkgear.lib
...

-- Configuring done
-- Generating done
-- Build files have been written to: C:/WORK/OPENVIBE/REPOSITORY/openvibe-0.14.2
-svn3326-src/local-tmp/openvibe-applications/acquisition-server/trunc

Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
Copyright (C) Microsoft Corporation. All rights reserved.

...

[ 69%] Building CXX object CMakeFiles/OpenViBE-acquisition-server-dynamic.dir/sr
c/neurosky-mindset/ovasCConfigurationNeuroskyMindset.obj
cl : Command line warning D9002 : ignoring unknown option '-mms-bitfields'
cl : Command line warning D9002 : ignoring unknown option '-mms-bitfields'
ovasCConfigurationNeuroskyMindset.cpp
C:\WORK\OPENVIBE\REPOSITORY\openvibe-0.14.2-svn3326-src\openvibe-applications\ac
quisition-server\trunc\src\neurosky-mindset\ovasCConfigurationNeuroskyMindset.cp
p(275) : warning C4800: 'gboolean' : forcing value to bool 'true' or 'false' (pe
rformance warning)
C:\WORK\OPENVIBE\REPOSITORY\openvibe-0.14.2-svn3326-src\openvibe-applications\ac
quisition-server\trunc\src\neurosky-mindset\ovasCConfigurationNeuroskyMindset.cp
p(276) : warning C4800: 'gboolean' : forcing value to bool 'true' or 'false' (pe
rformance warning)
C:\WORK\OPENVIBE\REPOSITORY\openvibe-0.14.2-svn3326-src\openvibe-applications\ac
quisition-server\trunc\src\neurosky-mindset\ovasCConfigurationNeuroskyMindset.cp
p(277) : warning C4800: 'gboolean' : forcing value to bool 'true' or 'false' (pe
rformance warning)
C:\WORK\OPENVIBE\REPOSITORY\openvibe-0.14.2-svn3326-src\openvibe-applications\ac
quisition-server\trunc\src\neurosky-mindset\ovasCConfigurationNeuroskyMindset.cp
p(278) : warning C4800: 'gboolean' : forcing value to bool 'true' or 'false' (pe
rformance warning)
[ 71%] Building CXX object CMakeFiles/OpenViBE-acquisition-server-dynamic.dir/sr
c/neurosky-mindset/ovasCDriverNeuroskyMindset.obj
cl : Command line warning D9002 : ignoring unknown option '-mms-bitfields'
cl : Command line warning D9002 : ignoring unknown option '-mms-bitfields'
ovasCDriverNeuroskyMindset.cpp

...

Linking CXX executable OpenViBE-acquisition-server-dynamic.exe
---> Copying dll file C:/JB_DEVELOPMENT/NEUROSKY MINDWAVE/Developer Tool
s 2.1/MindSet Development Tools/ThinkGear Communications Driver/win32/thinkgear.
dll for the Neurosky MindSet driver.
[100%] Built target OpenViBE-acquisition-server-dynamic

...

Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
Copyright (C) Microsoft Corporation. All rights reserved.

[100%] Built target OpenViBE-acquisition-server-dynamic
Install the project...
-- Install configuration: "Release"
-- Installing: C:/WORK/OPENVIBE/REPOSITORY/openvibe-0.14.2-svn3326-src/openvibe-
applications/acquisition-server/trunc/bin/OpenViBE-acquisition-server-dynamic.exe

...

Install the project...
-- Install configuration: "Release"

Building process terminated successfully

Installing files to 'dist' folder, this can take a few seconds - maybe a few min
utes...

## Installing openvibe\trunc ...
## Installing openvibe-applications\id-generator\trunc ...
## Installing openvibe-modules\ebml\trunc ...
## Installing openvibe-modules\fs\trunc ...
## Installing openvibe-modules\socket\trunc ...
## Installing openvibe-modules\system\trunc ...
## Installing openvibe-modules\stream\trunc ...
## Installing openvibe-modules\xml\trunc ...
## Installing openvibe-modules\automaton\trunc ...
## Installing openvibe-kernel-omk\trunc ...
## Installing openvibe-toolkit\trunc ...
## Installing openvibe-plugins\acquisition\trunc ...
## Installing openvibe-plugins\classification\trunc ...
## Installing openvibe-plugins\classification-gpl\trunc ...
## Installing openvibe-plugins\feature-extraction\trunc ...
## Installing openvibe-plugins\file-io\trunc ...
## Installing openvibe-plugins\samples\trunc ...
## Installing openvibe-plugins\signal-processing\trunc ...
## Installing openvibe-plugins\signal-processing-gpl\trunc ...
## Installing openvibe-plugins\simple-visualisation\trunc ...
## Installing openvibe-plugins\stimulation\trunc ...
## Installing openvibe-plugins\stream-codecs\trunc ...
## Installing openvibe-plugins\streaming\trunc ...
## Installing openvibe-plugins\tools\trunc ...
## Installing openvibe-plugins\vrpn\trunc ...
## Installing openvibe-applications\designer\trunc ...
## Installing openvibe-applications\acquisition-server\trunc ...
## Installing openvibe-applications\plugin-inspector\trunc ...
## Installing openvibe-applications\vr-demo\trunc ...
## Installing openvibe-applications\vrpn-simulator\trunc ...
## Installing openvibe-applications\skeleton-generator\trunc ...
## Installing openvibe-applications\ssvep-demo\trunc ...
## Installing openvibe-plugins\matlab\trunc ...
## Installing openvibe-plugins\python\trunc ...
## Installing openvibe-scenarios\trunc ...

Install completed

Druk op een toets om door te gaan. . .

-

Now the NeuroSky MindSet driver is visible in the OPenVibe Acquisition Server, as:
"NeuroSky MindSet (MindSet Dev. Kit 2.1+)" !

These are the Driver Properties of the NeuroSky MindSet / MindWave in OpenVibe Acquisition Server:
Identifier: 0 (default)
Age: 18 (default)
Gender: male (default)

Sampling frequency: 512 (default; only possible value)
COM Port: ghosted: no value is visible, no value can be choosen or input !!

ESense (Meditation/Attention): enabled (default: disabled)
Power (8 channels): enabled (default: disabled)
(8 channels: low alfa,high alfa, low beta,high beta,delta,theta,low gamma,mid gamma,
Blink Strength,Raw EEG (= Electrode))
Blinks (As OVTK_GDF_Blink_Simulation): enabled (default: disabled)
Blink Strength (1 channel with spikes): enabled (default: disabled)

My MindWave set is connected to COM7, which is allright:
it has to be between 1 and 16 for the driver to be able to find it,
see this message:

http://openvibe.inria.fr/FAQ/#I+can%E2% ... sky+Driver

I can’t connect my MindSet/MindWave to the Neurosky Driver
Several users reported having problems connecting the Neurosky MindWave
or MindSet headsets to OpenViBE.

The Neurosky driver in OpenViBE can theoretically communicate with any device
that uses the Thinkgear protocol from Neurosky.

This includes the MindSet and the MindWave.
As recommended in the MindSet documentation (Feb. 2011)
we use low value COM port for the Bluetooth connection.

The driver search for headsets on port COM 1 to 16.
Please verify that your device is installed on a COM port lower than 16.
A recurrent issue also appears with the bluetooth connection manager on Windows.

As reported by Marco (mmarchesi) on our forums:
“I’ve discovered an unusual COM driver configuration in my Device Manager
on Windows (Control Panel -> Hardware and Sound -> Device Manager).
Windows tries to work with an internal “USB-SERIAL CH340″ driver
instead of the correct Mindwave USB Adaptor
(typically installed in “C:/Program Files/NeuroSky/MindWave Driver” folder.
This issue has been reported as well last December:
http://support.neurosky.com/kb/mindwave ... ting-often

So, once I have changed the driver,
the acquisition server worked perfectly with Mindwave!” !!!!! !!!!! !!!!!
Please check your Window Device Manager if you experience the same problem.

See also the discussion under
viewtopic.php?t=605

There you can find this important message of user mmarchesi:

Post subject: Re: MindwavePosted: Tue Jan 31, 2012 4:42 pm

Joined: Tue Jan 31, 2012 11:04 am
Posts: 1
Location: Italy
Hi there,
I hope I found a solution for the Mindwave compatibility issue.
The problem is not the OpenVibe driver, I checked the source code,
it's clean and it would work perfectly with any ThinkGear-based device on 1-16 COM ports.

I've discovered an unusual COM driver configuration in my Device Manager on Windows
(Control Panel -> Hardware and Sound -> Device Manager).
Windows tries to work with an internal "USB-SERIAL CH340" driver
instead of the correct Mindwave USB Adaptor
(typically installed in "C:/Program Files/NeuroSky/MindWave Driver" folder.
This issue has been reported as well last December:

http://support.neurosky.com/kb/mindwave ... ting-often

So, once I have changed the driver, the acquisition server worked perfectly with Mindwave!

Cheers
Marco

All his remarks were applicable to my current situation !

A strange, and very annoying thing I have to add is,
that after starting up OpenVibe Acquisition Server,
choosing the "NeuroSky MindSet (MindSet Dev. Kit 2.1+)" driver
and giving it the desired settings, pressing the connect button,
and pressing the play button once,
most of the time (in fact in all cases that I tried) the connection is not made with the MindWave !
Then messages such as this one appear:

[ INF ] ThinkGear Connection ID is: 0.
[ INF ] Scanning COM ports 1 to 16...
[ INF ] Connection available on port COM1 -- STATUS: FAIL (0 bytes on the stream)
[ ERROR ] The driver was unable to find any valid device on serial port COM1 to COM16.
[ INF ] Connecting to device [NeuroSky MindSet (MindSet Dev. Kit 2.1+)]...
[ INF ] ThinkGear DLL version: 21
[ INF ] Eye blink detection is possible.
[ INF ] ThinkGear Communication ID is: 0.
[ INF ] Scanning COM ports 1 to 16...
[ INF ] Connection available on port COM1 -- STATUS: FAILED (0 bytes on the stream)
[ ERROR ] The driver was unable to find any valid device on serial port COM1 to COM16.
[ ERROR ] Connection failed...
[ INF ] Disconnecting.

So the first time you do this it gives you the string impression
that something is wrong, so you begin to doubt if you have to reconfigure or whatever !

But pressing the play button many times (I mean something like 5 to 10 times)
will make the connection work without altering anything !! So be warned about this ..... !!

-------------------------------------------------------------------------------------------------------------------

2 - Simply install the windows installer version 0.14.2 (NeuroSky driver is included directly),
available from http://openvibe.inria.fr/pub/bin/win32/

I found it rather hard to find this, because I found it under
"Older Versions of OpenViBE:
If you need to use an older (??) version of OpenViBE, you can browse our archives."
Remember: OpenVibe 0.14.2 is the most recent version of OpenVibe (not an older one ....).

This is the direct link to this most recent version of the Windows Installer for OpenVibe-0.14.2:
http://openvibe.inria.fr/pub/bin/win32/ ... -setup.exe !!!!! (76.1 MB)

I installed it, and indeed it comes with the NeuroSky MindSet/MindWave driver included !

With this downloaded version I also was able to succesfully make brainwave sessions
with my NeuroSky MindWave !

-------------------------------------------------------------------------------------------------------------------

I have made a lot of screenshots of my recent session with OpenVibe and my connected MindWave.
I am planning to upload these screenshots to this forum tomorrow !

Thanks Laurent for your quick replies and help today !

Jan Bours

Post by **jlegeny** » Thu Jun 21, 2012 5:44 am

Hello Jan,

a problem was indeed on our side regarding the link to the 0.14.2 version. It is working now and is on the front page as it should be.

Glad you got the neurosky working.

Cheers
Jozef

jbopenvib · Post by **jbopenvib** » Thu Jun 21, 2012 3:25 pm

I already did some simple scenario's today !
Very user friendly interface and stable software.

I would like to post some screenshots via this forum,
butbdo not know how to do this !
Can you you tell me how ?

I am working on an iPad now, and can not post imagesmI think.
Perhaps on a PC this forum has other features .... ??

jbopenvib · Post by **jbopenvib** » Sat Jun 23, 2012 4:02 am

I have uploaded 33 screenshots I made from the first experiments I did last week,
using my NeuroSky MindWave headset connected to the Acquisition Server of Open Vibe.
(OpenVibe 0.14.2 on Windows 7 Ultimate).

Then I used the Open Vibe Designer to do some first experiments which generated these screenshots.

I hope the filenames of these screenshots will still be visible after uploading
because they are quite descriptive of the experiments / scenario's !

Some (important) observations:
- Open Vibe's Acquisition Server has to pass the firewall
- The Blink Strength signal (which represents the voltages from blinking ones eyes, which are muscle potentials,
not EEG potentials !) can vary in strength according to the strength of the blink.
But typically they are much stronger than the brainwaves themselves !
- The blink signals are in good synchronization with the raw EEG signal (raw EEG is called "Electrode")
- The NeuroSky MindWave set can produce 12 different output channels:

1 - the raw, unfiltered EEG signal ("Electrode")
2 - the Attention level (proprietary algorithm of NeuroSky, "eSense")
3 - the Meditation level (proprietary algorithm of NeuroSky, "eSense")
4 - Delta - (Interpretation: deep sleep, unconscious)
5 - Theta - (Interpretation: drowsiness & deep relaxation)
6 - Low Alpha (a.k.a. Alpha1) - (Interpretation: relaxation & meditation)
7 - High Alpha (a.k.a. Alpha2 - (Interpretation: relaxation & meditation)
8 - Low Beta (a.k.a. Beta1) - (Interpretation: focus & attention)
9 - High Beta (a.k.a. Beta2) - (Interpretation: focus & attention)
10 - Low Gamma (a.k.a. Beta3) - (Interpretation: related to some senses & memory)
11 - Mid Gamma (a.k.a. Beta4) - (Interpretation: related to some senses & memory)
12 - Blink Strength (strength of muscle voltages while blinking ones eyes) (NeuroSky, "eSense")

NeuroSky publishes a White Paper on their website
(URL http://www.neurosky.com/Documents/Docum ... 35cfa1de92)
"Brain Wave Signal (EEG) of NeuroSky, Inc. (December 15, 2009)".

In this document the following relation between the various EEG frequency bands
and the corresponding various brain states is presented:

Brainwave Type Frequency range Mental states and conditions
Delta 0.1Hz to 3Hz Deep, dreamless sleep, non-REM sleep, unconscious
Theta 4Hz to 7Hz Intuitive, creative, recall, fantasy, imaginary, dream
Alpha 8Hz to 12Hz Relaxed, but not drowsy, tranquil, conscious
Low Beta 12Hz to 15Hz Formerly SMR (Sensory motor rhythm,
seems to link brain and body functions), relaxed yet focused, integrated
Midrange Beta 16Hz to 20Hz Thinking, aware of self & surroundings
High Beta 21Hz to 30Hz Alertness, agitation
Gamma 30Hz to 100Hz Motor Functions, higher mental activity (consolidation of information)

The NeuroSky eSense algorithm is proprietary. Some parts of it are dynamically learning,
and at some times employ some "slow-adaptive" algorithms to adjust to natural fluctuations and trends
of each user, accounting for and compensating for the fact taht EEG in the human brain is subject
to normal ranges of variance and fluctuation. This part of the reason why ThinkGear sensors
are able to operate on a wide range of individuals under an extremely wide range of personal
and environmental conditions while still giving good accuracy and reliability.

I hope the screenshots speak for themselves !