** Changed in: epics-base/3.15
Status: In Progress => Fix Committed
--
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/1829770
Title:
event record device support broken with constant INP
Status in EPICS Base:
Invalid
Status in EPICS Base 3.15 series:
Fix Committed
Status in EPICS Base 7.0 series:
Invalid
Bug description:
Eric Norum reported:
------------------ 8< ---------------------
record(event, "$(P)$(R)reconn_") {
field(DTYP, "Soft Channel")
field(INP, "55")
field(TPRO, "1")
}
record(fanout, "$(P)$(R)reconnWFR_") {
field(SCAN, "Event")
field(EVNT, "55")
field(TPRO, "1")
}
When the “reconn_” record is processed, niether ”reconnWFR_” nor any
other record with that SCAN setup gets triggered. It’s not enough to
set INP=55 in the .db file, I must explicitly set VAL for it to work.
------------------ 8< ---------------------
The init_record() routine in devEventSoft.c (Base-3.15 branch) doesn't
look right, I think it's missing a call to eventNameToHandle().
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1829770/+subscriptions
- Navigate by Date:
- Prev:
[Bug 1842661] Re: seq record doesn't process LNK0 in "Specified" mode Gabriel Fedel via Core-talk
- Next:
Build failed: EPICS Base base-7.0-546 AppVeyor 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 1829770] Re: event record device support broken with constant INP Gabriel Fedel via Core-talk
- Next:
[Bug 1829770] Re: event record device support broken with constant INP Andrew Johnson 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
|