I am trying to set up the BCI2000 to record VEPs on the Measurement Computing USB-2537 DAQ and I was wondering what would be the best way to go about doing this?
Thanks,
Rebekah
Measurement Computing USB-2537 DAQ
-
griffin.milsap
- Posts: 58
- Joined: 08 Jun 2009, 12:42
Data Acquisition
Hello Rebekah,
First off, might I say that that is a mighty fine board you have there. I'm jealous!
I took a look through the user manual and saw that it should come with drivers. I didn't see whether or not it came with an SDK, but that'd be pretty helpful.
You'll probably want to develop a source module for your device. There's a handy tutorial here: http://www.bci2000.org/wiki/index.php/P ... ion_Module. You'll likely need to include some headers and link to a few provided libraries, but once you have the project set up correctly, you should be able to access the board's output and feed it into BCI2000.
If you don't have an SDK, you'll have to write a C interface for the board based on the product specifications. This could be tricky, so I'd advise you to look for an SDK.
Good luck,
-Griff
First off, might I say that that is a mighty fine board you have there. I'm jealous!
I took a look through the user manual and saw that it should come with drivers. I didn't see whether or not it came with an SDK, but that'd be pretty helpful.
You'll probably want to develop a source module for your device. There's a handy tutorial here: http://www.bci2000.org/wiki/index.php/P ... ion_Module. You'll likely need to include some headers and link to a few provided libraries, but once you have the project set up correctly, you should be able to access the board's output and feed it into BCI2000.
If you don't have an SDK, you'll have to write a C interface for the board based on the product specifications. This could be tricky, so I'd advise you to look for an SDK.
Good luck,
-Griff
-
griffin.milsap
- Posts: 58
- Joined: 08 Jun 2009, 12:42
As far as I'm aware, there are no pre-built signal acquisition modules in the core distribution or contrib branch which will work for this device. You will have to write and build your own executable.
I would read through the SDK documentation, and plan out what parameters you'll need for BCI2000 to set up the hardware and what needs to happen at the hardware level during the preflight, initialization, and runtime phases. Look through the tutorial I posted above for an example. You'll likely be able to use much of this as your code and only change certain parts to work with your API.
You'll have to use Borland to compile your executable with the BCI2000 framework. Hopefully you have a bunch of .lib files and .h files that you can use to link your project. If you've got a more advanced API which uses COM objects or ActiveX, you may run into problems with Borland's import procedure.
Only one more thing to note here, is that Borland likes OMF formatted .lib files, and its likely that you've got COFF formatted .libs. You'll be able to tell when Borland tells you that your .lib is mal-formatted or corrupted. There is a simple executable called "coff2omf" shipped with Borland to do conversion from a COFF formatted library to an OMF formatted library.
That ought to do it. Good luck!
-Griff
I would read through the SDK documentation, and plan out what parameters you'll need for BCI2000 to set up the hardware and what needs to happen at the hardware level during the preflight, initialization, and runtime phases. Look through the tutorial I posted above for an example. You'll likely be able to use much of this as your code and only change certain parts to work with your API.
You'll have to use Borland to compile your executable with the BCI2000 framework. Hopefully you have a bunch of .lib files and .h files that you can use to link your project. If you've got a more advanced API which uses COM objects or ActiveX, you may run into problems with Borland's import procedure.
Only one more thing to note here, is that Borland likes OMF formatted .lib files, and its likely that you've got COFF formatted .libs. You'll be able to tell when Borland tells you that your .lib is mal-formatted or corrupted. There is a simple executable called "coff2omf" shipped with Borland to do conversion from a COFF formatted library to an OMF formatted library.
That ought to do it. Good luck!
-Griff
-
mellinger
- Posts: 1341
- Joined: 12 Feb 2003, 11:06
Rebekah,
the BCI2000 DAS_ADC contribution was written to interface with Measurement Computing boards, using the MMC universal library.
However, it has not been tested with newer boards. For more details, see
http://www.bci2000.org/wiki/index.php/C ... ns:DAS_ADC
HTH,
Juergen
the BCI2000 DAS_ADC contribution was written to interface with Measurement Computing boards, using the MMC universal library.
However, it has not been tested with newer boards. For more details, see
http://www.bci2000.org/wiki/index.php/C ... ns:DAS_ADC
HTH,
Juergen
Who is online
Users browsing this forum: No registered users and 0 guests