Y6 Hex setup randdom motors not arming.

[severe trail]

I apologize if I am not posting this in the correct section but I am new to this forum. That being said, 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 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 now 2 and 6 would not. 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, if there is any additional info I can provide please just let me know and I will do my best to provide it. Now move forward about a week and I have 5 of the 6 motors arming consistantly but can't seem to get motor #4 to arm, it just sits there and beeps. I have attempted re-calibrating the motor several times to no avail. I am basically stuck at this point as I am simply out of ideas. Any help would be GREATLY appreciated.
Scotty68
ps. I will post additional info including an entire dump along with a theory/suspicion in two minutes. (darned slowmode) lol

[willow haven]

✨AI-Generated response✨

This sounds like it could be a mixer configuration issue, or possibly something related to the motor outputs.

• First, ensure you have selected the correct mixer for a Y6 configuration in the Betaflight Configurator under the Configuration tab, as incorrect mixer can lead to unexpected motor behavior. Mixer Types
• Verify that the motor order and direction are configured correctly under the Motors tab. You can use the motor direction test tool there to check each motor individually. Motors Tab
• Double check the ESC calibration, although if some motors arm and some don't, this is less likely to be the issue, but still good to rule out.

If you're still stuck after verifying these settings, it may be helpful to get more specific troubleshooting help in the #1052457584772255784 channel, and provide a full dump of your Betaflight configuration from the CLI dump command within the Betaflight Configurator. This will allow other users to review all of your settings.

[severe trail]

I have been looking at the results of a dump on my drone and I may have found something. Let me start off by saying that I don't pretend to know squat about what I am looking at but I am fairly good at spotting patterns. I am going to post the entire dump but what I am focusing on is the "TIMER" section. What I am seeing is this: notice how all of the "AF" designations coincide with the same "TIM" designations? For example: Every "TIM8" corresponds with "AF3", every "TIM1" corresponds with "AF1", every "TIM3" corresponds with "AF2" but then down at the bottom of the list you have this lonely little "TIM2" thrown in all by itself with the "TIM1's" in the "AF1" category? What I mean is with the exception of the single "TIM2" all the other like "TIM's" are associated with the same "AF" number. All except for the single "TIM2", shouldn't he have an "AF" number all to himself? Again, I don't pretend to know anything about anything, I just thought this stood out as being odd. What are your thoughts?
ps. I just noticed this when I pasted the "Dump" results to this response. In the results I see that the kv setting of my motors is set to 1960, my motors are only 800kv. Don't know if that makes any difference and don't know HOW it got set to 1960 but that number is incorrect. just sayin'
Thanks for your helps so far,
Scotty68

Full "DUMP" to follow

[remote loom]

!supportid

[warped pulsar]

Betaflight Support

Submit Support Data

1. Open the CLI tab
2. Click the "Submit Support Data" button

• Optionally enter a brief description of the problem
• Wait for it to finish

3. Copy the resulting support ID

Check the image below for visual steps:

[remote loom]

No dumps please

(dump is included in support id with additional info)

[severe trail]

Id: "8c257e64-38f2-4f07-a05f-94682d18083c"

[remote loom]

Timers have been utilized

Currently active Timers:
-----------------------
TIM1:
    CH1 : MOTOR 3
    CH2 : MOTOR 4
TIM2: FREE
TIM3:
    CH3 : MOTOR 5
    CH4 : MOTOR 6
TIM4: FREE
TIM5: FREE
TIM6: FREE
TIM7: FREE
TIM8:
    CH3 : MOTOR 1
    CH4 : MOTOR 2
TIM9: FREE
TIM10: FREE
TIM11: FREE
TIM12: FREE
TIM13: FREE
TIM14: FREE

Does it help when you do

use dshot_bitbang = ON
save

In the first place - why do you have

set motor_pwm_protocol = PWM

What protocol is the ESC using ?

[severe trail]

The protocol needed for my ESC is PWM

I do not know what dshot bitbang is or how it was enabled.

also, I do not know enough to control things through CLI commands (noob) so anything that is enabled or disabled got that way via various tabs in Betaflight config. And I will admit, it is VERY possible I made mistakes while attempting to figure this situation out.

[remote loom]

Okay - ignore bitbang suggestion. Reflash with motor protocol PWM instead of DSHOT

Must be very old ESC

[severe trail]

Nope, motor #4 still beeping.

The ESC's are DJI 420 Lite. Brand new but not sure of release date. Was informed on another forum of them being PWM and once switched solved several other issues.

[severe trail]

Okay, I just tried a re-calibration of that motor only by connecting the signal wire of its corresponding ESC directly to channel 3 (throttle) of the TBS Crossfire Nano RX, placing the throttle lever on my Transmitter to full throttle and powering on the receiver. Then waiting for tone before moving the throttle lever to low. The ESC actually accepted the calibration and armed.... I then disconnected it from the RX and reconnected the signal wire to the flight controller and powered everything back up and SAME EXACT PROBLEM. Nothing changed at all, that motor still doesn't arm. It HAS to be something in the flight controller settings/firmware. Please help!

[remote loom]

Perhaps try earlier firmware (4.3.2) - as I'm out of ideas here

If that works go up from there

[severe trail]

I am willing to try earlier firmware but before I do could you take a look at this? I was looking thru the dump out put and came across this. I am focusing on is the "TIMER" section. What I am seeing is this: notice how all of the "AF" designations coincide with the same "TIM" designations? For example: Every "TIM8" corresponds with "AF3", every "TIM1" corresponds with "AF1", every "TIM3" corresponds with "AF2" but then down at the bottom of the list you have this lonely little "TIM2" thrown in all by itself with the "TIM1's" in the "AF1" category? What I mean is with the exception of the single "TIM2" all the other like "TIM's" are associated with the same "AF" number. All except for the single "TIM2", shouldn't he have an "AF" number all to himself? Again, I don't pretend to know anything about anything, I just thought this stood out as being odd. What are your thoughts?
ps. I just noticed this when I pasted the "Dump" results to this response. In the results I see that the kv setting of my motors is set to 1960, my motors are only 800kv. Don't know if that makes any difference and don't know HOW it got set to 1960 but that number is incorrect. just sayin'