Hi Angelic,
Do you write to one of those records that take a long time to complete a
ca_put_callback? Many SynApps records behave like that. For example the motor
record does not become "ready" until motion has finished.
Dirk
Angelic Ebbers wrote:
From studying the debugging logs, it looks like some channels
continuously report:
"write() pv not ready" when a client tries to write to them through the
gateway.
Then (usually triggered by a caget from a terminal) they become ready
"vcAdd() connecting -> ready"
After which a large backlog of writes are allowed through.
In some cases, I looks like a write to an input field is put on hold as
the channel isn't "ready" and then when a write to the Directive field
goes through, the input field becomes ready and the input is written
after the directive ... causing the "out of order", and thus failed,
commands.
What handshake between the ioc and the gateway is failing to set some
channels ready while others work properly?
Some help here would be greatly appreciated.
Angelic
--
Dr. Dirk Zimoch
Paul Scherrer Institut, WBGB/006
5232 Villigen PSI, Switzerland
Phone +41 56 310 5182
- References:
- Gateway problem .... more info Angelic Ebbers
- Navigate by Date:
- Prev:
Gateway problem .... more info Angelic Ebbers
- Next:
Re: sseq link problem on Linux Tim Mooney
- 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:
Gateway problem .... more info Angelic Ebbers
- Next:
RE: Gateway problem .... more info Angelic Ebbers
- 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
|