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: | ASYN devEpics output record initialization |
From: | Eric Norum <[email protected]> |
To: | Mark Rivers <[email protected]> |
Cc: | "[email protected] Techtalk" <[email protected]> |
Date: | Mon, 18 Jun 2012 09:37:16 -0700 |
I'm working on a driver for a piece of equipment that has a bunch of password-protected settings. The settings can be read without providing a password. I've discovered that the asynFloat64 devEpics support doesn't appear to clear UDF on record startup. Here's an example record record(ao, "$(P)$(R)EEP_TmaxFET") { field(DESC, "Maximum FET temperature") field(DTYP, "asynFloat64") field(OUT, "@asyn($(PORT) 20 0)") field(PREC, "5") field(EGU, "degrees C") } When the IOC starts I can see the parameter readback command and reply on the communication link. The 'ao' record in question ends up with the correct value in its VAL field, but UDF is still set to 1. Is this the expected behaviour? The record has a correct value so it seems to me that UDF should be 0 after the initial readback succeeds. I can't set PINI=YES on the ao record since that ends up putting the record into error when the parameter update command is rejected because of the password protection. -- Eric Norum [email protected]