Thermostat cluster enable issue

RE: Thermostat cluster enable issue

Rohit Rajapure — Fri, 30 Jul 2021 13:35:02 GMT

Hi Marte,

Okay, I will post in new and if you get any suggestion let me know.

Also, as per your suggestion we ported our functions into SDK4.1 but still we are getting same result in current 1mA avg.

Do not close this ticket, I need some points in new ticket as a reference. Once done I will only close.

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Marte Myrvold — Fri, 30 Jul 2021 12:44:10 GMT

Hi Rohit,

Thank you for providing detailed explanations of your project and set up. I have tried to look into it, but current consumption is not my field of expertise, so I have been unable to solve this so far. Most of the Zigbee team is out of office right now, so I have not been able to ask them more about expected current consumption in your scenario. I have asked some of our experts on current consumption to take a look. They have not been able to do so yet, but they will look into it next week.

I will be out of office the next few weeks, so someone else will take care of your case. Since this ticket has become rather long and the problem you have now is not directly related to the original topic of the ticket, can you please create a new ticket with your current problem? Please explain the problem you are having now in detail in the other ticket, and provide the information you shared in your last replies here. This will make it easier for the engineer responsible for your case to help you.

Best regards,

Marte

RE: Thermostat cluster enable issue

Rohit Rajapure — Wed, 28 Jul 2021 06:37:39 GMT

Hi Marte,

Thank you so much for the response.

Please find my attached document and explanation for your question, setup images.

Also, I have attached code which I used to check the current.

Go through my comments and let me know your feedback on my comments as early as possible.

devzone.nordicsemi.com/.../nRF52840-setup-and-comments.docx

main. cfile.

devzone.nordicsemi.com/.../456428.main.c

Hi,

Just now I tried with zigbee_power_down_unused_ram() function. As suggested ported the function from SDK4.1 to SDK3.0. And as per your suggestion called the function after zb_set_rx_on_when_idle(ZB_FALSE); in main file but still current remains same 1mA.

Along, with multi meter we used power profile kit to measure the current. In both tool we are getting avg current = 1mA.

Hi Marte,

One more update from my end. We tested our code using power profile Kit as said previously. And this is what we observed on power profile Kit.

Setup is same Radiator plus Nrf devkit as shown in document.

We see that there are spike in every 2.5sec. please find attached image of the same for reference. This might help us to narrow down the sleep issue.

My observation - In idle state, the power profiler show the current consumption in ampere. Average we see is around 1mA. But after every 2.5msec we see a spike of around 19msecs. This means that controller is either waking up every 2.5msec or it is not sleeping at all from start.

Let me know your feedback on this.

lasted main. c file with power down unused ram section as per SDK4.1. function.

devzone.nordicsemi.com/.../520150.main.c

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Marte Myrvold — Tue, 27 Jul 2021 14:27:26 GMT

Hi Rohit,

[quote userid="79402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321885#321885"]So, Till we get developer feedback on waking up device using Zigbee command. We tried SED config. And it gave us some better result around 1mA. But again this huge my target is 30uA. [/quote]

Can you please give some more information about what your project is doing when you are measuring the current and how you are measuring it? You say the device has joined the network, but is it performing any other actions while you are measuring the current consumption?

You can also check out our guide Measuring current, and I recommend reading the note further down on that page. Additionally, it is suggested to cut SB40 to put P22 in series with the load, as explained in Preparing the DK. You should also set SW6 to "nRF only".

When performing current consumption tests earlier, our developers have managed to get sleep current consumption down to 1.6-3.3 µA, depending on the amount of RAM retention. This was when the device had joined and was not performing additional actions, but being in sleep mode. However, it is difficult to compare with your results without knowing more about your test setup.

[quote userid="79402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321885#321885"]That's why asked any update from Developer for this? If the waking up device using Zigbee command gives us better result in current consumption I will definitely use that not SED. On other hand after configuring SED if would resulted me in uA (micro Ampear) then I would go ahead with. I didn't bother for waking up on Zigbee command.[/quote]

Please read what I wrote in my previous reply about this. If you want to get the lowest possible current consumption, you should use SED. You will not get lower current consumption when not using SED. The difference between SED and non sleepy devices is that with SED the radio is turned off and does not receive or send packets. This greatly reduces current consumption.

If you are using SED but does not see a significant impact on the current consumption, then it is possible the device does not go to sleep as it should, or that it wakes up very often.

Also, the current consumption in SED applications is further optimized in v4.1.0 of the SDK, so you it is very likely you would get a lower current consumption using that version.

[quote userid="79402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321885#321885"]Also, some points regarding System ON, no ram retention but how to do that no explanation.[/quote]

Please read my previous replies. I explained clearly what the parts of this configuration means:

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321062#321062"]

System ON: This means that the chip is in system ON, and not in system OFF, which means that the chip is in a regular state ready to run, and that the CPU is in sleep mode. The CPU is in a WFE (waitinf for event) call, and will wake when there is an interrupt. This interrupt is typically the RTC clock, but with 1 μA. the RTC is not in use.
no RAM retention: this means that the RAM is not conserved, and will practically mean that there is no code running on the chip.

