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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | bo Record not forcing VAL to 0 or 1 |
From: | Bruce Hill <[email protected]> |
To: | Techtalk <[email protected]> |
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_LOOPHowever, 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 |