February 18, 2010Dietrich Beck CS-Framework Overview (for newcomers) Ideas behind CS Cooking recipe Main Features...

February 18, 2010Dietrich 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

February 18, 2010Dietrich Beck Definition of the CS framework 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..." Back-end (SCADA, GUI,...) Application layer (sequencer,...) Front-end (devices, drivers,...) Ansatz: "Three-layer architecture" Cycle Control AFG Timing+DAQ HV GUI

February 18, 2010Dietrich Beck 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

February 18, 2010Dietrich 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,... object are active OO implemented by CS using pure LabVIEW (no LVOOP)

February 18, 2010Dietrich 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

February 18, 2010Dietrich 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)

February 18, 2010Dietrich Beck 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 server A DIM server B DIM client 1 DIM client 2 service "i" service "ii" command "iii" DIM name server (negotiates connections)

February 18, 2010Dietrich Beck DIM-LabVIEW Performance

February 18, 2010Dietrich Beck Domain Management System: Process Management in a Distributed Environment

February 18, 2010Dietrich Beck DMS Viewer > 3 months

February 18, 2010Dietrich Beck Other Tools and Features I configuration data base –queries via SQL –MS-Access as ODBC data source –only read access via central server –clients connect to server via TCP/IP 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 –(LabVIEW-DIM interface also working on Pharlap)

February 18, 2010Dietrich Beck 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?

February 18, 2010Dietrich 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 ClusterTRAP WITCH TrigaTRAP

February 18, 2010Dietrich Beck Sources of Information, Code,... –documentation –HOW-TOs –FAQs –... –downloads (if you know, what your are looking for) –bug reports –feature requests –mailing list –... –source code control system –based on Subversion –is now available world wide

February 18, 2010Dietrich Beck Conclusion CS 3.13 released for LV What about LV8.6, LV2009?  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...