[/quote]

You get System ON when the CPU is in sleep mode, so either when a SED goes to sleep, or when calling zb_osif_wait_for_event(). You must have some RAM retention, as without it, your application cannot run, but you can power down unused parts of RAM, as I have explained previously.

[quote userid="79402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321721#321721"]And also, I would like to know can we use system off in sleepy end device and wake up on GPIO interrupt.[/quote]

In both the case of SED and non-SED devices, the stack calls zb_osif_wait_for_event(), which will behave like a single call of __WFE() instruction, from a functional point of view. So if an interrupt occurs between zb_osif_wait_for_event() calls, the device will wake up. Thus, you can implement GPIO interrupts in the same way as you would with WFE (wait for event). You must enable GPIO, configure a pin for input, and configure it to give an interrupt on pin change. An example of how you can do this is to create a gpio_init functions as follows:

static void gpio_init(void)
{
    ret_code_t err_code;
    
    err_code = nrf_drv_gpiote_init();
    APP_ERROR_CHECK(err_code);
    
    nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_TOGGLE(false);
    in_config.pull = NRF_GPIO_PIN_PULLUP;
    
    err_code = nrf_drv_gpiote_in_init(PIN_IN, &in_config, in_pin_handler);
    APP_ERROR_CHECK(err_code);
    
    nrf_drv_gpiote_in_event_enable(PIN_IN, true);
}

Then you can call this function in main() during initialization. You must remember to define PIN_IN as the pin you want to use for interrupts. You can also check out the GPIOTE driver for more information.

Best regards,

Marte

RE: Thermostat cluster enable issue

Rohit Rajapure — Mon, 26 Jul 2021 16:56:09 GMT

Hi Marte,

Thanks for the response.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321875#321875"] I have already answered this, and explained that this is not possible with SED. With devices that are not SED, this will happen by default if you are using zb_osif_wait_for_event() to reduce power.[/quote]

- My point here is, I want less current consumption for my device it should be 30uA. As per your suggestion we tried SED because zb_osif_wait_for_event(); Didn't worked. It gave us current 3.9mA.

So, Till we get developer feedback on waking up device using Zigbee command. We tried SED config. And it gave us some better result around 1mA. But again this huge my target is 30uA.

- That's why asked any update from Developer for this? If the waking up device using Zigbee command gives us better result in current consumption I will definitely use that not SED. On other hand after configuring SED if would resulted me in uA (micro Ampear) then I would go ahead with. I didn't bother for waking up on Zigbee command.

- Point is, using SED or zb_osif_wait_for_event() not gave me less current. In document typical value mentioned. Also, some points regarding System ON, no ram retention but how to do that no explanation. System Off also same. Only wakeup on reset or GPIO interrupt that also not help me here.

Then how to reduce current?? We trying different different ways but still same result. Current not reducing below mA.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321875#321875"] As this feature is only available in v4.1.0, you must implement it yourself in v3.0.0. As I stated before you should look at the function zigbee_power_down_unused_ram() in zigbee_helpers.c in v4.1.0 to see how this can be done. After implementing the function, you should call it right after setting SED with zb_set_rx_on_when_idle() in main().[/quote]

- I saw some post and suggestion followed below to configure the same.

NRF_POWER->RAM[0].POWERCLR = 0x3;

NRF_POWER->RAM[1].POWERCLR = 0x3;
NRF_POWER->RAM[2].POWERCLR = 0x3;
NRF_POWER->RAM[3].POWERCLR = 0x3;
NRF_POWER->RAM[4].POWERCLR = 0x3;
NRF_POWER->RAM[5].POWERCLR = 0x3;
NRF_POWER->RAM[6].POWERCLR = 0x3;
NRF_POWER->RAM[7].POWERCLR = 0x3;
NRF_POWER->RAM[8].POWERCLR = 0x3F;

- As per our study I commented RAM[0], RAM[1] and RAM[2] and set RAM[8] = 0x3 then able to run my code.

- And, if i just comment RAM[0] and RAM[8] = 0x3F as per one of nrf engineer post, I am not able to run code. IT enters into hardfault.

- Okay, I will follows your steps. Use 4.1 to port in 3.0 SDK.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321875#321875"]I will come back to you regarding this.[/quote]

- Yes, please I will wait.

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Marte Myrvold — Mon, 26 Jul 2021 14:54:32 GMT

Hi Rohit,

[quote user="Rohit Rajapure"]And is there any update from developer regarding system wakeup on zigbee command?[/quote]

I have already answered this, and explained that this is not possible with SED. With devices that are not SED, this will happen by default if you are using zb_osif_wait_for_event() to reduce power.

SED: A Sleepy End Device will go into sleep mode, and not only low power mode. This will, among other things, turn off the radio. So the device cannot receive Zigbee packets, as the radio is not receiving anything. Sending a command to wake the device will do nothing, as it will only receive the command after it is already awake. This is part of the Zigbee specification, for RxOnWhenIdle = false devices (some places call it RxOnIdle = false or RxOffWhenIdle = true).
Non-SED: Calling zb_osif_wait_for_event() makes the device go into low power mode. This is functionally the same as a single call of __WFE() instruction (wait for event). The CPU goes into a low-power state until an event occurs. Any interrupt occurring between zb_osif_wait_for_event() calls will wake up the device, same as with __WFE(). The radio is not turned off, so the device will still receive Zigbee packets. Receiving Zigbee packets will be an event, so it will wake up.

