Advanced Navigation Boreas D90 - RTCM Differential GNSS Corrections Input; Trimble GNSS Input; U-Blox GNSS Input; Hemisphere GNSS Input

Auxiliary:
Receive
Description
:
This function accepts data in the ANPP format as specified in 11 Advanced Navigation
Packet Protocol.
When this function is enabled, the GPIO and auxiliary ports function the same as the
primary port, with one exception:
1. When setting the ANPP packet and message output rates, the changes only apply
to the port you are connected to. For example, you cannot change the primary port
or GPIO port packet and message rates when connected to the auxiliary port.
10.6.1.32 RTCM Differential GNSS Corrections Input
Type:
Serial Receive
GPIO Port:
2
Auxiliary:
Receive
Description
:
This function accepts RTCM v3 GNSS corrections messages. This allows for Differential
GNSS or RTK with the Boreas internal GNSS receiver.
10.6.1.33 Trimble GNSS Input
Type:
Serial Receive
GPIO Port:
2
Auxiliary:
Receive
Description
:
This function is designed for interfacing Boreas with an external Trimble GNSS receiver. It
accepts data in the Trimble binary format GSOF and expects packet 0x40 with records 1,
2, 8, and 12 at rates higher than 1Hz (20Hz recommended) and optional records 9 and 34
at 1 to 2Hz.
10.6.1.34 u-blox GNSS Input
Type:
Serial Receive
GPIO Port:
2
Auxiliary:
Receive
Description
:
This function is designed for interfacing Boreas with an external u-blox GNSS receiver. It
accepts data in the u-blox binary format and expects message NAV-PVT at rates higher
than 1Hz.
10.6.1.35 Hemisphere GNSS Input
Type:
Serial Receive
GPIO Port:
2
Auxiliary:
Receive
Description
:
This function is designed for interfacing Boreas with an external Hemisphere GNSS
receiver. It accepts data in the Hemisphere binary format and expects message Bin1 at
rates higher than 1Hz. For Hemisphere receivers that provide heading using two
antennas, NMEA should be used instead as the binary format does not allow for
v1.2 Page 105 11 Oct 2022
Boreas Reference Manual • Interfacing