Logitech FIPs working erratically

User Support Hub Hardware & Peripherals
1

Greetings fellow flightsimmers,

Before posting this I did extensive research on various boards and fora to see if anyone else had come up with a suitable solution. I am hoping that by providing some additional information, someone out there may have an idea on how to fix this ongoing problem:

SITUATION: I have a dedicated flightsim rig which includes 6 Logitech FIPs. The rig is running Windows 10. Each time I boot up the computer, certain FIPs are not recognized by either the computer of the SPAD.neXt software which I am currently using, thus requiring a restart of the FIPs by disconnecting and reconnecting them. All advanced power management features in the computer have been turned off (verified multiple times) and the FIPs are plugged into 2 USB 2.0 hubs which in turn are plugged into two USB 2.0 connectors on the computer (so I have 3 FIPs running on each hub). I know that the FIPs are notoriously power hungry -some say 1.0 to 1.5 amps at startup which is odd given that I understand the max power rating for USB 2.0 to be 500mA).

BOOT UP OBSERVATIONS: When I turn on my computer, all 6 FIPs come to life, meaning that t all six are being powered as their screens turn a slightly lighter shade of blue. The screens stay this way until Windows starts to load (the white dotted circle appears and turns on the screen). From this point until loading is complete and the login screen appears, the FIPs seem to randomly turn off and on. Once the login screen is up, whichever FIPs are dark need to be manually disconnected and reconnected to be recognized.

While I am not as intimately familiar with the inner working of computer hardware and software, it seems to me that since all the FIPs come on at bootup, the problem may well reside in the Windows bootup sequence. I have also tried turning on the power to the FIPs AFTER windows has completed loading, but that seemed to have no difference either.

Ergo, I am stumped!

I am hoping someone out there may come up with an idea or two, but if noting else, the posting of this message has served as a cathartic release of frustration and amazingly, my keyboard is still in one piece!

Cheers,

Jeff

2

Jkemp1960 - I’m only experiencing the erratic behavior on Logitech’s Throttle Quadrant, which I’ll refer to as TQ, the device is part of the Logitech Control Yoke System. This occurs in MSFS 2020 but not in X-Plane 11, and that’s because X-Plane 11 has the internal capability to calibrate the devices it uses, whereas MSFS 2020 does not because it uses the settings configured in Windows, usually through Control Panel, Devices and Printers. This will usually display all the peripherals that are plugged into the system, whether into a USB or HID port. On my system the capability to calibrate the device is not present for some reason because I replaced the original throttle quadrant that I bought in 2013 when the company was Saitek, I did that 3 weeks ago and now the TQ behaves erratically in MSFS. I suspect the peripheral(s) you’re referring to are also doing that because of the same reason.

Microsoft’s Flight Simulator 2020 web site has an FAQ page and it mentions that they’ll add the capability to calibrate the control peripherals in a “future update” (as stated). I got angry because right now my flight simulator is not usable and I cannot wait for their update, which God only knows how long that will take, and I insisted that they create this update ASAP. So we’ll see, hopefully they’ll add that capability with their upcoming update on July 27th, or sooner.

3

I am new @ this and with Logitech Control Yoke System but acouple of times upon hitting Ready To Fly the yoke in the plane will be jerking spasmaticly. After some research I found out it was do to it loosing it’s Calibration. The first time it happened I went through the entire re-download of the Drivers and all as instructed but have since found that simply unplugging the Yoke System and plugging it back in again usually Fixes it also. It has not happened for a few day so I hope it remains Calibrated for awhile.

4

FWIW, check your USB hubs. I have had problems with USB hubs in the past that seem to be working fine but the devices connected randomly stop working. Not all brands of USB hubs are equal. Some USB hubs are powered by the PC and others that have an external power supply. I recommend using hubs with external power supplies. Also, replace any older USB cables as connectors and shielding tend to deteriorate over time. Hope this helps!

5

Hi, i have exactly the same problem. When i start my pC all of my fips gets energized until w10 starts. Then, some of the fips goes down (erratic) and i have to reconect again one by one. I have an usb hub with external power and power buttons for each usb port, that makes it not so frustrating. Did you solve the problem?. Thanks.

6

Yes, I use this AC mains powered hub which has 13 ports and two switches. By switching those two switches (taping 2 push buttons) all the ports will turn off and then back on. This will power up everything plugged in there. I have two stream decks plugged into it.
It used to be problematic whether these streamdecks would power on with a windows system reboot. Now I just tap those two buttons and everything turns on.
Sabrent HB-U14P powered hub.
https://www.amazon.com/gp/product/B00HL7Z46K/

7

Hi I get the same problem with different computers, different operating systems and different hubs.

Currently Im on Windows 11 and I’m using Sipolar A-832 hub (with a lot of power delivered by 2 external power supply units)

Little knowledge before I will share full script which solving my problem (which I think is caused because all FIP’s starting at exactly the same time making a conflict).

VID and PID

  • VID (Vendor ID): This is a unique identifier assigned to a manufacturer by the USB Implementers Forum (USB-IF). It helps identify the vendor of the USB device.
  • PID (Product ID): This is a unique identifier assigned by the manufacturer to a specific product. It helps distinguish between different products from the same vendor.

In script, VID_06A3 identifies the vendor (Logitech in this case), and PID_A2AE identifies the specific product (likely a flight instrument panel).

Script Explanation

  1. Get all devices with specific VID and PID:
$logitechDevices = Get-PnpDevice | Where-Object { $_.InstanceId -like "*USB\VID_06A3&PID_A2AE\*" }

This line retrieves all Plug and Play (PnP) devices whose instance ID contains the specified Vendor ID (VID) and Product ID (PID). The -like operator is used to match the pattern.
2. Display the devices:

$logitechDevices | Format-Table -Property Name, DeviceID, Manufacturer, Status

This line formats and displays the retrieved devices in a table with columns for Name, DeviceID, Manufacturer, and Status.
3. Disable all devices:

foreach ($device in $logitechDevices) {
    Disable-PnpDevice -InstanceId $device.InstanceId -Confirm:$false
    Write-Output "Disabled device: $($device.Name)"
}

This loop iterates through each device in $logitechDevices, disables it using Disable-PnpDevice, and outputs a message indicating the device has been disabled.
4. Wait for 2 seconds:

Start-Sleep -Seconds 2

This line pauses the script for 2 seconds.
5. Enable devices one by one with a 2-second interval:

foreach ($device in $logitechDevices) {
    Enable-PnpDevice -InstanceId $device.InstanceId -Confirm:$false
    Write-Output "Enabled device: $($device.Name)"
    
    # Wait for 2 seconds before enabling the next device
    Start-Sleep -Seconds 2
}

This loop iterates through each device in $logitechDevices, enables it using Enable-PnpDevice, outputs a message indicating the device has been enabled, and waits for 2 seconds before proceeding to the next device.

Below full script

# Get all devices with VID_06A3&PID_A2AE&MI_01 using -like
$logitechDevices = Get-PnpDevice | Where-Object { $_.InstanceId -like "*USB\VID_06A3&PID_A2AE\*" }

# Display the devices
$logitechDevices | Format-Table -Property Name, DeviceID, Manufacturer, Status

# Disable all devices
foreach ($device in $logitechDevices) {
    Disable-PnpDevice -InstanceId $device.InstanceId -Confirm:$false
    Write-Output "Disabled device: $($device.Name)"
}

# Wait for 2 seconds
Start-Sleep -Seconds 2

# Enable devices one by one with a 2-second interval
foreach ($device in $logitechDevices) {
    Enable-PnpDevice -InstanceId $device.InstanceId -Confirm:$false
    Write-Output "Enabled device: $($device.Name)"
    
    # Wait for 2 seconds before enabling the next device
    Start-Sleep -Seconds 2
}

For troubleshooting problems with USB you might like Windows Driver Kit
[Download the Windows Driver Kit (WDK) - Windows drivers | Microsoft Learn]

After installations in my case tools were at path:
C:\Program Files (x86)\Windows Kits\10\Tools\10.0.26100.0\x64

Especially usefull is usbview.exe

image
image823×322 28.1 KB

I hope it will help you and many others :slight_smile:

8

Hi, one year after, I still didn’t solve the FIPs problem (now I have an industrial 20 ports usb 2.0 hub with external power but it’s not the solution) so I just tried your PowerShell script. It works correctly disabling and re-enabling the FIPS. Those FIPS that looks dead after starting w11 come alive (black screen to brown screen) but after that, SpadNext doesn’t recognize most of them. I,m getting crazy.

Greets, Juan.