paparazzi-devel
[Top][All Lists]
Advanced

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

Re: [Paparazzi-devel] Eagletree airspeed sensor problems


From: Balazs GATI
Subject: Re: [Paparazzi-devel] Eagletree airspeed sensor problems
Date: Tue, 22 Jan 2013 08:09:58 +0100
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2

My config:
TWOG + Airspeed_ETS + Baro_ETS (USE_AIRSPEED, USE_BARO_ETS)
it works seamless with version 4.0

Balazs


2013.01.22. 5:53 keltezéssel, Eduardo lavratti írta:

This is my planes. All with airspeed_Ets.
Plane1: YAPA2 + Airspeed_ETS + mpu6000 + ms5611 + camera controller (atmega8).
Plane2: TWOG + Airspeed_ETS + l3g4200 + hmc5883 + bmp050 .
Plane3: TWOG + Airspeed_ETS + itg3200 + hmc5883 + bmp050.

Some time with original drive the airspeed not initialize then i modified 
airspeed driver to wait some time to initialize.
This problem occur with all ppz versions.
Date: Mon, 21 Jan 2013 21:30:28 -0700
From: address@hidden
To: address@hidden
Subject: Re: [Paparazzi-devel] Eagletree airspeed sensor problems

Hello,
I was just wondering what sort of configurations people are definitely having 
problems with? What other devices are on the bus? Would be nice to have a clear 
and comprehensive list of what works and what doesn't and what the symptoms 
are...

I have been using an ETS airspeed sensor with Lisa/M v2.0 on I2C2 (no baro 
running) with aspirin 2.1, with absolutely no problems at all that I can 
detect. Of course, I don't think anything else is on this bus. (Last run on 
v4.1.1_testing-11-ga0fbe08 in my scdwyer git repo).

Thanks,-Stephen Dwyer


On Mon, Jan 21, 2013 at 11:40 AM, Gerard Toonstra <address@hidden> wrote:

I've got two here and want to use them too. I've got a buspirate, which allows 
me to test various things quite easily over a console.
Tomorrow I'm away, but wednesday I should be able to have a look there.
G>


On Jan 21, 2013, at 3:06 PM, Felix Ruess <address@hidden> wrote:

Hi Tilman,


I have to admit, I don't quite understand the problem. I used to get values 
with this module (never flew it though)

Did it break or was it broken all the time? I thought this module was rather 
widely used.

That somehow never got quite clear from following the thread.
I really don't know, as I never used one myself... But it seems to me that it 
might have worked in old versions purely by chance (e.g. because some things 
added a fixed busy wait at initialization or something along these lines).

The point is that we don't really know what the startup requirements for this 
sensor are... other standard I2C sensors are working fine.
Cheers, Felix


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



_______________________________________________

Paparazzi-devel mailing list

address@hidden

https://lists.nongnu.org/mailman/listinfo/paparazzi-devel





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



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


--
Balazs GATI, PhD
     Department of Aircraft and Ships
     Budapest University of Technology and Economics

Address:   Budapest
          Stoczek u 6. J. ép. 423
          1111
Tel:       +(36)-1-463-1960
Fax:       +(36)-1-463-3080
Homepage: http://rht.bme.hu/~gatib/



reply via email to

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