Introduction to the CS framework

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

2. 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 A framework... add-ons may become part of framework bug reports, new features requested experiment ECOS bug fixes, new features, maintenance Dietrich Beck, d.beck@gsi.de

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

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

5. 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 Dietrich Beck, d.beck@gsi.de

6. GUI Cycle Control HV Timing+DAQ AFG 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 Dietrich Beck, d.beck@gsi.de

7. One development tool  LabVIEW Fast learning curve Multi-Threading Event driven communication … Object oriented approach  ObjectVIEW 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 … Cooking recipe Dietrich Beck, d.beck@gsi.de

8. Statements • Each object represents a hardware device, an application layer item or a GUI. • 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  send event wait for event Dietrich Beck, d.beck@gsi.de

9. 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. ... more statements ... Dietrich Beck, d.beck@gsi.de

10. 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 ... . ... even more statements ... Dietrich Beck, d.beck@gsi.de

11. 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? ... statements continued  ... Dietrich Beck, d.beck@gsi.de

12. 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? ... final statements Dietrich Beck, d.beck@gsi.de

13. User PC n On-line Analysis GUI Control GUI Central PC DSC Interface DSC Engine DataCollector Sequencer DiscArchiver Data Acquisition Timing AFG High Voltage DataAcq. Instr. Driver Timing Instr. Driver AFG Instr. Driver HV Instr. Driver Front-end PC 1 Front-end PC n SR430 PPG100 DS345 IHQF015p Event Hardware Software (Proc) Software (Lib) Exp. Specific General Part Buy! OPC Example for a simple control system Dietrich Beck, d.beck@gsi.de

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