[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] Test flight results (Lisa/M, ETS, Pitch-loop, GPS)

From: Tilman Baumann
Subject: Re: [Paparazzi-devel] Test flight results (Lisa/M, ETS, Pitch-loop, GPS)
Date: Wed, 19 Sep 2012 22:05:37 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20120724 Icedove/3.0.11

On 10/09/12 17:46, Christophe De Wagter wrote:
Dear Marc,

thanks for your feedback:


2. The Airspeed sensor works on the I2C2 port with 3.3V (also written in the specs). But initialisation seems to be a problem. Only after (Luftboot)programming, the sensor delivers data. If I just plug the battery in, airspeed is constant 8.. Sensor display shows numbers like usual. Should there be some kind of pause in the ETS init? Or is this an I2C related problem?

This problem is also known and a hacked solution is also in the tudelft/tudelft4.0/sw/airborne/arch/stm32/mcu_periph/i2c_arch.c

I tried the same thing. But no luck for me. (In fact the file was already the same in my git checkout)
I also observe a static airspeed value in the messages (15m/s).
But I don't even see it working with going through luftboot first.

   <load name="airspeed_ets.xml">
      <define name="AIRSPEED_ETS_I2C_DEV" value="i2c1"/>

    <target name="ap"             board="lisa_m_2.0">
      <define name="USE_I2C1"/>
      <define name="USE_AIRSPEED"/>

Any tips on how I should debug that?

PS: My code is on
Pulled from v4.0 with basically just my airframe changes added conf/airframes/examples/bixler_lisa_m_2.xml

reply via email to

[Prev in Thread] Current Thread [Next in Thread]