[quote user="Rohit Rajapure"]let me know how I to power down unused ram section. [/quote]

As this feature is only available in v4.1.0, you must implement it yourself in v3.0.0. As I stated before you should look at the function zigbee_power_down_unused_ram() in zigbee_helpers.c in v4.1.0 to see how this can be done. After implementing the function, you should call it right after setting SED with zb_set_rx_on_when_idle() in main().

[quote user="Rohit Rajapure"]Let me know whether I have followed correct API to execute this erase info and NVIC_SystemReset() is for software? [/quote]

It should be enough to define ERASE_PERSISTENT_CONFIG as ZB_TRUE and call zigbee_erase_persistent_storage(ERASE_PERSISTENT_CONFIG). This should erase network data on a reset or power cycle of the device. This function calls zb_set_nvram_erase_at_start(), which enables or disables NVRAM erasing on application startup. If using zigbee_erase_persistent_storage() does not work, you can try calling zb_set_nvram_erase_at_start(ZB_TRUE) directly, but I would recommend using zigbee_erase_persistent_storage() instead. You should call these functions during the initialization, and not when the application is running. The function zigbee_erase_persistent_storage() will not make the device leave the network.

Since you are using v3.0.0, you can make your device leave the network by creating a function that does the same as light_switch_leave_nwk() in the light switch example.

static void light_switch_leave_nwk(zb_uint8_t param)
{
    zb_ret_t zb_err_code;

    /* We are going to leave */
    if (param)
    {
        zb_buf_t                  * p_buf = ZB_BUF_FROM_REF(param);
        zb_zdo_mgmt_leave_param_t * p_req_param;

        p_req_param = ZB_GET_BUF_PARAM(p_buf, zb_zdo_mgmt_leave_param_t);
        UNUSED_RETURN_VALUE(ZB_BZERO(p_req_param, sizeof(zb_zdo_mgmt_leave_param_t)));

        /* Set dst_addr == local address for local leave */
        p_req_param->dst_addr = ZB_PIBCACHE_NETWORK_ADDRESS();
        p_req_param->rejoin   = ZB_FALSE;
        UNUSED_RETURN_VALUE(zdo_mgmt_leave_req(param, NULL));
    }
    else
    {
        zb_err_code = ZB_GET_OUT_BUF_DELAYED(light_switch_leave_nwk);
        ZB_ERROR_CHECK(zb_err_code);
    }
}

[quote user="Rohit Rajapure"]And also, I would like to know can we use system off in sleepy end device and wake up on GPIO interrupt[/quote]

I will come back to you regarding this.

Best regards,

Marte

RE: Thermostat cluster enable issue

Rohit Rajapure — Mon, 26 Jul 2021 08:15:32 GMT

Hi Marte,

Update from my end,

As per your suggestion, I made the code in SED configuration. I have shared my main file in previous post. - Let me know any changes.

But with this SED, configuration what I observed is with Dev-kit and Radiator base (STM) board I am getting 1mA current. Which is comparatively less than what I was getting previously.

Now I would like to do further reduction in current including nRF dev-kit and STM8 board I need almost 60uA and only nRF i need 30uA.

So, I decided to add ram retention also here along with sleep. Please find the attached image of my memory usage and let me know how I to power down unused ram section.

I request you, please give your feedback as early as possible on this.

And also, I would like to know can we use system off in sleepy end device and wake up on GPIO interrupt. I mean device should work as sleepy end device as well as system off mode. It should wake up periodically like SED and wake up on system off mode? Let me know your feedback on this.

And is there any update from developer regarding system wakeup on zigbee command? I am getting pressure from team to resolve sleep issue.

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Rohit Rajapure — Fri, 23 Jul 2021 12:18:15 GMT

Hi Marte,

As I said last post that I am getting 3.9mA current with this config as you explained me,

zb_void_t zb_osif_go_idle(zb_void_t)
{
//TODO: implement your own logic if needed
zb_osif_wait_for_event();
}

I have tested multiple times and gave me 3.9mA. My last reading 0.03 mA was not correct. My mistake while taking readings. But I need help to reduce current.

Can you help me what could be the issue here?.

After battery life calculation we came to conclusion that we need at least 30/ 35uA only nRF part. My nrf52840 node should give me 30 to 35uA.

Hi,

Please find the attached code, as per your instruction I made the changes in my code regarding sleepy end device. Let me know I have followed your all steps so that I can test the current for this. As I am getting higher current in previous code so decide to test this sleepy end device also. main.c file

devzone.nordicsemi.com/.../211224.main.c

Also, below snippet is regarding erasing bonding info. The snippet present in attached uart_statemachin.c file. Let me know if I followed anything wrong here to erase info.

              //Master reset is executed
              if(ui8GetFlagBuffer[2] & FLAGS_BYTE_2_MASTER_RESET_REQUEST)
              {
//                boolReady = false; //set flag to execute communication state
//                boolIsMCURequest = true;
                zigbee_erase_persistent_storage(ZB_TRUE);  //erase bonding info or leave network
              }

devzone.nordicsemi.com/.../uart_5F00_statemachine.c

- After bonding erase I would like to perform soft reset and I used NVIC_SystemReset() function here. What I observed is after reset my while(1) loop not executing and when i paused the code it show me in nrf_log_frontend() file's bool nrf_log_frontend_dequeue(void) function.

-Why reset not working correctly?Let me know your feedback on this.

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Rohit Rajapure — Fri, 23 Jul 2021 09:18:53 GMT

Hi Marte,

Thank you for the response,

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321364#321364"]

To configure the device as a SED you must call zb_set_rx_on_when_idle(ZB_FALSE) in main, such as in the multi sensor example. This enables sleepy behavior and makes your device act as a Sleepy End Device.

You are correct in that you must call zb_sleep_now() in zboss_signal_handler(), when receiving the signal ZB_COMMON_SIGNAL_CAN_SLEEP. Again, you should do as in the multi sensor example.

[/quote]

- Okay, Noted.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321364#321364"] Yes, with SED you will use zb_sleep_now() to put the device and radio to sleep, and you can remove zb_osif_go_idle() from main.c. The function zb_osif_go_idle() is not really necessary to have in main.c if you are not using SED either, as it is already implemented in external/zboss/osif/zb_nrf52840_common.c. The only reason to use it in main.c is if you want to override the function to make it do something else than what it does in the implementation in zb_nrf52840_common.c.[/quote]

- Okay, Noted.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321364#321364"]

You can read about the clock sources for the LFCLK controller here: LFCLK controller. Further down on that page you will find 32.768 kHz crystal oscillator (LFXO), where you can read about LFXO.

You can see more about typical current consumption for nRF52840 in the electrical specification, where you can find information such as sleep current and radio transmitting/receiving current. The nRF52840 specification does not show the typical current for using LFXO, only LFRC, but the electrical specification for some of the other SoCs does, to show a comparison between using LFRC and LFXO as clock source:

[/quote]

- Okay, I will check.

I have noted down your points for configuring SED. And as per your previous post I have discussed your points about SED with my team. But they are like we will test the current default code on custom hardware and check the current.

- After testing default code on custom it gave us 3.9mA. This is too high. We are testing again on Dev-kit as well as custom. I will get back to you on result early.

And they want device should wake up Zigbee commands( it must) as per client requirement. But since nordic developer are busy. I will wait for something can we do here. But need help as early as possible make system wake up on Zigbee command and sleep if no commands. - Need help for this.

One more update from my end.

- There is one feature in my device, that is perform "network leave or erase the current connect coordinator info"

- To this what I done is, used zigbee_erase_persistent_storage() and set ZB_TRUE; this means by setting true it will erase the info.

- I did the same but it not erasing nor performing NVIC_SystemReset() correctly.

- My requirement is I have long button press which result in Reset of my STM8 board and that give me signal to nRF board (node) and I have perform erase info and softreset the device and start again.

Let me know whether I have followed correct API to execute this erase info and NVIC_SystemReset() is for software?

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Marte Myrvold — Thu, 22 Jul 2021 13:07:20 GMT

Hi Rohit,

[quote user="Rohit Rajapure"]If I configure as SED. It will give comparatively less current than getting now correct?[/quote]

Yes, that is correct.

[quote user="Rohit Rajapure"]And, If I just call sleep now () in zigbee_signal_handler means it is configured as SED[/quote]

This is not entirely correct.

You are correct in that you must call zb_sleep_now() in zboss_signal_handler(), when receiving the signal ZB_COMMON_SIGNAL_CAN_SLEEP. Again, you should do as in the multi sensor example.

[quote user="Rohit Rajapure"]And I can comment this part from code to make SED? Correct? [/quote]

Yes, with SED you will use zb_sleep_now() to put the device and radio to sleep, and you can remove zb_osif_go_idle() from main.c. The function zb_osif_go_idle() is not really necessary to have in main.c if you are not using SED either, as it is already implemented in external/zboss/osif/zb_nrf52840_common.c. The only reason to use it in main.c is if you want to override the function to make it do something else than what it does in the implementation in zb_nrf52840_common.c.

[quote user="Rohit Rajapure"]But LFRC give me better result then how to configure this? Is there any example for reference? [/quote]

You can read about the clock sources for the LFCLK controller here: LFCLK controller. Further down on that page you will find 32.768 kHz crystal oscillator (LFXO), where you can read about LFXO.

I_{ON_RAMON_RTC}	System ON, Full 24 kB RAM retention, Wake on RTC (running from LFRC clock)	1.5 µA
I_{ON_RAMON_RTC_LFXO}	System ON, Full 24 kB RAM retention, Wake on RTC (running from LFXO clock)	1.1 µA

Please note that the above numbers are from another SoC than the nRF52840 and has different typical current consumption than nRF52840.

Best regards,

Marte

RE: Thermostat cluster enable issue

Rohit Rajapure — Wed, 21 Jul 2021 12:06:25 GMT

Hi Marte,

Any update on above post?

My understanding is correct to configure SED device?If yes, then will configure likewise and test for current. Let me know your feedback.

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Rohit Rajapure — Wed, 21 Jul 2021 10:07:02 GMT

Hi Marte,

Thank you so much for response,

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321062#321062"]Due to summer vacation you might have to expect some increase in response time, also from our developers.[/quote]

- Okay, i will wait but need help.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321062#321062"]As for current consumption, you will notice a significant increase in current consumption when not using Sleepy End Device (SED) compared to a device with SED enabled. This is because with other low power modes, the radio is still always on, causing a much higher current consumption than if it is off. With SED the other hand, the radio will be off when it sleeps. However, this will make it so that the device will not be able to receive messages at all times, and cannot wake up by a command from another device, as it will not receive the message when it is sleeping. So you will have to either use SED and have the radio off at times, or you will have to have a higher current consumption. A device implemented as a SED will wake up periodically to check for messages, as I have explained earlier.[/quote]

- Okay, If I configure as SED. It will give comparatively less current than getting now correct?

- And, If I just call sleep now () in zigbee_signal_handler means it is configured as SED. And I can comment this part from code to make SED? Correct?

zb_void_t zb_osif_go_idle(zb_void_t)
{
//TODO: implement your own logic if needed
zb_osif_wait_for_event();
}

- And, in SED device wake up every 10sec correct? I read in one of the nordic link.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321062#321062"]The best option would be to use SDK 4.1.0 instead, but since that is not an option, you can try to add the function zigbee_power_down_unused_ram to your project yourself, as the implementation of the function is available in v4.1.0, and not an internal stack function. To do this, you must add the function to your SDK, as well as any dependencies of that function. I cannot guarantee that it will work, as there might be other changes between v3.0.0 and v4.1.0 affecting this, but it should be possible to power down the unused RAM in v3.0.0 as well.[/quote]

- Okay, I will check.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/321062#321062"] However, since you are able to power down unused parts of RAM, you will not have full 256 RAM retention, which will reduce current compared to the above. Additionally, you can use LFXO as a clock source instead of LFRC, and use an external crystal, which will have slightly lower current consumption than using LFRC.[/quote]

- No, I have note configured yet. But would like to configure. But LFRC give me better result then how to configure this? Is there any example for reference?

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Marte Myrvold — Wed, 21 Jul 2021 09:08:29 GMT

Hi Rohit,

Due to summer vacation you might have to expect some increase in response time, also from our developers.

As for current consumption, you will notice a significant increase in current consumption when not using Sleepy End Device (SED) compared to a device with SED enabled. This is because with other low power modes, the radio is still always on, causing a much higher current consumption than if it is off. With SED the other hand, the radio will be off when it sleeps. However, this will make it so that the device will not be able to receive messages at all times, and cannot wake up by a command from another device, as it will not receive the message when it is sleeping. So you will have to either use SED and have the radio off at times, or you will have to have a higher current consumption. A device implemented as a SED will wake up periodically to check for messages, as I have explained earlier. It will do this by polling it's parent and asking the parent if there are any messages for it, as the parent store the messages for some time so that the SED will receive them on wake up. You can change the poll interval with zb_zdo_pim_set_long_poll_interval, to make the sleepy end device poll it's parent at a shorter interval than the default one.

[quote user="Rohit Rajapure"]Can we use in SDK 3.0 ? If yes the How to handle it in helper.c file or any other file. [/quote]

The best option would be to use SDK 4.1.0 instead, but since that is not an option, you can try to add the function zigbee_power_down_unused_ram to your project yourself, as the implementation of the function is available in v4.1.0, and not an internal stack function. To do this, you must add the function to your SDK, as well as any dependencies of that function. I cannot guarantee that it will work, as there might be other changes between v3.0.0 and v4.1.0 affecting this, but it should be possible to power down the unused RAM in v3.0.0 as well.

[quote user="Rohit Rajapure"]"ION_RAMOFF_EVENT System ON, no RAM retention, wake on any event 0.97 μA" typically. [/quote]

This mode and current is for the base current consumption of the chip in ON idle mode.

System ON: This means that the chip is in system ON, and not in system OFF, which means that the chip is in a regular state ready to run, and that the CPU is in sleep mode. The CPU is in a WFE (waitinf for event) call, and will wake when there is an interrupt. This interrupt is typically the RTC clock, but with 1 μA. the RTC is not in use.
no RAM retention: this means that the RAM is not conserved, and will practically mean that there is no code running on the chip.

So you will not be able to get this current consumption and still run your application on your device. You will minimally need RAM retention, RTC to wake up at intervals, and the LF clock, which is needed for RTC. Therefore, your current consumption will be above 1 μA, even if you are using SED and powering down RAM sections. According to the specification, the expected current consumption with RAM retention and RTC is as follows:

I_{ON_RAMON_RTC}

System ON, full 256 kB RAM retention, wake on RTC (running from LFRC clock)

3.16

µA

However, since you are able to power down unused parts of RAM, you will not have full 256 RAM retention, which will reduce current compared to the above. Additionally, you can use LFXO as a clock source instead of LFRC, and use an external crystal, which will have slightly lower current consumption than using LFRC.

Best regards,

Marte

RE: Thermostat cluster enable issue

Rohit Rajapure — Wed, 21 Jul 2021 05:27:35 GMT

Hi Marte,

Any update from developer? I need urgent help.

And, how to enable this below configuration

"ION_RAMOFF_EVENT System ON, no RAM retention, wake on any event 0.97 μA" typically.

can you explain me the configuration for same.

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Rohit Rajapure — Tue, 20 Jul 2021 10:01:10 GMT

Hi Marte,

I went through the Power down RAM section. Here, It is mentioned that use zigbee_power_down_unused_ram() function from Zigbee application components. If I tried to search API/ function here it says zero result.

Similarly, Checked the light_switch example as it was mentioned in link for reference but in example alsp it says zero result. Am I following anything wrong here?

Hi, I got this. zigbee_power_down_unused_ram() this present in light_switch SDK4.1 example and helper.c file but not present in SDK3.0.

Can we use in SDK 3.0 ? If yes the How to handle it in helper.c file or any other file.

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Rohit Rajapure — Tue, 20 Jul 2021 07:59:24 GMT

Hi Marte,

Thank you for the response.

Sorry my mistake, I have made confusion while explaining.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/320828#320828"]You should not call nrf_pwr_mgmt_run() in the main loop yourself.[/quote]

- This example is peripheral code. I have made one of example copy and followed some online tutorial steps to run this API.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/320828#320828"]When you call zboss_main_loop (or zboss_main_loop_iteration if you want to include custom features) in main you simply start the Zigbee stack, and the stack will interact with the application using stack signals (zboss_signal_handler) and ZCL callbacks (zcl_device_cb). So all of this is handled internally by the stack after you start the main loop. This includes the signal that it can go to sleep. The stack decides that it has nothing more to do, as there are no stack tasks or anything in the queue that needs to be handled, so the stack informs the device that it can go to sleep or power down. This will cause zb_osif_go_idle to be called automatically.[/quote]

- Yes, This is present in my radiator code. Here I have not added anything in while loop(). I kept code same as present in light_bulb code. With this only I have tested the current and it gave me 0.03mA after discovery. Where my Radiators STM base board and nRF52 Dev-kit connected. I want battery to life 2 years so I need almost 1uA current that too only my RF board (nRF should consume 1uA current).

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/320828#320828"]While I wait for a response from the developers,[/quote]

- ya , sure please let me know i will wait for positive response.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/320828#320828"]you can also take a look at Powering down RAM sections to further reduce current consumption by powering down sections of the RAM memory that are not used by the application.[/quote]

- Okay, I will check this part too.

Thank you so much.

Regards,

Rohit R

RE: Thermostat cluster enable issue

Marte Myrvold — Tue, 20 Jul 2021 07:48:16 GMT

Hi Rohit,

You should not call nrf_pwr_mgmt_run() in the main loop yourself. When you call zboss_main_loop (or zboss_main_loop_iteration if you want to include custom features) in main you simply start the Zigbee stack, and the stack will interact with the application using stack signals (zboss_signal_handler) and ZCL callbacks (zcl_device_cb). So all of this is handled internally by the stack after you start the main loop. This includes the signal that it can go to sleep. The stack decides that it has nothing more to do, as there are no stack tasks or anything in the queue that needs to be handled, so the stack informs the device that it can go to sleep or power down. This will cause zb_osif_go_idle to be called automatically. This function checks if the logger has anything to process and calls the function zb_osif_wait_for_event, which in turn calls the nrf_pwr_mgmt_run API. You can see part of this in the flowchart below, which is from the page about Zigbee stack sleep routines in our documentation. Since your device is not a sleepy end device, the third step will result in no, since "rx_off_when_idle" is not true, and it will go to zb_osif_go_idle.

While I wait for a response from the developers, you can also take a look at Powering down RAM sections to further reduce current consumption by powering down sections of the RAM memory that are not used by the application.

Best regards,

Marte

RE: Thermostat cluster enable issue

Rohit Rajapure — Tue, 20 Jul 2021 07:17:40 GMT

Hi Marte,

Thank you I will wait for your response. Please let me know as early as possible.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/320815#320815"]what the best way to do it when you want to wake up on received Zigbee commands and GPIO interrupt[/quote]

- Yes, more focus on wake up on zigbee commands from gateway ( first priority) and then GPIO as (second priority).

- But also, check my comments shared. Am I following correct steps or not? If I am doing anything wrong here then correct me. I will follow the steps and again check for current consumption.

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Marte Myrvold — Tue, 20 Jul 2021 07:08:56 GMT

Hi Rohit,

I have asked our developers about this, about how to further reduce current consumption and what the best way to do it when you want to wake up on received Zigbee commands and GPIO interrupt, in addition to the alarm and timer that is already a part of the sleep routine.

Best regards,

Marte

RE: Thermostat cluster enable issue

Rohit Rajapure — Tue, 20 Jul 2021 03:52:46 GMT

Hi Marte,

Any update on this?

Yesterday, I ran my code which contains below snippet in code, as per your explanation it handled by stack so tested current consumption with setup.

Here, I got 0.03mA after discovery/ network connect. But this is too high. I want battery life should be 2 years so I need almost 1uA.

/**@brief Function which tries to sleep down the MCU
*
* Function which sleeps the MCU on the non-sleepy End Devices to optimize the power saving.
* The weak definition inside the OSIF layer provides some minimal working template
*/
zb_void_t zb_osif_go_idle(zb_void_t)
{
//TODO: implement your own logic if needed
zb_osif_wait_for_event();
}

Also, I went through product specific document I found below measurement

"ION_RAMOFF_EVENT System ON, no RAM retention, wake on any event 0.97 μA" typically.

- I want similar should happen in my code means, It should wake up on any event either Zigbee or gpio. But I am not understanding how to enable this.

- By calling "nrf_pwr_mgmt_run();" only this function in main infinite loop() it will give me above configuration or do I need to have any other configuration? Can you please help here the configuration. Please urgent !!.

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Rohit Rajapure — Mon, 19 Jul 2021 03:55:47 GMT

Hi Marte,

Thank you for the response.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/320467#320467"]Since you want your device to be able to receive Zigbee commands during low power mode, you cannot use sleepy end device.[/quote]

- Okay , I will not configure this.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/320467#320467"]On devices that are not sleepy end devices the stack calls the nrf_pwr_mgmt_run API if the Zigbee scheduler queue is empty. This happens through the function zb_osif_wait_for_event(), and it happens by the stack already, as part of the internal handling of the stack inside zboss_main_loop_iteration()[/quote]

- Okay, so since it is already declared in my code. It is minimal possible sleep config. As it is already called by stack function. I do not need to call this again and with I can check default current? correct?.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/320467#320467"]The way you can do this is by simply creating a new definition of the function in your main.c file, as this is a weak function. This is already done in the light bulb example, so you can look there for an example of how to do this.[/quote]

- I am using light_bulb code only. I can see they have only called below snippet. Not handled any extra things to refer.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/320467#320467"]as well as implementing GPIO interrupts and wake up timer.[/quote]

- Okay, I will refer the power management code from peripheral example.

- In nrf_pwr_mgmt_shutdown() system enters into deep sleep mode and wake up on 4 ways." First is The DETECT signal. optionally generated by GPIO peripheral". This means I can use my ULP pin (GPIO pin as mentioned previous post) to wake up device correct? Let me know if i am wrong here.?

- Let me know your feedback as soon as possible. Because I have started this file including process and I would like to complete this today. Urgent for me.

Hi, Update from me,

- I had gone through the peripheral example and some link online. I tried to execute the system off mode configuration in simple code. Here, I want to wake up device using my ULP (GPIO pin ) interrupt. But I am not finding wake up function. I have put device in sleep in while (1) loop by calling "nrf_pwr_mgmt_run();" function.

- To make system OFF enabled I have used "NRF_PWR_MGMT_CONFIG_STANDBY_TIMEOUT_ENABLED 1". Followed the steps but it is waking up only after "RESET" is pressed but it doesn't work for me.

- As stated it should work on GPIO interrupt too correct? Then why it is not working on GPIO.

- And which function/API I have to call for wake up ?

Urgent. Please let me know your feedback.

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Marte Myrvold — Fri, 16 Jul 2021 13:59:34 GMT

Hi Rohit,

Since you want your device to be able to receive Zigbee commands during low power mode, you cannot use sleepy end device. On devices that are not sleepy end devices the stack calls the nrf_pwr_mgmt_run API if the Zigbee scheduler queue is empty. This happens through the function zb_osif_wait_for_event(), and it happens by the stack already, as part of the internal handling of the stack inside zboss_main_loop_iteration()

As you want to change the default behavior of the stack sleep routines, you should overwrite the function zb_osif_go_idle() to handle it the way you want. The way you can do this is by simply creating a new definition of the function in your main.c file, as this is a weak function. This is already done in the light bulb example, so you can look there for an example of how to do this. You can then implement functionality for putting the device to sleep/low power mode inside this function, as well as implementing GPIO interrupts and wake up timer.

I also recommend actually measuring the power consumption of the device during development, to make sure that it satisfies your specifications. You can read the part about power consumption measurements on our Zigbee examples page in the documentation for more information about this.

Best regards,

Marte

RE: Thermostat cluster enable issue

Rohit Rajapure — Fri, 16 Jul 2021 05:54:30 GMT

Hi Marte,

I had gone through the link that you have shared regarding Zigbee stack sleep.

But for me points are unclear. Means I am not getting how to handle go to sleep and wake up from sleep in this,

can you please guide me here,

I have one GPIO pins which toggles as input and output pin during command sharing between nRF and STM8 board over UART. Means this gpio pins first configured as input and if interrupt it switch to output pin and stay for 5msec high to send commands over UART.

So, my plan is to use this gpio for waking up device from sleep mode. Is it possible?

