ATLAS-SBM1-AIDA TELESCOPE USER GUIDE

SBM-AIDA Telescope


INTRODUCTION

This document contains a step-by-step user guide for operating the SBM-AIDA telescope built by the PH-ADE-ID CERN group. Documentation about the SBM-AIDA telescope itself can be found here: https://indico.cern.ch/event/361445/session/7/contribution/128/material/slides/0.pdf
At the end, the Miscellaneous section describes some tools that may be useful for the user as doing a shift remotely, or converting rce/txt data into Judith compatible data.

In case of problems during the shift, please contact: Matevz Cerv (166440), Malte Backhaus (167010), or Sonia Fernandez (168601).

NETWORK CONNECTIONS

Make sure you can internally access from your client PC to the laptop HP, Lecroy Waverunner (if needed) and Laptop HP 8530p.

Device Description Internal IP
Laptop HP

scvd-id.cern.ch

Laptop HP, Linux SLC6
Telescope DAQ, DUT DAQ, DHCP server. Connexion
through VPN (username: testbeam password:B3@mTe$t)

192.168.2.100
Lecroy Waverunnner 204 MXi Oscilloscope, Windows XP
DUT DAQ, FTP server (username: testbeam password:testbeam)
192.168.2.110
Telescope DAQ CIM13 192.168.2.113
RCE12 (DAQ for telescope 2) 192.168.2.12
RCE12 (DAQ for telescope 1) 192.168.2.13
Laptop HP 8530p Windows 7
High Voltage controller. Access through remote desktop connection (username: LocalAccount password:testbeam)
192.168.2.101
USB dongle Client access to the network 192.168.2.200

How to connect externally to the DAQ pc is explained in miscellaneos section.

SETTING UP HIGH VOLTAGE CONTROL

The ISEQ power supply will provide HV to the telescope from one of the channels, the other channel can be used to provide HV to a DUT if needed. Follow the instructions bellow for setting up and monitoring the ISEQ device.

In order to switch the polarity, a knob at the back of the ISEG power supply has to be switched to POSITIVE. Don’t do this for the telescope on CH1!

The computer(Laptop HP 8530p) is accessible even when its lid is closed.

  1. Make sure that ISEG power supply is ON. Set the knobs to 0 V, Switch to DAC mode for both channels and switch the HV ON.
  2. Make sure the ISEG is connected to PC via a USB-to-RS232 cable.
  3. Connect to the PC using Remote Desktop Connection (ip: 192.168.2.101)
  4. Open ISEG Monitor (shortcut on the desktop)
  5. Main menu: Monitor -> Connect Device.
  6. Choose COM port 4, timeout 10 s.
  7. Set Vset to 0 V and Vramp to 10 V for both channels.
  8. Main menu: Channel -> Set Names. Channel 1 = Telescope. Channel 2 = DUT
  9. Main menu: Monitor -> Start monitor.
  10. Set Vset for Telescope to -60 V while observing the display.
  11. Set Vset for DUT to whatever you need.

SETTING UP THE ANALOG READOUT

OSCILLOSCOPE

