nRF Cloud Assisted GNSS - Command sequence

RE: nRF Cloud Assisted GNSS - Command sequence

Pascal Hdz — Wed, 08 Apr 2026 08:09:07 GMT

I'm closing this ticket due lack of response. Please open a new ticket in case you have new questions.

Pascal.

RE: nRF Cloud Assisted GNSS - Command sequence

Pascal Hdz — Fri, 27 Mar 2026 09:20:26 GMT

Hello Andrew,

Do you need further assistance with this issue or could we close it?

Regards,

Pascal.

RE: nRF Cloud Assisted GNSS - Command sequence

Pascal Hdz — Tue, 24 Feb 2026 08:56:13 GMT

Hello Andrew,

I would recommend you to use our Location sample as a starting point. It uses the Location library which handles what you are trying to achieve.

https://github.com/nrfconnect/sdk-nrf/tree/main/samples/cellular/location

Regards,

Pascal.

RE: nRF Cloud Assisted GNSS - Command sequence

andychess — Tue, 16 Dec 2025 08:00:34 GMT

Hi Benjamin,

Thanks for your response. The specific problem that I have, is that if I use a 1000 ms delay in the polling loop below, I generally receive both agnss mqtt packets. However, if I shorten the the delay to 100ms then only one packet is received and agnss fails.

You can see the two packets being received in the log above. This is the effect of shortening the polling delay.

while (nrf_cloud_agnss_request_in_progress()) {
if (k_uptime_delta(&startTime) > timeoutMs) {
LOG_WRN("A-GNSS request timeout!");
break;
}
k_sleep(K_MSEC(100));
}

[00:00:27.359,039] <inf> location: A-GNSS request sent, waiting for processing...
[00:00:27.786,163] <dbg> nrf_cloud_transport: nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 1000 result = 0
[00:00:28.079,895] <dbg> nrf_cloud_transport: nct_mqtt_evt_handler: MQTT_EVT_PUBLISH: id = 1 len = 1517, topic = prod/71efa182-08ee-4647-b702-afa3cb32e6c0/m/d/5034474b-3731-4b68-80d9-0e234ccfe0f0/agnss/r
[00:00:28.159,851] <inf> location: Disconnecting from nRF Cloud...
[00:00:28.159,881] <dbg> nrf_cloud_transport: nct_disconnect: Disconnecting
[00:00:28.166,351] <dbg> nrf_cloud_transport: nct_mqtt_evt_handler: MQTT_EVT_DISCONNECT: result = 0
[00:00:28.166,351] <dbg> nrf_cloud: nfsm_set_current_state_and_notify: state: 1
[00:00:28.166,381] <inf> location: >>> Cloud event: type=415500, status=0 <<<
[00:00:28.166,381] <inf> location: Nrf Cloud disconnected.
[00:00:28.166,412] <inf> location: Disconnected from Nrf Cloud.
[00:00:28.166,412]

The 1000ms delay is generally enough but makes the loop fairly pointless since on at least one occasion there was an unusual delay and the second packet was missed even with the 1000ms loop delay..

Additionally, I am allowing 1 sec delay for the modem to stabilise after the agnss download, but have no idea whether this is strictly required. The combined effect is adding 2 secs to TTFF and doesn't appear to be 100% reliable.

SDK is 3.1.0, modem firmware 2.0.3.

RE: nRF Cloud Assisted GNSS - Command sequence

Benjamin — Mon, 15 Dec 2025 13:24:42 GMT

Hi Andy,

Using nrf_cloud_agnss_request_in_progress() to check whether you are waiting for a request response is correct. It returns false after the data has been received, but before it is sent to the modem. When it returns false, it is safe to turn off LTE and disconnect from nRF Cloud. This does not take the double MQTT issue into account yet. I need to investigate that part further.

What SDK version are you using?

What exact issue are you seeing when running your application?

Regards,
Benjamin