StreamDeck/FlightTracker and 25kHz freq spacing

856101 · March 5, 2024, 4:08am

I use the phenomenal “FlightTracker” plugin with my StreamDeck while flying. However, I noticed that when entering in new freqs via the numpad feature, sometimes it would become a NORDO event. So, I went digging, and discovered it was related to 25kHz spacing and how the plugin didn’t check for compliance before sending the new frequency to the sim.

After writing some code to solve, I opened a bug report. However, some real world events cropped up and don’t have the time to pursue a pull request and edit. Anyway, if you use the FlightTracker plugin, here is the bug report, and a post I made with the solution, in case you run into the same problem on VATSIM.

github.com/nguyenquyhy/Flight-Tracker-StreamDeck

Entering in COM frequency via numpad does not check for 25kHz frequency spacing compliance.

opened 11:52PM - 24 Dec 23 UTC

daneverette

bug

This is most applicable to online flying using ATC networks such as VATSIM, Pilo…tEdge, IVAO, etc. In 25kHz frequency spacing, ATC will usually only issue a frequency change including the first 2 numbers following the decimal point. If a user enters just the new assigned frequency, FlightTracker does not check compliance with the 25 kHz spacing before sending the new frequency to the sim. For example, if the new frequency to change to is "135.075", ATC will likely just issue "135.07" as the new frequency. If the user just enters what was assigned "135.07" into FlightTracker, the frequency sent to the sim is "135.070", but should be "135.075". This is particularly important in avionics that only display 2 digits after the decimal point. This is not an issue with new 8.33kHz frequency spacing in use in Europe, as ATC is required to read all three digits. Will create a pull request shortly to submit code for checking/modifying COM frequency is conforming to 25 kHz spacing.