|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||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|
|<== Date ==>||<== Thread ==>|
|Subject:||RE: Another gateway question|
|From:||"Jeff Hill" <email@example.com>|
|To:||"'Kevin Tsubota'" <firstname.lastname@example.org>, <email@example.com>|
|Date:||Tue, 24 May 2011 17:16:22 -0600|
First I should mention that a number of issues were fixed in the portable server “cas” library for R3.14.11, and that the portable ca server library is an significant component of the gateway. Some improvements were also made to the gateway code itself at that time. In particular, the put callback implementation, for gateways that permit writes, was substantially improved.
I see that there are two “Network Connection Lost” messages in the write-access-granted output that you sent, and that dbcar also sees that all of the channels have disconnected twice. Two disconnects is maybe a strange result unless this number is reflecting the number of times that you restarted the gateway. If you leave this running for awhile do you see that the number of disconnects, as seen by dbcar is continuously increasing? Alternatively, does this number increase each time that the gateway is restarted? If this number of disconnects is always two soon after the IOC reboots, and isn’t increasing, then I fear something is amiss with the R3.13 db ca link code or the ca client library. It might help to type “i” in vxWorks, and then send the output from “tt <task id>” for the db ca link thread, and the ca client related threads that are running at close to the same priority.
Ø Is it a vxworks / r3.13.x issue?
Its probably more likely to be an R3.13 issue than a vxWorks issue although I wasn’t aware that there were any issues with R3.13 clients accessing the R3.14 portable CA server library.
Does your R3.13 camonitor/caget connect ok to the R3.14 excas (which uses the same ca server library as the ca gateway)? A recent R3.14 CA reference manual will identify what PVs are available in excas. You might also try placing a test record in your R3.13 IOC which db ca links to an R3.14 excas.
Message content: TSPA
With sufficient thrust, pigs fly just fine. However, this is
not necessarily a good idea. It is hard to be sure where they
are going to land, and it could be dangerous sitting under them
as they fly overhead. -- RFC 1925