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: Convertion for asynFloat64 |
From: | Benoit <[email protected]> |
To: | "J. Lewis Muir" <[email protected]> |
Cc: | [email protected] |
Date: | Mon, 25 Nov 2013 11:30:38 +0100 |
On 11/22/13 11:16 AM, Andrew Johnson wrote:Hi, Andrew.
> Hi Lewis,
>
> On 11/22/2013 10:53 AM, J. Lewis Muir wrote:
>> EPICS Base developers, it would be great if a write to the calcout
>> VAL field did trigger record processing. But maybe there's a reason
>> why it doesn't?
>
> I didn't design that record type, but why would you want to be able
> to write a value to a field when that value is normally going to be
> immediately overwritten when the record processes?
My only reason is just from a PV "API" standpoint. Lots of people leave
off the ".VAL" suffix from the PV name, so in this case, they wouldn't
be able to do that unless the VAL field was pp(TRUE).
Interesting. Thanks for pointing that out; I didn't know that.
> Note that the pp(TRUE) setting only applies when doing a put through
> CA, a database link can directly control whether processing happens or
> not.
Right, that's what I said when I wrote, "So maybe you could write to
> In this particular case you're getting clever with the record so I do
> understand the request, but the ability to access the VAL field from a
> Calc _expression_ is a lot newer than the calcout record. Note also that
> in an OCAL _expression_, VAL actually returns the last value from the
> OVAL field, not the VAL field, so setting OCAL to "1000 * VAL" would
> not do the scaling of the VAL field that Benoit wants it to do.
that [the OVAL field], and use the OCAL _expression_ and set DOPT to 'Use
OCAL' and get the behavior you want by writing to OVAL instead of VALThanks,
(albeit confusing)?"
Lewis