[Top][All Lists]

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

Re: [Paparazzi-devel] Baro ms5611

From: Helge Walle
Subject: Re: [Paparazzi-devel] Baro ms5611
Date: Mon, 26 Jan 2015 10:09:39 +0100

Hi Felix,

I updated v5.4 and now the ms5611 baro is working! Also I tried on v5.2 and everything works there as well.

So I must have done something wrong when I tried on v5.2 before posting the problem. Sorry for that. The Logic screenshots were from the v5.4 testing.

Thank you very much for your help!


2015-01-25 23:28 GMT+01:00 Felix Ruess <address@hidden>:
Hi Helge,

Seems that with Freeks fixes for the Bebop ( there was also an error introduced in the ms5611 peripheral.
Found the probably problem and since it seems that Freek already found and fixed that bug as well, I just cherry picked his commit to master and v5.4.

So can you please update and try again?
But since this bug was not in v5.2 you should have seen a difference there (if that was indeed the cause in your case).
If you still have problems, please post the configuration you are using...

Cheers, Felix

On Sat, Jan 24, 2015 at 4:08 PM, Helge Walle <address@hidden> wrote:

Please see attached images. Screenshot_1.png showing 10s and Screenchot_2.png showing 0.6ms from the logic analyzer.

As part of trying to get two ms5611's working at the same time with my Twog, I first wanted to get the baro on my Drotek 10dof v2 working. I placed the defines for the baro in the airframe file, as stated in the wiki. After this, the imu worked fine, but I got no data from the baro.

I had a closer look at this, with these results:
- Connected the logic analyzer, but saw only imu messages. There was one for the baro however, see below.
- Removed the defines for the imu, to look specifically for baro messages.
- Now the analyzer showed only one single sequence of communication with the baro; after 1.5s<t<2.0s. See screenshots. After that the i2c bus was silent.
- Had a closer look at the specific sequence, which showed Twog connecting to the baro, getting an ACK, one new message and ACK, then nothing more. There are two "spikes" in the communication sequence, which look strange to me.
- Connected a standalone ms5611 baro instead of the Drotek imu, and got the same results.
- Defined and connected a bmp085 baro to the line, this worked just fine.

I use v5.4. I also tried with v5.2 but could not see any difference.
I need to look into the ms5611 driver later anyway, but would be grateful for any input on this.
BTW the Twog has a rather low i2c frequency at 37.5kHz, but I think this should not be a problem (?)


Paparazzi-devel mailing list

Paparazzi-devel mailing list

reply via email to

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