Presentation is loading. Please wait.

Presentation is loading. Please wait.

TURBO: VFAT CTRL/READOUT BOARD INVOLVED PEOPLE TOTEM(Pisa/Siena group and students), GDD-RD51(Matteo, Gabriele), CMS GEM upgrade group (Andrey, Stefano,

Similar presentations


Presentation on theme: "TURBO: VFAT CTRL/READOUT BOARD INVOLVED PEOPLE TOTEM(Pisa/Siena group and students), GDD-RD51(Matteo, Gabriele), CMS GEM upgrade group (Andrey, Stefano,"— Presentation transcript:

1 TURBO: VFAT CTRL/READOUT BOARD INVOLVED PEOPLE TOTEM(Pisa/Siena group and students), GDD-RD51(Matteo, Gabriele), CMS GEM upgrade group (Andrey, Stefano, Michal, Nicholas, Tommy, students…), TERA(Sarolta, Nail) and all the people that I’ve forgotten…. Starting Point: TOTEM TTP (Paschalis, Walter, Paul) Main Idea: - Portable. - User friendly (?). - With a “real time” response for the understanding on what is going on. - With the capability of DAQ for small/medium size system. - Fast (ref. VFAT 100kHz, not yet optimized to the maximum achievable). 1

2 TURBO Input/Output LVDS/NIM/CMOS (clk, trigger,…..) QuickUSB DAC Out Turbo Power VFAT2 Digital PowerVFAT2 Analog PowerDCU 8 x VFAT2 TURBOs Chain Control/Data BUS 2

3 TURBO Fpga: Altera Stratix II (EP2S60F672) Fpga Programming: Active Serial and JTAG. On Board Crystal Oscillator: 80MHz (XO IQD LFSPXO009441 ) Power Input (x3): 3 way horizontal PCB header,5.08mm pitch - Phoenix Contact MSTBA 2.5/ 3-G-5.08 Signal Input: 4LVDS (size 00 lemo B), 2NIM (size 00 lemo), 2LVTTL (size 00 lemo) Signal Output: 4LVDS (size 00 lemo B), 2NIM (size 00 lemo), 10BIT DAC 3.3V,15mA (size 00 lemo) Spare Input/Output: 66 true holes for std pin. Inegrated Detector Control Unit: DCU2 (G.Magazzu’ et al., CERN EP/MIC, INFN Pisa) VFAT Interface and Daisy Chain Connectivity: ERNI TYPE SMC 50 Male Connectors, spacing 1,27 mm USB interface: Bitwise Systems Quick-USB Ref. Dr. Cecchi Roberto, Dr. Bagliesi Maria Grazia. Siena University, Dept of Physics 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. “In Parallel” (available) and “In daisy chain” (under development) set up configurations allow to work with more than 8 chips. TURBO is controlled by a PC running LabView via USB interface (Quick-USB). The number of USB ports needed is equal to the number of TURBO boards used in the “In Parallel” set up configuration. In the Daisy Chain operation instead, a single USB port is needed for each group of 8 TURBOs. LabView softwares have been developed for VFATs control, standard calibration scans (threshold, calibration pulse, latency ), Data Acquisition and Quality Monitoring. 3

4 PC PS TURBO VFAT2s Typical Setup TURBO, PC, Power Supply, VFAT2 4

5 RD51 TB Set Up USB Trigger/VETO/CLK… 8 VFAT2 Control and Data Acquisition from 24 VFAT2s USB 8 VFAT2 One of the board is defined as a master and it will take care about clock, veto, Trigger/VETO/CLK… Master 5

6 Input Output RD51 TB Input / Output Configuration LVSD Clock IN NIM LV1 Trigger NIM VETO IN LVTTL counter Reset LVTTL Timestamps Reset LVDS Clock OUT1 LVDS Clock OUT2 LVDS Clock OUT3 NIM Sbit OUT NIM VETO OUT 6

7 RD51 TB Set Up 7

8 TURBO Chain (64 VFAT2) USB TURBO s CHAIN 8 VFAT2 MASTER 64 VFAT2 Not Ready …. 8

9 Software (developed by physicist(???)) obviously not optimized, but working…. CONTROL & TESTING: TURBO-CTRL-Something.vi Data Acquisition and Quality Monitoring: TURBO-DAQ-Something.vi TURBO-DQM-Something.vi 9

10 TURBO-CTRL-Something.vi 10

11 TURBO/VFAT CONTROLS TURBO registers/initialization VFAT register Any operation can be performed for all of part of the chip used 11

12 XML VFAT Interface (a useful upgrade) All the VFAT registers can be Loaded from or Saved to XML files… …that can be opened/written with std editor or excel Easy config/check 12

13 TURBO-CTRL-Something.vi : what is available… 13

14 Real Time  Particles/Noise Correlation SIMPLE ACQUISITION: “Real Time” graph 14

15 Cumulative  Dead Channels Cumulative  Beam Profile Cumulative  Damaged Channels with Micromegas. Beam Profile SIMPLE ACQUISITION: Cumulative Plot 15

16 Histogram  Cross Talk (~all channels on) SIMPLE ACQUISITION: “Channels on per trigger” Histo. Histogram  Anomalous Noise Structure Histogram  Beam and Noise (Cluster Size) 16

17 THRESHOLD SCAN Performed for all the channels You can view all of them using the “vfat channel” control. You can save (*) the scan channel by channel in ASCII format and analyze/compare with other scans easily with any software. (*) with the CTRL labview software we never save the VFAT Raw Data, but the scan output directly. For Raw Data you have to use the DAQ labview software. 17

18 CALIBRATION PULSE (and Internal Latency Scan) After having found the internal right latency,,,, … a calibration scan can be performed You can save the scan channel by channel as for the threshold scan in ASCII format and analyze/compare with other scans easily with any software. S-Curve 18

19 CALIBRATION PULSE: something that we have to do From single channel measurement… … to multi-channels analysis S-Curve S-Curve Mean S-Curve Sigma At the moment you have to do the scan and save the data channel by channel (not totally true: it depends on the number of channels that we can pulse at the same time). We have to implement an automatic procedure to scan all the channels that we have. 19

20 Beam Latency Scan Counts per trigger vs latency Needed to take data properly, but… … it could provide also some timing information … it could provide also some timing information A fastest (signal that starts at higher latency) with MicroMegas Information about the signal time structure can be collected playing with the VFAT monostable polarity … 20

21 S-Bit Settings (which vfats, which sector..) Trigger Counter and Timestamps Timing: Sbit provided to the Andrey’s TDC LV 1 Induced Noise seen with the SBit LV 1 SBit Timestamps (reset every SPS spill). Nice: Different rate between the beginning and the end of the spill has been observed and also some beam adjusting, optimization,… They can be used as a synchronizatio n check with other DAQs (saved in the raw data) 21

22 TURBO-DAQ-Something.vi & TURBO-DQM-Something.vi Something that we have to do: Integrate the Two into One (automatic DQM after DAQ) 22

23 List of XML files for the VFAT settings Multiple XML configuration files can be loaded and the DAQ will do them serially… amazing (you can go to sleep or smoke or for a coffee…) DAQ: Data Acquisition. Acquisition settings: number of events, file size,.. 23

24 CRC, IDs, EC,… checks Trigger Counter, Timestamps DQM: Data Quality Monitoring Check Config: # of VFATs,… 24

25 RAW Data Analysis (RAW= VFAT Frame + added Turbo header(timestamps,…)) Software for the ROOT framework developed by: Matteo, Gabriele + Stefano, Elena,… + … 25

26 26 Efficiency Scans… Detector “Radiography”… Beam profile… Just few examples….

27 27 the end, thanks


Download ppt "TURBO: VFAT CTRL/READOUT BOARD INVOLVED PEOPLE TOTEM(Pisa/Siena group and students), GDD-RD51(Matteo, Gabriele), CMS GEM upgrade group (Andrey, Stefano,"

Similar presentations


Ads by Google