You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be intentional but I noticed that in regular scanning mode a step width of 8.33 kHz always leads to 25 kHz increments after three steps, as expected. But in the spectrum analyzer the step seems to literally be treated as 8.330 kHz. This causes a growing mismatch between scanned frequency and valid air band channel frequencies.
The attached image shows the result of entering the spectrum analyzer with a scanning range of 118.000 to 137.000 MHz showing invalid air band frequencies for both the current and highest frequency.
The text was updated successfully, but these errors were encountered:
The upper limit is now displayed as "136.99999" but I can live with that. Other than that it seems to be working perfectly. Thanks!
Indeed. I figured it wasn't worth using extra bytes to fix such a small display quirk. Also, on my fork of the firmware the "last frequency" (137MHz) is not scanned anyways.
This might be intentional but I noticed that in regular scanning mode a step width of 8.33 kHz always leads to 25 kHz increments after three steps, as expected. But in the spectrum analyzer the step seems to literally be treated as 8.330 kHz. This causes a growing mismatch between scanned frequency and valid air band channel frequencies.
The attached image shows the result of entering the spectrum analyzer with a scanning range of 118.000 to 137.000 MHz showing invalid air band frequencies for both the current and highest frequency.
The text was updated successfully, but these errors were encountered: