SNS Integrated Control System ORACLE –JERI DB Generation April 27, 2004 Coles Sibley Jeff Patton

SNS Integrated Control System Overview l MPS Configuration Control »Mode Mask Files »Mode Mask Defaults »Db Files.substitution files »Startup scripts l Power Supply Apps (design flow) »MS Excel (BNL,LANL,LBNL-> SNS) ->.substitutions -> RDB »EPICS ->txt (archiver) ->RDB »Csv ->Splinefilt->RDB »*.txt ->RDB l Plans

SNS Integrated Control System Oracle – IOC Application Setup (From MPS but could be any application) l Setup Utility adds or modifies applications to an IOC l (Data can be initially populated by crawling cdCommands) l Adds directory paths to required file(s) l Each IOC application (i.e. VxStats) has a similar setup window. 1. HW init calls 2. SW Init routines 3. Post IOC init

SNS Integrated Control System Oracle – Hardware setup l Application setup adds hardware, db applications, sequencers, etc. l For example VME board / PCI card info »Hardware address »Interrupt vector »Hardware version »Serial number »etc. l Custom setup for each type of hardware MPS – Hardware jumpers PMC cards Use Heartbeat?

SNS Integrated Control System Oracle – Channel Setup l Creates “.substitutions” file. Each channel gets instantiated with the template file(s) previously shown. l ADEL, MDEL, SMOO come from manufactures hardware specs and physics requirements l MPS shown below (Software mask jumpers, Mode Masks, etc.) »Configuration Control and reporting) Data comes from a number of Oracle Tables Need an easy way to get data from RDB table(s) to.substitutions file

SNS Integrated Control System MPS Summary Hardware by IOC MMP Chain Hardware Configuration Channel Configuration Device (From cabling database) File Export options: Chassis IOC MPS Chain Accelerator Readiness Committees accept configuration control procedures (very little paperwork)

SNS Integrated Control System MPS Configuration control reporting MPS configuration changes logged in elog

SNS Integrated Control System MPS Exported files Hardware configuration Substitutions file Expanded db files Startup script Archive config files (From RDB filters) Created by java script in JERI

SNS Integrated Control System Data Flow into EPICS RDB

SNS Integrated Control System Power Supply Application l Initial data came out of excel spreadsheets »Power Supply limits (V and I) »IOC assignments »Channel assignments l Archiver configuration files Initially many sets of files, outdated, wrong. Led to operational errors

SNS Integrated Control System PS / Magnet data from RDB l Power Supply Calibration (from EPICS) l PSC / PSI calibration history l Power supply limits from manufacturer (RDB) l Operational Limits (Ops, magnets, cables, heat waves, etc) l Magnet mapping files l Magnet cycling profiles l SCORE – PS save / restore l Magnetic field set points from accelerator physics model (or golden tune, or last weeks tune, etc) »Alarm limits »MPS trip levels Status Data is getting into Oracle (Bar code constraints).Substitution files are getting generated

SNS Integrated Control System Problems – Future Plans l Problems using an RDB »Controls Group Acceptance (We didn’t do it this way) »Need EPICS or Engineering user interface »ACCL-SRV1 needs to be mirrored for Oracle development »A lot of overhead to set up, lack of RDB experience »Too many constraints, held up because of missing bar codes l Status and Future Plans »Archiver Configuration, Report generation »~45 MPS IOC’s and 60 MPS chassis configured »Power Supply IOC Application (testing) »Argonne Collaboration (IRMIS) »PV application locator (IRMIS) »Oracle mirror on ics-accl-srvxx (In progress) »Use RDB for Global System configuration (100’s of IOC’s to manage, will not be able to upgrade all at once)

SNS Integrated Control System

Signal Management – Import.DB/Templates Startup.cmd imported (crawler App keeps Oracle up to date) Bad signals, duplicates signals, etc flagged. New verses Old comparison Files generated by Oracle go back into the RDB, verifies what is loaded by IOCS.