NAVconfig is a tool included in NAVsuite, where users can configure their unit for their testing and measurement needs.

Note - The UI and the options presented to you in the application will differ according to the device you are configuring and the type of vehicle you are mounting the device in.

NAVconfig's Primary Antenna setup screen, one of the many configurable options in the tool

NAVconfig Explained

The application is separated into seven sections, each contains a set of options for you to work through during the configuration process. Each section is explained in this article.

Section 1: Home (New / Modify / Improve)

This section defines how you want to work with a configuration and provides an overview of the connected device and its status. It is the starting point for all workflows in NAVconfig.

When you open NAVconfig, you will be presented with 3 options, as follows:

New
Create a new configuration using blank settings. This is recommended for first-time setups or when configuring a device for a new vehicle or installation.

Modify
Load an existing configuration and change specific settings without repeating the entire setup process. This is useful for making small updates, such as output changes or antenna position adjustments.

Improve
Update a configuration after the device has completed a warm-up period, using a processed NCOM. This allows NAVconfig to apply improved parameters based on collected data, helping to optimize system performance.

Choose whether you are creating a new configuration, modifying an existing one or improving accuracies following after warm-up.

Device and Status Information

When you select a device to configure, or connect to one via Ethernet, the product name is displayed at the top of the window. If you are modifying an existing configuration on a unit, you will see a green "Modified" light in the top of the winodw.

The connection status is shown at the top right of the window:

A green indicator confirms the device is online.
If no device is connected, the status displays as offline.

This information allows you to confirm that NAVconfig is connected to the correct device before continuing.

Saving a Configuration

If you make changes to a configuration and want to keep them for later use, you can save a copy to your PC:

Click the Save icon at the top right of the screen.
Enter a name and description for the configuration.

Saved configurations can be reopened and modified at a later time without needing to reconnect to a device.

Save your progress if you need to come back to a configuration later.

Section 2: Start/Read Configuration

If you are starting a setup from scratch on a new device, you can click new configuration, where you can select to do an offline or connected configuration:

New configuration allows you to set up a configuration from scratch

If you connect a device, you can upload your new configuration directly to that device when you are done, and will have access to any feature code unlocked features that your device has available. Note that this is not the case with an offline configuration.

If you have a configuration you would like to modify, the read configuration section defines the starting point for your configuration by selecting where the base settings are read from. NAVconfig uses this information to populate the remaining configuration parameters.

Choose a Configuration Source

Select one of the following options:

From File
Loads a previously saved configuration from your PC. This is useful when reusing or refining an existing setup.
From RD File
Extracts configuration settings from an existing RD file. This allows you to match the configuration used during a previous data collection session.
From Device
Reads the current configuration directly from a connected device. This is typically used when modifying or improving a configuration already stored on the unit.

Once a configuration source is selected:

The settings are loaded into NAVconfig
Subsequent sections are populated based on the selected product and enabled features
Only options relevant to the device and feature codes are shown

This ensures the configuration process remains focused and avoids unnecessary or unusable settings.

Read configuration allows you to choose where you load the initial configuration settings from.

Section 3: Hardware Setup

This section is used to define how the device is installed on the vehicle. Accurate measurements and orientations entered here are critical to achieving optimal system performance.

IMU Orientation

Specify the orientation of the IMU relative to the vehicle:

Select the mounting orientation
Confirm axis alignment with the vehicle frame

Correct IMU orientation ensures acceleration and rotation measurements are interpreted correctly.

Antenna Configuration

Enter the positions of the GNSS antenna(s) relative to the IMU:

Measure antenna offsets accurately
Define primary and secondary antenna locations (if applicable)

Precise antenna measurements improve position accuracy and heading performance.

No-Slip Constraints

Configure no-slip constraints to support navigation performance by preventing heading variation during test runs.

Enable constraints where appropriate
Define which axes are constrained

These constraints help maintain solution stability when GNSS availability is reduced.

Differential Corrections

Configure how GNSS correction data is provided to the device:

Select the correction type (e.g. RTK, NTRIP)
Enter required connection or network details

LiDAR Configuration

If a LiDAR sensor is used, this section allows you to configure its communication settings:

