This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF9160 Sleep and Idle power consumption

Can you please tell us what is the power consumption in Idle State with DRX = 1.28s and Sleep State with DRX = 1.28s? And an estimate with eDRX at 5.12 s?

We are asking because in our solution the user can control the device and we need small delays. This means we cannot have the device sleep without checking for received messages for too many seconds. We will maybe use eDRX with 5.12 s but unlikely to use higher sleep values. 
What is the power consumption in this case?

Thanks

Parents
  • Hi,

    Thanks for the link for the power calculator, it's really useful!

    It seems most IoT applications allow larger sleep times and our usecase in which the user controlls the device and expects up to 2-3 seconds of delay is not the standard. I would appreciate if you confirm that my understanding is correct:
    - We can set the 1.28 or 2.56 iDRX interval. This is basically using standard DRX sleep mechanism.
    - eDRX is an extended DRX and we can set it to 5.12 and this would allow a longer idle time and less checks for received messages. This is as long as the network also allows the 5.12s eDRX interval.
    Is my understanding corect?

    And again, just to be 100% sure, the nRF9160 modem supports the above settings, right?

    If so, i will order a development kit and see how it goes from there!

    Thanks

  • Hi,

     

    nicolae.georgescu said:
    It seems most IoT applications allow larger sleep times and our usecase in which the user controlls the device and expects up to 2-3 seconds of delay is not the standard. I would appreciate if you confirm that my understanding is correct:
    - We can set the 1.28 or 2.56 iDRX interval. This is basically using standard DRX sleep mechanism.
    - eDRX is an extended DRX and we can set it to 5.12 and this would allow a longer idle time and less checks for received messages. This is as long as the network also allows the 5.12s eDRX interval.
    Is my understanding corect?

    Yes, you're right. You can disable both eDRX and PSM, in which you're in a higher level of sleep (connected DRX), with lower latency and higher current consumption.

    nicolae.georgescu said:
    And again, just to be 100% sure, the nRF9160 modem supports the above settings, right?

    If so, i will order a development kit and see how it goes from there!

    Yes, we support eDRX. 5.12 s is the lowest you can set/get with this power mode, provided that the network gives you this timing:

    https://infocenter.nordicsemi.com/topic/ref_at_commands/REF/at_commands/nw_service/cedrxrdp_set.html?cp=2_1_7_4_0

     

    Kind regards,

    Håkon

Reply
  • Hi,

     

    nicolae.georgescu said:
    It seems most IoT applications allow larger sleep times and our usecase in which the user controlls the device and expects up to 2-3 seconds of delay is not the standard. I would appreciate if you confirm that my understanding is correct:
    - We can set the 1.28 or 2.56 iDRX interval. This is basically using standard DRX sleep mechanism.
    - eDRX is an extended DRX and we can set it to 5.12 and this would allow a longer idle time and less checks for received messages. This is as long as the network also allows the 5.12s eDRX interval.
    Is my understanding corect?

    Yes, you're right. You can disable both eDRX and PSM, in which you're in a higher level of sleep (connected DRX), with lower latency and higher current consumption.

    nicolae.georgescu said:
    And again, just to be 100% sure, the nRF9160 modem supports the above settings, right?

    If so, i will order a development kit and see how it goes from there!

    Yes, we support eDRX. 5.12 s is the lowest you can set/get with this power mode, provided that the network gives you this timing:

    https://infocenter.nordicsemi.com/topic/ref_at_commands/REF/at_commands/nw_service/cedrxrdp_set.html?cp=2_1_7_4_0

     

    Kind regards,

    Håkon

Children
No Data
Related