1 / 11

DAQ Status

DAQ Status. Hardware. At the moment we have 3 working system at CERN, 1 in Genova (?) There are 2 “half system” (TTCci & FEC are missing) We have no more FEC & TTCci. We “sacrificed” the test system in Bari for the latest H8 installation. Activities.

kelda
Download Presentation

DAQ Status

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. DAQ Status

  2. Hardware • At the moment we have 3 working system at CERN, 1 in Genova (?) • There are 2 “half system” (TTCci & FEC are missing) • We have no more FEC & TTCci. We “sacrificed” the test system in Bari for the latest H8 installation. F.S. Cafagna, Coll. Meeting 16 March 2009

  3. Activities • Full support to the detectors in 555 and H8 (Everybody) • Opto-RX firmware maintenance and test (Michele) • Support to test activities in 555 (Ervin, Juha, Michele) • Debug and test of VME firmware (Gueorgui, Ervin, Juha, Michele) • Software development for VME readout (Ervin, Juha) • Monitor development (Jan, Mate) F.S. Cafagna, Coll. Meeting 16 March 2009

  4. F.S. Cafagna, Coll. Meeting 16 March 2009

  5. TOTFED class • Based on the HAL library • VME access functionality • Address tables • XDAQ compatible • Class doesn’t implement user interface Ervin & Juha

  6. F.S. Cafagna, Coll. Meeting 16 March 2009

  7. F.S. Cafagna, Coll. Meeting 16 March 2009

  8. F.S. Cafagna, Coll. Meeting 16 March 2009

  9. vfat_controller updates Juha • VME readout added to all the scans • Software now controls FEC, TTCci and FED • Reading 1 event at the time • Max trigger rate ~1kHz (one VFAT) • Gets slower while adding more VFATs (all commands are consecutive)

  10. Future Activities • Support to the detectors (as usual) • IP5 system review, repair and new software & hardware deployment. (PC OSs have been updated in IP5 ... ) • Debug and test of VME firmware • Development of DCS interface (we plan to set-up a test environment in 555) F.S. Cafagna, Coll. Meeting 16 March 2009

  11. Conclusion • Detector support is draining all the manpower. • No hardware to setup any other system even in IP5. • To be ready in IP5 we need to: • Deploy and test the software in the updated OS • Find: TTCci & FEC ( Or move from H8 or 555) • Is it the interface to DCS mandatory ? • There are no resources for software development until we have to support all those system and activities. F.S. Cafagna, Coll. Meeting 16 March 2009

More Related