This forum deals with BCI2000 configuration issues.
-
pjercic
- Posts: 14
- Joined: 02 Jul 2012, 10:03
Post
by pjercic » 25 Aug 2014, 05:32
I can't seam to connect my BCI2000 with National Instrument NI DAQP ad 6016. I just want to set up a single channel for start.
It might be a configuration issue, since I get the error
2014-08-25T11:22:14 - Operator set configuration
2014-08-25T11:22:14 - SignalProcessing confirmed new parameters ...
2014-08-25T11:22:14 - Application confirmed new parameters ...
2014-08-25T11:22:15 - DataIOFilter::Initialize: NIADC::Initialize: Requested value is not a supported value for this property. The property value may be invalid because it conflicts with another property.
Property: DAQmx_AI_TermCfg
Requested Value: DAQmx_Val_RSE
You Can Select: DAQmx_Val_Diff, DAQmx_Val_NRSE
Channel Name: Dev1/ai0
Task Name: myTask
Status Code: -200077.
2014-08-25T11:22:15 - DataIOFilter::Initialize: NIADC::Initialize: Specified operation cannot be performed when there are no channels in the task.
Task Name: myTask
Status Code: -200478.
I am using NI DAQmx to connect to my device and it acquires the signal perfectly, so the driver is good to go. The specifications of the NI DAQmx installation are as follows.
Operating System(OS) Windows XP Professional
OS Version 5.01.2600
OS Info Service Pack 3
Processor Intel(R) Pentium(R) CPU G2030 @ 3.00GHz / x86 Family 6 Model 58 Stepping 9 / GenuineIntel / 3000 MHz
Number of Processors 2
Physical Memory 3,20 GB of RAM
Drive C:\ 434 GB of 465 GB free
National Instruments Software: Version:
CVI Run-Time 13.0.1.204
NI-DAQmx Device Driver 9.6.0f0
NI-DAQmx ADE Support 9.6.0
NI-DAQmx MAX Configuration 9.6.0
NI I/O Trace 3.0.2f0
IVI Compliance Package 14.0
LabVIEW Run-Time 2010 SP1 10.0.1
Measurement & Automation Explorer 14.0.0f0
Measurement Studio Visual Studio 2010 Support - See individual versions below.
DotNET
Common 13.0.40.190
Common (64-bit) 13.0.40.190
NI-USI 2.1.0.5374
NI PXI Platform Services 3.2.1
NI-PAL Software 14.0.0
NI SignalExpress 14.0
NI System Configuration 14.0.0f0
NI-VISA 14.0
NiVisaServer.exe 5.3.0.49152
NIvisaic.exe 5.1.2.49152
NI-VISA Runtime 14.0
LabVIEW Run-Time 2011 SP1 f5 11.0.1
LabVIEW Run-Time 2012 SP1 f9 12.0.1
LabVIEW Run-Time 2013 SP1 f3 13.0.1
LabVIEW Run-Time 2014 14.0.0
LabVIEW Run-Time 8.2.1 8.2.1
LabVIEW Run-Time 2009 SP1 f6 9.0.1
-
boulay
- Posts: 382
- Joined: 25 Dec 2011, 21:14
Post
by boulay » 25 Aug 2014, 10:15
It looks like there were some parameters that were hard-coded into the module. You'll have to change them and recompile.
Open up BCI2000\src\contrib\SignalSource\NIDAQ-MX\NIADC.cpp
Search for
Code: Select all
long int terminalConfig=DAQmx_VAL_RSE;
.
(In my file it is line 413)
Change it to read
Code: Select all
long int terminalConfig=DAQmx_Val_NRSE;
or, if you are doing bipolar recording, use
Code: Select all
long int terminalConfig=DAQmx_Val_Diff;
.
-
pjercic
- Posts: 14
- Joined: 02 Jul 2012, 10:03
Post
by pjercic » 27 Aug 2014, 08:41
I found the mentioned spot and changed it, but QT library is bugging me when trying to recompile. I have QT installed on my system, but the system says it can't find the internal QT libraries when I run Make VS10 Project files.
Can you please recompile this module (EXEcutable) for me, or advise me on how to fix the recompilation issues with QT.
-
pjercic
- Posts: 14
- Joined: 02 Jul 2012, 10:03
Post
by pjercic » 28 Aug 2014, 05:55
In more detail, after running
Make VS10 Project Files I get the following error, I have installed QT:
Qt QTGUI library not found.
Qt QTCORE library not found.
-- Creating Project files for BCI2000 Version 3.0.5
-- Including custom extension DataGloveLogger
---- (to disable, set the BUILD_DATAGLOVELOGGER setting to FALSE)
-- Including custom extension WebcamLogger
---- (to disable, set the BUILD_WEBCAMLOGGER setting to FALSE)
-- Including custom extension EyetrackerLogger
---- (to disable, set the BUILD_EYETRACKERLOGGER setting to FALSE)
-- Including custom extension WiimoteLogger
---- (to disable, set the BUILD_WIIMOTELOGGER setting to FALSE)
-- Including custom extension GazeMonitorFilter
---- (to disable, set the BUILD_GAZEMONITORFILTER setting to FALSE)
-- Including custom extension AudioExtension
---- (to disable, set the BUILD_AUDIOEXTENSION setting to FALSE)
---Adding Framework Library: BCI2000FrameworkCore
---Adding Framework Library: BCI2000FrameworkSigSrcModule
---Adding Framework Library: BCI2000FrameworkSigProcModule
---Adding Framework Library: BCI2000FrameworkAppModule
Qt QTOPENGL library not found.
Qt QTGUI library not found.
Qt QTCORE library not found.
Qt QTOPENGL library not found.
Qt QTGUI library not found.
Qt QTCORE library not found.
CMake Error at C:/Documents and Settings/lab/Desktop/current/BCI2000/src/extlib/
3DAPI/Demo/CMakeLists.txt:31 (QT4_WRAP_CPP):
Unknown CMake command "QT4_WRAP_CPP".
p.s. I did found the solution which I quote bellow, but I couldn't force CMake to look for localy installed QT
When running CMake, it determines the current compiler/OS combination, and tries to download an appropriate version of the BCI2000-specific Qt build. If no such build is available, it expects a local Qt installation to be available, and fails with an error message if this is not the case.
If a BCI2000-specific Qt build is available for the current configuration, you will still have the option of using a locally installed version of Qt. This is a CMake option USE_EXTERNAL_QT appearing in the CMakeCache.txt file after CMake has been run for the first time. Such options may be changed using the CMake GUI, or a text editor. After changing the option, run CMake again to apply the change to the created project files.
-
boulay
- Posts: 382
- Joined: 25 Dec 2011, 21:14
Post
by boulay » 02 Sep 2014, 00:24
Sorry for the delay.
I was able to compile using revision 4730. I had to fix some LibTiny errors first.
I tried using an older revision but I had the same Qt errors as you describe.
See attached.
-
Attachments
-
- NIDAQ_mx_Source.zip
- 3 versions of NIDAQ_mx_Source for different terminal configurations.
- (1.5 MiB) Downloaded 771 times
-
pjercic
- Posts: 14
- Joined: 02 Jul 2012, 10:03
Post
by pjercic » 02 Sep 2014, 06:44
Wow, thanks for the help and the modules.
When I saw "DLL Hell" mentioned together with QT library, I was only expecting problems.
I am able to hook to the NI DAQP ad 6016 device, I can see the Active LED turned ON and the source module is running in NRSE mode.
I have connected one of the input channels to my sound card, which I can clearly acquire in the NI MAX and Signal express. Unfortunately, I can't get any signal reading away from the baseline, in the Signal Source display.
That is, all channels report 9.830100e+001 value all the time. Shouldn't there be a slight fluctuation of the signal even if nothing is connected to it, just because of the imperfection of the amplifier?
-
boulay
- Posts: 382
- Joined: 25 Dec 2011, 21:14
Post
by boulay » 02 Sep 2014, 12:55
It's not unusual to be flat if it's railing. However, that's a problem at the input. if you have a signal in NI MAX then you should see a similar signal in the signal source visualization.
Is your sound card outputting something sufficiently slow that it won't get filtered out by any filters that might be built in to the signal source module?
Sorry, I don't have any NIDAQ devices so I can't help you test.
-
pjercic
- Posts: 14
- Joined: 02 Jul 2012, 10:03
Post
by pjercic » 04 Sep 2014, 05:31
Thank for helping out.
I don't believe that my signal is railing, you can see in the images I attached, my signal is between 0 and 1 volts with 220Hz stimulus (there is also 50Hz there since it comes of the sound card).
You can perfectly see the signal in the NI software, but in BCI2000 the line is flat even on the muV scale.
I measured in differential and nrse mode where I could get a clear signal in both on NI software.
Can you please take a look and advise me on how to proceed further in fixing this, any advice is good.
-
Attachments
-
- signal_example.zip
- 4 images depicting example signal in NI MAX, NI Signal Explorer and BCI2000
- (166.4 KiB) Downloaded 781 times
-

- NRSE signal
-

- NRSE signal
-
boulay
- Posts: 382
- Joined: 25 Dec 2011, 21:14
Post
by boulay » 04 Sep 2014, 07:31
Have you ever had BCI2000 working with another module (even SignalGenerator)? If so, then I guess that your problem has to do with the NIDAQ module. I've never actually used any NIDAQ module, and I don't have a NIDAQ device so I cannot test.
Do you have access to any other NIDAQ devices that you can try?
You may need to do a little coding to fix it. If you do manage to fix it then please let us know and we will set you up to submit your changes upstream.
At the top of the NIADC.cpp file there is the contact information for the person that developed it. You might get better insight from him, but I don't know if that 6-yr-old institutional e-mail address is still valid.
Good luck.
Code: Select all
* Module: NIDAQmxADC.CPP *
* Comment: Support for National Instrument boards using DAQmx Driver, tested *
* with DaqPad 6015 up to 16 channel at 512 Hz in NRSE mode *
* Version: 1.05 *
* License: *
* Copyright (C) 2008 Giulio Pasquariello (g.pasqua@inwind.it), Gaetano *
* Gargiulo DIET Biomedical unit - University of Naples "Federico II" *
-
pjercic
- Posts: 14
- Joined: 02 Jul 2012, 10:03
Post
by pjercic » 09 Sep 2014, 05:02
I have BCI2000 working with the signal generator and I used NIDAQ device ad 6016 to test the NIDAQ module, the screenshots were made using that device and the signal from the audio sound card.
I will try with the contact details, before proceeding to solving the problem programmatically.
-
pjercic
- Posts: 14
- Joined: 02 Jul 2012, 10:03
Post
by pjercic » 19 Sep 2014, 06:46
Is there a way to run this module in DIFF mode, instead of NRSE?
I managed to prepare the signal in DIFF mode correctly, so if I get the module to work in DIFF mode I could get the correct signal.
-
boulay
- Posts: 382
- Joined: 25 Dec 2011, 21:14
Post
by boulay » 19 Sep 2014, 09:10
In the zip file (a few posts up) I included a diff version of the module.
Note, however, that it's possible the changes I made to LibTiny are the reason for your flatline problem, and will thus may also cause a problem using the diff module. I have no idea if my changes are the cause or not. I don't see how, and I don't intend to investigate because the primary BCI2000 developer should be back soon and he will likely make his own changes that will overwrite whatever I have done.
Who is online
Users browsing this forum: No registered users and 0 guests