CS-Framework Overview for newcomers Ideas behind CS

CS-Framework Overview (for newcomers) • Ideas behind CS • Cooking recipe • Main Features • . . . February 18, 2010 Dietrich 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 add-ons may become part of framework bug reports, new features requested control system = framework + add-ons bug fixes, new features, maintenance February 18, 2010 EE/KS Dietrich Beck experiment

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

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

Object Orientation (OO) with CS • "Base. Class" provides basic functionality (communication layer, active threads, . . . ) "Base. Class" inheritance • "Device. Class" adds functionality according to specs of device "DS 345" • Instantiation: one object per device "Device Class" AFG 1 AFG 3 AFG 2 • of course: classes for GUIs, Sequencer, State machines, . . . • object are active • OO implemented by CS using pure Lab. VIEW (no LVOOP) February 18, 2010 Dietrich Beck

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" client publisher client data subscriber command subscriber example: radio, television added in CS 3. 0 February 18, 2010 client subscriber receiver example: typical human communication sole possibility for CS < 3. 0 Dietrich Beck

Example for a simple control system User PC n On-line Analysis GUI Control GUI DSC Interface Data. Collector Central PC DSC Engine Sequencer Disc. Archiver Data Acquisition Timing AFG Data. Acq. Instr. Driver Timing Instr. Driver AFG Instr. Driver Front-end PC 1 SR 430 Hardware PPG 100 High Voltage Front-end PC n DS 345 Software (Proc) Software (Lib) Exp. Specific General Part February 18, 2010 Dietrich Beck IHQF 015 p Buy! Cmd Service (not shown) OPC

Communication Layer: DIM • • • Distributed Information Management: www. cern. ch/dim originally developed at [email protected]/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 command "iii" DIM server A February 18, 2010 DIM client 1 service "i" DIM server B DIM name server (negotiates connections) DIM client 2 service "ii" Dietrich Beck

DIM-Lab. VIEW Performance February 18, 2010 Dietrich Beck

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

DMS Viewer > 3 months February 18, 2010 Dietrich 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 (Su. SE 10. 3) MS-Windows as typical platform Lab. VIEW RT is deprecated, nobody is using CS on RT (Lab. VIEW-DIM interface also working on Pharlap) February 18, 2010 Dietrich 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, 2010 Dietrich 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 (1 M possible) process variables RISING HITRAP ISOLTRAP LEBIT SHIPTRAP Cluster. TRAP others. . . LPT PHELIX Motion Cave. A GSI, Germany Mainz, Germany FOPI REXTRAP WITCH Triga. TRAP February 18, 2010 Greifswald, Germany CERN, Switzerland MSU, USA Lanzhou, China Dietrich Beck data taking commissioning development

Sources of Information, Code, . . . • http: //wiki. gsi. de/cgi-bin/view/CSframework/Web. Home – – documentation HOW-TOs FAQs. . . • https: //sourceforge. net/projects/cs-framework/ – – – downloads (if you know, what your are looking for) bug reports feature requests mailing list. . . • https: //subversion. gsi. de/labview/trunk/ – source code control system – based on Subversion – is now available world wide February 18, 2010 Dietrich Beck

Conclusion • CS 3. 13 released for LV 8. 2. 1. What about LV 8. 6, LV 2009? Holger • About 10 -15 active users • 1, 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. . . February 18, 2010 Dietrich Beck