SB_0000002 Critical service bulletin for Cubes Purchased between January 2019 to July 2019. DO NOT FLY

Mandatory Safety Bulletins
100

Awesome news!!

101

I have an older 2016 cube. Got the error message but the service bulletin is SB_0000001. Takes me to the fix for channel 1 problem. I fixed that back in 2016. I’m good to fly right? Any way to reset it so the error message doesn’t come up? Down the road though, no rush.

102

You are good to go. That is an early one! Thanks for purchasing from the first batch!!!

That is just a note to let you know the sb1 applies to you. If you have done the mod, you’re all good :slight_smile:

Well worth checking in on that though! Better safe than sorry!

103

Thanks for the fast reply and good luck with getting the other issue sorted!

104

It’s obvious from your picture. You did not follow the instructions fully. Download latest Mission Planner msi that way you get the latest drivers then update the beta. We’re your picture shows “fmuv3” it should read “cubeblack”.

105

FYI: QGroundControl Stable build 3.5.1 was just released which includes the same check/warning as Mission Planner for the Cube Black issue. QGC Stable Build users should be notified to upgrade the next time they restart QGC. New Daily Builds of QGroundControl with the check will be available in about an hour.

1 Like
106

Thanks for info Don

107

Thank you Don.

Other things to watch…

  1. BRD_TYPE for cube black is 3

I have two reports through as 6… this is for cube Purple :slight_smile:

  1. Solo cube is not a CubeBlack… it’s built by 3DR, FMUV3 is the correct firmware for it.

  2. Some have put CubeBlack code on Pixhawk 1’s… this is fmuv3 if it’s new processor, and fmuv2 for old…

So far… only 9 cubes faulty in the community…

108

I’ve mentioned this in a number of places before: If you find something missing in QGC+ArduPilot please let me know. In general I can change things pretty quickly. Best spots to reach me for questions are at:

2 Likes
109

Thanks Don
Applies to everyone in this community, we cannot guess what you need :slight_smile:
Tell us, none of us are hard to find.

110

EDIT: 27th of April 2019: Ardupilot has now added detection, prearm checking, and inflight checking and failover to the redundant sensors. This is now in Release Copter and Release Plane.
Detection of the fault has also been added to Mission Planner, and QGC latest. Mission planner now collects information on this fault if you are willing to send it to us.

As such, we are reducing this service bulletin to flight is possible under the following conditions:

  1. You MUST run Latest Ardupilot RELEASE code.
  2. You must use latest Mission Planner or Latest QGC
  3. If QGC or Mission planner flags your code, contact your local re-seller, and log the issue. DO NOT FLY TILL I HAVE PERSONALLY CHECKED YOUR LOGS, and either given the go ahead, or, organised what we will do next in your case.
    4.Further flight is only to be conducted where you have carried out a full risk assessment on the implications of a failure occurring, the new code is good… but it should not be relied upon as your only means of protection. You must not fly over people, you must not fly over critical infrastructure, you must also take responsibility for your payload and vehicle.

Failure to comply with these requirements may lead to serious damage, injury, or death.

3 Likes
111

Hi Don,

i’m installing Q 3.5.2 and Ardu 3.6.8 on my Pix 2 boards to check, can you show how Q comunicates error? Should a pop up come? Or a row in the message window?

112
  • You MUST run Latest Ardupilot RELEASE CUBE BLACK code.

How can I do that? I installed the latest Mission Planer und tried a Firmware Update, but it says Error Uploading firmware. Can you please give more details, how to proceed. The ID check was fine, but it was said, that this is not sufficient.

Furthermore, we must suspect it is a hardware issue. When can we expect a replacement?

Thanks!

113

It’s been a few days since last post.
Any update?

114

Any issues with mission planner, can you please ask on the mission planner section?

The current news is to test with mission planner, and do a risk assessment before takeoff.

We will discuss other issues after we start shipping again.

Most likely it will be a return for repair if you have a broken cube.

115

@philip @DonLakeFlyer @Michael_Oborne

Can you guys please post screen shots of what the error/notification/popup/warning in each of the gcs softwares look like? Maybe it could go up in the OP? I think it would be helpful to know what we’re looking for.

116

@philip - I just received a cube I ordered 4/19 from robotshop. (Obviously before I was aware of this SB).

I did not get a warning from MP on initial setup. Does that imply that my cube is not affected? Are the HW ID numbers posted in OP still valid? (Mine match the original post)

Robotshop must have old(er) stock - do you have any guidance for end users who purchased after Jan 2019, but from a distributor that potentially has old stock? How can I confirm?

117

At this point, until we are finished our internal audit, assume any cube that you have from this year is affected.

118

No, acutally I have no issue with Mission Planer. I want to know, how I can do that:
You MUST run Latest Ardupilot RELEASE CUBE BLACK code.

Where do I get the code from and how do I get it onto the Cube.

119

You load the firmware via the standard method of loading firmware in mission planner.

When attempting to load firmware, if mission planner detects that you have the non cube black code, it will ask if it’s s cube black. Say yes… then it should automatically put the correct firmware on