1 / 25

Electronics Week Summary

Electronics Week Summary. M. Hansen, CERN. January 2012 Electronics week Session Summary. https://indico.cern.ch/categoryDisplay.py?categId=153 Token Ring operation workshop CMS common spares workshop Radiation Effects workshop DAQ and Online: VME maintenance and uTCA upgrades

taji
Download Presentation

Electronics Week Summary

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. Electronics Week Summary M. Hansen, CERN

  2. January 2012 Electronics weekSession Summary • https://indico.cern.ch/categoryDisplay.py?categId=153 • Token Ring operation workshop • CMS common spares workshop • Radiation Effects workshop • DAQ and Online: VME maintenance and uTCA upgrades • uTCA low level software • Firmware Maintenance Review • uTCA Rack and cDCS Integration • B904 workshop (Electronics integration centre) M. Hansen, CERN. magnus.hansen@cern.ch

  3. Token Ring operation workshop • Reminder • Pixels, Strips, ECAL, RPC slow control (FE configuration) • Redundant Ring architecture • Pixels and ECAL highly vulnerable to TR hardware failures • Strips (multiple independent layers) and RPC (accessible) less so • General Status • Pixels, ECAL, and RPC have all rings operational • ECAL has a few dead nodes for which the bypass function is successfully utilized • Strip tracker has one dead ring with B on and one dead with B off (!!!) M. Hansen, CERN. magnus.hansen@cern.ch

  4. Token Ring operation workshop • Soft issues (or resettable) • Pixels • Strips • A few rings lost communication during operation on a few occasions but still early days of investigation • ECAL • 39 cases of communication loss leading to data taking interruption • Mainly two different cases detected by DCC going to error • RPC • All OK (Operating with non-redundant configuration) • Significant effort in Strips and ECAL to keep up with soft issues, software updates, etc. M. Hansen, CERN. magnus.hansen@cern.ch

  5. Token Ring operation workshop • Opportunity to standardize software • Move to slc5 an opportunity but time too short • Agreements • All systems will evaluate Tkfecsoftware • Systems will attempt to align before end 2012 • Deployment of a common version beginning 2013 • Hypernews for communication • Hn-cms-TokenRing M. Hansen, CERN. magnus.hansen@cern.ch

  6. CMS common spares workshop • Goals • Identify means for track-keeping • E.g. EMDB • Identify candidate equipment • E.g. CAEN mainframes • Detect and mitigate “us and them” attitudes within CMS • Not that there seem to be any problem… M. Hansen, CERN. magnus.hansen@cern.ch

  7. CMS common spares workshop • Discussion • The Functionality of and Interfaces to the Equipment Management Database is almost there • Spreadsheet import is laborious • If the EMDB is used from the beginning of a construction project there is no import step needed. • The EMDB and its interface development team lacks resources to react rapidly to requests • The EMDB content need consolidation • Lacks a naming convention, e.gmao, A3486 and CAEN AC/DC is the same module type but the three names are different • Suggested to allow for aliases to give a name to a type of equipment M. Hansen, CERN. magnus.hansen@cern.ch

  8. CMS Radiation Effects workshop • Agenda • Overview of CMS environment and status of SEU mitigation • COTS in radiation environment • Mainly FPGA • Goals • Share experience • Review requirements • Review available tools for mitigation of SEU in FPGAs in CMS • Review availability of radiation facilities and their usage at CERN M. Hansen, CERN. magnus.hansen@cern.ch

  9. CMS Radiation Effects workshop • Discussion • Run down of current CMS issues related to Radiation and on-going work to mitigate • Run down of FPGAs in radiation from RPC, CSC, DT, HCAL • Upgrade plans increasing exposure • Increasing exposure due to increasing dose rates • Short summary of a PH/ESE seminar about SEE effects • Concludes that tools are effective, radiation tolerant design validation is difficult but crucial, SRAM based FPGAs (e.g. Xilinx) radiation hard but soft error rate is high, flash based FPGAs (e.g. ACTEL ProASIC) have less upsets but total dose resistance is limited and they are ??no longer developed?? • Summary of tools available at CERN and elsewhere as well as some test results • Introduction to CERN mixed field radiation facility, it’s future, and a summary of experience by a CMS user • Dt used the facility in 2011 • N.b. FPGA in radiation is a hot subject: part of program @ e.g. TWEPP2012 M. Hansen, CERN. magnus.hansen@cern.ch

  10. DAQ workshopuTCA upgrades and VME maintenance • Status and plans for VME PC replacement • Schedule: first three months of LS1 • Required: Subsystems should evaluate the PCIexpress conet2 controller card before summer • Two x4 cards installed in PCs in b904 • BRM will use such a card in CMS during 2012 and have ordered two cards M. Hansen, CERN. magnus.hansen@cern.ch

  11. DAQ workshopuTCA upgrades and VME maintenance • Current work in the cDAQ and plans was discussed • Evaluation of technologies for cDAQ upgrade • How to deal with legacy vs “new” cDAQ sources • Foreseen evolution of event size was reviewed • Current investigations of event size dependency on n.o. primary vertices • Discussion • All upgrade projects have to produce a time line showing how many FEDs need to be read out at any given time up to LS2 and document where the FEDs are going to be located • Information to the cDAQ group (Frans / Christoph) M. Hansen, CERN. magnus.hansen@cern.ch

  12. uTCA upgrades • Most upgrade systems target uTCA to replace legacy VME • uTCA is defined as a shelf (crate) carrying AMCs • Advanced Mezzanine Cards as defined in the ATCA specification • Double or Single Width (Slot height, that is) • Full, mid, or compact height (Thickness, that is...) • Double width full size AMCs are square and have enough space on top and bottom for components and cooling M. Hansen, CERN. magnus.hansen@cern.ch

  13. uTCA upgrades M. Hansen, CERN. magnus.hansen@cern.ch

  14. uTCA upgradesExample: Vadatech VT892 Power Module site #2 Twin bulk supply AMC13 on MCH site #2 Vertical Air flow! 12 slots Double Width Full Size Power Module site #1 Commercial MCH on MCH site #1 M. Hansen, CERN. magnus.hansen@cern.ch

  15. uTCA upgrades • The basic backplane, the MCH, and the power module are specified in detail in the uTCA specification in order to avoid interoperability issues. Nevertheless, in order to make maintenance easier and cheaper: • CMS target • Common Crates • Perhaps with variants of backplane • Common Bulk Power Supplies • Common Power Modules • Common CMS integration Module • A.k.a. AMC13 • Providing CMS wide common interface to TTC, TTS, DAQ M. Hansen, CERN. magnus.hansen@cern.ch

  16. uTCA UpgradesRack and cDCS Integration • Central DCS integration • Has been useful to have a centralised archive of temperatures, voltages, currents, etc. in central DCS • Requires a software bridge from PVSS to IPMI and a list of quantities to read and archive • LHCb has developed such a bridge that may be evaluated • The cDCS team believes the software development effort to include uTCA systems is available • The discussion about module standardisation was deferred • Shelf, backplane, power module, MCH • Foresee discussion during the upgrade week at the latest M. Hansen, CERN. magnus.hansen@cern.ch

  17. uTCA UpgradesIP address assignment • IP address analogous with VME base address for TCA systems • Need to represent physical location of the module, either by direct addressing or through LUT (IT DNS preferred by sysadmin) • D. Newbold (Bristol) will write a short note about a proposed baseline IP assignment procedure taking current requirements into account M. Hansen, CERN. magnus.hansen@cern.ch

  18. uTCA UpgradesFirmware Upload and Bootstrap features • Bootstrap • Includes functionality of Module Management Controller (MMC) • Common design preferred • UW development, IC development, CERN/CPPM/DESY • Common command set agreed • Includes on-board firmware management • “golden build” with firmware upgrade features • Non-upgradable • “production build” with required functionality • “development build(s)” with upgraded or modified functionality • Selectable by software • Greg Iles (IC) will write a short note about on-board firmware management M. Hansen, CERN. magnus.hansen@cern.ch

  19. uTCA low level softwareC. Schwick • Discussion about e.g. register access in uTCA • Through ethernet: no defined way to access registers in modules • Proposal • Ipbus • Initially defined in Minnesota • Refined and Currently maintained by a UK consortium • Contain software libraries and firmware demonstrator • The proposal has been adopted as the baseline for register access for XTCA in CMS M. Hansen, CERN. magnus.hansen@cern.ch

  20. Firmware Maintenance Review • Cyclic review • Latest review in 2009 • Reminder about use of back-up • Suggest to use a e.g. SVN repository at CERN or elsewhere for source code development • No seamless integration with development tools • In particular useful when multiple developers • Recommend to store binary files on the CMS online depository • As safe as other run conditions • Intended to be used as communication channel between developer and “upgrade manager” • Some complaints to be worked on • Limitations in version number format • Cannot delete files (but this is the whole point...) • Display option requests, e.g. Explode subdirectories M. Hansen, CERN. magnus.hansen@cern.ch

  21. B904Electronics Integration lab workshop • cDAQ installation almost finished • Private (.cms’) network ready • NAS ready configured as in CMS • Quattor templates debugged • User head node in place • 5-6 client machine installed, more on request • DAQ machines installation on-going • Using the P5 “dropbox” for updating configs in b904 • Installation slowed down by the cooling works on the building, star point power reliability, etc. M. Hansen, CERN. magnus.hansen@cern.ch

  22. B904Electronics Integration lab workshop • cTTC • One TTC Control PC installed (ttc-904) • One global TTC crate • Clock and Orbit Generator + fanouts • Few TTCci:s • GCT, GT • HCAL, ECAL, RPC (only soft) • cTTC Waiting for more users M. Hansen, CERN. magnus.hansen@cern.ch

  23. B904Electronics Integration lab workshop • DSS • https://indico.cern.ch/getFile.py/access?contribId=4&resId=0&materialId=slides&confId=164335 • All racks cut on smoke • Dew point monitored, currently no action • Pressure + temp of cooling plant monitored • Select racks have actions based on cooling (see talk linked above) • Please review and request modifications as appropriate • DSS back end installed and users enabled to acknowledge Alarms and Actions M. Hansen, CERN. magnus.hansen@cern.ch

  24. Upcoming reviews • RE4 ESR last Wednesday • Minutes available in agenda under electronics • Report being edited • ME1/1 EDR follow-up on the 28th of March • HO PRR scheduled on the 18th of April • MB SC relocation ECR to be scheduled early May M. Hansen, CERN. magnus.hansen@cern.ch

  25. Thank you

More Related