Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BF 3.0.0 RC7 - Baro Mode: Throttle Pumping #1003

Closed
RipperDrone opened this issue Aug 14, 2016 · 18 comments
Closed

BF 3.0.0 RC7 - Baro Mode: Throttle Pumping #1003

RipperDrone opened this issue Aug 14, 2016 · 18 comments
Labels
BUG Bugs are excluded from automatically being marked as stale

Comments

@RipperDrone
Copy link
Contributor

RipperDrone commented Aug 14, 2016

Baro Mode worked well after some PID tuning & adjustments in the code until BF2.9. From BF 3, there seems to be changes in Baro Mode which force my Armattan X155 / SPRF3 to 'pump' altitude up/down periodically (approx. 2 pumps per second). After trying to rgain control by several throttle stick up/down movements, it seems to eventually calm down.

Could be PID off target again? I am using your defaults now.

OR has there been any change in the Baro Mode PID loop / parameters in general?

I know Baro is not your primary focus, but for starting / landing I'd like to have the Baro mode working at least to an extent that I don't need to be scared... ;-)

@alsop
Copy link

alsop commented Aug 14, 2016

I am experiencing the same behavior with a Vortex 250 using 2.3.5 (the version it came with). Adjusting the Alt. P value from 50 down to 10 does not make any difference. The "sensor" display in Betaflight Configurator shows the barometer to be working correctly, although it does drift a bit (+/- 0.5 meters). So I am guessing that the PID values displayed in Configurator are not the ones actually being used when BARO mode is turned on. As delivered, the Vortex configuration had disabled the Barometer, so perhaps this is a well-known problem?

@borisbstyle borisbstyle added the BUG Bugs are excluded from automatically being marked as stale label Aug 19, 2016
@RipperDrone
Copy link
Contributor Author

Just completed maiden of my new build QAV. Exactly same isseu with stock ALT/VEL PID. Pumps / oscillates altitude / thrust when switching back from acro into self-level with MAG & BARO (for landing).

@borisbstyle
Copy link
Member

@RipperDrone
Baro // Mag is not the main priority of betaflight project. Those functions are better maintained in iNav and Cleanflight project.
In betaflight it is really best effort support. I wil park this for 3.1.

@RipperDrone
Copy link
Contributor Author

RipperDrone commented Aug 21, 2016

Acknowledged. Not asking for a butter smooth hold altitude here, though. Just very basic Alt Hold feature is enough. In the small group where I'm flying, everybody finds this mode helpful when landing. Excessive alt jumps in Alt Hold mode can crash the copter.

@borisbstyle
Copy link
Member

Can you try RC13 just to verify if this had to do with wrong baro detection? Reopen issue if it still persists

@RipperDrone
Copy link
Contributor Author

worked nice today however I noticed later that I had my ALT and VEL settings down to 30. No more pumping, not a single bit. Maybe you want to default the ALT / VEL to those lower values in the next rev?

Anyway, thank you for notifying me about the BARO detected wrong fix!

As you said, most of the time I'm using Acro / Air modes. BARO only sometimes to check things...

@alsop
Copy link

alsop commented Oct 18, 2016 via email

@Jerm357
Copy link

Jerm357 commented Jan 26, 2017

I'm having this same problem on 3.0.1 and 3.10 on my SPRacingF3 flight controller. I came from BF 2.6 and it was working pretty good but as soon as I upgraded to 3.0.1 and up I get this same Throttle Pumping as described above. I don't get any changes changing ALT or VEL P but changing VEL D does have some kind of effect. Everything else is working great for me so it would be awesome to get my Baro working back like it was. Any ideas what this could be?

@alsop
Copy link

alsop commented Jan 27, 2017

Hi Jerm357. Thanks for CCing me on your message. I am still running 2.xx versions and have also found that some of the settings have no observable effect. One thing that makes this a little more livable for me is to make sure my vertical speed is very near zero when I engage altitude hold. But if I try to climb much, it takes off like a rocket – and then nearly stops the props entirely. This is exciting visually, but not useful.

