Experimental Physics and Industrial Control System
|
Hmm...
You're mixing granularity levels: Nowadays every PV name that doesn't
contain a dot is regarded as a record name.
EPICS V4
So, when you're aliasing [particular_device].Setpoint to [particular_record].VAL
any generic or display tool will soon start asking for things like [particular_device].Setpoint.EGU
.RTYP .DRVH .DRVL .STAT .SEVR
and
so on and so on.
Do you want to create explicit alias definitions for all (pseudo)
fields of that (pseudo) device record? You will end up with zillions of
alias definitions on a single IOC.
If you try to escape by aliasing only on the same (record) level, you
don't gain as much. Simply having other names for records just creates
ambiguity - which of the many names for the same record do you use for
archiving? For snapshots? For the alarms? How do you compare snapshots
that contain the same record under different names?
Guess this needs more thought - maybe too simple?!
Ralph
Marty Kraimer wrote:
If I
read this correctly it is just asking for the CA server to support
aliases.
Marty
[email protected] wrote:
Hmmm, a clever and simple idea.
� Ned
|
- Replies:
- Re: Control System Data Access API Claude Saunders
- References:
- Re: Fwd: Control System Data Access API Marty Kraimer
- Navigate by Date:
- Prev:
Re: V4 DB RecordCommon: Suggestion for alarmAckTransient (ACKT replacement) Marty Kraimer
- Next:
Re: Link arrays / syntax Ralph Lange
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Fwd: Control System Data Access API Marty Kraimer
- Next:
Re: Control System Data Access API Claude Saunders
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 02 Feb 2012 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|