1 / 19

The Control System (not only) for SHIPTRAP Dietrich Beck, DVEE/GSI, 30.10.2001

The Control System (not only) for SHIPTRAP Dietrich Beck, DVEE/GSI, 30.10.2001. Motivation Requirements {The ISOLTRAP Control System SHIPTRAP and EU-Networks} Hardware Architectural Design Status Outlook. SHIPTRAP – an ISOL Facility for Transuranium Nuclides. SHIPTRAP – Set-up. 50.

eman
Download Presentation

The Control System (not only) for SHIPTRAP Dietrich Beck, DVEE/GSI, 30.10.2001

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Control System (not only) for SHIPTRAPDietrich Beck, DVEE/GSI, 30.10.2001 • Motivation • Requirements • {The ISOLTRAP Control System • SHIPTRAP and EU-Networks} • Hardware • Architectural Design • Status • Outlook

  2. SHIPTRAP – an ISOL Facility for Transuranium Nuclides

  3. SHIPTRAP – Set-up 50 100* 50 50 50 BUNCHING, COOLING SYSTEM STOPPING CHAMBER EXTRACTION SYSTEM TRANSFER REGION PURIFICATION TRAP PRECISIONTRAP Preliminary ion bunches Extraction to ext. experiments MassMeasurements SHIP * # of parameters

  4. Typical Scenario for a Mass Measurement 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

  5. Requirements to the control system • Active control in real-time with a precision of 100ns • 300 -1000 process variables (most of them are “static” ) • “ simple” data acquisition • High flexibility • SHIPTRAP has many different operational modes • new (not yet foreseeable) experimental techniques • Control System to be maintained by a PhD student • development environment must be easy to learn • creation and changing of GUIs should be simple • hardware and drivers have to be commercially available • Reusable for other (trap) experiments, if possible

  6. {

  7. PENNING TRAPS FOR MASS MEASUREMENTS, g-FACTOR DETERMINATIONS AND NUCLEAR PHYSICS SCIENCE Frans Michel Penning Wolfgang Paul EUROTRAPS EXOTRAPS Hans Dehmelt Gernot Graeff HITRAP Seattle Mainz NIPNET MIT Harvard ISOLTRAP ATRAP SMILETRAP CLUSTER TRAP Operational: ATHENA RETRAP g-factor trap CPT REXTRAP e+ TRAP In setup: LEBIT SHIPTRAP JYFL TRAP WITCH Future projects: MAFF TRAP TRIUMF TRAP HITRAP KVI TRAP

  8. Working Group for Control Systems

  9. Common Features LabVIEW: • Easy to learn, building of GUIs is easy • PC-Cards and Software from National Instruments • You know whom to blame • Low-level HW drivers commercially available and supported • drivers for third party HW are commercially available in many cases • Trending and alarming via Data logging and Supervisory Control module (former BridgeVIEW) Hardware • Multi channel scaler SR430 from Stanford Research • Arbitrary function generator DS345 from Stanford Research • High voltage modules from iseg • Pulse Pattern Generator PPG100 from Becker&Hickl • Gas inlet controller RVC200 from Pfeiffer • …

  10. The ISOLTRAP Control System A long time ago in Mainz: one control system for many experiments – general control system with experiment specific add-ons: ISOLTRAP, Cluster, RISIKO, 2 experiments in nuclear chemistry, … (SMILETRAP, REXTRAP) • Experiments grow: more flexibility • Less time required for development • Exchange of know-how

  11. Overview • “Separation of functions” • each function has its own process • event driven communication between processes • logical and real HW devices can be installed/removed “on the fly” and on request by the user during run-time • devices are not assigned to a specific task and can be replaced by another device • interfaces out of date and drivers not commercially available • OS/9, C, Assembler, WinNT, C++, … • No alarming, no trending

  12. }

  13. Cooking Recipe for the SHIPTRAP Control System • Take the concept and the (modified) design from the ISOLTRAP CS • Implement the control system with LabVIEW, • Add the DSC module (former BridgeVIEW) for trending and alarming, • Use a G++ toolkit to implement the CS in an object oriented way • Classes • Inheritance • G++  C++  limited number of levels of inheritance (VIs of the new class have links to VIs of the parent class )

  14. User PC On-line Analysis GUI Control GUI Frond-end PC Comm. Interface Data Acquisition Timing AFG High Voltage DataAcq. Instr. Driver Timing Instr. Driver AFG Instr. Driver HV Instr. Driver SR430 PPG100 DS345 IHQF015p Call Hardware Software (Proc) Software (Lib) Exp. Specific General Part Buy! OPC TCP/IP? LEGO-like Software Package Central PC Comm. Interface DSC Interface DSC Engine Data Server Super Central Process Super

  15. Functionality of the BaseProcess Class set watchdog alarm set tags SuperProc DSCIntProc DSC Engine inheritance install/remove watchdog set status and error Device Process BaseProcess • Individual event, periodic action and state machine loops (three threads) • Watchdog (event and periodic action loop) • Communication between processes via calls • Simple (one way) • Synchronous (wait for answer) • Asynchronous (answer will be sent later) • Trending and alarming via the DSC interface process • Parent class for ALL other processes • Daughter classes add new events, attributes and methods

  16. Hardware for SHIPTRAP

  17. Status SHIPTRAP specific part of the control system • Collection of Preliminary requirements for SHIPTRAP • Detailed user requirements specification for SHIPTRAP in progress • lots of hardware has already been bought and tested General part of the control system • (Prototypes for the) instrument drivers for the hardware modules are existing • Architectural Design “finished” • 80% of BaseProcess, SuperProc and DSCIntProc classes finished • Joint development with two other groups

  18. ISOLTRAP/GSI (F. Herfurth) LEBIT/MSU (S. Schwarz) SHIPTRAP/GSI (W. Quint) HITRAP/GSI (W. Quint) DVEE/GSI (D. Beck) WITCH/Leuven (M. Beck) TRIUMF-TRAP (J. Dilling) Joint Development of the General Part of the Control System Each circle contributes about one person full time!

  19. Outlook (near future) • Soon: give BaseProcess, SuperProc and DSCIntProc classes to LEBIT and WITCH • Implementation of the other general classes (DataServer, CommInterface, DeviceProcess, …) • Completion of the user requirements specification of the SHIPTRAP specific part • Summer 2002 first (alpha!) version of the SHIPTRAP control system

More Related