Back to your original post and the off base comment above, it seems like you owe DJI something ... not the other way around. Waiting until you gain a little knowledge before dragging someone or some company through the mud is always the smarter move.
DJI Not Honouring Warranty - Claims it was user error
- Thread starter parrajara
- Start date
Back to your original post and the off base comment above, it seems like you owe DJI something ... not the other way around. Waiting until you gain a little knowledge before dragging someone or some company through the mud is always the smarter move.
I found that being patient and courteous with DJI was the best strategy and yielded the best result !
I recently (week ago) experienced a strange situation with my mini. I use Dronelink to create and fly missions and also on the missions. One afternoon I flew one long mission, changed batteries and attempted to fly an orbit mission, something I have done many times, As I was setting the POI and the outside ring of the orbit I received a msg. that contact with the A/C had been lost. The A/C was only about 100 feet away and at a height of 70 feet. I then got a fast beeping (the sound you get when you have no battery left and the drone automatically lands) the drone stopped where it was and started descending, right near some people in outside dining. I was in an industrial park with all kinds of open space except that one restaurant. The battery was at 92% so that was not the cause. Any time I have lost connection with the drone it just hovered in place, not this time though. I had a small amount of control of the drone, enough to save it from crashing, but barely. It was zig zagging back and forth and I had to maintain a constant up stick just to keep it in the air long enough for it to make the measly 100 foot back to me. Even then it almost got run over by a car. I sent the flight record to DJI which clearly shows the program initiated an "Automatic Landing" with 92% battery. In my case they are not saying pilot error. They want me to send the drone in so they can look at it, they seem to think that loosing connection with the drone initiated the automatic landing but that should not happen. I don't know what to do, I don't want to use my Care refresh policy on something that rarely happens and I don't want to lose the drone for who knows how long.
If you can post your flight data here, someone might be able to interpret it and give you some ideas about the incident.
Attached is my DJI flight record but DJI has already seen it and can't explain what should not have happened. They want to take my drone and experiment with it. I don't really want to give it up. I was just explaining to Parrajara that strange things do happen.
That flight data doesn't match the incident you described.
It's for a flight where you brought the drone back at 44% battery and landed right at the home point without any complications.
Tufargon
Well-Known Member
I didn't read the whole thread but I just got an email from DJI to renew my Care Fresh and it states this.
Dear customer,
Your DJI Care Refresh will expire in 7 days.
But now with DJI Care Refresh + you can extend your Care Refresh and
receive one more opportunity to replace your damaged DJI product as well
as extending your product’s warranty by 12 months.
Replacement or repair services will be provided for product damage caused
by a user error, accident, water damage or manufacturing defect.
So even user error should be included If you have Care Fresh.
Dear customer,
Your DJI Care Refresh will expire in 7 days.
But now with DJI Care Refresh + you can extend your Care Refresh and
receive one more opportunity to replace your damaged DJI product as well
as extending your product’s warranty by 12 months.
Replacement or repair services will be provided for product damage caused
by a user error, accident, water damage or manufacturing defect.
So even user error should be included If you have Care Fresh.
Parrajara was the original person who smashed his drone flying it the city and DJI said they would not replace the drone because of user error. He claimed the drone started up by itself. I was just responding to him saying that the program may some bugs because my drone landed by itself. If you look at my flight record posted you can see the zig zagging caused by trying to keep an upward thrust and return back home. I have a 2 year old contract but I think they changed it, I actually called them and spoke to 2 people at 2 different times. One said they will cover everything even losing it in the water or a fly away, but the other said they would not cover user error or loss. They gave me a new one when I kept getting error msg., "Gimbal overheating, land immediately".
Tufargon
Well-Known Member
There was no disconnection and you have full data for every 1/10th of a second of the flight.
Your Failsafe Action was set to the default of RTH.
The data shows no warnings or messages at 1:50.2 when the autodescent commenced.
It appears that you accidentally pressed the autoland button
Then you fought against the autolanding, rather than cancelling and resuming control.
I can't see any evidence in the data of of a problem with the flight.
The msg. that I lost contact with the drone (not 100% sure what the actual msg. was) did not occur, I believe, in that flight. I will look at previous flights. I might have returned it to home and shut the drone off and then on and then tried to perform an Orbit. I use the RTH button all the time, just today I used it on 3 flights, after a mission is complete my drone goes into RTH mode and I stop it every time so that it does not land in tall grass and I hand catch it. Besides if I did hit the RTH by accident, and I know I did not, home was set at 140 feet right next to me. So the drone should have gone up to 140 feet and came back to me. RTH would not be of any use if it just landed wherever you hit the button. I fly in a relatively dense area of cell phone towers, radio signals etc. I lose contact with the drone frequently just 800 feet away, not 50 feet away like I did that day, and RTH is eventually initiated and the drone goes to 140 feet, if lower than that, and flys back to me, it does not just land there. Even DJI wants to take a look at the drone and the controller.
Well ... the data at least clearly state the reason for the autolanding starting 110sec into the flight ... circled in red in below chart.
(Click on the chart & picture below to make them larger)
And here the DJI Fly Safe material that are in your Mini ... the red cross marks where you were.
Oh and I just reviewed the flight record again, "A" says home distance was 0 feet implying I was at home, the drone was not. I took of to the right where it shows a battery at 97%. Where I actually landed it was at letter "D" and it says home distance was 66 feet, it was not, it was more like a car length and a half. The notifications section refers to a position "C" but it does not show that on the map. I fly in an airport zone everyday, and every time I land and take off I have to check off on all the agreements. That airport is over 4 miles away, I am not landing in the airport. I think I might even be closer to the flight paths when I fly at my house. I don't see how that has anything to do with drone just dropping out of the sky for no reason.
Last edited:
The reason, per the log (which doesn't lie - and slup doesn't either):
Seems to me you have two choices - you can accept the log, and the expert analysis of it, or keep on with your own interpretation
The Airdata interpretation of the log is wrong ... the log clearly show the recorded HP where you say it was.
The green star in the sat pic is where the HP was ...
... it was recorded 5,5sec into the flight with 16 satellites locked & with an GPS level of 5.
The log clearly state the reason for the autolanding ... right or wrong, it was due to:
And the only thing that can physically forceland your drone besides you is the DJI Fy Safe material uploaded in your drone ... and that tells us that you were in an authorization zone type Airport ... the only question mark here is why it let you fly for 110sec before it took your Mini down (most probably due to that you didn't unlock it as explained below)
That's correct ...
No-one made any mention of accidentally initiating RTH, because RTH was never initiated during the flight.
Slup has dug deeper and found what initiated autolanding in post #36 above.
You never lost contact at all during the flight.
And you never tried to cancel the autolanding and resume control.
Instead you left the drone autolanding and fought against it.
Whoever you talked to at DJI doesn't have the facts.
There's nothing at all wrong with your drone or the controller.
Go and do a simple test flight somewhere else and that will comfirm this.
I flew this mission same day 10 minutes or so before the near fatal landing. The link is in the beginning of this post, it was the one that I wrongly sent.
I am not disputing the AC went into auto land I am saying I did not cause it. To say it happened because of being in an airport area I dispute because of the flight before and I have flown 100s if not 1000s in the same area.
If it wasn't due to an airport issue, then go back to my suggestion that you accidentally initiated Autolanding.
Either way, the outcome doesn't change.
You could have cancelled the autolanding, but didn't
Similar threads
