Transcript The Detector Control System of the Experiment CMS at CERN MENU:

The Detector Control System of
the Experiment CMS at CERN
MENU:
1. The Experiment CMS
2. Architecture, what is DCS in CMS?
3. Joint controls project
4. SCADA system (supervisory controls and data acquisition)
5. Framework
6. Partioning
7. Further tools to build a control system
8. Applications
9. Milestones and future
09/2001
Wolfgang Funk -CERN CMS
1
CMS detector
09/2001
Wolfgang Funk -CERN CMS
2
09/2001
Wolfgang Funk -CERN CMS
3
09/2001
Wolfgang Funk -CERN CMS
4
09/2001
Wolfgang Funk -CERN CMS
5
09/2001
Wolfgang Funk -CERN CMS
6
09/2001
Wolfgang Funk -CERN CMS
7
DCS environment:
Infrastructure:
cooling
ventilation
electricity
TCR,
pompiers
DCS
Level 3
safety CMS
CMS
Security
System
CMS
Magnet
sensors
LHC
CMS
09/2001
Wolfgang Funk -CERN CMS
8
Architecture of the CMS control system (functional block diagram):
Selection of runtype
resource manager (selection of
needed resources)
Run CTRL
ext.communication(LHC,infrastructure,magnet,
safety,…)
DAQ
SCADA System
Supervisory
System
Communi
cation with
Supervision
sub
of
detector
subdetector
controllers
DB
DB
controllers
Subdetector 2
controller
Subdetector 1
controller
Classsical
Standard
LAN (ethernet)
Device
Server
(OPC, others)
slow
slow
control
control
fieldbus (CAN, Profibus, ..)
fieldbus devices, PLCs, VME,
Devices
HV+LV power supplies
Calibration events
(T, rad. source, …)
Downloading and
reading of constants
and programs
Sensors,
Actuators
FE
electronics
09/2001
Wolfgang Funk -CERN CMS
9
JCOP (Joint Controls Project):
Some years ago the 4 LHC experiments decided to try to
do as much as possible in common for building their
respective DCS system
Basic ideas:
1.) Use commercial hard- and software
components where possible to economise
manpower for development and maintenance
as industry is doing it everywhere
09/2001
Wolfgang Funk -CERN CMS
10
Basic ideas (cont.):
2.) use one unique system for all controls within
each experiment, which implies that system is
• scalable
• hierachical
• partionable (easily integratable)
• modular
• open to outside (extensible)
09/2001
Wolfgang Funk -CERN CMS
11
Functions of a SCADA system:
(Supervisory controls and data acquisition)
•
•
•
•
•
•
•
•
•
HMI
Logging and archiving
Handles distribution and redundancy
Report generation
Automation (scripting, recipes, ..), FSM added
Access control
Alarms
Trending
…
After intensive evaluation, the four LHC experiments
selected PVSSII, market is rapidly evolving
09/2001
Wolfgang Funk -CERN CMS
12
PVSSII (1):
•
•
•
•
•
•
•
•
•
09/2001
Device oriented (structure of data, graphical representation)
All data + configuration is stored in “objects”, which are
accessible through scripts, template panels and API,
therefore complete control from outside possible
Mix and match of operation systems (NT, Linux, HPUX)
Complex devices built up out of several “objects”
Event driven
Network access (with special software installed)
Actions e.g. when value above threshold (call back feature)
We have connected a FSM to product
“C” is scripting language (next version VB, Java-scripting)
Wolfgang Funk -CERN CMS
13
PVSSII (2):
•
•
•
•
•
09/2001
System of systems (distributed, hierarchical, partitioned),
therefore no limits of number of procs to build up system
All panels are ASCII files (can generate them algorithmically)
Alarm grouping
Changes can be done online (scripting language is
interpreted)
Timestamps
Wolfgang Funk -CERN CMS
14
Basic architecture of PVSSII:
UIM
Scripts
Ctrl
DM
UIM
API
D
User Interface Layer
Processing Layer
Communication and
Memory Layer
EV
D
09/2001
UIM
D
Wolfgang Funk -CERN CMS
Driver Layer
15
What are the Benefits of SCADA?
• Standard framework « homogeneous system (with
engineering)
• Support for large distributed systems (networking +
redundancy)
• Follow evolution of market
• Buffering against technology changes, Operating
Systems, platforms, etc.
• Saving of Development Effort (50-100 man-years)
• Stability and maturity
• Experience of companies built into products
• Support and maintenance, including documentation and
training
• Reduction of work for the sub-detector teams
09/2001
Wolfgang Funk -CERN CMS
16
What are Engineering Tasks?
• Templates, symbols libraries, e.g. power supply,
rack, etc.
• Guidelines on use of colours, fonts, page layout,
naming, ...
• Guidelines on partitioning
• Guidelines for alarm priority levels, access
control levels, etc.
• Model standard device behaviour
• Definition of system architecture (distribution of
functionality)
• Development of configuration tools
09/2001
Wolfgang Funk -CERN CMS
17
Framework:
Finally:
1.Version:
9/2001
All templates, standard elements and functions
in order to build a homogeneous supervision
system.
• Finite state machine (SMI)
• DIM interface
• CAEN PS (127,527,1527) interface
• Generic analog and digital channels
• Hierarchy
• External alarm handling
• ELMB Interface to PVSSII
• Configuration utilities for all above
Wolfgang Funk -CERN CMS
18
Partioning
RootOperator
1
1.2
1.1
1.1.1
1.2.1
1.1.2
1.3
1.2.2
1.3.1
1.3.2
1
RootOperator
Operator A
1.2
1.1
1.1.1
1.1.2
1.2.1
1.3
1.2.2
1.3.1
1.3.2
Operator B
09/2001
Wolfgang Funk - CMS
19
Partioning with DAQ
Resource manager
Runctrl
DCS general
DAQ general
Rctrl ECAL
DCS HCAL
...
DCS ECAL
DAQ ECAL
...
DAQ HCAL
Resource manager distributes available resources and allows
possible partioning
Trigger as DAQ, DCS has to run 365 days/year (has to work as
well independently)
09/2001
Wolfgang Funk - CMS
20
OPC
OLE for Process Control
Set of DCOM interfaces to connect applications (EXEL, SCADA,.
with devices
Client/server:
client
client
server
server
From devices
Tag oriented
Well supported by industry Server (standalone, SCADA,…)
Client (office application, SCADA,
batch system,…)
Toolkit
09/2001
Wolfgang Funk - CMS
21
DIM-Distributed Information Management
system
Communication System - main features:
Services
Sets of data (any type or size), identified by a name
Publish/Subscribe Mechanism
Servers publish Services.
Clients subscribe to Services (and send Commands)
Services can be received at regular intervals or on change
Transparency
Name service
Client Server connections are automatically (re)established
Clients do not need to know where their servers are
Clients and Servers can move from one machine to another.
Available on multiple (mixed) environments:
Unix , Linux, Windows NT, VMS, some Real-time Oss
DIM client/server available in “C”, C++ and Delphi (Kylix)
09/2001
Wolfgang Funk - CMS
22
Interface between custom s/w
and PVSS
simulator
debugger
PVSSII
Custom s/w
H/W
DIM
DIM
PVSSII
API
-DIM is supported and will not change, when new PVSSII versions arrive,
customs s/w would not be affected (buffer!)
-work naturally separated, debugging of both sides independently
possible
09/2001
Wolfgang Funk - CMS
23
Fieldbuses
CERN recommends and supports 3 fieldbuses:
CAN-bus with the protocol CANOPEN
(simple, flexible)
Profibus with the protocol Profibus DP
(a lot of actuators available)
Worldfip
(deterministic, mostly for accelerators, big data rate)
09/2001
Wolfgang Funk - CMS
24
PLCs
• Front end computer
• Reliable, used in industry
• Specific standardised program languages
• Used in distributed control
• Communication PLC - device: fieldbus
PLC - PLC:
fieldbus, ethernet
PLC - SCADA: fieldbus, ethernet
CERN recommends to use PLCs from 2 companies
(Siemens, Schneider), CERN support
09/2001
Wolfgang Funk - CMS
25
Sensors and actuators
We try to standardize sensors and actuators in the field of:
• T-measurement
• Humidity sensors
• Valves, gas mixers etc.
• Radiation measurements
• Strain gauges
• ...
They have to work in difficult environment: radiation, magnet field
09/2001
Wolfgang Funk - CMS
26
OPC Server configuration and connection to HV P.S.
NT with A303
(High Speed
CAENET Controller)
RS232
CAENET
OPC Server
Cr#m
Cr#n
TCP/IP
IP#a
SY1527
System2
SY1527
System1
System0
System3
IP#b
SY1527
System4
09/2001
SY127
SY527
Wolfgang Funk - CMS
HV P.S.
Path
Param.
System0
CAENET
Crate #n
System1
System2
System3
System4
CAENET
Crate #m
RS232
TCP/IP
TCP/IP
COM1
IP #a
IP #b
27
HCAL HV system control
to HV crates
09/2001
Wolfgang Funk -CERN CMS
28
Gas-control
SCADA
with OPC client
OPC server
ethernet
PLC
PLC
PLC
PLC
Profibus
Valves, etc.
represents a system module
as mixer, distributor, purifier
Gas working group at CERN will do all including hardware and controls
09/2001
Wolfgang Funk - CMS
29
Cooling-control
SCADA
with OPC client
OPC server
ethernet
PLC
PLC
PLC
PLC
I/O
I/O
I/O
I/O
sensors, actuators.
Cooling and ventilation working group at CERN will do all regulation
and controls (hardware and software)
09/2001
Wolfgang Funk - CMS
30
Rack-control
PC
Fieldbus, ethernet
Control unit with power
distribution box, fieldbus
node, ADC, safety, local
control, relais, etc.
T
humidity
contact
09/2001
racks
Wolfgang Funk - CMS
31
Integration of Alignment in DCS
HTML server
Conditions database
of CMS
PVSSII
PC
Internal database
~10000 coordinates (datapoints)
Interface to PVSS (API manager)
DIM
PC (Linux, NT)
DAQ and analysis
to laser
from sensors
-API manager provides integration of alarming, trending, access control,
filtering of unchanged data, etc., connection to main system
-Master data set of alignment data inside PVSSII, PVSSII transfers regularly
all data needed for reconstruction into external conditions database
09/2001
Wolfgang Funk - CMS
32
TRACKER FE configuration
SCADA
controls/GUI
user/
process
Database
parameters
API FE
supervisor
read back values
09/2001
Wolfgang Funk -CERN CMS
33
FE electronics configuration (2)
2
User
ss
to
SCADA
(with a description for logbook)
1
4
Ac
ce
Register the new version
n
rit
ea
a
re
gi
re
d
ve
e
ok
v
e
R
it
r
w
m
v
e
h
rt
io
rs
3
Log
n
e
fo
DB
ve
rs
io
09/2001
ne
w
er
p
e
rs
io
n
ste
io
si s
W
n
Wolfgang Funk - CMS
34
HCAL source control system
09/2001
Wolfgang Funk -CERN CMS
35
Thermal Screen Control TRACKER:
9/2001
Wolfgang Funk -CERN CMS
36
Milestones and future for DCS
2006
2004
.
2001
}
integration, full system ready (3/06)
engineering, individual subdetectors build up their
subdetector DCS, GIF and later H2 should be used to
test DCS in real environment, ready to use in UXC (7/04)
and in USC (10/04)
• Most of the subdetector groups have started to use PVSSII for testing
the pieces of the detectors, where procedures will be reused in the
final experiment.
• Test beams are essential for development of DCS and provide rigorous
testing ground in order to demonstrate that the concept works.
• Almost everything has to be ready when detectors are put together on
surface
09/2001
Wolfgang Funk -CERN CMS
37
Milestones and future for DCS (2)
•
•
•
9/2001
All what is needed for DCS by more than 1 LHC experiment should
be developed and maintained in common within a CERN activity.
Architecture is fully modular, development of control of all devices
can be done individually and finally put together to a big system
(development of individual vertical slices).
Structure of DCS system will be completely scalable, therefore, if
control of 1 device of certain kind works, control of n devices
works.
Wolfgang Funk -CERN CMS
38