1. André Augustinus 6 October 2005 Cabling, Interlocks, Racks Some remarks

2. André Augustinus 6 October 2005ALICE DCS Workshop Introduction  Re-iterate and update a few remarks from last workshop on interlocks and cabling  Stefano will cover some rack related issues

3. André Augustinus 6 October 2005ALICE DCS Workshop Interlocks  This addresses only the hardwired interlocks  We received no more additional input from the detectors since last workshop  We discussed with the principal sources of hardwired interlock signals: cooling and gas systems

4. André Augustinus 6 October 2005ALICE DCS Workshop Interlocks [cooling]  Any serious malfunctioning that would justify an interlock will affect the whole plant  Therefore the TS/CV group has foreseen only a single interlock signal per cooling plant (=per detector)  Only SDD (as far as known to us) had foreseen to receive more interlocks TS/CV was not aware of this We will need to see what are their exact requirements

5. André Augustinus 6 October 2005ALICE DCS Workshop Interlocks [gas]  The gas system will provide a single hardwired signal per gas system (=per detector)  This signal will be a copy of a software status indicating if the gas system is working nominally  There will be no delays in the signal Gas quality in the detector will only start to deteriorate after some time

6. André Augustinus 6 October 2005ALICE DCS Workshop Interlocks  If this does not suit you… …It’s too late ! … come with justification to re-discuss with TS/CV or Gas  Remaining issues: Distribution of the signal to the equipment (mainly power supplies) Implementation of delays (especially for gas) Did any of you already worked on these issues? Other (non gas or cooling) interlocks E.g. PMD “detector position” interlock

7. André Augustinus 6 October 2005ALICE DCS Workshop Cabling issues  Several issues related to cabling were presented in the last workshop  These concern control, interlock and network cables  In most cases the responsibility is as follows: We define the cables and connectors You define where they go (the ‘nodes’, in the cable database)

8. André Augustinus 6 October 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 SCEM: 04.21.60.491.2 SCEM: 04.21.60.430.5 13 June 2005 defined prototype exists

9. André Augustinus 6 October 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] 13 June 2005 Need to be ordered

10. André Augustinus 6 October 2005ALICE DCS Workshop Cabling issues  With the rack layout becoming clearer, other cables can be defined: CAEN bus from branch controller to easy crates ‘normal’ CAN bus (Iseg HV, crate control Wiener VME) Network (to Wiener LV, CAEN SY, Switches etc.)  Communicate any change in rack layout to Jean- Pierre Vanuxem and/or us These files are our source of information!

11. André Augustinus 6 October 2005ALICE DCS Workshop Summary  One interlock per detector for cooling and gas Discuss with SDD Look at distribution of interlock signal  Cabling more and more defined Communicate your ELMB needs Keep your rack layout up to date