[Zigbee] Sleepy end device get out of sleep in approx 10 mins

RE: [Zigbee] Sleepy end device get out of sleep in approx 10 mins

Tu Hoang — Mon, 18 Oct 2021 06:41:32 GMT

Hi Marte,

Sorry for the late reply, I have tested the new setting for the SDK and let the board run for 12 hours straight to find out that the power consumption did not suffer from the waking problem like before. So I guess that your walkaround solve the problem.

Thank you very much, I could not do it without your support.

Best regards and have a nice day,

RE: [Zigbee] Sleepy end device get out of sleep in approx 10 mins

Marte Myrvold — Mon, 20 Sep 2021 08:54:40 GMT

Hi Tu,

Have you been able to test the workaround? Did it work, or are you still experiencing this issue?

Best regards,

Marte

RE: [Zigbee] Sleepy end device get out of sleep in approx 10 mins

Tu Hoang — Fri, 10 Sep 2021 07:42:42 GMT

Hi Marte,

Thank you for the reply, so as i can see the value RADIO_DRIVER_RTC_OVRFLW_S the the amount of time in second that a device is allow to sleep.Anyway, I will try it and tell you the result.

Thank you for your help,

Best regards,

RE: [Zigbee] Sleepy end device get out of sleep in approx 10 mins

Marte Myrvold — Fri, 10 Sep 2021 07:04:11 GMT

Hi Tu,

This might be caused by the sleep period being longer than RTC overflow, as RTC overflow is 520 seconds, which is rather close to 10 minutes. Please try to make the following changes in external/zboss/osif/zb_nrf52_timer.c:

// In file: external/zboss/osif/zb_nrf52_timer.c
// make two changes
///////////////////////////////////////////
// Need this defines for later sleep period
// calculations.
// 
// Change this block:
#define ZB_NRF52_TIMER_VALUE    15360  /*microseconds in one beacon interval*/
// to this block:
#define ZB_NRF52_TIMER_VALUE      15360  /*microseconds in one beacon interval*/
#define MS_PER_S                  1000UL /* Miliseconds in one second. */
#define RADIO_DRIVER_RTC_OVRFLW_S 512UL  /* Time that has passed between overflow events. On full RTC speed, it occurs every 512 s. */
#define ZB_NRF52_MAX_SLEEP_PERIOD_MS  ((RADIO_DRIVER_RTC_OVRFLW_S - 1) * MS_PER_S) /* Zigbee max sleep period to prevent RTC timer overflow. */
///////////////////////////////////////////
///////////////////////////////////////////
// Workaround for long zigbee sleep period.
// Sleep period longer than RTC overflow,
// results in very short sleep scheduled,
// waking up the CPU frequently.
// 
// Change this block:
m_timer.dt        = 1000 * sleep_tmo;
// To this block:
/* Workaround for long zigbee sleep period.
 * Device wakes up on RTC event and scheduling sleep period
 * longer than RTC overflow (512 seconds) can result in very short sleep scheduled
 * whick wakes up CPU frequently and increases power consumptiom.
 */
m_timer.dt        = 1000 * ((sleep_tmo > (ZB_NRF52_MAX_SLEEP_PERIOD_MS)) ? (ZB_NRF52_MAX_SLEEP_PERIOD_MS) : (sleep_tmo));
///////////////////////////////////////////

Best regards,

Marte

RE: [Zigbee] Sleepy end device get out of sleep in approx 10 mins

Marte Myrvold — Thu, 09 Sep 2021 13:32:27 GMT

Hi Tu,

I am sorry for the delay.

I do not already know of any reason for the current consumption to suddenly go up after 10 minutes. I have tried to look into it to see if I could figure out why this is happening, but I have not been able to find an explanation as of yet. Are you able to turn on more logging? If you get logging from the zigbee_default_signal_handler() in zigbee_helpers.c, then you might see if the Zigbee stack generates any signal that is handled there when the current increase happens.

I have asked our developers if they know what might be the cause of this.

Best regards,

Marte

RE: [Zigbee] Sleepy end device get out of sleep in approx 10 mins

Tu Hoang — Wed, 08 Sep 2021 11:03:40 GMT

Hi Torbjørn,

Is there any update on the problem?

Best regards,

RE: [Zigbee] Sleepy end device get out of sleep in approx 10 mins

ovrebekk — Tue, 17 Aug 2021 13:22:17 GMT

Hi Tu

I think I will need help from the Zigbee experts to investigate this further, and I will do my best to get back to you early next week when they are back in office.

Best regards
Torbjørn

RE: [Zigbee] Sleepy end device get out of sleep in approx 10 mins

Tu Hoang — Mon, 16 Aug 2021 08:26:35 GMT

Hi Torbjørn,

Yes, you got that right, no devices were trying to communication to my board as well as my board was not connect to zigbee since there are no gw to send permit join request.

Best regards,

RE: [Zigbee] Sleepy end device get out of sleep in approx 10 mins

ovrebekk — Mon, 16 Aug 2021 08:16:23 GMT

Hi Tu

Thanks for the additional information.

So if I understand you correctly you are not connected to anything over Zigbee?

There are no other Zigbee devices in the area that might try to communicate with yours?

Best regards
Torbjørn

RE: [Zigbee] Sleepy end device get out of sleep in approx 10 mins

Tu Hoang — Fri, 13 Aug 2021 02:13:55 GMT

Hi Ovrebekk,

Nice to meet you.

Yes, i have a JlinkV9 debugger and use RTTViewer to see the log. I also put the code below in the zigbee handler and it is showing the time it have before waking up. In the first 10 mins, it just showing occationally the sleep_tmo. and the number are changing correctly (from the maximum timeout to to 0) but after 10 mins or even less, the sleep_tmo is poping up repeatedly (like in milisec). Beside that, I do not have anything in the log since the code i modified from the example are at the bare minimum of the example. I guess this have something to do with the Zigbee since i am not starting anything else but a buttons and some leds.

This is always happen every time after i reset and start up the program.

        case ZB_COMMON_SIGNAL_CAN_SLEEP:
            {
                zb_zdo_signal_can_sleep_params_t *can_sleep_params = ZB_ZDO_SIGNAL_GET_PARAMS(p_sg_p, zb_zdo_signal_can_sleep_params_t);
                NRF_LOG_INFO("Can sleep for %ld ms", can_sleep_params->sleep_tmo);
                zb_sleep_now();
            }
        break;

Hope that help,

Best regards,

RE: [Zigbee] Sleepy end device get out of sleep in approx 10 mins

ovrebekk — Thu, 12 Aug 2021 13:39:59 GMT

Unfortunately most of my colleagues experienced with Zigbee are on holiday for this week and next, so it is a bit limited what Zigbee support we can provide until they are back.

Have you done any testing with the debugger to try and figure out what might be happening when the current consumption increases?

Might there be any log output that could indicate something?

Would you say it happens consistently after a reset, at the same time?

Best regards
Torbjørn