Knowledge Base

Follow

FaderPort Classic isn't working correctly

We've gotten reports where the Faderport classic are suddenly losing connection completely where either the top 3 rows or the bottom 3 rows will light up showing ample power through the USB bus. This most likely is happening when Firmware Update is attempted using an incompatible USB 3.0 bus device. 

FaderPort (Classic) has 2 USB Modes of operation

  1. Normal Operation it is a USB 1.1 device
  2. DFU / Firmware Update Mode

------------------------------------------------------------------------------------------------------

1) Normal Operation Troubleshooting: 

There are no device drivers for the FaderPort Classic. It is a class compliant MIDI Controller with a motorized Fader. The device driver is controlled by the operating system (Microsoft standard MIDI interface driver for Windows) and (Apple has a MIDI Device driver for class compliant operation in OS X), neither of these are developed or controlled by PreSonus. 

There is an installer to place custom DLL control files in certain DAW programs for the FaderPort to talk to instead of using standard MCU or HUI protocols.

 The Motorized Fader requires the external power supply to drive the motor. If the power supply is not plugged in, the Fader won't move. If the firmware has been changed to an incompatible version than what came installed on the unit, the Fader will no longer move. (If this is your case, skip to DFU section below to learn more about how to correct) 

  • Make sure it is plugged directly into a USB Port on the computer and not through a USB Hub
  • Make sure the correct power supply is being used
  • Low power laptops like ULV (Ultra Low Voltage) / Netbook / MacBook Air may not have enough power over USB port to properly operate.
    • In that case a Powered USB Hub can be attempted. 
      • Do not use a passive (non-powered hub)
      • Powered Hub must provide at least 500mA per USB Port
        • Typical Powered USB Hub will have 500mA greater than number of ports
          • For example 7x Port Powered USB Hub (with 500mA per port ~ 3500mA / 3.5A) should have 4000mA / 4A or greater power supply. 
    • If it's a desktop, plug a dedicated PCI / PCI-e USB 2.0 expansion card into an available slot on the motherboard. This should resolve any connectivity issues as PCI / PCI-e slot has direct access to memory. 
      • You could consider the powered USB Hub option as mentioned above, however if your USB Ports on your desktop are heavily populated, you may have the same issue. 
      • Plugging in an expansion card may be your best option.  
      • If problems persist consider using a different machine.

2) DFU / Firmware Update Mode:

  • Was included in Universal Control starting with version 2.8.0.48221. 
    • Will appear in UC with version 1.45 which is the last firmware update. 
      • Any older version will appear as Version 1.0
      • These older versions may be 1.1, 1.2, 1.35 or 1.38. 
  • When FaderPort Classic is placed into Firmware Update Mode it will show up in Universal Control as firmware 1.0. That is not the version of the firmware, but the version of the Firmware Updater that's embedded in the unit. 
  • If the FaderPort Classic is plugged into USB 3.0 port (Mac / PC) and an update is attempted: 
    • Will throw error code 0x80004005 (generic error indicating that communication is not possible) This only means that the DFU communication could not complete.  
    • The firmware update lights will continue to blink after a failed firmware update. 
    • Disconnect Power, put the unit back in Firmware Update Mode and connect it to a computer with a USB 2.0 Port to reload the firmware to restore functionality. 
      • You may need to find an older computer to gain access to USB 2.0 Ports. 
  • Updating a working unit to a firmware version lower than the version your unit will cause the Fader to stop working. 
    • We fixed a Pro Tools error in 1.45 firmware however there are some that still think the older versions work better and downgrading firmware will bring greater functionality.  
    • There are many older firmware updaters for the FaderPort prior to its inclusion in Universal Control, These older versions may be 1.1, 1.2, 1.35 or 1.38.
      • Each of them have their own stand alone updaters, none of which are supported anymore.
      • Be wary of archived downloads of these older updaters on the internet from other vendors or public file sharing sites. 
    • Using one of these older stand alone updaters will render the fader useless. 
      • Only putting the unit back in firmware update mode and restoring firmware using Universal Control will restore functionality.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk