1. Introduction to the CS framework Definition of the CS framework Requirements Example Idea Cooking recipe Some statements Dietrich Beck, d.beck@gsi.ded.beck@gsi.de http://www.gsi.de/controls http://www-w2k.gsi.de/controls/CS/cs.htm

2. 2 February 2006Dietrich Beck, d.beck@gsi.de Definition of the CS framework optional usage of sequencers (= sequences of commands) optional usage of state machines (= states and actions) optional GUIs on the device level optional interfaces to control systems of accelerator and DAQ standardization via a framework, here: CS framework  Main emphasis: device control, not process control Back-end (SCADA, GUI,...) Middleware: app. layer, comm... Front-end (devices, drivers,...) Ansatz: "Three-layer architecture"

3. 2 February 2006Dietrich Beck, d.beck@gsi.de 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

4. 2 February 2006Dietrich Beck, d.beck@gsi.de Requirements Developer Only one development tool, that is easy to learn Hard- and Software commercially available Maintainability Software is structured into small (independent) packages Applicability to many different projects Documentation User Flexibility!!! – Multiplicity and type of used components as well as operational states(!) configurable on the fly System is operational during 100% of the time Comfortable handling Performance! Fast reaction time (ms). Repeat sequences at a rate of  10Hz and a granularity of  1ns. Access to and from everywhere

5. 2 February 2006Dietrich Beck, d.beck@gsi.de Example 1: SHIPTRAP STOP- CELL EXTRACTION RFQ BUNCHER &COOLER TRANSFE R REGION PREPARATION TRAP cold ion bunches SHIP extraction to ext. experiments PRECISION TRAP mass measurements 100 * 50 * # of process variables

6. 2 February 2006Dietrich Beck, d.beck@gsi.de Complex timing scheme Cycle: stopping of ions ion the gas cell (static) extraction from the gas cell transfer capture and cool ions in the buncher ejection from the buncher (dynamic) transfer capture in the cooler trap mass selective buffer gas cooling ejection from the cooler trap transfer capture in the precision trap purification excitation of ion motion at  RF   c = (q/m) · B (  gain of energy) measurement of kinetic energy via a time-of-flight technique Scan: repeat cycle for different frequencies (minutes-days) 1s

7. 2 February 2006Dietrich Beck, d.beck@gsi.de Idea behind the CS framework Distributed, individual objects are responsible for subtasks, as: –User interface –Cycle control –Acquisition –Devices No intrinsic bottleneck: Everything can talk to everything Using ‘standard’ pieces: Flexible system, that can even during runtime be adapted to the experiment Cycle Control AFG Timing+DAQ HV GUI

8. 2 February 2006Dietrich Beck, d.beck@gsi.de Cooking recipe One development tool  LabVIEW –Fast learning curve –Multi-Threading –Event driven communication … Object oriented approach  CS framework –Create objects (processes) on the fly –Create high level classes by inheriting from base classes –Encapsulate data and their treatment “information hiding” … SCADA functionality (alarming, trending, …)  LabVIEW DSC module Distributed system on several nodes  TCP/IP –Scalability –Remote access –…

9. 2 February 2006Dietrich Beck, d.beck@gsi.de Statements Each object represents a hardware device, an application layer item or a GUI. "One object per device, one class per device type" Typically, objects are not static. They contain active code. Each Lego brick corresponds to an object. Lego tubes and studs are realized by an event mechanism: (Of course, an object can send an event to itself.*) (Of course, one can also use direct method calls.) Objects are created and destroyed on-the-fly*.  Different experiments may still use the same binary.exe. * much better than Lego wait for event send event

10. 2 February 2006Dietrich Beck, d.beck@gsi.de... more statements... Our OS is neither Windows, nor Linux, nor.... Our OS is LabVIEW! Active objects are no processes in the OS, but threads within the LabVIEW environment. Multi-threading/tasking is organized by the internal scheduler.  If LabVIEW crashes, everything crashes. Events/semaphores are only valid within one LabVIEW runtime/development system, but: Several runtime/development systems can be coupled together via a CS server and client. But: Only one CS system per node.

11. 2 February 2006Dietrich Beck, d.beck@gsi.de... even more statements... A LabVIEW "*.exe" file is not an executable. It requires a LabVIEW runtime system. Neither a LabVIEW ".exe" nor the LabVIEW runtime system contain drivers. They must be installed separately on the target system. If one uses the Datalogging and Supervisory Control (DSC) module, one must install the DSC runtime system seperately. If one uses OPC servers, one must install....

12. 2 February 2006Dietrich Beck, d.beck@gsi.de... statements continued... So far, CS is device oriented. – high performance, no intrinsic bottlenecks – no security or user management implemented (yet) CS... : – was: based on third-party toolkit ObjectVIEW – is: based on core developed at GSI – will be: what about LabVIEW 8?

13. 2 February 2006Dietrich Beck, d.beck@gsi.de... final statements LabVIEW is more expensive than emacs and gcc. PCs are cheap, but... control software is using more resources than office software –I/O –CPU –memory control software is a good test program for PC hardware PCI or cPCI/PXI? commodity hardware or industrial PCs?

14. 2 February 2006Dietrich Beck, d.beck@gsi.de 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 HV Instr. Driver IHQF015p HardwareSoftware (Proc)Software (Lib) Exp. SpecificGeneral PartBuy! EventOPC Front-end PC n DiscArchiver

15. 2 February 2006Dietrich Beck, d.beck@gsi.de Usage of the CS framework today experiments requiring high flexibility experiments with a large variety of hardware types experiments with up to 10,000 process variables PHELIX PHELIX Motion CaveA SHIPTRAP ISOLTRAP REXTRAP REXTRAP LEBIT LEBIT GSI, Germany CERN, Switzerland MSU, USA data taking development commissioning Motion CaveA FOPI RISING

16. 2 February 2006Dietrich Beck, d.beck@gsi.de What's next? summarize the status (this morning) identify good and bad properties (this morning) wish list for future developments (after lunch) present developments (today afternoon) existing tools and prototypes (tomorrow morning) application layer (tomorrow around lunch time) coordination of upcoming developments