IAS button on Multi Panel (Logitech)

User Support Hub Hardware & Peripherals
1

Hi folks.
Finally got my Logitech Multi-Panel working (the auto pilot one).

The only oddity at the moment is the IAS button. When I click it, it doesn’t light up or show in the flight sim as engaged. I always need to click the flight sim IAS button. All other buttons are fine.

I have tested the button with the Logitech test panel tool and it does register and light up.

Just a bug at the moment with the Logitech plugin?

Oh, one other oddity - the panel does not appear in windows USB game devices or in the Flight Sim as a controller. Doesn’t stop working, just odd.

1 Like
2

It is normal, it is no a Human Interface Device as windows intend it, it connect directly to the simconnect library. about the IAS button cannot help since I do not use the logitech driver but the Spad.next utility that give me much more control on how the device interact with the sim…

3

thanks. Yes thinking of spad.next, but another £25 after spending £75 on the panel :man_facepalming:t2:
but may save a load of grief!

4

it really did :slight_smile: but you can always open a ticket with Logitech and see what the say…

1 Like
5

You get a LOT with Spadnext for that price. I run all my I/O through it now because it switches profiles automatically with planes. And I have real control through Simconnect that MSFS doesn’t have as assignable actions.

2 Likes
6

switching profiles is great - it’s what I liked about fsuipc on FSX

7

I also have a Logitech Multi Panel, the IAS button and light don’t work. Has anyone found a solution ?
The test utility only works with the 32-bit Windows. Can anyone share a link for the x64 version of the test software. Thanks.

8

Same here, got the panel but IAS button does nothing.

For the Modorra, bit late but the 64-bit version is there also on the same site, just choose the different download with the same name.

9

Yup, same here. You have to use spad.next to give out another function. Unfortunately, I found that when I use spad.next, each and every button and switch on each panel doesn’t seem to follow what it’s set to on the actual panel until you use it once in the sim.

E.g. starting in a c152, even if all the switches are physically off, everything will still be on in the sim.

At least with the logitech plugin, you only have to press ONE button or switch and then the sim reacts to how you’ve got the switches set… but with spad.next, each button needs to be “woken up” separately… not sure if I’m explaining it well.

10

I just got this panel and found the same thing. So odd. A shame, because otherwise it works great!!

11

Just got the panel. Same issue here.

12

You need an aircraft with IAS mode modelled within its own system and then the MP will interact with it. At least, this was the case with FSX and I haven’t used anything within MSFS that does, although thinking about it, the Caravan, TBM and CJ4 might.

13

I am thinking of getting this same panel. If I understand, the IAS button should be the equivalent of FLC? And/or autothrottle speed? That would be a bummer if it doesn’t work, though I might invest in the Spad.next.

Also, per the CJ4 Working Title documentation, “Autopilot modes cannot be triggered via key bindings or controllers and must currently be triggered in the cockpit with the mouse.” Does that include using this controller as well? That would be extra sad, since much of my flying is in this aircraft.

14

It’s not so much that it’s “broken”… the panel only does what it’s supposed to do…flc and ias are (from my limited knowledge), basically the same thing? But they are not labelled the same in different aircraft systems? The panel only has an ias button, so any system that it’s labelled as flc will not operate using this button.

The AP can be triggered on and off using the button on the panel though.

Also, if you really want the ias button to operate flc control, you can use something like spad.next to set all the buttons to whatever you like.

Personally, I couldn’t get on with spad.next, because I couldn’t find how to have EVERY button always synced with the sim on my other panels too…e.g. if the sim is showing beacon on and nav on at the start of a flight, even if both switches are physically off… you’d think that switching SOMETHING on the panel would then sync up all the buttons so that the sim matches the panels… but I found that, in the example above… if I switch the physical button for beacon to ON, that button then worked and matched the sim… but the nav light button is still ON in the sim… even if the physical switch is still OFF.

Found that very confusing and not really workable… what’s the point in having physical buttons if they don’t ALL sync up with the sim?

Anyway, that’s my rant over regarding spad.next.

But yeah, it’s still a great panel. Makes switching ap on and off very simple, you can also easily switch nav mode, vs mode, hdg mode, approach mode etc. The trim wheel is a great addition if you don’t have another trim wheel and the flaps level is also nice to have.

I have 2 touch screens for using an in flight sat nav like a g1000 or whatever, but I still usually use this panel for setting target alt and vs. Its a great bit of kit, especially if you’re going down the logitech build, because the panels all stack together.

Despite it’s small drawback with the ias button and lack of customisation without 3rd party software which in my experience doesn’t work properly… it’s still worth having in your setup I’d say.

Plus, only other route really would be to start building your own button boxes I guess?

1 Like
15

I contacted Logitech about this issue and they confirmed it’s a known issue, although they have only one report about it, so they have no time line or intend to fix it for now. I suggest more people to contact Logitech so they would actually care.