On 2/21/13 09:06 , "Hu, Yong" <[email protected]> wrote:
>For the conversion of ao, the data flow (conversion direction) is VAL
>(double type) --> RVAL (integer); input is double, output is integer;
>
>For the conversion of ai, the data flow (conversion direction) is RVAL
>(integer) --> VAL (double); input is integer, output is double;
>-----Original Message-----
>From: [email protected]
>[mailto:[email protected]] On Behalf Of haquin
>There is a rounding operation (cast to (epicsInt32)) when using the
>conversion of the ao record, hence, with this conversion only integer is
>output, no float ...
>This is surprising and not equivalent to what is done for the ai record.
As Yong describes, it is consistent both ways: There is usually a
conversion from the double type to/from the integer, and device support
would then use the integer.
But that's up to the device support.
With EPICS base, you get the "Soft Channel" device support for example
that will transfer the double VAL field.
The "Raw Soft Channel" device support will transfer the integer RVAL field.
For the EtherIP device support, floating point typed PLC tags are
transferred in/out of the VAL fields, otherwise the RVAL fields are used.
So it depends on your device support.
Thanks,
-Kay
- Replies:
- Re: Rounding in conversion of ao record haquin
- References:
- RE: Rounding in conversion of ao record Hu, Yong
- Navigate by Date:
- Prev:
RE: Rounding in conversion of ao record Hu, Yong
- Next:
Re: Rounding in conversion of ao record haquin
- 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: Rounding in conversion of ao record Hu, Yong
- Next:
Re: Rounding in conversion of ao record haquin
- 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
|