EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  <20002001  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  <20002001  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: support for output records
From: "Leo R. Dalesio" <[email protected]>
To: <[email protected]>
Date: Fri, 4 Feb 2000 11:32:05 -0800
So there are several inadequacies with output records that need to be
handled:
1) We need to be able to say - read value at initialization - but not
process
2) We need a general purpose way to reread the value fromt he hardware in
the case where there are multiple maters to the hardware. This opens up to
several questions -
do we always read before write? If we write and find that someone else wrote
over that value - do we overwrite it? Do we provide some general idea in the
IOC that the IOC is either
    A) MAster and whatever it says is enforced - finding a different value
in the PLC is an error
    B) Slave - we do not do any writing in this state
    C) Multi-master - we write and then read to determine the value in the
remote.
        - what about passive records? Does this add a scan on remote change
to value?
3) We need to fix passive BO's that say UDF when DOL is not defined. (Did I
get this one right?)

This affects bo, mbbo, mbbo-direct, longout, and ao.
Does it relate to steppermotors?
Does it relate to algorithmic records with OUT fields?

I think it only relates to output records with device support. I also think
that we could omit the case for steppermotors (even though I said it would
be nice to be consistent.....)

What else does this need to turn into an action item?

    Bob



Replies:
Re: support for output records Bernd Schoeneburg
References:
RE: VxWorks global variable device support Jeff Hill

Navigate by Date:
Prev: Re: VxWorks global variable device support (capfast can default DOL to not set) William Lupton
Next: Re: VxWorks global variable device support (boRecord.c) Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  <20002001  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: VxWorks global variable device support Jeff Hill
Next: Re: support for output records Bernd Schoeneburg
Index: 1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·