Hi Mark,
I have a handful of bo records, which are intended to initiate some
action in a device driver sub-classed from asynPortDriver. I want these
records to have VAL 0 when the IOC starts. A typical record looks like
this:
record( bo,"$(P):BO:$(MOD):CH$(N):STOP"){
field( DESC, "Stop:")
field( DTYP, "asynInt32")
field( OUT, "@asyn($(PORT) $(ADDR) 1)BO_STOP")
field( HIGH, "0.1")
field( ZNAM, "Not")
field( ONAM, "Yes")
field( VAL, "0")
}
When the IOC starts, these records have VAL=1, which is undesirable.
For testing I have created a soft channel bo record and it comes up with
the state consistent with what is in the VAL field. I suspect the
observed behavior has something to do with the "bumpless reboot" that
you mentioned in your last email to me. I must confess that I don't
understand the concept and more importantly how to avoid it, assuming
that is what is getting me.
I tried a few things in the device driver. I have captured the call in
readInt32 routine and set the return status to either asynSuccess or
asynError, which did not change the behavior. I have also added in the
constructor setIntegerParam( xxxx,0) for these records. This also did
not help. Could you put me on the right track with this?
Thanks in advance,
Zen
- Replies:
- RE: Initial Value of a BO Record Mark Rivers
- Navigate by Date:
- Prev:
sequencer release 2.1.13 Benjamin Franksen
- Next:
RE: Initial Value of a BO Record Mark Rivers
- 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:
sequencer release 2.1.13 Benjamin Franksen
- Next:
RE: Initial Value of a BO Record Mark Rivers
- 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
|