Contributions:AmpServerProADC

From BCI2000 Wiki
Revision as of 21:09, 10 June 2008 by Jfialkoff (talk | contribs) (ServerIP)
Jump to: navigation, search

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/04/2008 - First working version

Source Code Revisions

  • Initial development: 268
  • Tested under: 1110
  • Known to compile under: 1528
  • Broken since: --

Using the Amp Server Pro Source Module

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 begin, start the Amp Server by double clicking "Amp Server".

Compiling the Amp Server Pro Source Module

The Amp Server Pro Source Module is not considered to be part of the BCI2000 core and must be compiled manually. To compile the Amp Server Pro module you will need Borland C++ Builder v6.0 or later. To proceed, please follow the instructions below:

  1. Navigate to BCI2000/src/contrib/SignalSource/AmpServerPro.
  2. Double click AmpServerPro.bpr to open the Amp Server Pro project file in the Borland C++ Builder.
  3. From the file menu click Project > Make AmpServerPro to compile the AmpServerPro binary.

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. Download the batch file available here and save it to BCI2000/batch/CursorTask_AmpServerPro.bat.
  2. To run the cursor task in BCI2000, double click BCI2000/batch/CursorTask_AmpServerPro.bat. If you prefer to operate under a different paradigm, you can edit either of the last two lines of CursorTask_AmpServerPro.bat to load the appropriate modules.
  3. Click the "Configure" button.
  4. 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 follows.
  5. Click "Set Config". If the operator reports any errors, you must handle these.
  6. Click "Start" to begin your experiment.

Parameters

ServerIP

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 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