1 / 21

PCaPAC 3 rd International workshop on Personal Computer and Particle Accelerator Controls

THE OPERATOR INTERFACE OF THE LNS CONTROL SYSTEM Alberto Rovelli Istituto Nazionale di Fisica Nucleare Laboratori Nazionali del Sud Catania, Italy Guglielmo Bucchieri SeaSoft S.p.a. Catania, Italy. PCaPAC 3 rd International workshop on

ouida
Download Presentation

PCaPAC 3 rd International workshop on Personal Computer and Particle Accelerator Controls

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 OPERATOR INTERFACE OF THE LNS CONTROL SYSTEM Alberto Rovelli Istituto Nazionale di Fisica Nucleare Laboratori Nazionali del Sud Catania, Italy Guglielmo Bucchieri SeaSoft S.p.a. Catania, Italy PCaPAC 3rd International workshop on Personal Computer and Particle Accelerator Controls DESY, Hamburg, Germany October 9 - 12, 2000

  2. The LNS User Interface

  3. The programmer The operator • Suited language • Suited graphic interface • Object oriented technique • Operator profile oriented • Performance • Reliability and versatility • Easy maintenance • Friendly interaction • Fast response • Custom desktop • Automatic procedures • Efficient beam operation • Self-explaining information • Search and help tools Design Issues

  4. The basic choices • The hardware platform: • Intel Pentium III based Personal Computer • The operating system: • MS Windows NT 4.0 Workstation SP6b • The programming language: • MS C++ Visual Studio 6.0 SP3 • The communication protocol: • TCP/IP on Fast Ethernet • SeaNet Communication Agent • SeaNet Client/Server

  5. The architecture (the technology) • The application is written in Visual C++ with OOP technique • It was designed for a full integration into the Windows NT OS • Multi process • Multi thread • 32 bit native • The components are Active X objects • Methods • Properties • OLE communication between objects

  6. The architecture (the layers) Four layers characterize the user interface • The main COM objects container (UI) • The set of COM objects specific of the devices • The communication manager object • The communication client objects

  7. communication threads Client 3 Client 2 Client ... Communication Agent Client 1 Client n component threads out process UI Dev c Dev b Dev d Dev a Dev e main process WORKSTATION The architecture (the processes)

  8. Fast Ethernet LAN Client 1 Client 2 Client ... Client n TCP/IP Communication Agent OLE Dev b Dev c Dev d UI Dev a Dev e The architecture (the communications)

  9. The interface (the layout) The main window shows the whole accelerator facility layout. Scrolling the window it is possible to see all the components that are accessible to the operator. Screen-tips and highlights show the active components and, at the same time, facilitate their localization inside the facility itself.

  10. The first zoom level allows the representation of complex object (beam line, cyclotron, sources, etc.) The second zoom level allows the interaction with simple objects (faraday cup, power supply, pump, etc.) The interface (the zoom)

  11. The interface (the 1st zoom) Once selected, the complex object is visualized in the lower window and, in the upper window, a new color always allows its easy localization inside the facility. Moving the mouse over the object some screen-tips allow to individuate the internal components, reporting the related most significant informations: the name, the value and the status.

  12. The interface (the 2nd zoom) Once selected, the object is visualized in a new window. This is the deeper level of the representation, the instrument level. At this level we report all the informations, related to the selected device. Through this panel the operator gains the full access to the device: he may send commands, or read the representative value and the status. Furthermore, some resources allow the on-line (diagrams) and off-line (file) log and analysis of the informations.

  13. Beam Profile Monitor Beam Profile Monitor The instrument level (general) In the General tab are presented the informations related to the specific device. Several types of this window were implemented according to the device functionality. Each window has its own update rate that can be configured by the operator. This setting will affect only the update rate of the single operator workstation. Any change with respect the default setting will be stored in the operator profile and it will be applied at the next login session. A photo of the device is very useful for the operators training.

  14. The instrument level (graphics) The Graphics tab allows to configure a time diagram of the device value. The operator may start/stop and store the diagrams.

  15. The instrument level (alarms) The Alarms tab allows the setting of the lower and upper alarm thresholds. The operator may enable/disable the check and choice the notification action.

  16. The LogFile tab allows to set up the report generation on file. The operator may choice the recording media (file or printer), start/stop the report, set the recording time interval and select the informations to be reported. The operator, configuring the report generation on file, may choice two modes: table or graphics. Previously stored informations can be loaded and displayed again for off-line analysis. The instrument level (logfile)

  17. Advanced tools (tree view) The tree view is an explorer like representation of the accelerator facility components. Beam lines and specific devices can be explored just like directories and files. This representation allows to see all the simple objects inside complex objects. The main function of this view is the component search. A mouse click on the complex object (the directory) will expand its content showing the name of the simple objects (the files). The graphic representation of the object allows an easy understanding of its typology (the file extension). A double click on the selected object will display immediately on the right-lower window its position.

  18. Advanced tools (search view) The main function of this view is the component search. The typical search file options were implemented for the simple device search. • All the devices • All the devices of the same type • Search the device by: • name • beginning with • state (on/off, alarm, etc.) This search can be applied to one single complex object or to the whole facility. Also in this case the device is displayed on the right window.

  19. The personalized window (in progress) The operator may configure a special window for the parameters monitoring. From this box it will be possible to: • Create heterogeneous parameters reports • Build x/y graphs selecting any parameter • Create functional relationships between parameters • Look for parameters correlation • Interact with heterogeneous devices according to: • a beam optimization procedure • an operating mode • his personal feeling or attitude • whatever These custom views will be inserted in a list box and stored in the operator profile. During the session the operator can display or hide these representations and, in any case, they will be always available at the next login session.

  20. Other features • Operator password validation • Policy rights according to the security access level: • Administrator(grant the full control) • Operator (grant the full device interaction) • Guest (grant only to read the informations) • Operator profile management • Control system configuration

  21. Trends& Conclusions • The MMI is going to become a virtual facility • The request for instrumentation abstraction • Implementation of the beam optimization tools • Investigations on new and most useful components • The interface seems to be efficient and versatile • The custom view and log must be improved • The OOP is a mandatory technique developing the MMI • … but a lot of work has to be done to approach the end!

More Related