Good afternoon, I have begun testing firmware version 4.6.8.0 primarily to take advantage of the new AGNSS functionality, and have noticed that the GNSSLOC? command no longer returns location coordinates
Firmware 3.7.2.3:
app: +GNSSEV: 3,3
app: AT+GNSSLOC?
app: +GNSSLOC:
app: Latitude: 45 Deg 15 Min 35.45 Sec N
app: Longitude: 75 Deg 25 Min 0.60 Sec W
app: GpsTime:
app: FixType: 3D
app: HEPE: 0.40 m
app: Altitude: 42.800 m
app: AltUnc: 0.0 m
app: Direction:
app: HorSpeed:
app: VerSpeed:
app:
app:
app: OK
app: AT+GNSSSTOP
Firmware 4.6.8.0:
app: +GNSSEV: 3,3
app: AT+GNSSLOC?
app: +GNSSLOC:
app: Latitude:
app: Longitude:
app: GpsTime:
app: FixType: 3D
app: HEPE:
app: Altitude:
app: AltUnc:
app: Direction:
app: HorSpeed:
app: VerSpeed:
app:
app:
app: OK
app: AT+GNSSSTOP
Is this a known issue and is there a version with working GNSSLOC and AGNSS?
I’m aware the location can still be read via NMEA but for our application we only need the latest position fix, so switching into NMEA stream mode requires extra time and complexity.
Hi @dominic,
I am trying your case on my HL7800-M module. Can you please provide the sequence commands that you used to get the location?
Thanks,
Hi, thanks for taking a look at this.
The relevant sequence of commands is:
AT+CREG=1
AT+CPSMS=1,“00111000”,“00000001”
// Open a socket to a mqtt broker, send a few messages
// Wait for PSM to disable cell modem
+CREG: 4
AT+GNSSSTART=0
// Wait for fix…
+GNSSEV: 3,3
AT+GNSSLOC?
… The rest is as seen in the first message
Hi @dominic,
I have just tried your scenario, my module can return location coordinates after sending the AT+GNSSLOC? command.
Please refer to below log:
15:35:32.690 on 02-Apr-2021> ATI3
15:35:34.393 on 02-Apr-2021>
15:35:34.409 on 02-Apr-2021> HL7800-M.4.6.8.0
15:35:34.409 on 02-Apr-2021>
15:35:34.409 on 02-Apr-2021> OK
15:35:34.409 on 02-Apr-2021> ATI8
15:35:38.647 on 02-Apr-2021>
15:35:38.648 on 02-Apr-2021> HL7800-M.4.6.8
15:35:38.648 on 02-Apr-2021>
15:35:38.648 on 02-Apr-2021> OK
15:35:38.648 on 02-Apr-2021> AT+CEREG?
15:35:42.015 on 02-Apr-2021>
15:35:42.015 on 02-Apr-2021> +CEREG: 4,5,“0006”,“01A2D101”,7
15:35:42.037 on 02-Apr-2021>
15:35:42.037 on 02-Apr-2021> OK
15:35:42.037 on 02-Apr-2021> AT+GNSSCONF?
15:35:53.501 on 02-Apr-2021>
15:35:53.501 on 02-Apr-2021> +GNSSCONF: 1,0
15:35:53.501 on 02-Apr-2021> +GNSSCONF: 10,0
15:35:53.501 on 02-Apr-2021> +GNSSCONF: 12,0
15:35:53.517 on 02-Apr-2021>
15:35:53.517 on 02-Apr-2021> OK
15:35:53.517 on 02-Apr-2021> AT+CPSMS=1,“00111000”,“00000001”
15:36:14.737 on 02-Apr-2021>
15:36:16.423 on 02-Apr-2021> OK
15:36:16.423 on 02-Apr-2021> AT+CPSMS?
15:36:17.420 on 02-Apr-2021>
15:36:17.420 on 02-Apr-2021> +CPSMS: 1,“11100000”,“11100000”,“00010110”,“00001110”
15:36:17.420 on 02-Apr-2021>
15:36:17.420 on 02-Apr-2021> OK
15:36:17.420 on 02-Apr-2021> AT+CEREG=4
15:36:20.176 on 02-Apr-2021>
15:36:20.176 on 02-Apr-2021> OK
15:36:20.176 on 02-Apr-2021> AT+CEREG?
15:36:35.779 on 02-Apr-2021>
15:36:35.779 on 02-Apr-2021> +CEREG: 4,5,“0006”,“01A2D101”,7,“00001110”,“00010110”
15:36:35.779 on 02-Apr-2021>
15:36:35.779 on 02-Apr-2021> OK
15:36:35.779 on 02-Apr-2021>
15:36:43.096 on 02-Apr-2021> +CEREG: 4,“00001110”,“00010110” //PSM disable as you said
15:36:43.096 on 02-Apr-2021> AT+GNSSSTART=0
15:36:52.321 on 02-Apr-2021>
15:36:52.321 on 02-Apr-2021> OK
15:36:52.321 on 02-Apr-2021>
15:36:52.321 on 02-Apr-2021> +GNSSEV: 0,1
15:36:52.321 on 02-Apr-2021>
15:36:52.623 on 02-Apr-2021> +GNSSEV: 1,1
15:36:52.623 on 02-Apr-2021>
15:36:55.411 on 02-Apr-2021> +GNSSEV: 3,0
15:36:55.411 on 02-Apr-2021>
15:37:32.775 on 02-Apr-2021> +GNSSEV: 3,3
15:37:32.775 on 02-Apr-2021> AT+GNSSLOC?
15:37:35.027 on 02-Apr-2021>
15:37:35.027 on 02-Apr-2021> +GNSSLOC:
15:37:35.027 on 02-Apr-2021> Latitude: 10 Deg 51 Min 19.52 Sec N
15:37:35.027 on 02-Apr-2021> Longitude: 106 Deg 37 Min 52.67 Sec E
15:37:35.027 on 02-Apr-2021> GpsTime: 2021 4 2 08:37:34
15:37:35.027 on 02-Apr-2021> FixType: 3D
15:37:35.027 on 02-Apr-2021> HEPE: 0.25 m
15:37:35.027 on 02-Apr-2021> Altitude: 143.100 m
15:37:35.027 on 02-Apr-2021> AltUnc: 0.0 m
15:37:35.027 on 02-Apr-2021> Direction:
15:37:35.027 on 02-Apr-2021> HorSpeed:
15:37:35.027 on 02-Apr-2021> VerSpeed:
15:37:35.027 on 02-Apr-2021>
15:37:35.027 on 02-Apr-2021>
15:37:35.027 on 02-Apr-2021> OK
15:37:35.028 on 02-Apr-2021>
So, have you seen this issue one time or many times?
a, If this issue has happened only one time, please check again.
b, If this issue has happened many times, please provide me the service you used to get location by sending command AT+GNSSCONF?
Thanks,
Thank you for testing this, I updated a few more devices to 4.6.8.0 and they report the location correctly via the GNSSLOC? command. I’m not sure if the airvantage delta files were updated, unfortunately I don’t have access to the original devices to see if the problem still exists on those.
You can close this issue for now, I will comment if it shows up again.