NIDAQ MX COMPATIBLE

This forum deals with BCI2000 configuration issues.
Locked
EliGC
Posts: 26
Joined: 29 Feb 2008, 10:33

NIDAQ MX COMPATIBLE

Post by EliGC » 15 Aug 2008, 10:39

Hi everyone, first i want to say: thanks for all your help¡¡¡¡¡

I want to know if the NIDAQ MX that is on the source code is compatible with the new version of BCI 2000 (Version 2.0).

Regards,

Eli

gschalk
Posts: 615
Joined: 28 Jan 2003, 12:37

NIDAQ mx

Post by gschalk » 15 Aug 2008, 16:01

The NIDAQ MX Source module should work with v2.0. Because it has been provided by a BCI2000 user, and we do not have access to the hardware, we cannot test this module. If you have problems, please contact the author of the source module (listed in the corresponding page on the wiki) directly, or post other questions here if you have further problems.

Gerv

EliGC
Posts: 26
Joined: 29 Feb 2008, 10:33

Post by EliGC » 19 Aug 2008, 22:58

Hello, thanks for your attention.

We have problems when we compile the project NIDAQmx, at final of the compiler suddenly open a text box that say:

This file can´t be connected with the operator module.

And when i try to load these NIDAQmx.exe with the BCI Launcher, appear and error that says that the source module doen´t have the same version of the BCI 2000.

Can you help me with this.

Thanks in advanced,

Eli

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

Post by mellinger » 21 Aug 2008, 08:32

Eli,

when compiling, you probably trigger running the source module as well. E.g., when you press F9 in the IDE, compiler and linker will be called to compile and link the executable, and then the executable will be started in the debugger. This is the reason for the first error message: The source module is started but no operator module is running, so the source module cannot connect. It will try for some seconds, and then give up, displaying the error message you quote.

The second error message is probably due to the fact that you picked the NIDAQmx.exe executable located at:
BCI2000/src/contrib/SignalSource/NIDAQ-MX/for_BCI2000_V1/NIDAQmx.exe
After building the current version of the executable using the IDE, it will be located in the BCI2000/prog directory rather than inside the NIDAQ-MX directory.

Please note that there is now a binary version of BCI2000 with all contributions pre-built available as well, and can be downloaded at:
http://bci2000.org/downloads/bin/BCI2000Contrib.exe

Juergen

EliGC
Posts: 26
Joined: 29 Feb 2008, 10:33

Post by EliGC » 26 Aug 2008, 16:59

HI,

I continue having problems with NIDAQ mx, when i set config. this message appears:

26/08/2008 03:55:15 p.m. - NIADC::Preflight: Board number 1 not present.
26/08/2008 03:55:16 p.m. - NIADC::Preflight: or does not support DAQmx driver ver 8.0.

What can i do withe this

THANKS IN ADVANCE

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

Post by mellinger » 27 Aug 2008, 05:59

Eli,

have you tried the non-MX version of the NIDAQ source module?

Juergen

EliGC
Posts: 26
Joined: 29 Feb 2008, 10:33

Post by EliGC » 01 Sep 2008, 13:56

Hi, we solved the problem chaging the Windows Vista for Windows XP. But now we have problems with the gains. Can you tell me what is the exactly mean for muV (microvolts????), and why you put 0.033 for gains in all the channels, I ask you this, because when i connected the board (NI) and i introduced a signal for viewing on the Window Sourse Signal, i couln´t see anything, just a cero or a negative DC. :roll:

I would like to contact me with the creator of the module NIDAQ mx, to resolve all this problems, or can you help with that?
:cry:
THANKS IN ADVANCE, :D

Eli

gschalk
Posts: 615
Joined: 28 Jan 2003, 12:37

Gains ...

Post by gschalk » 02 Sep 2008, 10:10

Eli,

The value of 0.033 is just a default. It will have to be set to whatever factor converts from the device units into micro Volts. To find out, you could either write the creator of the NIDAQ mx driver, or simply set the gains to 1, record some signal with a known amplitude, and then load the data offline to see how large the stored values are. This will give you the conversion factor.

In addition to setting appropriate gain values, you have to make sure that you set the range for the display correctly. They are set in the Visualization tab in Config. If you get an incorrect gain or the range for Visualization is completely off, you may see only flat lines or DC offsets, etc.

Gerv

Locked

Who is online

Users browsing this forum: No registered users and 0 guests