I just recently bought the Logitec Switch and Radio Panel. Already had 2x Saitek Throttle Quadrant.

I am (still) using FSX, Win7(64), FSUIPC4 (registered) and LINDA 3.1.1

All Logitek Panels are fine (and fast) when I use the Logitec Driver and "LogiFlightSimX.exe" is running. But of course I cannot do any programming of buttons. Thats why LINDA comes into play. But as soon as LINDA is used, things go wrong. LEDs go OFF after the first switch on the Radio Panel is used, frequncies are not switched all sorts of things. Possible driver conflict.

Thus I uninstalled all Logitec Drivers even used RegEdit to remove them from the registry. But LINDA never worked the LEDs as expected. I tried GUI and LUA setup to no avail. For me the best solution would be, that LINDA only worked the Switch Panel and does not interfere with the Radio Panel, because the Logitec Drivers do that very well and there is no need to reprogram those. The problem is, that as soon as I tick "Saitek Panels" on the "Setup LINDA" page the GUI starts to also interact with the Radio Panel. How can this be stopped?

LINDA should only recognise the buttons of the Switch Panel and let me reprogram those. 

Edited January 6, 20224 yr by EchoCharly

Sorry, should have posted this in the LINDA support forum. Got it wrong.

Is there a way for _me_ to move it elsewhere after editing is no longer possible?

Or if not, can please someone move it to the correct place. Thanks ...

Edited January 7, 20224 yr by EchoCharly

After a good sleep, I continued my investigation (standard blue C172) on the topic. All boils down to the following:

After killing the running "LogiFlightSimX.exe"  with TaskManager,  LINDA works well in GUI and in LUA mode.

After doing an  ALT-Contr-R in FSX screen,   on the SwitchPanel  the LEDs rotate and on the RadioPanel all LEDs show dashes.

Switch on SP --> all well LEDs stop rotating, SP switches are active.

Switch on RP --> Dashes go away and all LEDs are OFF (although VC shows the radio stack on)

Everything works as expected, changing frequencies, operating STBY button. VCockpit shows all fine !!

BUT THE LEDs ON RP STAY OFF !! 

What part drives those LEDs and is there any Saitek or Logitec driver needed to get those LEDs working?

 

RP is connected to a powered HUB and I am on WIN7(64bit) so its not a power problem. Also when I do NOT use LINDA but the Logitec-all-in-one-driver    "FSX_Plugin_x64_Software_8.0.150.0"   all LEDs and switches are fine and responsive, but of course I cannot programm anything.  I want LINDA !!

 

Edited January 7, 20224 yr by EchoCharly

OK finally, a little success !!

After deinstalling all Logitec drivers (again...)  and cleaning the registry, all is up and running although very slow.

I can ONLY use the LUA setup, that is "Saitek Panels = unticked"   and   "Radio Panel = ticked."  Then all is up and running fine.

As soon as I switch to the GUI ("Saitek Panels = ticked,  Radio Panel = unticked) then the Radio Panel LEDs  show  all those Dashes  and as soon as I klick or turn any knob, LEDs go OFF. I can manipulate the frequencies via the RP rotaries much faster than via the LUA version, but the LEDs stay OFF.   Switch Panel is working OK.

So there  _must_  be a problem in the GUI when it drives the LEDs.

I use   "LINDA 3.1.1.854"    and    "FSUIPC 4.975a (registered)".

Should I try a differen LINDA/GUI version ?

 

Regards, and thanx to everybody who followed me up to here.  

(sorry, I am not native english speaking)

-ernst

 

You can disable individual joystick device by unticking the Enabled checkbox in the lower part of the Setup Joysticks page. As FSX is not available to me I can not look at any changes to the current Saitek/Logitech panel logic.

Andrew,

where can I download older versions of LINDA?  Say 3.1.0 or 3.0.12c ...

As I already mentioned, the LUA approach works OK although very, very slow when dialing frequencies, and the GUI setup leaves me with emtpy frequencies.

BUT:

By accident I switched the device selector to DME and XPDR and BAM ...  then I see a correct reading of the DME speed (upper display left)

and correct QNH on the lower right panel during my flight. So panel is working (somehow) but the data sent from the GUI cannot be interpreted or is wrong.

See my DropBox link:           https://www.dropbox.com/s/e1fo74b8vnza0rt/Foto%2009.01.22%2C%2017%2003%2026.jpg?dl=0

You did some "Internal GUI changes"  in Ver. 3.1.0 (see release notes), mayby .....

So I am willing to test some older versions on my setup.