Garmin GTX-345 Integration¶
The Garmin GTX-345 is a panel-mounted ADS-B In/Out transponder that broadcasts traffic and weather to portable devices over Wi-Fi using the same GDL90 protocol as Stratux. AZSuite Mobile is a fully-supported client.
Setup¶
GTX-345's Wi-Fi setup is done in the panel:
- Power on the GTX-345 and let it boot
- The unit broadcasts a Wi-Fi network — typically named after the unit's serial or a configurable label
- Connect your phone to that network
- Open the AZSuite mobile app
- The ADS-B Receiver tile starts receiving frames
Identical to Stratux from AZSuite's perspective — no AZSuite-specific configuration.
Differences from Stratux¶
The GTX-345 has a few traits worth knowing:
| Trait | Stratux | GTX-345 |
|---|---|---|
| Power source | External battery / aircraft power | Aircraft power only |
| GPS | Built-in (single antenna) | Aircraft's GPS source (typically a GTN/GNS) |
| Wi-Fi range | ~10 ft | ~30 ft (panel-mounted antenna position) |
| Cost | DIY ~$200 | Installed ~$5K+ |
| Cabin presence | A box on glareshield | Invisible (panel-mounted) |
| Multiple clients | Yes | Up to 2 simultaneous (firmware-dependent) |
The 2-client limit on GTX-345 means if you have your iPad on ForeFlight and your phone on AZSuite both connected, that's the cap. Adding a third client may bump one of the others off.
Frame format¶
GTX-345 sends:
- Heartbeat (msg ID 0)
- Ownship (msg ID 10) — uses the aircraft's panel GPS (more accurate than Stratux's puck)
- Ownship Geometric Altitude (msg ID 11)
- Traffic (msg ID 20)
- Uplink Data (msg ID 7) — FIS-B
- Foreflight-specific extension messages (rare; AZSuite ignores them)
Identical to Stratux. The only practical difference: the GTX-345's altitude data is more accurate because it uses the aircraft's certified GPS source.
Common gotcha: GTX-345 vs GTX-335¶
There are two similar Garmin units:
- GTX-345: ADS-B In + Out — broadcasts traffic / weather to your phone
- GTX-335: ADS-B Out only — does NOT broadcast to your phone
If your panel has a GTX-335, AZSuite mobile won't see anything from it (there's nothing to see — the unit only transmits to ATC, not to in-cabin clients). You'd need a separate ADS-B In source like a Stratux.
Troubleshooting¶
| Symptom | Likely cause | Fix |
|---|---|---|
| AZSuite sees no frames | Connected to a different Wi-Fi (typically your phone's autoconnect to a hotspot) | Verify the GTX-345's SSID in Wi-Fi settings |
| Two iPads connected, third device gets nothing | 2-client limit | Disconnect one of the others |
| Wi-Fi drops mid-flight | Panel reboot, electrical noise | Verify good ground / clean power; reposition iPad if interference |
| FIS-B works but no traffic | No nearby ADS-B-Out aircraft (rare in CONUS) | Verify on the GTX-345 panel — does IT see traffic? |
Multiple-aircraft clubs¶
If you fly several aircraft each with a GTX-345, AZSuite re-detects the new Wi-Fi network each time you switch aircraft. There's nothing to re-configure on AZSuite's side — just connect your phone to the new aircraft's GTX-345 Wi-Fi when you climb in.
Related¶
- ADS-B receiver
- Stratux integration — same protocol, different hardware