I have realityXP 530 V2 running successfully in FSX SE as part of my Aerosoft Twin Otter DHC6-300 float plane cockpit. 

Prior to installing reality XP the Saitek Radio Panel was working correctly, I was primarily using it to display and control Com2, Nav2, ADF, DME and XPDR.  It can also display and control COM1 and NAV, but this was being done directly via the original 530 unit display and controls.

After installing the RealityXP 530 V2 the outer (MHz) rotary selectors of the Saitek Radio Panel no longer work, oddly the inner (kHz) rotary selectors function correctly. In all cases the displays on the Radio Panel correctly display the frequency selected by the RealityXP 530 V2 gauge.

I realise that this is a bit of a specific question, what would be helpful though are any insights other users might have. In particular where to go looking for what appears to be a control conflict between the two.  As yet I have not found a post that covers this, apologies in advance if I have missed it.

Hi,

Is this both COM and NAV outer knobs not working on the Saitek?

Is this also not working when using the Saitek COM2/NAV2 outer knobs with a GNS #1, or using a Saitek COM1/NAV1 outer knobs with a GNS #2?

Hi Jean-Luc,

Many thanks for your reply,  hopefully your questions are answered below:

Both of the Saitek outer control knobs are inopperative (in all Saitek modes).  I hesitate to refer to them as COM or NAV as they are multifunction controls whose behaviour depends on two additional rotary switches whose selected position will configure them to be one of  COM1, COM2, NAV1, NAV2, ADF, DME or XPDR.  

In my setup (RealityXP.GNS.ini) I only have a single instance of the Reality XP 530 .... shown as GNS_530_1.  I'm guessing this is what you mean by the GNS #1 shorthand?.  To answer your question though the Saitek knobs are inopperative with the GNS #1 for COM2/NAV2.  I have not tried using the saitek COM1/NAV1 controls with a second instance of the GNS as there is no second unit in my cockpit.

I'm not sure if I am correct but this problem seems to suggest that the Reality XP commands to FS are all working correctly but someting is inhibiting the outer rotary GPS commands from the Saitek Panel.  Usually it is best to avoid two controllers controlling the same FS functions however it is odd that this problem only effects the outer rotary controls.

 

 

 

 

I'm short on suggestions but: do you "Use Simulator GPS Commands" setting?

The GNS is solely syncing the COM and NAV simulator frequencies bidirectionally (GPS <=> SIM) but it is not interfering with the COM/NAV events (inc freq/dec freq etc...). However with this setting it is intercepting all 'GPS' FSX events and could it be Saitek is using one of these to 'handle' their switch and knobs event through their driver?

 

Hi Jean-Luc

Good suggestion, I am using the 'Use Simulator GPS Commands' setting in the .ini file.  I will play with this setting and see if it affects the behaviour of the Saitek Radio panel. 

I use Spad.Next to interface with all of my devices.

I have RXP GNS530 setup as the Number 2 Unit (GTN750 is number 1)

I have no issues with the Saitek Radio Panel and controlling COM 1 or COM 2 with it.

When I first got into Flight Sim in 2015 (what was I doing all those years!!!) I could not stand the Saitek software as it would crash and lock up.  I found this Spad.Next software and have loved it ever since...My GNS 530 controller is just a Display/3D Printed Bezel and an Arduino Leonardo that I have configured as a "HID Joystick".  All of these allow me to program on a Plane by Plane basis but when it comes to the Saitek stuff you get to dump the Logitech software and just run it....Then you can modify all of the controls beyond the standard profiles and the like.

Hi Les,

Many thanks for adding your thoughts. As yet I have not had time to look at Jean-Luc's suggestons, however the issue of the Saitek driver is definately on my list to explore.  Good suggestion on using spad.next, this will be one of the things I will try next. Spad seems to get very good reviews.

Out of curiosity did you have any difficulty removing the original Saitek driver before adding spad?  I have tried deleting it (windows 10 OS) and reinstalling it as one of my orighinal fault finding tests, however it never really seems to be properly deleted....

For info my set up was using the latest Saitek driver and binding the controls using the Linda Saitek library.

 

On 6/10/2020 at 2:50 AM, juniper said:

Hi Les,

Many thanks for adding your thoughts. As yet I have not had time to look at Jean-Luc's suggestons, however the issue of the Saitek driver is definately on my list to explore.  Good suggestion on using spad.next, this will be one of the things I will try next. Spad seems to get very good reviews.

Out of curiosity did you have any difficulty removing the original Saitek driver before adding spad?  I have tried deleting it (windows 10 OS) and reinstalling it as one of my orighinal fault finding tests, however it never really seems to be properly deleted....

For info my set up was using the latest Saitek driver and binding the controls using the Linda Saitek library.

 

Sorry -- Forgot to turn on "Notify Me" and thus I have not seen this till now.......When I built my "New" Main Sim PC (I have 3 in the setup) It was ground up with windows 10 and just plugged everything in and then used Spad.Next from out of the gate.  Never Installed the Saitek/Logitech Software.

I am sure some basic Drivers are installed but nothing more and that is fine.  Really with those panels it is the Saitek Software that you don't want installed as it sucks and will have it's self put into the .exe and .dll sim auto run stuff...Note that in the past also just disabling those lines in the config files also helped keep them from running....but never having installed to begin with is always best.

What I find the real offender with a lot of this is the Windows USB Power Management stuff.....This will cause the to stop working during times of lack of input,  You really need to get those disabled and also head over to the Spad.NExt Forum as they just posted an app to help deal with the recent changes to the USB Power Management again......Also I have seen that after some Windows 10 updates I have to go back through a lot of the USB devices and turn off the power management again.......it's really annoying that you can not do this with a global setting....