SB_0000001 Critical service bulletin for Beta Cube 2.1

Yes you can :slight_smile: Kapton tape will work

1 Like

We specifically released this batch as a Beta batch.
We have highlighted the following issues…

  1. Case slightly loose… (cosmetic, no flight risk)
  2. Cable to Buzzer too short
  3. Zener diode on bower brick fitted with incorrect value, no effect on flight.
  4. One unit had an incorrectly mounted IMU. Prearm checks caught this, no risk to flight
  5. This issue, flight risk, immediately proven, verified, and a notification issued, with support from the Ardupilot Development team to find a software workaround while we get the repair kit to people.

I will continue to highlight my errors. And I thank those reporting the issues, so we can find and correct them. I hope we have found them all, but we will keep looking, and keep being honest.

3 Likes

Just as a side question…what for are this 4 pads?

Thanks for that @tridge.
As always the Ardupilot team come through with solutions and workarounds.

Thanks @proficnc for the honesty and quick notice to users.

2 Likes

PWM out… so you can set up a small vehicle without a carrier board…

1 Like

Also i would like to add;be careful when you use mounting screws on carrier board bcs. they can touch servo pins if tighten to much…

I get my Pixhawk 2 Suite on end of November (first batch) should I worry
or not ? I do not understand this information. It refers to beta cube
or all copies produced in 2016 ???

How thick can the insulation be?
I have some 0.13 mm plastic washers.
Will it work?

Kapton Tape

i think that is same tape you remove from HP toner printhead…

If I received the cube in 2016, it’s part of the “beta batch”?
I keep getting compass and gyro errors randomly… I can reboot the board and they’re gone, reboot again and they’re back.

and is it necessary to set servo1_function to 0?
(I just got the service bulletin when I updated MP)

Moved esc1 to esc7… weird stuff… I’m assuming that means my cube is f’ed.
Bad gyro health a million times…
I ran the calibrate level, and it stopped for now.
The mag field value dropped from 500 to 460

I’ve spent almost 2 months trying to figure out what I’m doing wrong… if this turns out to be the problem… ugh.

Do you know the serial numbers affected?

download the update for mission planner and it will either direct you here or not. (only thing I know to tell you)

well, stupid me… I just went to fly the drone, and it took off and went straight for a tree 30 yards away… the entire copter virtually demolished… lying upside down on the ground with one prop spinning at full throttle.

If anyone would like to see the log file, let me know.

if you received the cube in 2016, normally it’s part of the beta batch
and i had the same problems with my cube (bad gyro health, compass errors and some others problems)

That’s weird… I looked over everything again, and I don’t see the word “beta” anywhere. Or any mention that what I was purchasing was anything other than a released product. Did they send you a replacement?

Hey there,

I’m using the Pixhawk 2 with Arducopter 3.4.4 Traditional Heli, and changing RC5_FUNCTION to 33 and plugging the servo wire from channel 1 to channel 5 doesn’t have any effect. Is anyone else having the same problem or knows how to fix this?

Cheers

I’m flying Pixhawk 2 with Copter v3.4.4 and I too received the Pix2 back in November. Today I conducted my maiden and it ended it a crash. The only way I could make the compass variances to go away was by unchecking compass #2. My quad had a tendency to lift the tail at a much faster rate than the nose, first attempt it flipped over. Second attempt I made sure to raise throttle more carefully and still the tail was lifting up way before the nose. I kept on trying to compensate for it until I was able to leave the ground, only to see the quad to start a yaw right rotation and crash land.

@frizensami unfortunately that workaround won’t work with TradHeli in the 3.4.4 firmware, as heli in that firmware controlled its servo mapping directly (unlike multicopter).
If you use the 3.5beta that is out now then it will work. You can set SERVO5_FUNCTION=33 and it will move the first swash servo to channel 5.

@tridge thanks for the help!