PAW integration with Foreflight and or Garmin

[peter843]

Hi all,
Does PAW work well with Foreflight. Is it working in the same way that Skydemon does using GDL90 ?

I heard that Garmin have a proprietary protocol for traffic info, so no integration of PAW and Garmin panels like G3x yet ?

[Admin]

Yes on both questions
Its very annoying on Garmin, but they have a proprietary approach
Thx
Lee

[Jacko]

It seems that FLARM can now send TIS data over RS232:
 https://flarm.com/shop/garmin-tis-interface/

If you have a compatible Garmin device, this option will enable you to see FLARM traffic on your favorite display.

The Garmin device has to support Garmin TIS over RS-232.

So in theory it is possible.

[Jacko]

Keith,

Just bumping this thread because Garmin Pilot version 10.7 does now support Stratux with GDL90 protocol, and with version 11 it will support SkyEcho.

Is there a way to make PAW emulate either of these devices (Stratux or SkyEcho)?

TIA, Peter.

[Admin]

PilotAware outputs gdl90
So this should work

[Jacko]

PilotAware outputs gdl90
So this should work

Yes it should work, but for some reason it doesn’t. I guess there’s some kind of handshake between GP and the “supported” GDL90 devices.

Since PAW is a Raspberry pi, could it be programmed to emulate, and pretend to be, one of the supported devices?

[Admin]

I will try and take a look

[Jacko]

From the Stratux docs at

https://github.com/cyoung/stratux/blob/master/notes/app-vendor-integration.md

———————————-
Protocol & network information

Stratux uses GDL90 protocol over port 4000 UDP. All messages are sent as unicast messages. When a device is connected to the stratux Wi-Fi network and a DHCP lease is issued to the device, the IP of the DHCP lease is added to the list of clients receiving GDL90 messages.

The GDL90 is "standard" with the exception of three non-standard GDL90-style messages: 0xCC (stratux heartbeat), 0x5358 (another stratux heartbeat), and 0x4C (AHRS report).

How to recognize stratux

In order of preference:

1. Look for 0xCC (or 0x5358) GDL90 heartbeat message. This is sent at the same time as the GDL90 heartbeat (0x00) message.
2. Look for Wi-Fi network that starts with "stratux".
3. Detect 192.168.10.0/24 Wi-Fi connection, verify stratux status with JSON response from ws://192.168.10.1/status.
4. Use the the second stratux status message.
See main/gen_gdl90.go:makeStratuxHeartbeat() for heartbeat (#1) format.

———————————-

I don’t know which of the above recognition methods GP uses, but I could easily try 2.

Peter.

[Jacko]

I tried just setting the SSID to “stratux” - without success.

Next step might be to set the PAW’s IP to 192.168.10.1

However, I gather (perhaps incorrectly) that the facility for users to change the IP address was removed from PAW some time ago.

[Jacko]

The latest version of GP (11.1.4) has added “generic GDL90 device support” so it now seems to work with PilotAware. I haven’t tried it in flight yet, but it shows commercial traffic from my hangar.

[exfirepro]

Hi Jacko,

An interesting development - certainly looks promising. Please keep us posted on your findings - especially once you manage to test it 'in flight'.

Best Regards

Peter