This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

High sleep current consumption in SED Thread+BLE multiprotocol example

Hi 

There is an issue in SDK for Thread & Zigbee 4.1.0 release. It does not appear in previous releases. The problem manifests itself as higher current consumption. According to " https://devzone.nordicsemi.com/f/nordic-q-a/62129/high-sleep-current-consumption-in-sed-thread-ble-multiprotocol-example" ,after modification,the consumption is also have 1.2mA, is there something wrong? 

      I  just have modified "radio_mode        = THREAD_RADIO_MODE_RX_OFF_WHEN_IDLE"  and add "NVIC_ClearPendingIRQ(CRYPTOCELL_IRQn);" before "thread_sleep();" 

Parents
  • Hi Charliie

    The example is "examples\multiprotocol\ble_thread\ble_thread_dyn_template"  ,  just like above if I don't modified ,the current consumption is over 18mA.   According to my test,I think the current of 1.2mA  is All generated by thread. What can  I do to continue to reduce the current consumption of this example?

    Thanks!

  • Hi Xiang,

    Have you tried the BLE Scanner and Thread SED Example? The SED model will decrease the power consumption if it still satisfies your needs.  Otherwise, you have to think about other solutions instead of Thread, because it is not specifically designed for power-saving purposes. Its target is to provide IP connections for IoT devices. This kind of heavy protocol is not power-saving friendly.

    If you just start your new project, I also strongly suggest you move to NCS instead of nRF52 SDK, which will be no updated in the future.

    Best regards,

    Charlie

Reply
  • Hi Xiang,

    Have you tried the BLE Scanner and Thread SED Example? The SED model will decrease the power consumption if it still satisfies your needs.  Otherwise, you have to think about other solutions instead of Thread, because it is not specifically designed for power-saving purposes. Its target is to provide IP connections for IoT devices. This kind of heavy protocol is not power-saving friendly.

    If you just start your new project, I also strongly suggest you move to NCS instead of nRF52 SDK, which will be no updated in the future.

    Best regards,

    Charlie

Children
No Data
Related