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: Using CALC value to set NELM in subArray |
From: | "Wang, Andrew via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "Johnson, Andrew N." <anj at anl.gov> |
Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Wed, 21 Jul 2021 03:52:14 +0000 |
Hi Andrew,
Sorry for the delay. I'll send you an example of this issue sometime this week.
Thanks,
Andy
From: Johnson, Andrew N. <anj at anl.gov>
Sent: Thursday, July 1, 2021 8:31 AM To: Wang, Andrew <wang126 at llnl.gov> Cc: EPICS tech-talk <tech-talk at aps.anl.gov> Subject: Re: Using CALC value to set NELM in subArray Hi Andy,
On Jun 30, 2021, at 9:01 PM, Wang, Andrew via Tech-talk <tech-talk at aps.anl.gov> wrote:
The VAL field of a calc record holds a double, so even if you could cast the value in the _expression_ it would still be represented as a double result after the calculation was complete.
How are you copying your calc.VAL field value to the subArray.NELM field? I suspect that’s where your problem may be, are you trying to use NELM as a link? That would generate the “no digits to convert” error because NELM is a DBF_ULONG field so you can
only set it to an integer numeric value in your .db file. Only DBF_LINK fields can point to other PVs. To copy the calc result into it I would use a calcout record and point its OUT link (which is a DBF_OUTLINKfield ) to the NELM field so its value will be
copied.
If I’ve misunderstood what you’re doing, please post your .db file and the exact error message you’re getting; explicit examples are always much easier to debug than descriptions.
HTH,
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|