Nrf9160 not setting requested active time

[PieterK]

Good day I am wondering if you can help me.

For background information.

Network - NB-iot

Firmware -  1.3.1

Software - Serial LTE Modem

Hardware - nrf9160dk

I am trying to set the requested active time down so that when I go into idle to save power and keep my IP connection that the modem doesn't stay active for 60 seconds there after.

The device is going into low power mode but only after 60 seconds. 

I will attach a screen shot of the AT-commands that I take to get to the point where I'd like to go into low power but the Requested Active Time does not change.

I came across this following link while attempting to get my power consumption down.

(+) turn off active time and go directly to power save mode - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

I tried the command AT+CPSMS=1,"","","10101010","00000000" to set the periodic TAU to 10 minutes and the requested active time to 0 and to 2 (00000001) seconds.

But they had no influence on the 60 seconds of high power consumption after issuing the AT#XSLEEP=2 to put the system into idle.

If anyone has any input as to where I am going wrong I will greatly appreciate it.

[Albrecht Markus Schellenberger]

PieterK said:

Here is the response from the modem after giving the %XMONITOR command

Thanks a lot Pieter!

%XMONITOR values are looking good to me. The network accepts the request of 0s <Active-Time> and 10min <Periodic-Tau>. So I expect the device enter PSM immediately when coming to RRC idle.

Would you mind enabling %XMODEMSLEEP notifications and share a full application log (preferably in code text format)? It should notify the application when the modem actually enters PSM.

Regards,

Markus

[PieterK]

Good day here are the logs, I hope they have been done correctly, This is the first time that I use the trace tool.

If not please let me know then I will do it again.

I am very new to the nr9160 family but I am slowly getting the hang of it.

Kind Regards

Pieter

trace-2022-04-28T11-01-26.359Z.bin

Fullscreen 2022-04-28T10_54_30.193Z-log.txt Download

2022-04-28T10:54:30.770Z DEBUG Application data folder: C:\Users\Pieter\AppData\Roaming\nrfconnect\pc-nrfconnect-tracecollector
2022-04-28T10:54:30.837Z DEBUG App pc-nrfconnect-tracecollector v1.1.2 official
2022-04-28T10:54:30.838Z DEBUG App path: C:\Users\Pieter\.nrfconnect-apps\node_modules\pc-nrfconnect-tracecollector
2022-04-28T10:54:30.838Z DEBUG nRFConnect 3.11.0, required by the app is (^3.8.0)
2022-04-28T10:54:30.838Z DEBUG nRFConnect path: C:\Users\Pieter\AppData\Local\Programs\nrfconnect\resources\app.asar
2022-04-28T10:54:30.838Z DEBUG HomeDir: C:\Users\Pieter
2022-04-28T10:54:30.838Z DEBUG TmpDir: C:\Users\Pieter\AppData\Local\Temp
2022-04-28T10:54:30.841Z INFO Using nrf-device-lib-js version: 0.4.5
2022-04-28T10:54:30.841Z INFO Using nrf-device-lib version: 0.11.0
2022-04-28T10:54:30.841Z INFO Using nrfjprog DLL version: 10.15.1
2022-04-28T10:54:30.841Z INFO Using JLink version: JLink_V7.58b
2022-04-28T10:54:33.186Z INFO Device opened
2022-04-28T10:54:40.185Z INFO Device closed
2022-04-28T10:54:40.188Z INFO Device opened
2022-04-28T10:54:42.164Z INFO Tracefile created: C:\Users\Pieter\AppData\Roaming\nrfconnect\pc-nrfconnect-tracecollector\trace-2022-04-28T10-54-42.157Z.bin
2022-04-28T10:55:35.487Z INFO Tracefile closed
2022-04-28T10:59:07.146Z INFO Device closed
2022-04-28T10:59:07.148Z INFO Device opened
2022-04-28T11:01:26.361Z INFO Tracefile created: C:\Users\Pieter\AppData\Roaming\nrfconnect\pc-nrfconnect-tracecollector\trace-2022-04-28T11-01-26.359Z.bin
2022-04-28T11:02:55.591Z INFO Tracefile closed