Board index FlightGear Support Interfacing

Ads-b

Connecting two computers, using generic protocol, connecting with Matlab?

Ads-b

Postby Luckyfox7 » Tue Mar 10, 2020 9:04 am

Anyone know how to set up flightgear to have ads-b messages sent out of a network port? Just downloaded 2019.1.1 for Windows and Linux.

Thank you
Luckyfox7
 
Posts: 1
Joined: Tue Mar 10, 2020 9:01 am

Re: Ads-b

Postby Johan G » Tue Mar 10, 2020 4:34 pm

I do not think there is ADS-B output specifically. But if you want FlightGear to output data like the one that is in ADS-B I think you will find the FlightGear wiki articles Logging properties (permalink) and Interfacing FlightGear (permalink) to be good starting points. If you want to output actual ADS-B Out packets you would likely enjoy a look at mode-s.org, specifically ADS-B Basics (unfortunately the actual standards are behind paywalls).
Low-level flying — It's all fun and games till someone looses an engine. (Paraphrased from a YouTube video)
Improving the Dassault Mirage F1 (Wiki, Forum, GitLab. Work in slow progress)
Johan G
Moderator
 
Posts: 5782
Joined: Fri Aug 06, 2010 5:33 pm
Location: Sweden
Callsign: SE-JG
IRC name: Johan_G
Version: 3.0.0
OS: Windows 7, 32 bit

Re: Ads-b

Postby Hooray » Tue Mar 10, 2020 4:59 pm

You could probably try setting up a generic protocol (XML) and use a property that is Nasal driven, i.e. set up a really simple generic protocol to emit a static message first, then convert that into a message that is taken from a property. Once that is working, you can look at manipulating the static message, by writing a little script to create an ADS-B as needed, which will also require computing a CRC: https://mode-s.org/decode/adsb/introduction.html

If in doubt, you could simply create a protocol by sending 112 distinct boolean properties, which can then be individually controlled: http://wiki.flightgear.org/Howto:Parsin ... a_UDP_in_C

http://wiki.flightgear.org/Property_tree
http://wiki.flightgear.org/Property_browser
http://wiki.flightgear.org/Generic_Protocol

Basic concept outlined at: http://wiki.flightgear.org/Howto:Port_I/O_from_Nasal

Once you are running into restrictions, the generic protocol could be extended as needed and/or a dedicated protocol could be implemented in C++: http://wiki.flightgear.org/Property_Tree/Sockets

Speaking in general, for binary protocol handling, it would seem to make sense to hook up the property rule system to the generic protocol system, i.e. to have state machine support and to easily implement native helpers via XML (think CRC computation)
Please don't send support requests by PM, instead post your questions on the forum so that all users can contribute and benefit
Thanks & all the best,
Hooray
Help write next month's newsletter !
pui2canvas | MapStructure | Canvas Development | Programming resources
Hooray
 
Posts: 11836
Joined: Tue Mar 25, 2008 8:40 am


Return to Interfacing

Who is online

Users browsing this forum: No registered users and 1 guest