Tool/software:
We are having trouble establishing a reliable WiSUN connection between our Wi-SUN router nodes and a Renasys-based border router, used by our customer. We successfully handle broadcast messages, but once the unicast sequence starts we seem to lose packets and fail to establish a connection.
Our setup:
- We are using a TI CC13xx-based router node, with an unmodified WiSUN stack. (CCS 12.60 + SDK 7.10, same behaviour with CCS 12.71 + 7.41.00.17)
- The customer has confirmed that they are using a Renasys R5F56519BDFM with FAN1.0 stack.
- Region is configured for Brazil.
- WiSUN parameters, especially unicast & broadcast timing, match.
Observations:
- Fixed channel works well. Router nodes see advertisements, configuration, authenticates and figures out routing. Once established, this connection is stable.
- Frequency hopping fails. Specifically, the router node fails to receive an ACK, usually while we are still in the EAPOL exchanges.
- Sometimes (<%5), we progress beyond EAPOL, but we still lose packets shortly afterwards
- Sniffing is tricky across all the channels, but ever once in a while we'll catch a fragment of the authentication flow. This usually consists of a TX + ACK on a single channel, occasionally we only see the TX portion - I'm not sure how much we can deduce from this.
- We once or twice succeeded in the full authentication flow, but this was not repeatable.
- Broadcast messages from the border router are received reliably.
Do you have any suggestions to help and resolve this? For example,
- Are you aware of any WiSUN interop challenges between TI and Renasys?
- Is there a way to verify the channel hopping sequence?
