no, just a little 1550 4S :-)

Mavic 2, awesome machine

@Thu Nell Ⓥ Don't know. I gave up (for this and other reasons) and started using PrusaSlicer 2.x about a year ago. Uninstalled Cura a couple months later. The paths are so much better, and prints are so much cleaner, with PrusaSlicer.

Hoping to get it into 3.4. Other goodies on the way too.

github.com/betaflight/betaflight/pull/5427 Basically 3.3 (stage 2 BQRC on gyro) with the above pull request to provide a second PT1 on D. Setup with D weight = 1 and Transition = 0.01, to stop D damping of stick response around centre stick.

ctzsnooze what was kD?

P34, D17

try 3.2.4 it has fixes for these issues and the above code. works on all axes but can be set to yaw only.

ctzsnooze thx ok mine is only when I combine pitch and roll

+Joe Stubbs Current version of betaflight is 2.7.1 and is much better than 2.3. But all upgrades come with the risk that something just won't work. If you're not sure, don't do it. It's not so bad if you have a copy of the original hex and a dump of your original settings - you can go back if you need to. But without a copy of the original hex there's no way back. The best way to update settings from a backup is copy and paste. Just copy the contents of a 'dump all' command (drag over the entire dump and copy) and save to a text editor. To restore, copy the text of a previous dump all from the text editor, go to the CLI and paste it into the little box at the bottom of the CLI where you type commands, then check that every command was accepted without error. If OK type save and press return, otherwise exit the CLI and make no change. Warnings: - the syntax of some commands changes as code evolves, so what you paste may not be understood. Check each line of the CLI after the paste for error messages. Commands with error messages should be individually checked. - some slow interfaces may lose parts of the paste, you'll see that lines in what you pasted never appeared in the CLI after the paste when this happens. To resolve it, paste in small chunks and check each bit is good before moving on. - when pasting settings, some may not be appropriate for your quad, e.g. a dump file from someone else may specify a different radio or switch setup. ALWAYS after saving, exit the CLI, go back to the CLI, do a dump all, and confirm that the settings in your CLI are appropriate for your quad. Thanks for your suggestion but I'm not sure what needs updating. Sounds like you don't understand the basics of the CLI itself and how to send commands in via the CLI. Basics of how to use the CLI is not the topic of this video.

+rc-nut 1 yep sure was!

+Robert Stoughton Hi Robert - I'm not a true programming expert on these chips. I can sort of read code and modify things, but not really adapt it to totally different environments There are, however, many people with great expertise on RCGroups.com.

+Joe Smith I don't think there is a way to see the motor mixing as a list of values. Good question for cleanflight users at RCGroups. I personally don't use custom motor mixes. Sorry I can't be more help.

hmmm, will put it out there. Thanks!

+FPV Crash Test Dummy - no, that was exceptional, way out in front. The fast guys used 2.1mm lenses to 'see around corners'.

+nitro 20 the code controlling Horizon mode behaviour has to be modified, unfortunately, to provide inverted behaviour with levelling. Banked turns take practice in all modes, the right mixture of yaw, roll and throttle is needed, and that takes practice to get right. Eventually it becomes second nature, but wow is it difficult at first!

+ctzsnooze i can bank pretty good with the cc3d and open pilot... i can do 3 fast flips in about 15 ft drop in ratitude mode.. i can bank my naze32 cleanflight in angle. and it flys real good and tight. but i dont understand how to get it to stop wanting to correct it self in horizon mode so strongly..so it will do 3 flips and do moving flips. what is the settings at the bottom of the PID adjustment page...horzon(angle) and such..and also..what is the differece if i run rewrite or fluxfloat. can the naze32 do those other 3 modes. See on my cc3d 250 i just had to load up a 250 quad on openpilot vehicle settings, a few minor adjustments and i was off. tpa and everything was set up.. and for a new air modeler learning as fast as i am, i just dont know enough about the PIDs to progress past were i am.

+MrPnew1 Thanks! - my latest FPV video is basically from the same quad but with 3100kV motors and cut down 5030 to 4530 props - it's now really fast for such a tiny thing - without battery the current build weighs 170g so easy to get under 250g AUW with the right battery.

+mark rankin - sorry but you will need to do it on the transmitter. there is a CLI value for midrc but it's better to leave that at 1500 and make the changes on the Tx.

+ctzsnooze Thank you so much I will do the changes on the tx. Ive been trying to flash my naze with boris hex on cleanflight but the motors dont work even on the esc calibration part where you use the master motor tab. But when I flash back to a normal stable version everything works again would you know what im doing wrong. Thank you again for replying

+mark rankin it could be that the active betaflight versions are defaulting to 2kHz (500us loop times). Some ESCs don't like to calibrate with that fast a loop time. If you see loop times around 500 then check RC groups as to how to get it back to 1000 (set gyro_lpf = 188 I think)

+ctzsnooze Fantastic I will give that a shot CHEERS!

+mark rankin make sure to get the absolute latest binary there's been a lot happening and some releases have serious issues, think its good right now though. only use lux on F3 boards, it can work at 2kHz on F1 boards but read up on that. otherwise rewrite is more reliable on F1 boards.

+endzi junior - sorry don't have a cc3D board. can't do much unless the serial port can be opened. google might help.

+endzi junior , You unplug it then you throw it strait into the garbage can. Its an F1 target... OLD technology, you can get a naze for $12! If you choose to keep it, first you must open up openpilot and do a full chip erase. Then, plug your battery in(its a crap board) and go back to betaflight/cleanflight and load the hex.

+endzi junior try shorting the boot loader pads and then flashing. that's sometimes necessary if the wrong target has been loaded

hanks i have ready make witch libre pilot

+Martin Ward just about! Went through a few props though. :-) very long flight times on this little thing, it doesn't weigh much, about half a typical 250 racer including battery.

+Martin Ward The quad survives most anything! Its very tough. The Dinogy batteries have lots of go. Love 'em.

+Bill Morley Thanks Bill! :-)

+Carlos A Sorry I don't know exactly how to do that. I've seen posts in the Cleanflight RCGroups pages.

LCG350z The BLHeli documentation lists the ESCs it can connect to. They must have a boot loader.

Jahroen Yes, it was due to vibration aliasing. In the CLI, try setting acc_lpf_factor to 0 and gyro_cmpf_factor to 1000. Get the latest builds with soft filtering. See if that helps. It's OK for me now.

ctzsnooze i,m getting acc_lpf_factor Unknown command cleanflight 1.9.0 lol ok i see i forgot the word SET trying it now

ctzsnoozei tested it out but it did not help, still banks left in angle and to the right in rate mode

Jahroen If it consistently banks right in angle mode, that's sort of normal, because there is no levelling in angle mode, so it will never stay level. But of course, for the quad to be controllable, you must have the endpoints set in the radio so that in the GUI you see 1500 at centre sticks, and say 1050 -1950 as the endpoints. And that must be with NO Tx based trim at all (never use Tx trim). And the motors must be calibrated properly so that they all respond equally to instructions from the flight controller. If you then have no significant frame vibrations, it should be possible in rate mode to set it to the 'level hover' angle, and it should stay there. If in Level or Horizon mode, it assumes a non-level angle after acc calibration, this should be fixable with acc trimming using the sticks (while disarmed, hold the throttle full up, and the pitch/roll stick in the direction you want the quad to go, in your case to the right; hold for say 5 flashes/seconds, then stop). If you do this, it imparts an offset to the acc trim to angle the quad to the right by 5 clicks. With a bit of fiddling (might take 15 or more) you should be able to achieve a stable level hover. If you find the hover is unstable and that with less throttle it angles one way, and more throttle it moves another, then its possible that the accelerometer is not firmly secured to the frame so that vibrations affect it unequally, or that one motor is noisier than another. That's about all the advice I can give.

ctzsnooze i used right trim in angle mode and forgot about it,thats why it was banking to the right in rate mode. so i turned it back and rate mode is stable now angle mode hovers fine for 10 to 15 sec and then banks to the left. angle mode is selflevel. for the 1500 at center stick i use sub trim on Tx, i dont know how to move them otherwise. and i do have one motor that is vibrating more then the others.