Clarification about bbbmini HOT 22 CLOSED

The BBB(MINI) is powered by a UBEC 5V / 3A which is connected to the SYS_5V pins (P9.07 and P9.08) Power supply. High resolutions pictures will follow.

from bbbmini.

Is the use of a logic level converter necessary? I have so far a cape with a mpu9250 soldered properly and am waiting for my ms5611. from there I just need to know what else would be necessary. I already have a logic level converter as well.

from bbbmini.

from bbbmini.

The four ESCs are connected without logic level converter. The GPS is connected with logic level converter, but it can changed to 3.3 Volt I/O also. You should not connect 5 Volt signals to BBB inputs.

from bbbmini.

So I got my ms5611 in today and soldered it up. So I now have the mpu9250 and the ms5611. However I can not get ardupilot to detect both correctly. With them both connected Ardupilot automatically fails. With only the mpu9250 it fails on detecting the barometer. running the imu tests in the libraries\AP_IntertialSensor\examples it fails to detect the mpu9250 with both connected and reports a bad crc error for the ms5611. What could be causing this?

from bbbmini.

You have to connect the ms5611 even if you start the AP_IntertialSensor example. Could you post the console output, when you start the example (and the ms5611 is also connected).

from bbbmini.

Here is my output when running the test with both modules connected:
ubuntu@arm:~/ardupilot/libraries/AP_InertialSensor/examples/INS_generic$
sudo ./INS_generic.elf
AP_InertialSensor startup...
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
No INS backends available
Failed to boot MPU9250 5 times

If I disconnect pin 29 on the ms5611 it detects the mpu9250.

starting ardupilot gives me this output with all pins connected minus p9.29
for the ms5611:

./ArduCopter.elf

Init APM:Copter V3.3-dev (5f8c05b7)

Free RAM: 4096

FW Ver: 120

load_all took 132us
0 0 0 � ����Q��}�� �����Q�����3�����Calibrating barometerz�PANIC:
AP_Baro::read unsuccessful for more than 500ms in AP_Baro::calibrate [2]

root@arm:/home/ubuntu/ardupilot/ArduCopter# ./ArduCopter.elf

Init APM:Copter V3.3-dev (5f8c05b7)

Free RAM: 4096

FW Ver: 120

Bad CRC on MS5611
load_all took 128us

the bad crc on MS5611 has me wondering if the chip is the culprit.

On Sat, Apr 25, 2015 at 7:16 AM, Mirko Denecke [email protected]
wrote:

You have to connected the ms5611 even if you start the AP_IntertialSensor
example. Could you post the console output, when you start the example.

—
Reply to this email directly or view it on GitHub
#1 (comment).

from bbbmini.

Does the INS_generic run (the hole test) without problems when the p9.29 is not connected? Do you check the chip select lines (MS5611 P9.42 and MPU-9250 P9.28)? Can you post a picture of your board please.

from bbbmini.

With p9.29 disconnected and other pins still connected to the ms5611 does
not interfere with the mpu9250. I can run the INS_generic and calibrate and
test the mpu9250. with p9.29 connected it fails to boot the mpu9250.

AP_InertialSensor startup...
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
No INS backends available
Failed to boot MPU9250 5 times

On Sat, Apr 25, 2015 at 9:16 AM, Mirko Denecke [email protected]
wrote:

Does the INS_generic run (the hole test) without problems when the p9.29
is not connected? Do you check the chip select lines (MS5611 P9.42 and
MPU-9250 P9.28)? Can you post a picture of your board please.

—
Reply to this email directly or view it on GitHub
#1 (comment).

from bbbmini.

I just tested the version (5f8c05b7) that you also used, everything works fine on my side. May some wires are wrong. Which kind a breakout boards do you use?

from bbbmini.

http://www.ebay.com/itm/251637098006?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT
ms5611

http://www.ebay.com/itm/381029304894?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT
mpu9250

these are the modules i purchased

On Sat, Apr 25, 2015 at 10:34 AM, Alex Wright [email protected]
wrote:

With p9.29 disconnected and other pins still connected to the ms5611 does
not interfere with the mpu9250. I can run the INS_generic and calibrate and
test the mpu9250. with p9.29 connected it fails to boot the mpu9250.

AP_InertialSensor startup...
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
Failed to boot MPU9250 5 times
No INS backends available
Failed to boot MPU9250 5 times

On Sat, Apr 25, 2015 at 9:16 AM, Mirko Denecke [email protected]
wrote:

Does the INS_generic run (the hole test) without problems when the p9.29
is not connected? Do you check the chip select lines (MS5611 P9.42 and
MPU-9250 P9.28)? Can you post a picture of your board please.

—
Reply to this email directly or view it on GitHub
#1 (comment).

from bbbmini.

MS5611
Did you connect:
PS to low
SCL to P9.31
CSB to P9.42
SDO to P9.29
SDA to P9.30

from bbbmini.

The only thing not connected is ps to low. would that just need to be
connected to ground?

On Sat, Apr 25, 2015 at 4:34 PM, Mirko Denecke [email protected]
wrote:

MS5611
Did you connect:
PS to low
SCL to P9.31
CSB to P9.42
SDO to P9.29
SDA to P9.30

—
Reply to this email directly or view it on GitHub
#1 (comment).

from bbbmini.

Yes, that set the communication mode to SPI, otherwise it is I2C.

from bbbmini.

that took care of the issue. ArduCopter says that im ready to fly. I'll
solder up my servo/esc connections and start testing the other portions of
this build

Thanks for the help and responding promptly as well.

On Sat, Apr 25, 2015 at 4:45 PM, Mirko Denecke [email protected]
wrote:

Yes, that set the communication mode to SPI, otherwise it is I2C.

—
Reply to this email directly or view it on GitHub
#1 (comment).

from bbbmini.

I've got to bother you with another question. I was wondering If I have this mpu9250 oriented properly?

from bbbmini.

I have to look, but you can change it by modifying: https://github.com/diydrones/ardupilot/blob/master/libraries/AP_InertialSensor/AP_InertialSensor_MPU9250.cpp#L288

from bbbmini.

If you use the unmodified SP_InertialSensor_MPU9250.cpp file, the pin 1 dot of the MPU-9250 has to point to the left and to the tail of the copter.

from bbbmini.

From what you are saying, and with me assuming that vcc is pin 1 then with the way I have things soldered up I would need to either have the ethernet port side of the beaglebone black facing the left of the craft. If necessary I have no problem desoldering the breakouts from the protocape to orient better and possible even lay items out in a more concise manner.

from bbbmini.

Do you already connect your board to a ground station software via Ethernet? There you can check if the orientation fits. If it not right you could change it in software as described earlier. I add the orientation to the documentation yet.

from bbbmini.

No ground control station yet. Couldnt find anything in the gentoo repo's.
Will probably install something on my odroid u3 that is running ubuntu to
use in conjunction with the beaglebone black. Will probably try to get that
going when I get home from work later.

On Mon, Apr 27, 2015 at 3:53 PM, Mirko Denecke [email protected]
wrote:

Do you already connect your board to a ground station software via
Ethernet? There you can check if the orientation fits. If it not right you
could change it in software as described earlier. I add the orientation to
the documentation yet.

—
Reply to this email directly or view it on GitHub
#1 (comment).

from bbbmini.

I switched the orientation of the module after getting it hooked up to mission planner and seeing that it was indeed soldered incorrectly. This is good to go now on my part. I will be getting the power for the beaglebone black and servos situated now.

from bbbmini.