Nrf9160 not setting requested active time

RE: Nrf9160 not setting requested active time

Albrecht Markus Schellenberger — Tue, 10 May 2022 03:50:51 GMT

Hello Pieter,

[quote user="PieterK"]Here is my terminal log and my trace file[/quote]

thanks a lot! Now that looks a lot better :-)

[quote user="PieterK"]Now we just need to sort out this issue of the modem not entering idle then we have a very low power solution[/quote]

Here is my analysis. Please note that the timestamps do not completely match your application log:

At 12:55:11.80, the modem reports that the connection to the network is established.

12:55:11.808127 M4 TRACE_GROUP_UNASSIGNED L23_AT_STRING AT_STRING <= +CEREG: 1,"5209","09A53917",9,,,"00000000","10010100"\r\n

This as a consequence of completed network attach request at 12:55:11.68:

At 12:56:12.15, the modem reports that it has entered PSM:

12:56:12.153189 M4 TRACE_GROUP_UNASSIGNED L23_AT_STRING AT_STRING <= %CESQ: 255,0,255,0\r\n
12:56:12.154562 M4 TRACE_GROUP_UNASSIGNED L23_AT_STRING AT_STRING <= %XMODEMSLEEP: 1,599999\r\n

This as a result of that the network has released RRC at 12:56:12.03:

Hence, the modem enters PSM immediately after it has been released from the network. There is no <Active Time> here in between. The 60s delay comes from the network not releasing RRC earlier. You should be able to confirm that by requesting a different <Active Time>. The modem should then enter PSM after <Active Time> + 60s offset. I do not have that much experience with NB-IoT networks, since they are not available here. But this behaviour might plausibly be common.

Regards,

Markus

RE: Nrf9160 not setting requested active time

PieterK — Mon, 09 May 2022 10:37:39 GMT

Good day Markus.

Here is my terminal log and my trace file

(12:32:24.629) AT+CFUN=0
 (11)
(12:32:24.856) 
 (2)
(12:32:24.874) OK
 (4)
(12:32:27.491) AT%XMODEMTRACE=1,2
 (20)
(12:32:27.600) 
 (2)
(12:32:27.616) OK
 (4)
(12:32:28.973) AT+CEREG=5
 (12)
(12:32:29.054) 
 (2)
(12:32:29.054) OK
 (4)
(12:32:30.083) AT%CESQ=1
 (11)
(12:32:30.157) 
 (2)
(12:32:30.157) OK
 (4)
(12:32:31.151) AT%XMODEMSLEEP=1,1000,60000
 (29)
(12:32:31.292) 
 (2)
(12:32:31.308) OK
 (4)
(12:32:31.324) 
 (2)
(12:32:31.324) %XMODEMSLEEP: 4
 (17)
(12:32:32.465) AT+CFUN=1
 (11)
(12:32:32.586) 
 (2)
(12:32:32.604) OK
 (4)
(12:32:32.626) 
 (2)
(12:32:32.647) %XMODEMSLEEP: 4,0
 (19)
(12:32:35.734) 
 (2)
(12:32:35.782) %CESQ: 43,2,27,3
 (18)
(12:32:35.857) 
 (2)
(12:32:35.882) +CEREG: 2,"5209","09A53917",9
 (31)
(12:32:38.325) 
 (2)
(12:32:38.325) +CEREG: 1,"5209","09A53917",9,,,"00000000","10010100"
 (55)
(12:33:38.673) 
 (2)
(12:33:38.700) %CESQ: 255,0,255,0
 (20)
(12:33:38.783) 
 (2)
(12:33:38.813) %XMODEMSLEEP: 1,599999
 (24)

devzone.nordicsemi.com/.../trace_2D00_2022_2D00_05_2D00_09T10_2D00_32_2D00_20.907Z.bin

RE: Nrf9160 not setting requested active time

Albrecht Markus Schellenberger — Mon, 09 May 2022 10:15:56 GMT

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

RE: Nrf9160 not setting requested active time

Albrecht Markus Schellenberger — Fri, 06 May 2022 14:27:56 GMT

Hello Pieter,

Some feedback from my side:

[quote user="PieterK"]I did the trace up until %modemsleep came back with the unsolicited repl[/quote]

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

RE: Nrf9160 not setting requested active time

PieterK — Thu, 05 May 2022 10:35:05 GMT

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)

devzone.nordicsemi.com/.../trace_2D00_2022_2D00_05_2D00_05T10_2D00_29_2D00_57.423Z.bin

RE: Nrf9160 not setting requested active time

Albrecht Markus Schellenberger — Thu, 05 May 2022 08:52:01 GMT

[quote user="PieterK"]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.[/quote]

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

RE: Nrf9160 not setting requested active time

PieterK — Thu, 05 May 2022 08:45:19 GMT

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.

RE: Nrf9160 not setting requested active time

Albrecht Markus Schellenberger — Thu, 05 May 2022 08:37:11 GMT

Hello Pieter,

[quote user="PieterK"]We are just looking for a way to make the device go into idle (Keeping the IP connection) without having to wait 60 seconds after for the device to go into low power[/quote]

My bad! Looking one more time at the time stamps, I now see that there is a 60s delay between:

(11:00:12.926) +CEREG: 1,"5209","09A53917",9,,,"00000000","10010100"

and

(11:01:13.267) %CESQ: 255,0,255,0

My apologies for overlooking that!

I actually might need a modem trace here to get some more details around what the modem is reporting internally. You can follow this guide to do so, but I would recommend you to use Trace Collector V2 preview instead.

Thanks & regards,

Markus

RE: Nrf9160 not setting requested active time

PieterK — Thu, 05 May 2022 08:21:21 GMT

Good day.

The 60 seconds will happen when the device has only been connected to the NB-IOT networks. By the time we issue the sleep command we are already disconnected from the MQTT broker.

We are just looking for a way to make the device go into idle (Keeping the IP connection) without having to wait 60 seconds after for the device to go into low power

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

I was following these steps to try and get the device enter the low power mode immediately. Those 60 seconds of high power consumptions is something we cannot handle. The device entering idle is taking more battery consumption that what our MQTT cycles are using.

We would like to be able to idle keeping our IP connection to just connect to the broker ,publish, disconnect and enter idle.

RE: Nrf9160 not setting requested active time

Albrecht Markus Schellenberger — Thu, 05 May 2022 08:08:01 GMT

Hello Pieter,

[quote user="PieterK"]

My main concern is that in these 60 seconds before going to low power we are consuming weeks worth of power. The nrf9160 modem consumes 20ma for these 60 seconds.

Can we cut down the 60 seconds as we have battery powered applications and we cannot afford that most of our power consumption is used by the modem after we are already finished.

Our MQTT cycles last about 15 seconds.

[/quote]

I’m not sure if I can follow you here. Since the modem goes to PSM immediately, those 60s your are mentioning can not have anything to do with <Active Time> or PSM, unless the modem remains in RRC connected state (e.g. because of active MQTT transmission).

Otherwise, we are probably talking about Power Management of the application core or specifically Power saving for the SLM, which is a different thing as the modem is operating on a separate core.

Regards,

Markus

RE: Nrf9160 not setting requested active time

PieterK — Thu, 05 May 2022 06:06:05 GMT

Good day.

Yes this is correct. Both At Client and the SLM do the same steps. Both enter idle after we issue idle command.

My main concern is that in these 60 seconds before going to low power we are consuming weeks worth of power. The nrf9160 modem consumes 20ma for these 60 seconds.

Can we cut down the 60 seconds as we have battery powered applications and we cannot afford that most of our power consumption is used by the modem after we are already finished.

Our MQTT cycles last about 15 seconds.

RE: Nrf9160 not setting requested active time

Albrecht Markus Schellenberger — Thu, 05 May 2022 05:55:16 GMT

[quote user="PieterK"]Thank you very much for all the help.[/quote]

My pleasure, Pieter! I’m glad I can help :-)

[quote user="PieterK"]Here is the steps I took according to your steps.[/quote]

What I can see in the log is that the modem:

(11:00:12.926) +CEREG: 1,"5209","09A53917",9,,,"00000000","10010100"

Successfully establishes a connection to the network.

(11:01:13.267) %CESQ: 255,0,255,0

Releases the active session and goes into idle. The delay from RRC connected to RRC idle is network specific and can not be affected by the UE.

(11:01:13.304) %XMODEMSLEEP: 1,599999

Is entering sleep mode directly afterwards.

Hence, the nRF9160 goes into PSM as soon as possible, which also is < 60s and that looks correct to me. If you perform the same steps with the Serial LTE modem application, do you get a similar result?

Regards,

Markus

RE: Nrf9160 not setting requested active time

PieterK — Wed, 04 May 2022 09:03:00 GMT

Thank you very much for all the help.

I now understand the reason to use the AT-Client

Here is the steps I took according to your steps.

