Experimental Physics and Industrial Control System
I agree with your conclusion. I will make your suggested change so that it will
be in the next 3.13 and 3.14 releases.
Marty Kraimer
Bernd Schoeneburg wrote:
>
> Hi all,
> I have just discovered something that seems to me to be a bug in the
> mbbi record support routines. When status-values are defined but the
> current raw value doesn't fit any of them, the value will become 65535
> and the UDF bit will be set. In the alarm routine UDF causes an invalid
> severity error which can not be overwritten by something else. This
> leads to the situation that the setting of the UNSV field is without any
> effect.
> I propose to delete all existing manipulations of UDF in process() and
> insert only one "..->udf = FALSE" when the raw value is successfully
> read. This is the place after "if (status == 0)". This works fine for
> me. Any comments?
>
> Bernd
>
> Bernd Schoeneburg
> Group MKS-2
> DESY, Germany
- References:
- mbbiRecord undefined state Bernd Schoeneburg
- Navigate by Date:
- Prev:
Re: mbbiRecord undefined state Marty Kraimer
- Next:
VXI driver support John Faucett
- 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: mbbiRecord undefined state Marty Kraimer
- Next:
iocsh for Epics314b1 on win32 Marcel Grunder
- 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