Problem with the operator module

This forum deals with BCI2000 configuration issues.
Locked
dinasherif
Posts: 9
Joined: 15 Sep 2011, 09:22

Problem with the operator module

Post by dinasherif » 31 Jan 2012, 19:06

Hello,

I have a successful build for BCI2000 using VS2010, I even tried using it to acquire signals from the Neurosky Mindwave and it is working fine. When trying to rebuild the BCI2000 on another machine using the VS2008 compiler, I faced a problem. Please check the images below. After I successfully built the core modules, operator module, P3signalProcessing and P3speller modules, and the neurosky source module, I then run the batch file ... On pressing the Config button in the GUI i get the dialog which as shown has missing tabs and when I open the source tab i find it lacking alot of parameters and thus when I load the parameter file and press set config and I get the error attached in the system log image.
Missing tabs and parameters in the COnfig interface
Missing tabs and parameters in the COnfig interface
ERROR!
ERROR!
NOw, I followed the same steps as I did before when building using the VS2010, what could possibly be the problem?
The following image is what I get when running the VS2010 built version:
ConfigInterface_2.JPG


Waiting for a reply and thanks,

-- Dina.

mellinger
Posts: 1341
Joined: 12 Feb 2003, 11:06

Re: Problem with the operator module

Post by mellinger » 02 Feb 2012, 09:07

Hi,

I have just been compiling BCI2000 with various compilers for testing purposes, and never had such a problem. From your description and the error messages, I conclude that the DataIOFilter is not being instantiated in the source module. This may be because the file DataIOFilter.cpp is missing from the BCI2000FrameworkSignalSrcModule library project, or because the file SigSrcRegistry.inc is not generated properly.

When you generated the VS solution file using the VS2008 batch file from the build directory, did you get any error messages?
Does the full path to your BCI2000 directory contain any non-western characters? If so, try moving it to a location that has no such characters in its path, and re-run the VS2008 batch file.

Regards,
Juergen

dinasherif
Posts: 9
Joined: 15 Sep 2011, 09:22

Re: Problem with the operator module

Post by dinasherif » 06 Feb 2012, 10:19

Thanks Juergen!

Actually the problem was that the SigSrcRegistry.inc was not generated properly because the extract_registry project was not built.
Now it is working fine, thanks again,

-- Dina.

Locked

Who is online

Users browsing this forum: No registered users and 0 guests