Enter the LiDAR IP address
Select the LiDAR type from the supported list
LIP and LIR information for LiDAR Boost (if applicable)

Correct LiDAR configuration enables proper communication and alignment between the LiDAR sensor and the navigation system.

An example LiDAR configuration with a Velodyne VLP-16

Using differential corrections improves absolute positioning accuracy.

The Hardware setup section displays your device position and orientation measurements as
they are entered.

The lateral No-slip tab in the Hardware Setup section shows how the IMU position relates to the position of the vehicle's non-steered axle.

Configure GNSS Differential Corrections settings in one place.

Configure LiDAR system and communication

Section 4: Interfaces

This section is used to configure how data is output or input from the device and how external signals are received. Only interfaces supported by the connected product and are available (for example, xNAV650 configuration will not include CAN window).

A brief preview of the available outputs, these will vary by device.

Ethernet

Configure data output over Ethernet.

Enable or disable Ethernet data output
Select the output packet type (e.g. NCOM)
Set the output data rate

Ethernet output can also be synchronized to external triggers:

Output on falling or rising edge of an input trigger
Output based on a camera trigger
Independent trigger settings can be applied to multiple trigger inputs

If using a driving robot, you can also enter the Driving Robot IP address to enable communication.

UCOM

Configure serial output using the UCOM protocol.

Select UCOM message types
Set output rates and formatting

UCOM is typically used for integration with third-party systems requiring serial navigation data.

CAN Output

Configure navigation data output over CAN.

Enable CAN output
Select CAN message sets
Define output rates

This interface is commonly used for vehicle network integration and real-time control systems.

CAN Acquisition

Configure CAN inputs to be used by the navigation solution.

Select incoming CAN messages
Map signals such as wheel speeds or steering angle

Serial 1 Output

Configure data output on the primary serial port.

Select output messages
Set baud rate and update rate

This port is typically used for external logging or system integration.

Serial Aux Output

Configure data output on the auxiliary serial port.

Select message types
Set communication parameters

Useful when multiple serial consumers are required.

Analog

Configure analog input and output channels (if supported).

Enable available analog channels
Define signal behavior and scaling

Analog interfaces are typically used for specialized integrations or legacy systems.

PPS / Triggers

Configure Pulse-Per-Second (PPS) outputs and trigger inputs.

Enable PPS output
Configure trigger input behavior
Link triggers to data output or events

These settings are commonly used for time synchronization with cameras, LiDAR, or other sensors.

PTP

Configure Precision Time Protocol (PTP) settings.

Enable PTP synchronization
Define master/slave behavior (if supported)

PTP allows precise time alignment across connected devices.

Ethernet options including trigger setting and data rate are configured here

Most OXTS units can both output and acquire CAN, but cannot do both simultaneously. Configure the navigation and status messages you want to output from your device and export a DBC file.

Section 5: Environment

This section defines how the device behaves during initialization and operation based on the expected operating environment. These settings help NAVconfig tailor performance to real-world conditions.

Initialization Type

Select how the system initializes.

Dynamic initialization
Recommended for most applications. The vehicle will reach this speed during initialization, allowing the system to align more quickly and accurately.
Static initialization
Used when the vehicle must remain stationary during start-up.

GNSS Environment

Define the expected GNSS conditions.

Open sky
Some obstruction
Frequent obstruction (urban or tree-lined areas)

This helps the system manage GNSS weighing and reliability.

Vibration Level

Specify the level of vibration expected during operation.

Normal
High
Very High

Correct vibration settings improve filtering and solution stability.

Heading Lock

Configure how heading is maintained to prevent drift.

Set how tight heading will be while stationary
Select expected heading sources where available (non-flat surface)

Garage Mode

If enabled, Garage Mode allows the system to maintain heading and position accuracy when operating in enclosed or GNSS-denied environments such as garages or workshops.

Local Coordinates

If enabled, local coordinates allows the system to display coordinates relative to a preset point, instead of the typical global coordinate plane.

Environmental settings play a large role in how the Kalman filter, our post processing algorithm, will behave.

Section 6: Advanced Tools

This section provides access to advanced configuration options for OXTS users. These settings allow finer control of system behavior and data output. While most of these are not necessary for running a test, they can help maximize accuracy and data usability.

GNSS Control

