1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Epics 7 Alias options question |
From: | "Manoussakis, Adamandios via Tech-talk" <tech-talk at aps.anl.gov> |
To: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Thu, 3 Mar 2022 02:15:01 +0000 |
Hi All, I was reading through some old tech talk posts about how aliases work and had a few questions. The problem I am trying to solve is to add some level of flexibility to a piece of equipment’s PV names. I thought the alias might be a runtime
option where the operator could input to a CS Studio box a name such as “Water Level 1” which is saving to a PV “SCOPE1:DIG1:CH1.ALIAS” (after reading I don’t think this is possible though?). Currently I have each digitizer channel hardcoded with a signal
name “SCOPE1:DIG1:Water_Level_1”. The idea was to be able to rename the channels of a digitizer given what gets hooked up to each channel during runtime of the system.
From exploring tech talk posts are these the only ways to do the aliases
|