-
-
Notifications
You must be signed in to change notification settings - Fork 71
EFB Configuration
Stratux Europe Edition simultaneously supports three different protocols to connect to EFBs or Flight Simulators:
- GDL90 (Stratux will send unicast to all connected DHCP clients, using UDP Port 4000)
- FLARM-NMEA (EFB initiates the connection, using TCP Port 2000)
- Flight Simulator (X-Plane)
Different EFBs have different qualities in their implementation. This page is intended to provide experiences with different EFBs and how they need to be configured to work as good as possible with Stratux Europe Edition. Other configurations are possible, this is just what experience has shown to work best.
These settings apply as of 1.5b2-eu010.
- IP Address - 192.168.1.1
- Settings -> Third-Party Devices: enable FLARM Devices -> "Air Avionics AT-1" or "FLARM via Airconnect"
- Go Flying -> Use "Air Avionics AT-1" or "FLARM via Airconnect"
- less recommended as FLARM-NMEA has better support for bearingless targets
- IP Address - 192.168.10.1 or 192.168.1.1
- optional: GDL90 bearingless target circle emulation - enable
- Settings -> Third-Party Devices: enable "GDL90 Compatible Device"
- Go Flying -> Use "GDL90 Compatible Device"
- IP Address - 192.168.10.1
- optional: GDL90 bearingless target circle emulation - enable
- IP Address - 192.168.1.1
- Menu -> Flarm, activate Flarm
- recommended as it supports AHRS and bearingless targets (Sky-Map is displaying them seamlessly as a full circle)
- IP Address - 192.168.10.1
- optional: GDL90 bearingless target circle emulation - enable
- Setup -> Wireless Interface Setup -> Device -> "Stratux", no Password, use GPS data instead of internal GPS (recommended for correct relative altitude information)
- Setup -> Activate FLARM/ADSB traffic display
- Setup -> Vertical/Horizontal range as desired
- IP Address - 192.168.1.1
- Setup -> Wireless Interface Setup -> Device -> "Air Traffic AT-1", no Password, use GPS data instead of internal GPS (recommended for correct relative altitude information)
- Setup -> Activate FLARM/ADSB traffic display
- Setup -> Vertical/Horizontal range as desired
- IP Address: 192.168.10.1
- ADS-B Receiver: config should be automatic, Display FLARM traffic: off
- GPS Source: Stratux
Settings -> FLARM, ADSB-IN config -> Select Stratux and enter WIFI network Pretty good Stratux support. Data is also read from Stratux Webservice, so for example CPU temperature is available in VFRnav settings.
- IP Address: 192.168.10.1 or 192.168.1.1
- Settings -> GDL90 Settings -> Use GDL90
- Settings -> GDL90 Settings -> Use GDL90 GPS as EasyVFR GPS: On
- Settings -> GDL90 Settings -> Use GDL90 GPS as AHRS (optionally)
- Configuration -> System -> Location (GPS) source: Automatic
- automatically detects and selects Stratux when connected
- IP Address: 192.168.1.1
- Settings -> FLARM Settings -> Use FLARM
- Settings -> FLARM Settings -> WiFly IP Address: 192.168.1.1
- Settings -> FLARM Settings -> WiFly Port: 2000
- Settings -> FLARM Settings -> Use FLARM GPS as EasyVFR GPS: On
- Configuration -> System -> Location (GPS) source: FLARM (TCP)
- automatically detects Stratux when connected to Stratux WLAN, status of connection is shown in Main Menu
- IP Address: 192.168.10.1
- under "Devices" select "Stratux"
On top of air2air Stratux traffic, SafeSky adds up 14 different traffic sources to your EFB display.
- IP Address: 192.168.10.1
- Preferences -> Traffic Sharing
- Under the "Navigation" section, pick your favorite EFB (SkyDemon, ForeFlight, EasyVFR...)
- Under the "External traffic device", select "Stratux"
- If you want your Stratux collected traffic to be shared with the rest of the SafeSky pilot community, simply enable "Relay traffic"
More details here: https://github.com/b3nn0/stratux/wiki/SafeSky-integration
- IP Address: 192.168.10.1
- Double Tap screen Config -> Devices
- Choose for example F:
- Edit
- Port Type: TCP Client
- IP Address: 192.168.10.1
- TCP Port: 2000
- Driver: FLARM