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: Init pv properly |
From: | "Arnold, Ned D." <[email protected]> |
To: | Miguel <[email protected]>, "[email protected]" <[email protected]> |
Date: | Fri, 14 Apr 2017 16:24:20 +0000 |
>The problem is that i would not like it to be instantiated as an >undefined pv. If I understand correctly, I think all you need is the PINI field set true ... record(stringin , "$(user):ExperienceString"){ info(autosaveFields, "VAL") #autosave field(VAL, "no experience") field(PINI,"YES") field(DESC, "anotar estados da experiencia") } Ned ________________________________________ From: [email protected] [[email protected]] on behalf of Miguel [[email protected]] Sent: Friday, April 14, 2017 11:18 AM To: [email protected] Subject: Init pv properly Hello, I would like to create a Pv that at the epics start up does not have any specific value or one forced by me. For example i would like to have a string that its initial state is not really important (no experience). Like: record(stringin , "$(user):ExperienceString"){ info(autosaveFields, "VAL") #autosave field(VAL, "no experience") field(DESC, "anotar estados da experiencia") } Where ill change this afterwrds manually when it will be important. The problem is that i would not like it to be instantiated as an undefined pv. Changing the VAL is the most appropriated method? I tought about changin UDF to 0 but did not work. The same for a integer pv. Wich kind of pv should i use and how should i instantiate it? Thanks a lot, MiguelB |