Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020 
<== Date ==> <== Thread ==>

Subject: bo Record not forcing VAL to 0 or 1
From: Bruce Hill <bhill@slac.stanford.edu>
To: Techtalk <tech-talk@aps.anl.gov>
Date: Mon, 24 Jan 2011 21:14:02 -0800
In all the bo record documentation I can find, record processing specifies:
if DOL is DB_LINK and OMSL is CLOSED_LOOP
  • get value from DOL
  • check for link alarm
  • force VAL to be 0 or 1
However, the boRecord.c source code for 3.14.9 and 3.14.11 does not do this.
If you read a non-zero value from the DOL link, VAL and RVAL
retain that non-zero value, even if it isn't a 1.

Does anyone know if this is intentional, or a bug?

Thanks!
- Bruce
-- 
Bruce Hill
Member Technical Staff
SLAC National Accelerator Lab
2575 Sand Hill Road M/S 10
Menlo Park, CA  94025

Replies:
Re: bo Record not forcing VAL to 0 or 1 Andrew Johnson

Navigate by Date:
Prev: gensub/asub inputs not PP Till Straumann
Next: CSS BOY Meter widget limits Paweł Prędki
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020 
Navigate by Thread:
Prev: Re: gensub/asub inputs not PP Andy Foster
Next: Re: bo Record not forcing VAL to 0 or 1 Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·