You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the connection through a ATDECC controller of a talker to a listener is not working. It does not respond with a CONNECT_TX_COMMAND.
From analyzing working commercial endpoints, the process seems is the following:
Controller to IEEE1722 Multicast: AVDECC Connection Management Protocol CONNECT_RX_COMMAND
Listener to IEEE1722 Multicast: AVDECC Connection Management Protocol CONNECT_RX_RESPONSE
Listener to IEEE1722 Multicast: AVDECC Connection Management Protocol CONNECT_TX_COMMAND
Talker to IEEE1722 Multicast: AVDECC Connection Management Protocol CONNECT_TX_RESPONSE
This is also described in Section 8.1.1 in the IEEE 17221-2021 document (although a little cryptic, because of exception cases):
The ATDECC Controller sends a CONNECT_RX_COMMAND to the ATDECC Listener.
The ATDECC Listener sends a CONNECT_TX_COMMAND to the ATDECC Talker.
The ATDECC Talker responds with an appropriate STATUS and the connection information.
In case of a timeout of the first CONNECT_TX_COMMAND, the ATDECC Listener sends a single retry to the ATDECC Talker. If this command fails then the ATDECC Listener returns failure for the CONNECT_RX_COMMAND.
The successful sequence captured through tshark looks like this:
The problem is that the listener_unique_id checked in the _handleConnectRxCommand and other methods is not correctly set/handled, so that the validListenerUnique function returns false.
Currently, the connection through a ATDECC controller of a talker to a listener is not working. It does not respond with a
CONNECT_TX_COMMAND
.From analyzing working commercial endpoints, the process seems is the following:
CONNECT_RX_COMMAND
CONNECT_RX_RESPONSE
CONNECT_TX_COMMAND
CONNECT_TX_RESPONSE
This is also described in Section 8.1.1 in the IEEE 17221-2021 document (although a little cryptic, because of exception cases):
The successful sequence captured through
tshark
looks like this:The text was updated successfully, but these errors were encountered: