EPICS Record Naming Convention LCLS Collaboration, April 5, 2005
-
Upload
mollie-sargent -
Category
Documents
-
view
23 -
download
1
description
Transcript of EPICS Record Naming Convention LCLS Collaboration, April 5, 2005
Stephanie Allison
SLC-Aware IOC [email protected]
April 5, 2005
Proposal
Examples
Requirements
Plans
EPICS Record Naming ConventionLCLS Collaboration, April 5, 2005
Stephanie Allison
SLC-Aware IOC [email protected]
April 5, 2005
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, …
Stephanie Allison
SLC-Aware IOC [email protected]
April 5, 2005
XCOR:LA21:202:BACT
BPMS:LB21:201:Z
DT:XE00:1:V
VACV:XN01:99:STATE
MPS:LS00:1:RESET
Record Name Examples
Stephanie Allison
SLC-Aware IOC [email protected]
April 5, 2005
Usage by existing SLC 3.13 CA clientsEasier translation from SLC name to EPICS name by SLC-Aware IOCFamiliar to SLAC communityNo collision with SLC CA serverField naming requirements? Support 3.13 so must be <= 4 characters and all upper-case.Other? RDB requirements?
Record Naming Requirements
Stephanie Allison
SLC-Aware IOC [email protected]
April 5, 2005
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?
Record Naming Plans