Random motors not working in betaflight

[SKuhn68]

I am having issues with a Y6 drone I am building. The following equipment is currently in use:
SkyHero Spy 600mm frame
HGLRC Specter F722 pro flight controller
DJI E305 hex propulsion set with 420 lite ESC's
Matek XT60 equipped PDB
TBS Crossfire Nano RX
I have updated all firmware and calibrated the ESC's.
The problems I am having center around the motors. I can't seem to get all 6 of the motors to arm at the same time. This is regardless of whether I am connected to Betaflight or just using my transmitter. Some of the motors will arm (usually 4 of them) but not all. I have tried connecting the motors that won't arm to outputs used by the motors that do arm and they then arm just fine but then some of the motors that previously were arming now won't arm. Switching everything back to the original arrangement 4 motors still arm but now they are different motors. For instance, say originally that motors 1,2,3 and 5 were arming and 4 and 6 were not. After switching out puts then switching back motors 1,3, 4 and 5 would arm but 2 and 6 would not. I thought maybe for some reason or another the flight controller was only capable of running 4 motors at a time (even though there are 8 outputs) so I disconnected 5 and 6. Then only 3 would arm so I disconnected number 4 and only two would arm. Disconnected number 3 and only 1 of the two remaining motors would arm. and so on and so on. I have had as many as 5 of the 6 arming at once but never all 6. The weirdest part is that it isn't the same motors that arm or won't arm all the time, everytime I disconnect a motor the order changes. I am at a loss and any help would be greatly appreciated. If there is any additional info I can provide please just let me know and I will do my best to provide it.
Thanks,
SKuhn68

 

[LitterBug]

Can you give us a copy of the betaflight settings you are using? (output of diff)

 

[SKuhn68]

Can you give us a copy of the betaflight settings you are using? (output of diff)

Gladly,
# DIFF all

# version
# Betaflight / STM32F7X2 (S7X2) 4.5.1 Dec 2 2024 / 10:46:06 (77d01ba3b) MSP API: 1.46
# config rev: cb1d3ac

# start the command batch
batch start

# reset configuration to default settings
defaults nosave

board_name HGLRCF722MINI
manufacturer_id HGLR
mcu_id 0021003f3233510833373334
signature

# name: SPY

# feature
feature GPS
feature TELEMETRY
feature LED_STRIP
feature OSD
feature ESC_SENSOR

# serial
serial 0 2048 115200 57600 0 115200
serial 1 64 115200 57600 0 115200
serial 3 2 115200 57600 0 115200
serial 5 1024 115200 57600 0 115200

# mixer
mixer Y6

# beacon
beacon RX_LOST
beacon RX_SET

# aux
aux 0 0 0 900 1300 0 0
aux 1 1 2 900 1300 0 0
aux 2 2 2 1300 1700 0 0
aux 3 6 2 1700 2100 0 0
aux 4 46 1 1300 1700 0 0

# master
set acc_calibration = -23,-6,2,1
set min_check = 1070
set blackbox_disable_setpoint = ON
set blackbox_disable_bat = ON
set blackbox_disable_alt = ON
set blackbox_disable_rssi = ON
set blackbox_disable_gyro = ON
set blackbox_disable_gyrounfilt = ON
set blackbox_disable_acc = ON
set blackbox_disable_gps = ON
set min_throttle = 1050
set motor_pwm_protocol = PWM
set align_board_yaw = 180
set small_angle = 180
set gps_sbas_mode = AUTO
set gps_ublox_use_galileo = ON
set gps_set_home_point_once = ON
set pid_process_denom = 16
set debug_mode = DSHOT_RPM_ERRORS
set craft_name = SPY

profile 0

profile 1

profile 2

profile 3

# restore original profile selection
profile 0

rateprofile 0

rateprofile 1

rateprofile 2

rateprofile 3

# restore original rateprofile selection
rateprofile 1

# save configuration
save
#

 

[Merv]

Gladly, how do I do that? CLI status? Just walk me thru it.

Yes, go to CLI, type diff all & hit enter.
Copy the output & paste it here

 

[LitterBug]

I only see 4 motor outputs on that board. what are you using to connect motor 5 and 6? Pictures??

Oh wait, this is the pro but it uses the mini firmware. Hmmm.

 

[SKuhn68]

I only see 4 motor outputs on that board. what are you using to connect motor 5 and 6? Pictures??

Oh wait, this is the pro but it uses the mini firmware. Hmmm.

That is correct, it confused me too at first. There are 8 motor outputs as far as I can tell.

 

[LitterBug]

