[ADS-B] Add emitter category support & HTTP endpoint for retrieving ADS-B data #3428
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
I like it. Looks good to me. Why do you have it marked as draft? Other than the fact that you should squash that last commit into an earlier one, this looks good to go. |
Contributor
Author
I'd like to change the behavior of speech callouts by setting the thresholds a little further out and adding a 5km, 3km, and 1km warning level. Other than that, should be good to go. :) |
LachlanConn
reviewed
Jul 14, 2025
| adsbplane.IsOnGround = pllau.IsOnGround; | ||
|
|
||
| if (((DateTime) pllau.Time) > DateTime.Now.AddSeconds(-30)) | ||
| { |
Contributor
There was a problem hiding this comment.
Hi great PR hoping this merged but also in the switch case below should the Threat level NONE be changed to green.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the following:
Differentiated icons for light/small/large/heavy and similar aircraft types. This lets users differentiate a 747 from a C172 at a glance. Thanks to tar1090 for these sprites.
Instead of retaining different sprites per color, I'm instead coloring at runtime and caching to improve performance.
Before, all the same size/shape
After, with size/shape differences matching their size/shape
Type/Category readouts in the popover to make the size & type data more explicit.
In addition to the shape/size of the sprite changing, you can also explicitly read what type of aircraft you're looking at and its category.
An endpoint on the internal webserver at /adsb which serves Mission Planner's ADS-B data as JSON
This is extremely useful for external applications to understand local traffic. Whether you're using a MAVLink-connected ADS-B In receiver or the HTTP API support I recently added, you have a unified view of the same data your MAV & MP have.
Category support on ADSB_VEHICLE messages sent to the MAV
Previously the messages sent to the MAV didn't include the category (light, small, heavy) of the aircraft. Now it does.
Speech callouts for ADS-B Traffic at emergency proximities
When traffic is very close both horizontally and vertically, turning on the speech "ADS-B Alerts" checkbox in Planner settings will give a TCAS-style callout "Traffic: 4 O'Clock high; descend" every 5 seconds.