# Scope

Data acquisition components (EUDET mode):

• EUDET TLU (Trigger-Busy-Handshake, TriggerIDs, Global busy)
• EUDAQ1 (One DataCollector)

These scheme defines an event and an upper limit of the event rate:

• An event contains one read out frame of each sub-component (for example one trigger, one Mimosa read out frame, one DUT/FEI4 read out frame)
• Trigger rate (= Event rate) is limited by the slowest device (longest busy)

A description for data taking with the AIDA TLU and EUDAQ2 (AIDA mode) is under construction.

# Quick start manual

1. Install sensor planes and DUT(s) and measure distances
2. Switching on the hardware
• sensor cooling
• sensor power
• TLU and PMTs
• control and DAQ computers
3. Running EUDAQ
1. Starting run control components on RC PC
2. Starting senors and TLU components on NI crate
2. Jtagging Mimosa sensors (MI26.exe)
3. Starting EUDAQ NI and TLU producer
3. Configuring EUDAQ
4. Starting data taking ("Start" in EUDAQ)
4. Online monitoring of data taking
5. Switching off software and hardware

# Telescope

## Geometry and telescope resolution

The telescope is positioned on a supporting table (e.g. green DESY xy-support). Furthermore, it is possible to rotate the upper part of the telescope frame, in order to align all 6 telescope planes to the beam axis. This is important for alignment, however, it is usually aligned and users don't need to align the telescope.

The planes are counted from 0 upstream to 5 downstream. The sensor planes can be adjust according to the setup:

• The 3 upstream sensors (0, 1, 2) as well as the 3 downstream sensors (3, 4, 5) can be moved together on their rail on top of a sensor tower. It is recommended to move the rails in such a way that the distance of sensor 2 to the DUT and 3 to the DUT is as small as possible.
• The distances between the 3 sensors (upstream and downstream) can vary between a minimum of 2.5 cm and a maximum of 15 cm and the distance between the inner planes for integrating your DUT can be up to 50 cm at least. This geometry defines your telescope resolution. The best configuration (highest resolution) also depends on the thickness of the DUT ($X_0$) and the beam energy. Check out your specific geometry by reading/using:

Please measure the distance between each plane, measuring from one side of a plane to the same side of the following plane. This is important, if you analyse your data e.g. with EUTelescope.

## Material Budget

Test beam particles traverse:

• 2 scintillators
• 6 sensor planes
• 2 scintillators

A scintillator incorporates:

• 2-3 layers of 3M Vinyl tape (single thickness 0.177mm)
• 1 layer of 0.033mm thick PET radiant light film
• 3.0mm thick BC408 (scintillator)
• 1 layer of 0.033mm thick PET radiant light film
• 2-3 layers of 3M Vinyl tape (single thickness 0.177mm)

(Some scintillators are wrapped differently, using black shrinkable tubing e.g.).

A sensor plane incorporates:

# DUT integration

## Mechanical integration

The mechanical installation is quite flexible for the user. $$xy\phi$$-stages are provided for mounting the DUT and moving them remotely, see Hardware#PI-stages for moving DUTs. Find here a drawing of the angle with threads positions for mounting your DUT: File:Angle bracket.zip.

## EUDAQ integration

See, chapter 4 in the manual of EUDAQ#Introduction and Manual.

## PC integration in the local network

The telescope infrastructure provides a local network, typically in a format like 192.168.X.XXX. Telescope PCs have a fixed, manually assigned IP address. Users can integrate their PCs by setting a free IP address and connect their PC to the switch of the PC crate in the beam area or the switch located in the hut.

### Which IPs are free?

IPs of Telescope PCs, see the individual telescope pages (via Main Page).

Fast network check with nmap, e.g. for DATURA:

