Re: [Paparazzi-devel] Lisa M v2.0, aspirin v2.1 IMU freeze

[Felix Ruess]

Hi Loic,

Which paparazzi_version are you using? And are you trying to use an aspirin2.1 with an external MS5611 or do you really have one with the baro mounted on aspirin imu (v2.2)?

The <configure name="LISA_M_BARO" value="BARO_MS5611_SPI"/> currently only works for the rotorcraft firmware, it has no effect for fixedwing.

So you shouldn't even have any baro readings in fixedwing (unless you added a module to read the baro).

Also are rather doubt that this is directly related to exposing the baro to light.

A quick guess is that since the baro is not read in the fixedwing firmware, the baro CS line is floating and it causes trouble.

So probably related to https://github.com/paparazzi/paparazzi/pull/369

Cheers, Felix

On Mon, Jul 1, 2013 at 5:27 PM, Loic Drumettaz <address@hidden> wrote:

Hi,

I have a lisa m 2.0, with imu aspirin 2.1. The IMU raw values (ACCEL, GYRO and MAG) all become equal to -1 when the baro MS5611 is exposed to the light!

It looks like the baro is not only sensitive to the light (as BMP085), but also perturbate the other sensors...

The most surprising is: that only happens using Fixedwing firmware. I couldn't get the same error using rotorcraft firmware.

What could be different between fixedwing and rotorcraft firmwares when using:

<target name="ap" board="lisa_m_2.0">
<subsystem name="imu" type="aspirin_v2.1"/>
 <configure name="LISA_M_BARO" value="BARO_MS5611_SPI"/>

Any ideas?

Regards

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