@Jerm357
Copy link

Jerm357 commented Jan 30, 2017

Any way to open back up this issue so we can get this looked at again?

@MrSmith2017
Copy link

Yes, would be nice when this can be fixed.

@wogfun
Copy link

wogfun commented Feb 15, 2017

Experiencing same issue as described above on latest spf3 fc.

@STOLerant
Copy link

I'm having the same issue, was there ever a solution?

@andrejpodzimek
Copy link
Contributor

andrejpodzimek commented Aug 7, 2017

The same issue still persists. I’ve just seen severe throttle pulses (with a frequency of ~2 per second) with the latest 3.2-to-be master build, with this aircraft. Although my barometer is now working, thanks to the great advice from experts in the community, I can’t really use it, because my hex (well, quads also have a short name, so why not hex) just jumps around the target altitude in a crazy way. I surrounded the baro with foam to rule out interference with propeller sound, but nope, it’s still bad, to say the least.

EDIT: I’d love to try iNav, which many people recommend, but it doesn’t work. I’ll give it a try once the issue is fixed. Anyway, it would be awesome to have the functionality in Betaflight too.

@noviuk
Copy link

noviuk commented Oct 20, 2017

Betaflight 3.2.2
SP F3 clone
Had the same issue. Solved by changing P to 0, and increasing I to 15 with D to something like 10.
1st tests show that there is no more oscilation.
2nd tests show that there in no altitude hold. its or descends or ascends.
Edit:
changed ALT PID back to original 50 ; 0 ; 0
and then changed VEL PID to 50 ; 5 ; 30
no oscilation and altitude hold works fine.
tho still need some tweaks because there is some werid behavior when i lower the throttle.

@Glowhead
Copy link

Glowhead commented Oct 25, 2017

I have never had a problem with the modified F3 versions pumping the throttle (no need for BMP085). With two SP Racing F3 boards only one has the pumping throttle issue using BMP 085. The modification:
ALT PID 50;0;0 and VEL PID 50;5;30 helped a lot! The altitude does float between the widest ranges of all four models but it works. I always land baro off. Not problems landing. You can use BMP120 instead of BMP085. Works perfectly.

@SpyQuad
Copy link

SpyQuad commented Aug 21, 2018

+1 for me for Altitude Hold (Baro) PID settings ALT PID 50;0;0 and VEL PID 50;5;30. I have built a QAV250 quad with a "HobbyKing" Ghost Edition frame and MT2204 2300KV motors driven by KingKong 12A ESCs and an F1 class Illuminati 32 (Naze32 clone) Flight Controller with built in Baro (MS5611). I have experimented a lot with CleanFlight (different versions) but although Acro mode was working steadily, Baro mode never worked, or I could'nt make it work.
Then I switched to BetaFlight and I saw improvement in the quad's behavior from the start. I flashed BetaFlight 3.2.5, although some suggest not to try past the 3.0.1 version for F1 class FCs. In my case all went well and the quad's behavior was adequate from the beginning.
However in Baro mode I experienced the "either going up or going down" syndrome with no real "altitude hold". Then I saw this thread and tried VEL PID 50;5;30 as suggested, and voila !
Altitude hold works within let's say 0,5 meters. There is enough "dead zone" around the initial throttle stick position, so you can find the neutral position easily. When you move the stick past the dead zone the quad slowly begins to ascend or descent as expected. When you re-enter the throttle stick's neutral zone the quad again holds its altitude.
I should also mention that I have set:
set alt_hold_fast_change = OFF (max alt change = +/- 0.5 m/s)
Now I just have some oscillations in Angle mode and I am trying with the motion PID settings to also overcome this. Any suggestions ?

@MR444
Copy link

MR444 commented Aug 31, 2018

Baro mode was removed in 3.5.0. I started a feature request.
#6675

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG Bugs are excluded from automatically being marked as stale
Projects
None yet
Development

No branches or pull requests