On 18.12.2017 19:34, Mooney, Tim M. wrote:
I don't understand what's happening, but I have a clue: If you write to "mode" directly from an aSub output link, the database behaves as it should.
Interesting.
Also if I scan the aSub directly rather than with a monitor it works as
expected.
BTW: Making the links from and to the mode record CA (and thus breaking
up the locksets) does not help.
On 19.12.2017 00:46, Michael Davidsaver wrote:
Needless to say, my first advice is to be careful about using seqRecord in a loop!
Or any records in a loop. :-)
Thanks for your replies.
I rather wrote the code to make the record asynchronous (when in
re-initialization mode). That works well and also does not illegally
delay record processing.
Dirk
- References:
- Puzzled with lockset(?) problem Dirk Zimoch
- Re: Puzzled with lockset(?) problem Michael Davidsaver
- Navigate by Date:
- Prev:
Re: Channel Archiver compilation error Heinz Junkes
- Next:
VisualDCT not starting on RHEL7 Ralph Lange
- 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: Puzzled with lockset(?) problem Michael Davidsaver
- Next:
EPICS Releases (two!) Andrew Johnson
- 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
|