Clara Gaspar on behalf of the ECS team: CERN, Marseille, etc. October 2015 Experiment Control System & Electronics Upgrade.

Slides:



Advertisements
Similar presentations
ESODAC Study for a new ESO Detector Array Controller.
Advertisements

IO Controller Module Arbitrates IO from the CCP Physically separable from CCP –Can be used as independent data logger or used in future projects. Implemented.
OUTLINE WHAT ? HOW ? WHY ? BLUEPOST Poster and Message Content Specified by the User Displaying the Poster Content on a Monitor Sending Messages to.
Clara Gaspar, May 2010 The LHCb Run Control System An Integrated and Homogeneous Control System.
Manfred Meyer & IDT & ODT 15 Okt Detectors for Astronomy 2009, ESO Garching, Okt Detector Data Acquisition Hardware Designs.
CERN CMS Project Host / SD Card Configuration Data Access Dave Ojika Alex Madorsky Dr. Darin Acosta Dr. Ivan Furic.
Clara Gaspar, March 2006 LHCb’s Experiment Control System Step by Step.
Clara Gaspar, November 2012 Experiment Control System LS1 Plans…
Input/Output. Input/Output Problems Wide variety of peripherals —Delivering different amounts of data —At different speeds —In different formats All slower.
Calo Piquet Training Session - Xvc1 ECS Overview Piquet Training Session Cuvée 2012 Xavier Vilasis.
Using PVSS for the control of the LHCb TELL1 detector emulator (OPG) P. Petrova, M. Laverne, M. Muecke, G. Haefeli, J. Christiansen CERN European Organization.
5 March DCS Final Design Review: RPC detector The DCS system of the Atlas RPC detector V.Bocci, G.Chiodi, E. Petrolo, R.Vari, S.Veneziano INFN Roma.
The High Voltage, Monitoring and Control systems of the Hadronic and Electromagnetic calorimeters are essentially slow control based, and therefore are.
Calorimeter upgrade meeting - Wednesday, 11 December 2013 LHCb Calorimeter Upgrade : CROC board architecture overview ECAL-HCAL font-end crate  Short.
VELO upgrade Front-end ECS LHCb upgrade electronics meeting 12 April 2012 Martin van Beuzekom on behalf of the VELO upgrade group Some thoughts, nothing.
Start-up & synchronization sequence for Front-End LHCb Electronics Upgrade Meeting 13 February 2014 F. Alessio, CERN.
Clara Gaspar, October 2011 The LHCb Experiment Control System: On the path to full automation.
GBT Interface Card for a Linux Computer Carson Teale 1.
Status of Readout Board Firmware Guillaume Vouters On behalf of the MiniDAQ developers 11 December 2014 LHCb Upgrade Electronics.
Understanding Data Acquisition System for N- XYTER.
The GBT A single link for Timing, Trigger, Slow Control and DAQ in experiments A. Marchioro CERN/PH-MIC.
Design and Performance of a PCI Interface with four 2 Gbit/s Serial Optical Links Stefan Haas, Markus Joos CERN Wieslaw Iwanski Henryk Niewodnicznski Institute.
Design & test of SciFi FEB
Status report for TFC and ECS* LHCb Upgrade Electronics meeting F. Alessio, CERN with acknowledgements to Cairo (Caplan), Mauricio (Rivello),
LNL 1 SLOW CONTROLS FOR CMS DRIFT TUBE CHAMBERS M. Bellato, L. Castellani INFN Sezione di Padova.
Bart Hommels Univeristy of Cambridge EUDET Annual Meeting, Ecole Polytechnique, Paris JRA3: DAQ Overview Objectives System Overview Status of.
ALICE, ATLAS, CMS & LHCb joint workshop on
Gueorgui ANTCHEVPrague 3-7 September The TOTEM Front End Driver, its Components and Applications in the TOTEM Experiment G. Antchev a, b, P. Aspell.
1 Outline Firmware upgrade of the HV_LED_DAC boards. HV Status Bits board. Status of the board integration into the LHCb TFC system. CALO HV system and.
I/O Computer Organization II 1 Interconnecting Components Need interconnections between – CPU, memory, I/O controllers Bus: shared communication channel.
Management of the LHCb DAQ Network Guoming Liu * †, Niko Neufeld * * CERN, Switzerland † University of Ferrara, Italy.
Clara Gaspar, March 2005 LHCb Online & the Conditions DB.
Lecture 12: Reconfigurable Systems II October 20, 2004 ECE 697F Reconfigurable Computing Lecture 12 Reconfigurable Systems II: Exploring Programmable Systems.
Latest ideas in DAQ development for LHC B. Gorini - CERN 1.
LHCb front-end electronics and its interface to the DAQ.
Chapter 13 – I/O Systems (Pgs ). Devices  Two conflicting properties A. Growing uniformity in interfaces (both h/w and s/w): e.g., USB, TWAIN.
Input/Output Problems Wide variety of peripherals —Delivering different amounts of data —At different speeds —In different formats All slower than CPU.
1 Calorimeters LED control LHCb CALO meeting Anatoli Konoplyannikov /ITEP/ Status of the calorimeters LV power supply and ECS control Status of.
CALO DCS upgrade A. Konoplyannikov, M. Soldatov, A. Ostankov, Yu. Guz (IHEP, Protvino) V. Kudryavtsev (BINP, Novosibirsk)
Clara Gaspar, December 2012 Experiment Control System & Electronics Upgrade.
A Super-TFC for a Super-LHCb (II) 1. S-TFC on xTCA – Mapping TFC on Marseille hardware 2. ECS+TFC relay in FE Interface 3. Protocol and commands for FE/BE.
Configuration database status report Eric van Herwijnen September 29 th 2004 work done by: Lana Abadie Felix Schmidt-Eisenlohr.
TELL1 command line tools Guido Haefeli EPFL, Lausanne Tutorial for TELL1 users : 25.February
March 7th 2005 Stefan Koestner LHCb week ECS-tools for the CCPC/Tell1 (a tutorial in 3 acts): (1) CCPC/PVSS Interface: - few comments on the server - quick.
MND review. Main directions of work  Development and support of the Experiment Dashboard Applications - Data management monitoring - Job processing monitoring.
Clara Gaspar, April 2014 ECS (Marseille+Annecy+CERN) 1 FPGA CCPC Firmware DIMServer Mini DAQ Test UIHW Description UIOperation UI Control PC WinCC-OA PCIe.
Clara Gaspar, April 2006 LHCb Experiment Control System Scope, Status & Worries.
Firmware Overview and Status Erno DAVID Wigner Research Center for Physics (HU) 26 January, 2016.
1 Basic Processor Architecture. 2 Building Blocks of Processor Systems CPU.
Control and operation of detector systems and their readout electronics in a complex experiment control system Stefan Koestner (CERN) on behalf of the.
ATLAS DCS ELMB PRR, March 4th 2002, H.J.Burckhart1 Embedded Local Monitor Board ELMB  Context  Aim  Requirements  Add-ons  Our aims of PRR.
Rutherford Appleton Laboratory September 1999Fifth Workshop on Electronics for LHC Presented by S. Quinton.
Software for tests: AMB and LAMB configuration - Available tools FTK Workshop – Pisa 13/03/2013 Daniel Magalotti University of Modena and Reggio Emilia.
SEPTEMBER 8, 2015 Computer Hardware 1-1. HARDWARE TERMS CPU — Central Processing Unit RAM — Random-Access Memory  “random-access” means the CPU can read.
August 24, 2011IDAP Kick-off meeting - TileCal ATLAS TileCal Upgrade LHC and ATLAS current status LHC designed for cm -2 s 7+7 TeV Limited to.
October 12th 2005 ICALEPCS 2005D.Charlet The SPECS field bus  Global description  Module description Master Slave Mezzanine  Implementation  Link development.
Jun 18th 2009 SPECS system D.Charlet The SPECS field bus ACTEL APA 150 GLUE.
Clara Gaspar, February 2007 LHCb’s Experiment Control System & Electronics Integration Step by Step.
DeLiDAQ-2D ─ a new data acquisition system for position-sensitive neutron detectors with delay-line readout F.V. Levchanovskiy, S.M. Murashkevich Frank.
of the Upgraded LHCb Readout System
Use of FPGA for dataflow Filippo Costa ALICE O2 CERN
Control of ASICs via GBTx
Enrico Gamberini, Giovanna Lehmann Miotto, Roland Sipos
Erno DAVID, Tivadar KISS Wigner Research Center for Physics (HU)
MiniDAQ2 Workshop Control System.
Front-end digital Status
IEEE - Nuclear Science Symposium San Diego, Oct. 31st 2006
Chapter 13: I/O Systems.
Presentation transcript:

Clara Gaspar on behalf of the ECS team: CERN, Marseille, etc. October 2015 Experiment Control System & Electronics Upgrade

Clara Gaspar, October 2015 ECS & Upgrade Electronics 2 ❚ ECS Design doesn’t change (in principle) ❙ Same tools: ❘ Communications: DIM ❘ Supervision: WinCC-OA ❘ Sequencing and Automation (FSM): SMI++ ❙ Same philosophy: ❘ Generic tools to describe the hardware (FwHw) 〡 Board Types -> “chips” -> registers => Boards ❘ Operation tools to Configure/Monitor boards 〡 “Recipes” for different configuration modes 〡 Stored in Configuration DB ❙ New electronics will be interfaced like before

Clara Gaspar, October 2015 ❚ Two types of boards to control: ❙ Back-End boards (Readout Boards, etc.) ❘ Physically only one board type (PCIe40): ❘ But logically different types TELL40, S-ODIN, SOL40 ❘ (Past equivalent: fwCcpc) ❙ Front-End Boards ❘ Sub-detector Specific ❘ Several protocols available (via GBT-SCA) ❘ (Past equivalent: fwSpecs) 3 Electronics Interfaces

Clara Gaspar, October 2015 BE Board Interface ❚ Physically only one board type (PCIe40) for: TELL40, S-ODIN, SOL40, etc. ❙ But logically different types ( different firmware -> different “registers”) ❚ Tools will be provided centrally: ❙ Low-level libraries and command-line tools: ❘ Allow accessing the different registers (PCIexpress) ❙ A DIM server: ❘ Will implement higher-level commands to configure and monitor the board components ❙ A WinCC-OA component ❘ Providing the high-level description and access of all electronics components 4

Clara Gaspar, October 2015 ECS BE Dataflow 5 Control PC Test UIHW Description UIOperation UI FPGA Firmware DIMServer PCIe40 PCIe driver  PCIe Library  GbtServ PCIe Host PC WinCC-OA

Clara Gaspar, October 2015 FE Board Interface ❚ Interface to FE Electronics ❙ Two Architectures envisaged: ❘ FE electronics in one single FE board ❘ FE electronics accessed via a “Service” board (masterGBT SCA via “long” Elink) 6

Clara Gaspar, October 2015 FE Board Protocols ❚ Interface to the FE Chips ❙ The GBT-SCA provides the following protocols: ❘ 16 x I2C master controllers ❘ 1 x JTAG master controller ❘ 32 x ADC channels (multiplexed) ❘ 1 x Memory bus (32 bits) controller ❘ 4 x PIA (Parallel Interface Adapter) controllers ❘ 1 x SPI (Serial Peripheral Interface) bus ❘ 4 x DAC channels ❙ Recommended protocols (for bulk transfers) are: ❘ I2C ❘ SPI using independent chip selects (daisy chained SPI not allowed) 7

Clara Gaspar, October 2015 FE Addressing ❚ FE Chip Register Address: [ ] fixed variable 8 Control PC

Clara Gaspar, October 2015 ECS FE Dataflow 9 Control PC Test UIHW Description UIOperation UI GBT Link SOL40 FPGA Firmware DIMServer SOL40 PCIe driver  PCIe Library  GbtServ PCIe Host PC WinCC-OA

Clara Gaspar, October 2015 FE ECS Software/firmware ❚ Will be centrally provided: ❙ The FPGA firmware for the SOL40 board ❘ Will prepare, send and receive the GBT-SCA frames for the various user protocols 〡 Should take load away from CPU as much as possible ❙ Low-level libraries and command-line tools: ❘ Will allow accessing the different FE chips ❙ A DIM server: ❘ Will implement higher-level commands to configure and monitor the FE chips ❙ A WinCC-OA component ❘ Providing the high-level description and access of all electronics components 10

Clara Gaspar, October 2015 ❚ For both BE and FE boards 11 WinCC-OA: Test UI

Clara Gaspar, October 2015 WinCC-OA: HW tool 12 Control PC HW Description UI GBT Link SOL40 FPGA Firmware DIMServer SOL40 PCIe driver  PCIe Library  GbtServ PCIe Host PC WinCC-OA XML Description

Clara Gaspar, October WinCC-OA: HW tool

Clara Gaspar, October 2015 WinCC-OA: Configuration 14 Control PC HW Description UIOperation UI WinCC-OA Conf.DB ❚ Configuration Tools ❙ Use “Recipes”: Groups of settings for many registers GBT Link SOL40 FPGA Firmware DIMServer SOL40 PCIe driver  PCIe Library  GbtServ PCIe Host PC

Clara Gaspar, October 2015 ❚ MiniDAQ Based ❙ BE boards: ❘ DIM Server adapted ❘ FwCcpc/FwHw adapted accepts XML input ❘ Started building Tell40 panels ❙ FE Boards: ❘ SOL40 Firmware 1 st version exists ❘ Building low-level libraries (GBT-SCA protocols) ❘ Extending the XML description ❙ In general: ❘ FwCcpc / Ccserv (tell1) ❘ FwSpecs / SpecsServer 15 Current Status FwGbt / GbtServer 15 FPGA CCPC Firmware DIMServer Mini DAQ PCIe driver  PCIe Library  Ccserv PCIe

Clara Gaspar, October 2015 Scalability & Efficiency ❚ Configuration and Monitoring speed ❙ Is not just data size / bandwidth ❙ Depends on: ❘ How the data is distributed, for ex.: 〡 A few large registers or many small ones ❘ Are blocking operations needed, for ex.: 〡 A register needs to be set and read-back before configuring the next one 〡 or read-modify-write operations that need to be done by the back-end ❘ Which user protocol is used and how it is used, for ex.: 〡 Some I2C devices needed an extra I2C operation to write a sub-address before the block of data could be written 〡 Some did not implement auto-increment so block transfer could not be used ❙ Try to influence design early enough… 16