Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix ADSB Squawk back to decimal #3452

Merged
merged 1 commit into from
Nov 25, 2024

Conversation

magicrub
Copy link
Contributor

This commit by @MUSTARDTIGERFPV changed the squawk text to be shown in Hex. I'm not sure why, maybe he knows? I've never seen it expressed as a decimal. Technically it's an octal number but decimal is the normal conversion.

@meee1 meee1 merged commit 5c46b09 into ArduPilot:master Nov 25, 2024
6 checks passed
@MUSTARDTIGERFPV
Copy link
Contributor

Hey @magicrub! Unfortunately this change doesn't match normal aeronautical standards. A quick check shows squawk values with 5 digit decimal representations. When squawk values are shown for display in applications, they're actually a representation of the octal value as a 4-digit hex value, not as a decimal number.

Take as an example, N635ND flying over the Seattle area right now. They're squawking 1200, the standard US squawk code for VFR flight. Here's that displayed by tar1090.
image

This matches how a squawk value is entered into a transponder and read over the radio.
image

By comparison, with your change, now Mission Planner shows this squawk code as 4608. Excuse the weird font, I'm running on macOS because that's what I have available at the moment.
image

This PR should be reverted.

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.

3 participants