From BCI2000 Wiki
Revision as of 14:26, 4 August 2020 by Abelsten (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


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. Amplifiers that record data a administer transcranial direct current stimulation (GTEN devices) are supported.




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

Alex Belsten (, NCAN. (V2)

Version History

  • V1.00 - 06/11/2008 - First working version
  • V2.00 - 05/10/2020 - Added support for GTEN devices and packet format 2

Source Code Revisions

  • Initial development: 1998
  • Tested under: 6138
  • Known to compile under: 6138
  • 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

EGI Amplifier webpage

There are two computers necessary to use AmpServerPro module with BCI2000. One is the iMac Net Station and the other is the client PC on which BCI2000 is installed and run. The Net Station, client PC and the amplifier are all connected to a network switch box. The two computers are connected to the CAT 5 inputs and the amplifier is connected through the fiber optic cable inputs. The client PC's IP address must be configured to allow the amplifier and Net Station to recognize it. On the client PC, configure the IP (IPv4) for a manual IP address (10.10.10.xx where ‘xx’ is any digits other than the last two digits used by the amp); with the manual IPv4 address configured, set the subnet mask to Once this has been completed, open a browser on the client PC and enter the amplifiers IPv4 address into the address bar. If the client PC's IP address is set correctly then the page will populate with information about the amplifier as shown in the figure to the right. If a webpage similar to the one on the right is not shown, then the IP address of the client may not have been set correctly or the client PC has a firewall that is blocking the amp. Verify that the client IP is correct and firewalls have been disabled.

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


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



Enter the number of channels that have electrodes connected (32, 64, 128, or 256). Make sure that SourceChOffset and SourceChGain are set to "auto" or you may get an error message about a mismatching number of entries.


This parameter should always be set to auto. If the amp uses packet type 1 then the block size is fixed at 40 samples per block. If the amp uses packet format 2 then the block size specified by SampleBlockSize will be used. The packet format will be displayed in the operator window of BCI2000 after clicking 'Set Config' and successful connection to amp.


The IP address of the amplifier (e.g.


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-1 where N is the number of amplifiers connected.

Packet Format 2 Parameter


If the connected amp uses packet format 2, then the user can configure the number of samples per block using this parameter.

GTEN Parameters

The GTEN parameters are only used when using a GTEN device. If the connected amp cannot perform stimulation, disable RunTranscranialStim.


Enables stimulation. If stimulation is enabled, the following parameters are used.


The modulation plan file contains all of the information about the stimulation train. This file is created on the Net Station iMac with the EGI program Reciprocity. Reciprocity allows the user to configure all of the parameters of the stimulation train such as electrode location, waveform amplitude, duration, etc. See EGI's GTEN manual for information related to Reciprocity use.

Once the train is designed in Reciprocity, save the .mcb plan and note its location. Copy the .mcb to the client PC. Launch BCI2000 and click the browse button for the ModulationPlanFile parameter. Navigate to the .mcb folder that was written by Reciprocity. Inside this folder, there will be multiple files and two folders. Select the file called 'plan.mcf' upload to BCI2000. DO NOT change any of the contents of the .mcb folder and be sure that ONLY 'plan.mcf' is uploaded.


Expression that triggers stimulation. For more info on expressions, see User Reference:Expression Syntax.



This binary state is set to 1 when stimulation is triggered.


This state is one byte in size and contains information sent back from the amplifier about stimulation. If bit 2 is low (XXXX X0XX) then current is being injected by the amp. If bit 4 is low (XXX0 XXXX) then a new block in the neuromodulation train has just begun.

See also

User Reference:Filters, Contributions:ADCs