vXS fPGA-based Time to Digital Converter (vfTDC)

Slides:



Advertisements
Similar presentations
GSI Event-driven TDC with 4 Channels GET4
Advertisements

Commercial FPGAs: Altera Stratix Family Dr. Philip Brisk Department of Computer Science and Engineering University of California, Riverside CS 223.
A Low-Power Wave Union TDC Implemented in FPGA
JLab High Resolution TDC Hall D Electronics Review (7/03) - Ed Jastrzembski.
On-Chip Processing for the Wave Union TDC Implemented in FPGA
Tests of CAEN 1190 Multi-hit TDCs Simona Malace Brad Sawatzky and Brian Moffit JLab Hall C Summer Workshop Aug , JLab.
1 MTD Readout Electronics J. Schambach University of Texas Hefei, March 2011.
Y. Karadzhov MICE Video Conference Thu April 9 Slide 1 Absolute Time Calibration Method General description of the TOF DAQ setup For the TOF Data Acquisition.
Octal ASD Certification Tests at Michigan J. Chapman, Tiesheng Dai, & Tuan Bui August 30, CERN.
David Nelson STAVE Test Electronics July 1, ATLAS STAVE Test Electronics Preliminary V3 Presented by David Nelson.
Low Cost TDC Using FPGA Logic Cell Delay Jinyuan Wu, Z. Shi For CKM Collaboration Jan
3/7/05A. Semenov Batch-by-Batch Intensity Monitor 1 Two-Channel Batch by Batch Intensity Monitor for Main Injector BBI.
Electronics for PS and LHC transformers Grzegorz Kasprowicz Supervisor: David Belohrad AB-BDI-PI Technical student report.
TID and TS J. William Gu Data Acquisition 1.Trigger distribution scheme 2.TID development 3.TID in test setup 4.TS development.
Trigger Supervisor (TS) J. William Gu Data Acquisition Group 1.TS position in the system 2.First prototype TS 3.TS functions 4.TS test status.
The GANDALF Multi-Channel Time-to-Digital Converter (TDC)  GANDALF module  TDC concepts  TDC implementation in the FPGA  measurements.
Prototype Test of SPring-8 FADC Module Da-Shung Su Wen-Chen Chang 02/07/2002.
TDC and ADC Implemented Using FPGA
SBS meeting VETROC application for Cerenkov triggering Alexandre Camsonne March 18 th 2015.
Leo Greiner IPHC meeting HFT PIXEL DAQ Prototype Testing.
SBS meeting VETROC application for Cerenkov triggering Alexandre Camsonne March 18 th 2015.
K.C.RAVINDRAN,GRAPES-3 EXPERIMENT,OOTY 1 Development of fast electronics for the GRAPES-3 experiment at Ooty K.C. RAVINDRAN On Behalf of GRAPES-3 Collaboration.
Status of the Beam Phase and Intensity Monitor for LHCb Richard Jacobsson Zbigniew Guzik Federico Alessio TFC Team: Motivation Aims Overview of the board.
06/07/041 F1TDC Status Update Hall D Collaboration Meeting Indiana University – Bloomington, IN May 20-22, 2004 Fernando J. Barbosa
LANL FEM design proposal S. Butsyk For LANL P-25 group.
Features of the new Alibava firmware: 1. Universal for laboratory use (readout of stand-alone detector via USB interface) and for the telescope readout.
Testing of Latch-TDC Da-Shung Su Jia-Ye Chen, Hsi-Hung Yao, Su-Yin Wang, Ting-Hua Chang, Wen-Chen Chang 2011/07/13.
FPGA firmware of DC5 FEE. Outline List of issue Data loss issue Command error issue (DCM to FEM) Command lost issue (PC with USB connection to GANDALF)
01/04/09A. Salamon – TDAQ WG - CERN1 LKr calorimeter L0 trigger V. Bonaiuto, L. Cesaroni, A. Fucci, A. Salamon, G. Salina, F. Sargeni.
KLM Trigger Status Barrel KLM RPC Front-End Brandon Kunkler, Gerard Visser Belle II Trigger and Data Acquistion Workshop January 17, 2012.
CMS FED Testing Update M. Noy & J. Leaver Imperial College Silicon Group.
CBM-TOF-FEE Jochen Frühauf, GSI Picosecond-TDC-Meeting.
8133A Overview. 8133A Overview 10-Feb04 Page A Overview 1) Specifications and Applications 2) Operational Overview 3) Block Diagram.
Vladimir Zhulanov for BelleII ECL group Budker INP, Novosibirsk INSTR2014, Novosibirsk 2014/02/28 1.
C.Beigbeder, D.Breton, M.El Berni, J.Maalmi, V.Tocut – LAL/In2p3/CNRS L.Leterrier, S. Drouet - LPC/In2p3/CNRS P. Vallerand - GANIL/CNRS/CEA SuperB -Collaboration.
29/05/09A. Salamon – TDAQ WG - CERN1 LKr calorimeter L0 trigger V. Bonaiuto, L. Cesaroni, A. Fucci, A. Salamon, G. Salina, F. Sargeni.
SKIROC status Calice meeting – Kobe – 10/05/2007.
DAQ and Trigger for HPS run Sergey Boyarinov JLAB July 11, Requirements and available test results 2. DAQ status 3. Trigger system status and upgrades.
AJAI IYER COSMIC RAY LABORATORY(OOTY) DEPARTMENT OF HIGH ENERGY PHYSICS.
9530 T IMING C ONTROL U NIT Features TCU-1 Key Features 250ps timing resolution with < 50ps jitter 8 independent outputs with full individual programming.
TDC and ADC Implemented Using FPGA
Work on Muon System TDR - in progress Word -> Latex ?
DAQ ACQUISITION FOR THE dE/dX DETECTOR
OMEGA3 & COOP The New Pixel Detector of WA97
DCH FEE STATUS Level 1 Triggered Data Flow FEE Implementation &
Journées VLSI-FPGA-PCB Juin 2010 Xiaochao Fang
Jinfan Chang Experimental Physics Center , IHEP Feb 18 , 2011
LHC1 & COOP September 1995 Report
14-BIT Custom ADC Board Rev. B
Readout electronics for aMini-matrix DEPFET detectors
Iwaki System Readout Board User’s Guide
96-channel, 10-bit, 20 MSPS ADC board with Gb Ethernet optical output
From SNATS to SCATS C. Beigbeder1, D. Breton1,F.Dulucq1, L. Leterrier2, J. Maalmi1, V. Tocut1, Ph. Vallerand3 1 : LAL Orsay, France (IN2P3 – CNRS) 2 :
PID meeting SCATS Status on front end design
DCH FEE 28 chs DCH prototype FEE &
Status of the Beam Phase and Intensity Monitor for LHCb
FIT Front End Electronics & Readout
FPGA implementation of a multi-channels, 1 ns time resolution, multi-hit TDC Lorenzo Iafolla Lorenzo Iafolla SuperB Workshop.
Hellenic Open University
8254 Timer and Counter (8254 IC).
Fernando J. Barbosa F1TDC Status Update Hall D Collaboration Meeting Indiana University – Bloomington, IN May 20-22, 2004 Fernando J.
FPGA-based Time to Digital Converter and Data Acquisition system for High Energy Tagger of KLOE-2 experiment L. Iafolla1,4, A. Balla1, M. Beretta1, P.
Trigger status Fan-out Trigger processor
Programmable Interval timer 8253 / 8254
Programmable Interval timer 8253 / 8254
Stefan Ritt Paul Scherrer Institute, Switzerland
8253 – PROGRAMMABLE INTERVAL TIMER (PIT). What is a Timer? Timer is a specialized type of device that is used to measure timing intervals. Timers can.
Programmable Interval Timer
BUCKEYE has internal shift register which controls calibration
Synchronization and trigger management
Presentation transcript:

vXS fPGA-based Time to Digital Converter (vfTDC) 18Mbit RAM Generic 8 differential In 8 ECL out preliminary VME64x: Register, Data Readout 32 differential in 32 LVTTL in Trigger Interface Trg/Clk/Reset/Busy VXS P0: Trg/Clk/Reset/Busy 4x fiber Tx/Rx 28 LVTTL on row A 4 + 4 LVTTL on row D 28 LVTTL on row C 32 differential in 32 LVTTL in (with mezz. for differential IN) FPGA, XC7A200T-2FF1156C

FPGA-based TDC measurement: It measures the edge relative to the clock directly, How many clock cycles passed (coarse measurement); Latency between the signal edge and the clock edge (fine measurement) The common start (or common stop) can be used as a normal channel, (multiple measurement on the common signal can decrease the statistical measurement error) If the clock is accelerator synchronized clock, there will be no need for the precise common start (or common stop). The readout trigger should be sufficient. Easier PCB design. Actually, this is based on a PCB designed for HallA.

Single channel measurement: Ch_In Carry Chain 32x4 units Calib_In Calib_sel Clock 500MHz Register 128 FD FD FD FD FD FD FD FD FD FD FD FD FD FD FD FD FD FD FD FD Edge finder, rising/falling edge Pipelined encoder R_edge F_edge Fine_Time(6:0) (one edge per 2ns) R_edge F_edge 18Kb ring buffer, 4 us deep Fine_Time(6:0) Clock 250 MHz Dly_R_edge Dly_F_edge Dly_Fine_Time(6:0) Ring_Buf_read_ddr(9:0) EdgeInfo(17:0) Readout Lookback Readout window CoarseTime FineTime “ZERO” suppressed Trigger Event FIFO 36(wide) x 512(deep) Event marker

