The LyrTech data acquisition system uses TCP connections to transfer data between the various components of the system. As a result these components may be distributed in different workstations but they may all be in the same workstation. The protocols and data format used for these data links is the same in all cases and hence a number of configurations is possible. Two potential configurations are 1) LyrTech cPCI crate (VHS-ADCs) => Data Merge => Data Storage 2) LyrTech cPCI crate (VHS-ADCs) => Data Merge => Event Builder => Data Storage The TCP ports used are defined via configuration files. In the case of the Event Builder the input and output ports can be changed via its GUI. 1) LyrTech cPCI crate This uses 1 TCP connection for each ADC module. Only the destination port number of the first module needs to be defined. The remaining modules use consecutive port numbers. startup file contains configuration information c:\MIDAS\LyrTech\StartUp\RTDEX4.cmd netstring TS_Server "192.168.0.203" defines the IP address or name of the data destination netint TS_Port 11011 defines the first of a group of IP ports for the data destination 2) Merge process This has 1 TCP port for each ADC module to read the data sent by the LyrTech system. input configuration file /MIDAS/Merger/IDS/GS_configuration incoming links defined by statement links 4 /MIDAS/Merger/link64 11011 defines 4 links starting at port 11011 The link software is /MIDAS/Merger/link64 output configuration file /MIDAS/Merger/IDSMerger The Merge combines the incoming data stream into 1 outgoing stream netstring TS_Server "localhost" defines the IP address or name of the data destination netint TS_Port 10305 defines the IP port for the data destination 3) Event Builder process 4) Data Storage process (Tape Server) configuration file /MIDAS/config/TS_10205/TS_configuration The record /MIDAS/TapeServer/Linux64/linkTCP defines the IP port used by data input (default is 10305) The record file_path_base /TapeData defines the base directory used for writing data to disc. Note that this may be a symlink.