And also wake up using wake up timer?

I have referred ble_peripheral examples here for GPIO interrupt. Can I use same method in Zigbee code ?

As per your suggestion, I have referred multi sensor example to enable sleep_now() function in my code. I have included it my code zigbee_signal_handler().

Attached is my main.c file. Let me know your feed back on this.

devzone.nordicsemi.com/.../0486.main.c

- With initialization will my sleep work and can I test the current consumption for the same?

Please guide me how to implement GPIO wake up mechanism here and go to sleep()?

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Rohit Rajapure — Wed, 14 Jul 2021 14:34:30 GMT

Hi Marte,

Thank you for the response.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/320062#320062"]The button does not make the device go into sleep mode or wake up from sleep when it is pressed. What it does is to enable sleepy end device behavior. This is there so that the user can decide, when resetting the device, whether they want the behavior enabled or not. In the multi sensor example it is enabled from start, as zb_set_rx_on_when_idle(ZB_FALSE) is called in main() before the Zigbee stack is started. Light switch instead calls sleepy_device_setup(), which checks whether the button for enabling sleepy end device is pressed or not, and will enable the behavior if the button is pressed. Additionally, the button must be pressed while resetting the board. Pressing the button while the device is on will not affect the sleepy end device behavior.[/quote]

- Okay, my understanding is wrong.

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/320062#320062"]above, zb_set_rx_on_when_idle(ZB_FALSE) will not make it go to sleep, it will enable sleepy end device behavior. It will go to sleep when there is nothing to do and the signal ZB_COMMON_SIGNAL_CAN_SLEEP is generated. This happens when there is no immediate callback for execution and there is no outgoing packet on the MAC level. If there are any alarms in the queue, then the device will wake up when the first alarm is called. If there are no alarms in the queue, then the sleep duration is set to 10 seconds.[/quote]

-Okay, as per your suggestion I have referred the multi sensor example and made the respected changes in zigbee_signal_handler() as done in multi sensor done.

- as per explanation it in sleep mode is configured and it will enter into sleep if there is no signal. Correct? Correct me if I am wrong.

And wake up from sleep every 10sec default time. Correct?

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/320062#320062"]You will not be able to use sleepy end device if you want your device to wake up if there is a Zigbee command. [/quote]

- Okay, then How to configure it then?

[quote userid="92402" url="~/f/nordic-q-a/75611/thermostat-cluster-enable-issue/320062#320062"]You can also change the sleep functionality if you do not want to use the default behavior by using the weak functions zb_osif_go_idle or zb_nrf52840_sleep. [/quote]

- Sorry, It is unclear.

- And, we can not use this "ZB_COMMON_SIGNAL_CAN_SLEEP ". If we are waking up device using Zigbee command and GPIO interrupt. Correct? If yes, then let me know which example explain this 2 waking mechanism. I will refer the that example for my implementation.

Thanks and Regards

Rohit R

RE: Thermostat cluster enable issue

Marte Myrvold — Wed, 14 Jul 2021 14:04:13 GMT

Hi Rohit,

[quote user="Rohit Rajapure"]this means If button is pressed device will not go into sleep correct? or is it wake up from sleep when button pressed?[/quote]

The button does not make the device go into sleep mode or wake up from sleep when it is pressed. What it does is to enable sleepy end device behavior. This is there so that the user can decide, when resetting the device, whether they want the behavior enabled or not. In the multi sensor example it is enabled from start, as zb_set_rx_on_when_idle(ZB_FALSE) is called in main() before the Zigbee stack is started. Light switch instead calls sleepy_device_setup(), which checks whether the button for enabling sleepy end device is pressed or not, and will enable the behavior if the button is pressed. Additionally, the button must be pressed while resetting the board. Pressing the button while the device is on will not affect the sleepy end device behavior.

[quote user="Rohit Rajapure"]Means, only calling this function device will go to sleep correct? But when it wake up ? Is it wake up periodically or any other way? [/quote]

No, it will not go to sleep. As I explained in my previous reply and above, zb_set_rx_on_when_idle(ZB_FALSE) will not make it go to sleep, it will enable sleepy end device behavior. It will go to sleep when there is nothing to do and the signal ZB_COMMON_SIGNAL_CAN_SLEEP is generated. This happens when there is no immediate callback for execution and there is no outgoing packet on the MAC level. If there are any alarms in the queue, then the device will wake up when the first alarm is called. If there are no alarms in the queue, then the sleep duration is set to 10 seconds.

You will not be able to use sleepy end device if you want your device to wake up if there is a Zigbee command. When using sleepy end device, the device will not receive messages while it is asleep, but will poll it's parent at intervals to see if there are any messages waiting for it.

You can also change the sleep functionality if you do not want to use the default behavior by using the weak functions zb_osif_go_idle or zb_nrf52840_sleep. See Zigbee stack sleep routines for more information. This documentation is for v4.1.0, as the "Zigbee application helper functions" is not in the documentation for v3.0.0, but the weak functions exist in both versions.

Please also see Power saving for ZED to get a clearer understanding of the power saving mechanisms for end devices in the SDK.

Best regards,

Marte