Assistance Needed: Issues with Motor Pin Configuration and Unidentified Motor Wiring on Holybro X650

Hello,
I am currently building a Holybro X650 and am a beginner in the world of drones. I’ve encountered some issues during the setup process that I’m hoping to get help with.
Issue 1: Motor Pin Configuration Resets
After every restart of the Pixhawk 6x v2a or a reconnection of the battery, I face an issue where the motor pins need to be reconnected in new slots for the motors to work. For instance, if the motors were initially connected to slots MAIN 1-4, I have to reconnect them to MAIN 5-9 after a restart to get them functioning again.

This behavior is puzzling to me, and I’m unsure what could be causing it.

  • Could this issue be related to some internal parameter or setting that I’m missing?
  • Is there a specific parameter responsible for “binding” motor connections to specific outputs?
  • Can this issue be resolved without needing to reinstall or reset the firmware each time?

I’d appreciate any insight into how to resolve this problem and ensure consistent motor pin assignments across reboots.

Issue 2: Unidentified Wiring from Motors
Additionally, I’ve noticed an extra set of wires connected directly underneath each motor. These wires are yellow, red, and black (YRB), and they are separate from the ESC wires (which are white and black). I initially assumed that these YRB wires were somehow related to the ESC, but upon disassembling one of the preassembled arms of the drone, I realized that they come directly from the motor, not the ESC.

The manual provided with the drone did not offer any explanation regarding these wires, and my online research suggests that they may be related to NeoPixel LEDs or some type of motor status indicator. Following this assumption:

  • I connected the yellow wire to an AUX pin on the Pixhawk and configured the respective AUX output in Mission Planner’s Servo Output settings as NeoPixel1 (120) and other related functions.
  • Despite these changes, no effect was observed—the LEDs (if that’s what they are) did not react in any noticeable way.

This leaves me with a couple of questions:

  1. Are these YRB pins indeed for NeoPixel LEDs or something else entirely?
  2. If they are LEDs, could I be missing additional steps for configuration, such as voltage requirements, a specific function in the Servo Output settings, or a relevant parameter?
  3. If they are not LEDs, do they serve any other functional purpose, or are they unnecessary for the operation of this drone?

If any additional information is required I can provide it
Thank you in advance


They are for the LEDs. HolyBro states that there is no native support for the drivers for those LEDs using PX4 but they have a workaround firmware and parameter file you can start with. NeoPixel WS2812 LED Setup Instruction | Holybro Docs

Save that firmware locally, and reflash the FC with it. You don’t have to use their parameter file if you don’t want to. If I recall correctly, AUX 1-4 will default to Motor1, Motor2, Motor3, and Motor4 with NeoPixel as the protocol, and the LEDs will work. They should be green when GPS locked and red on low battery. (Also need to ensure that you’re powering that servo rail or else the LEDs won’t receive any power down their power wires. The rail needs 5V and GND plugged into any slot of the rail. There should be a separate power module somewhere in your kit that doesn’t have a home yet.

Regarding the motor output pins. Put them on Main 1-4. In the actuators tab of QGC, find Main 1-4 and change to Motor1, Motor2, Motor3, Motor4 and ensure that bank of 4 pins is set to PWM400 protocol in the dropdown. The Main pins don’t support DSHOT.

Let me know if that doesn’t solve your issues.

I found the solution described in the manual mentioned above.
This solution involves re-soldering a certain pin (or board) inside the pixhawk.
At the moment I think this is not necessary for my project, also because the pixhawk is glued to the drone frame with double sided tape and I am low key lazy to do it.
I myself will move on to writing documentation and preparing next steps for next year.
Thanks for your help, have a great Christmas! Or Hanukkah