Drone Won't Arm Unless Connected to Betaflight

[Jocko]

Not in the video.

 

[droneguy]

Not in the video.

What version of BF is on the FC?

 

[Jocko]

# dump

# version
# Betaflight / STM32F7X2 (S7X2) 4.2.6 Jan 5 2021 / 19:08:42 (a4b6db1e7) MSP API: 1.43
# config: manufacturer_id: LMNR, board_name: LUXF7HDV, version: 8f0c8286, date: 2020-08-18T22:02:36Z

 

[droneguy]

It's hard to tell, but If it's one long... and three short. Looks like a high throttle condition
or maybe two long and three short then its a calibration issue.

Each long beep represents 5, while each short beep represents 1. The final flag number can be calculated as 5 x <the number of long beeps> + <the number of short beeps>.

Name	Description	Beep code	Required Actions
							4.2+
NOGYRO	A gyro was not detected	1	1				1	You may have a hardware failure, if a previous firmware version works then it may be a firmware issue.
FAILSAFE	Failsafe is active	2	2				2	Rectify the failure condition and try again.
RXLOSS(1)	No valid receiver signal is detected	3	3				3	Your receiver is either faulty or has no link to the transmitter.
BADRX(1)	Your receiver has just recovered from receiver failsafe but the arm switch is on	4	4				4	Switch the arm switch off.
BOXFAILSAFE	The ‘FAILSAFE’ switch was activated	5	5				5	See FAILSAFE
RUNAWAY	Runway Takeoff Prevention has been triggered		6				6	Disarm to clear this condition.
CRASH	Crash Recovery has been triggered						7	Disarm to clear this condition.
THROTTLE	Throttle channel is too high	6	7				8	Lower throttle below min_check.
ANGLE	Craft is not level (enough)	7	8				9	Level craft to within small_angle degrees (default 25).
BOOTGRACE	Arming too soon after power on	8	9				10	Wait until pwr_on_arm_grace seconds (default 5) have elapsed.
NOPREARM	Prearm switch is not activated or prearm has not been toggled after disarm	9	10				11	Toggle the prearm switch.
LOAD	System load is too high for safe flight	10	11				12	Revisit configuration and disable features.
CALIB	Sensor calibration is still ongoing	11	12				13	Wait for sensor calibration to complete.
CLI	CLI is active	12	13				14	Exit the CLI.
CMS	CMS (config menu) is Active – over OSD or other display	13	14				15	Exit the CMS (or OSD menu).
OSD	OSD menu is active	14	15					Exit OSD menu.
BST	A Black Sheep Telemetry device (TBS Core Pro for example) disarmed and is preventing arming	15	16				16	Refer to the manual for your hardware.
MSP	MSP connection is active, probably via Betaflight Configurator	16	17				17	Terminate the Betaflight Configurator connection (disconnect).
PARALYZE	Paralyze mode has been activated						18	Power cycle/reset FC board.
GPS	GPS rescue mode is configured but required number of satellites has not been fixed						19	Wait for GPS fix or disable GPS rescue mode.
RESCUE_SW	GPS Rescue switch is in an unsafe position						20	Turn off the GPS Rescue switch to arm.
RPMFILTER(2)	Motor RPM-based filtering is not functioning						21	One or more ESC’s are not supplying valid RPM telemetry.
REBOOT_REQD	Reboot required						22	Reboot the flight controller for settings changes to take effect.
DSHOT_BBANG	DSHOT Bitbang is not working						23	(3)
ACC_CALIB	Accelerometer calibration required						24	Calibrate the accelerometer or disable features that use it
ARMSWITCH	Arm switch is in an unsafe position	17	18				25	Toggle the arm switch to arm.

 

[droneguy]

Just by chance have you ever done a calibration of the accelerometer?

 

[Jocko]

Yes, it has been calibrated.

I can't tell if it's 2 long and 3 short or 1 long and 3 short.

I'm going to walk away from this for now and see what GetFPV can do.

Thanks again for your time. I'll let you know if/when we find a solution.

 

[droneguy]

Did you get this resolved?

 

[Jocko]

FC. GetFPV overnighted me a new FC and, BAM!, good to go!

I really appreciate you taking the time to troubleshoot the issue with me.

 

[droneguy]

Awesome! Glad to hear you are up and running!

 

[kvrnd]

Hello Jacko,

I have the same issue like you.

Do you know how can I solve?

Kind regards

 

[Stevefpv]

Ok so no other flags. Have tried turning off the wait for satellites before arming flag in BF just to eliminate that possibility? Some GPS still take a min or more on a warm start and the number of satellites doen't always update right away. I may still show the old number from the previous flight or even default the display at 8 till until the warm start is complete.

So I have been going nuts I have flown this iflight titan xl5 and it’s got a gps but I haven’t activated it fully yet, and today I put some new 6s motors to convert from 4 to 6s and it just WONT arm, I did eveything obv like the low throttle etc but nothing and I have like 20 quads so I know it’s not the radio. I’m realizing this is my only gps and it had no problem spinning props on betaflight AND beeped plus tutle mode works. I’m wondering if that’s why, I also have beta 4.2 on the fc it says when I went to change the prop direction but I don’t feel comfortable I’m afraid of loosing the cli. My ig is @_stevefpv if you wanna dm me I never am on here but I’d appreant anyt help, I’m wondering if this is just bc It still needed to get satilites? But it also said update fw yet spun motors besides when I’d arm and I changed to other aux buttons to make sure it’s not my radio. Thanks in advance