Introduction Current Status Outlook and Time Schedule CS Framework Overview Introduction Current Status Outlook and Time Schedule 01-Feb-2007 Dietrich Beck, GSI

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 01-Feb-2007 Dietrich Beck, GSI

Cooking recipe for CS framework One development tool  LabVIEW 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, …)  LabVIEW DSC module 01-Feb-2007 Dietrich Beck, GSI

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, ... OO implemented by CS using pure LabVIEW (no LVOOP) 01-Feb-2007 Dietrich Beck, GSI

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 01-Feb-2007 Dietrich Beck, GSI

Communication Layer: DIM Distributed Information Management: www.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 name server (negotiates connections) DIM client 1 DIM server A command "iii" service "i" DIM server B DIM client 2 service "ii" 01-Feb-2007 Dietrich Beck, GSI

CS (DIM Server/Client) SCADA Backend DSCIntProc class is reduced to a DIM-DSC Gateway DSCAlarm and DSCTrend class retrieve information from the DSC engine directly. Dedicated GUI class communicate via commands (events). CS (DIM Server/Client) service data commands DSCIntProc DSCAlarm DSCTrend LabVIEW DSC module (trending, alarming, ...) 01-Feb-2007 Dietrich Beck, GSI

CS (DIM Server/Client) OPC Connectivity DSCIntProc class is used as a DIM-OPC Gateway Remark: In principle, the same DSCIntProc object may serve as a DIM-OPC gateway and a DIM-DSC interface. CS (DIM Server/Client) service data DSCIntProc LabVIEW DSC module (OPC Server/Client) 01-Feb-2007 Dietrich Beck, GSI

Domain Management System: Process Management in a Distributed Environment 01-Feb-2007 Dietrich Beck, GSI

DMS Server 01-Feb-2007 Dietrich Beck, GSI

DMS Client 01-Feb-2007 Dietrich Beck, GSI

DMS Viewer 01-Feb-2007 Dietrich Beck, GSI

(New) Features for CS 3.00 Support for LabVIEW 7.1. DIM (www.cern.ch/dim) as communication layer real publisher-subscriber mechanism CSAccessSystem: reservation mechanism for (groups of) objects DomainManagementSystem: distributed process management (Windows, Linux) Source code control via SubVersion Packaging http://wiki.gsi.de/cgi-bin/view/CSframework/WebHome documentation HOW-TOs FAQs ... https://sourceforge.net/projects/cs-framework/ downloads bug reports feature requests 01-Feb-2007 Dietrich Beck, GSI

Schedule as of February 2006 1st step: Change event mechanism to DIM using LV 7.1 2nd step: Migrate to LV 8.XX: to be done Jan06 2-3 Feb Feb06 Mar06 Apr06 May06 Jun06 Jul06 Aug06 1st Sep Sep06 1st Oct Oct06 Nov06 15th Nov Dec06 15th Dec KS-Team workshop Test Dim-LV UserManger DSC/Tools Linux/RT Reserve Vacation Sync-Freeze Integration 3.0 alpha fix 3.0 beta CS 3.0 Users alpha test beta test Jan07 1-2 Feb Feb07 Mar07 1st April Apr07 1st May May07 Jun07 15th Jun Jul07 15th Jul stop LV7.1 port 2 LV8 3.1 alpha 3.1 beta CS 3.1 01-Feb-2007 Dietrich Beck, GSI

Future Releases Changes for CS 3.10 (until summer 2007) What next? Mainly formal changes Porting code to LabVIEW 8.20 CS as a LabVIEW project (.lvproj) classes as LabVIEW libraries (.lvlib) change directory structure of file system need to search/replace a few sub-VIs No (or very little) changes in functionality Internal changes of LV-DIM interface Take into account changes in LV scheduler: An object must not be able to "commit suicide". Performance Same, after the control system has been configured (Creating objects takes considerably longer in development system). What next? LVOOP, CS 4.00, CS++ (OOPCS) ... ??? (Discussion tomorrow) 01-Feb-2007 Dietrich Beck, GSI

Conclusion CS 3.00 released for LV7.1. Porting CS to LV8.20 is ongoing: CS 3.10. 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 Consistent set-values are straight forward 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) 01-Feb-2007 Dietrich Beck, GSI

Time for a Short Demo? DMS (Domain Management System) CS Inspector GOG CS 3.00 and CS 3.10 interoperability consistent set values CAS (CS Access System) CAS Server via GOG 01-Feb-2007 Dietrich Beck, GSI