Open thread ACK

Hi Team

Some times our nRF52 can't received the ACK from border router. But we can see that the border router send the ACK from sniffer data.  

  • which Kconfig can set the Rssi filter in open thread like otLinkFilterSetDefaultRssIn
  • CONFIG_OPENTHREAD_MAC_SOFTWARE_ACK_TIMEOUT_ENABLE  if I set this to N, the ACK time out is genetated by hardware?
  • Can I modify the kAckTimeout value in line 650 v2.5.0\modules\lib\openthread\src\core\mac\sub_mac.hpp?
  • Is there any other thing which I can check for this issue.

Regards

Victor

  • Hello,

    Can you please send the sniffer trace that your screenshot is from?

    What is the root issue? Are you not seeing the ACK in your application (sometimes)? 

    Best regards,

    Edvin

  • Hi Edvin

    Customer lost their orignal trace data. They send me a new one. There is also same issue in this trace data. The device drop from the thread network sometimes. 

    • In trace data, From the line 2760446, the device 5a:3f:82:d6:7d:60:fd:87 become abnormal. It seems can't receiceve the ACK from router 62:5f:87:d6:91:00:d5:e4.
    • The device  drop from thread network, and try to re-connect. It still can't recieved the data from router sometimes.
    • The device re-connect to thread network in line 2762993.
    • It took a total of one minute from the device becoming abnormal to the device returning to normal.

    It seems that the device suddenly lost its RX capability. Could you help to analyze this issue. Thank you.

    2024_01_07.pcapng

    Regards

    Victor

  • Hi Edvin

    Is there any update for this issue?

    Regards

    Victor

  • Hello Victor,

    Sorry for the late reply. I have been out of office since Monday. 

    I get this popup when I try to open the trace:

    In addition, the file only has 1018837 lines. Finally, I am not able to decrypt the packets:

    But I am not sure whether that is due to a different network key, or if it is because the file is corrupted. 

    Do you see the same if you download the file that you uploaded? And do you see the same if you open your original file?

    Do you know anything about the placement of the node that drops out? Is it far from the other devices? Is it possible that it is not in range of the rest of the network?

    Best regards,

    Edvin

  • Hello Victor,

    I still can't decrypt the packets. Do you know what network key they are using?

    I am looking at your trace (from Teams) now. I see (filtering on the wpan.src16 == 0x6035) that the node has a lot of retransmissions between packet ~2753543 and ~2779915. 

    I see that this is not limited to the 0x6035 device. Does it occur particularly often on this device? Or is it evenly distributed?

    How about the range of the devices. Are they close to one another, or are they widely spread out? Are any of the nodes physically moving, or are they stationary?

    I see that there is quite a lot of traffic on the network. Did the issue occur more frequently as more nodes were added, or does it also happen if you take away e.g. half of the nodes?

    A lot of questions here, but we need to start somewhere.

    Best regards,

    Edvin

Related