"

RE: "

DWater — Fri, 08 Aug 2025 18:35:17 GMT

Hi Dejan,

Appreciate your help. This ticket can be closed.

RE: "

dejans — Fri, 08 Aug 2025 12:56:03 GMT

Hi,

From the perspective of application and network behavior, everything is working as it should. The warning you see comes from Location library. The requesting of PSM active time works such that device requests a value and network decides and reports the given value. Now that device requests too small value of 8s, network gives something that is a lot more, in this case 180s (3min). Can you try to request bigger value, for example 60 seconds and see if this helps? This could potentially help in getting rid of the warning and more importantly, let the modem go to PSM quicker.
You should subscribe to notifications using AT+CEREG=5 and AT%MDMEV=1 before AT+CFUN=1.
This might be intentional, but you can double check if you want your application to connect to udp-echo.nordicsemi.academy.

Best regards,
Dejan

RE: "

DWater — Thu, 07 Aug 2025 11:15:20 GMT

Hi Dejan,

I have added .mtrace file. The instance of "<wrn> location: PSM is configured, but modem did not enter PSM in 2 minutes. Starting GNSS anyway." is around 1:44 minutes into the start.

devzone.nordicsemi.com/.../trace_2D00_2025_2D00_08_2D00_07T10_2D00_58_2D00_17.935Z.mtrace

Thank you and appreciate your support!

RE: "

dejans — Wed, 06 Aug 2025 14:58:06 GMT

Hi,

Have a look at these documentation links:
capturing modem trace
debugging with modem trace
modem tracing with UART snippets
modem trace module
modem trace activation
capturing modem trace

Best regards,
Dejan

RE: "

DWater — Wed, 06 Aug 2025 12:20:11 GMT

how do I enable modem trace?

RE: "

dejans — Wed, 06 Aug 2025 09:37:27 GMT

Hi,

The warning seems to be normal given the parameters, i.e. active time 180 seconds. When A-GNSS is not used, location library waits for the device to get to PSM before starting GNSS because getting a fix without A-GNSS and not being in PSM is unlikely. In your case, there might be some other activity that blocks PSM. Modem trace could potentially provide more information on what is blocking PSM.

Best regards,
Dejan

RE: "

DWater — Tue, 05 Aug 2025 12:40:49 GMT

NOTE 1: The location timeout is as expected since I am collecting this log while inside a building.

NOTE 2: see time [00:02:23.381,591]

[00:00:00.669,464] <inf> PWLS: Connecting to LTE network
[00:00:00.669,525] <inf> PWLS: Register GPS callback function
[00:00:00.669,525] <inf> PWLS: GpsInit()
%XMODEMSLEEP: 4
%XMODEMSLEEP: 4,0
+CEREG: 2,"6A25","08111911",7
[00:00:02.913,452] <inf> PWLS: NOT CONNECTED
+CSCON: 1
[00:00:06.818,023] <inf> PWLS: RRC mode: Connected
+CEREG: 5,"6A25","08111911",7,,,"00100011","11100000"
[00:00:08.607,330] <inf> PWLS: Network registration status: Connected - roaming
[00:00:08.607,421] <inf> PWLS: LTE CONNECTED...
[00:00:08.607,452] <inf> PWLS: COMMS - while(1)
+CEDRXP: 4,"1001","1001","0001"
[00:00:08.707,336] <inf> PWLS: LTE_LC_EVT_EDRX_UPDATE: 7
%XTIME: "0A","5280502123100A","01"
[00:00:08.807,800] <inf> PWLS: CommsDateTimeEvtHandler()
[00:00:08.807,830] <inf> PWLS: Local time: 1754397121000
[00:00:08.808,227] <inf> PWLS: LTE_LC_EVT_PSM_UPDATE: tau: 1800, active_time: 180
+CSCON: 0
[00:00:11.083,099] <inf> PWLS: RRC mode: Idle
%XMODEMSLEEP: 2,143312
[00:00:21.367,889] <inf> PWLS: IOButtonPressedISR(): ioPins: 0x00040000, Value: 0x0C080300, AND: 0x00000000
[00:00:21.367,919] <inf> PWLS: TimerStart(), 0x00040000
[00:00:21.367,950] <inf> PWLS: TEST_BUTTON
[00:00:23.367,980] <inf> PWLS: ISR: Test Button Timer Expired
[00:00:23.368,041] <inf> PWLS: EVENT: 18
[00:00:23.368,072] <inf> PWLS: GpsLocationGet()
[00:00:23.377,319] <inf> PWLS: Requesting GNSS location, 4 min timeout
[00:00:24.994,995] <inf> PWLS: IOButtonPressedISR(): ioPins: 0x00040000, Value: 0x0C0C0300, AND: 0x00040000
[00:00:24.995,025] <inf> PWLS: TimerStop(), 0x00040000
[00:00:24.995,025] <inf> PWLS: TEST_BUTTON
[00:02:23.381,591] <wrn> location: PSM is configured, but modem did not enter PSM in 2 minutes. Starting GNSS anyway.
%XMODEMSLEEP: 5,0
%XMODEMSLEEP: 2,0
[00:05:00.402,984] <inf> PWLS: uptime: 300
[00:05:23.377,563] <inf> location: Timeout for entire location request expired
[00:05:23.377,593] <wrn> location: GNSS timed out possibly due to too short GNSS time windows
[00:05:23.378,021] <inf> PWLS: location_event_handler()
[00:05:23.378,021] <inf> PWLS: Getting location timed out

%XMODEMSLEEP: 1,1487600
[00:05:23.497,467] <inf> PWLS: LTE params: err: 0, mcc: 310, mnc: 410, band: 12, snr: 28, rsrp: 48, rsrq: 20
[00:05:23.497,528] <inf> PWLS: Network Status: Connected - ROAMING
[00:05:23.497,528] <inf> PWLS: ServerResolve()
%XMODEMSLEEP: 1,0
+CSCON: 1
[00:05:23.882,720] <inf> PWLS: RRC mode: Connected
[00:05:24.714,050] <inf> PWLS: IPv4 Address found 20.82.16.164
[00:05:24.714,080] <inf> PWLS: ServerConnect()
[00:05:24.714,721] <inf> PWLS: ServerConnect() - Successfully connected to s_server
[00:05:24.714,752] <inf> PWLS: dateTime: 1754397436906
[00:05:24.714,782] <inf> PWLS: Length: 52
Message: [00:05:24.715,667] <inf> PWLS: CommsMsgSend(): msg: 00.01.00.01.0A.54.45.53.54.20.31.32.33.34.35.02.01.12.03.08.EA.6B.3C.7A.98.01.00.00.04.01.32.05.06.36.01.9A.01.30.00.06.01.28., len: 126
[00:05:24.716,247] <inf> PWLS: token: 0x0000C079
[00:05:24.716,278] <inf> PWLS: CoAP packet: 0x62 0x03 0x9C 0xBE 0x79 0xC0 0x01 0x20
[00:05:24.716,339] <inf> PWLS: Request: hrd: 6 max:200 off: 9 Olen: 2 delta: 12 data: by
[00:05:24.716,400] <inf> PWLS: View CoAP Packet
[00:05:24.716,400] <inf> PWLS: CoAP PUT request sent: Token 0xC079

[00:05:24.717,254] <inf> PWLS: Successfully sent message
[00:05:24.717,254] <inf> PWLS: CommsMsgReceive()
[00:05:25.175,201] <inf> PWLS: Data received from the s_server: len: 161, msg: (Time: 2025-08-05 12:37:18 Message: 00.01.00.01.0A.54.45.53.54.20.31.32.33.34.35.02.01.12.03.08.EA.6B.3C.7A.98.01.00.00.04.01.32.05.06.36.01.9A.01.30.00.06.01.28.)
[00:05:25.175,262] <inf> PWLS: COMMS - while(1)
+CSCON: 0
[00:05:28.614,868] <inf> PWLS: RRC mode: Idle
%XMODEMSLEEP: 2,153452

RE: "

dejans — Tue, 05 Aug 2025 10:12:30 GMT

Hi,

Can you show your complete application log?

Best regards,
Dejan

RE: "

DWater — Tue, 05 Aug 2025 00:23:41 GMT

I see the warning almost every time I request GNSS position.

It is based on 'Cellular IoT Fundamentals', Lesson 6 - Exercise 2, thought there are some modifications related to my application.

CONFIG_LTE_LC_EDRX_MODULE=y

CONFIG_LTE_LC_PSM_MODULE=y

CONFIG_LTE_PSM_REQ=y

CONFIG_LTE_EDRX_REQ=y

# Request PSM active time of 8 seconds.

CONFIG_LTE_PSM_REQ_RAT="00000100"

RE: "

dejans — Mon, 04 Aug 2025 15:35:31 GMT

Hi,

Can you provide more information about your application? Is it based on any of existing samples?

Can you show your PSM configuration?

[quote user=""]I often see the following warning when requesting a GNSS location: "<wrn> location: PSM is configured, but modem did not enter PSM in 2 minutes. Starting GNSS anyway."[/quote]

How often do you see this warning?

Best regards,
Dejan

RE: "

DWater — Mon, 04 Aug 2025 14:27:44 GMT

same application, same network (Conexa SIM roaming on AT&T network). Cell info:

LTE params: mcc: 310, mnc: 410, band: 12, snr: 16, rsrp: 37, rsrq: 3

RE: "

dejans — Mon, 04 Aug 2025 12:50:26 GMT

Hi,

[quote user="DWater"]be nice to have 'edit' feature to fix title for the ticket creator as I've had some challenges submitting tickets in DevZone[/quote]

Please make another separate ticket, explain your challenges when submitting tickets and elaborate on your feature request.

[quote user=""]I often see the following warning when requesting a GNSS location: "<wrn> location: PSM is configured, but modem did not enter PSM in 2 minutes. Starting GNSS anyway." - what is this warning? Is this a setup issue or expected behavior?[/quote]

Does this happen using the same application and on the same network? What are network conditions?
You can read about PSM usage in the documentation.

Best regards,
Dejan

RE: "

DWater — Fri, 01 Aug 2025 12:55:56 GMT

be nice to have 'edit' feature to fix title for the ticket creator as I've had some challenges submitting tickets in DevZone