Hello total newbie here I got the f330 chassis with 4 bldc motors and their ESCs and got the omnibus f4v3 (AliExpress) and for the remote I'm using the flysky fs i6. When I wired everything to the FC and flashed it in betaflight, the receiver worked I can get signal on receiver tab, and in the motors tab I can make the motors rotate however when I try to move the throttle to make the motors spin, they won't and there is a solid red led and blinking blue led only when throttle is higher than 1000. Anyone got any idea what it can be ? There are no arming warmings other than msp when plugged in

Have you set up a arming switch on your Flysky FS-i6 transmitter to output on one of the auxiliary channels, and have you configured an ARM mode in Betaflight to be triggered when you flip the configured arming switch? If not then you aren't going to be able to get the motors spinning because you first need to arm the motors first using a switch on your transmitter (with the throttle at the lowest position when you do that), then once the motors are armed you can raise the throttle and the motors should speed up as expected. Make sure you do any testing with the props OFF.

I haven't done that since I had no idea I had to do that. Thank you I will try it and see what happens

Have a watch of the following video which walks you through setting up an arming switch on a Flysky FS-i6 transmitter and it then also shows you how to configure that switch for use with the ARM mode in Betaflight...

(04-Apr-2024, 12:51 PM)SnowLeopardFPV Wrote: Have you set up a arming switch on your Flysky FS-i6 transmitter to output on one of the auxiliary channels, and have you configured an ARM mode in Betaflight to be triggered when you flip the configured arming switch? If not then you aren't going to be able to get the motors spinning because you first need to arm the motors first using a switch on your transmitter (with the throttle at the lowest position when you do that), then once the motors are armed you can raise the throttle and the motors should speed up as expected. Make sure you do any testing with the props OFF.

This worked like a charm!! However now the motors when first arm will rotate exactly like I want then after 5 seconds they will rotate uncontrollably even though on the receiver tab in betaflight the values are correspondent with the sticks position
Note: my motors won't spin unless I put the protocol to PWM in the motors tab

Firstly, what ESCs are you using? If they aren't capable of running the DSHOT protocol then you are going to need to calibrate them. If you tell us what the ESCs you have we can figure out if they have DSHOT capabilities.

Secondly. if you are testing the motors with props off on the bench then the behaviour you are seeing is completely normal and is to do with the PID controller detecting no expected change in attitude of the quad as the motor RPM is raised, so it keeps raising the motor RPM higher and higher to try and get the quad to lift off the ground because it thinks there isn't yet enough thrust to do so which is why your motors can appear to behave erratically or spin up to max RPM by themselves. Have a watch of the following video to understand why. To get proper behaviour you need to put the props on and take it outside for a hover test. You will then find that the motors behave as commanded by your transmitter. But if your ESCs restrict you to running only the PWM protocol you will still need to calibrate them first.

Okay I calibrated them and everything looked fine, went to try and test the drone and on PWM 1070 it just flew to around 4 stories!! I had to un-arm and let it fall. I couldn't get it to hover because even at that low PWM it was too powerfull

It sounds like you are experiencing what is known as a flyaway. In the first instance, do the following:

1. Make sure that all bolts on the frame are really tight.
   
2. Make sure that all motor bolts are really tight.
   
3. Ensure that the flight controller is securely mounted with none of screws / mounts broken, and make sure it is mounted using anti-vibration gummies or stand-offs.
   

Because you are using a large DJI F330 Flame Wheel frame which isn't a particularly rigid frame, it is going to suffer from vibrations that a carbon fibre frame doesn't, and any excess vibrations that make their way to the gyro in the flight controller are going to cause issues with the PID controller and a potential flyaway situation like you seem to be having, so you may have to start delving into the minefield of filter and PID tuning.

You could also try having a look through the DJI F330 Flame Wheel Owners Thread on RC Groups at the link below to see if there are any pointers to try and help you out. It's quite an old thread that was started in 2013 and runs into 98 pages of posts, the last of which was posted in 2019, but that's because it's quite an old frame...

https://www.rcgroups.com/forums/showthre...ers-Thread