Saitek Flight Panels

It does indeed sound like there’s a fault which was what I suspected - sorry.

@benjack57 Something strange is happening there because when you quit MSFS our plug-in listens for that and should quit. However, if you’re getting the instance already in progress error message when you try and start the sim again then that says that it hasn’t quit when MSFS is shut down, which is not something we’ve seen before.

Clearly you’re able to get the panels working again somehow - what are the steps that enable you to do that? Also, when the panels stop working on starting the next flight, do they start working if you unplug/replug them?

if I restart the simulation it does not work is there a solution to stop the pluging and restart it
thank you

Sorry, that wasn’t clear. Could you clearly answer my last questions about how you get it working again and confirm if unplug/replug make them work too please?

when i land i cut from the flight panel all the screens and the contact then i leave the game. I tried to unplug and re-plug the panels but it s the same it does not work. For this to work I have to shut down the computer and start over, it’s very painful
do you have a solution to restart the plug-in
thank you

Multi Panel worked perfectly with version 8.0.281.0. After updating to version 8.0.285.0 they stopped working. Tried changing ports, reboots, etc. When I look at Windows Task Manager I do not see LogiMicrosoftFlightSimulator.exe running as I did prior to the update.

When I manually run the program (with or without FS 2020 running) I get an error “No arguments use – help for argument list”

1 Like

How about if you run it using the icon on your desktop?

@benjack57 Let us try and replicate but at the very least you should be able to quit LogiMicrosoftFlightSimulator.exe from your Task Manager and then run the icon on your desktop to start the plug-in again.

I received the same error running from desktop. I added the exe.xml to the correct folder and it seems to be working now. I’ll see what happens when I restart the sim or reboot.

That’s odd indeed because the icon on the desktop does include a -run argument! A missing exe.xml file wouldn’t have helped though so putting that in place should get you going every time now.

No I don’t have any 3rd party solutions for the Saitek panels or yoke.

I did try a Spad demo last year, but that only ran for a few weeks then I think I uninstalled it.

I’m convinced there is a firmware/hardware encoder bug, as it appears on Xplane as well as MSFS, and the Logitech panel test program on PC and laptop.

Will Logitech be able to repair/fix this problem?

-Paul

Based on your symptoms it’s a hardware fault with the dial. It’s not firmware otherwise everyone would have the issue, which is not the case - the increment issue you see posted by others is not a double count but rather a multiplication of a factor of 10 on SimConnect increments for the HDG, ALT etc.

We do not have repair workshops that can work on this though, I’m afraid.

The x10 bug is to do with the Honeycomb yoke. If you have any of it’s buttons or switches bound, you get 10 degree, and thousand feet increments. Unbind the switches, and it goes away.

Apparently Warthog users have had this. Theory seems to be any buttons higher then a certain number triggers it. 32 I think.

Richard,

Thanks. I have identified the 3 encoder wires by inspection.

So I’ll unsolder the original encoder and test with a new encoder from my spares box.

Interestingly my Dad used to repair military HUD displays and Boeing autopilots/autothrottles at Smiths Industries UK, who decades ago made many steam guages and gyroscopes.

My Grandfather worked at the Gloucester Aircraft Factory between WW1 and WW2, on the same runway Frank Whittle used for his jet engine experiments in the 1940s.
Most of Grandad’s planes seemed to be made of wood and string ha ha.

Cheers
Paul

3 Likes

Engineering runs in the family then! I love this kind of thing - sincere thanks for sharing.

Anyone got the issue when putting down the gear lever or switching off the landing lights that it switches off other switches too? I got this that also the generators get switched off.

I think I know what you are experiencing. Anytime a switch is flipped or moved on the Saitek switch panel, all switch settings are sent to the simulator for that Saitek switch panel. This means that if you turned NAV lights on with the Saitek switch panel, then later turned them off via mouse inside the cockpit. Your physical NAV light switch on the Saitek switch panel would be on while the simulator NAV switch is off. Now if you Turn on for example PITOT Heat on the Saitek panel. All switch settings are sent to the simulator. Since that NAV light switch was out of sync and left on your NAV lights in the Simulator will come back on. I hope I have explained my thoughts clearly here.

Ah yeah that makes sense. But when I lower the gear the generator switch turns off. I didnt switched off the generator with the mouse in the cockpit either on the panel. It remained on all the time since start up

If you run the panel tester software that’s downloadable from the website, does the landing gear lever cause any of the other buttons to respond when you switch it?

@Tr1cky Count me in on this problem as well. I particularly have a problem with ADF/DME/XPDR. Tuning these often causes the display to cut out as I’m tuning, but it is usually registering the tuning as I go, making it tricky to get the right numbers in.

I’ve also noticed that with the Beechcraft King Air 350 specifically, tuning causes the ACTIVE to change, not the Standby. This is the only aircraft I’ve noticed this with so far.

Have you turned off the Windows power management for the panels as recommended earlier in this thread?

The Beechcraft issue appears to be an aircraft-specific issue which should be reported via Zendesk.

The enhanced power management thing? Yes I attempted that. I only have the radio panel though, and most discussion seemed to be about the Instrument panel but did give that a go.

As to the Beechcraft, I will open a support ticket for that.