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: | RE: PV alias with logical names |
From: | Freddie Akeroyd - UKRI STFC <[email protected]> |
To: | Bo Jakobsen <[email protected]>, EPICS Tech Talk <[email protected]> |
Date: | Fri, 5 Oct 2018 10:05:29 +0000 |
Hi Bo, If you just need a pure name alias, then there are two options: ·
You could use the “alias” db command and create a file of aliases that you load into the IOC. The alias command only works for PVs in the same IOC,
so you would need to load these into the temperature monitoring IOC and then restart this IOC on any name changes. ·
You can use an EPICS gateway running locally to alias PVs, which is what we do. There are notes in the EPICS gateway manual about how to run an “Alias
Gateway” Regards, Freddie From: [email protected]
[mailto:[email protected]] On Behalf Of Bo Jakobsen Hi, I am setting up a new EPICS system for monitoring process values in our labs. I will for now be using a temperature monitoring box which has a number of channels, so PV will be e.g. lab1:Tbox1:T1 ... However, I would like to have PV names for the users of the system which directly reflects what is measured, e.g. lab1:T:CoolWater I was considering to set up an extra soft IOC with records like: record(ai, "lab1:T:CoolWater") { and then define alarm limits and PV archiving based on this. Is this the right way to obtain logical names, and is there any downsides of having monitor PV's. Best Bo |