- 1 Synopsis
- 2 Location
- 3 Versioning
- 4 Using the Amp Server Pro Source Module
- 5 Parameters
- 6 States
- 7 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: --
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 start the amp server simply navigate to the Amp Server Pro directory and double click the file named "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 from the source code before it can be used. To compile the Amp Server Pro module you will need Borland C++ Builder v6.0 or later. To proceed, please follow the instructions below:
- Navigate to BCI2000/src/contrib/SignalSource/AmpServerPro.
- Double click AmpServerPro.bpr to open the Amp Server Pro project file in the Borland C++ Builder.
- From the file menu click Project > Make AmpServerPro.
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:
cd ..\prog start operat.exe start AmpServerPro.exe 127.0.0.1 start ARSignalProcessing.exe 127.0.0.1 start CursorTask.exe 127.0.0
Then, save the file to BCI2000/batch/CursorTask_AmpServerPro.bat. You may want to modify lines 3 and 4 to suit the needs of your experiment. Please browse the files in BCI2000/batch/ for other example batch files.
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.
- Double click BCI2000/batch/CursorTask_AmpServerPro.bat - the batch file that was created in the previous section - to start BCI2000.
- 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 can be found below.
- Click "Set Config" and attend to any errors reported by the BCI2000 operator. If there were any errors, repeat this step.
- 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.
The Amp Server Pro source module introduces no additional states.