(10:59:20.948) *** Booting Zephyr OS build v2.7.0-ncs1  ***
 (46)
(10:59:20.956) I: Starting bootloader
 (24)
(10:59:20.956) I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
 (75)
(10:59:20.968) I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
 (77)
(10:59:20.978) I: Boot source: none
 (22)
(10:59:20.978) I: Swap type: none
 (20)
(10:59:21.021) I: Bootloader chainload address offset: 0x10000
 (49)
(10:59:21.031) I: Jumping to the first image slot
*** Booting Zephyr OS build v2.7.0-ncs1  ***
 (81)
(10:59:21.266) Flash regions		Domain		Permissions
 (36)
(10:59:21.266) 00 03 0x00000 0x20000 	Secure		rwxl
 (37)
(10:59:21.266) 04 31 0x20000 0x100000 	Non-Secure	rwxl
 (41)
(10:59:21.266) 
 (2)
(10:59:21.266) Non-secure callable region 0 placed in flash region 3 with size 32.
 (69)
(10:59:21.292) 
 (2)
(10:59:21.319) SRAM region		Domain		Permissions
 (34)
(10:59:21.332) 00 07 0x00000 0x10000 	Secure		rwxl
 (37)
(10:59:21.332) 08 31 0x10000 0x40000 	Non-Secure	rwxl
 (40)
(10:59:21.332) 
 (2)
(10:59:21.332) Peripheral		Domain		Status
 (28)
(10:59:21.332) 00 NRF_P0               Non-Secure	OK
 (39)
(10:59:21.356) 01 NRF_CLOCK            Non-Secure	OK
 (39)
(10:59:21.356) 02 NRF_RTC0             Non-Secure	OK
 (39)
(10:59:21.356) 03 NRF_RTC1             Non-Secure	OK
 (39)
(10:59:21.356) 04 NRF_NVMC             Non-Secure	OK
 (39)
(10:59:21.356) 05 NRF_UARTE1           Non-Secure	OK
 (39)
(10:59:21.356) 06 NRF_UARTE2           Secure		SKIP
 (38)
(10:59:21.356) 07 NRF_TWIM2            Non-Secure	OK
 (39)
(10:59:21.386) 08 NRF_SPIM3            Non-Secure	OK
 (39)
(10:59:21.386) 09 NRF_TIMER0           Non-Secure	OK
 (39)
(10:59:21.386) 10 NRF_TIMER1           Non-Secure	OK
 (39)
(10:59:21.386) 11 NRF_TIMER2           Non-Secure	OK
 (39)
(10:59:21.386) 12 NRF_SAADC            Non-Secure	OK
 (39)
(10:59:21.386) 13 NRF_PWM0             Non-Secure	OK
 (39)
(10:59:21.386) 14 NRF_PWM1             Non-Secure	OK
 (39)
(10:59:21.386) 15 NRF_PWM2             Non-Secure	OK
 (39)
(10:59:21.418) 16 NRF_PWM3             Non-Secure	OK
 (39)
(10:59:21.418) 17 NRF_WDT              Non-Secure	OK
 (39)
(10:59:21.418) 18 NRF_IPC              Non-Secure	OK
 (39)
(10:59:21.418) 19 NRF_VMC              Non-Secure	OK
 (39)
(10:59:21.418) 20 NRF_FPU              Non-Secure	OK
 (39)
(10:59:21.418) 21 NRF_EGU0             Non-Secure	OK
 (39)
(10:59:21.418) 22 NRF_EGU1             Non-Secure	OK
 (39)
(10:59:21.418) 23 NRF_EGU2             Non-Secure	OK
 (39)
(10:59:21.418) 24 NRF_EGU3             Non-Secure	OK
 (39)
(10:59:21.455) 25 NRF_EGU4             Non-Secure	OK
 (39)
(10:59:21.455) 26 NRF_EGU5             Non-Secure	OK
 (39)
(10:59:21.455) 27 NRF_DPPIC            Non-Secure	OK
 (39)
(10:59:21.455) 28 NRF_REGULATORS       Non-Secure	OK
 (39)
(10:59:21.455) 29 NRF_PDM              Non-Secure	OK
 (39)
(10:59:21.455) 30 NRF_I2S              Non-Secure	OK
 (39)
(10:59:21.455) 31 NRF_GPIOTE1          Non-Secure	OK
 (39)
(10:59:21.455) 
 (2)
(10:59:21.455) SPM: NS image at 0x20200
 (26)
(10:59:21.455) SPM: NS MSP at 0x200185f0
 (27)
