Cube orange randomly reset parameter to default

ArduCopter Copter 4.0
, ,
29

The fix is actually to the bootloader and there are upgrade instructions here on the wiki. Please note that once that bootloader upgrade is done you can switch back to using Copter-4.0.3.

So to explain a little more deeply, the issue you’re likely facing is with a “floating” pin connected to the FRAM chip while the bootloader is running. The updated bootloader fixes this problem. The bootloader is a separate firmware that we bundle up with the main ArduPilot flightcode firmware but it’s not installed unless the user actively asks for it to be installed (see wiki linked above). So you can temporarily upgrade to the development firmware, trigger the bootloader upgrade, then re-install the stable firmware and it should all be fine.

Copter-4.0.4-rc1 also includes the new bootloader and will be released for beta testing later this week.

1 Like
30

That is good to know, that i can switch back after the Boot loader Update! Because we had problems with the RM3100 in the dev Version.

31

OK, great! I upgraded the boot loader and the firmware to version 4.0.4. All seems to be fine now. I have modified the parameters and so far no reset.
So what you were saying if I go back to a stable version of the firmware I will not lose my parameters?

32

@Michael_Kaplan,

Yes, you should be able to go back to stable Copter-4.0.3 and you won’t lose any parameters.

33

Thank you sir I appreciate your assistance and I am looking forward to many enjoyable flights.

image

34

Does this bootloader update also apply to the Black Cube?

35

@DroneWrangler, yes, the bootloader issue affected many boards including the CubeBlack and the original Pixhawk. We are still not sure why the CubeOrange was affected more than the CubeBlack but it is likely because of some small hardware difference.

36

@rmackay9 We had the problem, that after we downgraded back to 4.03, the reset does happen again.

37

I have a similar problem. It is concerning single parameters and happend with an Pixhawk as well as with my mRo x2.1 777.

I wonder whether that is kind of dangerous?

38

I have updated the bootloader but the problem persits. Its always the parameter BRD_PWM_COUNT which is set from 3 to 2 every boot.

39

Same problem with cube black in Kore board fw 3.6.12.

40

Had same problem today on cube black on kore board. Latest stable 4.0.3 and bootloader updated to latest on MP. Did control all params but for sure all SrX params to zero and rangefinder to zero too.

41

Hi, I have a hexacopter with cube black and kore carrier. the arducopter version is 4.0.4 and I lost the parameters twice already, there is anything I can do to fix it?

thanks,
Omri

42

Still happening to me too after updating to latest firmware and updating to latest bootloader. Unacceptable. I guess my only option is to ditch the OrangeCube altogether.

43

I Had the same problem in a lot of Cube Orange using with 4.0.5 fw. I upgraded the bootloader, now i will make some tests.

44

There is some work on this going on but there is no date for a release yet.

45

We had an orange do the same today. I pulled it and put in a black. Thanks to all who are working on it and good luck. Let us know when it’s fixed :slight_smile:

46

It should be fixed on arducopter 4.0.7-rc1 released over a week ago.

47

it appears my cube orange is permenantly bricked.

Months ago when I changed to Cube orange (black was apparently being discontinued) I had a cube that showed up and from the moment I plugged it in it refused to output a signal to the rear two motors (quad)

I elected it was a dud and changed for a second cube orange I had. This worked without issues. It flew loads of missions until the other day when it decided to just sit beeping in the field.

I found this thread and figured it had lost its settings. I pulled the cube and went back to black.

Now I figured I better see if I can get the orange working as it seems the devs are close to a cure.

However now the second orange does exactly as the first did out of the box. The rear two motors act like they dont have any esc signal. They just sit beeping.

I have redone boot loader, tried to calibrate esc 6 ways to sunday, and loaded different FW etc.

No luck.

Any chance that the issue in this thread is to blame for two cubes being unusable now?.

Any thoughts as to what else I should try? I do have another brand new orange here which I don’t feel like bricking if I can help it!!!

Thanks all.

48

Try switcing firmware vehicle type from copter ->plane -> copter or vice versa. That will clear any flash issues if that is what this is.