TDC readout (data merging): Trigger/Clock/Reset Ch#1 data(26:0) Ch#2 data(26:0) Merged data(26:0) 27(wide) x 2048(deep) Event Headers 32(wide) x 1024(deep) Further merged data(26:0) (connector#1) 27(wide) x 2048(deep) Merged data(26:0) 27(wide) x 2048(deep) Ch#8 data(26:0) Further merged data(26:0) (All channels) 27(wide) x 4096(deep) 6  1 merger Merged data(26:0) 27(wide) x 2048(deep) Merged data(26:0) 27(wide) x 2048(deep) Ch#32 data(26:0) Full block Block headers event#1 headers event#1 data ------ event#n data Block Trailer Further merged data(26:0) (connector#6) 27(wide) x 2048(deep) Merged data(26:0) 27(wide) x 2048(deep) VME Readout Other Readout Ch#192 data(26:0) 8  1 merger 4  1 merger Data Format Bits (31:27, 26-24, 23:19, 18, 17:8, 7, 6:0 Format Connector# Channel# EdgeType Coarse_time 2ns Fine_time xxxxx 0 - 5 0 - 31 1: R 0: F 4*(0 – 1023) ns 0/1 0 - 127

Special features of the vfTDC: Some edges will be measured twice. This gives a real-time carry chain delay calibration, esp. the fine delay step size (LSB); The FPGA built in IODelay elements can be used to calibrate the delay chain linearity; External calibration is needed only for the delay offset. Programmable: by sacrificing the channel count (192), the vfTDC can expand its measurement ranges (4 us) (limited by the total available memory size); Choosing a higher performance FPGA, the measurement LSB can be improved.

vfTDC in-FPGA calibration Increment 31.25MHz clock Calib1 Output Input Ch#1 TDC IN1 IODELAY VME_Calib Initialize Calib32 Ch#32 TDC IN32 Delay (~us) Calib_Trg TRG Calib_Sel Each group (32 channels) has one set of calibration logic, so the IODELAY is localized One rising edge and one falling edge per 32ns. IODELAY increases (2.5ns/32 ~78ps) every 32ns.

A typical channel in-FPGA calibration (TDC Count) Routing inside the FPGA The 250MHz clock count was subtracted for the plot; ‘Double measurement’ is used to calibrate the LSB, here: LSB=18.2ps; IODELAY calib: LSB= 18.1ps; Falling edge Double measurement Rising edge (In 78ps steps)

A typical channel in-FPGA calibration * event#1 + event#2 ◊ event#3 ○ event#4 X event#5 (TDC Count) Another channel with five calibration events; Routing specific linearity (FPGA Clock routing, Carry chain routing) Event by event repeat,  TDC measurement reolution (In 78ps steps)

A lego plot of in-FPGA calibration (Entries) Another channel 1000 calibration events. The resolution (on the majority of the calibration points) is less than one LSB (<18ps) (TDC Count) (In 78ps steps)

vfTDC status and to do lists 192 Channel TDC compiled ; VME data readout; Minimum pulse width 3ns, separation 3ns: guaranteed by design; LSB: 18ps; In-FPGA calibration resolution: <18ps To do lists: FPGA clock distribution specific calibration, FPGA LOCed routing; Channel offset calibration (external calibration); Overall TDC resolution (PCB noise, etc); Real situation performance and feedback Extension: The Trigger Supervisor board can be used as a 64 channel TDC. The IOs are fully differential on the PCB, and a higher overall resolution can be achieved

External inputs for overall noise/resolution 8 channels of test signal, synced with ClkVme, 20ns high, 20 ns low. Various inputs are tried. Example plots with randomly choosen channels. 8-Ch ECL Ouptuts Ch1-32 Ch33-64 The signal looks like a clock 20ns 20ns The skew between the eight channels are less than 0.4ns (peak to peak) Ch129-192 Ch65-96 Ch97-128 CAEN A395A

Channel to Channel measurement 8 channels of test signal, synced with ClkVme, 20ns high, 20 ns low. Various inputs are tried. Example plots with randomly choosen channels. The signal looks like a clock. With ~1us DAQ window, there are ~50 edges per event 20ns 20ns The skew between the eight channels are less than 0.4ns (peak to peak) There are 35K events for the plots Timing measurement difference between Ch#n and the first channel (CH#0 and Ch#80) *RED: Edge=1, rising edge BLUE: edge = 0, falling edge

Channel to Channel measurement Channel#4 as example, further analyze it For Edge=1, and Fine<35, the DT = 42.4+-1.5  TDC measurement RMS: 20 ps

Within the same Channel measurement Pulse width measurement Channel#5 as example, plot all the ~50 edges in the right plot Pulse high: ~20.8ns, pulse low: ~ 19ns Average: 1277, (1280=20ns); Fine<50 region: 1239+-1.7 (edge=1)  TDC measurement RMS: ~25 ps

Within the same Channel measurement Some pulses are measured in two consecutive clock cycles, when the carry chain range is longer than the clock period (feature of the carry chain). Channel#5 as example, The 2n range corresponds to 128-DeltaT Fine>128 has different range than that for Fine<128. This means that the Clk250 is not perfectly 50% duty cycle. Duty cycle difference: 100ps (/4ns) LSB: 2ns/105=19ps