1 / 24

IRMIS at CLS

IRMIS at CLS. Elder Matias, Diony Medrano, Dong Liu. Where is Saskatoon?. Saskatchewan Accelerator Laboratory . Originally established in 1964 as the Saskatchewan Accelerator Laboratory (SAL). Canadian Light Source. In 1999 the SAL accelerator was re-purposed as an injector for the CLS

sawyer
Télécharger la présentation

IRMIS at CLS

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. IRMIS at CLS Elder Matias, Diony Medrano, Dong Liu

  2. Where is Saskatoon?

  3. Saskatchewan Accelerator Laboratory • Originally established in 1964 as the Saskatchewan Accelerator Laboratory (SAL)

  4. Canadian Light Source • In 1999 the SAL accelerator was re-purposed as an injector for the CLS • Between 1999-2003 a new booster and storage ring was constructed.

  5. I CLS Uses IRMIS asa Control systemsearch tool

  6. IRMIS Search Tool(Current use at CLS) • IRMIS supports our ability to search for IOCs based on PV names • To accomplish this we use a modified pvCrawler from the original IRMIS release • A simple web-interface written in PHP

  7. PV search system architecture

  8. pvCrawler - Linux based IOC(Current use at CLS) • Moxa (used for serial or USB devices) • Intel (using optical Links to VME crates) • Applications located on a central file server, NFS mounted as /IOCApps • IRMIS crawls the NFS mount for db information

  9. pvCrawler RTEMS based IOC(Current use at CLS) • Primarily diskless machines • Programming comes off the central file servers using bootp • IRMIS crawls the bootp directory for db information

  10. pvCrawler(future enhancement) • Ability to identify source files that make use of a PV: • EDM Files • CSS Alarm Handler • EPICS State Notation Language • EPICS Gateways • EPICS Data Archiver • Matlab Code (accelerator toolbox) • Python Code (used on the beamlines) • AutoCAD Drawings

  11. Potential benefit • Motivation for additional crawlers: • Tool used to identify the impact of changes (critical for maintenance activities) • Database can then be scanned for consistently: • Identify dead-pv’s that are not used anymore • Use of incorrect data types/attributes • Other consistency/correctness checks?

  12. I Generating DB Files

  13. For Modicon PLCs(currently not part of IRMIS) • Modcion Momentum PLC variables follow a standard naming convention • An awk script parses the PLC variable list, and uses template substitution files to generate epics definitions • We currently don’t generate configuration files for the data archiver or EDM screens, however it is done by other labs, e.g., TRIUMF

  14. Current Process for Generating PV from PLCs PLC Project File Variable List • Process driven by Make files • Current limitations: • Alarm limits, variable descriptions are hardcoded into the tpl(templates) • Attributes of PV are hidden and notvisible to users • Could IRMIS do a better job? Modicon Concept CLS Awk Script Standard *.tpl files Generated *.sub files IOC build *.db files

  15. I Cables database

  16. Cables Database • History of Cables Database • Original implementation on PDP-11 • Converted to SunOS/PostgreSQL • 1999 Converted to MS-SQL Server • Now being converted to Java • Critical features is each cable being numbered

  17. Cable search system architecture

  18. Requirements Capture • We currently capture control systems requirements on PID drawings and word documents • Longer-term we want to move towards computerised requirements management that makes use of integrated change control and configuration management

  19. MKS • We use MKS as our configuration management tool and for change requests • We also group change requests into “work packages” (aka a project) with a project charter. • Our next step is to start to capture requirements and provide the traceability from requirements, down to the implementation

  20. Example of PID Drawings

  21. MKS Architecture(slide courtesy of MKS a PTC Company) Currently used by CLS Currently being evaluatedby CLS

  22. I Electronic Logbook

  23. Electronic Logbook • We use the TRIUMF electronic logbook system. • Simple web interface and fairly simple implementation • Mostly implemented in Perl running on top of PostgreSQL.

  24. Science Studio/ANISE

More Related