Those fields are definitely writeable from EPICS channel access. Have you tested that?
I can't say that I've ever tried linking to them with database links, but I can't see why it would not work.
Mark
________________________________
From: [email protected] on behalf of Eric Williams
Sent: Tue 1/22/2008 7:40 PM
To: [email protected]
Subject: asynRecord immutable fields
I'm trying to drive a GPIB device with a genSub record through an
asynRecord, but I've been unable to change some of the asynRecord fields
that I need to perform all the necessary control functions.
In particular, I've been unable to modify TMOD or NOWT, which I've
linked to output fields of the genSub record. (There are probably other
asynRecord fields that act similarly, but these are the ones I've run
into so far.) Writing to AOUT works OK.
If I link my genSub record output fields instead to "normal" records
(eg: longout), then the values go through just fine. But they never
show up when linked to the asynRecord fields. In contrast, I'm able to
modify these fields through dbpf on the console.
I've looked at the DBD file, and I'm not able to find any reason why one
field would be writable and another isn't. Anybody have a guess?
--
eric
Environment:
linux-x86
epics 3.14.9
asyn 4-8
genSub 4-6
- Replies:
- Re: asynRecord immutable fields Eric Williams
- References:
- asynRecord immutable fields Eric Williams
- Navigate by Date:
- Prev:
asynRecord immutable fields Eric Williams
- Next:
Re: CA connection management - vxWorks David Maden
- 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:
asynRecord immutable fields Eric Williams
- Next:
Re: asynRecord immutable fields Eric Williams
- 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
|