Stratux Troubleshooting: WiFi and GPS
The two things that go wrong between the receiver and your tablet, and what is actually causing them
Almost every Stratux that is described as broken turns out to be one of two things: a WiFi link that will not come up or will not stay up, and a position that comes from the wrong device. Neither is a fault in the receiver, and both look alike from the cockpit - which is why guessing at remedies wastes an afternoon. Work the chain in order and each case names itself.
Start at the status page, not in the app
The chain has three links - receiver, network, app - and the status page at 192.168.10.1 tells you which one is broken in about ten seconds. If it will not load at all, the problem is below it, in power or WiFi. If it loads and looks healthy while your EFB stays empty, the receiver is fine and the problem is in the app's settings. That single check decides which half of this page you need.
The WiFi link
- The stratux network never appears
- Give it a full minute before you judge it - the access point comes up late in the boot. If it still is not there, suspect the supply rather than the software: two SDR dongles draw their peak exactly while the system is starting, and a supply that sags there leaves the Pi stuck before it ever opens the network. A thicker, shorter cable and a power bank that genuinely holds 2.5 A fix this far more often than reflashing does.
- The network is there, but the tablet will not join
- This is nearly always a stale saved password. The network was open when your device first met it; you later set a password, and the device keeps offering the old empty one and fails silently. Make the device forget the network and join it again from scratch.
- Connected, but the address starts with 169.254
- That range is what a device gives itself when no DHCP answer arrived, so it is on the network but has no usable address and nothing will reach 192.168.10.1. Toggle WiFi off and on to ask again; if it repeats, the receiver was still booting when the device asked.
- Android drops back to mobile data
- Android notices a WiFi with no internet and switches away from it, taking your traffic feed along. Telling it to stay connected works until the next reboot; switching the Stratux to WiFi Direct solves it for good and keeps mobile data alive at the same time.
- On iOS the app cannot see the receiver at all
- iOS requires an explicit local-network permission before an app may discover anything on the WiFi it is joined to. Without it the app looks connected and finds nothing. Grant it in the system settings, then fully close and reopen the app. While you are there, WiFi Assist is worth switching off: it quietly moves you back to cellular on a network with no internet.
- You set a WiFi password and cannot remember it
- It is stored in plain text in the configuration on the SD card, so a card reader and any text editor will recover it. Reflashing the image also clears it, at the cost of your other settings.
- It restarts over and over
- A boot loop is a power symptom until proved otherwise. Two dongles on an unpowered port exceed what many supplies deliver; give it a genuine 3 A source or a powered hub and a short cable. If it still loops on good power, the card is the next suspect - cheap microSD cards fail in exactly this way.
Position and GPS
- No fix indoors or in the car
- Expected, not a fault. A car body is a Faraday cage and a roof is nearly as good at blocking the sky. Take it outside, allow a few minutes for the first cold start, and leave it running for half an hour once so it can store the full almanac - after that it fixes in seconds.
- The app navigates on the tablet's own GPS
- The classic silent failure: traffic arrives, everything looks right, and the position never switched sources. Set the Stratux as the position source explicitly in the app, then compare the satellite count it reports against the status page. They should agree.
- A WiFi-only tablet shows no position at all
- Those models have no GPS receiver built in - the location they normally show comes from known WiFi networks, which do not exist at altitude. The external receiver is the only position source they have, so the setting above is not an improvement there but a requirement.
- The position jumps or lags behind
- Look at where the GPS antenna sits. A heated windscreen has a conductive layer in it, carbon fibre blocks as well as metal does, and an antenna in the footwell sees a sliver of sky. Move it up onto the glareshield or out to a window with a clear view.
- The altitude disagrees with the altimeter
- They are measuring different things. The barometric sensor reports pressure altitude against the standard setting, which is what traffic systems compare, while your altimeter shows what you set on the subscale. A difference is correct; it is only wrong if it does not move with the weather.
- Your own aircraft shows up as traffic
- The receiver is hearing your own transmitter - ADS-B Out, or a FLARM or OGN tracker aboard - and has no way to know it is yours until you tell it. Enter the aircraft's code in the settings and it will filter itself out instead of warning you about yourself all flight.
What the lights actually tell you
A Stratux has no status light of its own. What you can see through the case are the Raspberry Pi's two LEDs and whatever the SDR dongles carry, and between them they report power and the memory card - not reception. Knowing which is which saves you reading meaning into a light that has none.
- Red, steady
- The supply is present and holding. This is the normal state and the only thing the red LED is for.
- Red, blinking or dark while running
- Undervoltage - the Pi flags it below roughly 4.6 V. This is the most useful thing the device tells you without a browser, and it points at the cable, the supply or an unpowered hub rather than at the software. A short blink while it reboots is normal.
- Green, flickering
- Memory card activity. Busy during boot, occasional afterwards - exactly what you want to see.
- Green, a repeating long-then-short pattern
- That is the Pi's boot error code, not Stratux doing anything. It never reached the system, so no WiFi will appear - suspect the card or the image on it.
- Green, dark from the start
- The card is not being read at all. Reseat it, and write the image again if that changes nothing.
- The dongles' own LEDs
- USB power is reaching them. They say nothing about whether a dongle is tuned, calibrated or hearing anything - only the status page knows that.
Many cases cover these lights entirely. If yours does, you are not missing much: the status page reports everything the LEDs can and all the things they cannot.
When the receiver is not the problem
- An aircraft that transmits nothing cannot be shown. A Mode A/C transponder, or none at all, leaves no trace for any receiver - which is why none of this replaces looking out.
- Thin traffic on 868 MHz usually means an uncalibrated dongle rather than an empty sky. These tuners drift, and FLARM and OGN occupy a narrow enough slice that a small offset costs you most of the band while everything still looks healthy.
- Swapped antennas produce a convincing half-failure: one band works, the other is quiet. They are tuned to their frequency and are not interchangeable.
- Missing weather is not a fault in Europe. FIS-B is a 978 MHz service from FAA ground stations; nothing transmits it here, so weather in your EFB has to come over the internet.
Related Technology Guides
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.