- Support portal
- Evaluation Kits and partner products
u-blox Support
- Product documentation
Documentation
- About
- Sustainability
- Partners and Alliances
- Contact
About u-blox
- Investor relations
Investor relations
+UGSRV | ||||||
Modules | LEXI-R10401D-00B LEXI-R10801D-00B | |||||
Attributes | Syntax | PIN required | Settings saved | Can be aborted | Response time | Error reference |
partial | No | No | - |
Configures the network connection to a Multi GNSS Assistance (MGA) server used also per CellLocate. The configuration is saved in NVM and applied at the next GNSS power cycle or next CellLocate request. By default, the cellular module connects to u-blox’ primary MGA server; if the connection fails then the cellular module connects to u-blox’ secondary MGA server. The set command registers a token for gathering assistance data from MGA servers.
Setting up an internet connection and network registration is not part of this command and must be handled by the user separately to this command.
If not specified, the <cid> parameter set by means of the +UDCONF=19 AT command is used.
See +CGACT AT command for activating a PDP context.
For more details about Multi GNSS Assistance (MGA) feature, see to AssistNow services.
Type | Syntax | Response | Example |
---|---|---|---|
Set | AT+UGSRV=[<mga_primary_server>],[<mga_secondary_server>],<auth_token>[,<days>[,<period>[,<resolution>[,<GNSS_types>[,<mode>[,<datatype>[,<cid>]]]]]]] | OK | AT+UGSRV="cell-live1.services.u-blox.com","cell-live2.services.u-blox.com","123456789abcdefghijklm",14,4,1,65,0,1,1 OK |
Read | AT+UGSRV? | +UGSRV: <mga_primary_server>,<mga_secondary_server>,<auth_token>,<days>,<period>,<resolution>,<GNSS_types>,<mode>,<datatype>,<cid> OK | +UGSRV: "cell-live1.services.u-blox.com","cell-live2.services.u-blox.com","123456789abcdefghijklm",14,4,1,65,0,1,1 OK |
Test | AT+UGSRV=? | +UGSRV: <mga_primary_server>,<mga_secondary_server>,<auth_token>,(list of supported <days>s),(list of supported <period>s),(list of supported <resolution>s),(list of supported <GNSS_types>s),(list of supported <mode>s),(list of supported <datatype>s),(list of supported <cid>s) OK | +UGSRV: "srv1","srv2","token",(1,2,3,5,7,10,14),(1-5),(1-3),(1-77),(0-2),(0-15),(0,254) OK |
Parameter | Type | Description |
---|---|---|
<mga_primary_server> | String | Host name of the primary MGA server; the maximum length is 254 characters. Empty string is not allowed. If the primary MGA server is omitted, the current stored value is preserved.
|
<mga_secondary_server> | String | Host name of the secondary MGA server; the maximum length is 254 characters. Empty string is not allowed. The default and factory-programmed value is "cell-live2.services.u-blox.com". If the secondary MGA server is omitted, the current stored value is preserved. |
<auth_token> | String | Authentication Token for MGA server access. |
<days> | Number | The number of days into the future the Offline data for u-blox 7 and previous version should be valid for. The allowed values are: 1, 2, 3, 5, 7, 10 and 14. The default and factory-programmed value is 14. |
<period> | Number | The number of weeks into the future the Offline data for u-blox M8 should be valid for. The range of the allowed values goes from 1 to 5. The default and factory-programmed value is 4. |
<resolution> | Number | Resolution of offline data for u-blox M8. Allowed values:
|
<GNSS_types> | Number | Bitmask for combining the desired GNSS for the (offline) aiding
The default and factory-programmed value is GPS+GLONASS (65). If the parameter is omitted, the current stored value is preserved. Bitmask values:
|
<mode> | Number | Mode of operation of AssistNow Online data management
|
<datatype> | Number | Bitmask for combining the desired data types for the (online) aiding
The default and factory-programmed value is all aidings without filter on visible satellites (15) |
<cid> | Number | PDP context identifier. See <cid>. For more details on the default and factory-programmed value, see the command description. |
The <days>, <period>, <resolution>, <GNSS_types>, <mode> and <datatype> parameters have no effect.
+ULOC | ||||||
Modules | LEXI-R10401D-00B LEXI-R10801D-00B | |||||
Attributes | Syntax | PIN required | Settings saved | Can be aborted | Response time | Error reference |
full | No | No | No |
Requests cellular module to provide the location data; the location can be determined using the supported sensors such as:
GNSS receiver
CellLocate® (location based on network cells data)
SpotNow sensor (location based on GPS signal processed through cellular module)
Wi-Fi sensor (location based on nearby access points)
Combination of different technologies (hybrid)
A partial operation can also be performed by starting a scan of the cellular network and saving the data obtained in the file system. In this case, no position request is sent to the CellLocate service. The user’s application can separately forward the saved file to the CellLoLocate service to locate its own device.
The final result code indicates if sending the command request to the localization information process was successful or not. The URC is issued to provide the requested information via +ULOC set command.
To use simultaneously GNSS interface and CellLocate® where both are supported, the GNSS shall not be a sensor for +ULOC: if the GNSS sensor is reserved to another interface (e.g. +UGPS) and is selected as a sensor also for +ULOC, an error result code is provided (“+CME ERROR: GPS busy” if +CMEE: 2).
It is possible to configure the hybrid positioning through +ULOCGNSS and +ULOCCELL AT commands (if supported) even if it is running: the parameters are stored in NVM and will be applied at the next +ULOC command.
If the +ULOC command is sent while a previous +ULOC 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.
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, CellLocate® or SpotNow solutions are present, the previous position degradated is used instead.
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.
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-63),(0-2),(1-999),(1-999999),(1-16) OK |
URC | 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>,<response_source>,<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, <response_source>= 1 and <num_hypothesis>=N: +UULOC: <sol>,<num>,<response_source>,<date>,<time>,<lat>,<long>,<alt>,<uncertainty>,<speed>,<direction>,<vertical_acc>,<SV_used>,<antenna_status>,<jamming_status> | +UULOC: 1,2,1,08/04/2015,09:02:32.000,45.7141652,13.7410666,266,47,0,0,40,3,0,0 | ||
If <response_type>=2, <response_source> = 2 and <num_hypothesis>=N: +UULOC: <sol>,<num>,<response_source>,<date>,<time>,<lat>,<long>,<alt>,<lat50>,<long50>,<major50>,<minor50>,<orientation50>,<confidence50>[,<lat95>,<long95>,<major95>,<minor95>,<orientation95>,<confidence95>] | +UULOC: 2,2,2,08/04/2015,09:02:19.000,45.7140665,13.7411681,0,45.7240260,13.7511276,113,10,0,50,45.7240260,13.7511276,143,41,0,95 | ||
If <response_type>=2, <response_source>= 0: +UULOC: <sol>,<num>,<response_source>,<date>,<time>,<lat>,<long>,<alt>,<uncertainty> | +UULOC: 1,1,0,08/04/2015,09:03:45.000,45.7140290,13.7410695,0,32 |
Parameter | Type | Description |
---|---|---|
<mode> | Number | Allowed values:
|
<sensor> | Number | Sensor selection: it is possible to combine different sensors summing <sensor> values of the selected sensors:
Allowed sensors:
|
<response_type> | Number | Type of response:
|
<timeout> | Number | Timeout period in seconds (1 - 999) |
<accuracy> | Number | Target accuracy in meters (1 - 999999) |
<num_hypothesis> | Number | Maximum desired number of responses from CellLocate® (up to 16): multiple positions followed by their ellipsoidal uncertainties. This value has to be increased by 1 (GNSS solution) to get the maximum number of possible solutions. This optional parameter can be used only if <response_type>=2. The default value is 1. |
<date> | String | UTC date[3] (DD/MM/YYYY) of the estimated position |
<time> | String | UTC time (hh:mm:ss.sss) of the estimated position |
<lat> | String | Estimated latitude, in degrees |
<long> | String | Estimated longitude, in degrees |
<alt> | Number | Estimated altitude, in meters[4] |
<uncertainty> | Number | Estimated 50% confidence level error, in meters (0 - 20000000) |
<speed> | Number | Speed over ground m/s |
<direction> | Number | Course over ground in degree (0 deg - 360 deg)() |
<vertical_acc> | Number | Vertical accuracy, in meters |
<response_source> | Number | Method used for the position calculation:
|
<SV_used> | Number | Number of satellite used to calculate the position |
<sol> | Number | Solution index (between 1 and <num>) |
<num> | Number | Total number of the available hypotheses (less than or equal to <num_hypothesis>) |
<lat50>/<lat95> | String | Estimated latitude (50/95% confidence levels), in degrees |
<long50>/<long95> | String | Estimated longitude (50/95% confidence levels), in degrees |
<major50>/<major95> | Number | Semi-major axis of the ellipse (50/95% confidence levels), in meters |
<minor50>/<minor95> | Number | Semi-minor axis of the ellipse (50/95% confidence levels), in meters |
<orientation50>/<orientation95> | Number | Orientation of the ellipse (50/95% confidence levels), in degrees |
<confidence50>/<confidence95> | Number | 50/95% confidence levels, in percentage |
<antenna_status> | Number | Antenna status (0 - 4)(). For more details, see the u-blox GNSS receiver protocol specification |
<jamming_status> | Number | Jamming status. For more details, see the u-blox GNSS receiver protocol specification |
If AssistNow Online aiding data has been configured by means of the <aiding> parameter of +ULOCGNSS AT command, the +ULOC request using <sensor>=1 (GNSS receiver only) can provide a +UULOC URC reporting a CellLocate® solution (<response_source>=2). This can happen if:
a GNSS fix is not available.
the CellLocate® solution is more accurate (i.e. CellLocate® solution’s uncertainty is better than the GNSS’s one).
If <sensor>=1 (use the GNSS receiver for localization), <response_type>=2 (multi-hypotheses response) is not supported.
The <jamming_status> value must be ignored if the jamming is disabled through +ULOCGNSS command.
The <date>, <time>, <lat>, <long> values are not enclosed in double quotes in the URC.
Wi-Fi scanning can only be executed when the PHY is in an idle state.
+ULOCIND | ||||||
Modules | LEXI-R10401D-00B LEXI-R10801D-00B | |||||
Attributes | Syntax | PIN required | Settings saved | Can be aborted | Response time | Error reference |
full | No | No | No | - |
Configures sending of URCs from MT to TE in the case of +ULOC operations. The URC provides the result of the steps of an +ULOC operation.
A URC is issued for each check in of an MGA server (primary and secondary).
Type | Syntax | Response | Example |
---|---|---|---|
Set | AT+ULOCIND=<mode> | OK | AT+ULOCIND=1 OK |
Read | AT+ULOCIND? | +ULOCIND: <mode> OK | +ULOCIND: 1 OK |
Test | AT+ULOCIND=? | +ULOCIND: (list of supported <mode>'s) OK | +ULOCIND: (0-1) OK |
URC | If <mode>=1: +UULOCIND: <step>,<result> | +UULOCIND: 1,0 |
Parameter | Type | Description |
---|---|---|
<mode> | Number | URC configuration:
Allowed values:
|
<step> | Number | Informs the user about the operation in progress:
|
<result> | Number | Represents the result of the aiding operation:
|
The command setting is not stored in the NVM.