jayh410
lvl.4
Flight distance : 11266 ft
United States
Offline
|
if you're of a certain age you'll get the reference....
So, Sunday I was working through the modes, starting with Gesture, which worked pretty neat. Got some nice pictures and it works as advertised. I'm sure I looked pretty silly walking around with my pet drone following me at about 20 feet, occasionally flashing the two-handed "box" gesture. But like I said, it worked exactly as expected.
Next up, I tried TapToFly mode and I tapped to fly in a general direction, which unfortunately led it directly through a tree. It was pretty obvious where it was going so I tried gaining altitude to go over the tree but the mavic seemed determined to hit it. Since the tree didn't have any leaves I feared it wouldn't trigger obstacle avoidance so all I could do was watch it get tangled in the branches, hanging up about 30 feet above the ground. Of course as the propellers thrashed the controller was telling me about neat things about how I'm probably frying one of my engines, etc. Eventually it exited weed wacker mode and just hung out, red light flashing forlornly.
Fortunately home doubles as a tree farm so there was no shortage of tools or ladders. The only way I could get close to the drone was with a 16 foot step ladder with a 12 foot pole pruner, of the manual, not chain saw type. I was able to bounce the branches below into the branch it was stuck on but I still couldn't get it free. So disregarding the safety recommendations on the ladder I got a little higher and it fell out of the tree. Miraculously I was able to grab it on the way down without falling off the ladder.
I had to replace all four blades, and now I've got a couple more spares on order. I took it up for a quick flight to see what kind of damage was inflicted. It seemed to fly well and sounded more or less normal. Are there any diagnostics I can run to make sure all the motors are functioning normally? Anything to listen or watch for if the bearings in the motor were compromised? The preflight checklist is a place to start but a little more detail would be nice.
So, the core of the issues was user error, but the obstacle avoidance doesn't seem to identify bare branches as an obstacle. What are the parameters for the obstacle avoidance? Is there a minimum object density that it avoids? For instance, had the tree been fully foilaged would the obstacle avoidance have kicked in? How solid does an object need to be for obstacle avoidance to function. In the tapfly tutorial video it actually shows obstacle avoidance working, avoiding a branch with leaves on it. I'm sure it's all tied into algorithms which are tied into input from the sensor unit. Eventually the algorithms will be updated and refined to keep us idiots out of the trees. What's the functional distance for the front sensor?
So, what's a proven technique everyone uses to avoid catastrophe when you see it coming? Hit RTH? Is there an "Omigod, we're all gonna die mode" which would cause the craft to dump momentum and hover immediately? Between glare and inexperience I didn't see a panic button of any type which I could have hit to avoid the tree. Flight logs are uploaded if DJI wants to check things out.
|
|