Reduce the number of retries for an unavailable device

RE: Reduce the number of retries for an unavailable device

AHaug — Mon, 06 May 2024 10:25:03 GMT

Hi,

The answer is as follows:

`ZB_N_APS_MAX_FRAME_RETRIES` defaults to 3, but the Zigbee spec defines `apscMaxFrameRetries` as `The maximum number of retries allowed after a transmission failure`, so I would say it leaves the door open to set a lower value.

`ZB_MAC_MAX_FRAME_RETRIES` defaults to 3, and as mentioned the IEEE 802.15.4 spec defines `macMaxFrameRetries` also as `The maximum number of retries allowed after a transmission failure` and allows the values 0-7.

However, both are defined in `modules/lib/zboss/include/zb_config_common.h`, which means that those are hard coded in the stack provided with the precompiled libraries and modifying them has no effect (as you observed).

So, those are the values that were used to asses the Zigbee certification conformance and Nordic in-house testing. Changing them could lead to unexpected behavior and potentially non-conformance with the Zigbee certification.

You can see more in 2.2.7.1 in the Zigbee spec.

Kind regards,
Andreas

RE: Reduce the number of retries for an unavailable device

AHaug — Mon, 29 Apr 2024 13:27:12 GMT

Hi,

Just an update: We've done some testing regarding the following

apscMaxFrameRetries is set to 3 according to the spec, but macMaxFrameRetries in the 802.15.4 spec is 3 by default but can be 0-7. The question is if it is possible to change this value.

ZB_MAC_MAX_FRAME_RETRIES, which the customer changed, does not seem to affect the number of MAC frame retries.

We've created an internal inquiry with the Zigbee team and I'll get back to you when I have some more information

Kind regards,
Andreas

RE: Reduce the number of retries for an unavailable device

AHaug — Fri, 26 Apr 2024 11:35:14 GMT

Hi,

I've picked up your case and will be looking into it. I will return with an update regarding the status next week.

Kind regards,
Andreas