...
Here is the entry for our CHRG example:
##############################################################################
# Register path Asyn parameter name ##
##############################################################################
...
| Code Block | ||
|---|---|---|
| ||
############################################################################## # Register path Asyn parameter name ## ############################################################################## /mmio/DigFpga/ApplicationCore/SysGen[0]/DspCoreRes/Mult2 CHRG |
Note that the "parameter name" has to be unique, but it is not required to match the PV attribute name. The attribute name is used above for convenience.
The second requirement is to add one or two entries to a substitutions file that will be used to generate an EPICS database. Several templates exist to support various register types. The CHRG example uses RegisterDoubleIn.template:
| Code Block | ||
|---|---|---|
| ||
#====================================== |
...
# Register with DoubleVal_RO interfaces |
...
#====================================== |
...
file "db/RegisterDoubleIn.template" { pattern |
...
{ P, |
...
R, DESC, PINI, SCAN, PORT, EGU, PARAM } { BCM:B84:15, |
...
CHRG, |
...
"Charge", |
...
"YES", |
...
"1 second", |
...
S5, |
...
"pC", |
...
CHRG } } |
}
Note that the template specifies the DESC, PINI, SCAN, and EGU fields of the PV.
...