|Subject:||Re: [Paparazzi-devel] Eagletree airspeed sensor problems|
|Date:||Fri, 28 Jun 2013 10:20:40 -0300|
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
Subject: Re: [Paparazzi-devel] Eagletree airspeed sensor problems
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.
On Wed, Feb 6, 2013 at 7:57 AM, Felix Ruess <address@hidden> wrote:
_______________________________________________ Paparazzi-devel mailing list address@hidden https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
|[Prev in Thread]||Current Thread||[Next in Thread]|