Idle power consumption jumps up following the very first distance measurement

The idle power consumption (i.e. the current draw between adverts) is 2.4uA prior to the first call of dm_request_add() following reset.

Once a distance measurement has taken place (i.e. dm_request_add() has been called), the idle power consumption increases to 8.8uA and never returns to the original value of 2.4uA.



No other changes were made to the code between the two screenshots, other than commenting out the call to dm_request_add.

Is this because a peripheral e.g. 
ncs,dm-timer = &timer2; continues to run when it shouldn't?

Parents
  • Hi Matthew

    Yes, most likely this is due to the timer or another peripheral instance not being disabled correctly after a distance measurement. Can you confirm that the device is successfully disconnected from the other when this excess power consumption occurs, and what NCS version are you working on when seeing this? Are you measuring this using an nRF52833 DK or custom board?

    Best regards,

    Simon

Reply
  • Hi Matthew

    Yes, most likely this is due to the timer or another peripheral instance not being disabled correctly after a distance measurement. Can you confirm that the device is successfully disconnected from the other when this excess power consumption occurs, and what NCS version are you working on when seeing this? Are you measuring this using an nRF52833 DK or custom board?

    Best regards,

    Simon

Children
Related