BradThePilot
New Member
- Joined
- Sep 24, 2022
- Messages
- 11
I flew around for a while today, capturing all UDP packets sent by SkyView via wifi to port 4000 on my laptop. While still investgating the results, what I've found is that SkyView (as of v16, anyway) sends GDL90 'traffic report' and 'uplink' packets, but never sends the 'heartbeat' or 'ownship' messages that are part of the GDL90 spec. This was for a flight that lasted over an hour, and the heartbeat is supposed to be sent once per second so I would have thought I would have seen something.
I'm wondering if this is why (or at least part of the why) some clients don't work with SkyView's WiFi ADS-B - those missing messages are mandatory in the GDL specification but they ain't coming out of SkyView's ADS-B feed over wifi. It's reasonable to expect that a client (EFB app, Avidyne IFD, etc.) written to the GDL spec would be expecting the heartbeat message, at a minimum, and if it doesn't see it doesn't listen for the other items.
Thoughts?
I'm wondering if this is why (or at least part of the why) some clients don't work with SkyView's WiFi ADS-B - those missing messages are mandatory in the GDL specification but they ain't coming out of SkyView's ADS-B feed over wifi. It's reasonable to expect that a client (EFB app, Avidyne IFD, etc.) written to the GDL spec would be expecting the heartbeat message, at a minimum, and if it doesn't see it doesn't listen for the other items.
Thoughts?