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.

[PieterK]

Good day.

Thanks Markus.

I will attach my dev kit to the nrf52832 and let the device run over night this evening and I will firstly test the traces before I let it run.

[Albrecht Markus Schellenberger]

PieterK said:

I will attach my dev kit to the nrf52832 and let the device run over night this evening and I will firstly test the traces before I let it run.

To start with, it should be enough to record the steps below, which should go quite fast.

(10:59:21.658) *** Booting Zephyr OS build v2.7.0-ncs1  ***
 (46)
(10:59:21.702) The AT host sample started
 (28)
(10:59:31.904) AT+CEREG=5
 (12)
(10:59:31.990) OK
 (4)
(10:59:39.021) AT%CESQ=1
 (11)
(10:59:39.075) OK
 (4)
(10:59:48.760) AT%XMODEMSLEEP=1,1000,60000
 (29)
(10:59:48.842) %XMODEMSLEEP: 4
 (17)
(10:59:48.842) OK
 (4)
(10:59:55.141) AT+CFUN=1
 (11)
(10:59:55.225) %XMODEMSLEEP: 4,0
 (19)
(10:59:55.225) OK
 (4)
(10:59:57.882) %CESQ: 40,2,27,3
 (18)
(10:59:57.922) +CEREG: 2,"5209","09A53917",9
 (31)
(11:00:00.414) %CESQ: 41,2,22,3
 (18)
(11:00:10.312) %CESQ: 39,1,28,4
 (18)
(11:00:12.926) +CEREG: 1,"5209","09A53917",9,,,"00000000","10010100"
 (55)
(11:01:13.267) %CESQ: 255,0,255,0
 (20)
(11:01:13.304) %XMODEMSLEEP: 1,599999
 (24)

So you do not have to let your device run over night :-)

Regards,

Markus

[PieterK]

Hi there. Sorry I took so long.

We have a on site test that started today with the nrf9160 and they are preforming well from what I can see. Now we just need to sort out this issue of the modem not entering idle then we have a very low power solution

I did the trace up until %modemsleep came back with the unsolicited reply.

Hope this gives us more insight into the problem

(12:30:02.759) AT+CEREG=5
 (12)
(12:30:02.838) 
 (2)
(12:30:02.838) OK
 (4)
(12:30:08.694) AT%CESQ=1
 (11)
(12:30:08.769) 
 (2)
(12:30:08.769) OK
 (4)
(12:30:13.290) AT%XMODEMSLEEP=1,1000,60000
 (29)
(12:30:13.439) 
 (2)
(12:30:13.439) OK
 (4)
(12:30:13.454) 
 (2)
(12:30:13.470) %XMODEMSLEEP: 4
 (17)
(12:30:15.053) AT+CFUN=1
 (11)
(12:30:15.149) 
 (2)
(12:30:15.149) OK
 (4)
(12:30:15.165) 
 (2)
(12:30:15.181) %XMODEMSLEEP: 4,0
 (19)
(12:30:18.076) 
 (2)
(12:30:18.076) %CESQ: 33,1,28,4
 (18)
(12:30:18.156) 
 (2)
(12:30:18.175) +CEREG: 2,"5209","09A53917",9
 (31)
(12:30:18.827) 
 (2)
(12:30:18.827) %CESQ: 27,1,22,3
 (18)
(12:30:30.932) 
 (2)
(12:30:30.956) %CESQ: 32,1,28,4
 (18)
(12:30:31.619) 
 (2)
(12:30:31.637) %CESQ: 30,1,23,3
 (18)
(12:30:33.651) 
 (2)
(12:30:33.672) +CEREG: 1,"5209","09A53917",9,,,"00000000","10010100"
 (55)
(12:30:46.236) 
 (2)
(12:30:46.236) %CESQ: 32,1,28,4
 (18)
(12:30:48.458) 
 (2)
(12:30:48.483) %CESQ: 30,1,23,3
 (18)
(12:30:52.520) 
 (2)
(12:30:52.559) %CESQ: 27,1,16,2
 (18)
(12:30:54.135) 
 (2)
(12:30:54.164) %CESQ: 28,1,22,3
 (18)
(12:31:08.527) 
 (2)
(12:31:08.559) %CESQ: 33,1,27,3
 (18)
(12:31:14.204) 
 (2)
(12:31:14.204) %CESQ: 28,1,24,3
 (18)
(12:31:15.019) 
 (2)
(12:31:15.019) %CESQ: 24,1,16,2
 (18)
(12:31:15.819) 
 (2)
(12:31:15.848) %CESQ: 27,1,21,3
 (18)
(12:31:16.426) 
 (2)
(12:31:16.456) %CESQ: 30,1,26,3
 (18)
(12:31:28.996) 
 (2)
(12:31:29.034) %CESQ: 25,1,18,2
 (18)
(12:31:30.003) 
 (2)
(12:31:30.037) %CESQ: 28,1,23,3
 (18)
(12:31:34.081) 
 (2)
(12:31:34.117) %CESQ: 255,0,255,0
 (20)
(12:31:34.188) 
 (2)
(12:31:34.236) %XMODEMSLEEP: 1,599999
 (24)

trace-2022-05-05T10-29-57.423Z.bin

[Albrecht Markus Schellenberger]

Hello Pieter,

Some feedback from my side:

PieterK said:

I did the trace up until %modemsleep came back with the unsolicited repl

The modem trace you recorded is still not good, but I’m facing the same problem on one of my DKs as well. I need to investigate this a little. I will come back to you as soon as I know more.

Have a great weekend!

Cheers,

Markus

[Albrecht Markus Schellenberger]

Hello again Pieter,

would you mind recording the trace one more time? But before that, please execute the following command when the modem is switched off (AT+CFUN=0):

AT%XMODEMTRACE=1,2

Thanks & regards,

Markus