GPS Status?

F1Rocket

Member
Official iFly Beta User
Joined
May 3, 2023
Messages
16
Reaction score
1
My Android tablet is connected to the "Ping wifi" while flying. My iFly "instrument" titled "GPS Status" shows ADS-B and a single green bar. I have seen talk here that WAAS in blue means something, but don't recall the details. My uAvionix Echo is connected to my Garmin 430W. Thanks.
 
Not exactly sure what your question is?

To shotgun some info in the hopes it's helpful:
  • If iFly is using location data from the tablet device on which it's running, the GPS Status instrument looks like this: 1726501036701.png
  • If iFly is using GPS data provide by an external ADSB receiver, the GPS Status instrument looks like this: 1726501086060.png
    • The "WAAS" indication may or may not be present depending on whether the ADSB receiver is processing a WAAS signal.
 
This is what my screen looks like. I would think a Garmin 430W would be supplying WAAS. As this is a new device, I am trying to understand if this signal is coming from the Android device or from the EchoUAT.

IMG_9156.jpeg
 
This is what my screen looks like. I would think a Garmin 430W would be supplying WAAS. As this is a new device, I am trying to understand if this signal is coming from the Android device or from the EchoUAT.
I'm an iFly guy, not an expert in all types of ADSB receivers, so you're going to have to help with with how an EchoUAT works. What's that got to do with your 430W? Does the EchoUAT use the 430W as its GPS source? (How does that work??)

If so, then the EchoUAT just may not know whether the GPS position it's getting from the 430W is WAAS-enhanced or not. Or for whatever reason it may not be passing that indication out in its feed to iFly.

Other ADSB receivers that I'm more familiar with (like my Stratux) have their own GPS receivers that can incorporate WAAS, and those receivers provide an indication whether WAAS is incorporated when they provide their GPS location output. Stratux passes the WAAS status indication on in its output that iFly consumes, so iFly can then show it on the display.

It may be that the 430W is outputting a WAAS-enhanced position but not telling the EchoUAT that it's WAAS-enhanced. Or it may be that the EchoUAT forwards on the WAAS-enhanced position but doesn't include the WAAS indicator. If that WAAS indication is getting lost either in the link between the 430W -> EchoUAT or in the link between EchoUAT -> iFly, then iFly won't know the position is WAAS-enhanced and so won't show that.

I don't know enough about how an EchoUAT works to know what's happening with the WAAS indication. 🤷🏻‍♂️
 
The 430W is hard wired to the EchoUAT as a WAAS GPS source. It is not a big deal, but I always wonder, when I become aware of something not working as expected, what else is not working as expected. Thanks.
 
The 430W is hard wired to the EchoUAT as a WAAS GPS source.
OK, gotcha. Then as explained above, the answer to your question lies in the details of how the EchoUAT works. Dunno if anyone else around here is EchoUAT savvy, but I am not. Maybe you could reach out to the EchoUAT folks for more information.
 
Last edited:
Back
Top