paparazzi-devel
[Top][All Lists]
Advanced

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

Re: [Paparazzi-devel] Trouble getting Eagle Tree Airspeed Sensor working


From: Cameron Lee
Subject: Re: [Paparazzi-devel] Trouble getting Eagle Tree Airspeed Sensor working
Date: Tue, 11 Jun 2013 11:28:24 -0600

Thanks for your help guys. The only difference I see between your airframe files and mine is that you've defined SENSOR_SYNC_SEND under the target, not in the airspeed_ets module like I did. I'll give that a try tonight and see if it works. If not, I don't know what the issue could be other than maybe a hardware problem with my TWOG.

Thanks,

Cameron


On Sun, Jun 9, 2013 at 2:38 PM, Helge Walle <address@hidden> wrote:
Hi,
 
The attached airframe file works with my ETS airspeed sensor, Sparkfun SEN-10121 IMU and BMP085 barometer on the same I2C bus.
I paid some attention to the pullup resistors on the bus and removed the ones on the barometer to get a (in my opinion) sensible total value.
 
I use a TWOG and v4.2.
 
Helge.

 
2013/6/9 Cameron Lee <address@hidden>
Hello everyone,

I recently got the Eagle Tree airspeed sensor so that I can use the energy based altitude control loops with my plane. However, when I follow the instructions as per here: http://paparazzi.enac.fr/wiki/Module/Airspeed_ETS the code build's fine, but once I upload it to the TWOG, there is no telemetry sent. I believe this is a different problem than the widely reported issue of the Eagle Tree Sensor only working when the autopilot is flashed, not when the autopilot was booted up normally.

I've double-checked the wiring, and the sensor works fine on it's own - I can see the max speed on the LCD display. Nothing appears on a scope when looking at the SCL or SDA lines - this would make sense if the TWOG isn't doing anything right?

Here's the airframe file I'm using (pared back to just measuring the airspeed, no energy control). This is all in v4.2, although I've also tried in v4.0 without success:


I also determined that the issue doesn't happen when only <define name="USE_I2C0"/> is added. It happens when the ets airspeed module is loaded: <load name="airspeed_ets.xml"/>.    

Any ideas for further troubleshooting or help regarding this would be very appreciated.

Cameron Lee

_______________________________________________
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



reply via email to

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