It does not make sense that it is writing 0.
Does your driver implement readInt32 and does it get called during iocInit for that record? If so what does it return as the status function return value?
Mark
________________________________________
From: Zenon Szalata [[email protected]]
Sent: Wednesday, June 26, 2013 12:01 AM
To: Mark Rivers; [email protected]
Subject: Record Processing
Hi Mark,
I have a simple longout record
record( longout, "$(P):LO:DEBUG-$(M):MFUNC"){
field( DESC, "Modbus Func:")
field( DTYP, "asynInt32")
field( OUT, "@asyn(DEBUG,0,1)LO_MFUNC")
field( VAL, "3")
field( PINI, "YES")
}
It is a part of an IOC which uses asynPortDriver class driver. I put a
print statement in writeInt32 function and at IOC initialization time it
prints that the value to write is 0.
Then at the end of st.cmd script I have put a
dbpf <record name>.PROC 1
for this record and this time the value to write is 3. Why is the
record writing 0 at IOC initialize time?
I am not sure if this is a basic EPICS or asyn issue, so I thought I ask
you.
Thanks,
Zen
- Replies:
- Re: Record Processing Zenon Szalata
- References:
- Record Processing Zenon Szalata
- Navigate by Date:
- Prev:
Re: caget can't connect to soft ioc on host with multiple NICs Hu, Yong
- Next:
RE: caget can't connect to soft ioc on host with multiple NICs 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:
Record Processing Zenon Szalata
- Next:
Re: Record Processing Zenon Szalata
- 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
|