Configuration; Essential Settings - FLARM FUSION PowerFLARM User And Maintenance Manual

FLARM Technology Ltd
Hinterbergstrasse 15
CH-6330 Cham
5

Configuration

The functioning of FLARM, including collision warnings, depends on the aircraft
type in which it is installed. Thus, it is essential that FLARM is correctly configured
during installation, when moving the device to another aircraft, and when replacing
the device.
The following means of configuration are available:
1. Interactively via FLARM Hub (see Section 3.4.1)
2. Interactively through a connected display that supports it
3. Using a configuration file and the USB flash drive (see Section 4)
If configuring using a USB flash drive, the configuration should be verified using
FLARM Hub or by other means. The essential settings should also be verified after
a firmware update.
5.1

Essential Settings

The following settings must be configured:
Aircraft type
FLARM uses collision algorithms specific to the aircraft type in which it is installed.
If the wrong aircraft type is configured, this will have negative effects both for the
own system as well as FLARM systems in other aircraft, e.g. when calculating the
collision risk with the own aircraft.
Transponder type
The type of transponder installed must be configured, so FLARM knows how to
interpret the data from the own transponder.
ICAO 24-bit aircraft address
If the aircraft has a Mode-S transponder or separate ADS-B Out 1090ES
equipment, the 24-bit aircraft address must be configured. This ensures that
receiving devices can correctly correlate the FLARM and transponder signals.
Furthermore, this allows to use the pressure altitude received from the own
transponder instead of from the integrated barometric sensor. This produces more
accurate altitude readings.
Protocol Version and Baud Rate
Configure the highest protocol version and baud rate that the connected display(s)
support, on each data port, respectively. This information is available from the
POWERFLARM
FUSION USER AND
MAINTENANCE
MANUAL
Date: 2020-11-10
Version: 1.0
Page: 27 of 49
Document Number:
FTD-078