Download Straw_Tracker_DCS - Indico

S.Sergeev (JINR)
Tracker consists of

4 stations of

4 views (planes) 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


Interpretive system


Events related to a change of a data point element (member field)
value
Language – some mixture of C, C++ and Pascal
Distributed system
 Straw
tracker needs 4 HV (2 HV?) channels
per view => 64 HV channels (32 channels)
 Possible HV power supplies

CAEN HV modules



 If
A1832 – 12 channels, 6KV, 1 mA or
A1535 – 24 channels, 3.5 KV, 1 mA
CAEN mainframe SY2527LC (up to 6 modules)
Mainframe SY1527LC is used => could be
shared with other sub-detectors
Windows
PC
OPC server
OPC
client
PVSS II
Windows or
Linux PC
Could be
single PC
Ethernet
TCP/IP
COM/DCOM
(TCP/IP)
 Should
be used Wiener power supply
 Current per plain (view) ~3A
 Wiener MPV 4008L could be used







4 channel per module => one unit per station
0V ... 8V
5A
40W per channel
12bit control DAC, ADC
<10mVpp
Communication by TCP/IP, USB, CAN-bus
Windows
PC
CAN-Bus
Interface
(Quasar XXXX)
CAN-Bus
OPC server
Could be
single PC
OPC
client
PVSS II
COM/DCOM
(TCP/IP)
Windows or
Linux PC
Ethernet
Terminator
 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
Open questions

View (plane), 60 measurements in total, 0.5C
 1 temperature measurement per cover on the bottom of
the PCB (to measure gas and board temp)
 1 voltage measurement per cover
 4 temperature measurements for mechanics. There are
28 covers/view

Station
 4 views
 240 measurements/station (112 volt, 128 temp)
 6 ELMBs

Detector
 4 stations
 24 ELMBs total
Windows
PC
OPC server
OPC
client
PVSS II
Windows or
Linux PC
Ethernet
CAN-Bus
Interface
(Quasar XXXX)
4 stations
CAN-Bus
6 ELMBs per station,
24 ELMBs in total,
4 CAN-bus branches
Wiring is not clear,
8 ELMBs per station?
Any detector DCS has three trees
 Hardware tree in terms rack-crate-boardchannel. Used for geographical addressing of
infrastructure units
 Logical tree in terms detector-subdetectorstation-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
LV
Voltage
Tracker
Current
Station1
Temp.
View X
LV
HV1
HV4
Cover1
Cover28
Temp.
Voltage
HV
Voltage
Current
Temp.
Ramping
Trip TO
Proposed states of the Straw tracker

DOWN, color – BLACK. All power supplies are OFF
Available command – STANDBY

OFF, color – BLACK. Some power supplies are on.
Available commands – STANDBY, DOWN

STANDBY, color – BLUE. All LV power supplies are ON, all HV power
supplies are OFF
Available commands – ON, DOWN

NOT_READY, color BLUE. ALL LV power supplies are ON, some HV power
supplies are ON.
Available commands – ON, DOWN

ON, color GREEN. ALL power supplies are ON.
Available commands – STANDBY, DOWN

Error, color RED. Some power supplies are in TRIP state, overheating etc.
Available commands – ON, STANDBY, DOWN, RESET(?)




It seems reasonable at the beginning of the work to use
individual Windows PC for Tracker DCS running PVSS system
(UI manager, DB manager, Event manager, Distribution
manager) and all OPC servers. This PC should provide
access to all tracker GUIs.
After the development is finished it seems to be
reasonable to port Tracker DCS to common DCS PC (both
PVSS panels and servers. To be confirmed)
To avoid crowds at a single Central DCS PC screen we plan
to run tracker GUIs (PVSS UI manager) at the tracker PCs
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.