PMDG Forum Rules

1) SIGN YOUR POSTS. Since 1997, we have asked users to sign their real name, first and last, to all posts in the PMDG forum. We do this in order to keep conversations personal and familiar. You took the time to be here, we want to get to know you. This is one of the few rigid rules that we enforce regularly. We do so because we feel that forums in which users must engage one another personally are generally warmer, more collegial and friendly. Posts that are unsigned will be quietly removed without comment by the moderators, so to make your life easy- we recommend enabling your forum signature so that you never need to remember. Do this by clicking the username pull-down at the top right, then selecting "User Settings." You will find the signature editor on the ACCOUNT tab, about half way down the page. Look for "Edit Post Signature." Be sure to click the "Show Signatures" box.

2) BE NICE. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Treat everyone else in the forum with respect even when you disagree. If someone frustrates you, walk away from the conversation or ask for a moderator to get involved. Speaking of Moderators, they prefer not to be treated as "The Thought Police" but if any behavior infringes on the enjoyment of another user or is otherwise considered to be unacceptable in the moderator's judgment, it will be addressed in keeping with our view of ensuring that this forum remains a healthy environment for all simmers.

3) BE LAWFUL: Any behavior that infringes upon the law, such as discussion or solicitation of piracy, threats, intimidation or abuse will be handled unsympathetically by the moderators. Threats and intimidation may, at the moderator's discretion, be provided to law enforcement for handling.

4) BE FACTUAL: When you post, always be factual. Moderators will remove posts that are determined not to be factually accurate.

5) RESPECT COPYRIGHTS: Posting of copyrighted material such as flight manuals owned by Boeing or various airlines is not allowed in this forum. If you have questions related to copyrighted material, please contact a forum moderator for clarification.

6) RESPECT PMDG: We love to hear what you like about our products. We also like to hear what you think can be improved, or what isn't working. Please do tell us and we will always treat your feedback with value. Just be sure to treat the team respectfully, as they do put a significant amount of effort into building and maintaining these great simulation products for you.

7) RESPECT PMDG DEVELOPERS: All of the developers will spend some time here. Given the ratio of developers-to-users, it simply isn't possible for us to answer every post and private message individually. Please know that we do try to read everything, but developer workload is simply too high to manage personal contact with tens-of-thousands of users simultaneously. In most cases, members of the development team will stick to conversations in the forum and will not answer private messages.

8) RESPECT OTHER DEVELOPERS: PMDG has always advocated for a strong development community and we have many friends within this community. Every developer offers something unique that helps to make the simming community larger and more vibrant. We insist that you treat our friends respectfully.

9) RESPECT MODERATORS: Moderators have a tough job, and none of them enjoy having to stomp out negativity. If a moderator has to weigh in to keep a thread peaceful, please respect that effort and refrain from giving the moderator any grief.

10) If you require official support for any of our products please open a support ticket through the support portal,

11) This forum is designed primarily as a vehicle for the PMDG development team to interact with our customers, and for customers to interact with one another in a manner that is positive, supportive and assists in the general advancement of understanding the simulation and helping to make this and future simulations better. Any other use of this forum is not permitted, including but not limited to discussion of pricing policies, business practices, forum moderating policies, advertising of non-PMDG products, promotion of events, services or products that are not approved in advance by PMDG or any other topic deemed unacceptable by any forum administrator

12) HAVE FUN: This is the whole point of it all.
See more
See less

VHF/COM frequencies only allow ".025" steps // Online flying

  • Filter
  • Time
  • Show
