Some days ago I was flight my hexa, and sudenly the cube just shut down and fell like a rock.
My Setup is:
-Minicarrier
-Pixhawk black cube
-HereLink Air
-Mauch Current and Voltage sensor
-Mauch Power Source (it power the Power the Mauch sensor, and this one power on the Cube)
-5 and 12V BEC to power the HereLink and the camera systems (this time was with no camera).
Frame: HEXA
13-Dec-19 3:57:11 PM : CubeBlack 0027002C 3138510E 35363631
13-Dec-19 3:57:11 PM : ChibiOS: d2030d88
13-Dec-19 3:57:11 PM : ArduCopter V3.6.9 (632be63f)
As you can see in the picture, the cube stop recording and 10 meters, that is what I saw more or less from the ground.
I dont see a current spike, thinking about a shortcut some where.
When the drone was on the ground after the crash, I hear a little sound from the speaker, like tok, tok, tok. The cube was energized, but like stuck. How can I realize if this was because the bug reported on the SB5?
Finaly here is a video of a strange sound of the Cube at the startup. This sound always be there, even before the crash, but no other cube I have make that sound at the startup
Doesnt look like i2c issue, could be but there isnt any watchdog message afterwards, it may not have had a chance to reboot though. Id be looking at your power wiring, that doesnt look like a mauch Vcc
But what do you mean with the VCC doesnt look good? The voltage difference between the min and max never went more than 0.120V, and never went down the 5V. As I understand, the min voltage of the cube to work is 4.7V.
And of course is a mauch here is a picture of the wiring. The Mauch energize the Mauch Voltage and current module, and this last one module power up the cube.
your voltage sags and current goes up…yup thats a classic sign of a short dude…you lucky it didnt last too long and burnt your bird down…check ESCs, motors, fryed wiring, etc…mauch is pretty good stuff so I doubt that was it…
This is a tough one. I think there are two possibilities, both of which you already know:
Electrical short
I2C interrupt bug
It is hard to tell the difference between them from the log. There is a small current increase and voltage sag happening at the same time as a roll attitude divergence which may suggest a short, but there’s not enough info to confirm that.
There’s a few things you might have noticed that could help determine the cause.
Did it sound like the motors turned off (suddenly sounded quiet) and the drone fell, or did the motors keep running and power itself into the ground?
Did you notice if the video or TX telemetry cut off when the drone fell?
Was the drone still powered after it crashed?
Since the crash, have you powered the drone with battery and checked if everything powers on?
The drone was in front of me, so I can tell you the motors just stop in the air and fell.
I was not looking the video at the moment (anyway the drone have no camera because I was trainning a customer), because I was training a customer, so we were looking at the drone.
After the crash the FC was on, the battery didnt come out, but like stuck, it was making a sound like Tock, tock, tock… but no data, no nothing, just that strange sound.
After the crash, on the bench, the first I did was to check the XT90 for a short (measure the continuity with the tester), but was ok. I have check for broken cables because the crash and everything was ok. I have plug in the battery, armed the drone and run the motoros without props several times and several minutes and was ok.
The only time I’ve heard the “tok tok” sound is when I power the Cube with USB and the peripheral devices are drawing too much current. The Cube will keep re-trying to boot, and the buzzer will make the sound every time it tries. I assume the power selection module is detecting over-current on the USB power rail, causing it to reset.
But at the moment, nothing was pluged during the flight, is just a “service” port to connect the computer.
Sorry for the mess of the cables, thats is how the drone is after the crash, I dont want to take it a part yet until discard all the “physical” problems it could have.
I see you have both main power inputs connected, but the log says you only have power 1 connected (POWR.Flags = 1). Is there something wrong with power 2?
