Betaflight FC motor pin testing and fixing

This is an example of testing a bad Omnibus F3 flight controller. You can see how 5 of the pins do not connect to the chip. Each pin should show continuity to a pin on the IC.

Often only one pin-out if broken but in this case 5 of them do not show any connection to the IC. In cases of only 1 or 2 broken pin-outs, you can use the resource parameter to fix the problem. Changing the motor or servo pin to another ID.eg

The pin-out diagram for STM32F303 shows each as P for pin and the ID xx.eg PB7

PB7 equates to b07 in the Betaflight resource set.

# resource
resource BEEPER 1 C15
resource MOTOR 1 B07
resource MOTOR 2 B09
resource MOTOR 3 A03
resource MOTOR 4 A02
resource MOTOR 5 B08
resource MOTOR 6 B06
resource PPM 1 B04
resource LED_STRIP 1 A08
resource SERIAL_TX 1 A09
resource SERIAL_TX 2 A14
resource SERIAL_TX 3 B10
resource SERIAL_RX 1 A10
resource SERIAL_RX 2 A15
resource SERIAL_RX 3 B11

If you concider the numbers on the right as the set of outputs you can use you can reassign them to any motor. The default order is as you see here for my FC but yours may be differeent, so you need to check.

# resource
resource BEEPER 1 C15
resource MOTOR 1 B08 (was motor 1 connector 1 but now motor 1 on connector pin 5)
resource MOTOR 2 B09
resource MOTOR 3 A03
resource MOTOR 4 A02
resource MOTOR 5 B07 ( as above but connector pin 1 is now motor 5)
resource MOTOR 6 B06
resource PPM 1 B04
resource LED_STRIP 1 A08
resource SERIAL_TX 1 A09
resource SERIAL_TX 2 A14
resource SERIAL_TX 3 B10
resource SERIAL_RX 1 A10
resource SERIAL_RX 2 A15
resource SERIAL_RX 3 B11

You can remove a motor (one not being used) by type
"resource motor [motor number] none"

Thats it. Now you are free to swap and change your motor any which way, if the connector pins don't work and you have enough working.

Cheers

This entry was posted in UAV. Bookmark the permalink.