Friday 9-6-19 I got bit buy the compliancy bug and watched the camera the entire time I was flying a rolling shot. Long story short by the time I looked up the drone was about 3 foot from a tree and when I hit the opposite direction on the stick it had an unusual amount of lag before it responded to the command. This took the drone right into the tree branch, shut the motors down, and drone force one went nose first down 30 foot onto concrete.
A decent amount of physical damage is on the nose along with a depressed vision housing and a cracked glass on the left vision sensor. Believe it or not the vision sensors still work after recalibrating them. What I'm left with is a "Gimbal cannot receive MC data" error.
What does work
1. Drone powers up.
2. Gimbal does the initializing dance.
3. Gimbal moves when tilting drone.
4. Drone GPS, IMU, work and have been calibrated.
5. Vision system still works after a calibration via assistant.
6. Drone will take off, hover in place, and fly as normal.
7. Drone lands without issue.
What DOESNT work
1. No video feed to phone connected via go app.
2. No control of gimbal via RC.
3. When trying to calibrate gimbal, nothing happens, I.E. doesn't even acknowledge the command.
4. Trying to reset gimbal settings via RC gives "Timeout error"
5. Refreshing software fails on the third iteration.
6. Attempting to downgrade software fails on third iteration.
7. Compass receives interference in unusual places and wont complete a calibration. However when placed in open field, has no interference. May be an intermitting issue or just me never noticing it before?
Findings of the autopsy
1. Removed top shell and observed any damaged wires or loose connections; None found.
2. Removed gimbal, replaced, and terminated all connections from the gimbal ribbon and sensor ribbons.
3. Verified connections of gimbal cables to underbody terminations on main PCB
4. Removed gimbal again this time dismantling it and confirming all terminations made from the ribbon and silver cable.
5. Pulled out more hair and cried for another hour.
6.The large side ribbon cable that runs from the gimbal PCB to the main underbody motherboard has a bad connection. New cables ordered for replacement.
Turned out being this connection I thought was good was a bad cable. Got drone back unrepaired, swapped cable, drone works flawless.
Summary
Everything works with the exception of the above mentioned gimbal MC data failure. Ordered new silver cable and ribbon cable for the gimbal. Also ordered the main gimbal ribbon cables that route to the mother board. IF these don't solve the problem then I'm stuck with returning the drone. If you have any suggestions I'm all ears. I had vacation set for this coming weekend to get some great aerials of Hilton Head Island.
A decent amount of physical damage is on the nose along with a depressed vision housing and a cracked glass on the left vision sensor. Believe it or not the vision sensors still work after recalibrating them. What I'm left with is a "Gimbal cannot receive MC data" error.
What does work
1. Drone powers up.
2. Gimbal does the initializing dance.
3. Gimbal moves when tilting drone.
4. Drone GPS, IMU, work and have been calibrated.
5. Vision system still works after a calibration via assistant.
6. Drone will take off, hover in place, and fly as normal.
7. Drone lands without issue.
What DOESNT work
1. No video feed to phone connected via go app.
2. No control of gimbal via RC.
3. When trying to calibrate gimbal, nothing happens, I.E. doesn't even acknowledge the command.
4. Trying to reset gimbal settings via RC gives "Timeout error"
5. Refreshing software fails on the third iteration.
6. Attempting to downgrade software fails on third iteration.
7. Compass receives interference in unusual places and wont complete a calibration. However when placed in open field, has no interference. May be an intermitting issue or just me never noticing it before?
Findings of the autopsy
1. Removed top shell and observed any damaged wires or loose connections; None found.
2. Removed gimbal, replaced, and terminated all connections from the gimbal ribbon and sensor ribbons.
3. Verified connections of gimbal cables to underbody terminations on main PCB
4. Removed gimbal again this time dismantling it and confirming all terminations made from the ribbon and silver cable.
5. Pulled out more hair and cried for another hour.
6.The large side ribbon cable that runs from the gimbal PCB to the main underbody motherboard has a bad connection. New cables ordered for replacement.
Turned out being this connection I thought was good was a bad cable. Got drone back unrepaired, swapped cable, drone works flawless.
Summary
Everything works with the exception of the above mentioned gimbal MC data failure. Ordered new silver cable and ribbon cable for the gimbal. Also ordered the main gimbal ribbon cables that route to the mother board. IF these don't solve the problem then I'm stuck with returning the drone. If you have any suggestions I'm all ears. I had vacation set for this coming weekend to get some great aerials of Hilton Head Island.
Last edited: