André Augustinus 13 June 2005 User Requirements, interlocks, cabling, racks, etc. Some remarks.

Slides:



Advertisements
Similar presentations
André Augustinus 22 June 2004 DCS Workshop Status on services controls.
Advertisements

André Augustinus 5 March 2007 Infrastructure status.
André Augustinus 15 March 2003 DCS Workshop Safety Interlocks.
HV-LV DCS Workshop – 16/03/2004 G. De Cataldo, A. Franco, A.Tauro - INFN Bari Progress report on the HMPID LV System Cabling and LV sectorsCabling and.
André Augustinus 16 June 2003 DCS Workshop Safety.
1 WP 10- High Voltage ’06 March 23 rd HV Trip studies  See previous meetings for the foreseen tests on LBC44  Started late by Clermont people when Clermont.
Supervision of Production Computers in ALICE Peter Chochula for the ALICE DCS team.
David Emschermann DCS Workshop – PI Heidelberg – 22/01/2007 How to power up the TRD David Emschermann Physikalisches Institut Universität Heidelberg updated.
DCS aspects of TDAQ racks in USA15 and SDX1 Y. Ermoline et al. ATLAS Week, CERN, 15 February 2005.
Marc R. StockmeierDCS, KIP ALICE WEEK FALL 2003 TRD DCS Status ● DCS-board status ● Poweresupply ●
DSS Advisory Board Christoph Schäfer Rack Safety System.
3 June 2003U. Frankenfeld1 TPC Detector Control System Status.
LHC Gas Control System Stefan Haider EP-TA1-GS ALICE DCS workshop, S.Haider2 Outline Introduction and working philosophyIntroduction and working.
1 Status & Plans DCS WS L.Jirdén. 2 DCS Planning FINAL INST COM- MISS BEAM OP PRE- INST DET DCS URD ENG. SOLUTIONS PROTOTYPE SUBSYSTEM.
L.Jirden1 Update on Power Supplies DCS WS L.Jirden u Wiener u Caen u Global Support Contracts.
André Augustinus 10 September 2001 Common Applications to Prototype A two way learning process.
André Augustinus 16 September 2002 Safety issues.
V. Bobillier1 Long distance cable installation status Calorimeter commissioning meeting.
15/12/10FV 1 Common DCS hardware. General ideas Centralized system: o Common computers. Detector dedicated computers (with detector participation) only.
Ethernet IP solution for ATLAS IBL and CMS Pixel detectors CO 2 cooling plants Lukasz Zwalinski PH/DT/DI.
Electronic Systems Support CAN Branch PSU Designed: Bjorn Halgren PH-ESS Responsible:Paul Harwood.
DCS T0 DCS Answers to DCS Commissioning and Installation related questions ALICE week T.Karavicheva and the T0 team T0 DCS Answers to.
André Augustinus 10 September 2001 DCS Architecture Issues Food for thoughts and discussion.
1 Status and Plans DCS workshop L.Jirdén u Budget u Status u Planning u Goals for end 2002.
1 Responsibilities & Planning DCS WS L.Jirdén.
André Augustinus 17 June 2002 Technology Overview What is out there to fulfil our requirements? (with thanks to Tarek)
André Augustinus 13 June 2005 Control through serial links RS232 etc.
André Augustinus 10 October 2005 ALICE Detector Control Status Report A. Augustinus, P. Chochula, G. De Cataldo, L. Jirdén, S. Popescu the DCS team, ALICE.
André Augustinus 26 October 2004 ALICE Technical Board DCS for ‘services’ costs On behalf of Lennart Jirdén.
André Augustinus 6 October 2005 Cabling, Interlocks, Racks Some remarks.
André Augustinus OPC news, versions to use on behalf of Sorina Popescu.
André Augustinus 21 June 2004 DCS Workshop Detector DCS overview Status and Progress.
André Augustinus 10 March 2003 DCS Workshop Detector Controls Layout Introduction.
15-16/3/04 DCS workshop G. De Cataldo, A,.Franco and A. Tauro 1 Answers from the HMPID to the ACC questions 1.Concerning global DCS overview drawing 2.Concerning.
André Augustinus 16 September 2002 PVSS & Framework How to get started.
CERN, O.Pinazza: ALICE TOF DCS1 ALICE TOF DCS Answers to DCS Commissioning and Installation related questions ALICE week at CERN O. Pinazza and.
JCOP/DCS Plans for HW Upgrade A. Augustinus (ALICE), C
October 9th 2006ALICE WEEK - DCS WorkShop1 DEVICE USER SUPPORT OVERVIEW - Presentation - First Line Support - Reference System - Current Developpement.
André Augustinus 16 June 2003 DCS Workshop General Purpose Monitor.
André Augustinus 9 October 2006 Interlocks update.
Alice MTR DCS F.Jouve 15 th DCS workshop CERN 13/03/2006 UX-A,B,D Detector PVSS II Detector Ethernet Database(s) OPC client DIM client 1672 Detector ?
André Augustinus 21 June 2004 DCS Workshop Follow-up from last workshop.
DCS Workshop, CERN MARCH ACORDE (Alice Cosmic ray detector) 60 scintillator modules (120 HV channels) Each module will have two scintillator counters.
NA62 straw tracker DCS Straw tracker overview Bulk power supply Power supply distribution and monitoring LV + monitoring HV Temperature monitoring Gas.
DCS Workshop 17 June 2002 PHOS DCS status Serguei Sadovski.
André Augustinus 16 September 2002 Muon tracker URD summary or, what we understand from the URD.
24/03/2010ALICE TOF General Meeting March TOF hardware and data taking 2010 Andrea Alici Museo Storico della Fisica e Centro Studi e Ricerche “Enrico.
5th March 0718th DCS Workshop1 News on ISEG & WIENER Lionel Wallet, CERN High Voltage, Low Voltage & VME Crate control.
André Augustinus Infrastructure  Turbines  Radmon  Thermocouple readout  Netgear redundancy  Other cavern items  Cooling CRs  Other CR and surface.
European Organization for Nuclear Research DCS remote control in NA62: Equipment & Control Integration. Mathias Dutour NA62 Collaboration 9th December.
Straw electronics status  Signal generation and formation in straw  Webs + Cover  Backend  TTC  Services + DCS  New engineer on VIA program Georgios.
14 November 08ELACCO meeting1 Alice Detector Control System EST Fellow : Lionel Wallet, CERN Supervisor : Andre Augustinus, CERN Marie Curie Early Stage.
AFP Trigger DAQ and DCS Krzysztof Korcyl Institute of Nuclear Physics - Cracow on behalf of TDAQ and DCS subsystems.
Status of the NA62 network R. Fantechi 23/5/2012.
Report on database work for INB in ALICE Latchezar Betev (ALICE) Information Session INB – June 8, 2006.
ATLAS DCS ELMB PRR, March 4th 2002, H.J.Burckhart1 Embedded Local Monitor Board ELMB  Context  Aim  Requirements  Add-ons  Our aims of PRR.
22/03/11FV 1 NA62 DCS CAN bus lines. Short reminder General properties of CAN bus o Up to 64 nodes on one bus o Different devices need different buses.
DCS workshop,march 10th P.Saturnini, F. Jouve Slow control trigger of the muon arm Muon trigger of the muon arm Low voltage VME Crate External parameters.
E Ethernet C CAN bus P Profibus HV HV cables LV LV cables (+busbar) S Serial (RS232) Signal cable Other/Unknown Liquid or Gas Cable and/or Bus PCI-XYZ.
1 Update on Power Supplies TB L.Jirden u LV u Concerns u Orders & deliveries u Maintenance u HV u Overview u purchasing.
André Augustinus 17 June 2002 Detector URD summaries or, what we understand from your URD.
D. EliaALICE week / DCS workshop - Sept 20, SPD Power Supply System DCS status Domenico Elia INFN Bari.
André Augustinus 16 June 2003 DCS Workshop Detector DCS status Overview and news.
1 Infrastructure and DCS Presentation of the Infrastructure Controls aspect in the ALICE DCS Based on U ser R equirements D ocument …you should still know.
André Augustinus 18 March 2002 ALICE Detector Controls Requirements.
1 COSTING DCS WS L.Jirdén. 2 LAN WAN Storage Configuration DB, Archives FSM servers Terminal servers, ACR consoles, etc Experimental equipment.
General aspects: Optical links :
Institute of Nuclear Physics Polish Academy of Sciences
DT Infrastructure: LV, HV, Gas
TPC Detector Control System
Presentation transcript:

André Augustinus 13 June 2005 User Requirements, interlocks, cabling, racks, etc. Some remarks

André Augustinus 13 June 2005ALICE DCS Workshop Introduction  Overview drawings and URDs should be our main depository of knowledge  Over last few months we realized some information is still “missing”, even on hardware issues such as: Interlocks Rack contents Cabling

André Augustinus 13 June 2005ALICE DCS Workshop Overview  Very brief on URDs etc.  Reminder on interlocks  Some remarks on ‘missing’ information  Information on cabling and cabling database

André Augustinus 13 June 2005ALICE DCS Workshop URD and overview drawing  Regular (strong) requests to update your URDs (e.g. virtually every DCS workshop) No real reaction from the detectors We see no miracle solution here We just insist…  Overview drawings seem to have a bigger success Regular updates from detectors… … and from our side after detector discussions

André Augustinus 13 June 2005ALICE DCS Workshop Interlocks  Last DCS workshop(s) we requested your input on interlocks Some detectors volunteered (more or less complete) information.  The information on hardwired interlocks is critical now: Systems that generate interlocks are being finalized (gas, cooling) Cables need to be defined, patch boxes, etc.

André Augustinus 13 June 2005ALICE DCS Workshop Interlocks, last warning  You can still communicate your requirements on your hardwired interlocks …... but you have to be fast now!  If we get no input from you, we can only make an educated guess of your needs!  You will then only be provided with the minimum Later additions or modifications might be difficult, costly or even impossible! So: better think now!

André Augustinus 13 June 2005ALICE DCS Workshop Interlocks, last warning  The minimum we think providing:  Only for those detectors that have gas and/or cooling systems: A single signal indicating gas is OK/Not OK A single signal indicating cooling is OK/Not OK  That’s all ! If you need more (or less): react now!

André Augustinus 13 June 2005ALICE DCS Workshop “Missing” information  We have entered the installation phase now Information on several issues is vital to proceed with the installation: Cabling has to be defined, ordered and installed Racks need to be connected and equipped Service infrastructure needs to defined, ordered and installed (network, cooling, etc.). It is all on a bigger scale now, we are talking large numbers now ALICE is your detector times or even more !

André Augustinus 13 June 2005ALICE DCS Workshop “Missing” information We talk about: many kilometres of cables, A network installation with hundreds of Ethernet ports Installation and equipping hundreds of racks Lead times for this (including design, ordering and installation) is many months, sometimes more than half a year. All of this you expect to be available (and operational) when you arrive with your detector and associated equipment Remember: we are mid-2005 now

André Augustinus 13 June 2005ALICE DCS Workshop “Missing” information  On many issues the information it there People seem reluctant to take a ‘final’ decision  Dedicated meetings are organized now, per detector On cabling and rack contents  Collect the “missing” information that is not really missing  Identify the really open issues

André Augustinus 13 June 2005ALICE DCS Workshop Cabling issues  Several issues related to cabling were identified in cabling and rack meetings Control cabling (fieldbusses etc.) Interlock cables Network cabling  This seem to be a grey area; there seem to be some confusion on who is responsible for what

André Augustinus 13 June 2005ALICE DCS Workshop Cabling issues [General remarks]  You are responsible to define the cabling for your detector You know what you need where Cables will be in the database for your detector But, We will in some cases define the type of cable and/or connectors We will define in some cases the start or end point We will help you to update your cable database for this  If you are not sure, contact us and mark your control cables as ‘provisional and to be checked by DCS’

André Augustinus 13 June 2005ALICE DCS Workshop Cabling issues [control cabling]  Control cabling covers mainly fieldbusses: CANbus for the ELMBs “CANbus” for the CAEN Easy system CANbus for ISEG High Voltage CANbus for Wiener VME crate control Ethernet (?) for Wiener Low Voltage …

André Augustinus 13 June 2005ALICE DCS Workshop Cabling issues [control cabling: ELMB CANbus]  Carries bus and power For ALL detectors power is provided centrally All cabling starts from CR3 Both power (rack Z08) and bus (racks Z01-Z06) Up to the first ELMB a ‘big’ cable is used To limit voltage drop A ‘patch box’ is under development A ‘standard’ ELMB to ELMB cable is under definition

André Augustinus 13 June 2005ALICE DCS Workshop Cabling issues [control cabling: ELMB CANbus]  Do not use flat cables when not strictly needed  Sensor – ELMB cabling is up to you But we can help  Related point: Signal adapters are (will be) centrally available Communicate us your needs! Rack mounted PCs With Kvaser CAN card [in CR3] ELMBs [on detector?] CANbus Power patchbox CANbus & Power [in same cable] to Sensors Defined/delivered by central DCS team (paid by detectors) Guidelines by central DCS team Central power supplies [in CR3]

André Augustinus 13 June 2005ALICE DCS Workshop Cabling issues [control cabling: CAEN ‘CANbus’]  Special bus from branch controller (in CR) to Easy crates (in UX) 50-wire cable special daisy-chain from crate to crate Also connects CAEN 48V power supply  Standard cable under definition (with CAEN) To get to first Easy crate  Start to look at daisy-chaining Inside rack, or inter-rack

André Augustinus 13 June 2005ALICE DCS Workshop Cabling issues [control cabling: other]  ISEG (HV) and  Wiener (VME crate control) Standard CANbus A standard cable is under definition  Let us know if you have other CAN controlled devices  Wiener Low Voltage will use Ethernet Will be included in Ethernet infrastructure You have to define where your power supplies will be

André Augustinus 13 June 2005ALICE DCS Workshop Cabling issues [interlock cabling]  Standard cabling/connectors will be used for Gas and Cooling interlocks Currently under definition  Starting point will be defined by us With gas and cooling groups  Receiving end to be defined by you What device(s) will receive the interlock  Let us know your other interlocks Use same standards?

André Augustinus 13 June 2005ALICE DCS Workshop Cabling issues [network cabling]  You have to express your needs  We will order the network from IT/CS Constraint: no IT equipment (switches) in cavern! IT will provide cabling up to UX racks All switches and cabling/equipment behind your switches in UX are your responsibility  Standardize for non-IT network equipment, cabling and connectivity Major effort by TRD group  Let us know your needs, if you haven’t done yet

André Augustinus 13 June 2005ALICE DCS Workshop Summary  Overview drawings are extremely useful But it gives only the “hardware view”, so: Don’t forget the URDs !  Urgently communicate your needs on hardwired interlocks Otherwise you only get the ‘default’  An effort is ongoing to extract ‘missing’ information on cabling and racks  Control related cabling need to be in your database We will provide you with standards and guidelines and help you updating the database