Presentation is loading. Please wait.

Presentation is loading. Please wait.

Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 MICE Control and Monitoring: General Architecture Subsystem Integration User Interface.

Similar presentations


Presentation on theme: "Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 MICE Control and Monitoring: General Architecture Subsystem Integration User Interface."— Presentation transcript:

1 Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 MICE Control and Monitoring: General Architecture Subsystem Integration User Interface Pete Owens

2 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 General Architecture Client-Server Model

3 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Channel Access GUI CA Clients CA Servers IOC Archiver… IOC process variables

4 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Channel Access Server Channel Access device/driver support IOC tradionally VME/VxWorks EPICS database EPICS core Hardware

5 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Channel Access Client Channel Access CA library Application (user interface / archive engine / etc…) Typically Unix/Linux

6 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Subsystem Integration * Naming convention * Simulation * File system * Standard hardware interfaces

7 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Naming Convention * Process Variables located by name - Names MUST be unique * Naming convention should apply to physical devices – not just control system. The same names should be used consistently in drawings, labels, documents and so on.

8 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Naming Convention * A-Z (upper case letters) * 0-9 (numerals) * : used to separate structural parts of name * - used to delimit distinct elements

9 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Naming Convention DDDD-TT-CCCCC-NN:SSS:RRRRRR device sub-system record (optional) domain (physical location) MICE technical area eg. HY, RF, VA … component eg. VALVE, identifier (01 -99)

10 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Example Record Names * MICE-RS-RDMON-01:RATE radiation monitor : dose rate * MICE-VA-VALVE-01:STA vacuum valve : status * MICE-VA-PIRG-03:CTL:SP pirani gauge : control relay : setpoint

11 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Simulation * EPICS database with ‘soft’ records ie no hardware * Allows you to build test and demonstrate client side applications * Should not be too realistic

12 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 File system EPICS release /home/epics/R3.13.7/base /extensions production modules module name / version /home/mice/R3.13.7/prod/support/a-module/1-0/ /ioc/an-ioc/3-4/ working directory for development modules /home/mice/R3.13.7/work/

13 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Standard Hardware Interfaces * EPICS supports many different hardware interfaces. To keep systems as compatible as possible the use of Hytec 9010 IOC and IP modules is recommended for most applications. * For more complex situations specialised systems such as VME crates may be necessary. This approach will require considerably more software expertise to develop and integrate.

14 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Standard Hardware Interfaces * The Hytec 9010 IOC supports upto 6 Industry pack (IP) interface modules. * Suggested IP modules are: * IP-ADC-84018 channel 16-bit ADC (+/- 10V) * IP-DAC-840216 channel 16-bit DAC (+/- 10V) * IP-SIO-850516 channel buffered digital I/O

15 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 User Interface * Standard EPICS Tools * ALH - Alarm Handler * Channel Archiver * BURT - Backup & Restore * Schematic Displays * EDM – Extensible Display Manager * Scripts/programs * Probe * Strip Tool * etc.

16 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 ALH – alarm handler Hierarchical monitoring and recording of alarm conditions

17 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Channel Archiver (3.13) Provides historical archive of configured process variables. Dead-band set in the database to prevent recording noise. Export data to different file formats Web-based user interface

18 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Channel Archiver (3.14) Improved storage and retrieval system BUT – fewer interface options to date

19 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 BURT – backup & restore tool Saves snapshots of sets of values that can be restored later

20 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Strip Tool Provides chart recorder style plotting Multi-channel Fully configurable scaling Can also plot historical data from the archiver

21 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 probe Monitors a single PV – useful for debugging

22 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Display Manager Used to generate graphical control and monitoring displays from pre-defined widgets. Several to choose from: EDD/DM, MEDM, EDM, DM2K EDM is currently the most actively developed display manager A limitation all of these display managers is that it is not possible to add intelligence or data processing to the application. This must be done either in the IOC or in a separate client application.

23 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 Colour Scheme * Grey - background * Blue - control * Green – monitor/on/open/OK * Yellow – warning * Red – alarm/off/closed * White - invalid

24 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 EDM – extensible display manager

25 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 EDM – extensible display manager

26 Presenter Name Facility Name Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 CA Programming Language Interfaces * Tcl/tk * Java * Python * Active X etc…


Download ppt "Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 MICE Control and Monitoring: General Architecture Subsystem Integration User Interface."

Similar presentations


Ads by Google