Difference between revisions of "Contributions:AmpServerProADC"

From BCI2000 Wiki
Jump to: navigation, search
(Creating a BCI2000 Batch File)
 
Line 24: Line 24:
  
 
===Creating a BCI2000 Batch File===
 
===Creating a BCI2000 Batch File===
Although it is not necessary, it is convenient to create a batch file to run BCI2000 with the Amp Server Pro module.  To create the batch file, open up a text editor and then copy the text below into a blank text file:
+
Although it is not necessary, it is convenient to create a batch file to run BCI2000 with the Amp Server Pro module.  To create the batch file, start out with a copy of a suitable batch file in <tt>BCI2000/batch/</tt>, and open it in a text editor.
cd ..\prog
+
 
start operat.exe
+
Towards the end of the file, you will see a sequence of lines beginning with
start AmpServerPro.exe 127.0.0.1
+
  start executable
start ARSignalProcessing.exe 127.0.0.1
+
 
start CursorTask.exe 127.0.0
+
These lines are responsible for starting up source, signal processing, and application module, in that sequence. To use the AmpServerPro module, you will need to replace the executable name in the first entry, e.g.
Then, save the file to <tt>BCI2000/batch/CursorTask_AmpServerPro.bat</tt>.  You may want to modify lines 4 and 5 to suit the needs of your experimentPlease browse the files in <tt>BCI2000/batch/</tt> for other example batch files.
+
  start executable SignalGenerator --local
 +
becomes
 +
start executable AmpServerPro --local
 +
 
 +
For more information, see [[Contributions:How_to_use_a_Contributed_Source_Module#Creating_batch_files|this page]].
  
 
===Using Amp Server Pro with BCI2000===
 
===Using Amp Server Pro with BCI2000===

Latest revision as of 15:42, 24 October 2013

Synopsis

The AmpServerProADC component implements the client side of EGI's TCP/IP-based Amp Server Pro (ASP) protocol. Thus, it may be used to interface BCI2000 with an EGI amplifier managed by an ASP server.

Location

http://www.bci2000.org/svn/trunk/src/contrib/SignalSource/AmpServerPro

Versioning

Author

Joshua Fialkoff, (c) 2008 Wadsworth Center, New York State Department of Health.

Version History

  • V1.00 - 06/11/2008 - First working version

Source Code Revisions

  • Initial development: 1998
  • Tested under: 1998
  • Known to compile under: 1998
  • Broken since: --

Using the AmpServerPro Source Module

For using the AmpServerPro source module, you will need to obtain a license for the AmpServerPro SDK. Without such a license, you may be able to connect to the machine running the EGI software, but it will not send any real time data when asked to. In order to obtain an AmpServerPro SDK license, you will need to contact EGI at http://www.egi.com.

Starting Amp Server Pro

Amp Server Pro is capable of working with many amplifiers concurrently. To begin using Amp Server Pro with BCI2000, ensure that at least one amplifier is connected to the server. If no amplifier is connected, the Amp Server software emulates an amplifier. If you choose to use the emulated amplifier, you should expect to see a smooth sine wave signal for all channels. To start the amp server simply navigate to the Amp Server Pro directory and double click the file named "Amp Server".

Creating a BCI2000 Batch File

Although it is not necessary, it is convenient to create a batch file to run BCI2000 with the Amp Server Pro module. To create the batch file, start out with a copy of a suitable batch file in BCI2000/batch/, and open it in a text editor.

Towards the end of the file, you will see a sequence of lines beginning with

start executable 

These lines are responsible for starting up source, signal processing, and application module, in that sequence. To use the AmpServerPro module, you will need to replace the executable name in the first entry, e.g.

start executable SignalGenerator --local

becomes

start executable AmpServerPro --local

For more information, see this page.

Using Amp Server Pro with BCI2000

Once you have started the Amp Server and compiled the Amp Server Pro module, you can begin collecting data with BCI2000 by following the steps below.

  1. Double click BCI2000/batch/CursorTask_AmpServerPro.bat - the batch file that was created in the previous section - to start BCI2000.
  2. Click the "Configure" button.
  3. Set the appropriate parameters. The Amp Server Pro module is initialized with a number of parameters which can be configured from the "Source" tab. A summary and description of these parameters can be found below.
  4. Click "Set Config" and attend to any errors reported by the BCI2000 operator. If there were any errors, repeat this step.
  5. Click "Start" to begin your experiment.

Parameters

ServerIP

The IP address of the computer running the Amp Server software (e.g., 192.168.0.3).

CommandPort

The port number of the port used for command layer communication. Unless you have explicitly set the port number via Amp Server's configuration, the default of 9877 should be correct.

NotificationPort

The port number of the port used for notification layer communication. Unless you have explicitly set the port number via Amp Server's configuration, the default of 9878 should be correct.

StreamPort

The port number of the port used for data streaming. Unless you have explicitly set the port number via Amp Server's configuration, the default of 9879 should be correct.

AmplifierID

Amp Server Pro is capable of managing many amplifiers concurrently. BCI2000, however, operates with a single amplifier. If only a single amplifier is connected, you may enter the value "auto" here and allow BCI2000 to automatically determine the Amplifier ID. If multiple amplifiers are connected, however, you must enter a valid ID from 0 to N-1 where N is the number of amplifiers connected.

States

The Amp Server Pro source module introduces no additional states.

See also

User Reference:Filters, Contributions:ADCs