Clear All
new posts

    VHF/COM frequencies only allow ".025" steps // Online flying

    Dear PMDG 777 Pilots,
    VHF/COM frequency only allows "dot 025" (.025) steps, e.g. 128.250 -> then 128.275 (next higher) -> 128.225 (next lower).
    For EKCH_APP you have to set 119.800 when flying online, similar frequencies apply to other areas and to ATIS information as well - no chance to fix them on the T7 (PMDG 737 does allow these frequencies..). Thank you for any feedback and solution for this issue.

    Best regards

    The limitation is with the simulator platform. All comm and nav radio functions are features of the simulator and the aircraft container simply provides a user interface such as a model of the radio faceplate and clickspots for operating.

    The 25 kHz spacing is still common in a few parts of the world but I agree it would be nice to see modern (as in the past 20 years) technology applied to the simulation.
    Dan Downs KCRP


      Hello Michael.

      Are you not able to tune the COM to 119.800 in the 777? Was no issue in my -200...
      Unless I have misunderstood your post...

      Regards, Orjan Polman.


        Originally posted by DDowns View Post
        it would be nice to see modern (as in the past 20 years) technology applied to the simulation.
        I'm guessing MSFS2020 will have it
        Thanny Davelaar - Proud owner of PMDG NGX, 777, 747


          Hei Orjan,
          You are fully right - my mistake! COM 119.800 is working, but I wouldn't be able to fix some EGKK frequencies as per below screenshot and as an example only ->

          -EGKK_APP 126.820
          -EGKK_ATIS 136.520
          -EGKK_TWR 124.220
          -EGKK_M_GND 199.998

          Further examples:
          ENGM_ATIS is currently under 127.150 -> this one would work, but EKBI_ATIS shows 118.770 // EBBR_ATIS 132.470 // EHAM_ATIS 132.970 // EDDN_ATIS 123.070 - no chance to fix on the T7, neither 772 nor 773/ 773ER

          I guess I need to do some 737 trainings again if flying online..

          VATTASTIC screenshot EGKK // 05JAN20 at 18:30Z


          Thank you and best regards
          Attached Files
          Last edited by Michael Sabisch; 05Jan2020, 18:55.


            The 199.998 frequency is a UHF frequency, it is outside of the VHF comm range and is probably used by military only.

            The others should be useable if you ignore the third decimal place. For example, 126.820 probably works on 126.825, 136.520 is 136.525, etc. This is 25 kHz channelization (25 kHz = 0.025 MHz).

            Useable channels are for example 126.000 126.025 126.050 .... 126.500 126.525 etc.
            Dan Downs KCRP


              Hi Michael.

              No problem sir
              And in addition to what Dan writes, Vatsim "ignores" the third decimal in the frequency.
              So even if the frequency is for example 126.820, and you tune to 126.825, you will still be perfectly able to listen and transmit on the frequency you have tuned.
              I have never had any issues with it.

              Regards, Orjan Polman.


                To give a bit more background to this:

                In The Old Days most default (and addon) aircraft had radios with only two decimal places. Historically therefore it was only possible to read frequencies out of the sim to two DP (e.g. 126.82).

                As a result, FSD (the server protocol used by VATSIM and IVAO) reads frequencies in BCD16 format: 126.825 as set on your COM radio is read by your pilot client and the VATSIM network as "2682".

                The assumption made by legacy pilot clients (Squawkbox, FSINN) is that the first digit is a 1 and the last digit is a zero. So "2682" to Squawkbox means "126.820".

                However, the network itself (in particular controller clients) is capable of reading 3dp frequencies. The problem is that whilst a controller can set 126.825 quite happily, the older clients (SB and FSINN) are tuning you as a pilot to 126.820. Result = no comms.

                So controllers have to set xxx.820 to make sure it all works for everybody.

                Newer pilot clients like vPilot, as well as the new Audio for VATSIM voice system, 'normalise' all frequencies to the correct 25kHz steps so even where the controller sets 126.820 you will see the "proper" 25kHz frequency of 126.825 displayed in the ATC list.

                In essence - as others have said above, just pretend the third digit doesn't exist.

                199.998 is effectively an inactive frequency precisely so you cannot tune it - in this case it is an ATC mentor who is training a student on EGKK_GND. They show 199.998 because they have not set a primary frequency in order to avoid messing up the way that the ATC clients deal with handoffs between controllers (which is in part dependent upon the controller's primary frequency).
                Simon Kelsey


                  Originally posted by skelsey View Post
                  199.998 is effectively an inactive frequency precisely so you cannot tune it - in this case it is an ATC mentor who is training a student on EGKK_GND. They show 199.998 because they have not set a primary frequency in order to avoid messing up the way that the ATC clients deal with handoffs between controllers (which is in part dependent upon the controller's primary frequency).
                  Interesting... I knew it wasn't a valid VHF and had no idea what it was because it wasn't in the UHF comm range either (225.0–399.95 MHz). In other words, it's a dummy.
                  Dan Downs KCRP


                    Dear All,
                    Thanks a lot for your comments and insights - very helpful (also the aspect of the "dummy frequency" for EGKK_GND)!

                    Really hope that tuning a 25kHz frequency will then allow any readable com data like in the above example -> 126.825 then also covering 126.820.
                    I used to have the Squawkbox on board in former times and have now installed the vPilot client.

                    Cheers, Michael/EDDH


                      Hello...that data is for organizations that utilization transmitters - they are being required by FCC request to change or redesign their equipment to gear that fulfills the new bandplan of 12.5 kHz channel dispersing. That whole FCC archive doesn't matter to you as an audience with a scanner other than to tell you in an indirect manner that in the coming years that scanner you have probably won't get anything on explicit frequencies, that is pretty much all.

                      rush turn pcb assembly in canada
                      Last edited by StacyPoli; 17Jul2020, 19:04.