If your DUT is not a single pad (eg: Diamond) or a single pixel (eg: XFAB), skip this section.

  1. Switch on the oscilloscope.
  2. Make sure it’s connected to the switch with an Ethernet cable.
  3. Check its IP (via Command prompt using ipconfig –all or in the DSO, tab Utilities -> Utilities setup -> Remote. It has to be 192.168.2.110.
  4. Try pinging it from the client PC.
  5. (optional) check the connectivity with ./testbeamController software.
  6. Connect to the oscilloscope using RDC (IP: 192.168.2.110, username: Testbeam, password: the funny one).
  7. If the DSO keeps crashing, it’s due to its display settings that need to be changed manually. Tab Utilities -> Preference setup -> Optimise for Analysis
  8. FTP SERVER: Start -> Programs -> FileZilla Server -> Start FileZilla Server (+ Interface)
  9. Get ready to take data: Main menu: File -> Save waveform

DRS4

The DRS4 software is installed on the DAQ pc.

1. Open a terminal and type:

- cd

-cd DRS/drs-5.0.3

-sudo ./drsosc

-Note: xhost+local:

2. The DRS4 behaves as an oscilloscope, much faster but it has some other limitations.

-fix the input range (-0.5, 0.5V)

-choose your channel and set you volt/time range (!! note: the biggest time window that can be set is 1.5us)

-set the trigger to "normal"

-Choose external trigger "E"

3. For saving data and data acquisition

- click the "save"bottom and create a new folder. Select the kind of file to be saved ".dat" and give a name to your file

-Select the num maximum of events to be saved (note: This is tricky. If the DRS4 reaches that number it fill not save the events anymore, but the RCE will go on running)

-Click "run"

SETTING UP TELESCOPE RCE READOUT

From the DAQ Laptop (Laptop HP), to run the Telescope RCE readout:

  1. $ cd
  2. $ sudo /etc/init.d/iptables stop
  3. $ sudo /etc/init.d/dhcpd restart
  4. $ source StartPartition
  5. $ source RCEloader 12 13
  6. $ calibGui &
  7. $ cosmicGui &
RCE settings for different setups:

- Triggering on DUT: Consec. trgs: 16, Trg delay 223, HB delay D+ 0, HSIO Ext 1, Oscilloscope: Trig on C3!

- Triggering on HB w/ DUT: Consec. trgs: 4, Trg delay 223, HB delay D+ 3, HSIO Ext 1, Chip2 (Chip2)

- Triggering on HB w/o DUT: Consec. trgs: 4, Trg delay 226, HB delay D+ 0, Hitbus (Chip2)

Oscilloscope Controller

If your DUT DUT is not a single pad (eg: Diamond) or a single pixel (eg: XFAB), skip this subsection.

TestbeamControl --> to run the oscilloscope controller:

  1. $ cd ~/AIDA/DUT/controller
  2. $ ./testbeamControl <sampleName> <biasVoltage> <DOSdirectoryOnOsc> <runNumber>
<sampleName> and <biasVoltage> can be arbitrary as they are not used in the program.

<DOSdirectoryOnOsc> The directory has to have the following format: D:\\Testbeam\\Diamond\\2014-10-23. It also has to be created MANUALLY on the oscilloscope (winXP). The resulting data folder for each run will then be D:\Testbeam\Diamond\2014-10-23\RUNxxxxxx\, which will include all binary files from one run. Directory RUNxxxxxx is created automatically.

  1. Program usage: in the prompt, enter “panel” to choose between panels “Matevz” and “Sonia”.
  2. Change the directory on the oscilloscope’s tab “Save Waveform” to that output by the program
  3. When a run was started in cosmicGui, enter “acq” to start acquiring data.
  4. To stop the acquisition, FIRST stop the cosmicGui run and then enter “endacq” in the program.
  5. To send the data from the run that just finished from the oscilloscope to the DAQ PC (scvd-id), enter “senddata”.
  6. Repeat 4-7. The run number will increase automatically and a folder RUNxxxxxx will be created.
  7. Enter “quit” to exit the program.

DATA TAKING

  1. Make sure you have the following windows open:
    a. DAQ PC via VNC client
    i. terminal for RCE readout + cosmicGui
    ii. terminal for testbeamControl
    b. Oscilloscope via RDC with tab “File->Save waveform” open
    c. HV PC via RDC

  2. Check that cosmicGui has the right data folder (date).
  3. If testbeamControl hasn’t been started yet, start it and set the panel (only for oscilloscope users)
  4. Start run in cosmicGui.
  5. Start run in testbeamControl by entering “acq” (only for oscilloscope users)
  6. To end the run, enter “endacq”. (only for oscilloscope users)
  7. Stop the RCE
  8. Enter “senddata” to send the data from the oscilloscope to DAQ PC (only for oscilloscope users)

    Note: every run folder contains a .root file and a .rce file. If the planes addresses are implemented on the "Judith style" the .root file can be used directly for the Judith reconstruction (make sure with the testbeam managers that it is the case). Otherwise, the .rce file will be converter into .root by tbconverter. Read more on section MISCELLANEOUS/TBCONVERTER USER GUIDE.

REGION OF INTEREST (ROI)

Region of interest is implemented by applying a hitOR mask onto one of the FE-I4 planes. The following subsection explains how to produce such mask and implement it in the telescope. This particular procedure applies a mask to the modul Mod4 (MSBM-21).

  1. Make sure the telescope configuration file that is loaded in cosmicGui is 527.

  2. Take data with the DUT as a trigger. Resulting plot for Mod4 (MSBM-21) should look something like this:
    ROI.png
  3. Read the X-Y dimensions of the sample. Bin the X-axis into 8 bins (0-7) whereas Y-axis has 336 bins.

  4. run the program ./produceHBmask <xLeft> <xRight> <yBottom> <yTop>

  5. In this case, following command has to be called to get the whole diamond in: ./produceHBmask 2 4 120 230. For in-DUT triggering, we’d use 3 3 140 210.

  6. A file hitbusMaskSmall.dut is produced. Send it to the DAQ PC:

    $ scp hbMaskSmall.dat testbeam@192NOSPAMPLEASE.168.2.100:/home/testbeam/AIDA/moduleConfigs/hitbus

  7. In the DAQ PC:

    $ vi /home/testbeam/AIDA/moduleConfigs/MSBM-21/configs/MSBM-21__52700.cfg

  8. Find the line with a title “hitbus”.

  9. Change the adjacent value to: hitbus/hitbusMaskSmall.dut

  10. In cosmicGui, Main tab, press Load and load the telescope configuration with the number 52700.

  11. Start a run and observe the online monitor.

SUGGESTED PROCEDURE FOR DUT TESTING

  1. A long run without the DUT (for telescope alignment).
  2. Few short runs with the DUT to get to know the readout and timing.
  3. A longer run with the DUT and full-frame hitbus triggering.
  4. A run with DUT being a trigger (to see its shadow in the telescope).
  5. Application of the trigger ROI mask on Mod4.
  6. Runs at various DUT settings (e.g. bias voltage).
  7. For the users using the oscilloscope as DUT DAQ: ROI runs should not be longer than 50000 triggers because the oscilloscope readout gets very slow (see plot below).
    Measured <span class=ToT with time (for 80.000 triggers)" height="241" src="https://twiki.cern.ch/twiki/pub/Main/ATLASSBMAIDATELESCOPEUserGuide/TOT_vs_timestamp.png" title="TOT_vs_timestamp.png" width="240" />

MISCELLANEOUS

REMOTE CONTROL SHIFTERS

The system is so stable that shifts can be performed remotely from home. In ordert to do that, follow the instructions bellow:

  1. Connect yourself into the cern network:
    ssh -Y username@lxplusNOSPAMPLEASE.cern.ch
  2. Connect to the testbeam network from the cern network:
    a) ping scvd-id (to get the external IP of the DAQ pc)
    b) Open VNC viewer --> enter IP and password

