Experimental Physics and Industrial Control System
Hi all,
I've written a very simple record interface and am having
a strange problem.
The record is very simple :
record(ai,"TEMP1") {
field(SCAN,"Passive")
field(DTYP,"TEMP")
field(INP,"@d=$(device) t=$(tty) b=$(baud) p=$(portconf) c=1 ")
field(PINI,"1")
field(LINR,"NO CONVERSION")
field(PREC,"14")
field(HOPR,"500")
field(LOPR,"0")
}
The driver simply reads a temperature from a device on
a serial port and writes it to the VAL field of this record.
The problem I'm having is that both the medm & probe programs
that came with the extensions package are displaying the
value from the RVAL field, rather than the VAL field.
Is there some other field I need to set to get these other
programs to retrieve the value from the VAL field? Is this
a bug? I've looked through the Record Reference Manual
several times, and haven't seen any mention of fields
that might affect this behavior.
Since this data doesn't need any conversions applied to it,
I tried to work around this problem by setting RVAL to the
temperature, only to find that the RVAL field is merely an int
field, while my temperature value is a double, and I lose the
precision of my data.
Why is RVAL only an int type if it is intended to hold the
raw data from hardware?
Thanks for any help or suggestions.
Amy
BTW: I'm using Redhat 7.3, vanilla 2.4.20 kernel, gcc 2.96
- Replies:
- Re: aiRecord, RVAL vs. VAL Amy Baum
- Navigate by Date:
- Prev:
RE: dynamical record loading/unloading and normal database Jeff Hill
- Next:
Re: aiRecord, RVAL vs. VAL Amy Baum
- 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
- Navigate by Thread:
- Prev:
RE: dynamical record loading/unloading and normal database Jeff Hill
- Next:
Re: aiRecord, RVAL vs. VAL Amy Baum
- 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