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?
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?
be nice to have 'edit' feature to fix title for the ticket creator as I've had some challenges submitting tickets in DevZone
Hi,
DWater said:be nice to have 'edit' feature to fix title for the ticket creator as I've had some challenges submitting tickets in DevZone
Please make another separate ticket, explain your challenges when submitting tickets and elaborate on your feature request.
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?
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
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
how do I enable modem trace?
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
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.
trace-2025-08-07T10-58-17.935Z.mtrace
Thank you and appreciate your support!
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
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
Hi Dejan,
Appreciate your help. This ticket can be closed.
