1. 7 February 2008Dietrich Beck CS-Framework Overview Ideas behind CS Cooking recipe Main Features...

2. 7 February 2008Dietrich Beck 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 EE/KS experiment bug reports, new features requested add-ons may become part of framework bug fixes, new features, maintenance

3. 7 February 2008Dietrich Beck Definition of the CS framework Standardization of components Flexibility: Plugging components together via events Main emphasis: device control, not process control Back-end (SCADA, GUI,...) Application layer (sequencer,...) Front-end (devices, drivers,...) Ansatz: "Three-layer architecture" Cycle Control AFG Timing+DAQ HV GUI

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

5. 7 February 2008Dietrich Beck 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" "Device Class" inheritance AFG1 AFG2 AFG3 of course: classes for GUIs, Sequencer, State machines,... OO implemented by CS using pure LabVIEW (no LVOOP)

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

7. 7 February 2008Dietrich Beck Service Example for a simple control system User PC n Control GUIOn-line Analysis GUI Central PC Sequencer DataCollector DSC EngineDSC Interface SR430PPG100DS345 Front-end PC 1 Data Acquisition DataAcq. Instr. Driver Timing Timing Instr. Driver AFG AFG Instr. Driver High Voltage IHQF015p HardwareSoftware (Proc)Software (Lib) Exp. SpecificGeneral PartBuy! Cmd OPC Front-end PC n DiscArchiver (not shown)

8. 7 February 2008Dietrich Beck Communication Layer: DIM Distributed Information Management: www.cern.ch/dimwww.cern.ch/dim originally developed at DELPHI@LEP/CERN 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 server A DIM server B DIM client 1 DIM client 2 service "i" service "ii" command "iii" DIM name server (negotiates connections)

9. 7 February 2008Dietrich Beck DIM-LabVIEW Performance

10. 7 February 2008Dietrich Beck Domain Management System: Process Management in a Distributed Environment

11. 7 February 2008Dietrich Beck DMS Viewer

12. 7 February 2008Dietrich Beck CAS (CS Access System), I tree type structure "tree parent" of each object defined by CSAccessServer each object "inherits" the accessID from its parent each object accepts only commands with correct accessID

13. 7 February 2008Dietrich Beck CAS, II if "a" object acquires control of "another" object –object "a" becomes the parent of "another" object –changes the "tree parent" of one object, restructures whole trees –requires username and password –users have roles a supervisor can take control of a sub-tree locked by an operator another operator can't take control of a sub-tree locked by an operator

14. 7 February 2008Dietrich Beck "Demo CAS"

15. 7 February 2008Dietrich Beck "Demo CAS"

16. 7 February 2008Dietrich Beck 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 PHELIX PHELIX Motion CaveA SHIPTRAP ISOLTRAP REXTRAP REXTRAP LEBIT LEBIT GSI, Germany Mainz, Germany Greifswald, Germany CERN, Switzerland MSU, USA Lanzhou, China data taking development commissioning Motion CaveA FOPI RISING others... HITRAP LPT TrigaTRAP ClusterTRAP

17. 7 February 2008Dietrich Beck Sources of Information, Code,... http://wiki.gsi.de/cgi-bin/view/CSframework/WebHome –documentation –HOW-TOs –FAQs –... https://sourceforge.net/projects/cs-framework/ –downloads –bug reports –feature requests –mailing list –... https://subversion.gsi.de/labview/trunk/ –source code control system –based on Subversion –might be available world wide soon

18. 7 February 2008Dietrich Beck Conclusion CS 3.10 released for LV8.2.1. About 10-15 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 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...