- 1 Synopsis
- 2 Location
- 3 Versioning
- 4 Functional Description
- 5 Using the Amp Server Pro Source Module
- 6 Parameters
- 7 States
- 8 See also
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.
Joshua Fialkoff, (c) 2008 Wadsworth Center, New York State Department of Health.
- V1.00 - 06/04/2008 - First working version
Source Code Revisions
- Initial development: 268
- Tested under: 1110
- Known to compile under: 1528
- Broken since: --
This section comprises a technical description of the Amp Server Pro source module (AmpServerPro.exe). This module has been tested with Amp Server Pro v1.0 beta running on an Intel-based Mac and with BCI2000 running on Windows XP. There is a known issue running both Amp Server and BCI2000 on the same computer via Parallels. That particular configuration is not recommended and may result in unpredictable behavior.
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. When your amplifiers are connected, start the Amp Server by double clicking "Amp Server".
Compiling the Amp Server Pro Source Module
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:
- Download the batch file available here and save it to BCI2000/batch/CursorTask_AmpServerPro.bat.
- 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.
- Click the "Configure" button.
- 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.
- Click "Set Config". If the operator reports any errors, you must handle these.
- Click "Start" to begin your experiment.
IP address of the computer running the Amp Server software (e.g., 192.168.0.3).'
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.
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.
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.
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.
In the case that BCI2000 loses its connection to the Amp Server, a given read request may hang indefinitely. In order to avoid this issue, set the timeout to a value greater than 0. Note the value is interpreted as milliseconds and that 0 disables the timeout.
The Amp Server Pro source module introduces no additional states.