| 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: | Andrew Johnson <[email protected]> |
| To: | "J. Lewis Muir" <[email protected]> |
| Cc: | [email protected] |
| Date: | Fri, 22 Nov 2013 11:16:01 -0600 |
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? 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.
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.
- Andrew -- Advertising may be described as the science of arresting the human intelligence long enough to get money from it. -- Stephen Leacock