IIRC (I don't have the code in front of me at the moment) the way to override this asyn behavior is to set OMSL to Closed Loop and DOL to a constant value.
Cheers,
Nick Rees
Principal Software Engineer Phone: +44 (0)1235-778430
Diamond Light Source Fax: +44 (0)1235-446713
Mark Rivers <[email protected]> wrote:
Hi Zen,
Remember that standard asyn device support for output records does the following at iocInit:
1) Attempts to read the current value from the asyn port driver
2) If that read returns asynSuccess then the VAL field in the record is replaced by the one read from the driver
3) If that return does not return asynSuccess then the VAL field is not modified
This behavior is designed to support “bumpless reboots”.
I suspect your driver is returning asynSuccess on a call to asynInt32->read() at iocInit. If you want to preserve the value of the VAL field from the database file then your driver must not return asynSuccess.
Mark
From: [email protected] [mailto:[email protected]] On Behalf Of Szalata, Zenon M.
Sent: Friday, November 16, 2012 10:32 AM
To: [email protected]
Subject: DB Question
Hi,
I am a bit confused by the following behavior.
I am using EPICS R3.14.12.2 and asyn R4.20.
I have a simple longout record:
record( longout, "$(P):$(N):LO:BTOI:NCOEF"){
field( DESC, "N Coefs:")
field( DTYP, "asynInt32")
field( OUT, "@asyn($(PORT),$(N),1)LO_NCOEF")
field( VAL, "2")
field( PINI, "1")
}
After this record is done initializing, caget on it gives me 0.
I have introduced another record as follows:
record( longout, "$(P):$(N):LO:NCOEF"){
field( DESC, "N Coefs:")
field( VAL, "2")
field( OUT, "$(P):$(N):LO:BTOI:NCOEF PP")
field( PINI, "1")
}
record( longout, "$(P):$(N):LO:BTOI:NCOEF"){
field( DESC, "N Coefs:")
field( DTYP, "asynInt32")
field( OUT, "@asyn($(PORT),$(N),1)LO_NCOEF")
# field( VAL, "2")
# field( PINI, "1")
}
With these two records the second one now has the correct value.
Why does the single record solution lose its VAL value?
Thanks in advance,
Zen
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
- Replies:
- RE: DB Question Szalata, Zenon M.
- References:
- DB Question Szalata, Zenon M.
- RE: DB Question Mark Rivers
- Navigate by Date:
- Prev:
RE: DB Question Szalata, Zenon M.
- Next:
RE: DB Question 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:
RE: DB Question Szalata, Zenon M.
- Next:
RE: DB Question Szalata, Zenon M.
- 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
|