[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: Marc Schwarzbach
Subject: Re: [Paparazzi-devel] Test flight results (Lisa/M, ETS, Pitch-loop, GPS)
Date: Thu, 20 Sep 2012 00:00:50 +0200

Hi Tilman,

the only difference seems to be the I2C Port..
Can you quickly change to port 2 for a test?

Regarding going through luftboot just to check, my timing is: Attach 
programming wire, power on (luftbook blink sequence running), load firmwire, 
while that is happening unplug programming wire, system is running...

Power off, power on, ETS shows static value...

Another thing Felix told me to try some days ago was to insert an 
initialisation delay to the ETS code like already implemented in the mkk 
controllers (sw/airborne/firmwares/rotorcraft/actuators/actuators_mkk.c), since 
the problem looked similar. I will not be able to test in the next time, 
prbably you can?

Hope we get that running...



-------- Original-Nachricht --------
> Datum: Wed, 19 Sep 2012 22:05:37 +0100
> Von: Tilman Baumann <address@hidden>
> An: address@hidden
> Betreff: Re: [Paparazzi-devel] Test flight results (Lisa/M, ETS, Pitch-loop, 
> GPS)

> 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"/>
> </load>
> <target name="ap"             board="lisa_m_2.0">
> <define name="USE_I2C1"/>
> <define name="USE_AIRSPEED"/>
> </target>
> 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]