That’s correct, it sends us the information, so we can follow up with serial numbers etc
Thanks
@philip
My apologies for my message but since it seems that either i did not understand the “check” instructions properly or all my boards, even though i got from my supplier in 2019 are most likely a 2018 production and to make it clear for all:
a) Download latest MP beta update and reboot
b) download latest copter beta (3.6.8-rc1)
c) connect board and see if you will get any error or contact message.
Unless you get this you are good to go?
No, just because it passes, that’s not enough.
Unless you are specifically doing beta testing, or flying thing that are ok to crash… in areas that are ok to crash
The grounding is still in force!
Once we know exactly the batches affected, we will let you know
Hi Philip,
An friend of mine in South East Asia has a crash with one of their Copters with FLIR camera during a job few days ago. Started to jerk around like crazy for no apparent reason and then fell to the ground. He did not get the news on time. He usually sends me his logs whenever he has trouble and is not sure what happened. When he sent me this, the first thing I looked for is the ID in the parameters.
Should he contact you directly? As I do not have the Cube myself I do not get popup in mission planner, so not sure where the logs need to be sent. I have his logs so I can forward them to you with his contact details.
As a side not I do not know exactly which retailer they get their Cubes from, but I am yet to see any Cube retailer send out a warning email or post warning. We are registered at a few outlets (from older purchases) ourselves and I am yet to get any such emails. I urge you to urge them to do so and not take this lightly. Not everyone uses facebook or in is your group (my friend it not) and not everyone buys directly from CubePilot so would have not gotten your email about registering on your new forum.
Feel free to post this link on whatever forum, BBS, Twitter, electricity pole whatever.
We operate as a community, we have posted on the ardupilot forums, on Facebook, all over the place. But we rely on the community to assist with getting information out.
The one source of information for the cube is here. This needs to be part of people’s checks.
This is aviation, important notices will be here.
I will prompt all resellers again.
2 Likes
I would not post this notice externally anywhere. I am not a Cube reseller. I do not want to step on anyones toes or hurt anyone’s business.
I did post the link as you well know on Facebook Cube group, I called your attention to the fact that many did not get this info the first time as it was not pinned. Also that till date the older ground has more registered users than the new one. Also made suggestion about sending out the email which I am happy you did. I think this is exactly what you describe as a community effort.
Even now my suggestion was in this line, that you do prompt all resellers about this again. You can understand that everyone is hesitant to not hurt their businesses, so I guess they are all waiting to see how serious the situation is and how their counterparts react.
Anyway I did not get and answer to my question. About what he should do. Contact you directly? I mean his log might help with tracing the issue or you have enough logs already?
He should update mission planner and update his cube to lates Cube black copter beta.
Then after the update is completely done, connect.
It “should” detect the error and give him the opportunity to register the faulty cube
Thanks. Will let him know.
Tested the fix. No issues
Thanks!
can the 3.6.8-rc1 be used to fly normal like the 3.6.7?
Or is it only to test the fault?
Yes, but only on non grounded cubes.
I am ready to go with plane beta firm
Once copter is released as non Beta, we will be reducing this to a “Use extreme caution”
The software doesn’t “fix” the hardware on a broken cube, but it allows normal cubes to fly with the knowledge that if something goes wrong, a failover to the working sensor should get you home.
3 Likes
We have purchased Pixhawk cube flight controller in month of November.Is this flight controller also need to be checked.
This is not in the batch we are concerned abou
Hello Philip,
Thanks for all the information you gave. I ordered the Cube Combo on February this year. My Quad was ready for first take off in the mid of March but it never flies till now.
The error “your board has a critical service bulletin” aren’t appears in Mission Planners massage window after booting the Cube, or should I look somewhere else?
After all, by missing the message doesn’t mean that there is no failure on the PCBs between the inner layers 2 and 3! It would be better to start an exchange-service for all Cubes that are produced in the period in question.
I do all the updates you informed in Ardupilots blog.
I don’t understand why you didn’t inform in the blog which serial numbers are affected. In your own interest is the publication of the first serial number from there on definitely no Cubes aren’t involved.
Also the procedure CubePilot tries to find an approach isn’t really professional. The better way, as far as I concern, is having a complete isolated test routine as an EXE-File instead of using the Mission Planner and the Arducopter firmware (sorry).
A few points
As I have stated. Please let us finish our investigation.
When we have a list of serial numbers, we will release it.
FYI, the serial numbers are processor individual unique IDs… these do not always arrive to us in sequence.
Not every IMU pcb is damaged. We are trying to narrow this down as much as possible.
Once we have all the information, and not before, we will move onto the next step.
I can assure you that us spending time responding to everyone, is not speeding this process up, nor is it fixing the problem.
We use mission planner to do the identification, because 90% of our customers use Mission Planner. I have no idea why or how some brand new customised application would be in anyway better than a tool that our team has that has nearly 9 years of experience with…
Moving on…
I tested yesterday a quad with 3.6.8 beta, works normal. Tested autotune, and other modes. Was in air for at least 40 minutes.
Awesome news!!