TBCONVERTER USER GUIDE

TBConverter converts different data types (rce, text ...) to Judith readible data types. Currently there are four conversions implemented which are described bellow:

Dependencies:
- ROOT environment installed
- Unix machine

Installation:
- $ make

1) convertbintoroot

Batch-converts LeCroy binary data files into a Judith-compatible ROOT file format. It is intended to find a pulse amplitude in the waveform.

Config_file: any empty text file
Input: path to the folder containing binary files
Output: ROOT file name

Example:
-open terminal and go into the tbConverter folder
- ./tbConverter –h (it will show you the existing commands you can use)
- ./tbConverter –c convertbintoroot –f configs/empty.cfg –i /path to the input file –o /path to the output files

2) convertbintotext

Batch-converts LeCroy binary data files into text waveform data files.
Input: path to the folder containing binary files
Output: path to the folder containing resulting text files

Example:
-open terminal and go into the tbConverter folder
- ./tbConverter –h (it will show you the existing commands you can use)
- ./tbConverter –c convertbintotext –f configs/empty.cfg –i /path to the input file –o /path to the output files

3) converttexttoroot

Converts a single text file containing a list of events into a Judith-compatible ROOT file format.
Input: TXT file name
Output: ROOT file name
Format: EvtNo Timestamp IsHit Ampl Area Baseline (\t for spacing)

Example:
-open terminal and go into the tbConverter folder
- ./tbConverter –h (it will show you the existing commands you can use)
- ./tbConverter –c converttexttoroot –f configs/empty.cfg –i /path to the input file –o /path to the output files

4) convertrcetoroot

Converts a single RCE binary data file into a Judith-compatible ROOT file format.
Config_file: CFG file name
Input: DAT file name
Output: ROOT file name

Example:
-open terminal and go into the tbConverter folder
- ./tbConverter –h (it will show you the existing commands you can use)
- ./tbConverter –c convertrcetoroot –f configs/RCE.cfg –i /path to the input file –o /path to the output files

COPYING DATA VIA TERMINAL

From Linux to Linux/Mac:
scp -r user@server:/path_to_be_copied/ .

From Windows to Linux/Mac:
wget -b -P . -r ftp://username@ip:/path_to_be_copied

SUMMARY OF USER'S PROBLEMS IN PREVIOUS CAMPAINGS

TEST BEAM SCHEDULE

May Test Beam

TestBeamScheduleMay_2.png</verbatim> -- SoniaFernandez - 2015-05-04

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng ROI.png r1 manage 43.0 K 2015-05-04 - 15:07 SoniaFernandez  
PNGpng Screen_Shot_2015-05-04_at_11.34.08.png r1 manage 793.5 K 2015-05-04 - 11:37 SoniaFernandez  
PNGpng TOT_vs_timestamp.png r1 manage 17.3 K 2015-05-04 - 15:15 SoniaFernandez  
PNGpng TestBeamScheduleMay.png r1 manage 49.4 K 2015-05-18 - 10:17 MalteBackhaus  
PNGpng TestBeamScheduleMay_2.png r1 manage 49.4 K 2015-05-18 - 10:19 MalteBackhaus  
Edit | Attach | Watch | Print version | History: r11 < r10 < r9 < r8 < r7 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r11 - 2015-07-16 - SoniaFernandez
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback