Flight Controller Passthrough

flight controller passthrough is only supported on configurator versions ≥ 1 12 0 flight controller passthrough is in beta bugs or instability may be encountered flight controller passthrough (fc passthrough) enables the hargrave configurator to communicate with hargrave motor controllers through a flight controller using the serial (dshot/pwm) signal lines flight controller requirements the flight controller must support serial passthrough using the blheli 4 way interface the flight controller must also support msp serial communications the following common flight controller firmwares have been tested with and confirmed to work ardupilot copter 4 6 2 betaflight 4 5 1 inav 8 0 0 other versions of flight controller firmware are likely to work, depending on the implementation of the msp serial protocol other flight controller firmwares (e g kiss) have not been tested and are not guaranteed to work configuration the flight controller must be correctly configured for fc passthrough to work as expected it must have the correct number of motor outputs configured and assigned to the correct motor controller outputs some flight controllers will also require passthrough to be manually enabled in its configuration, please consult the documentation for your specific flight controller firmware motor controller requirements the motor controller must have firmware supporting fc passthrough and be connected to the flight controller correctly for serial throttle control (dshot/pwm) please consult the integration guide in your motor controller's documentation for wiring details connecting with passthrough open the connection manager to connect to the flight controller, first open the connection manager select passthrough create a new passthrough connection by clicking the 'passthrough' button select the com port of the flight controller select the com/serial port for your flight controller, this interface will look different depending on whether you are using the web based configurator or the offline version connect to motor controllers select which motor controllers to connect to and click connect auto reconnect devices connected using fc passthrough support the same auto disconnection and reconnection features as other connection methods to support auto detection, devices that have previously been discovered are periodically scanned auto connection detection may not work as desired during operations that communicate with a passthrough device device scan the device scan process can be started with the 'device scan' button in the connection manager use the device scan if a device is not appearing in the list of available devices during a device scan the configurator will try to establish a passthrough connection with all possible configured motor outputs of the flight controller that have not already been discovered troubleshooting if a device is not showing up as available to connect to over passthrough or the configurator is failing to connect to the flight controller it is recommended to restart the flight controller and power cycle the motor controller and try again