1. Progress on Motors/DCS Helen Heath, Magnus Loutit

2. Progress on DCS • Useful meetings at CERN before Easter • ML and HH met with John Fullerton from BE for practical advice on the CEDAR motor controls • Also met with the NA62 DCS group to discuss Motor controls and DCS in general • Detailed minutes of the DCS meeting at https://indico.cern.ch/conferenceDisplay.py?confId=170350

3. Motor Controls • Information from JF • Once set up the CEDARs are very stable. • CEDAR adjustment is not anticipated to be performed regularly during runs – expert operation • X and Y motors currently take ~30s from one end to the other. • Approach to ~2mm and then pulse.

4. EN/ICE involvement • EN/ICE group will develop the PLC system and integrate into a UNICOS application • There involvement is now approved • Magnus has produced a Motor Control Specification (attached) • EN/ICE will translate into their standard project specification. • Equipment will be ordered through EN/ICE

5. Actions DCS meeting re motors • Requirement/Description document with details of the control logic to be prepared and sent to EN/ICE: as soon as possible (the week after Easter) • Approval of the project by EN/ICE: no later than week of 23 April, • Delivery/Commisioning deadline: mid-June

6. General DCS issues • Considered Document prepared by Tim • Detailed discussion • Queries circulated in an updated document. • These need to be clarified

7. HV system – NA62 Standard • Assign to channel a symbolic name • Set output voltage (VSET) • Set max. output current (ISET) • Set output voltage software limit (SVMAX) • Set voltage ramp-up speed (RAMP-UP) • Set voltage ramp-down speed (RAMP-DOWN) • Set TRIP parameter • Enable/disable POWER ON option • Switch channel ON/OFF • Monitor output voltage (VMON) • Monitor output current (IMON) • Monitor channel status

8. HV questions • Draft Document has TTRP Time at current>ITRP • Not a standard parameter. Is this necessary? Or is setting a trip current sufficient? If not why not? Trip would normally produce a fatal alarm. • Note there is expected to be over and undervoltage warning as well as fatal alarms • Expect Operating voltage (VSET) to be set every run but other parameters would be static from run to run. • Are there any issues with this?

9. HV A1536 card monitoring • Board Temperature • Does this need a fatal alarm? It would seem likely but should there be a warning before? Warning might cut off board. • Connection Error • Is this a cable disconnected from the card (seems unlikely) or a loss of control (Note it wasn’t clear that the hardware can detect a disconnected cable).

10. Channel Layout • We need to add physical layout of the channels – which channel is which PMT • Any logical arrangement is fine someone just needs to do this. Who?

11. Not relevant • Nino – control not included in the “012 Technical Run • TEL62 • PMT pulser

12. Gas Controls • Old Gas controls are standalone and will be used in 2012. • Will not be integrated in the DCS • Need to discuss whether data will be displayed. • Provision for 8 temperatures to be read out • DCS group would like to know where the sensors are . Are there warnings or are these just for display?

13. Cooling • Status of cooling could be read by the CEDAR Motor control PLC if cooler is near CEDAR • If so then this needs to be added to the motor-control project. • What sort of flow meters are envisaged and how are they connected. • Enclosure monitoring. • Require mapping of temperatures to ELMB channels • Where are the probes?

14. Next Steps • Procurement of motor system • Update of DCS document