150 likes | 348 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 BE VME crates – to be clarified soon.
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 • BE VME crates – to be clarified soon
TRACKER DCS constraints • Only “CERN Standard” solutions • PVSS II + JCOP framework as a basement for DCS development • 4 chambers in 4 locations => 4 CAN-bus branches => 1 CAN-bus adapter card • Baseline • Tracker has it’s own DCS PC • We would like to have our own “PVSS system” at this PC
HV system (i) • Straw tracker needs 2 HV channels per view => 32 HV channels, could be expanded in the future • 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
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) • Current per plain (view) ~30A • Wiener PL506 + MDH 2-7 V seems to be OK, granularity to be fixed later • 1 power supply mainframe per chamber • The most convenient refresh period ~1 sec
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 CAN-Bus One branch per chamber PL506 Terminator +5V to chamber views ELMBs, VME crates
Gas system • JCOP framework + CERN Gas working group • CERN Standard 2-component gas mixer • For safety (working in vacuum) • Up to 28 gas segments per view (???) • Two electric valves per plane (station???) with 2 flow meters and manometers to cut the gas in case of broken straw + manual valves to cut off the segment with the broken straw Open questions to be clarified soon
IVT monitoring (I) • View (plane) • There are 28 covers/view • 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 • 4 temperature measurements for mechanics. • 28*(2+4)+8=176 ADC channels per view • Chamber • 4 views • 704 ADC measurements/chamber, 11 ELMBs/chamber • Detector • 4 chambers • 44 ELMBs total • 2816 ADC channels • Refresh period - 1..10 sec
IVT monitoring (II) Windows PC PVSS II Windows PC OPC client OPC server Ethernet CAN-Bus Interface (QuazerXXXX) CAN-Bus 11 ELMBs per chamber, 4 CAN-bus branches LV PS 4 chambers
Local debugging clients As a Possible back-up solution PVSS UI Could provide 1 sec refresh period 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/FSM tree NA62 Root LV Voltage Tracker Current Chamber1 Temp. View X LV HV HV1 Voltage HV2 Current Cover1 Temp. Cover28 Ramping Temp. Trip TO Voltage
DCS Development and commissioning • It has been decided to use individual Windows PC for Tracker DCS running all OPC servers • At the development phase this PC also could run local OPC clients with data refresh period ~ 1 sec (back-up solution) • To allow simple maintenance, the tracker panels, functions etc. should be converted to the JCOP framework components.