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: CSS BOY Meter widget limits |
From: | Paweł Prędki <[email protected]> |
To: | "Kasemir, Kay" <[email protected]> |
Cc: | TechTalk <[email protected]> |
Date: | Tue, 25 Jan 2011 16:44:09 +0100 |
W dniu 2011-01-25 16:24, Kasemir, Kay pisze:
Hello: On 1/25/11 10:17 , "Paweł Prędki"<[email protected]> wrote:The thing is the HIHI, HIGH, LOW and LOLO values are initialized in the record but BOY doesn't seem to be loading them. The record I'm referring to is as follows: record(ao,DISK:FORWARDING") { field(DESC,"Forwarding Throughput") field(DTYP,"Raw Soft Channel") field(EGU,"Gbps") field(OMSL,"supervisory") field(DRVL,0.0) field(DRVH,10.0) field(LOPR,0.0) field(HOPR,10.0) field(HIHI,8.0) field(HIGH,7.0); field(LOW, 1.0); field(LOLO,0.0) }Not sure about the quotes in this example. Does the IOC load the database without errors? Try caget to read the value as a DBR_CTRL_DOUBLE: caget -d 34 DISK:FORWARDING It should also show NaN (actually nan) for fields that the IOC reports as not initialized. -Kay
Hello,You are right - I get nan for the lo/hi warn/alarm fields using caget. It doesn't matter if I use the quotes or not. The IOC doesn't display any errors when loading this db.
Does the fact that the native data type is DBF_DOUBLE have anything to do with it? I wonder why only those four fields are invalid in this case.
Pawel