[Paparazzi-devel] YNT: airspeed_ets calibration

[Refik Sever]

Hi Chris,

Our flight time is around 10min, so I couldn't observe a drift at this short interval.
After 10min. flight we land and change the battery, therefore the sensor starts with a different offset value. Thats our problem.

Now I removed the initialization line and made it constant (1558 for my sensor), which I measure indoor. I also calculated the scale and offset values using the samples which we took by car. I will try these tomorrow.

According to the codes, the sensor initializes at power on. Therefore,  I don't understand why your sensor drifts in flight.

Refik

---

Kimden: Chris Gough address@hidden adına paparazzi-devel-bounces+address@hidden [paparazzi-devel-bounces+address@hidden
Gönderildi: 25 Ağustos 2013 Pazar 16:39
Kime: address@hidden
Bilgi: address@hidden
Konu: Re: [Paparazzi-devel] airspeed_ets calibration

Hi Refik,

Do you find your ETS airspeed sensor is drifting, or some other problem? I seem to be having a similar issue, today ours drifted by ~5 m/s in ~1 hour. E.g. after the hour it would report 1 m/s heading into a ~6 m/s wind, 2 m/s heading into 7m/s wind, 0 m/s heading into 5 m/s (or less) wind. 

Chris Gough

On 25/08/2013, at 11:09 PM, Refik Sever <address@hidden> wrote:

Hello,

Airspeed calibration is a very tedious task.

We flied a lot in calm weather conditions and tried to calibrate it by trying several offset (AIRSPEED_ETS_OFFSET) and scale values. We want to make the airspeed and gps speed  equal to each other. But although we make them equal, in the succeeding flights it always changes.

At last, we tried to calibrate it by using a car :) We drove the car with 10km/h steps between 10km/h and 100km/h, and took sample values at every step. I recommend this for anyone who wants to calibrate airspeed.

In the airspeed_ets.c file, I saw that the offset value ("airspeed_ets_offset", not "AIRSPEED_ETS_OFFSET") is calculated for once when we power on the autopilot. Therefore, the offset changes in every time we open it in different wind conditions. That explains why we couldn't calibrate it.

I think that calculating and fixing the airspeed_ets_offset for once will be better then to change it in every power on.

Regards,
Refik

Relevant part of the code:

if (!airspeed_ets_offset_init) {
      --airspeed_ets_cnt;
      // Check if averaging completed
      if (airspeed_ets_cnt == 0) {
        // Calculate average
        airspeed_ets_offset = (uint16_t)(airspeed_ets_offset_tmp / AIRSPEED_ETS_OFFSET_NBSAMPLES_AVRG);
        // Limit offset
        if (airspeed_ets_offset < AIRSPEED_ETS_OFFSET_MIN)
          airspeed_ets_offset = AIRSPEED_ETS_OFFSET_MIN;
        if (airspeed_ets_offset > AIRSPEED_ETS_OFFSET_MAX)
          airspeed_ets_offset = AIRSPEED_ETS_OFFSET_MAX;
        airspeed_ets_offset_init = TRUE;

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel