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

Power Consmuption issue in nrf51 during advertising packets

Hi All,

My goal is to advertise the generic packets untill a GPIO interrupt occurs. So in order to achieve low power consumption I have increased the time interval of those packets being advertised from 40ms to 3 seconds. While scanning i am able to see the packets in every 3 sec, but as intended i don't see any reduction in power consumption. With both the intervals, it consumes same 10mA. Am i missing something on this, please suggest.

Any suggestion would be well appreciated.

Thanks

Parents
  • @Brajesh: Depends on which timer you are using, if you use the RTC timer (app_timer) then the current consumption should be few uA. If you use the timer running on 16MHz the current consumption will be 30uA+400uA (or +700uA depends on the 16MHz clock source) => Anyway it can't be the timer running on 16MHz clock.

    When in connection how long in a conection event do you keep the CPU on (to do interrupt handler for example) ?

    I would suggest you to test with our example. You can either try with ble_app_pwr_profiling (which is power optimized) or with any normal example , ble_app_hrs for example.

Reply
  • @Brajesh: Depends on which timer you are using, if you use the RTC timer (app_timer) then the current consumption should be few uA. If you use the timer running on 16MHz the current consumption will be 30uA+400uA (or +700uA depends on the 16MHz clock source) => Anyway it can't be the timer running on 16MHz clock.

    When in connection how long in a conection event do you keep the CPU on (to do interrupt handler for example) ?

    I would suggest you to test with our example. You can either try with ble_app_pwr_profiling (which is power optimized) or with any normal example , ble_app_hrs for example.

Children
No Data
Related