SARA-R4/N4 series - AT Commands Manual
UBX-17003787 - R09
22 GNSS
Page 238 of 307
If the +ULOC command is sent while a prULOC activity is still in progress the previous activity is
aborted, the available position is immediately output and the next +ULOC request is served.
The data connection cannot be immediately dropped at the +ULOC timeout expiration. This could lead to
a delay in the expected response time.
Depending on the aiding chosen, a data connection could be required; see the
description.
If no position is available (no GNSS coverage, no network information and no previous data available) then
the <lat> latitude and <long> longitude will be set to '0'.
If the previous position degradated by the elapsed time satisfies the desired accuracy then the sensor '0'
is reported in the information text response.
If multi-hypothesis is required the GNSS solution and the CellLocate
®
solutions are reported, if available.
If no GNSS or CellLocate
®
solutions are present, the previous position degradated is used instead.
If multi-hypothesis is required but the sensor is set to GNSS (<sensor>=1), only one solution will be
provided: the GNSS one (or the previous position degradated if GNSS solution not available).
If a valid GNSS fix with an accuracy below the required value (<accuracy>) occurs before the end of the
network scan, the GNSS-only solution will be available, even if multi-hypothesis has been required.
22.16.2 Syntax
Type
Syntax
Response
Example
Set
AT+ULOC=<mode>,<sensor>,
<response_type>,<timeout>,
<accuracy>[,<num_hypothesis>]
OK
AT+ULOC=2,3,0,120,1
OK
Read
AT+ULOC?
+ULOC: <mode>,<sensor>,
<response_type>,<timeout>,
<accuracy>,<num_hypotesis>
OK
+ULOC: 2,3,1,0,20,0
OK
Test
AT+ULOC=?
+ULOC: (list of supported <mode>s),
(list of supported <sensor>s),(list
of supported <response_type>s),
(list of supported <timeout>s),(list
of supported <accuracy>s),(list of
supported <num_hypotesis>s)
OK
+ULOC: (0-2),(0-3),(0-2),(1-999),(1-
999999),(1-16)
OK
If <response_type>=0:
+UULOC: <date>,<time>,<lat>,
<long>,<alt>,<uncertainty>
+UULOC: 13/04/2011,09:54:51.000,
45.6334520,13.0618620,49,1
If <response_type>=1:
+UULOC: <date>,<time>,<lat>,
<long>,<alt>,<uncertainty>,
<speed>,<direction>,<vertical_
acc>,<sensor_used>,<SV_used>,
<antenna_status>,<jamming_
status>
+UULOC: 25/09/2013,10:13:29.000,
45.7140971,13.7409172,266,17,0,0,18,
1,6,3,9
If <response_type>=2, <sensor_
used>= 1 and <num_hypothesis>=N:
+UULOC: <sol>,<num>,<sensor_
used>,<date>,<time>,<lat>,
<long>,<alt>,<uncertainty>,
<speed>,<direction>,<vertical_acc>,
<SV_used>,<antenna_status>,
<jamming_status>
+UULOC: 1,2,1,08/04/2015,09:0
2:32.000,45.7141652,13.7410666,
266,47,0,0,40,3,0,0
URC
If <response_type>=2, <sensor_
used> = 2 and <num_hypothesis>=
N:
+UULOC: <sol>,<num>,<sensor_
used>,<date>,<time>,<lat>,<long>,
+UULOC: 2,2,2,08/04/2015,09:0
2:19.000,45.7140665,13.7411681,0,
45.7240260,13.7511276,113,10,0,50,
45.7240260,13.7511276,143,41,0,95