(10:59:21.455) SPM: NS reset vector at 0x221e5
 (33)
(10:59:21.455) SPM: prepare to jump to Non-Secure image.
 (43)
(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)

RE: Nrf9160 not setting requested active time

Albrecht Markus Schellenberger — Wed, 04 May 2022 08:46:23 GMT

Hello Pieter,

[quote user="PieterK"]

I see that the MQTT commands all reply with error.

Would you possibly be able to assist me in getting the MQTT commands to work?

[/quote]

The MQTT AT commands below are SLM-specific, and can not be used with the AT Client.

But to analyse your initial problem with <Active Time>, the MQTT commands are not needed. It is just enough to perform the same steps as I did.

By the way, to make life a little bit easier for me: Could you please share the application log as text format, preferably using the Insert → Code functionality here in DevZone. Going through a log which is a picture, is a little bit of a pain in the back.

Thanks & regards,

Markus

RE: Nrf9160 not setting requested active time

PieterK — Wed, 04 May 2022 08:23:23 GMT

Good dy. I am looking at the AT-Client. I see that the MQTT commands all reply with error.

Would you possibly be able to assist me in getting the MQTT commands to work?

RE: Nrf9160 not setting requested active time

Albrecht Markus Schellenberger — Wed, 04 May 2022 08:15:23 GMT

Hello Pieter,

[quote user="PieterK"]

What is the major differences between the AT-client and the SLM?

Does the AT client also do power management on its own?

[/quote]

The AT Client is a simple program which can be used to send AT commands via UART from an external source to the modem.

The Serial LTE modem application basically provides the same functionality as the AT Client and can additionally be used as a stand-alone LTE modem on the nRF9160. Hence, the application itself supports a lot more features, like Power saving or other SLM-specific AT commands to enable certain functionality.

So you can perform the same steps below with the Serial LTE modem as well.

Regards,

Markus

RE: Nrf9160 not setting requested active time

PieterK — Wed, 04 May 2022 06:27:00 GMT

Hi Markus.

Thank you for the valuable insight. I will give this a try today.

What is the major differences between the AT-client and the SLM?

Does the AT client also do power management on its own?

RE: Nrf9160 not setting requested active time

Albrecht Markus Schellenberger — Tue, 03 May 2022 11:08:41 GMT

Hello Pieter,

first of all, my apologies for the delayed reply. I have been out of office for the last couple of days.

[quote user="PieterK"]

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.

[/quote]

No worries, we will do this step by step :-)

[quote user="PieterK"]I hope they have been done correctly, This is the first time that I use the trace tool.[/quote]

Unfortunately, something went wrong during the record, as I mostly see errors in the modem trace.

But we actually do not have to start with that, an application log should be enough for the moment. Below you can find an example from the AT Client, which I control using a serial terminal.

*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
The AT host sample started
AT+CEREG=5
OK
AT%CESQ=1
OK
AT%XMODEMSLEEP=1,1000,60000
%XMODEMSLEEP: 4
OK
AT+CFUN=1
%XMODEMSLEEP: 4,0
OK
%CESQ: 56,2,23,3
+CEREG: 2,"7AA9","01444000",7
+CEREG: 1,"7AA9","01444000",7,,,"00001010","11000001"
%CESQ: 255,0,255,0
%XMODEMSLEEP: 1,1151979975

Regards,

Markus

RE: Nrf9160 not setting requested active time

PieterK — Thu, 28 Apr 2022 11:08:40 GMT

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

devzone.nordicsemi.com/.../trace_2D00_2022_2D00_04_2D00_28T11_2D00_01_2D00_26.359Z.bin devzone.nordicsemi.com/.../2022_2D00_04_2D00_28T10_5F00_54_5F00_30.193Z_2D00_log.txt

RE: Nrf9160 not setting requested active time

Albrecht Markus Schellenberger — Thu, 28 Apr 2022 10:19:07 GMT

[quote user="PieterK"]Here is the response from the modem after giving the %XMONITOR command[/quote]

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

RE: Nrf9160 not setting requested active time

PieterK — Thu, 28 Apr 2022 05:23:49 GMT

Good Morning Markus.

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

RE: Nrf9160 not setting requested active time

Albrecht Markus Schellenberger — Wed, 27 Apr 2022 10:56:22 GMT

Hello Pieter,

[quote user=""]

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.

[/quote]

Could you please read the modem parameters using %XMONITOR and share its values? I wonder if the network has allowed your device to enter PSM.

Thanks & regards,

Markus