Configure how GNSS data is used by the system.

Select GNSS control mode
Enable or disable GNSS aiding features

These options influence how the system responds to changing GNSS conditions.

Coordinate Frames

Select the coordinate frame used for output data.

Choose the required reference frame
Configure local or global coordinate options

This ensures data is reported in the correct format for downstream systems.

Wheel Speed Aiding

Configure wheel speed sensor inputs.

Enable wheel speed aiding
Map input channels

Wheel speed aiding improves navigation performance during GNSS outages and low-speed operation.

Acceleration Filtering

Configure acceleration filtering behavior.

Enable or adjust acceleration filters

This helps reduce noise in high-vibration environments.

Output Smoothing

Control smoothing applied to output data.

Enable or disable smoothing
Select smoothing levels where available

Smoothing can improve data readability for visualization and control applications.

Additional Advanced Settings

Depending on the product and licenses, additional options may be available, including:

Sensor fusion controls
Aiding sources
Commands

These settings should only be adjusted if you are familiar with their impact on system performance.

GNSS control allows you to set which GNSS processing algorithm the system will uses to update the Kalman filter. Read more about gx/ix here.

Enter the measurement point of an odometer in relation to the INS to configure wheel speed input.

Specify the accuracy of your measurements used in hardware setup. Some of these measurements will be improved during warm-up.

Section 7: Write configuration

Now that you have entered your configuration settings ,you can commit the settings to the device, or save them to your PC. This can be done via an Ethernet connection from your PC, or over Wi-Fi if you are using the RT-XLAN Wi-Fi network.

Select the device you want to commit the configuration to from the drop-down list.
In order for the configuration changes to be made on the device the device needs to be reset. You can choose to do this immediately, or save the configuration for later.

Once you click 'Commit' (bottom right), the configuration changes will be made to the device. NAVdisplay will automatically load (if the checkbox is ticked) and you can begin initialization and warm-up procedures.

Device information (i)

This section displays information about the device that is connected to the application, including the feature codes that are enabled and the hardware and firmware device status.

The Features Codes table shows the features that are enabled on your device. Contact OXTS support if a feature you are expecting to be available is not enabled.

System Information shows: Product Information (product type), Hardware Configuration and Firmware Information.

Application settings

This section contains global settings for the application, including Language, measurement units and the folder where configurations are saved to your PC.

Application settings include Language and Measurement unit type. You can also change where configuration files are saved on your PC by default.

Symbols

Improve settings after a warm-up

This option allows NAVconfig to refine certain configuration parameters after the device has completed its warm-up period. It is typically used to optimize performance once the system has stabilized.

When to Use Improve

Use the Improve workflow when:

The device has already been configured and installed
The system has completed a warm-up period
You want to apply optimized parameters without rebuilding the full configuration

This is commonly performed after initial data collection or during system fine-tuning.

What Is Improved

During the Improve process, NAVconfig can update selected parameters based on collected data, such as:

Sensor Alignment
Antenna Position
Wheel Speed Sensor position

These improvements are applied automatically and do not require manual entry.

Applying Improvements

To apply improvements:

Select Improve in the Start section
Connect to the device or load the relevant configuration
Write the updated configuration back to the device

Once written, the improved settings are stored on the device and used in subsequent operation.

Notes and Best Practices

Ensure the system has completed a full warm-up and process the resulting RD before using Improve, for instructions on post processing refer to Post Processing using NAVsuite – OXTS Support
Do not move or remount hardware between warm-up and improvement
Use Improve Configuration only when installation parameters have not changed

Read improved settings from a device, an RD file or folder on your PC

Confirm the device or file you wish to read improved settings from

The improved settings will be displayed in each section

Commit the improved settings by clicking Finish. You can choose to reset the device automatically or wait until later.

	Click on this symbol to save the progress of your configuration to your PC.
	Indicates that a measurement will be improved in accuracy during a device warm-up. Hardware setup measurements are set to 20cm accuracy. You can change this accuracy in the Advanced Tools section.
	Draws your attention to an instruction.
	Indicates that a feature is locked on your device. You can unlock a feature code by contacting sales@oxts.com.
	Indicates that a feature has been unlocked by a feature code on your device.

Articles in this section

Contents