1 / 5

EPICS Record Naming Convention LCLS Collaboration, April 5, 2005

EPICS Record Naming Convention LCLS Collaboration, April 5, 2005. Proposal Examples Requirements Plans. Record Naming Proposal. PRIM:LOCA:UNIT:SECN PRIM: Device/System Type (max 4 char) XCOR, STEP, WIRE, KLYS, VACV, VACG, LCW, IOC, PNET, … LOCA: Location (4 char)

Download Presentation

EPICS Record Naming Convention LCLS Collaboration, April 5, 2005

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. EPICS Record Naming ConventionLCLS Collaboration, April 5, 2005 • Proposal • Examples • Requirements • Plans

  2. Record Naming Proposal PRIM:LOCA:UNIT:SECN • PRIM: Device/System Type (max 4 char) • XCOR, STEP, WIRE, KLYS, VACV, VACG, LCW, IOC, PNET, … • LOCA: Location (4 char) • LA21, LB21, XE00, XN02, XT49, … • UNIT: Device/System “serial” integer number unique for specific PRIM and LOCA (4 char max, 3 preferred) • 1, 203, … • SECN: Device/System Attribute (4 char max for SLC IOC, 12 char max for non-SLC IOC) • BDES, IACT, STAT, STATE, STATUS, V, VACM, X, XRMS, …

  3. Record Name Examples • XCOR:LA21:202:BACT • BPMS:LB21:201:Z • DT:XE00:1:V • VACV:XN01:99:STATE • MPS:LS00:1:RESET

  4. Record Naming Requirements • Usage by existing SLC 3.13 CA clients • Easier translation from SLC name to EPICS name by SLC-Aware IOC • Familiar to SLAC community • No collision with SLC CA server • Field naming requirements? Support 3.13 so must be <= 4 characters and all upper-case. • Other? RDB requirements?

  5. Record Naming Plans • Create Excel spreadsheet in shared area • Add new PRIMs, LOCAs, and SECNs to spreadsheet during development • List SECNs per PRIM • Probably affects RDB design • What else?

More Related