- Joined
- Sep 26, 2011
- Messages
- 1,628
- Location
- State of Confusion
- Display Name
Display name:
chartbundle
So, after hours of work I'm happy to announce a document on the basics of the GDL39 protocol as provided on the Bluetooth interface.
The upside is that it's pretty simple and does almost all the ADS-B and FIS-B decoding for you(no 6 bit alphabets or random lat+lon encoding)
The downside for iOS is that because it's Bluetooth it will require any vendor who wants to use it to have Garmin bless their application before it would be available in the App Store(which I don't think is likely since they don't seem to officially document the protocol.) This is one of the advantages of the devices using WiFi. For any other device(Android, PC, Mac) it's just as easy as a bluetooth connection.
I've not looked at the serial cable yet, but one is on order.
I'm sort of considering an Android app that can translate for WiFi apps but that's significantly more work than just decoding, maybe someone else will handle that part.
http://www.chartbundle.com/tech/gdl39/
The upside is that it's pretty simple and does almost all the ADS-B and FIS-B decoding for you(no 6 bit alphabets or random lat+lon encoding)
The downside for iOS is that because it's Bluetooth it will require any vendor who wants to use it to have Garmin bless their application before it would be available in the App Store(which I don't think is likely since they don't seem to officially document the protocol.) This is one of the advantages of the devices using WiFi. For any other device(Android, PC, Mac) it's just as easy as a bluetooth connection.
I've not looked at the serial cable yet, but one is on order.
I'm sort of considering an Android app that can translate for WiFi apps but that's significantly more work than just decoding, maybe someone else will handle that part.
http://www.chartbundle.com/tech/gdl39/