PA-28: Unable to Tune Certain ADF Frequencies

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

I have found an issue with radio tuning in the Piper PA-28 Dakota.

When trying to tune a COM frequency such as Asturias Ground on 121.705 MHz, it is impossible to enter the correct value because the small tuning knob increments the frequency in 25 kHz steps. As a result, it jumps from 121.700 MHz directly to 121.725 MHz, making 121.705 MHz inaccessible.

I have also noticed a similar problem with the ADF receiver.

The ADF frequency selector normally allows coarse tuning in 10 kHz increments and fine tuning in 1 kHz increments. In the Dakota, pressing the small tuning knob should switch between coarse and fine tuning modes, allowing individual kHz adjustments. However, this does not work. The selector always changes the frequency in 10 kHz steps, making it impossible to tune frequencies such as the Asturias NDB on 387 kHz.

Because of this issue, many valid ADF frequencies cannot be entered at all.

FREQUENCY OF ISSUE

Always

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Try to tune ADF on 387 KHz

  2. Try to tune Radio on 121.705 MHz

YOUR SETTINGS

PC

Nothing relevant. Defaul aircraft Piper PA 28 Dakonta.

MEDIA

Please add a screenshot or video of the issue occurring.

Everything in this game is frustrating. Bugs, bugs and more bugs everywhere.
It’s impossible to make serious and detailed flights without tons of problems…

Hi @Mutadeus
For the Comm change, go into the “AUX” page of the 530, move to “setup page 1” go to the bottom and select “com configuration” and then make the change there.

I’ll go look at the ADF in a bit. It seems like there was something different you had to do so you’d get all the digits.
Regards

P.S. I forgot, but there was a much earlier thread on this ADF issue. But basically, the large rotary moves the first two digits, the small rotary adjusts the third digit, and then I have to click the end of the button with both mouse buttons simultaneously, and the small rotary will control the last digit. I’ll try to find the earlier thread, because some folks found other ways to do these same actions.
Here’s one of the earlier threads where some folks had to use different method of “pushing” the end of the knob.

Hello, and thanks for your help.

Regarding the ADF I could configure specific keys for increasing 1 KHz and another for decreasing 1 KHz, but obviously, I’d like to use the aircraft buttons. I saw in youtube videos where clicking on the small knob toggles between 1 and 10 KHz, but it didn’t work for me.

Yea, clicking the small knob has been problematic for several folks. There have been several ways tried with mixed results. Here’s another old thread with a couple of methods folks have used.

The problem now is, some of those other options aren’t really viable either. So it’s definitely hit or miss. Sorry it’s not working for you.
I just gave it another try, and now my right mouse button will push the button in and then I can use my mouse scroll wheel to move the digits.
The only good news is that you can see the button move in whenever the right combination is used. Again, hope something works for you!
Regards

@MarkHaz3157 : if @Habu2u2 advice about COM frequencies resolved your issue, could you update the title/description to just report the ADF selection issue ?

On further testing, the action that allows me to push the button in (and change which digits are subsequently changed, is what I’ve got bound to the action “Cockpit Interaction-Secondary action”. I have something else bound to “cockpit interaction-primary action” and have no idea why the primary button won’t push the button but the secondary button does work.
But you might check and see if you have something bound to that action, or bind something to it, and see if that works to push the button for you.
Regards