Legacy Configuration Interface Compatibility; Navigation Configuration - u-blox NEO-M9N Integration Manual

Standard precision gnss module
Table of Contents

Advertisement

u-center application. RTCM corrections from a virtual reference service are also supported by the u-
center NTRIP client.
3.1.6 Legacy configuration interface compatibility
Although there is some backwards compatibility for the legacy UBX-CFG configuration messages,
users are strongly advised to adopt the configuration interface described in this document.
See Legacy UBX-CFG message fields reference section in the applicable interface description [2].
3.1.7 Navigation configuration
This section presents various configuration options related to the navigation engine. These options
can be configured through CFG-NAVSPG-* configuration keys.
3.1.7.1 Platform settings
u-blox receivers support different dynamic platform models (see the table below) to adjust the
navigation engine to the expected application environment. These platform settings can be
changed dynamically without performing a power cycle or reset. The settings improve the receiver's
interpretation of the measurements and thus provide a more accurate position output. Setting the
receiver to an unsuitable platform model for the given application environment is likely to result in
a loss of receiver performance and position accuracy.
The dynamic platform model can be configured through the CFG-NAVSPG-DYNMODEL
configuration item. The supported dynamic platform models and their details can be seen in
3
and
Table 4
below.
Platform
Portable (default)
Stationary
Pedestrian
Automotive
At sea
Airborne <1g
Airborne <2g
Airborne <4g
Wrist
Table 3: Dynamic platform models
Platform
Max altitude [m]
Portable
12000
Stationary
9000
Pedestrian
9000
Automotive
6000
At sea
500
Airborne <1g
80000
UBX-19014286 - R07
C1-Public
Description
Applications with low acceleration, e.g. portable devices. Suitable for most situations.
Used in timing applications (antenna must be stationary) or other stationary applications.
Velocity restricted to 0 m/s. Zero dynamics assumed.
Applications with low acceleration and speed, e.g. how a pedestrian would move. Low
acceleration assumed.
Used for applications with equivalent dynamics to those of a passenger car. Low vertical
acceleration assumed.
Recommended for applications at sea, with zero vertical velocity. Zero vertical velocity assumed.
Sea level assumed.
Used for applications with a higher dynamic range and greater vertical acceleration than a
passenger car. No 2D position fixes supported.
Recommended for typical airborne environments. No 2D position fixes supported.
Only recommended for extremely dynamic environments. No 2D position fixes supported.
Only recommended for wrist-worn applications. Receiver will filter out arm motion.
Max horizontal
velocity [m/s]
310
10
30
100
25
100
3 Receiver functionality
 
Max vertical velocity
Sanity check type
[m/s]
50
Altitude and velocity
6
Altitude and velocity
20
Altitude and velocity
15
Altitude and velocity
5
Altitude and velocity
6400
Altitude
NEO-M9N - Integration manual
Max
position
deviation
Medium
Small
Small
Medium
Medium
Large
Page 11 of 95
Table

Advertisement

Table of Contents
loading

This manual is also suitable for:

M9

Table of Contents