Looking for a loose FC that I can use to mock this up. A Y6 is one of the layouts I haven't played with but have thought about doing. I have quite a few tricopters that I could convert. I've thout about converting one to y4 also. The Y6 would alleviate the issues with the tail servo, but keep the benefits of the Y layout.

 

[SKuhn68]

Looking for a loose FC that I can use to mock this up. A Y6 is one of the layouts I haven't played with but have thought about doing. I have quite a few tricopters that I could convert. I've thout about converting one to y4 also. The Y6 would alleviate the issues with the tail servo, but keep the benefits of the Y layout.

Let me know if you come up with anything, I still haven't figured out my issue.

 

[LitterBug]

My gut reaction is that the M5-M8 pads may not be mapped in BetaFlight, or mapped incorrectly.

If you go in to the motors tab, have you tried each motor individually to figure out which pads are working, and which are not? (props off during testing)

 

[LitterBug]

From CLI, type resource and hit return. It will show the resource mappings including the motors. Should look something like this, but probably not exactly like this.... ( I trimmed most of the rest off too)

# resource
resource BEEPER 1 B02
resource MOTOR 1 C08
resource MOTOR 2 C09
resource MOTOR 3 A08
resource MOTOR 4 A09
resource LED_STRIP 1 B03
resource SERIAL_TX 1 B06
resource SERIAL_TX 2 A02
resource SERIAL_TX 3 B10
resource SERIAL_TX 4 A00
resource SERIAL_TX 5 C12
resource SERIAL_TX 6 C0
....

(the rest has been cut)



You can see on my FC that only 4 motors are mapped.

 

[SKuhn68]

From CLI, type resource and hit return. It will show the resource mappings including the motors. Should look something like this, but probably not exactly like this.... ( I trimmed most of the rest off too)

# resource
resource BEEPER 1 B02
resource MOTOR 1 C08
resource MOTOR 2 C09
resource MOTOR 3 A08
resource MOTOR 4 A09
resource LED_STRIP 1 B03
resource SERIAL_TX 1 B06
resource SERIAL_TX 2 A02
resource SERIAL_TX 3 B10
resource SERIAL_TX 4 A00
resource SERIAL_TX 5 C12
resource SERIAL_TX 6 C0
....

(the rest has been cut)



You can see on my FC that only 4 motors are mapped.

# resource
resource BEEPER 1 C13
resource MOTOR 1 C08
resource MOTOR 2 C09
resource MOTOR 3 A08
resource MOTOR 4 A09
resource MOTOR 5 B00
resource MOTOR 6 B01
resource MOTOR 7 A10
resource MOTOR 8 B04
resource LED_STRIP 1 B03
resource SERIAL_TX 1 B06
resource SERIAL_TX 2 A02
resource SERIAL_TX 3 B10
resource SERIAL_TX 4 A00
resource SERIAL_TX 5 C12
resource SERIAL_TX 6 C06
resource SERIAL_RX 1 B07
resource SERIAL_RX 2 A03
resource SERIAL_RX 3 B11
resource SERIAL_RX 4 A01
resource SERIAL_RX 5 D02
resource SERIAL_RX 6 C07
resource I2C_SCL 1 B08
resource I2C_SDA 1 B09
resource LED 1 C14
resource LED 2 C15
resource SPI_SCK 1 A05
resource SPI_SCK 2 B13
resource SPI_SDI 1 A06
resource SPI_SDI 2 B14
resource SPI_SDO 1 A07
resource SPI_SDO 2 B15
resource ADC_BATT 1 C02
resource ADC_RSSI 1 C00
resource ADC_CURR 1 C01
resource PINIO 1 C03
resource PINIO 2 A15
resource FLASH_CS 1 B12
resource OSD_CS 1 B02
resource GYRO_EXTI 1 C04
resource GYRO_CS 1 A04

 

[LitterBug]

So it appears you do have 8 motor pads mapped. That is a good thing.

Have you tried using the motor tab in the betaflight configurator to test each motor individually?

What motor protocol are you using? PWM, Oneshot, dshot?

 

[SKuhn68]

So it appears you do have 8 motor pads mapped. That is a good thing.

Have you tried using the motor tab in the betaflight configurator to test each motor individually?

What motor protocol are you using? PWM, Oneshot, dshot?

I am using PWM and yes, I have gone into the "Motor" tab in Betaflight and tested each individual motor. That is how I know exactly what motors are arming and which are not. Right now I have 5 out of 6 of them arming. I just can't seem to get motor #4 to arm, tomorrow I plan on trying to disconnect that motor only and try a re-calibration on that motor all by its lonesome. That way I don't accidentally un-calibrate (yay, new word) the ones that seem to be working properly. I will post any positive results.
SKuhn68