This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2652R: Group executions getting missed when executing groups repeatedly

Part Number: CC2652R


Hi,

I am trying to execute a group update continuously on my network.

The test case send a group message every 1 second to a group.
However on the sniffer I am observing that the device generating the group message skips some executions of this message altogether.
I have verified that I am making the request to the zstack layer correctly and periodically every 1 second.

Please could you advise, why this could be happening ?

Thanks
Akhilesh

  • Hi,

    From further investigation, we observed that the we receive zstackmsg_CmdIDs_AF_DATA_CONFIRM_IND with status 0xE1, when the message fails.

    This status is not mentioned in the ZStatus enum as well. What is this error, why and when does it occur.

    Edit: Found that this error is

    #define MAC_CHANNEL_ACCESS_FAILURE  0xE1  /* The operation or data request failed because of
                                                 activity on the channel */

    Can we prevent or identify when this error can happen ?

    Thanks
    Akhilesh

  • Hi Akhilesh,

    Thank you for taking the additional debug steps to identify the root cause of your issue.  MAC_CHANNEL_ACCESS_FAILURE results when the CSMA/CA (carrier-sense multiple access/collision avoidance) detects that the channel is too noise to effectively send out Zigbee packets over-the-air.  The macPibDefaults values which determine this feature (maxCsmaBackoffs, minBe, and maxBe) are configured in mac-cfg.c but it is preferable to reduce channel interference or find a less noise channel on which to operate.  As observed, you can identify occurrences of MAC_CHANNEL_ACCESS_FAILURE from your application and take further action based on that information.

    Regards,
    Ryan

  • Hi Ryan,

    Thanks for the info.
    We chose an optimal channel and are retrying a few times to reduce the percentage of failed messages.

    Akhilesh