- Joined
- Oct 20, 2016
- Messages
- 7
- Reaction score
- 2
Hi guys,
I got in a pretty bad crash, which resulted in the main board dislodging from the chassis of the solo. It also knocked the HDMI port on the gimbal off, but I got that 'fixed' at work.
I stripped Solo down all of the way to check everything and it all looked fine for the most part except for the main board being slightly bent towards the rear. After inspection I re-assembled everything, checking all contacts and wires carefully.
Items I noted during re-assembly:
Here's what I've go going on now:
With the gimbal in place I insert a battery then turn on the Solo. I then turn on the controller then I wait. After a few minutes of "Waiting for Solo" on the controller it finally comes up and says "Waiting for GPS" and "Gimbal Not Connected" or whatever.
Sometimes the controller will connect then go back to "Waiting for Solo" intermittently every few minutes.
IF and when it gets GPS and is "ready to fly" it acts normally, sort of, except that it still does not see the gimbal. I tried testing it out and was able to start the motors and "take off" - this was done with no props on.
I got brave and decided to do another test, this time with the props on. I was able to manually fly the Solo. I took off and hovered around at about 3 meters off the ground and everything seemed fine, then all of the sudden it started gaining altitude on its own. Finally Solo lost connection completely but somehow I got lucky and it decided to land itself. This was a little scary. If I do this sort of test again the Solo will be tethered with 55 cord.
Current Status:
This is what I'm wondering:
I got in a pretty bad crash, which resulted in the main board dislodging from the chassis of the solo. It also knocked the HDMI port on the gimbal off, but I got that 'fixed' at work.
I stripped Solo down all of the way to check everything and it all looked fine for the most part except for the main board being slightly bent towards the rear. After inspection I re-assembled everything, checking all contacts and wires carefully.
Items I noted during re-assembly:
- Solo Link Board (PN #PH11A) was partially unplugged
- Main Board was slightly bent down toward the rear
- All wires appeared normal
Here's what I've go going on now:
With the gimbal in place I insert a battery then turn on the Solo. I then turn on the controller then I wait. After a few minutes of "Waiting for Solo" on the controller it finally comes up and says "Waiting for GPS" and "Gimbal Not Connected" or whatever.
Sometimes the controller will connect then go back to "Waiting for Solo" intermittently every few minutes.
IF and when it gets GPS and is "ready to fly" it acts normally, sort of, except that it still does not see the gimbal. I tried testing it out and was able to start the motors and "take off" - this was done with no props on.
I got brave and decided to do another test, this time with the props on. I was able to manually fly the Solo. I took off and hovered around at about 3 meters off the ground and everything seemed fine, then all of the sudden it started gaining altitude on its own. Finally Solo lost connection completely but somehow I got lucky and it decided to land itself. This was a little scary. If I do this sort of test again the Solo will be tethered with 55 cord.
Current Status:
- Does not detect or provide power to gimbal
- GPS acquisition seems about normal
- Connection between controller and Solo is shaky at best
- Motors all work properly
- I think I'll need a new gimbal at the very least.
This is what I'm wondering:
- Is there any possibility of my Solo working properly again or is this flaky behavior a symptom of its demise?
- Is there a way to do some kind of hard reboot?
- Is there a way to re-calibrate everything?
- Is there a way to run diagnostics on the main board?
- Should I strip it back apart and try to restore it somehow?
- Should I try to buy a new main board (or a whole new Solo)?
- Should I just sell the Solo and accessories on Ebay and start over with another system?