1 / 14

Canadian National Laboratory for Particle and Nuclear Physics

A joint venture owned and operated by Canadian universities, conducting research in particle and nuclear physics.

jorgei
Download Presentation

Canadian National Laboratory for Particle and Nuclear Physics

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. CANADA’S NATIONAL LABORATORY FOR PARTICLE AND NUCLEAR PHYSICS Owned and operated as a joint venture by a consortium of Canadian universities via a contribution through the National Research Council Canada LABORATOIRE NATIONAL CANADIENPOUR LA RECHERCHE EN PHYSIQUE NUCLÉAIRE ET EN PHYSIQUE DES PARTICULES Propriété d’un consortium d’universités canadiennes, géré en co-entreprise à partir d’une contribution administrée par le Conseil national de recherches Canada tdct – a Capfast replacement R.Keitel Epics Collaboration Meeting, Padova, Oct. 2008

  2. EPICS Meeting Spring 2009April 30th – May 2ndVancouver R.Keitel – tdct

  3. What is Capfast? Electronics Design Tool, adapted to configure EPICS databases (Phase3) • Electronics Schematics editor • Flexible • Customizable • Symbol editor • Epics Symbol Library • Translator: Schematics  EDIF • EDIF to DB converter e2db • Build IOC database: • .sch  .edif  .db R.Keitel – tdct

  4. What about Capfast? • +++ • Does Hierarchy really well • User-customizable symbols • Can use graphics to enhance understanding • ASCII data and configuration files • --- • Is not EPICS aware (i.e. enumerated menus) • Arcane user interface • Displays only one schematic • Was adapted for EPICS but not built for EPICS • Licence issues R.Keitel – tdct

  5. Capfast at TRIUMF • History • Wanted to use hierarchy • Devices are instantiated out of relational databasebut: • Want to see all levels in graphics R.Keitel – tdct

  6. Capfast at TRIUMF • Object-”like” device implementation • Schematics  object • Hierarchy: • Sub-system (collection of device objects)  EPICS .db • Device (components [ + EPICS records])-- Component (components [ + EPICS records]) …….-- primitive Component (EPICS records) R.Keitel – tdct

  7. Capfast Hierarchy: Sub-system level R.Keitel – tdct

  8. Capfast Hierarchy: Sub-system level R.Keitel – tdct

  9. Capfast Hierarchy: Device Level R.Keitel – tdct

  10. Why replace Capfast? • --- • Arcane user interface • Displays only one schematic • Was adapted for EPICS but not built for EPICS • Licence issues • TRIUMF specific • Mixed shop - Windows, Linux • Dongles don’t work any more • Needed a break from paper pushing • Future • Java IOC ??? R.Keitel – tdct

  11. tdct features • Java – cross platform • Capfast compatible (caution: reengineered TRIUMF use) • EPICS aware • One stop shopping • Schematics editor • Symbol editor • Data base generator (single and batch) • Error checking • Fix a few Capfast bugs R.Keitel – tdct

  12. tdct status • Release 0.99 • Testing and feature tweaks • >90% of TRIUMF data bases built identical • Started using for production • Will abandon Capfast soon R.Keitel – tdct

  13. tdct road map • Ideas • Merge schematic and symbol files • Add channel access for “live” display • Look at supporting java IOC • Your ideas? • Do nothing • Problem: resources R.Keitel – tdct

  14. Thank you R.Keitel – tdct

More Related