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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: record with constant input link |
From: | Rolf Keitel via Tech-talk <tech-talk at aps.anl.gov> |
To: | tech-talk at aps.anl.gov |
Date: | Fri, 3 Nov 2023 08:50:33 -0700 |
Gerrit,
One should not initialize the VAL field of a stringin record by
setting the INP field to a string
(or the VAL field of a stringout record by setting DOL), as the
field value might be interpreted as
a record name and the link as a channel access link.
Keep in mind that on records where INP expects a number, a
constant value is used to initialize VAL, but
a constant INP link is only processed at record initialization.
Writing a new value to INP via channel access
or dbput will not update the VAL field.
Another issue I have been running into with this is the order of record initialisation. The string in this record is needed by other records and thus should be initialised first. But from what I have read on the web so far I understand there is no mechanism to guarantee that within one database. However, I probably could put records like this in a separate database and load that one in st.cmd first?
For this (within one IOC) you can use the PHAS field of a record. Records with smaller PHAS values are processed before records with higher values.