control system studio (css)css.desy.de/content/e198/e2712/e2727/am04-cssatiter.pdf · css at iter,...
TRANSCRIPT
CSS at ITER, 3-June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 1
Control System Studio (CSS)
At ITER…
CSS at ITER, 3-June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 2
CSS Features & Benefits
• CSS is an Eclipse-based Integrated Environment:
– Based on plugintechnology and therefore easily extensible
– Generic features like menus, preferences, help…
– Multi-platform support (portable JAVA code)
CSS provides a modern User Interface
CSS at ITER, 3-June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 3
CSS Integrated Platform
• CSS is a common platform for new control system applications
• Connection to external data sources like JDBC-databases, JMS and LDAP servers…
• Data accessible through all the applications
PV object contribution
2 sources: SNS and DESY
CSS at ITER, 3-June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 4
ICH SampleCore System V1
• Core System V1:– IOC Core – EDM screen– SNL Sequencer– Alarm Handler– EPICS Channel
Archiver tools– IOC Error
Logging tools– Autosave
CSS at ITER, 3-June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 5
BOY
• ICH EDM screen converted to BOY:
– Label, line, rectangle, text update
• Personalisation:Action button, menu, slider, chart…
• No script for now!
User friendly editor
CSS at ITER, 3-June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 6
BOY – many screens!
• Detailed views have been defined for the 5 x ICH main components
• The new display could replace the existing one, appear in a new Tab (press Ctrl) or in a new Window (press Shift)
Open a detailed display in a Tab
CSS at ITER, 3-June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 7
Data Browser
• Tool for displaying live as well as historic data in a Strip-Chart type plot
• Compatible with EPICS Channel Archiver (Abyss Standalone server)
• Plot toolbar: different zooms, annotation…
Strip chart live and archived data
CSS at ITER, 3-June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 8
BEAST - distributed alarm system
• Distributes system:– Alarm Server– User Interface– Configuration and
logging DB – <web report>
• User interface:Access guidance, invoke
links to related operator displays, acknowledge alarms and edit the configuration
• EPICS ALH configuration imported in BEAST but needs personalisation
Alarm tree, table and history
CSS at ITER, 3-June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 9
SNL Sequence Editor
• Syntax highlighted• Quick navigation
using the Outline view
• Compilation
• Diagram view
Programming editor
CSS at ITER, 3-June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 10
ITER Specific
• Self-Description interface– Access to PVs definition (name, alarm limits, states etc) shall be from
ITER configuration data management (“Self-Description Data”).• Data-base interface?• Plug-ins to interact with a SDD?• Impact on existing components (BOY, BEAST, SNL…)
It’s important to keep a unique interface for PV services (extensions).– A PostgreSQL back-end shall be added to the Oracle and MySQL
ones.
• Some ITER customization will be required (ex: standard symbols in synoptics)It’s important to maintain shared sources!
CSS at ITER, 3-June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 11
Conclusion
• Control System Studio is a very good platform to build an integrated development environment for the development, test and commissioning of the plant systems controls.
• There are arguments on RCP vs. web applications (light clients). We’ll certainly use both, depending on user and use cases (ex: data browsing, some edition, fixed screens).
• We are including CSS applications in CODAC Core System Vs 2 (2011/Q1) for HMI and alarm handling (archiving ?).
– We will maintain EDM, AHS and ChannelArchiver in this version.• It shall be integrated with EPICS application (IOC) development tools, using
“SDD”, SNL editor and DCT(?) • There will be additions from ITER. • It is important to have a well established process for sharing the sources
– A common repository (SourceForge)– A good structure of the components– Clear versions and tags– Regular & automated check/merge of between the shared repository and the lab’s
sources copies..