Arming issue with betaflight f4 board and 32bit esc

preview_player
Показать описание
Been a while sense I've had an Issue I can't figure out at all. I hope you guys might have some advice for me. Thanks and please don't forget to subscribe

Contact/Mailing
3380 La Sierra Ave #104-150 Riverside, CA 92503

CAMERA GEAR

GOGGLES

MINI QUAD GEAR
Konasty 6' Cougar Frame
6" Motors - Cobra 2206 2100kv
Props- HQ 6x4x3/6x4.5x2
Foxeer Arrow V3

RADIO
Рекомендации по теме
Комментарии
Автор

Eric, not sure what version of Betaflight you are on but get yourself on one of the late October releases of 3.3.0. Default your BFF4 board and flash that hex. Download the blheli32 package and double check that your motors are responding via the pass through. My quads are all on the Betaflight f4 boards (moved over from DYS F4 Pros) and 32bit escs and running dshot1200 @ 48khz. Zero issues 👍

ARIS
Автор

I had similar arming issue. A piece on my matek PDB broke off and was causing the exact issue. Replaced it and it works perfect

iStackSlow
Автор

I had a similar arming issue when I switched over to crossfire. When I set the endpoints for throttle to 1000 and 2000 in the Taranis and my quad would not arm. I adjusted the low end throttle end point to 995 and boom no more arming problems. Cheers.

kevinclark
Автор

As others have said, make sure calibrate accel if its on, turn on warnings in OSD if you're using biggest thing, put the ESC's on the bottom of the arms...this won't help with arming, but the LEDs look cooler there! Happy flying.

alphadog
Автор

I hate those kind of "Mystery" problems. I'm having one now with my quad, where after I crashed, my quad it went full throttle when I tried Turtle mode and almost had a melt down before I could disarm. Now it wants to do it randomly when I arm. Almost took my face off! Hope you get it figured out.

gtwelder
Автор

Damn Gremlins. I don't know enough to be helpful, but thanks for the content. Your flying is makes me want to continue improve and continue enjoying this hobby. Thanks man

Vobe
Автор

Check your config to see if Accelerometer is enabled. If so you should also check on the right that your Max Angle is set to “25”

ByunDan
Автор

Mine when on 6s it use to throught the calibration warning. But out the the blue world work here and there

gregcapazzi
Автор

Kiss and beta flight not like each other maybe:) I’m flying BF DShot 1200 with BL Heli 32 and I don’t think I’m gonna fly anything else. It’s awesome. Hope you get it sorted out

Politicallyhomeless
Автор

Eric Konasty it could be battery low battery warning. It may think that you use discharged 5s lipo. Try to set voltage to LIHV lipo.
If doesn't help, go on github and ask for help there. There are a lot of people that will help you. :)

BuzZ.
Автор

Like others have said, it looks like you never calibrated your accelerometer. It's arming after plug and unplug changing the angle and the gyro thinks the quad isn't level until that one plugin where you lay it down at just the right angle. You can either turn off the accelerometer or calibrate it and it should arm fine. There is a button the calibrate on the setup screen.

BASHERSUNITED
Автор

Had this once before, turned put to be a broken bootbutton, with that shorted it starts up in dfu so no arming. I just broke of the bootbutton and it worked fine.

bramnw
Автор

showclass move a body shirt for the win

mikestevens
Автор

yeah remove blades plug battery in while ts having issue plug in to usb then go to cli and type status in cli it should tell you the flags why its not arming. also recheck your solder points on receiver signal and esc signal. Question are you running the board in overclock ? I sometimes got cpu load issues so cut it off and just run 16/8k not 32/16. also check that your small angle is 180 or you need to be 25* to level setting of accel

youeladamas
Автор

if last info didn't help try setting gyro to calibrate after you arm gyro_cal_on_first_arm = on this will make it calibrate after you arm so if you hand launch you need to level arm disarm first

youeladamas
Автор

I had a problem like that when I copied my config from the Betaflight F3 board to the Betaflight F4. Right now I’m running the BF4 3.2.1 with Airbot 32-bit ESC v32.3 and CRSF without issue. I manually reprogrammed my quad and that fixed my issue. I think that pasting the dump all from the BF3 board altered the resource assignments causing the issues. The combination works it must be a config issue.

carlosfpv
Автор

In addition to the status from the CLI, you can also turn on warnings in the OSD. The advantage of that is there's no need to have a device with you.
E.g. I had one board where I get a similar problem and the warning on the OSD tells me "nogyro", then you wait a long time e.g. 5 mins and it gets better or like what you're doing just reboot it a few times.

flite
Автор

I'm having the same problem I sent my board back to helidirect and they're checking it out . If you figure out what the problem is please post a video explaining it for the rest of us lol

maine_iacfpv
Автор

Nice Q X7S paintjob! Would you mind sharing some more details on it?

froqstar
Автор

I have the same problem with the betaflight f4 Board won’t arm.only randomly it would arm like yours. The only time I could get it to arm was if I plugged it into betaflight via usb with battery on and then armed. I got the same blinking red led I spoke with the guys at fpv model maybe defective gyro

chineseempanada
visit shbcf.ru