Subject: |
Re: menuFtype for 64 bit integers aka. long long and unsigned long long |
From: |
Andrew Johnson <[email protected]> |
To: |
[email protected] |
Date: |
Mon, 26 Mar 2012 09:06:02 -0600 |
Hi Hinko,
On 2012-03-26 Hinko Kocevar wrote:
> Our instrument natively uses 64-bit integers for some parameter, so I
> reckon that using casted epicsFloat64 back to integer 64 would not cut it.
>
> Right the only solution I see using two 32-bit integers in an array.
That is probably the best and safest solution, and I'd recommend making them
signed integers (DBF_LONG) not unsigned (DBF_ULONG) so you don't have any
problems with Channel Access which can pretend that DBF_ULONG values are
actually DBF_DOUBLE. You can use the aSub record to transport and process
those arrays within the IOC, and I think the sequencer will also be able to
handle them properly.
- Andrew
--
Never interrupt your enemy when he is making a mistake.
-- Napoleon Bonaparte
- References:
- menuFtype for 64 bit integers aka. long long and unsigned long long Hinko Kocevar
- RE: menuFtype for 64 bit integers aka. long long and unsigned long long Mark Rivers
- Re: menuFtype for 64 bit integers aka. long long and unsigned long long Hinko Kocevar
- Navigate by Date:
- Prev:
RE: Alarm annunciation via email in CSS BEAST Kasemir, Kay
- Next:
Google Groups subscription to tech-talk? Andrew Johnson
- 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: menuFtype for 64 bit integers aka. long long and unsigned long long Hinko Kocevar
- Next:
waveform ENUM FTVL or BOOL FTVL Hinko Kocevar
- 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
|