1. tdct – a Capfast replacement
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 CANADIEN POUR 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 2009 April 30th – May 2nd Vancouver
EPICS Collaboration Meeting, Padova, Oct. 15, 2008
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
EPICS Collaboration Meeting, Padova, Oct. 15, 2008
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
EPICS Collaboration Meeting, Padova, Oct. 15, 2008
R.Keitel – tdct

5. Capfast at TRIUMF History Wanted to use hierarchy
Devices are instantiated out of relational database but:
Want to see all levels in graphics
EPICS Collaboration Meeting, Padova, Oct. 15, 2008
R.Keitel – tdct

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

7. Capfast Hierarchy: Sub-system level
EPICS Collaboration Meeting, Padova, Oct. 15, 2008
R.Keitel – tdct

8. Capfast Hierarchy: Sub-system level
EPICS Collaboration Meeting, Padova, Oct. 15, 2008
R.Keitel – tdct

9. Capfast Hierarchy: Device Level
EPICS Collaboration Meeting, Padova, Oct. 15, 2008
R.Keitel – tdct

10. Why replace Capfast? --- TRIUMF specific Future 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 ???
EPICS Collaboration Meeting, Padova, Oct. 15, 2008
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
EPICS Collaboration Meeting, Padova, Oct. 15, 2008
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
EPICS Collaboration Meeting, Padova, Oct. 15, 2008
R.Keitel – tdct

13. tdct road map Ideas Problem: resources
Merge schematic and symbol files
Add channel access for “live” display
Look at supporting java IOC
Your ideas?
Do nothing
Problem: resources
EPICS Collaboration Meeting, Padova, Oct. 15, 2008
R.Keitel – tdct

14. Thank you EPICS Collaboration Meeting, Padova, Oct. 15, 2008
R.Keitel – tdct