150 likes | 318 Views
Straw Tracker DCS. S.Sergeev (JINR). NA-62 Detector. Straw Tracker. 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. DCS constraints. Only “CERN Standard” solutions
E N D
Straw Tracker DCS S.Sergeev (JINR)
Straw Tracker 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
DCS constraints 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
HV system (i) • 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
HV system (iI) Windows PC PVSS II Windows PC OPC client OPC server Could be single PC Ethernet COM/DCOM (TCP/IP) TCP/IP
LV system (I) • Should be used Wiener power supply • Current per plain (view) ~30A • Wiener MPV 8008L could be used • 8channels per module => one unit per station • 0V ... 8V • 10A • 50W per channel • 12bit control DAC, ADC • <10mVpp • Communication by TCP/IP, USB, CAN-bus • 2 modules per chamber • The most convenient refresh period ~1 sec – to be discussed
LV system (iI) Windows PC PVSS II Windows PC OPC client OPC server Could be single PC COM/DCOM (TCP/IP) CAN-Bus Interface (QuazerXXXX) Ethernet Terminator CAN-Bus
Gas system • 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
I,V,T monitoring (I) • 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
I,V,T monitoring (II) Windows PC PVSS II Windows PC OPC client OPC server Ethernet CAN-Bus Interface (QuazerXXXX) CAN-Bus 11 ELMBs per station, 44 ELMBs in total, 4 CAN-bus branches 4 chambers
Local debugging clients Could provide 1 sec refresh period PVSS UI GUI Depends on PVSS lisence GUI OPC client OPC client OPC server Central DCS Windows PC PVSS II Tracker Windows PC OPC server OPC clients Ethernet
DCS trees 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
Logical tree NA62 Root LV Voltage Tracker Current Station1 Temp. View X LV HV HV1 Voltage HV4 Current Cover1 Temp. Cover28 Ramping Temp. Trip TO Voltage
DCS Development and commissioning • 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.