RFN Gauge Standby-to-Active frequency switch
Results 1 to 13 of 13

Thread: RFN Gauge Standby-to-Active frequency switch

  1. #1

    RFN Gauge Standby-to-Active frequency switch

    After a fresh install I'm back to using the RFN Gauge (64-bit in P3D v4.5+). I cannot get the "double-arrow" button to switch between Standby-to-Active frequencies to work (neither right, left, or wheel button mouse clicks). Any ideas what I'm doing wrong?

    Many thanks

    Andy

    Attached Thumbnails Attached Thumbnails doublearrowswitchrfngauge.jpg  

    i9-10900K, 64 Gb RAM, RTX 3090 FE, Win10 Pro 64-bit, Reverb G2

  2. #2
    You might look at section "4-4) Malfunction and interference" of the gauge manual for some things to check.
    Could be there is not be a standby frequency enabled for Nav 2 in the [Radios] section of the aircraft.cfg file for that aircraft?

  3. #3
    Many thanks for the reply. The aircraft.cfg contained the following, originally...

    Code:
    // Radio Type = available, standby frequency, has glide slope
    Audio.1       = 1
    Com.1         = 1, 0
    Com.2         = 1, 0
    Nav.1         = 1, 0, 1
    Nav.2         = 1, 0, 0
    ... so I changed this to...

    Code:
    // Radio Type = available, standby frequency, has glide slope
    Audio.1       = 1
    Com.1         = 1, 0
    Com.2         = 1, 0
    Nav.1         = 1, 1, 1
    Nav.2         = 1, 1, 0
    ... and even...

    Code:
    // Radio Type = available, standby frequency, has glide slope
    Audio.1       = 1
    Com.1         = 1, 1
    Com.2         = 1, 1
    Nav.1         = 1, 1, 1
    Nav.2         = 1, 1, 0
    ... but to no avail. The problem persists!

    For the aircraft where is does work I have...


    Code:
    // Radio Type = available, standby frequency, has glide slope
    Audio.1       = 1
    Com.1         = 1, 1
    Com.2         = 1, 1
    Nav.1         = 1, 1, 1
    Nav.2         = 1, 1, 0
    Any further help is much appreciated!

    Andy

    i9-10900K, 64 Gb RAM, RTX 3090 FE, Win10 Pro 64-bit, Reverb G2

  4. #4
    Hi
    4-4) Malfunction and interference
    Have a look on your previous flight.

    The double arrow of the NG box may, in some cases, not work. This situation is often the result of the default flight. It is possible to correct by opening the configuration file. For FSX-Acc, FSX-SE, open with Notepad ++ the .flt file of the recorded flight located in \ Documents \ Flight Simulator X Files.
    Find the [Avionics.0] section.
    If the value of AvionicsSwitch = False change it to AvionicsSwitch = True.
    For P3D the .fxml file of the recorded flight is in \ Documents \ Prepar3Dvx Files.
    Make a Backup of original files.

    Michel

  5. #5
    Many thanks Michel.

    I checked and all was correct.

    Still, to be sure, I deleted the default flight. I then also re-installed the aircraft and modified the new panel.cfg afresh! I then created a new default flight from scratch. The result....? No change!

    Andy

    i9-10900K, 64 Gb RAM, RTX 3090 FE, Win10 Pro 64-bit, Reverb G2

  6. #6
    Hi Andy
    First, take an aircraft with an avionic master. Put this on ON.
    Then take your airplane with the RFN gauge and try the change of frequency.
    If no luck we try another thing.

  7. #7
    If no change, be sure that all these components are installed :
    - Redistribuable Microsoft Visual C++ x86 ou x64 as system specification
    - Microsoft.NET Framework
    With the latest versions of Windows and although installed by default, NET framework does not appear in the list of programs. If present, the installer will signal it.
    - Microsoft Flight Simulator SimConnect Client which is installed with the simulator
    You can install it manually by double cliking on
    1) :\Lockheed Martin\Prepar3D v4\redist\Interface\ESPv1\SimConnect.msi
    2) :\Lockheed Martin\Prepar3D v4\redist\Interface\FSX-RTM\retail\lib\SimConnect.msi
    3) :\Lockheed Martin\Prepar3D v4\redist\Interface\FSX-SP1\retail\lib\SimConnect.msi
    4) :\Lockheed Martin\Prepar3D v4\redist\Interface\FSX-SP2-XPACK\retail\lib\SimConnect.msi

    After each modification, it is necessary to make a test.
    Let me know the result.
    Regards
    Michel

  8. #8
    BINGO! It was the master avionics switch
    Many thanks indeed for your help

    i9-10900K, 64 Gb RAM, RTX 3090 FE, Win10 Pro 64-bit, Reverb G2

  9. #9
    Happy for you.
    I add this in the malfunction section.
    Michel

  10. #10

    RFN Gauge standby-to-active switch

    Hallo Together, I am facing the same issue at the moment. The arrow switch changes only the frequency on the stand-by side using the frequency set on the nav radio. The compass rose of the RFN gauge is working but the ship is not detected. Is there any help to guide me to a perfect carrier landing? Thanks a lot Achim

  11. #11

    RFN gauge not working - Solved

    Quote Originally Posted by loomy View Post
    Hallo Together, I am facing the same issue at the moment. The arrow switch changes only the frequency on the stand-by side using the frequency set on the nav radio. The compass rose of the RFN gauge is working but the ship is not detected. Is there any help to guide me to a perfect carrier landing? Thanks a lot Achim
    Hi,

    I solved this issue yesterday by installing the gauge into the T-45 Goshawk Vcockpit02. I previously created a new Vcockpit01 for it, but this is not foreseen. So, the installation in Vcockpit02 solved this issue.

    Save landing and stay healthy
    Achim

  12. #12
    I had a similar experience last month when we started testing a new ship that uses the gauge. I ended up removing everything
    and reinstalling the entire gauge. That was probably overkill but I've worked with this gauge for so many years it's very a very
    quick process for me to scrape it off and reinstall. Just a suggestion.

  13. #13
    Hi
    Sorry for this confusion.
    The previous documentation (29/02/2020) of the RFN gauge 5.0 was :
    D) In section [VCockpit01] add the following lines after the already declared gauges:

    Because some aircrafts may have not a [VCockpit01] the install in the documentation (14/06/2020) is:
    D) In the first [VCockpitxx] section, add the following lines after the already declared gauges:

    Regards
    Michel

Members who have read this thread: 0

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •