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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: CA_PROTO_READ_NOTIFY Response |
From: | <[email protected]> |
To: | <[email protected]> |
Date: | Thu, 3 May 2012 15:56:23 +0000 |
Mark, Jeff, Thanks for the clarification. The Rabbit CA server code and documentation, along with the Cosylab CA documentation gives a clear picture of what I need.
From: [email protected]
[mailto:[email protected]] On Behalf Of Mark Davis We are planning on changing from using ModBus to CA for the link between EPICS and our in-house low-powered embedded controllers (ones using Rabbit Core Modules from Digi), so
I have recently finished writing and debugging a CA server that could run on this low-end hardware. In the process I found several errors and a number of places with very confusing and/or contradictory wording that required examination of other working implementations
to sort out. "Return codes are communicated in the protocol by the
CA_PROTO_READ_NOTIFY, CA_PROTO_WRITE_NOTIFY, monitor subscription responses, and the CA_PROTO_ERROR responses." All, According to the Channel Access protocol specification from the Cosylab website, parameter 1 of the header of a CA_PROTO_READ_NOTIFY response contains the channel SID (the same as the request header received). Is this correct? Monitoring network traffic from a 3.14.12 win32-x86 soft IOC, this value always appears to a fixed value of 1, no matter what the serverID, or clientID of the channel. Returning anything other than 1 also appears to break
correct functioning of a caget. Thanks, Graham
Header
-- --
|