# Saitek FIP (Flight Instrument Panel)

For SPAD.neXt to handle the Saitek/Logitec FIP correctly the following steps need to be performed:

* Install the Saitek FIP Drivers. (Download at their webpage)
* After installation, uninstall the "DirectOutput Service"
* MSFS: Uninstall the the Logitec "Flightsimulator Plugin"

For best practices about FIP connection to your PC please see <https://fipgauges.com/hardware.php>

Also note that the [USB HUB requirements](https://docs.spadnext.com/hardware-specific/usb-hub-requirements) apply!

{% hint style="warning" %}
Please note, in contrast to the original Saitek implementation, which limits updates to one device at a time , SPAD.neXt will drive all FIP at full speed with concurrent updates, resulting in up to 16fps per device.\
However, this will draw the full 500mA per deviceport from the hub. Therefor it is **important** to follow the best practices.
{% endhint %}

SPAD.neXt supplies the standard saitek gauges that come with the FIP. For more sophisticated gauges it's recommend to have a look at [fipgauges.com](https://fipgauges.com) or [Fsx times](https://fsxtimes.wordpress.com/category/gauges/)\
Also there are some user created gauges available inside SPAD.neXt and on the Community Discord.

### Error Rendering on Device

This is indicates the device is not getting enough usb power to keep up rendering.\
See [HUB requirements ](https://docs.spadnext.com/hardware-specific/usb-hub-requirements)and the best practice above

### €œThe FIP with Serial XXX did not respond to the initialize request. This can happen if the FIP internally crashed. Please powercycle the FIP.

Latest Windows 11 changes will  turn on and off power to usb devices in a quick sequence while booting. Saitek FIP devices do not support this, becaus ethey have a long bootcycle, and in result will crash internally.\
Best practice is not to plugin the FIP devices before windows is fully booted and running