Because its unreliable.Yes, why in the world would you turn off the coolest thing about it?! the sensors?!
UPDATE:
[msinger] rocks!
Thats what i would do, yes...interesting, so the take home message for now i think is
if you are flying close, have sensors on
if your are far off, potentially having a RTH triggered, then turn them off. right?
It would be cool to see the video of the crash, were you recording? I like the feature on Litchi that enables recording at takeoff. I don't see any reason to not record the entire flight given the size of SD cards these days.
Of course sharing the video is exactly what some people here would prefer not to happen, but my curiosity far outweighs my concern about their opinions
Having the obstacle avoidance sensors on limits the speed of the craft to 22 MPH. Normally this is about as fast as you'd need to go under most conditions. Having them turned off allows you to open up to the maximum non-sport mode of 35 MPH. If you're at altitude with nothing in the way or over flat expanses of land and want to get somewhere quickly you might consider turning them off.Yes, why in the world would you turn off the coolest thing about it?! the sensors?!
The OA avoidance sensors have never triggered any false positives on my Phantom 4 that I can remember. As I stated in another post I usually fly with them disabled most of the time. Having them enabled has not prevented a crash or saved my a$$ when I've been actively piloting the craft, because there hasn't been a need for it to engage. However it has saved me on at least two occasions that I know of. Once, on a smart return to home when I lost connection it flew towards a stand of trees and braked JUST in time to avoid them and flew over them. I was exploring an inter-tidal lowland valley flanked by wooded areas of trees on the coast of New Hampshire. I was skimming just above the surface of the brackish water / vegetation when I lost signal of it. I did not know it did that until later that day when I reviewed the video. Another when I was playing with the active track feature (which I haven't used much) after first getting the P4. I was on a bike and it maneuvered quite evasively and aggressively to avoid plowing into a mailbox. The street that I was on had a slight uphill rise to it. Those two instances made the OA feature worth it, in my mind, over the Phantom 3 Professional that I had just upgraded from. In my experiences having OA turned on during the autonomous flight profiles has made it worth the price of admission. I have not tried to fly it into a wall as others on youtube have but it has kicked in a few times when I've brought it towards me during landing and it sensed me standing there. In one circumstance I was standing on the balcony of a rental cabin high up overlooking the side of a mountain in Tennessee. It was beeping incessantly because I needed to bring it close to the balcony (and side of the building) to land it. I ended up turning it around and reversing it towards me before setting it down on the wide wood planked patio handrail.Because its unreliable.
It has been fooled many times by just lighting and making the aircraft refuse to fly forwards.
It needs refinement (like nearly everything DJI release in the early life cycle of a product)
A few more updates and I'm sure it will perform as it was intended.
For now, it is an (unreliable) gimmick
For me: If I am flying close to obstacles low to the ground or around buildings turn the sensors ON. Far away around tall obstacles with the potential to lose contact and have a failsafe return to home triggered turn them ON. Set your RTH altitude higher than the highest obstacle you will encounter. Wide open area with trees / power lines no higher than 80-90 feet and I'm at 300 feet I turn them OFF, only because I can attain the higher speed with them off. If you're a beginner leave them ON all the time until you're familiar / more confident / more experienced with your craft.interesting, so the take home message for now i think is
if you are flying close, have sensors on
if your are far off, potentially having a RTH triggered, then turn them off. right?
Some of the bashing doled out by a minority of the members have been irksome to a small degree. Mainly because it contributes no valuable content and is unhelpful to an after-the-fact incident and their negativity may sadly discourage other members from contributing their stories. That fact was on my mind as stated in my initial post and sure enough it happened. There are ALWAYS a few simple minded people like that in every forum. Always. I'm ok with that because they don't know who I am as a person and I won't lose any sleep with their utterances. As you said, reading about lessons learned in crashes is valuable benefit to the community. Informing other readers of what went wrong can help prevent them from making the same mistakes. If I can spare one pilot from the heartbreak and agony of losing their awesome aircraft along with preventing disasters on the ground I can be satisfied with that.+1 to that.
And thanks for sharing all this with us, Reaper. Reading about lessons learned from crashes is, in my opinion, one of the best and most useful parts of a forum like this. And as far as the public beat downs that some like to dish out go, I doubt they're likely to change anyone's flying behavior, but they may very well succeed in discouraging honest and open discussions about it.
Here's a few scenic shots I've gotten in the countryside:Here's my future forecast for this awesome piece of technology: Someone flies through downtown-anywhere into a high rise, it falls hundreds of feet and hurts or kills someone. Then we get to only fly in the rural countryside or RC flying parks. Not very photographic.
I was recording. And I think it would be cool to see video of the crash as well. After all, I paid for it! Three flights made so far at the average cost of $433 per flight. I was curious too and wanted to see the moment of impact and subsequent fall. That's the part I fast forwarded to upon retrieving the drone and memory card. I watched from the moment I lost control of the Mavic. It hovered for a few seconds, then automatically swung around in the direction of the home point. Ascended the short distance to 90 meters. Then went into forward flight. Closer and closer towards the looming building. It's not gunning it but here it comes..... closer, closer. Nail biting now. Then nothing. The video stops about 3 seconds from impact. Strange, I wondered. But then I realized that maybe it's the way it buffers before saving to the memory card. And at some point during the fall or crash to the surface the battery was forcefully ejected so perhaps it didn't get a chance to write that part to the card. So unfortunately I do not have that moment in video to save for all posterity.Great story about the retrieval! Glad you got it back.
It would be cool to see the video of the crash, were you recording? I like the feature on Litchi that enables recording at takeoff. I don't see any reason to not record the entire flight given the size of SD cards these days.
Of course sharing the video is exactly what some people here would prefer not to happen, but my curiosity far outweighs my concern about their opinions
UPDATE:
I have recovered my drone. With the help of member msinger AKA MavicHelp who was able to analyze my flight log and point me in the direction where the bird went down I was able to return to the scene and speak with the building management about the incident. I was honest about my mistake and described what happened. I was fully expecting them to be angry but surprisingly they were not. They were very understanding and cooperative. The security agent went onto the roof of the west wing (the building has the high rise tower in the middle with two four story wings on both sides) and there it was, right in the area msinger indicated it would be. Next to the air conditioner. Which, by the way was in the area that my friend and I covered in his drone but he did not think to go that far north or get close enough. Upon reviewing his video we did see it, but being so far away did not recognize it for what it was, tiny as the Mavic already is.
On the first search the security found the aircraft body and battery laying a few feet apart but the camera was missing. She went up an hour later on and found the tiny camera under the rooftop air conditioning unit and called me back to let me know she had it. Upon thanking her profusely and offering a reward which she graciously declined I was beyond stoked.
Now onto the good: the Mavic flies! Two props were broken at the tips but after replacing them the Mavic took to the skies without a beat. This thing loves to fly. Full functions, telemetry, altitude, speed, LED beacons, GPS, flight data all works as it should. Full range of movement. Arms are just fine. It folds and unfolds just like it did out of the box. The thing is built well. It did take an impact to the nose towards the starboard obstacle sensor and has a nasty scratch there. The top front cover is cracked near that spot. Starboard side front arm has a slight scuff near the red navigation light. Starboard rear arm has some very very slight scuffing to the bottom of it. Other than that, the rest of the body is absolutely flawless. Port side arms unaffected, heat sink on the bottom is mint. Maybe with the ability of the arms to fold allows it that much more "give" in a collision which could mean the difference broken an intact arm or a broken one.
The bad: Battery is destroyed. Like totally wasted. It looks like a twisted lump of plastic. It took a huge beating in the crash and got ejected. I can't imagine the foot pounds of energy that rippled through it during the sudden deceleration. The camera / gimbal mount has been detached from the aircraft body. The assembly looks like it might be fine, but the ribbon / connector has been torn. See the attached pictures.
Here's what happened: My Mavic lost RC connection as it flew around the building in question. It went into failsafe RTH. Without any way of getting input from me it initiated RTH and swung itself around and climbed from 252 feet to 90 meters (295 feet) which was the predetermined RTH altitude. As forward vision sensors were turned OFF at the time it did not engage them on the RTH. It dutifully made a beeline back to the home point before flying smack dab into the northwest/west side of the building. It fell about 250 feet to the rooftop of the west wing below. Member msinger went through my flight data and informed me of this and the recovered video from the drone collaborates with his information. He showed me a detailed satellite picture and highlighted the area where it went down. Thanks msinger! If you guys ever need help with located a downed drone please make him your go-to guy! He rocks!
I am going to work with DJI on repairing my drone as it appear that it does not have user serviceable parts at this time. I will keep you updated with the repair progress. Thank you to the members who offered support and especially to the one who offered me detailed help. It made a difference in being able to recover my Mavic and begin the repair process. Both of the Mavic and of my humility and bruised ego. I will most definitely fly smarter from now on.
RTH active with the appropriate height setting that is.Glad to hear you recovered it. Best to have RTH active if you're ever in an area that has tall buildings/objects...
RTH active with the appropriate height setting that is.
We use essential cookies to make this site work, and optional cookies to enhance your experience.