1 / 28

JCOP-UNICOS

JCOP-UNICOS. Purpose of this meeting. Requested by IT/CO To present you the UNICOS requirements on the hierarchy classifications Not to discuss the implementation or to impose an implementation UNICOS is one user of the JCOP framework UNICOS is using the JCOP hierarchy mechanism. Outline.

kyros
Download Presentation

JCOP-UNICOS

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. JCOP-UNICOS

  2. Purpose of this meeting • Requested by IT/CO • To present you the UNICOS requirements on the hierarchy classifications • Not to discuss the implementation or to impose an implementation • UNICOS is one user of the JCOP framework • UNICOS is using the JCOP hierarchy mechanism

  3. Outline • Applications using UNICOS • Requirements for the hierarchical classification • JCOP components used in UNICOS v1.0 • JCOP components to be used in UNICOS • Development procedure of UNICOS application • Demo

  4. JCOP-UNICOS • Close collaboration with JCOP-FW • Share PVSS expertise • Re-use of components • UNICOS follows the JCOP device model • For version 2.0 (planned for end of July 2003) • Easy to add new device into the UNICOS core

  5. Application using UNICOS • Accelerator sector: • LHC Cryogenics • Surface and tunnel • Discussion with the Vacuum system • Experimental sector: • GCS of the experiment: IT/CO • Magnet control of the experiment • ATLAS liquid Argon Calorimeter: LAL • Cryogenics for experiments: AT/ECR

  6. Application using UNICOS-PVSS • Version v1.0: • Fully compatible with the JCOP-framework v1.2.3 • Used in production • LHC cryogenics: QRL test, Nov 2003 • Gas control: GCS team (IT/CO), one application: ALICE TPC • Magnet control of the experiment • ATLAS vacuum: EP/TA3 • LN2 refrigerator: BNL to be test in Summer 2003. • Cryogenics for experiments: End 2003, AT/ECR • ATLAS main refrigerator • ATLAS shield refrigerator • ATLAS proximity solenoid • ALICE Solenoid control: EP-TA3, in preparation planned for Sept 2003.

  7. UNICOS hierarchy requirements – 1 • Hierarchy used for: • Devices (11 devices) classification • E.g.: AnalogInput, DigitalInput, etc. • 3 possible hierarchical classifications: • Hardware hierarchy used by the expert doing the cabling • In PVSS this is the dpName: prefix-PLCName-ApplicationName-DeviceType-number • Functional hierarchy used by the cryogenics expert, it corresponds to the cryogenic drawing • In PVSS the alias is used: system_location_deviceName • Software hierarchy used by the software expert implementing the control in the PLC • Into the PLC: link between device for the control • Not currently in PVSS but GCS team and cryogenics expert requested it. Planned for future release • Parent-child relationship • E.g.: in the PVSS layer, get the list of device link

  8. UNICOS hierarchy requirements – 2 • Hierarchy used for • Panel hierarchical classification • Like window explorer • The panels can be referenced in many places of one or many hierarchies • Equivalent to symbolic link in UNIX • Plot and page hierarchical classification • JCOP trending tool • Like window explorer • The plot and page can be referenced in many places of one or many hierarchies.

  9. UNICOS constraints • Avoid whenever possible create/delete of dps • UNICOS encountered problem with project having a lot of copy/delete • The system was slow • UNICOS always reserves spare elements • The functional name (PVSS alias) can be modified online • Insert nodes (folder) • Into the panel, plot, page hierarchies • Want to be compatible with JCOP: • Build on top of JCOP • Users from LHC experiments • Re-use of JCOP components • Provide useful components to JCOP: if interested

  10. JCOP components in UNICOS v1.0 • JCOP hierarchy to build: • Panel hierarchies • No use of the basic PVSS panel hierarchy because: • Reference to other panel from a hierarchy is a copy • No node • We also need a horizontal navigationDP type • Component installation tool: • To install the JCOP and UNICOS components • Trending tool: • To configure the plot and page • To define the hierarchies • To show the plot and page. • Not the same look and feel as JCOP • Access control: • One domain and four privileges used to act on the device • Per device type

  11. JCOP components for UNICOS • FSM toolkit: • For high level of processing • No need for partionning (not now but may be in the future) • Database interface: • PVSS & front-end Configuration • Recipes • Long term archiving • UNICOS has to be interfaced to the LHC Logging • Any other useful components

  12. Development of UNICOS application SCADA Databases Premium database Database Specification Template 3 Automated Generation Tool 2 2 1 Premium User program Quantum database Object Instantiation

  13. Development of UNICOS application • 4: set-up the communication with the front-end • 5: validate the devices • Generic panels based on the hardware hierarchy • Will be automated in future release • 6: develop synoptic (panel) • With PVSS00NG but not the PARA • 7: configure the hierarchical and horizontal navigation • 8: configure the plots and page • Hierarchical and horizontal navigation • Plot and page definition • 9: adjust the device configuration • Save back to the specification database • 10: configure the integrity of the PVSS application • Checks of PVSS drivers, archives error, front-end communication problem

  14. GraphicalFrame • UIM • PVSS modules • Closeclose all the modules • 1 per screen • Header • Alarm row • Logo, application name • Access to utilities • Horizontal, hierarchical navigation • Alarm list, etc. • Configuration, management menu • Synoptic area • One per module • One opened at a time • Footer • Contextual area • For devices • Panel, plot, page • Text message

  15. Devices in synoptics • Each device: • Contextual panel • Faceplate • Set of widgets • Libs. • Generation • Display

  16. Develop synoptic Double click or Ok button

  17. Demo: synoptic development

  18. Panel: hierarchy configuration – 2 • Creation panels, node & navigation • Reserved to expert user and users in expert group Not allowed for Views and node

  19. Horizontal navigation • For panel, plot, page device • Up to 10 panels, plots or pages • Shown in the context area

  20. Historical navigation • Panel, plot and page opened in the central area of the graphicalFrame • Like Internet Explorer • Back, forward, home, refresh, close • History

  21. Demo: panel, plot & page

  22. Adjust the device configuration Double click or Ok button

  23. Adjust the device configuration

  24. Demo: modify device configs

  25. UNICOS device: widget – 1 Device selected mouse over • Mouse over • Mouse click • Select if user authorized: operator minimum • Mouse double click • Select, open faceplate • Mouse right click • Menu • Device selected: • White box around • Contextual button opened in context area • Device name set in the footer of the graphicalFrame Mouse over Device selected By another UIM No action possible Device selected

  26. Data quality Alarm W A Body M Mode UNICOS device: widget – 2 • Color and letter convention • Dark pink: no data connected to the device, no access • Cyan: data invalid • aut_inv bit • The data was never updated into PVSS • Body to represent the type of widget • Pump, heater, etc. Selection

  27. Mode Mask Body Data quality Alarm Letter Letter Color Letter Color Letter Color Color Priority Color Priority Priority Priority Invalid Full Stop Interlock Alarm Blocked (in PLC) Cyan F B Red Highest Yellow Highest Highest Invalid Auto None N None Cyan Highest Alarm Unack. Alarm Masked (in PVSS) Red Blinking M High High Manual IO Error Stop Interlock M E S White Orange Highest High Alarm Red Normal Start Interlock IO Simulated Local L S I White High Normal Data quality Alarm Forced Mode Yellow Low W A Forced Forced <> Auto Position Alarm F W P Yellow Normal Body M Auto Mode Green Lowest Mode Regulation R White Manual <> Auto Tracking T White Position Warning … UNICOS device: widget – 3 Data invalid Data not connected

  28. UNICOS device: faceplate • Data area • Trend area • Info: HTML page • Diagnostic: PVSS panel • Contextual button • Per device type • Animation depend on the state of the device

More Related