** Changed in: epics-base
Assignee: Andrew Johnson (anj) => Joao Paulo Martins (joaopaulosm)
--
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1398215
Title:
Make output records only write on change
Status in EPICS Base:
Triaged
Bug description:
Add a field to the output record types to allow them to only write a
new value to the hardware when it differs from the previous value.
This saves adding another record to implement the only-on-change
behavior, and can reduce the data communication volume for slow I/O.
Can be made backwards-compatible if the default value of this field is
output always.
Gotcha's to think about: For extended device support, if a user
changes the hardware address of a record the newly addressed device
might need to reset the "previous value" somehow to ensure it gets
written to the next time the record processes, even though the value
hasn't changed. Could be tricky, discuss...
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1398215/+subscriptions
- Navigate by Date:
- Prev:
Re: [Merge] ~dirk.zimoch/epics-base:dbChannelForDBLinks into epics-base:7.0 mdavidsaver via Core-talk
- Next:
Re: [Merge] ~dirk.zimoch/epics-base:dbChannelForDBLinks into epics-base:7.0 Dirk Zimoch via Core-talk
- Index:
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:
[Bug 1398215] Re: Make output records only write on change Joao Paulo Martins via Core-talk
- Next:
[Merge] ~anj/epics-base/+git/base-7.0:typed-dsets into epics-base:7.0 mdavidsaver via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
|