1. CS-Framework Overview
Ideas behind CS
Cooking recipe
Main Features
...
26 February 2009
Dietrich Beck

2. Definition of the CS framework
provides features that are commonly needed by many experiments
can be maintained be a dedicated and central group
allows for exchanging software and know-how
saves man power
should scale with future experiments
control system = framework + add-ons
add-ons may become part of framework
bug reports, new features requested
bug fixes, new features, maintenance
EE/KS
experiment
26 February 2009
Dietrich Beck

3. Definition of the CS framework
"Three-layer architecture"
Ansatz:
Back-end (SCADA, GUI, ...)
Cycle
Control
AFG
Timing+DAQ HV
GUI
Application layer (sequencer, ...)
Front-end (devices, drivers, ...)
Standardization of components
Flexibility: Plugging components together via events
Main emphasis: device control, not process control
 "It's a kind of toolbox plus some bricks..."
26 February 2009
Dietrich Beck

4. Cooking Recipe for the CS Framework
One development tool  LabVIEW
Standardization  object oriented approach
Distribution to many nodes  DIM (
Event driven communication for everything
Scaling to large systems by distribution
Remote access …
SCADA functionality (alarming, trending, …)  LabVIEW DSC module
26 February 2009
Dietrich Beck

5. Object Orientation (OO) with CS
"BaseClass" provides basic functionality (communication layer, active threads, ...)
"DeviceClass" adds functionality according to specs of device "DS345"
Instantiation: one object per device
"BaseClass"
inheritance
"Device Class"
AFG3
AFG1
AFG2
of course: classes for GUIs, Sequencer, State machines, ...
object are active
OO implemented by CS using pure LabVIEW (no LVOOP)
26 February 2009
Dietrich Beck

6. Event basics an entity waits for the next event, no polling!
timeout handling is an important issue
observer pattern: "one-to-many"
command pattern: "many-to-one"
publisher
client
client
client
data
command
subscriber
subscriber
subscriber
receiver
example: radio, television
added in CS 3.0
example: typical human communication
sole possibility for CS < 3.0
26 February 2009
Dietrich Beck

7. Example for a simple control system
User PC n
On-line Analysis GUI
Control GUI
Central PC
DataCollector
DSC Interface
DSC Engine
DiscArchiver
Sequencer
Data Acquisition
Timing
AFG
High Voltage
DataAcq. Instr. Driver
Timing Instr. Driver
AFG Instr. Driver
Front-end PC 1
Front-end PC n
SR430
PPG100
DS345
IHQF015p
Hardware
Software (Proc)
Software (Lib)
Exp. Specific
General Part
Buy!
Cmd
Service
OPC
(not shown)
26 February 2009
Dietrich Beck

8. Communication Layer: DIM
Distributed Information Management:
originally developed at around 1991
available for a multitude of platforms and languages
light-weight, aiming at high performance, based on TCP/IP
today: "backbone" of control systems for LHC experiments
concept: named services, peer-to-peer connections
DIM name server
(negotiates connections)
DIM client 1
DIM server A
command "iii"
service "i"
DIM server B
DIM client 2
service "ii"
26 February 2009
Dietrich Beck

9. DIM-LabVIEW Performance
26 February 2009
Dietrich Beck

10. Domain Management System: Process Management in a Distributed Environment
26 February 2009
Dietrich Beck

11. DMS Viewer
> 3 months
26 February 2009
Dietrich Beck

12. Other Tools and Features I
configuration data base
queries via SQL
MS-Access as ODBC data source
only read access via central server
operating system
core components run on MS-Windows and Linux (SuSE 10.3)
MS-Windows as typical platform
LabVIEW RT is deprecated, nobody is using CS on RT
26 February 2009
Dietrich Beck

13. Other Tools and Features II
Base Class Collection (base classes with GUIs for devices...)
Motion
Powersupply
Digital I/O
Arbitrary Function Generator
Muli-Channel-Scaler
next: pattern generator, cameras
...
CS Access System (CAS)
tree-like structure determined by CS Access Server
each node "inherits" lock status from its parent node
a feature many people asked for... Who is using it?
26 February 2009
Dietrich Beck

14. Usage of the CS framework today
experiments requiring high flexibility
experiments with a large variety of hardware types
experiments with up to 10,000 (1M possible) process variables
Motion CaveA
RISING
LEBIT
SHIPTRAP
ClusterTRAP
HITRAP
others ...
LPT
ISOLTRAP
PHELIX
GSI, Germany
Mainz, Germany
Greifswald, Germany
CERN, Switzerland
MSU, USA
Lanzhou, China
data taking
FOPI
REXTRAP
commissioning
Motion CaveA
TrigaTRAP
development
WITCH
26 February 2009
Dietrich Beck

15. Sources of Information, Code, ...
documentation
HOW-TOs
FAQs
...
downloads
bug reports
feature requests
mailing list
source code control system
based on Subversion
is now available world wide
26 February 2009
Dietrich Beck

16. Conclusion CS 3.10 released for LV8.2.1. What about LV8.6?  Holger
About active users
1,000,000 PVs demonstrated, an even larger number should be feasible
5,000 objects ( hardware devices) demonstrated, an even larger number should be feasible
test set-up: stability of a distributed CS system is better than a few hundred hours of continuous operation, requiring
binaries, dlls, etc. are NOT on a network drive (MS-Windows)
a node is rebooted and local processes are restarted after installation of software updates (MS-Windows)
no power cuts...
26 February 2009
Dietrich Beck