1 / 12

MTest Pixel Telescope – Status Update

MTest Pixel Telescope – Status Update. David Christian September 11, 2007. MTest Telescope. Constructed using “BTeV pixels” Pixel size = 50 m x 400 m (600 m ) Oriented to provide “precision-x” or “precision-y” measurements. Layout. Aperture ~ 3.5cm x 3.5cm 4 – 6 stations. y. y. Beam.

devi
Download Presentation

MTest Pixel Telescope – Status Update

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. MTest Pixel Telescope – Status Update David Christian September 11, 2007

  2. MTest Telescope • Constructed using “BTeV pixels” • Pixel size = 50m x 400m (600m) • Oriented to provide “precision-x” or “precision-y” measurements.

  3. Layout • Aperture ~ 3.5cm x 3.5cm • 4 – 6 stations y y Beam x x

  4. Nomenclature • Station = 2 planes & an SLINK • Plane = 3 modules mounted on a TPG heat spreader • Module = hybrid pixel detector glued & wire-bonded to a High Density Interconnect (Kapton flex circuit) • Hybrid = pixel sensor bump bonded to 4 FPIX2.1 ASICs

  5. DAQ Overview ROUTER SLINK Trigger/timing signals Twin-ax (sATA) Removable disk Fiber PCI Interface LINUX pc Trigger/timing signals

  6. DAQ • SLINK communicates with 2x3x4=24 FPIX2.1 chips & with ROUTER. • Relays commands & responses • Collects data • Deserialize (digital phase follower) • Time order & construct data blocks w/extended time stamp & chip ID headers • Hierarchy of 2-way data merges

  7. DAQ - continued • ROUTER communicates with PCI interface & SLINKs and (optionally) DUTs • 12 sATA ports, 4 RJ45 ports • Relays commands & responses • Collects data • Hierarchy of 2-way data merges (same logic as SLINK) • PCI Interface communicates with ROUTER & pc • Relays commands & responses • Uses 3 CSRs & 3 ring buffers in the pc main memory (64 MB)

  8. Detector Status/Plan • Hybrid development complete • 11 good hybrids in hand • Balance waiting for LANL PO to VTT • Delivery Jan – May (schedule risk) • Module development • 4x HDI layout ~85% complete (FNAL) • Prototype by end of October, production Nov-Dec (on the optimistic critical path)

  9. Detector Status/Plan continued • Plane/Station development: • TPG in hand, reinforcing about to start (FNAL) • Mechanical design underway (FNAL) • SLINK pcb layout & final design is waiting for completion of 4x HDI (Nevis) • Box/Area: • Cleanup has started • Mechanical design underway (FNAL)

  10. DAQ Status/Plan • DAQ Hardware/Firmware (Nevis) • PCI interface ~90% complete (trigger/timing hooks not written) • Router ~70% complete (trigger/timing, implementation of merges, integration of DUT?) • SLINK • Prototype tested at ~90% level; linked to 2 modules • Design/layout waiting for 4x HDI • On the optimistic critical path

  11. Software Status/Plan • Online software (FNAL, Syracuse?, UNM?) • Core low level routines exist & have been tested. • Need to specify online, including online/offline boundary, write & test code. • On the optimistic critical path • Offline software (Syracuse, FNAL?, UNM?) • Data unpacking • Alignment • Tracking, integration of DUT • On the optimistic critical path • Strategic decisions to be made in the next 4-6 weeks

  12. Schedule • Focus on full telescope in ~Feb • If bump bonding is delayed (past ~Jan)… • Install 1st station + fragments as available (~Jan?)

More Related