hello

after takeing the bosch 085 bro out putting instead ms5611 i2c 3.3v

thanks to Frank Al for sharing this http://diydrones.com/forum/topics/just-a-thought-barometer-apm1-vs-...

I get  initializing constant (solid red led) and when I run tests

looks like the baro isn't calibrated when I try to calibrate it it get stuck  

i run varies test using arduino and all seems fine even the new ms5611

what am i doing wrong?

any tip maybe regards modifying the code to ignore or disable the onboard baro bosch as it has been removed and replaced with the ms5611?

where in the code can i modify it?  

Views: 2443

Attachments:

Reply to This

Replies to This Discussion

i have added the AP_Baro_MS5611_test serial output

Hi Elad,

There was no need to remove the bosch baro because it has another i2c address. Are you sure no collateral damage was done ?

The only thing you really should do is make the correct connections, place the solder-jumpers, replace the AP_Baro_MS5611.cpp and put #define CONFIG_BARO AP_BARO_MS5611 in APM_Config.h

The latter prevents initialization of the bosch baro. In fact, I just use the standard MS5611 arducopter code but communicate I2C instead of SPI.

Btw: I didn't test 2.9 yet.

I use arduplane maybe that is the reason

I double checked everything I could using the examples test

the only issue I can see is when it gets to the initializing of the baro it get stuck then it continue with apm initializing constant

I will have a scope this weekend then I could check the actual signal and see if any damaged but I believe it is just a code problem as I had the baro test in the photo at the first reply

the only damaged done to the shield as far as I could see is small trace of the old bosch baro that pulled up and been cut

added better resolution photos no reason

The results from your test shows something is wrong. Values are constant while they're suppose to differ a little bit each time. Temperature should show a rise when you put a finger next to it. It's really sensitive.

So basically, start using the testcode until the readings are ok, continue testing the arduplane code.

frank thank you so much!

after reading that you test it to firmware2.9 I understand that you using the copter version tried it with arduino edit uploaded and everything is lock and load :)

still need to test code the new ms5611 as like you said it isn't looking right plus need to check the compass as it to show strange results but now that the initializing is done i have one less thing to worries about

so looks like the problem is in the ardupilot code and I would appreciate if any one can help

me figure out how can I modify it or where?

Oh yes, that's right, I did the modification for arducopter. But whatever Arduthing it concerns, a test program should show correct figures. The program I used to check the 5611 (test1i2c.cpp.hex) is attached. It uses my modified code.

It's compiled for a Mega2560. Use http://kmtronic.com/upload-hex-files-to-arduino.html to upload it to your board.

So if this runs ok, than at least the hardware is ok, don't you agree ?

Attachments:

looks like the readings are normal

i have no doubt about the hardware but still good to be sure about it

will have a scope on the weekend so i'll look for interference i think that if i'll extend the wire for both the compass and the baro the interference should be gone but maybe it could be resolved in a more aesthetic way

Yes, that readings are fine indeed! Is that 22.3 your outside temp too ? Better than here in holland... :-(

winter time temp varies between ~25 - ~15 at night but the moist make it a little bit colder but summer time is just like standing next to no not next to but inside an oven no not oven but sauna

feel that way too

 

Hi Elad!!

Any progress?

I did this steps  but my copter didn't arm any more. 

I need your help?

 

done and done

was a version difference once fixed everything went smooth :) 

I tried 2.9.1b  verson. it did not work.

Are you using 2.8.1 version?

Reply to Discussion

RSS

© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service