1 / 27

TURBO: VFAT CTRL/READOUT BOARD

TURBO: VFAT CTRL/READOUT BOARD. 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.

adia
Download Presentation

TURBO: VFAT CTRL/READOUT BOARD

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TURBO: VFAT CTRL/READOUT BOARD • 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). 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….

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

  3. TURBO Fpga: AlteraStratix 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. LabViewsoftwares have been developed for VFATs control, standard calibration scans (threshold, calibration pulse, latency ), Data Acquisition and Quality Monitoring.

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

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

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

  7. RD51 TB Set Up

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

  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

  10. TURBO-CTRL-Something.vi

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

  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

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

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

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

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

  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.

  18. CALIBRATION PULSE (and Internal Latency Scan) After having found the internal right latency,,,, … a calibration scan can be performed S-Curve 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.

  19. CALIBRATION PULSE: something that we have to do From single channel measurement… 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. S-Curve … to multi-channels analysis S-Curve Mean S-Curve Sigma

  20. Beam Latency Scan Counts per trigger vs latency Needed to take data properly, but… … 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 …

  21. Trigger Counter and Timestamps S-Bit Settings (which vfats, which sector..) They can be used as a synchronization check with other DAQs (saved in the raw data) Timing: Sbit provided to the Andrey’s TDC 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,… LV1 SBit LV1 Induced Noise seen with the SBit

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

  23. DAQ: Data Acquisition. Acquisition settings: number of events, file size,.. 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…)

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

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

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

  27. the end, thanks

More Related