nRF9160/SLM sleep power consumption increases ~20uA after wakekup and AT#XSLEEP=2

RE: nRF9160/SLM sleep power consumption increases ~20uA after wakekup and AT#XSLEEP=2

Stian Røed Hafskjold — Tue, 30 Aug 2022 14:43:14 GMT

Hi, I did some more testing and I can see the same current consumption here with the prj.conf changes you are using. There is no need to patch the SLM application as indicated in my first reply.

When you reset the chip, it starts up in system OFF mode, which has the lowest current consumption, because nothing is running on the chip.

Then after you wake up and go back to sleep using AT#XSLEEP you can choose between going back to system OFF again (AT#XSLEEP=1) or continue in system ON idle mode (AT#XSLEEP=2), which will keep the application RAM retention, application RTC running (and the modem connected if initialized):

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/serial_lte_modem/doc/Generic_AT_commands.html#id8

The expected current consumption for system OFF is 1.4 uA, and for system ON idle you have 2.2 uA:

https://infocenter.nordicsemi.com/topic/ps_nrf9160/_tmp/alta.nRF9160/autodita/CURRENT/parameters.id_current_sleep.html?cp=2_0_0_4_5_0_1

I can see that you enable modem trace in the prj.conf file, CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y. This will consume an additional 10-20 uA. If you set this to =n you should see around 2.2 uA after calling AT#XSLEEP=2.

Best regards,
Stian

RE: nRF9160/SLM sleep power consumption increases ~20uA after wakekup and AT#XSLEEP=2

Michal Mühlpachr — Fri, 26 Aug 2022 16:41:25 GMT

Do you mean, the https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/serial_lte_modem/README.html require fix ?

Regards,
Michal

RE: nRF9160/SLM sleep power consumption increases ~20uA after wakekup and AT#XSLEEP=2

Stian Røed Hafskjold — Fri, 26 Aug 2022 15:25:00 GMT

Hello, I have not been able to test this yet, but I'm suspecting that you need to add the wakeup pin to the edge sense mask. The pin interrupts are configured to use the GPIOTE IN event by default, which will consume more current. The alternative is to use the GPIO SENSE event (GPIOTE PORT). The way to configure the GPIO to use the sense event has changed in recent versions of the nRF Connect SDK. You can read the documentation here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/build/dts/api/bindings/gpio/nordic,nrf-gpio.html?highlight=sense%20edge%20mask

or check out my answer here: RE: nRF9160: LIS2DW12 high current consumption

Best regards,
Stian