Jump to content

The magic 134.675 frequency


aua668
 Share

Recommended Posts

Hi,

 

I use the A320 Pro version 1.4.1.2 with P3D 5.1 (latest Hotfix). I control my radios via GoFlight hardware. I set the standby frequency (COM1 and COM2) with rotaries via the following FSUIPC/P3D controls:

 

66434   COM_RADIO_FRACT_DEC_CARRY
66435   COM_RADIO_FRACT_INC_CARRY
65636   COM_RADIO_WHOLE_DEC
65637   COM_RADIO_WHOLE_INC
 

and 

 

66439   COM2_RADIO_FRACT_DEC_CARRY
66441   COM2_RADIO_FRACT_INC_CARRY
66436   COM2_RADIO_WHOLE_DEC
66437   COM2_RADIO_WHOLE_INC
 

This works fine in the A320 like for many other aircrafts (stock aircrafts - but also for the Aerosoft Twin Otter for example).

 

But there is one bug, which only arises in the A320: If I tune the frequency 134.675 and swap this frequency from the standby to the active freuency,  this works well. Frequency is tuned and I can communicate with the controller on VATSIM. But as soon as I swap this frequency back to standby, I can't tune it anymore. Something is setting the frequency immediately back to this value, as soon as I try to tune to the next step. And this for increment and decrement (whole and fraction). The only way to get out of this situation is to use the mouse and tune the frequency via the panel.

 

Debugging the FSUIPC log to see the events, I found out, that you are permanently set the COMx standby frequencies to 134.675:

 

  1263688 *** EVENT: Cntrl= 67363 (0x00010723), Param= 136675000 (0x08257eb8) COM1_STBY_RADIO_HZ_SET
  1263688 *** EVENT: Cntrl= 67364 (0x00010724), Param= 134675000 (0x0806fa38) COM2_STBY_RADIO_HZ_SET

  1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2016 (0x000007e0) PANEL_ID_CLOSE
  1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2017 (0x000007e1) PANEL_ID_CLOSE
  1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2019 (0x000007e3) PANEL_ID_CLOSE
  1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2020 (0x000007e4) PANEL_ID_CLOSE
  1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2022 (0x000007e6) PANEL_ID_CLOSE
  1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2023 (0x000007e7) PANEL_ID_CLOSE
  1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2024 (0x000007e8) PANEL_ID_CLOSE
  1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2025 (0x000007e9) PANEL_ID_CLOSE
  1263703 *** EVENT: Cntrl= 66834 (0x00010512), Param= 0 (0x00000000) FREEZE_ALTITUDE_SET
  1263703 *** EVENT: Cntrl= 66828 (0x0001050c), Param= 0 (0x00000000) FREEZE_ATTITUDE_SET
  1263735 *** EVENT: Cntrl= 66717 (0x0001049d), Param= 1 (0x00000001) TURBINE_IGNITION_SWITCH_TOGGLE
  1263735 *** EVENT: Cntrl= 66717 (0x0001049d), Param= 2 (0x00000002) TURBINE_IGNITION_SWITCH_TOGGLE
  1263735 *** EVENT: Cntrl= 66466 (0x000103a2), Param= 0 (0x00000000) COM_RECEIVE_ALL_SET
  1263735 *** EVENT: Cntrl= 67363 (0x00010723), Param= 136675000 (0x08257eb8) COM1_STBY_RADIO_HZ_SET
  1263735 *** EVENT: Cntrl= 67364 (0x00010724), Param= 134675000 (0x0806fa38) COM2_STBY_RADIO_HZ_SET

 

The radios worked fine, until you changed something in one of the previous updates, which broke the radios for many users in this forum completely. The last version in the experimental stream repaired this - but obviously not completely.

 

I know, that this special frequency worked in the past without problems. Why? That's simple. That's the frequency of LOWW_APP, which is the home base of my VA. So I fly typically quite often in and out of Vienna.

 

I always can reproduce this error - but only in the A320 Pro. All other aircrafts (Majestic Q400, Twin Otter, C172, etc.) work perfectly. Maybe some rounding or similar problem, which does not allow to tune to the next step with one of the controls above.

 

Rgds

Reinhard

 

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...