It’s very unlikely that your crash was caused by this. Two reasons.
First, a quadcopter usually won’t go very far with one motor stopped. Second, you clearly have an EKF problem.
1 Like
Yes, all 6 motors full speed, then 5 stopped when they smashed the tree… indeed, it did not go very far at all after that.
I don’t think it’s the issue which prompted this service bulletin, but I do believe it’s a problem with the cube or “beta” cube.
I was really hoping it was something wrong with my transmitter… but I’ve since thoroughly tested it, and can’t find anything unusual.
If anybody would like the logs, I have the sd card now… and can post them here or a new thread, which would be a better idea I think :-).
Please raise an issue, and provide logs.
Raise it as a new post, please keep this thread clear for SB related information
@proficnc That would probably explain why my quad flipped mid-flight without Tx input and crashed? Are there any plans to compensate users who are affected like that? (I was lucky, only landing gear and props, but others probably have it worse)
Also, I missed out on the part of my $269 PH2 being a beta version - it doesn’t say that on the invoice or in the title. @devere mentioned the same issue. Please clarify on that.
Since I received mine in 2016 and you said
I believe I’m in there.
What date of purchase and delivery do you have.
I bought in October 2016 and delivery in January 2017.
I do not yet know if mine is affected.
I speak English and I do not know.
I would like to clarify again… this issue has NOT caused the loss of ANY vehicles, we released this as soon as the possibility of this issue was seen.
If you are having an issue with your system, make your own post, post exact details of your vehicle, and POST YOUR LOGS!
speculation doesn’t help anything… if we find issues, in software or hardware, the community will help.
did you post your log? if you do, a new post is what is needed.
regarding compensation… if your unit was proven to be the cause, then it would be replaced.
there is no flight controller that offers to replace anything other than the part that you purchased. Who did you purchase it through?
please get involved in the community, facebook, gitter etc.
I’m just in the process of insulating the little potential short detailed,probably by grinding the nut away, but I won’t know until I get the cube seperated.I’d already fixed the rattly cap with hot glue,so that’s not a problem.What is a problem is that one of the tiny grub screws has sheered off half of it’s cheesehead and so can’t be loosened.Another one hardly grips at all ( it only tightens on the last two turns so won’t self extract) and I had to strggle to extract it.So I’m no nearer fixing the problem.I’m going to try sticking a driver to what’s left of the screw with superglue to see if I can extract it.I was less than impressed by these grub screws when I first encoutered them.Now I’m starting to really hate them.
Update: All sorted out throught the Facebook page via a very helpful third party.Thanks Charles.
I still hate the grub screws.
Another edit: I’ve got a new cover on the way but I got this one off as once two screws are removed on the one side the cover just slips off.Only took me an hour or two to realise.Grinding the nut was a doddle but I kappa taped it too.
hello, when you say “One unit had an incorrectly mounted imu, Prearm check caught this…”, you mean the prearm check warns us or it compensates values etc ?
You do a really great job,
thank you
It stops it from Arming
A small update from me.I’ve just received my replacement cube shell so thanks very much whoever was responsible for doing that.In the meantime I did two mods as a belt and braces approach to sorting this little poser.I ground the corner off of the nut and then I stuck a bit of Kappa tape over the contacts so I shouldn’t get any shorts happening any time soon.I expect I’ll stick a connector on the wrong way around at some point but for now I think I’m safe.Hope these mods help.
1 Like
Dear Proficnc staff
We ordered the Cube B version and got through the procedure and fixed the thing, but next we installed Mission Planner and had to external compasses mounted: and when connecting the drone we got an inverted horizon ie blue at bottom part, green top, and error messages bad compass health, etc. We disconnected the external compasses and GPS but in spite of that we saw in the calibration large differences in the compasses (it seems that the calibration is then of the 3 internal compasses, since the external ones were disconnected. Next, we tried to change the differences in the compasses by inverting eg roll 180 so that the difference in Y value would be corrected, Never-the-less no solution and the horizon is still “green”! So since we cannot resolve it and understand that others had similar problems, we need to have a fix to this issue: PLS help with a fix quickly. Best regards, Winfried
Can it be that you need to change the the board orientation in order the horizon be at top.
Pixhawk 2 configuration from factory is inverted.
1 Like
You need to set your AHRS to 0, you will find its set to 12.
1 Like
I had a recent crash with a P2.1 beta. I believe the issue was related to a motor failure. Unfortunately, that motor happened to be on RC_OUT 5 (on a quad) which makes me suspicious. Can someone help take a look at my logs and see if we can rule out anything related to this bulletin?
I replied on your post. The short version…
If you were not using PWM1, then your crash is unrelated to this issue.
Things to post on the other thread that will help narrow down your search.
Photos of your setup… lots of them.
Motors? ESC’s? Any additional information
When do we expect to receive the kit?.thanks