1 / 8

Control System Studio Training - “ Products ”

Control System Studio Training - “ Products ”. Kay Kasemir ORNL/SNS kasemirk@ornl.gov April 2013. Product: Composition of Plugins. Feature-Based Products. org.cstudio.basic.epics.product/CSS.product Based on “ Features ” org.csstudio.sns.feature.applications

yule
Download Presentation

Control System Studio Training - “ Products ”

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. Control System Studio Training-“Products” Kay Kasemir ORNL/SNS kasemirk@ornl.gov April 2013

  2. Product: Composition of Plugins

  3. Feature-Based Products • org.cstudio.basic.epics.product/CSS.product • Based on “Features” • org.csstudio.sns.feature.applications • org.csstudio.diag.pvmanager.probe • org.csstudio.diag.epics.pvtree • … • and features …opibuilder, …databrowser Features: • “Group” plugins to better organize them • Features can be installed & updated from update sites • Individual plugins can’t

  4. Smaller Products without Features • org.csstudio.archive.engine/ArchiveEngine.product • org.csstudio.archive.config.rdb/ArchiveConfigTool.product • org.csstudio.alarm.beast.server/AlarmServer.product • org.csstudio.alarm.beast.configtool/AlarmConfigTool.produc It’s OK to not use features Easier to start that way. But: Less organized, no install & update possible.

  5. Obvious Dependencies • org.csstudio.diag.pvmanager.probe • MANIFEST.MF, plugin.xml • Dependency on ..utility.pvmanager • org.csstudio.utility.pvmanager Products that include probe must also include utility.pvmanager.Otherwise obvious error about missing dependency at startup, or no product at all. Similar: Databrowser depends on org.csstudio.archive.reader,org.csstudio.logbook

  6. Less Obvious Dependencies org.csstudio.utility.pvmanager • Probe, Data Browser, … simply won’t load without. org.csstudio.utility.pvmanager.epics,org.csstudio.utility.pvmanager.sim,org.csstudio.utility.pvmanager.sys,org.csstudio.utility.pvmanager.pva • CSS integrator must decide which to use! Probe etc. will run with just “pvmanager”,but won’t get any datawithout *.epics, *.sim, ...

  7. Extension Points • org.csstudio.utility.pvmanager • Extension point datasource • “How to get live data” • org.csstudio.utility.pvmanager.sim • Implements that ext. point for “sim://” • org.csstudio.utility.pvmanager.epics • Implements that ext. point for “ca://” • Depends on ..libs.epics You may include pvmanager.epics, or *.sim, or both.Not enforced by Eclipse.No error message on startup.But probe may not display any data. Similar:org.csstudio.logbook.* - Need 0 or 1org.csstudio.archive.reader.* - Need 0 or more

  8. To build a custom product: • You pick what you want • Probe, Data Browser, BOY, … • Add dependencies, Eclipse helps • Logbook, pvmanager, archive, … • Determine what you may also need • pvmanager.epics, logbook.mysite, archive.reader.* • Test within Eclipse IDE (Run Configurations…) • Then update your *product, *feature Read http://cs-studio.sourceforge.net/docbook/

More Related