Kay is correct. I don't think the record you are looking at is a bo record. This is what cainfo says for a bo record:
corvette:~/devel/asyn/asyn>cainfo 13IDD:Unidig1Bo0
13IDD:Unidig1Bo0
State: connected
Host: ioc13idd.cars.aps.anl.gov:5064
Access: read, write
Native data type: DBF_ENUM
Request type: DBR_ENUM
Element count: 1
Note that it is DBF_ENUM, not DBF_LONG.
Mark
> -----Original Message-----
> From: Kasemir, Kay <[email protected]>
> Sent: Wednesday, March 28, 2018 2:15 PM
> To: Sobhani, Bayan <[email protected]>; Mark Rivers <[email protected]>; tech-
> [email protected]
> Cc: Mazzoli, Claudio <[email protected]>
> Subject: Re: camonitor not updating when PV changed
>
>
> > The PV in question is defined like this:
> > record (bo, "$(Sys)$(Dev)OLDMOV")
>
> In that case, wouldn't 'cainfo' report DBF_ENUM as the native type?
>
> > Here is the output of cainfo Sys{Dev}OLDMOV:
> > Sys{Dev}OLDMOV
> > Native data type: DBF_LONG
>
> Check the record's MDEL field.
>
> -Kay
- Replies:
- Re: camonitor not updating when PV changed Arnold, Ned D.
- References:
- camonitor not updating when PV changed Sobhani, Bayan
- RE: camonitor not updating when PV changed Mark Rivers
- RE: camonitor not updating when PV changed Sobhani, Bayan
- Re: camonitor not updating when PV changed Kasemir, Kay
- Navigate by Date:
- Prev:
Re: camonitor not updating when PV changed Kasemir, Kay
- Next:
Re: camonitor not updating when PV changed Arnold, Ned D.
- 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: camonitor not updating when PV changed Kasemir, Kay
- Next:
Re: camonitor not updating when PV changed Arnold, Ned D.
- 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
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·