Re: [Paparazzi-devel] Critical behaviour of baro_ms5611

On Tue, Jun 10, 2014 at 4:27 PM, AFISH <address@hidden> wrote:

Hi Felix

Thank you so much for your attention. But is that possible you change some code in the subsystem just limite the raw sensor data range, I can try if that can work. From the log you can see, the wrong raw data is huge different to the normal range of the baro_raw. I guess that is close to the limitation of int32. I don't know where to change it, but my idea is, for example if baro_raw is more than 10 times of 100 times of normal range, just abandon it. Can you help me? Tell me where is the code I can do for this, I can do some test.

—
Sent from Mailbox for iPhone

On Tue, Jun 10, 2014 at 9:22 AM, Felix Ruess <address@hidden> wrote:

Hi,

sorry, I have no idea what causes this problem and I can't reproduce it on my board with Aspirin2.2.

Did anybody else notice problems with the MS5611 barometer?

Felix

On Thu, Jun 5, 2014 at 11:28 PM, AFISH <address@hidden> wrote:
sorry log file is tgz file
—
Sent from Mailbox for iPhone

On Thu, Jun 5, 2014 at 4:15 PM, afishindouban <address@hidden> wrote:

Hi Felix

I create a new user in my system and install a new paparazzi environment to
make the test.

Here is the build version: Paparazzi version
v5.1.1_testing-68-ga15d707-dirty
Here is board info: Using device 013: ID 1d50:600f Transition Robotics Inc.
- Lisa/M (Upgrade) V1.1 - LM2-385 34FFD6053452323353321643
Programming memory from 0x08002000..

and attach

the test result shows when telemetry in default, after GPS 3d locked, GCS
show alt can jump from -15000 to 15000m.
if I change telemetry to raw_sensor, check baro_raw message,abs value is
show normally around 74800, but timely, it will jump to around 4294803968,
and then become normal, and repeat frequently. I guess this is the reason
cause the alt number get crazy? looks like no filter abandon this number
which for sure are abnormal, and i dont understand why baro_raw has this
kind of behave. then I change to antoher lisa board I have, the same happen.
here is the logs: logs.z <http://lists.paparazziuav.org/file/n15634/logs.z>
here is the airframe: microjet_lisa_m.xml
<http://lists.paparazziuav.org/file/n15634/microjet_lisa_m.xml>

Please help me have a look. Thank you so much.

Kevin

flixr wrote
> Hi Kevin,
>
> Just checked again on my LisaMX with aspirin2.2 and I don't see any weird
> spikes like this.
> You could try with latest master, if it still occurs, please post your
> full
> configuration.
>
> Cheers, Felix
>
>
> On Thu, Jun 5, 2014 at 3:50 PM, AFISH <

> afishindouban@

> > wrote:
>
>> Hi Loic
>>
>> I use a 3d printed case protect Lisa board. And there is no light get to
>> the back side of the Lisa board where asiprit 2.2 IMU mounted.
>>
>>
>>
>> —
>> Sent from Mailbox <https://www.dropbox.com/mailbox> for iPhone
>>
>>
>> On Thu, Jun 5, 2014 at 5:23 AM, Loic Drumettaz <

> loic.drumettaz@

> >
>> wrote:
>>
>>> Hi,
>>>
>>> Please check that your baro is well protected from light. Baros are
>>> sensitive to light.
>>>
>>> Regards
>>>
>>> Loïc
>>>
>>>
>>> 2014-06-05 9:17 GMT+02:00 afishindouban <

> afishindouban@

> >:
>>>
>>>> Hi Felix
>>>>
>>>> As you mention below, Also I check the branch master sample
>>>> Microjet_lisaM,
>>>> that configuration is same as your description.
>>>> So I just build and flash to my transition robotic Lisa/M2 AP. and the
>>>> GCS
>>>> ALT number getting crazy. So I turn on RAW_SENSOR, I found baro_raw is
>>>> not
>>>> stable at all. some time has peak value absolutely high. this should be
>>>> the
>>>> reason of my ALT number get crazy? what could be the reason of that? I
>>>> show
>>>> you the plotter of that to you.
>>>>
>>>> <http://lists.paparazziuav.org/file/n15618/53.png>
>>>>
>>>> Thank you so much
>>>>
>>>> Kevin.
>>>>
>>>>
>>>> flixr wrote
>>>> > Hi,
>>>> >
>>>> > just
>>>> >
> <configure name="LISA_M_BARO" value="BARO_MS5611_SPI"/>
>>>> > is enough.
>>>> >
> <define name="USE_BAROMETER" value="TRUE"/>
>>>> > is only needed if you want to
>>>> > use for altitude estimation in
>>>> >
> <subsystem name="ins" type="alt_float"/>
>>>> > .
>>>> >
> <configure name="USE_BARO_BOARD" value="TRUE"/>
>>>> > is not really needed (since
>>>> > TRUE by default on boards like Lisa/M that have a baro).
>>>> > Remove
>>>> >
> <define name="USE_SPI_SLAVE3"/>
>>>> > and the baro modules.
>>>> >
>>>> > Cheers, Felix
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://lists.paparazziuav.org/Critical-behaviour-of-baro-ms5611-i2c-tp11592p15618.html
>>>> Sent from the paparazzi-devel mailing list archive at Nabble.com.
>>>>
>>>> _______________________________________________
>>>> Paparazzi-devel mailing list
>>>>

> Paparazzi-devel@

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

> Paparazzi-devel@

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

> Paparazzi-devel@

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

--
View this message in context: http://lists.paparazziuav.org/Critical-behaviour-of-baro-ms5611-i2c-tp11592p15634.html
Sent from the paparazzi-devel mailing list archive at Nabble.com.

_______________________________________________
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

From:	Felix Ruess
Subject:	Re: [Paparazzi-devel] Critical behaviour of baro_ms5611_i2c
Date:	Tue, 10 Jun 2014 17:51:03 +0200

Re: [Paparazzi-devel] Critical behaviour of baro_ms5611_i2c