Connect to devices

Choose the guide for your traffic source. For a first Bluetooth connection, start with:

• Quick start: SafeSky App via Bluetooth — add the Display from SafeSky App on your phone/tablet.
• Quick start: Aero-Tracker via Bluetooth — connect from the Display's Bluetooth menu.

Wi-Fi connections and other supported devices are covered below.

info

Although the Display firmware may support been connect to multiple devices at the same time, it's a situation that is not properly tested and not intended as standard operation.

note

If testing while on the ground, it is advisable to disable the vertical decluttering filter from the Display otherwise may not see any traffic due to vertical altitude filtering.

Go to Settings / Config / Vertical Decluttering and check the option Show All

Note that the data source (for example SafeSky App) may already be implementing some kind of filtering...

Connection with SafeSky App

Bluetooth is the recommended connection method for SafeSky App. Follow the SafeSky Bluetooth quick-start guide for requirements, setup, status checks, and troubleshooting. SafeSky manages the connection and supplies collision alerts to the Display.

---

Alternate method

There is other way to connect the Display to SafeSky App, we can use Wifi instead of BLE (although when using with SafeSky App, BLE is the official supported way).

For this method to work:

• Connect the FLYSky Display to the same Wifi Network used by the phone/tablet where SafeSky App is installed
• Have SafeSky App configured to share the traffic, and that the software is defined as one of the following
  • EnRoute
  • Garmin Pilot
  • SkyDemon
• On the FLYSky Display access Settings / Config / Wifi Supported Protocols and make sure that GDL90 is selected.

• Also set the option Settings / Config / Traffic/Alerts Data Source to Others

After that, the FLYSky Display should start receiving data from SafeSky App (after performing TakeOff).

If everything is OK, if SafeSky App is in Flight mode, the icons on the FLYSky Display should look like this when connected to SafeSky App using Wifi:

This method from the FLYSky Display side probably works with other data sources that implement GDL90 over Wifi (it's known that the device Sentry although it uses GDL90 is not compatible)

---

Connection With AeroTracker

Bluetooth is the recommended connection method for Aero-Tracker. Follow the Aero-Tracker Bluetooth quick-start guide for setup, status checks, automatic reconnection, and troubleshooting. The Display connects to Aero-Tracker and generates collision alerts when its data source is set to Others.

---

Aero-Tracker via WIFI

From the FLYSky Display side is simple to connect to the Wifi network that Aero-Tracker has. Adjust this settings for better experience:

• On the Display access Settings / Config / Wifi Supported Protocols and make sure that only NMEA or just GDL90 is selected.

• Also set the option Settings / Config / Traffic/Alerts Data Source to Others

If everything is OK, the icons on the FLYSky Display should look like this when connected to AeroTracker using Wifi:

tip

If using AeroTracker via Wifi it is important to not have AeroTracker also configured as Bluetooth device on the FLYSky Display, use only one option or connect via Wifi or Via Bluetooth

tip

If using AeroTracker via Wifi it recommended to configure just one Wifi Protocol on the FLYSky Display, since there may be data conflicts between NMEA and GDL90 information on the Display when attempting to merge the data.

---

Connection to SkyEcho2

The FLYSky Display can receive traffic from SkyEcho using the GDL90 protocol via WIFI Connection.

• Connect the Display to the same Wifi network being created by SkyEcho2
• On the Display access Settings / Config / Wifi Supported Protocols and make sure that GDL90 is selected.

• Also set the option Settings / Config / Traffic/Alerts Data Source to Others

If everything is OK, the icons on the FLYSky Display top bar should look like this when connected to SkyEcho2:

note

At this point is unknown if SkyEcho2 supports sending traffic information of ModeS / Bearingless targets via GDL90 protocol, or how that information is sent.

---

Connection to FDR

The FLYSky Display can receive traffic from FDR using the GDL90 protocol via WIFI Connection.

• Connect the Display to the same Wifi network being created by FDR
  • Check FDR Serial number, the WIFI Network has the same name
• On the Display access Settings / Config / Wifi Supported Protocols and make sure that GDL90 is selected.

• Also set the option Settings / Config / Traffic/Alerts Data Source to Others

If everything is OK, the icons on the FLYSky Display top bar should look like this when connected to FDR:

note

There are some constraints using FDR:

• No support to show Mode-S targets, since this is data directly from SafeSky servers we always have targets real position (may be based on MLAT)
• The data being requested to SafeSky server is limited to:
  • Maximum of 10 targets (sent by proximity order)
  • Relative vertical altitude of +/-5000ft
  • Maximum distance of 14nm
• In case the FDR is paired with FDR_ADSB_Receiver the limits mentioned are not applicable (except that for the moment we do not support Mode-S targets even with local ADSB Receiver)
• FDR receives updated server data at intervals of 1s to 30s, depending on its current status (in an ILS zone, on the ground, airborne, etc.). Between server updates, FDR continues sending the last received traffic information to the Display. If server communication is lost, FDR clears that information when its internal timeout expires. The server update interval is separate from the Display's 10-second timeout for traffic messages received from FDR.

It is possible to have FDR paired with a local ADSB receiver, if the local ADSB receiver is present some of the limitations mentioned no longer applies to the FLYSky Display.

At the moment (it will change in the Future), even when paired to the local ADSB receiver, Mode-S targets are still not supported on the FLYSky Display, this feature is pending some internal testing.