> if someone likes to change the ao record: What do you think about adding two
> new fields? These fields contain binary values which indicates that the high
> (low) limit is reached (limited or rejejected). This would be useful for
> other application parts like digital records or graphic displays.
I would strongly oppose against such kind of suggestions. For a record
that is used as widely and in high numbers as the ao, there must be more
than good reason to blow up its code and storage.
Also having multiple single bit fields for conditions that are exclusive
seems a bit inefficient.
In this case the intended functionality can be achieved in many ways
using the ao's alarm limits and/or a second (e.g. calcout) record that
might even write to another mbbi if translation into status strings is
needed. Such solutions using an additional calcout can also be used for
trend indication, rate-of-change calculation etc.
One of the main advantages of the EPICS database is the approach of
small atomic records that are connected by powerful links to build
complex applications. Introducing all possible features and complexity
into the atomic components breaks this concept.
Ralph
- References:
- Re: AO Record: New Drive Limit Mode? J. Frederick Bartlett ([email protected])
- Re: AO Record: New Drive Limit Mode? Bernd Schoeneburg
- Navigate by Date:
- Prev:
Re: AO Record: New Drive Limit Mode? Bernd Schoeneburg
- Next:
Re: tNetTask consumes all CPU time nda
- 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: AO Record: New Drive Limit Mode? Bernd Schoeneburg
- Next:
waveform record question Pedro Gigoux
- 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
|