Hi all,
since upgrading from 3.14 to 3.16.1, I see the following messages on the console of an IOC:
DB CA Link Exception: channel "dest1"
DB CA Link Exception: native T=DBR_DOUBLE, request T=DBR_DOUBLE, native N=1, request N=1, access rights {RW}
DB CA Link Exception: "Channel write request failed", context "dest1"
This is from a dfanout record that simply pushes a value to another IOC.
However, the write succeeds.
It's totally reproducible with these two DBs run in softIOCs:
sender.db:
record(calc, "count") {
field(SCAN, "1 second")
field(VAL, "0")
field(PINI, "YES")
field(INPA, "count")
field(CALC, "A+1")
}
record(dfanout, "send1") {
field(DOL, "count CPP")
field(OMSL, "closed_loop")
field(OUTA, "dest1")
}
record(dfanout, "send2") {
field(OMSL, "supervisory")
field(OUTA, "dest2")
}
receiver.db:
record(ao, "dest1") {
}
record(ao, "dest2") {
}
There's one messages every second about dest1, and one on every write to send2.
Cheers,
Michael
--
Dr. Michael Ritzert Tel: +49 621 181 2883
Schaltungstechnik und Simulation Fax: +49 621 181 2734
Technische Informatik, Uni Heidelberg [email protected]
68131 Mannheim, Germany http://sus.ziti.uni-heidelberg.de
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
- Replies:
- Re: Spurious "Channel write request failed" messages Ralph Lange
- Navigate by Date:
- Prev:
Control System Engineer Opening at Lawrence Berkeley Laboratory Robert Gunion
- Next:
Re: Spurious "Channel write request failed" messages 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:
Control System Engineer Opening at Lawrence Berkeley Laboratory Robert Gunion
- Next:
Re: Spurious "Channel write request failed" messages 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
|