Connect a Stratux to ForeFlight

GDL90 over UDP 4000 - and the one Stratux setting a European pilot must not leave off

ForeFlight talks to a Stratux over GDL90 and over nothing else, so there is no protocol to choose and no address to type. The receiver announces itself and the app lists it. What is left to decide happens on the Stratux: whether it draws the bearingless FLARM and OGN contacts that European airspace is full of, and whether it has a sensor board to feed attitude. Both are covered below.

Why there is no address to type

A Stratux hands out addresses to whatever joins its network and then pushes GDL90 to each of those devices on UDP port 4000. It does not wait to be asked. Alongside the traffic and position messages it sends an identification message once a second that carries a short device name and the running software version - that is what ForeFlight reads to list the receiver, and it is why the entry already shows a version number before you have touched anything. Read that row on the ground: it is the quickest confirmation that the firmware you think you flashed is the firmware that booted.

Setup, step by step

  1. 1Power the Stratux and give it a minute. The WiFi network "stratux" appears; it has no password.
  2. 2Join that network on the tablet. On iOS, allow the local-network prompt the first time ForeFlight asks - deny it and the app will never see the receiver, with no error to explain why.
  3. 3Open the device list in ForeFlight. The Stratux is already there, with its version. Nothing is paired, nothing is typed.
  4. 4Open its detail view and check the rows that matter: a GPS fix with a satellite count, a traffic count that is not stuck at zero, and - if a sensor board is fitted - attitude.
  5. 5Now the European step: open 192.168.10.1 in a browser on the same network and switch on the circle emulation for bearingless targets. Save and let the receiver apply it.
  6. 6Keep mobile data usable while the tablet sits on the receiver's WiFi, or everything the app fetches from the internet - charts, weather, notams - stops updating.
  7. 7Fly the check on the ground, not on the runway: ownship where you are parked, satellites in double figures, and at least one target if anything is airborne within range.

The setting that decides what you see in Europe

A FLARM or OGN contact often arrives with a distance but without a direction that can be trusted. GDL90 has no way to express that: a target either has a position or it does not exist. So the Stratux offers to draw those contacts as a ring around your own aircraft at the measured distance - a shape that says "something is this far away, bearing unknown". Switched off, those contacts are not downgraded, they are dropped, and the app looks quiet while a glider is two kilometres away.

This is also the honest difference between the two big European EFBs. A SkyDemon user can sidestep the whole problem by taking FLARM-NMEA from the receiver instead. ForeFlight has no such door, so the ring is the only representation it will ever get.

Attitude and altitude, precisely

  • Attitude travels on the same connection as the traffic, on the same port. If the receiver has a sensor board, the app gets it; if it has none, no app setting will conjure it.
  • The receiver declares its own capabilities in that identification message, and it declares geometric altitude rather than barometric. Treat the altitude it feeds as a GPS height, and keep reading your altimeter for the number that matters.
  • A barometric sensor on the board still earns its place: it is what gives the traffic picture a pressure altitude to compare against, so relative heights read sensibly.

What ForeFlight will not show you here

American guides to this same app spend half their length on NEXRAD images and uplinked METARs. None of it applies on this side of the Atlantic: that weather is FIS-B, a ground service the FAA broadcasts and nobody here does. ForeFlight is not at fault and neither is the receiver - there is no European broadcast to receive. Weather in a European cockpit arrives over the internet, which is why the mobile-data step above is not optional.

When it does not come up

The device list stays empty
Almost always the local-network permission on iOS, declined once and never asked again. Grant it in the system settings for the app. Second candidate: the tablet quietly left the stratux network for a known one with internet.
The device is listed but there is no position
The receiver is talking, its GPS is not ready. A cold start under a hangar roof can take minutes; outside with a clear view it is usually under one. The receiver's own status page tells you the satellite count before the app does.
Traffic appears, then the connection drops under load
Look at power before you look at software. A receiver running two radios and a transmitter sits close to what the board can supply, and a thin cable finishes the job. The power guide works through the numbers.
Everything works, but no glider traffic ever shows
The circle emulation is off, or the 868 MHz side is not calibrated. Both are cheap to check and both are in the receiver's own interface, not in the app.

Values from the Stratux project's EFB configuration wiki

Disclaimer

Stratux is not certified aviation equipment. It does not replace a transponder or relieve the pilot of traffic awareness responsibilities. Use as supplementary situational awareness only. Dross:Aviation assumes no responsibility or liability for the use of Stratux devices, firmware flashing, or hardware modifications. All DIY guides are provided without warranty: use at your own risk.