teleuser@fhltb21:~$nmap -sP -PS22,3389 192.168.21.1/24 Starting Nmap 6.40 ( http://nmap.org ) at 2015-07-01 17:31 CEST Nmap scan report for 192.168.21.1 Host is up (0.00017s latency). Nmap scan report for 192.168.21.2 Host is up (0.00060s latency). Nmap scan report for 192.168.21.3 Host is up (0.00038s latency). Nmap scan report for 192.168.21.251 Host is up (0.00028s latency). Nmap done: 256 IP addresses (4 hosts up) scanned in 3.01 seconds  ### Other helpful settings • Setting two IP's having one network card (in Ubuntu): sudo ifconfig eth0:1 192.168.x.xxx netmask 255.255.255.0 up # Switching on the hardware Usually the telescope is already turned on when you start data taking, but the situation might arise that the hardware is partially or completely turned off. Then you can refer to this section to make sure that you do it correctly. ## Sensors ### Cooling To switch on the minichiller: • Check the water level at the front panel. (The device stops cooling if the level is too low and will emit an alarm sound. Remember that the sound is probably not audible in the control room.) • Switch on the main switch. • Press and hold down the Set button • Adjust the temperature using the arrows to 15$^{\circ}$C (or higher if the ambient temperature is high) • Release the Set button • To start the pump press and hold the button on the right until it switches on ### Power To power the sensors in "standby" • Press the main power button of the power supply (Agilent E3644A) • Press the Recall button two times and see if 8 V is set already, otherwise.. • Press the Set Limits button. Verify the limit is 4.0 A on the power supply. • Set the voltage to 8 V. • Enable the output using the Output On/Off button. • Enable the green light button at the cable panel below the Agilent PS, see picture. • The currents will rise to approximately 2.0 A and later to 3.7 A when switching on the sensors, see below. Powering Mimosas at DESY's telescopes ## Trigger Logic Unit (TLU) and PMTs • For the Hardware#EUDET TLU: Check USB connection to the NI crate (or Run Control PC) and power supply at the rear side. • For the Hardware#AIDA TLU: Check the network connection to the Run Control PC and power supply at the rear side. • Check the PMT connections: power (4pin LEMO in "LV-Out") and signal (standard LEMO in "PM in"). ## Computers • Hardware#NI crate in the beam area • If the PC is off, switch on by pushing the white button in the the lower left corner of the front panel. • Login as telescope user (get the password from telescope_coor@desy.de). • Hardware#RunControl PC in the beam area • If the PC is off, switch on. • Login as telescope user (get the password from telescope_coor@desy.de). • Hardware#Terminal PC in the hut • If the PC is off, switch on. • Login as telescope user (get the password from telescope_coor@desy.de). # Running EUDAQ 1 To start the data taking, all necessary telescope components of EUDAQ have to be running properly: run control, data- and log-collector, onlinemonitor and all hardware producers. We describe the standard runs to check, if the telescope is working: telescope_autotrigger.conf without beam and telescope_beam.conf with beam. To run with a DUT or more, you have to integrate your DUT hardware, DAQ and EUDAQ producer - however, the procedure is analogous. Here in a nutshell, below in detail: 1. #Starting run control: ssh to RunControl, start ./STARTRUN.default 2. #Preparing hardware and starting EUDAQ producers • Mimosa26 sensors: remote desktop to NI crate • start MimosaDAQ.exe • Jtag: start MI26.exe, open mcf-file, press "All", "Read", "Start" • NI and TLU EUDAQ producers: start_EUDAQ_ni_tlu.bat 3. #Configuring EUDAQ: euRun: select conf-file and "Configure" 4. #Starting data taking: euRun: "Start" ## Starting run control For example at DATURA, From the Terminal PC in the hut, you can access remotely the Run Control PC which controls your data taking as well as store the data physically: • Open a terminal and connect to RunControl PC (192.168.21.1): ssh -X teleuser@192.168.21.1 • Start 4 EUDAQ components: euRun.exe, euLog.exe, TestDataCollector.exe, OnlineMonitor.exe: • cd eudaq/etc/scripts • ./STARTRUN.telescope (Optionally, you can start the processes step-by-step manually; therefore, have a look in a STARTRUN-script.) If every component starts properly, you should see three windows: #### Troubleshootings • Not starting in general: Check, if the correct IP-address (NOT the computer name and NOT the localhost 127.0.0.1) is set as HOSTNAME in the STARTRUN-script or as option (-a / -r). • error while loading shared libraries: libCore.so.5.34: Root paths are missing, execute the following script to set the right PATH and LD_LIBRARY_PATH: setup_eudaq.sh or ilcsoft/v01-1X-XX/root/5.XX.XX/bin/thisroot.sh (with right version number instead of X's) • Problems with DataCollector: Check, if eudaq/data is a correct link to a writeable destination. ## Preparing hardware and starting EUDAQ producers Besides the EUDAQ run control, the EUDAQ producers for hardware components have to be running. We explain it for the Mimosa26 sensors (telescope planes) and for the TLU, however, it is the same procedure for a DUT or any other hardware: • Start hardware (power and DAQ). • Start EUDAQ producer communicating with hardware DAQ and EUDAQ run control. ### Mimosa26 sensors The Mimosa sensors are operated and read out by a FPGA and software infrastructure which is running on the NI crate. For example at DATURA at the Terminal PC (fhltb21: • Open Remmina (remote Desktop) and connect to NI crate (192.168.21.2) operated by Windows 7 #### 0. (Starting the FPGA) The FlexRIO board of the NI crate processes the Mimosa26 sensor data. Therefore, the FPGA has to be programmed correctly ("Download Bitfile to flash"). However, it is usually not necessary to flash the FPGA , since this will be usually done automatically, after booting the NI crate. If not, do the following: • Open "RIO Device Setup" • Select the "Resource" from the pull-down menu, usually "RIO0". • After clicking the folder icon, browse to the path of the bitfile "anemone.lvbitx". • Click the "Download Bitfile" button. • Select the "Device Settings" tab and select "Autoload VI on device powerup". • Click the "Apply Settings" button. • Click the "Exit" button. Now the NI-crate will load the bitfile to the FPGA, flash memory and run the FPGA. #### 1. Starting MimosaDAQ The "MimosaDAQ" is a LabView programme providing the communication between the FPGA onthe NI FlexRIO and the NI producer (EUDAQ producer for Mimosa26 sensors). You have to start it, before starting the NI producer: • Click on shortcut at Desktop "MimosaDAQ" (starts the program "anemone_v1.3.exe") • When opened, it should be running properly: black single arrow, white double arrow, red stop point. Here you find a documentation on the Anemone LabView interface: File:Artemsdocumentation.pdf ##### Troubleshootings • If a red light is on on the left, an error occured, and you should reset MimosaDAQ by clicking red stop point and twice double arrow. Known errors are e.g.: • "DataTransportListener" due to wrong TCP/IP settings in EUDAQ configuration • "ErrorConfig Socket" due to occupied port. • On the left, the fields after "MIMOSA_X" (X = 1, 2, 3, 4, 5, 6) displays the header of the Mimosa26 data, if EUDAQ processes data. It should be 555X5555 for each sensor, otherwise, there is something wrong. #### 2. Starting sensor: MimosaJTAG The Mimosa26 sensors are programmed via JTAG using the parallel port of the NI-Crate. To program and start the sensors, the software "Mimosa36 JTAG Master Configuration" (MimosaJTAG) is used. During this process, it is recommended to check the sensor current by eye looking at the display of the sensors' Hardware#Power supply (in the area or via camera in the hut) or using a "Keysight BenchVue" software which can control and monitor the Hardware#Power supply via GPIB (at PC, e.g. in the hut): To start the sensors ("jtagging"), do the following: 1. The Hardware#Power supply for the Mimosa26 sensors and all supporting boards (Hardware#Sensors and periphery) should be switched on. If not, see #Power. The total current of the boards and 6 sensors is ~2.0 A (standby). 2. Open "MimosaJTAG" (using "Mi26.exe p:0x378" as command to avoid the pop-up window). Two windows will open, a main window (left) and a second window with all the register settings (right). For normal operation, the main window only is required. 3. Load a threshold mcf-file (threshold 5 or 6 is recommended): Click "Open" in "Master Configuration" section and select a file from the JTAG-folder. 4. Press "All", "Read" and "Start" (from right to left!) in "Device Update" : 1. Press "All" to send register settings to sensors, the current should increase to ~2.9 A ("All"). 2. Press "Read" to read registers as cross-check. The current should shortly change, but stay at ~2.9 A ("Read"). 3. Press "Start" to start the rolling shutter read-out of the sensors. The current should be at ~3.6 A ("Start"). Now you can start the NI producer (#3. Starting EUDAQ NI producer). After that, configuring (#Configuring EUDAQ) and starting EUDAQ (#Starting data taking), Mimosa26 data will also be processed and saved. 5. Repeat 3. and 4. for using another threshold. If you want to stop the sensors (see also #Switching off the hardware), press "Reset". The current should be ~2.0 A (standby). ##### Troubleshootings • Standby current is not ~2.0 A: Check if each plane has a standby current of ~300 mA by plugging in plane-by-plane. • Error(s) are read back during jtagging indicated at the bottom line of "MimosaJTAG" after pressing "Read": • Repeat: "Reset", "All", "Read" --> errors? • Power cycle: "Reset", switch Hardware#Power supply off and on, "All", "Read" --> errors? • Not starting, not reaching ~3.6 A: • Check if power supply is switched on. • Check connection of all power cables. • Check all RJ45 signal cables are properly connected to its connectors. • In any case never change the sensor order! #### 3. Starting EUDAQ NI and TLU producer After starting the MimosaDAQ (anemeone.vi LabView program) and starting the Sensors ("Jtagging"), you should start the NIProducer, which is the EUDAQ component running on the NI crate and communicating via TCP/IP to the run control (euRun.exe). Since the TLU is also connected to the NI crate via USB, usually you start both producers using a bat-script in the EUDAQ bin-folder or the link on the desktop containing:  :: set the IP from RunControl PC set RUNCONTROL=192.168.X.1 start NIProducer.exe -r tcp://%RUNCONTROL%:44000 timeout /T 2 > nul start TLUProducer.exe -r tcp://%RUNCONTROL%:44000  This starts the NIProducer and the TLUProducer (EUDAQ component of Hardware#Trigger Logic Unit) on the NI crate. After a successful start, you will see the producers in the euRun.exe: ##### Troubleshootings • NIProducer or TLUProducer don't start and are not connecting to euRun.exe: Check the TCP/IP connection/communication: • Can you ping the run control (euRun.exe) from the NI crate and vice versa? • Is the environment variable RUNCONTROL correct (IP of run control PC with "euRun.exe")? • NIProducer or TLUProducer are not found: Check if you have a properly compiled EUDAQ version, see EUDAQ#Cmake options. ### DUT(s) ## Configuring EUDAQ After successfully starting all EUDAQ components and producers, EUDAQ components can be initialized (just a default/empty telescope.init file) and configured. Each component has options which are set in the config-files (*.conf) in the conf-folder. In the following, we explain two configurations: • telescope_autotrigger.conf: This is an important functionality test of the telescope. Using no beam, triggers produced by the TLU internally are sent to test the data taking (EUDAQ event building). • telescope_beam.conf: This is the functionality test with beam. PMTs/scintillators in coincidence are used to produce triggers for event building. Both configurations can be used as template for DUT integration, EUDAQ with an integrated DUT is configured analogously. ### telescope_autotrigger.conf The content of the conf-file is: [RunControl] RunEventLimit = 1000000 NoTrigWarnTime = 10 [LogCollector] SaveLevel = EXTRA PrintLevel = INFO [DataCollector] FilePattern = "../data/run$6R$X" [Producer.TLU] # Auto trigger with interval in units of ms TriggerInterval = 1 # Activate DUT Channel 0 -> only telescope DutMask = 1 # Don't power PMTs: Set Control Voltage to 0 mV PMTVcntl1 = 0 PMTVcntl2 = 0 PMTVcntl3 = 0 PMTVcntl4 = 0 [Producer.MimosaNI] # Set here the local IP of the NI crate on which MimosaDAQ (Anemone LV) is running NiIPaddr = 192.168.22.2 #TriggerType = 1 Det = MIMOSA26 Mode = ZS2  The structure incorporates the names of each EUDAQ component (in brackets []), followed by the appropriate options. If a option is not in the file, EUDAQ will use the default value, which is hard-coded in the corresponding source code. The relevant options for autotriggering are: • TriggerInterval: If TriggerInterval is a nonzero value in units of milliseconds, the TLU produces triggers internally. The minimum value is 1, which provides a 1 kHz trigger rate. • DutMask: This option activates DUT interface channels at the TLU by using bit mask. Usually, the Hardware#Data reduction board of the Mimosa sensors is connected to the channel 0. Thus, running EUDAQ only reading out the sensors corresponds to a DutMask = 1. After pressing "Config" in euRun.exe, the RunControl and the MimosaDAQ change their state: ### telescope_beam.conf To activate the external trigger inputs -- at the telescope, the inputs of the four PMTs/scintillators, the OrMask or the AndMask has to be activated: [Producer.TLU] # Activate DUT Channel 0 -> only telescope DutMask = 1 # Set coincidence of all 4 scintillators/PMT inputs, bitmask = 1 + 2 + 4 + 8 AndMask = 15 # Set Control Voltage in mV (default) PMTVcntl1 = 800 PMTVcntl2 = 800 PMTVcntl3 = 800 PMTVcntl4 = 800  TriggerInterval is set to 0, since triggers should now be produced by external input. Usually, a four-coincidence input is used, thus, AndMask = 15, see bit mask. ### Important options to adjust Besides the individual DUT options, the most important options for the user are: [RunControl] RunSizeLimit = 100000000  or [RunControl] RunEventLimit = 10000  RunSizeLimit sets the maximum size of raw data files in units of bytes. 100000000 corresponds to 100 MB, which is recommended by default. After reaching this file size, RunControl (euRun.exe) increments the run number automatically and creates a new raw data file. Or, you can also set RunEventLimit, which gives the events for a run, before starting the next run. [RunControl] NextConfigFileOnFileLimit = 1  Setting NextConfigFileOnFileLimit to 1 activates a "DUT parameter scan": After reaching a limit, RunControl will re-configure by using the next (alphabetically ordered) conf-file in the conf-folder. [DataCollector] FilePattern = "../data/run$6R\$X"


Using the FilePattern option, you can change the file name pattern and/or the data-directory, which is eudaq/data by default. At the moment, the OnlineMonitor only looks in the eudaq/data-folder, thus, it is recommended to use a soft link instead of the FilePattern option, e.g. for DATURA RunControl PC on which a Raid is mounted at /data2:

mkdir /data2/data_2015/YOUR_FOLDER
ln -e /data2/data_2015/YOUR_FOLDER /opt/eudaq/data

[Producer.MimosaNI]


NiIPaddr sets the IP address of the NI producer. Usually, this is already set in the default conf-files of the corresponding telescope setup.

[Producer.TLU]
DUTInput3 = LEMO


AndMask: If a PMT/scintillator device is not working (e.g. a "Scalers" value is not incrementing), you can deactivate a channel by setting the appropriate bit mask. DutMask: If you integrate your DUT and connect it to the Hardware#Trigger Logic Unit, you have to activate the corresponding channel, see bit mask. DUTInput: You can activate the DUT LEMO interfaces 0-3, here e.g. channel 3.

### Troubleshootings

• NIProducer crashes during configuring: Check the IP address in the EUDAQ conf-file. It should be the IP of the NI crate where the NIProducer is running:
 [Producer.MimosaNI]


## Starting data taking

After successfully configuring all EUDAQ components and producers, EUDAQ data acquisition can be started by pressing "Start". If everything works correctly, "Triggers" and "Events Built" values are incrementing equally, e.g. for autotrigger data taking:

You can stop the data taking by "Stop", and e.g. reconfigure by selecting an updated conf-file and restart data taking "Start".

##### Troubleshootings
• No event building by EUDAQ ("Events Builts" is not incrementing):
• If "Trigger" are not incrementing, check if trigger logic (AndMask) is set correctly,
• if "Trigger" are incrementing but no events are built, check if the headers are properly found by "MimosaDAQ". The Mimosa Headers are 555X5555 with X being the sensor number and should appear in the upper left column of the LabView window. If there are 0 in , please try to restart everything:
• Power cycle the #Mimosa26 sensors and restart the programs incl. EUDAQ (Step 1, 2 and 3)
• (Only sometimes working: Download the FPGA Bit-File, see #0. (Starting the FPGA)
• If this is not helping, reboot the NI crate: Shutdown, wait 2-3 minutes, restart.
• Check connection of red data cables.
• Event size meter over 1000 and data taking is stopping after few seconds. The data flow of the sensor read-out is too hight, maybe due to:
• wrong Jtag files, broken pixel-columns not deactivated
• not working Aux board
• ao problem

## Online Monitoring

At the moment, the OnlineMon.exe only runs on Unix operation systems properly. Therefore, we recommend to run the euRun.exe, euLog.exe, TestDataCollector.exe and OnlineMon.exe on a Unix machine.

TODO: example picture

## Stop Run, Re-Configure, Terminate

under construction

# Running EUDAQ 2

Installations on the RunControl PC:

• EUDAQ2 installation in /opt/eudaq2/
• Ipbus/Cactus installation int /opt/cactus/

Start

• source /opt/eudaq2/user/eudet/misc/environments/setup_eudaq2_aida-tlu.sh
• cd /opt/eudaq2/user/eudet/misc/starting_scripts
• decide: multiple data collectors or one data collector
• choose a starting script
• choose the corresponding conf file

# Switching off software and hardware

You should ask telescope-coor@desy.de in which state you should set the telescope after test beam week. If necessary, you can power down the whole system.

## Stopping data taking

• "Stop" EUDAQ and "Terminate"

## Sensors

• Stopping sensors: On the NI crate, in the JTAG pgrogramm "MIMOSA26 JTAG Master Configuration", press "Reset" button in the bottom left corner.
• Switching off power: Press "ON/OFF" switch to set 0 V at the Agilent power supply. Press main switch.
• Cooling: Press main switch at the Huber minichiller.

## PI Stages

• Moving down $$y$$-stage: Use the software PIMikroMove.
• Switching off power of stages: Unplug the power of the $$x$$- and $$y$$-stage. Support the $$y$$ stage, it might be fall down, if there is a heavy DUT installation!
• Switching off power of controllers by unplugging.

## TLU

Unplug the power supply connector on the back.

## Computers

Remember to copy your data in eudaq/data-folder and your conf-files and maybe log-files!

You get the passwords from the coordinators (telescope-coor@desy.de). Choose remote or direct shutdown:

• NI crate (Windows)
• remotely: "teleuser" login via Remmina from Terminal PC and shutdown
• directly: "teleuser" login and shutdown
• Run Control PC (Ubuntu)
• remotely: "telescope-admin" login via "ssh 192.168.21.1" from Terminal PC and "sudo shutdown now"
• directly: "telescope" login and shutdown

In addition, set each main switch to off.