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

airspeed "quick cal" advanced option #8463

Open
dagar opened this issue Dec 13, 2017 · 11 comments
Open

airspeed "quick cal" advanced option #8463

dagar opened this issue Dec 13, 2017 · 11 comments

Comments

@dagar
Copy link
Member

dagar commented Dec 13, 2017

Airspeed calibration determines the offset of the differential pressure sensor averaged over a few seconds (# samples), then applies the offset, waits briefly, then asks you to blow to verify the tubes are connected properly.

This should definitely remain the default, but more advanced users would like the option to zero the differential pressure sensor immediately and skip the blowing step.

This could be an advanced param for airspeed quick calibration.

@raygamero

@raygamero
Copy link

Thanks for this issue Daniel. I'm going to see if I can come up with a good solution.
Do you mind telling me where to start to understand the current cal module?

@Antiheavy
Copy link
Contributor

Interesting idea. Most other autopilot systems don’t have a diff pressure test step although I really like it. Actually I would love to see it as a pre-arming check as well, but I have thought through how that would be implemented firmware side.
Personally, I would like to see the averaging time cut in half to speed up calibration. The time now seems too long and may introduce more chances for error than it tries to average out. As mentioned, I really like the “blowing” step to verify the pneumatics. ...although I never blow into a Pitot (moisture from mouth/lungs can be bad news) , I press my finger over the end to create and hold pressure.

@tubeme
Copy link

tubeme commented Jan 14, 2018

Hi Daniel, that is a very good idea. I understand the procedure of calibrating the airspeed sensor has two aspects. 1. The most important to see the hardware inbuilt difference between the two tubes ie the two sensors in the chip at same given pressure (that is why we need not to fly and cover the pitot at that moment). 2. To see what is the current reading at static pressure and take it as zero.

This complicates the whole use case because we cannot get this two different calibrations separatelly when we need them.

As far as I understand the pressure difference between the two ports of the chip is something that does not change with time, because it is inbuilt the sensors. Or maybe it changes with time but very very slowly. So it does not matter if it is done in closed space in the workshop. This can include blowing the tube.

The second calibration can be done on the airfield and it definitely should not include blowing in the tube. It just has to get the reading from the static tube and take it as zero.

I don't know if by "quick cal" you mean this?

Using airspeed sensor now is so cumbersome it is not real. Especially on a windy day on the field...

@raygamero
Copy link

I'm intimately aware of high dollar UAS that, for day to day flying, have a procedure to "bag" the pitot (placing a loosely fitting bag over the tube to block wind) and then "zeroing" the sensor. This is simpler and safer, assuming that you don't leave the bag on the pitot! This would be a "quick cal" or some descriptive title.
The initial check, to verify if your tubes are not swapped is great and should not be removed. It is just not used every time. Maybe just after repairs or during inspections.

@Antiheavy
Copy link
Contributor

This could be an advanced param for airspeed quick calibration.

instead of a param to switch what the routine does, should it be two different routines that can be called separately? I realize QGC (or your favorite software) would then have to deal with two different message sets, but the "zeroing" and "testing" really are two different things.

I've got the reverse argument of some others in the thread. There are newer differential pressure sensors that claim to never need in-field calibration (I'm skeptical, but would happily be proved wrong) - I still want the ability for a "test" of the pitot-static tube even if the calibration routine isn't run. Not only are we testing that the tubes are not backwards, but we are testing for leaks and blockages that easily occur when landing in rough ground. A future firmware feature might be an option to require a successful diff pressure "Test" to unlock arming.

@Antiheavy
Copy link
Contributor

this is still relevant.

@Antiheavy
Copy link
Contributor

still relevant. @Kjkinney I wonder if this is something we can look at?

@stale stale bot removed the Admin: Wont fix label Jun 25, 2019
@PX4 PX4 deleted a comment from stale bot Jun 25, 2019
@PX4 PX4 deleted a comment from stale bot Jun 25, 2019
@PX4 PX4 deleted a comment from stale bot Sep 25, 2019
@stale stale bot removed the Admin: Wont fix label Sep 25, 2019
@Antiheavy
Copy link
Contributor

This "quick cal" feature would also be neat to be able to run at boot. either as a optional parameter controlled thing, or maybe scripted as part of the start-up scripts.

@dagar
Copy link
Member Author

dagar commented Oct 3, 2019

This "quick cal" feature would also be neat to be able to run at boot. either as a optional parameter controlled thing, or maybe scripted as part of the start-up scripts.

I wonder if we could get away with doing it automatically if disarmed and any time the differential_pressure is sufficiently stable for a relatively long period of time. Maybe combined with the vehicle being still (attitude and position)?

@Antiheavy
Copy link
Contributor

sufficiently stable for a relatively long period of time

some of the cheaper (and more popular) diff pressure sensors are never really stable, especially at the very low end of the scale (very noisy and bouncy).

Also, having it happen at boot up is something that can easily be explained/training. e.g. one option to recal airspeed is to just reboot the vehicle and block the pitot from wind.

@stale
Copy link

stale bot commented Jan 1, 2020

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

@stale stale bot added the stale label Jan 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants