![Advanced Navigation Boreas D90 Reference Manual Download Page 54](http://html.mh-extra.com/html/advanced-navigation/boreas-d90/boreas-d90_reference-manual_2856109054.webp)
8.5 Data Anti-aliasing
Internally the Boreas filters update at 1000 Hz. When Boreas outputs data, most applications require the data at
a much lower rate (typically < 100 Hz). This causes a problem for time-based data such as velocities and
accelerations where aliasing will occur at the lower rate. To prevent this problem, if the output rate is lower than
1000 Hz, Boreas will low-pass filter the values of the time-dependent data between packets to prevent aliasing.
This is only the case when a packet is set up to output at a certain rate. If the packet is simply requested, no
anti-aliasing will occur. Additionally there is no anti-aliasing for non time-dependent fields such as position.
8.6 Vehicle Profiles
Boreas supports a number of different pre-configured vehicle profiles. These vehicle profiles impose constraints
upon the filter to increase performance. If your application matches one of the available vehicle profiles, it is
required that you select it for use in the
page in the Web UI or Boreas Manager. For a list of the
different vehicle profiles, see
. If the wrong vehicle profile is selected, it can cause a
significant decrease in performance.
8.7 Atmospheric Altitude
Boreas contains an internal atmospheric pressure sensor. This is used as an altitude aid in the filter. If Boreas is
mounted in an area subject to unusual pressure waves, for example helicopters, or is mounted inside an
enclosure that is not exposed to atmospheric pressure, the pressure sensor input should be disabled. This can
be done by disabling Atmospheric Altitude in the Filter Options page in the
9.1 Using the Web User Interface
or
8.8 Odometer Pulse Length
For Boreas to use a wheel speed sensor or odometer input, it must know the pulse length of the signal. The
pulse length is the distance in metres between low to high transitions of the signal. By default, the odometer will
automatically calibrate itself. To automatically calibrate the odometer pulse length, use the procedure outlined
below.
8.8.1 Calibrating Odometer Automatic Pulse Length
1. Ensure that the signal is connected correctly and that the GPIO pin is configured as an odometer input
using the GPIO configuration page in the web UI or Boreas Manager. See
or
2. Open Boreas Manager, connect to Boreas and open the Odometer Configuration dialogue. In the Odo-
meter Configuration dialogue select the
Automatic pulse length calibration
check box and click
Save
.
3. Wait until Boreas has a continuous GNSS fix and then conduct the test in an area with no obstructions
over the test circuit.
4. If Boreas loses a GNSS fix for any extended period of time during the calibration, the distance travelled
will be reset. The distance travelled can be checked in the Odometer Configuration dialogue to ensure
that it has passed 1000 metres.
5. Once 1000 metres has been driven, check that the automatic pulse length check box has become un-
ticked and the Pulse Length value has changed. This indicates a successfully completed calibration.
v1.2
Page 42
11 Oct 2022
Boreas Reference Manual • Using Boreas