Purpose: The purpose of this Knowledge Base article to is outline a few commonly seen issues and fixes that surround large GNSS position errors seen internationally. It is important to note that these issues are not at the fault of Inertial Labs products, but satellite line of sight issues, and satellite correction services.

Topics: MRU, INS, receiver, Error, Position, EGNOS, WS, SBAS, Correction

Purpose: The purpose of this Knowledge Base article is to show how information is used from respective sensors inside the Inertial Navigation System. Although a complex product, this diagram breaks down the different functions and explains how data is used and how it can be accessed on the device.

Topics: INS, Data, Flowchart, Flow, Communication, Ports, COM

Purpose: The purpose of the this knowledge base document is to explain the potential interference caused by ports such as USB3.0 in interfering with satellite line of sight (LOS).

Last Updated: March, 2020

High-frequency devices, like high-speed processors or high-speed communication buses (say, USB3 or PCIExpress) are known to produce electromagnetic interference (EMI) in the 1.2 – 1.5 GHz range, where all GNSS signals reside.

Topics: USB, INS, Interference, Satellite, EMI

Purpose: To give insight for the potential user on a commonly seen misunderstanding in the difference between UTC and GPS timestamps.

Last Updated: March, 2020

 

Customer:

I have found one issue that I am currently confused with. The timestamp recorded from COM1 of the INS is consistently 17-20 seconds fast. If I start recording at 00 seconds, the first timestamp is equal to 17+ seconds, however the location data that comes from the GPS receiver is correct for 00 seconds and not 17+ seconds. Any insights into this issue?

Topics: INS, GPS, Difference, UTC, Time, Offset, Position

Purpose: To direct product users to the LabVIEW drivers for the Inertial Labs IMU-P, MRU and INS.

Topics: MRU, IMU, INS, Driver, LabVIEW

Purpose: To diagnose the common issue of a user being able to connect to an Inertial Labs Inertial Navigation System using Windows 10 but when using a different operating system, such as Windows 7, the unit will not connect.

Topics: INS, Driver, FT230x, Error, Windows, 7, 10

 

Purpose: To describe the Inertial Labs ROS Driver Package for INS/MRU/AHRS/IMU.

Last Updated: December 8, 2020

Click Here to Download ROS Package for Inertial Labs Products

The InertialLabs_ros_package package is a linux ROS driver for GPS-Aided Inertial Navigation Systems (INS), IMU-P, AHRS and AHRS-10 of Inertial Labs. The package is developed based on the official SDK v0.2 for Linux. 

Topics: MRU, AHRS, IMU, INS, ROS, Driver

• For some applications, the Inertial Labs Inertial Navigation System (INS) is configured to allow external heading input from a Stand-Alone Magnetic Compass (SAMC).

Topics: INS, Magnetic, SAMC, Compass, Stand-Alone

Purpose: The purpose of this article is to help diagnose an accidental break condition. This same situation is capable of occurring for both INS models and MRU models.

Last Updated: July 2019

 

Customer:

The customer connects the AHRS-II-P with the Auto-pilot. Then power is switched on for the AHRS-II-P unit – neither the LED glows nor the unit outputs any data and this remains the same for a long time if left untouched.

Topics: MRU, AHRS, INS, Break, Off, Restarting, AHRS-II-P, Condition, On

Last Updated: November 2019

Purpose: Link to the Inertial Labs Software Development Kit (SDK). This SDK applies to all models of the Inertial Labs Inertial Navigation System (INS), Marine Reference Unit (MRU), and Attitude and Heading Reference System (AHRS-II).

Topics: MRU, AHRS, INS, Software, SDK, Development, Kit, Linux