Re: [Paparazzi-devel] Eagletree airspeed sensor problems

[Stephen Dwyer]

Hello,

Yes, I am also confused, but in this instance, it seemed to work. It looks like (if I remember correctly) it took about 32ms from Lisa/M boot (power on) to send the first i2c message to the ETS, but this always locked up the i2c bus. Once i added a 1 second delay, it seemed to work no problem afterwards. No idea why. I need to look into it further with a scope on the power. It might be that the PIC or whatever is on that sensor doesn't boot up in time, the nack gets sent back and the i2c driver/bus doesn't recover.

I can submit a pull request if you like. Code is here for now (no updates to module xml). https://github.com/scdwyer/paparazzi/commit/08a5a76d765c6c58966d021cd038d10cd399a714

Thanks,

-Stephen Dwyer

On Sun, Jun 30, 2013 at 3:28 PM, Felix Ruess <address@hidden> wrote:

Hm... I'm kind of confused...
On this older post the consensus seemed to be that a delay (in the airspeed ets module) does not help: http://lists.gnu.org/archive/html/paparazzi-devel/2012-10/msg00050.html

Stephen, what kind of delay (and where) did you implement?

On Fri, Jun 28, 2013 at 3:20 PM, Eduardo lavratti <address@hidden> wrote:

I ever use startup delay when using ETS airspeed as i tell some times here.
Some time the sensor not initializer ever in branch 4.2

---

Date: Thu, 27 Jun 2013 22:28:32 -0600

From: address@hidden
To: address@hidden
Subject: Re: [Paparazzi-devel] Eagletree airspeed sensor problems

Hello,

I just came upon this problem today. Before with something around v4.1 I didn't have any problems, but today with v5.0.0_stable-29-g4bd194f-dirty (on a custom branch here: https://github.com/scdwyer/paparazzi/tree/uasgroup-v5.0) the ets airspeed sensor would not work. I ended up implementing a startup delay of 1 second, and now it is working again. I haven't had time to investigate further, but if I have a chance I will try to put a scope on it and see if there is anything interesting. On failure it looks like it was giving a NACK after the address was sent on the bus, and it never recovered from this. The rest of the autopilot worked fine, but the i2c2 bus did not show any further activity. The ETS went on happily blinking out the last max speed.

This was with Lisa/M v2.0 and Aspirin 2.1. Airframe is conf/airframes/UAlbertaUAS/UAP3/UAP3_A_v5-0.xml in the above repo.

If I find anything else out I will report back.

Thanks,

-Stephen Dwyer

On Wed, Feb 6, 2013 at 7:57 AM, Felix Ruess <address@hidden> wrote:

Hi,

ok, was just a random stab in the dark...

Can anyone who has an ETS airspeed sensor, a scope and JTAG/BMP have a closer look at this?

Cheers, Felix

On Fri, Jan 25, 2013 at 4:07 PM, Tobias <address@hidden> wrote:

Hi Felix,
sorry - I m not using the api protocol at the moment.

_______________________________________________
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

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