Yes. RT-Range is the industry standard for ADAS testing and is compatible with a wide range of testing hardware. To find information on a specific system, click here to contact our support team.  
Contact support 

Yes, as long as your GNSS/INS is suitable you just need to be able to mount at least one small Pozyx Industrial Tag to your vehicle or robotic platform, you can maintain sufficient accuracy to operate driving robots and platforms. 

Contact us with your usage requirements and building floorplan and we can advise you exactly what you need. OXTS and Pozyx work closely together to achieve suitable installation plans for each installation.  

There are hundreds of Pozyx systems installed around the world already; it is a very well-proven technology. Multiple NCAP facilities, OEMs, and Tier 1 suppliers use Pozyx 2GAD and an OXTS GNSS/INS. 

The Pozyx system can support 1000s of tags at once. When being used and configured with an RT this is reduced to around 200 tags which means normally around 100 moving actors can be used. 

Our RT-Range solution is flexible enough to handle any ADAS test, including those involving moving or stationary targets, robotic platforms, and lane markings or road edges. 

Learn more about RT-Range

Pozyx 2GAD is compatible with RT3000v3, RT3000v4, RT1003v2, xNAV650, AV200, AB Dynamics LaunchPad v4, AB Dynamics Pinpoint v3. A firmware update may be required. 

Due to the intrinsic behaviours of ultra wideband, the exact performance will vary depending on the physical geometry and design limitations of the area. It is normal to achieve relative accuracy of around 3.5cm CEP, in nice open spaces it is likely to be better and in complex designs may be reduced. The permitted signal strength and frequencies may also vary between countries depending on the specific local regulation. 

Any. The Pozyx system is suitable for small (10m) to very large (3km+) installations. Contact us with your needs and we will work to make it a reality. 

Yes, as long as your GNSS/INS is compatible. You just need to be able to mount at least one small Pozyx Industrial Tag to your robot. 
Learn more about Pozyx 2GAD 

For synchronisation with sensors such as LiDAR, cameras, and radar, OXTS devices provide both PPS (Pulse Per Second) and PTP (Precise Time Protocol) for clock synchronisation. PTP is more often used nowadays and streamlines synchronisation over a network. OXTS devices support PTP 2.0 and gPTP in either master or slave configurations. 

Aside from synchronisation, there are also decoders available in C/C++, ROS2, and NVIDIA DriveWorks to integrate the INS outputs into the autonomous vehicle environment. Similarly, the OXTS GAD Interface, you can package up data from other sensors to be fed into the OXTS navigation engine. 

The pose of a robot/vehicle is described by its position and orientation within a reference coordinate frame. An INS uses a fusion of GNSS data and data from its inertial sensors to estimate those measurements. 

A typical GNSS/INS relying solely on GNSS and IMU fusion will switch to inertial dead reckoning in the absence of GNSS signals. Dead reckoning aims to continue updating the pose outputs based purely on the inertial measurements of motion. However, any IMU will suffer from position and velocity drift over time due to inherent errors that accumulate over time. 

To minimise or even eliminate this drift in GNSS-denied areas, OXTS INSs are capable of integrating additional sensor information in order to constrain the IMU errors in place of GNSS. For example, our LiDAR Boost technology can generate velocity and position data using LiDAR data. It’s also possible to integrate other sensor data with our Generic Aiding Data interface, including ultra-wideband (UWB), ground penetrating radar, vehicle odometry from an on-board CAN bus, and camera-based visual inertial odometry. 

Localisation is a core component of an autonomous vehicle’s control stack. Localisation tells the vehicle where it is and how it’s moving, and combines with perception modules to give the vehicle the information it needs about the environment it will be navigating in. A GNSS/ INS provides high accuracy, low latency localisation data in real-time that feeds the rest of the autonomy stack to enable autonomous driving. 

The list of export controlled INS Units is:

RT3000 v1

RT3000 v2

RT3000 v3

RT500

Survey+

Survey+ v3

OEM3000 v3

Inertial+

RT-Split

All RT3000 except RT3000v4 require an export licence. Please contact OXTS for confirmation of the ECCN.

All current OXTS models are ITAR-free, meaning that they are not subject to ITAR regulations and can be exported globally with ease. 

Some older models are ITAR-regulated; if you own an older OXTS GNSS/INS, please contact your reseller or OXTS directly for more information. 
Contact us 

Please contact OXTS for confirmation of the correct ECCN.

OXTS GNSS/INS units have the HS Tariff code 8526100090 

No. By default, the data from your OXTS GNSS/INS is a fusion of the raw GNSS and IMU data done by our Extended Kalman Filter. The EKF ensures the data is highly accurate. 

No. The warmup process is designed to measure real-time errors from the sensors and adjust the navigation engine in the GNSS/INS to compensate for them. Those errors are different every time you start up your GNSS/INS, so your warmup from one session won’t work for another. The good news is that our latest technology can warm up with just three minutes of low-dynamic driving. 

Any  sensor can be fused with an OXTS GNSS/INS to provide accurate localisation indoors – and WayFinder provides indoor localisation functionality out of the box. OXTS also enables you to transition between indoor and outdoor spaces seamlessly. 
Learn more about Pozyx2GAD  

No, but dual antenna will give you more accurate heading data at lower speeds, and prevent heading drift when your vehicle is stationary. A single antenna setup will work well and give an accurate heading at higher speeds, though. 

Simply click below to go to the latest version of NAVsuite. 
Download NAVsuite 

An OXTS GNSS/INS outputs a number of status information and quality metrics that help determine the accuracy, integrity, and confidence of the measurements it provides. Each navigation measurement has an associated value called an “innovation” that represents how well the independent data sources such as the GNSS and IMU solutions agree with each other, and how far those deviate from the Kalman Filter estimates. 

There are also indicators showing what state the GNSS/INS position and velocity modes are in, including: RTK Integer (Fix), SPS, Odometry; the number of satellites currently being used from each constellation; and the status and age of any differential corrections received. 

OXTS systems provide several synchronisation methods to ensure that data from multiple sensors (e.g., cameras, LiDAR, radar) is correctly synchronised, including PTP, gPTP, NTP, PPS and NMEA. This is essential for any application involving data from different sources and ensuring that the resulting maps are accurate. 

Data is logged internally on the device and can also be streamed in real time over ethernet to other devices included external data loggers. The data stored on the internal memory can be extracted using FTP. 

No, NAVsuite is not directly supported in Linux. However, we offer command line options in Linux, such as NAVsolve CMD, and also NCOM decoders, which you can find on our tools page. 
Visit tools page 

Data is available in real time over CAN and our proprietary NCOM format over serial or Ethernet. NMEA data is also available over serial or Ethernet. Post-processed data can be output in a generic .csv format to import into Matlab, Excel or similar. 

Corrections services vary throughout the US. Some states provide correction services for free, while others have independent providers who charge for their services.  

All OXTS GNSS/INS units (except WayFinder) contain a fully configurable NTRIP client which can be set to accept corrections in many different forms, including:  

• Base Station via RS232 port 

• NTRIP via RS232 port 

• NTRIP via DGPS over ethernet 

• WAAS (also known as SBAS). 

Our units can also accept corrections from external NTRIP clients like Lefebure given the proper setup is in place by the user. You can find guidance for this by clicking here.  

The three main types of data an OXTS GNSS/INS provides are: 

• Position data – the location of the GNSS/INS, in a local or global coordinate frame. 

• Pose data – the heading, pitch, and roll of the GNSS/INS. 

• Dynamics data – linear and angular velocity, acceleration, etc. 

To see the specification for your device, visit the relevant product page and download the datasheet. 
See our products 

All of our R&D and our production is done in the UK. 

Quite a few units have a STEP file uploaded on our support site; click the link below, open up the “products” drop-down menu, and click on your model. If no STEP file is shown, please contact our support team for more help. 
Email support 

Pin diagrams are generally found towards the end of a unit’s manual. An online version of the manual can be accessed from the relevant product page on our website. 
View our products 

This is a known issue on xNAV650, AV200, and RT1003 v2 units, and happens because the GNSS cards inside them do not report differential age. This issue has been fixed in 230113×1 firmware, which you can download by emailing us. 
Email support 

Yes. OXTS systems are used in a wide variety of mobile mapping systems to provide accurate positioning and orientation data. That data can then be used to georeference LiDAR scans, images, and other sensor data, allowing for precise mapping of roads, buildings, and other infrastructure. Popular applications include asset management, HD map creation for autonomous vehicles, and infrastructure monitoring. 

OXTS’ software can output trajectory data in standard formats (such as .pos, .csv, SBET, .ncom) that can be easily imported into popular mapping and GIS software (e.g., TerraSolid). OXTS also provides georeferencing software tools like OXTS Georeferencer for LiDAR boresighting and pointcloud creation that output in standard formats (.las, .laz, .pcd). 

At the core of every OXTS GNSS/INS is a fusion of GNSS and IMU data that provides a high-frequency stream of accurate and precise data for georeferencing. That data stream can be enhanced with data from additional sensors such as LiDAR to provide accurate position, velocity, and orientation data in challenging environments where GNSS signals may be weak or intermittent (e.g., urban canyons or dense forests). This helps improve the precision of georeferencing in those environments, whether in real-time or post-process. 

Georeferencing is the process of aligning spatial data (e.g., images, scans, or point clouds) to real-world coordinates, using trajectory data from a localisation system. It ensures that the collected data is accurately positioned in a global coordinate system, which is critical for precise mapping, navigation, and analysis. 

A static survey involves taking a relatively small number of GNSS measurements from fixed positions. This can achieve high accuracy, but is extremely time consuming and labour intensive. Direct georeferencing involves moving vehicle on which a sensor is mounted, to collect georeferenced data while in motion. OXTS systems are designed for high accuracy direct georeferencing. 

OXTS systems can be mounted on various platforms, including cars, drones, boats, and UAVs. We have a range of hardware models that are optimised for different use cases, including SWaP-optimised models for aerial surveying. 

You may have set the “error threshold” too low in “processing options”. If the NCOM accuracy isn’t high enough, all of the point cloud will be removed from the final result. Try setting the error threshold to 100cm, and decrease it as far as you can.