S.Sergeev (JINR)

Tracker consists of  4 chambers of 4 views each In total ~7200 drift tubes (~450 per view) To be controlled/monitored  HV system  LV system  Gas system  Thermo-sensors

Only “CERN Standard” solutions PVSS II + JCOP framework as a basement for DCS development PVSS II is a SCADA toolkit for high level control system development  Visual programming (active pictures)  Object-oriented (data point)  encapsulation  inheritance  member fields  Event-driven  Events related to a change of a data point element (member field) value  Interpretive system  Language – some mixture of C, C++ and Pascal  Distributed system It is assumed that tracker has it’s own DCS PC

 Straw tracker needs 2 HV channels per view => 32 HV channels  Possible HV power supplies  CAEN HV modules A1535 – 24 channels, 3.5 KV, 1 mA  CAEN mainframe SY2527LC (up to 6 modules)  The most convenient refresh period ~1 sec – to be discussed

Windows PC OPC server PVSS II Windows PC Could be single PC TCP/IP COM/DCOM (TCP/IP) OPC client Ethernet

 Should be used Wiener power supply  Current per plain (view) ~30A  Wiener MPV 8008L could be used  8 channels per module => one unit per station  0V... 8V  10A  50W per channel  12bit control DAC, ADC  <10mV pp  Communication by TCP/IP, USB, CAN-bus  2 modules per chamber  The most convenient refresh period ~1 sec – to be discussed

Windows PC OPC server PVSS II Windows PC Could be single PC COM/DCOM (TCP/IP) OPC client Ethernet Terminator CAN-Bus Interface (Quazer XXXX) CAN-Bus

 JCOP framework + CERN Gas working group  CERN Standard 2-component gas mixer  For safety (working in vacuum)  Up to 32 gas segments per view (???)  Two electric valves per plane (station???) with 2 flow meters to cut the gas in case of broken straw + manual valves to cut off the segment with the broken straw A lot of open questions

 View (plane), 176 measurements in total  1 temperature measurement per cover on the bottom of the PCB (to measure gas and board temp), requires 2 ADC channels  3 (?) voltages + 1 current measurement per cover  There are 28 covers/view  4 temperature measurements for mechanics.  28*(2+4)+4=176 ADC channels per view  Chamber  4 views  704 ADC measurements/chamber, 11 ELMBs/chamber  Detector  4 chambers  44 ELMBs total  Refresh period - to be discussed

Windows PC OPC server PVSS II Windows PC OPC client Ethernet 4 chambers CAN-Bus Interface (Quazer XXXX) CAN-Bus 11 ELMBs per station, 44 ELMBs in total, 4 CAN-bus branches

OPC client OPC server GUI Tracker Windows PC OPC server PVSS II Central DCS Windows PC OPC clients Ethernet OPC client GUI PVSS UI Could provide 1 sec refresh period Depends on PVSS lisence

Any detector DCS has three trees  Physical tree in terms rack-crate-board- channel. Used for geographical addressing of infrastructure units  Logical tree in terms detector-subdetector- station-plane-channel-parameter. Used for navigation in the detector view  FSM tree. Used to propagate commands from top layer to bottom layer and states from the bottom to the top. Usually it is similar to the Logical tree

NA62 Root Tracker Station1 View X LV HV1 HV4 Cover1 Cover28 Temp. Voltage LV Voltage Current Temp. HV Voltage Current Temp. Ramping Trip TO

 It seems reasonable to use individual Windows PC for Tracker DCS running all OPC servers  At the development phase this PC could also run local OPC clients with data refresh period ~ 1 sec  After the development is finished it seems to be reasonable to stop local OPC clients and to use only PVSS data with refresh period ~30 sec  To avoid crowds at a single Central DCS PC screen it seems reasonable to run tracker GUIs (PVSS UI) at the tracker DCS PC leaving the “PVSS system” at the central DCS PC.  To allow simple maintenance, the tracker panels, functions etc. should be converted to the JCOP framework component.