Skip to content

ADSB selected the most dangerous vehicle by CPA calculation#11346

Draft
error414 wants to merge 4 commits intoiNavFlight:maintenance-9.xfrom
error414:error414/feature/adsb-intercept-calc
Draft

ADSB selected the most dangerous vehicle by CPA calculation#11346
error414 wants to merge 4 commits intoiNavFlight:maintenance-9.xfrom
error414:error414/feature/adsb-intercept-calc

Conversation

@error414
Copy link
Contributor

@error414 error414 commented Feb 18, 2026

Base of this PR is add posibility to choose CPA calculation. If vehicle flies from warning zone to alert then vehicle is showed in OSD as alert (blinking).

Manual is changed https://github.com/error414/inav/blob/error414/feature/adsb-intercept-calc/docs/ADSB.md and Martinov created nice video with explanation https://discord.com/channels/791437907478577172/881440734761345086/1473447570234806486

Next changes:

  1. ADSB calculation was removed from OSD thread and moved to ADSB thread (500ms). OSD thread takes soo much time so better to move ADSB calculation to his own thread. ADSB thread takes a few uS.

  2. added two new MSP2 commands, ADSB_LIMITS and ADSB_WARNING_ICAO. "Limits" returs ADSB limits from OSD settings, and "adsb_warning_icao" returns icao of plane which is selected as dangerous. MSP commands are new functionality in configurator

  3. in configurator, selected vehicle as dangerous is marked red or orange depend of if iot's warning or alert

  4. map is spread to whole VISIBLE area

  5. visually represented ADSB limits on map, see screenshot

image

Configurator: iNavFlight/inav-configurator#2569

BTW: MSP is breaking change so maybe better to merge it to INAV 10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments