Posts: 391
Threads: 23
Likes Received: 50 in 41 posts
Likes Given: 56
Joined: Feb 2016
Reputation:
8 I've just flashed the new version of Betaflight on my Naze32 and now the quad is completely un flyable. I was previously using 2.7.1 which was great, the only reason I am upgrading is to try the new rates and expo settings in Betaflight.
I was wondering what I could be doing wrong, I have configured the settings exactly the same as I always do. I am currently using BLHeli 14.6 but the same happens on 14.5 which is what I was using before.
Any ideas would be appreciated.
Current quad: ZMR 250 / DYS SE2205 / Littlebee 20A ESCs / Drone Lab 1500 4S / Naze32 Rev5 / BF 2.7.1
FPV: Runcam Skyplus / Aomway 200mw VTX / Fatshark DomV1
>>>>>>>>>>
Check Out My Build<<<<<<<<<<
• Posts: 12
Threads: 1
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Mar 2016
Reputation:
0 05-Jun-2016, 08:11 AM (This post was last modified: 05-Jun-2016, 08:29 AM by artur_k. Edit Reason: typo ) It's the same for me on blheli 14.4.
Quad is oscilating on my 2.7.1 pids, and feels very floaty at the same time. I also have a bit of drift now possibly due to deadband set to 0 as suggested - my input is only jumping by 1-2 and my deadband was set to 2 in 2.7.1.
Air mode is not working when enabled as a feature - I got a nice hairy moment when the quad dropped like a brick when I tried it first time and wrecked a brand new set of props when I set airmode_activate_throttle to 1050 - the quad just flipped violently on takeoff.
The new rates/expo system feels great though when you ignore the above.
• Posts: 5,323
Threads: 674
Likes Received: 3,159 in 1,747 posts
Likes Given: 2,032
Joined: Jan 2016
Reputation:
139 do you guys mean Betaflight 2.8.0? would love to know if there is a solution as I am considering to update as well..
• Posts: 947
Threads: 66
Likes Received: 350 in 248 posts
Likes Given: 164
Joined: Apr 2016
Reputation:
34 05-Jun-2016, 10:01 PM (This post was last modified: 05-Jun-2016, 10:03 PM by oyvinla.) MY lisam210 and beerotor f3 flies very good on 2.8.0. The only bug I have found is that the failsafe land activates even though the quad is not armed or failsafe is set to drop. If I turn of the transmitter while the quad is unarmed, the motors starts spinning for a second. This can be quite scary and I have already destroyed a USB cable because of this
• Posts: 12
Threads: 1
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Mar 2016
Reputation:
0 05-Jun-2016, 11:23 PM (This post was last modified: 05-Jun-2016, 11:29 PM by artur_k.) Right, I managed to get 2.8 set up for my quad, I only hovered it in the garden but it feels and looks ok now.
I'm running 4k/4k/4k on a f1 cc3d and little bee's 20a with multi shot 14.4.
I set gyro and dterm lowpass to 80, dropped d gains by 2, put the air mode on a switch, set the rates to 75 and its flying.
Edit: I'll test that failsafe bug tomorrow, but thanks for the warning.
• Posts: 6
Threads: 1
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Jun 2016
Reputation:
0 I just loaded 2.8 on my spracingf3 in my zmr and it flew great. The only weird thing I noticed was when I was tuning trying to find oscillation points on roll and pitch I ended up maxing pitch out before I got any noticeable oscillations. My PID's seem quite high. I'm at 8.3 on roll and 13.0 on pitch. Will have to fly it and look at the BB and see what that looks like.
• Posts: 6
Threads: 1
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Jun 2016
Reputation:
0 Stock PID's on rewrite were 4.5 on pitch and roll. Yaw I think was 10.
• Posts: 947
Threads: 66
Likes Received: 350 in 248 posts
Likes Given: 164
Joined: Apr 2016
Reputation:
34 How do you set the F3 controller to run 4k/4k/4k? My littlebee 20Amps are flashed with multishot capable blheli and looptime is set to 250. I tried to set the pid_process_denom=1 in the CLI, but then I could not arm. I had to set it back to 2 to be able to arm. From what I understand, Im only running 2k to the motors now.
• Posts: 52
Threads: 22
Likes Received: 27 in 12 posts
Likes Given: 1
Joined: Jun 2016
Reputation:
0 2.8.1 just came out. Here is a message from Boris on 2.8.0
"2.8.0 VERSION HAS BEEN DEPRICATED DUE TO PROBLEMATIC ITERM TUNING. ALL ISSUES ARE SOLVED IN 2.8.1
YOU CAN DOWNLOAD 2.8.1 PRE RELEASE BELOW ALREADY BEFORE IT IS FULLY RELEASES"
•