[trike_flyer]

Hello

My cc3d mini has started acting bad.  When I power it up it has trouble doing a boot up.  After plugging into librepilot it tells me it booted into a failsafe mode. in doing so it looses all my settings and is unflyable.  Is there a problem with some of the boards loosing info and becoming bad?  I have tried a rescue and upgrade to no luck.  Do i need to leave it plugged in for a while to recharge something on the board?

Thanks for any help in this.

TF

[TheOtherCliff]

Save settings if you can, not the default ones, but the real ones.

Maybe try with battery in addition to USB.  Maybe try with ports disconnected.  Maybe look for crushed pins inside mainport and flexiport.

It's possible that you enabled some options that caused this, for instance, CC3D is low on memory.  Enabling many features could cause this.

Finally do Rescue (or just boot to default settings after normal boot failure) then Erase Settings and start over.  Save settings as you go, before enabling a lot of stuff (e.g. telemetry and GPS for OSD).

[trike_flyer]

Thanks Cliff for the reply.  I tried using a battery to boot then plugging in the usb.  Seems like the com is stuttering when I plug it in.  Like windows does three resets on it before it is happy.  Is there an onboard battery that has to charge and looses its charge when it is down to long?  I tried a rescue and update firmware and thought it was good but it did it again. I think one of the chips went flakey on it.

TF

[TheOtherCliff]

No battery or such.  Either it's broken or you have enabled too many high memory things.

If you suspect you know what setting you changed that broke it, you can just (all without rebooting) change that setting, then change it back to default, then reboot because it will save changes even when booted from default state.

Else: Not rescue and update, you must "erase settings" and start over.  Erasing settings should get it where it boots correctly (with minimum changes, just to know that it is actually using your config and not default).  Verify that it saves some minimum small change (like a PID change of 1 unit) through reboots.

[trike_flyer]

The only change I did was change telemetry to MSP for the osd to talk to it. I will try another rescue and see if that fixes it or a total boot loader reflash and start again.  Will let you know how it goes.

TF

[TheOtherCliff]

Telemetry MSP uses a lot of memory.  That would probably do it.  As previously discussed, you can save yourself some work by booting into default and setting telemetry (say first to MSP, then) back to none, then rebooting to see if that fixes it.

[trike_flyer]

I finally got back to working on it after all this time.  It is the MSP shooting the memory over the top causing the issue.  I had it back running and when I turned on MSP for the tel it crashed. I can get it to that point without the gps but I would like to have a way of finding it if I crash. So how do you get the cc3d to use tel and gps at the same time if it sends it over the memory top? Or is it just too much for its memory and I have to take a one or other deal. Could it be the board was built with to small a memory being not an original.

JB

[TheOtherCliff]

It is very likely that you have a perfectly working CC3D with the correct amount of memory on board.

Although it is possible that some other ("next") version (compared to 16.09) will allow you to use both, the answer for CC3D is to use an OSD firmware that uses a protocol that doesn't use so much memory.  That is MinOpOsd firmware which uses the default UAVO protocol.

Other than that, in the future, buy boards that have a bigger processor, not an F1 processor.

[trike_flyer]

Cliff thanks for the trick of setting the port back to the standard then rebooting it. Saved me a lot of time trying to get it running again. The reason I went with the mw route was because arducam would not update the osd board. Arduino ide wrote to it without any fuss and gave me a working osd. It seems that by using ide I was able to get a bootloader on the board and now I can use arducam to do updates to it. It seems to be working good now. I even took it out for a flight and had no problems. The two boards are talking and I got the gps stats all showing. I will have to remember this trick the next time I get an osd that will not update.

TF