SNS EPICS Config Database May 2001 KayUwe Kasemir

SNS EPICS Config. Database May 2001 Kay-Uwe Kasemir, LANL

Approaches to EPICS DB Generation n n Text Editor, Capfast, xdct *. DB Device Info + Script *. DB Template + Substitution Table from RDB *. DB Template + Device Info from RDB + Script *. DB Common: Results in DB file

Put EPICS *. DB in RDB n Experience: Quickly import “signal lists” for e. g. PLCs n Tabular view allows rapid data entry n RDB helpful for setting e. g. limits of related records at once n Debugging: “Where is PV XYZ supposed to be? ” n RDB provides reports: signal lists, used/unused HW Problem: How to include external sources, e. g. Capfast schematics, and keep track of changes to both external source and RDB? n n

‘IOC’ Table n Perl: n Java:

‘Logic’ Table n Logic = collection of records, could be n n Device Algorithm Subsystem IOC Possible: Logic Id=IOC Id

Implementation Details n Helper Tables n n (SCAN, PINI, alarm severities, …) Each record has “External Source” n n Record Types Allowed Fields Menus for fields Original DB file, Capfast schematic Each field has External + Internal Value n From external source + (maybe) modification

Rec. Browser for Single Record n n Edit single record All fields with description, maybe menus Shows external source & value Edit internal value

Table. Browser for ‘Logic’ n n Add, remove, sort, filter, fill columns Color-coded values: external/internal/conflicting

Basic Spreadsheet Support n Perl tools for Import/Export n ASCII, Columns have to match EPICS fields

Scenario: Have (Capfast)-DB n n Check/Define IOC and Logic for that DB Create DB from Capfast Import DB, specify the Capfast drawing as the “external source” Create *. DB for IOC n n could use the original DB, but this assures that the import worked For changes: n RDB indicates Capfast drawing, so that source can be changed and re-imported

Scenario: Signal List Spreadsheet n Setup: n n n Define IOC and logic Import spreadsheet into that logic Use Table. Browser to “fill blanks”, add records, modify errors Generate DB file from RDB Changes: n Might change spreadsheet and re-import, though in many cases the spreadsheet contained only rudimentary information (NAME, INP/OUT) and is rarely used again.

Scenario: Template & Substitution Info n Setup: n n IOC, Logic On Host, create DB from Template plus Device Information from RDB, script, substitution file, … Import DB, specify the script as the “external source” When modifying, RDB indicates original source, so that template/device information can be changed and re-imported

EPICS RDB Idea emacs, vi, . . . Capfast template Device RDB <? > script *. DB SQL, perl-DBI JDBC EPICS RDB: reports, define missing fields, . . . *. DB, maybe startup, dbd IOC IOC