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: | "Hill, Jeffrey O" <[email protected]> |
To: | "[email protected]" <[email protected]>, "[email protected]" <[email protected]> |
Date: | Wed, 2 May 2012 15:04:46 +0000 |
Ø
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). typedef
struct ca_hdr {
ca_uint16_t m_cmmd;
/* operation to be performed */
ca_uint16_t m_postsize;
/* size of payload */
ca_uint16_t m_dataType;
/* operation data type */
ca_uint16_t m_count;
/* operation data count */
ca_uint32_t m_cid;
/* channel identifier */
ca_uint32_t m_available;
/* protocol stub dependent */ }
caHdr; The
m_cid field in the CA_PROTO_READ_NOTIFY response message header communicates the CA status (see
caerr.h) of the request, as it was executed in the server, with this request type. Jeff From: [email protected]
[mailto:[email protected]] On Behalf Of [email protected] 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
-- |