Work in progress
--
BrianDorney - 15 Sep 2014
TURBO
Introduction
- TURBO is a stand alone portable Control and Data Acquisition platform for the VFAT front end ASIC.
- It has been developed on the basis of the Totem Test Platform (TTP) used for testing the TOTEM hybrids equipped with VFAT chips.
- Each TURBO board can be interfaced with 8 VFATs.
- TURBO is controlled by a PC running LabView via USB interface.
- LabView softwares have been developed for VFATs control, standard calibration scans (threshold, calibration pulse, latency ), Data Acquisition and Quality Monitoring.
- Analog readout
Why we use it
- Portable
- User friendly
- "Real Time" response in order to understand what's going on
- Capability of DAQ for small/medium size system
- Fast
TURBO Software Structure
The TURBO Software is organized in three steps:
- TURBO CONTROL to control and test (➜ TURBO-CTRLXXXXXX.vi)
- DATA ACQUISITION (DAQ) (➜ TURBO-DAQXXXXXX.vi)
- DATA QUALITY MONITORING (DQM) (➜ TURBO-DQMXXXXXX.vi)
TURBO CONTROL step by step
- In TURBO REGISTER
- Initialize DAQ
- Write/Read TURBO Registers
- In VFAT REGISTER
- Write/Read ➜ button WRITE
- In SIMPLE ACQUISITION
- From here we can set threshold and latency
➜ Some plots to check
- In THRESHOLD SCAN
- Select INTERNAL TRIGGER
- Start (OUT OF THE SPILL)
- Determine correct Threshold on TURBO 0 VFAT 1,4 ,5,6,7
- Determine correct Threshold on TURBO 1 VFAT 1,4 ,5,6,7
- Determine correct Threshold on TURBO 2 VFAT 1,4 ,5,6,7
➜ Some typical threshold scan plots
➜ Some typical Calibration Pulse plots
* In
CAL PULSE LATENCY SCAN
- In BEAM LATENCY SCAN
- Select EXTERNAL TRIGGER
- Start whenever we want (WE NEED THE BEAM)
- Determine correct latency for peak position on histogram (rightone) typically between 20 and 40
- Make the XML file according with values you measured
➜ Some typical BEAM LATENCY SCAN plots
- IN VFAT REGISTER XML
- Load VFAT registers from XML file
- IN SBIT
- QUSB (First)
- VFAT1
- S1
- SB: Write/Read SBIT
- Read/Write SBIT gaps
➜ REMIND: BEFORE EACH RUN
- Check in the oscilloscope the VFATs are synchronous
- If NOT SYNCRONIZED we have to do a main reset
- Click ok ➜ until VFATs are in phase and trigger is on rising edge
- TDC cannot overwrite files: check you are incrementing the numbers on INFINITE RUNS (/home/XXX/XXXX/data /)
IComp Scan: HV scan run step by step
- START INFINITE RUN ON TDC
- Filename: infinite #
- Large number of events ~50000
- GO ON TURBO CTRL ➜ if program stops do STEP 1 in TURBO CTRL
- VFAT Register-tab
- Load VFAT Registers values from XML file
- Choose file with right IComp values (HV SCAN IComp=XXX)➜Desktop/XXXXX/ConfigurationFiles
- Now we have right IComp setting on VFAT
- THRESHOLD SCAN
- Step THRESHOLD SCAN in TURBO CTRL
- Save threshold in XML file
- in Desktop/XXXXXXX/ConfigurationFiles copy one file and change name to corresponding run number
- Open with Excel
- Check IComp values
- Select threshold where there are no hits
- Threshold=vthreshold2-vthreshold1
- Save XML (Developer-tab ➜XML➜Export)
- BEAM LATENCY SCAN
- Check that TDC is running
- Step BEAM LATENCY SCAN in TURBO CTRL
- If counts are level for a VFAT you need to raise its threshold and restart latency scan
- Export XML
- Rename XML➜ [IComp,lat=Latency of VFAT1 on TURBO 1 (&2), th=threshold of TURBO 1 VFAT 1] ➜check/change these parameters in the filename * TDC
- Stop the old run ➜ CTRL+C
- Start a new run
- Number of events 5000
- Filename “TDC” [XML-filename]
- TURBO-DAQ
- Load XML file
- Check number of events (same as in TDC)
- If “events in FIFO”< 90 ➜ increase delay in readout (“ Delay between Readout “=600, try 700)
- If “events in FIFO”=90 all the time ➜ decrease delay in readout (“ Delay between Readout “=600, try 700)
- Press ➜ to start
- We can change delay while running ➜ Do changes between spills to avoid loosing events