Skip to main content
    • Aa
    • Aa

Receiver Interface Requirements for Deep INS/GNSS Integration and Vector Tracking

  • Paul D Groves (a1) and Christopher J Mather (a1)

Vector tracking of global navigation satellite systems (GNSS) signals and deeply integrating GNSS with an inertial navigation system (INS) improve robustness and accuracy in poor GNSS signal-to-noise environments. Both require a dedicated interface between the GNSS receiver and the navigation processor to enable the GNSS receiver to output the correlator measurements and input numerically-controlled oscillator (NCO) commands. This paper investigates the requirements for such an interface. Data latency is analysed for a range of different stand-alone GNSS vector tracking and deep INS/GNSS integration architectures. Suitable latency compensation techniques are identified. It is shown that, for the majority of applications, an NCO command update rate of 50 Hz with latency compensation and 100 Hz without is sufficient. An approach to interface standardisation which can handle a wide range of different GNSS signals and receiver designs is proposed.

Corresponding author
Linked references
Hide All

This list contains references from the content that can be linked to their source. For a full set of references and notes please see the PDF or HTML where available.

[9] D H Titterton and J L Weston , Strapdown Inertial Navigation Technology, 2nd edition, IEE, 2004.

Recommend this journal

Email your librarian or administrator to recommend adding this journal to your organisation's collection.

The Journal of Navigation
  • ISSN: 0373-4633
  • EISSN: 1469-7785
  • URL: /core/journals/journal-of-navigation
Please enter your name
Please enter a valid email address
Who would you like to send this to? *



Full text views

Total number of HTML views: 2
Total number of PDF views: 16 *
Loading metrics...

Abstract views

Total abstract views: 54 *
Loading metrics...

* Views captured on Cambridge Core between September 2016 - 24th May 2017. This data will be updated every 24 hours.