DJI evades responsbility of cost of repair after its faulty firmware/flight controller directly caused high-speed out-of-control crash of drone flying it 56+ mph into a tree during a forced autolanding mode!
On August 29th of 2020 I flew my DJI Mavic 2 Pro on a bright sunny day, little to no winds, perfect conditions. Soon after takeoff I noticed that DJI Mavic drone started acting erratically, I have previously flow hundreds of flights before and had never had any issues. A few days prior to this the DJI app had forced me to do a new firmware update before allowing me to fly. This was around mid August. On this particular morning (Aug 29th) a few moments after noticing the aircraft behaving erratically it somehow entered into a forced autoland mode by itself, even though I was not inside of any NoFlyZone nor had I breached any altitude restrictions... I had flow at this same location dozens of times before in the past months and exactly the same route and never had any issues.
Soon after I noticed the Mavic going into a force autoland it did something else totally unexpected... I saw the propellers clearly in the liveview screen on my phone (DJI Go app) and knew right then and there something was very wrong, the Mavic had pitched itself at an ungodly angle (more than 45 degrees it seemed) and the props were in full view of the screen, and as I watched it in the sky, I saw it zooming by at extremely high speeds flying past me at what seemed to be almost 60 mph and then away from me uncontrolled and uncontrollable... any and all of my attempts to stop the undesired movement was blocked/unsuccessful and in mere seconds it crashed into a tree at very high speed before crashing into the ground and breaking to pieces having inflicted severe damage.
Subsequently I contacted DJI support and detailed these events and provided DJI with both the flight record and the raw flight data logs as captured by the DJI drone itself.
Sometime later DJI told me to send the drone back to them for analysis and repair...
However after had sent it, some days go by and when I finally hear from DJI, they stated that because I did not buy their DJI Care insurance they are refusing to even analyze the data and refuse to determine what happened to the aircraft, and subsequently their logic is that because they have no analysis to prove they were at fault (due to them refusing to analyze the data in the first place!) they are now holding my drone hostage until I pay their ransom money so they can then "repair" their own flawed drone just to send it back to me!
Subsequently I analysed the data myself using available data analysis tools and determined and proved beyond any reasonable doubt that this that in this case it is the 100% fault of the DJI, to wit: it is the total fault of the DJI Mavic's firmware bug which caused an out of control event that forced the drone to fly erratically against user control and beyond normal flight permitted characteristics, ultimately resulting in a hard crash causing significant damage to the drone itself.
The logs show that subsequent to the Mavic's imuYaw re-initialization a critical firmware bug caused both IMU's fail simultaneously and locked one motor keeping it's revs constant way above the rest for no explainable nor logical reason as a result caused the Mavic to fly out of control at excessive speeds of 55+ mph whilst in forced autoland mode (thus refusing any inputs from the user/pilot) and directly causing and directly resulting in a very damaging uncontrollable crash at high speed into a tree.
The root cause of this incident was on a level above the IMU, as the evidence shows, this was can only be explained by a defect in the firmware and/or in the flight controller itself, in both/all instances, this definitely falls on DJI to repair or replace at DJI's cost!
After having replied back and sent DJI all the evidence and analysis based on that evidence, DJI has so far refused to accept responsibility, and refused to repair or replace at their option and cost, and is still holding my $1600+ USD drone hostage until I pay them the ransom money!
I've been flying dji drones since the first mavic first came out back in late 2016. Since that time i've bought a spark, mini and also have the mavic 2 pro as well. Dji has pretty much dominated the consumer drone market for a couple years now, especially after the battle with gopro went decidedly in favor of dji.
Most people considered the mavic 1.0 state of the art at the time, and the mavic 2.0 an iteration on top of that. Before the skydio 2 came out, the dji activetrack 2.0 was pretty much considered the best there was on the market.
2019 hadn't been a good year for dji. I felt that they really didn't come out with anything new or mind-blowing and in fact the mini was a step backwards. Sure the mini lets them market the mass lower market, but it demonstrated no progress in terms of technological advancement. The innovation train at dji seemed to have stopped or at least paused for a year.
While the skydio 2 as of yet is not really an all-around well rounded replacement of the mavic 2, it does have the competitive advantage in terms of true autonomy and ai tracking that puts dji's current lineup to shame.
I personally don't have a skydio yet but i've been watching a lot of youtube videos showcasing the competitive advantage of the skydio especially as compared to dji active track. Having had mavic for a while, i've never really tried its activetrack 2.0 features, but having some time on my hands on the last day of the decade Dec 31 2019) and living near a large high school with empty deserted parking lot i decided to give it a try to have it chase my car while i'm driving super slowly Less than 10 miles per hour).
Long story short, it ended in disaster with my mavic pro crashing and suffering much damage. This was my very first time using active track from dji, and it was also my very first crash out of hundreds of successful flights. The fateful flight in question was done in broad daylight, little to no wind, not in or even anywhere near any nfz zones or areas, and as well i was utilizing the "slow mode" of the activetrack 2.0 in which the drone was using all sensors including the side sensors. I didn't subject it to tricky situations, no skinny tree branches or reflective mirrors or any gimmicks or gotchas. While it was actively tracking me in the slow mode it collided into an obstacle that it could have, and indeed should have been able to see in time to completely avoid.
What made the matter so much worse is the string of issues that lead up to the crash. It wasn't just the fact that in this instance activetrack 2.0 failed me and caused the dji mavic to collide with an object that it should have avoided, it was the fact that this accident was a chain of issues that all lined up and each of the issues themselves was attributed to yet another failure on the part of dji itself.
You see, when i first set out to test activetrack 2.0 on my mavic pro 2 in the empty parking lot i was cognizant of the height issue and wanted to maintain a floor of at least 200 feet agl at all times, this was basically my backyard and my neighborhood and i knew that 200 feet would give me plenty of margin for error even if activetrack failed to see or avoid any taller obstacles.
However even though this was in broad daylight, with almost no winds that day, and i was the only car in the very large empty parking lot, when flying at around 200 feet in the air the mavic would lose activetrack within a few seconds after having acquired a lock and started tracking. In essence, activetrack was essentially nonfunctionality in terms of attempting to track a vehicle In this case my own car going very slowly at less than 10 mph at all times) at a height of just 200 feet.
So i had to lower the height to something much lower to have it actually be able to track my car. This was the first failure of dji activetrack not being reasonably robust enough and having these severe limitations that required the tracking to be commenced in such low altitudes that it put the aircraft in a significantly more dangerous flight envelope and also contributed to the lack of safety margins that ultimately combined with other flaws in the dji design that ultimately lead to fatal crash. )
I lowered it to around 80 feet and it would track my car, but for the life of me i could not get it to stay in "behind" mode, i wanted it to track my car from behind and not from the front or from the side, but every time i started a track from "behind" it would inevitably and invariably move to the side the moment i turned my car in any direction.
There was simply no way i could force the mavic to keep tracking me from the behind, regardless of how slow i was going in my car. This was the second failure on the part of dji activetrack, as had it been able to follow simply instruction of tracking me from behind it could have compensated for the first flaw Requiring very low height in order to keep tracking lock) without putting safety in jeopardy, but since it decided to start moving to the side this put the mavic in a position where potentially it would be more prone to strike objects, given the dual prong facts that the side sensors were less able than the stereo front /back sensors, and also that when tracking a car on the street, usually the behind profile would be safer than the side profile in terms of flying/tracking at lower heights. This was basically an all-around bad combination of events that dji itself caused...
So after having spun a few times around the parking lot, i decided to drive a short block around my immediate neighborhood street. I drove very slowly, slower than 10 miles per hour, and as i turned the corner i could see that since the mavic choose on its own to shift to the right side tracking profile it would come within close range to a taller tower-like structure or obstacle that we were approaching.
Immediately i grabbed hold of the joystick and made inputs for the mavic to increase in height. I was still getting a perfect real-time picture feed and perfect downlink from the mavic cameras to my dji go app on my ipad tablet device connected to the mavic remote controller, and at no point did i have any loss of connection or loss of video feed, however i observed that despite my full deflection on the height input telling the mavic to climb as quickly as it could to get as much altitude as it can, the mavic stayed in its activetrack profile and refused my command inputs to increase in altitude.
Out of all my years of flying the mavic i've never encountered any situation in which it would refuse to listen to my input to command it to increase in altitude. The only other scenario in which this happened was when it was in a nfz with a max altitude/height restriction, but this being in my own backyard i knew for sure 100% that there were no nfz's around nor any altitude restrictions, and in any case, my mavic was only about 100 feet at the time, well under the 400 feet agl as dictated by the faa.
The only thing i can surmise is that the activetrack 2.0 had a glitch or a bug that caused in this instance the mavic to refuse all height input commands. This reminds me of the boeing 737max mcas issue in which the pilots try to save the aircraft but the flawwed ai thinks it is smarter than the pilot and then locks the pilot out, causing a fatal crashes.
Soonafter, before i even had a chance to manually cancel the activetrack and take full manual control, i heard a loud band and a thud noise and i knew the mavic had collided with something while flying in the "slow" Safer) mode of activetrack, in broad daylight, with no wind, nowhere near a nfz zone, and with all sensors including side sensors actively operating. Not only did the mavic refuse my command input to increase height, not only did its obstacle avoidance completely fail to avoid the object, but it hit the object while refusing to allow me to make manual corrections that could have saved the day.
My next course of action after i got home with the damaged drone was to figure out what the heck happened. Part of that was the recovery of the flight logs, but as it turns out, the flight logs were mysteriously missing and apparently deleted by the dji go app itself. It wasn't like i flew a whole bunch of missions after this and the flight logs somehow overwrote itself, the fact of the matter was i didn't fly any missions after the crash and didn't even touch the ipad until it was time for me to attempt to retrieve the logs to figure out what the heck had happened. So the only possible scenario in which the flight recorder logs disappeared was that dji simply didn't log it in the first place, or somehow the dji app locally or dji themselves remotely deleted it somehow after the fact. This was more mysterious given the fact that i had logs from the 24th, and so the other older missions logs were still intact but not the mission that was most critical for analysis!
I also learned that even though the actual raw .Dat logs were on the ipad and could be retrieved that starting with the mavic 2 dji decided to encrypt those logs without giving anyone the key. So the .Dat logs were for all intents and purposes useless to anyone but dji themselves, how transparent of them!
One would think in this day and age in which the us government is deciding whether or not to ban dji Much like how they banned huawei etc) that dji would be more transparent and would choose to not encrypt the logs! for one thing, we all know dji is coming up with app to allow anyone to track dji drones anywhere, and the dji drones is emitting telemetry to the entire world and public at large, so from end user Customer/drone pilot) standpoint dji seems to think that level of sharing privacy is okay but then dji goes behind the backs of its customers and encrypts their own flight log data and doesn't give the key?!
It just seems backwards... Dji actively disregards the privacy of their own customers but then go out of their way to hold their own customers' data hostage from themselves! even critical diagnostic data! this makes no sense whatsoever and doesn't even pass the smell or sniff test.
This is not what a customer service oriented company should treat its paying customers. This is not a good trend for the industry! trade war or no trade war, entity list or no entity list, dji should not be eroding the privacy of their paying customers whilst at the very same time locking their customers down and blocking them from access to their very own data! there is no excuse for this double standard and hypocrisy!
I'm not anti-dji and in fact in the past when i criticized other drones like the uk zano drone i was publicly accused of being an employee of dji :
For the past couple years, i've been a huge supporter of dji and their products, but there comes a point in which one has to admit that dji is starting to fall behind in terms of innovation, and without a credible contender to effectively compete with dji, then i do believe we are already seeing stagnation in the industry and this is to the detriment of the end users and the consumers and the growth and viability of the industry itself long term.
It is not surprising then that skydio 2 has targeted its strengths to be exactly where dji is lacking the most, in terms of true ai autonomy and real active tracking... While the dji mavic 2 is still a very good product overall, and overall well-polished, its biggest lack would definitely be its glaring weakness when it comes to things like autonomy, active track and other forms of ai modes, or lack thereof.
I've flown the mavic for years, hundreds of flights, never a hitch. That is a testament to the quality of the dji mavic product. But the very first time i attempt an active track flight, dji flies the mavic into an object and crashes. Sure this is just one instance and not representative nor statistically significant, but it is significant to me subjectively and it shows me that when it comes to things like activetrack, dji products are not to be trusted and still light-years away from any sort of truly smart autonomy or trustworthy tracking capabilities.
It is my hope that the third version of the mavic Mavic 3.0) will greatly improve in this regard, but as things stand, the mavic 2.0 activetrack 2.0 is in my opinion less than useless and it almost cost me a loss of nearly $1600 usd. This is at best a total loss of confidence in dji's so-called activetrack tech and at worst almost criminal level of false advertising. Since i was using the "slow mode" which was pitched as being full sensor ultra-safe, and this was flown under the most ideal of circumstances, broad daylight, super slow, no wind, fully up to date firmware, etc)
To sum it up, we as consumers should welcome competition in the open market from all players and all angles, if skydio 2 can bring the best out of dji and finally force them to make mavic 3 with actually usable active track and real autonomy then all the better, but if dji fails to improve then i can foresee the day in which a skydio 3 could be a full on replacement for any dji mavic or other dji drones in the future.
Below you will find the email I sent to DJI. Not once, not twice, but three times. No one answered the emails only the twitter posts at @ViewsElevated where they did nothing but send me blanket responses. Oddly I received 2 responses, one where they were insinuating that nothing happened and they didn't know that firmware wrecked Osmo 2 Gimbals from DJI (which is a lie because it's all over the internet and their own forums). The other telling me that I was past 15 days out and because of that they wouldn't do anything. They later told me that I should ship it to a facility for them to determine if it was messed up. THIS is NOT feasible as DJI is known for taking peoples units and shipping back broken, or units missing parts. A youtube search of DJI Sucks will show these videos.
I simply asked their DJI Customer Support on twitter @DJIGlobal @DJIEnterprise @DJISupport to please send me a new unit since mine was only used twice before the firmware crashed it and send me a label to return the other unit. They told me no and gave me the reasons above and told me they absolutely would not help me out. I had an event last night, tonight and tomorrow (all of which I had to forefeit) becausse they would not replace the unit and I wasn't going to go buy another one of theirs.. and the unit I ordered from another company won't be here for 2 more weeks. I did NOT know DJI had a history of treating their customers horribly until I resesarched complaints over the last 2 days.
Again, all I wanted was the unit replaced with the same or upgraded unit for the trouble. They are crooks and by sending out firmware that is bricking and crashing units .. draw your own conclusion. #DJISucks Good afternoon,
I am not sure what is more disappointing, your product or your customer service "team" as you call them. I purchased the highly desired Osmo 2 Mobile from DJI from the Apple online store just a couple of months ago over the Osmo. Your marketing team did a solid job in selling me and many others a very weak piece of equipment. As well, the new firmware is a complete and utter failure, the motors make loud noises, and it's only been used 2 times prior. And then when I installed the new firmware that a lot of people stated bricked their device, I had the same result of the phone going "limp" - you can understand where this would be a problem right? A problem that no technical viagra can fix apparently...
To give a basic run down I installed your latest firmware that is supposed to resolve issues NOT BREAK the device. DJI GOs red banner popped up, we installed it, and it looked fine until we went to calibrate the phone. After calibration it requested a reboot of the Osmo2 and we did that. It restarted, the phone swung around like it normally does then boom LIMP like an 80 year old man in an cooler. I restarted the phone, the osmi, I rebalanced the iPhone X, and - AND it swung around, and LIMP! So, took my small case off my phone and it did the same thing, I tried my Note 8 and nothing. I did on occasion get some motor noises but that was about the extent of it. So, I then looked up on the forums to see if anyone else had these issues. And to my surprise, MANY people had these problems with their units being bricked etc... (Imagine that!) So I figured I would give this customer care a shot, maybe, just maybe it would be as good as 3Dr's when I had their drone and it had issues... Nope, just epic failure written all over it. I first explained to your customer service agent "who spoke very little english" yet was taking calls from the US, that I have an event tomorrow and Friday. He didn't seem to care much and simply followed his script. I explained to this rep all that I had done so that we could skip most of these steps YET he preceeded to ask me the same question 3x in a different form. Not sure why, but he did. After going back and fourth with him on this amazingly well service call (sarcasm) I then just requested to get to a supervisor. We can only imagine how well this went since support reps must learn their lack of ability from the TOP.
So, after 30 minutes of waiting I get this young lady on the phone who (yup) followed pretty much the same script, telling me that this is all they can do and that I would have to send it in for replacement or fix. I told her this was not an option that I needed a working device for my event tomorrow and she pretty much gave me a simulated, digital middle finger through the phone. Hardly appropiate for service staff to be this way but this is how she was. I was fuming at this point because I now have a device that hasn't been used and now doesn't work at all and I am screwed. Maybe I should have purchased the OSMO but then now knowing what kind of service I would receive, maybe not. I now wonder if my P4P+ is going to get the same service level as I received here after 54 minutes of total support time.
I know you all don't care, I can see it on your twitter responses. I dealt with it first hand there and on my phone call. But maybe, just maybe.. someone out there in DJI Land will take a look around and instead of enjoying this market share, you will look after your customers. I come from a service background with the best in the world at delivering service "Disney, Ritz Carlton, Marriott" so maybe I expect to be treated like a client vs a stain on the ground. That did not happen here though and the support level seems to be across the board.. BAD. All I wanted was a workind device, no one that grinded and made motor noises then killed it self once I did a firmware update. Thats all... It's really a shame that did not happen. Thanks for listening,
DJI Reviews
DJI evades responsbility of cost of repair after its faulty firmware/flight controller directly caused high-speed out-of-control crash of drone flying it 56+ mph into a tree during a forced autolanding mode!
On August 29th of 2020 I flew my DJI Mavic 2 Pro on a bright sunny day, little to no winds, perfect conditions. Soon after takeoff I noticed that DJI Mavic drone started acting erratically, I have previously flow hundreds of flights before and had never had any issues. A few days prior to this the DJI app had forced me to do a new firmware update before allowing me to fly. This was around mid August. On this particular morning (Aug 29th) a few moments after noticing the aircraft behaving erratically it somehow entered into a forced autoland mode by itself, even though I was not inside of any NoFlyZone nor had I breached any altitude restrictions... I had flow at this same location dozens of times before in the past months and exactly the same route and never had any issues.
Soon after I noticed the Mavic going into a force autoland it did something else totally unexpected... I saw the propellers clearly in the liveview screen on my phone (DJI Go app) and knew right then and there something was very wrong, the Mavic had pitched itself at an ungodly angle (more than 45 degrees it seemed) and the props were in full view of the screen, and as I watched it in the sky, I saw it zooming by at extremely high speeds flying past me at what seemed to be almost 60 mph and then away from me uncontrolled and uncontrollable... any and all of my attempts to stop the undesired movement was blocked/unsuccessful and in mere seconds it crashed into a tree at very high speed before crashing into the ground and breaking to pieces having inflicted severe damage.
Subsequently I contacted DJI support and detailed these events and provided DJI with both the flight record and the raw flight data logs as captured by the DJI drone itself.
Sometime later DJI told me to send the drone back to them for analysis and repair...
However after had sent it, some days go by and when I finally hear from DJI, they stated that because I did not buy their DJI Care insurance they are refusing to even analyze the data and refuse to determine what happened to the aircraft, and subsequently their logic is that because they have no analysis to prove they were at fault (due to them refusing to analyze the data in the first place!) they are now holding my drone hostage until I pay their ransom money so they can then "repair" their own flawed drone just to send it back to me!
Subsequently I analysed the data myself using available data analysis tools and determined and proved beyond any reasonable doubt that this that in this case it is the 100% fault of the DJI, to wit: it is the total fault of the DJI Mavic's firmware bug which caused an out of control event that forced the drone to fly erratically against user control and beyond normal flight permitted characteristics, ultimately resulting in a hard crash causing significant damage to the drone itself.
The logs show that subsequent to the Mavic's imuYaw re-initialization a critical firmware bug caused both IMU's fail simultaneously and locked one motor keeping it's revs constant way above the rest for no explainable nor logical reason as a result caused the Mavic to fly out of control at excessive speeds of 55+ mph whilst in forced autoland mode (thus refusing any inputs from the user/pilot) and directly causing and directly resulting in a very damaging uncontrollable crash at high speed into a tree.
The root cause of this incident was on a level above the IMU, as the evidence shows, this was can only be explained by a defect in the firmware and/or in the flight controller itself, in both/all instances, this definitely falls on DJI to repair or replace at DJI's cost!
After having replied back and sent DJI all the evidence and analysis based on that evidence, DJI has so far refused to accept responsibility, and refused to repair or replace at their option and cost, and is still holding my $1600+ USD drone hostage until I pay them the ransom money!
Forensic hashes of the flight logs data:
< T:\20-08-29-09-18-19_FLY056.DAT >
MD5: C6EAB26A7200B298DC470166FAAD0A2A
SHA-1: CE71C8B13CACFAF50B89B19434638F0541CC0CE5
SHA-256: B10199201A1DFA18C31C6CA2EF375C8BB213C98141889279031D42068CA19F84
SHA-512: 4C4AD4895CA779A7838381E6D13146F44608D13539E7F48E0F567D1DD57845AC48677B0A127E9D63A3C686FAEA4D145C1D585043A55E139C1FF7E1800ADCA112
< T:\DJIFlightRecord_2020-08-29_[09-18-40].txt >
MD5: 6B967FD0706208FE6E0A4D4D57BA3461
SHA-1: 4A11E3F7445D9390FD5C7B9C675FF341979D71CF
SHA-256: 29D3E9967C5FCD77B8CC7707B145C9D7362722E6B785122230C3D5FDCB0F6925
SHA-512: 21150D2695D048C2B25FB05BF89E9E0E26EE6D0F377EFA22C76BF60F09592933B50A2632CE10C1922A3A2A320250F657CA0CEBAA0F6019B83E8FD6E1F385C30A
Competition from skydio 2 is good for the entire consumer drone industry, activetrack is dji's true achilles heel...
Https://vimeo.com/382213949
Https://archive.Org/details/dji_m2p_activetrack_crash_dec312019
I've been flying dji drones since the first mavic first came out back in late 2016. Since that time i've bought a spark, mini and also have the mavic 2 pro as well. Dji has pretty much dominated the consumer drone market for a couple years now, especially after the battle with gopro went decidedly in favor of dji.
Most people considered the mavic 1.0 state of the art at the time, and the mavic 2.0 an iteration on top of that. Before the skydio 2 came out, the dji activetrack 2.0 was pretty much considered the best there was on the market.
2019 hadn't been a good year for dji. I felt that they really didn't come out with anything new or mind-blowing and in fact the mini was a step backwards. Sure the mini lets them market the mass lower market, but it demonstrated no progress in terms of technological advancement. The innovation train at dji seemed to have stopped or at least paused for a year.
While the skydio 2 as of yet is not really an all-around well rounded replacement of the mavic 2, it does have the competitive advantage in terms of true autonomy and ai tracking that puts dji's current lineup to shame.
I personally don't have a skydio yet but i've been watching a lot of youtube videos showcasing the competitive advantage of the skydio especially as compared to dji active track. Having had mavic for a while, i've never really tried its activetrack 2.0 features, but having some time on my hands on the last day of the decade Dec 31 2019) and living near a large high school with empty deserted parking lot i decided to give it a try to have it chase my car while i'm driving super slowly Less than 10 miles per hour).
Long story short, it ended in disaster with my mavic pro crashing and suffering much damage. This was my very first time using active track from dji, and it was also my very first crash out of hundreds of successful flights. The fateful flight in question was done in broad daylight, little to no wind, not in or even anywhere near any nfz zones or areas, and as well i was utilizing the "slow mode" of the activetrack 2.0 in which the drone was using all sensors including the side sensors. I didn't subject it to tricky situations, no skinny tree branches or reflective mirrors or any gimmicks or gotchas. While it was actively tracking me in the slow mode it collided into an obstacle that it could have, and indeed should have been able to see in time to completely avoid.
What made the matter so much worse is the string of issues that lead up to the crash. It wasn't just the fact that in this instance activetrack 2.0 failed me and caused the dji mavic to collide with an object that it should have avoided, it was the fact that this accident was a chain of issues that all lined up and each of the issues themselves was attributed to yet another failure on the part of dji itself.
You see, when i first set out to test activetrack 2.0 on my mavic pro 2 in the empty parking lot i was cognizant of the height issue and wanted to maintain a floor of at least 200 feet agl at all times, this was basically my backyard and my neighborhood and i knew that 200 feet would give me plenty of margin for error even if activetrack failed to see or avoid any taller obstacles.
However even though this was in broad daylight, with almost no winds that day, and i was the only car in the very large empty parking lot, when flying at around 200 feet in the air the mavic would lose activetrack within a few seconds after having acquired a lock and started tracking. In essence, activetrack was essentially nonfunctionality in terms of attempting to track a vehicle In this case my own car going very slowly at less than 10 mph at all times) at a height of just 200 feet.
So i had to lower the height to something much lower to have it actually be able to track my car. This was the first failure of dji activetrack not being reasonably robust enough and having these severe limitations that required the tracking to be commenced in such low altitudes that it put the aircraft in a significantly more dangerous flight envelope and also contributed to the lack of safety margins that ultimately combined with other flaws in the dji design that ultimately lead to fatal crash. )
I lowered it to around 80 feet and it would track my car, but for the life of me i could not get it to stay in "behind" mode, i wanted it to track my car from behind and not from the front or from the side, but every time i started a track from "behind" it would inevitably and invariably move to the side the moment i turned my car in any direction.
There was simply no way i could force the mavic to keep tracking me from the behind, regardless of how slow i was going in my car. This was the second failure on the part of dji activetrack, as had it been able to follow simply instruction of tracking me from behind it could have compensated for the first flaw Requiring very low height in order to keep tracking lock) without putting safety in jeopardy, but since it decided to start moving to the side this put the mavic in a position where potentially it would be more prone to strike objects, given the dual prong facts that the side sensors were less able than the stereo front /back sensors, and also that when tracking a car on the street, usually the behind profile would be safer than the side profile in terms of flying/tracking at lower heights. This was basically an all-around bad combination of events that dji itself caused...
So after having spun a few times around the parking lot, i decided to drive a short block around my immediate neighborhood street. I drove very slowly, slower than 10 miles per hour, and as i turned the corner i could see that since the mavic choose on its own to shift to the right side tracking profile it would come within close range to a taller tower-like structure or obstacle that we were approaching.
Immediately i grabbed hold of the joystick and made inputs for the mavic to increase in height. I was still getting a perfect real-time picture feed and perfect downlink from the mavic cameras to my dji go app on my ipad tablet device connected to the mavic remote controller, and at no point did i have any loss of connection or loss of video feed, however i observed that despite my full deflection on the height input telling the mavic to climb as quickly as it could to get as much altitude as it can, the mavic stayed in its activetrack profile and refused my command inputs to increase in altitude.
Out of all my years of flying the mavic i've never encountered any situation in which it would refuse to listen to my input to command it to increase in altitude. The only other scenario in which this happened was when it was in a nfz with a max altitude/height restriction, but this being in my own backyard i knew for sure 100% that there were no nfz's around nor any altitude restrictions, and in any case, my mavic was only about 100 feet at the time, well under the 400 feet agl as dictated by the faa.
The only thing i can surmise is that the activetrack 2.0 had a glitch or a bug that caused in this instance the mavic to refuse all height input commands. This reminds me of the boeing 737max mcas issue in which the pilots try to save the aircraft but the flawwed ai thinks it is smarter than the pilot and then locks the pilot out, causing a fatal crashes.
Soonafter, before i even had a chance to manually cancel the activetrack and take full manual control, i heard a loud band and a thud noise and i knew the mavic had collided with something while flying in the "slow" Safer) mode of activetrack, in broad daylight, with no wind, nowhere near a nfz zone, and with all sensors including side sensors actively operating. Not only did the mavic refuse my command input to increase height, not only did its obstacle avoidance completely fail to avoid the object, but it hit the object while refusing to allow me to make manual corrections that could have saved the day.
My next course of action after i got home with the damaged drone was to figure out what the heck happened. Part of that was the recovery of the flight logs, but as it turns out, the flight logs were mysteriously missing and apparently deleted by the dji go app itself. It wasn't like i flew a whole bunch of missions after this and the flight logs somehow overwrote itself, the fact of the matter was i didn't fly any missions after the crash and didn't even touch the ipad until it was time for me to attempt to retrieve the logs to figure out what the heck had happened. So the only possible scenario in which the flight recorder logs disappeared was that dji simply didn't log it in the first place, or somehow the dji app locally or dji themselves remotely deleted it somehow after the fact. This was more mysterious given the fact that i had logs from the 24th, and so the other older missions logs were still intact but not the mission that was most critical for analysis!
I also learned that even though the actual raw .Dat logs were on the ipad and could be retrieved that starting with the mavic 2 dji decided to encrypt those logs without giving anyone the key. So the .Dat logs were for all intents and purposes useless to anyone but dji themselves, how transparent of them!
One would think in this day and age in which the us government is deciding whether or not to ban dji Much like how they banned huawei etc) that dji would be more transparent and would choose to not encrypt the logs! for one thing, we all know dji is coming up with app to allow anyone to track dji drones anywhere, and the dji drones is emitting telemetry to the entire world and public at large, so from end user Customer/drone pilot) standpoint dji seems to think that level of sharing privacy is okay but then dji goes behind the backs of its customers and encrypts their own flight log data and doesn't give the key?!
It just seems backwards... Dji actively disregards the privacy of their own customers but then go out of their way to hold their own customers' data hostage from themselves! even critical diagnostic data! this makes no sense whatsoever and doesn't even pass the smell or sniff test.
This is not what a customer service oriented company should treat its paying customers. This is not a good trend for the industry! trade war or no trade war, entity list or no entity list, dji should not be eroding the privacy of their paying customers whilst at the very same time locking their customers down and blocking them from access to their very own data! there is no excuse for this double standard and hypocrisy!
I'm not anti-dji and in fact in the past when i criticized other drones like the uk zano drone i was publicly accused of being an employee of dji :
For the past couple years, i've been a huge supporter of dji and their products, but there comes a point in which one has to admit that dji is starting to fall behind in terms of innovation, and without a credible contender to effectively compete with dji, then i do believe we are already seeing stagnation in the industry and this is to the detriment of the end users and the consumers and the growth and viability of the industry itself long term.
It is not surprising then that skydio 2 has targeted its strengths to be exactly where dji is lacking the most, in terms of true ai autonomy and real active tracking... While the dji mavic 2 is still a very good product overall, and overall well-polished, its biggest lack would definitely be its glaring weakness when it comes to things like autonomy, active track and other forms of ai modes, or lack thereof.
I've flown the mavic for years, hundreds of flights, never a hitch. That is a testament to the quality of the dji mavic product. But the very first time i attempt an active track flight, dji flies the mavic into an object and crashes. Sure this is just one instance and not representative nor statistically significant, but it is significant to me subjectively and it shows me that when it comes to things like activetrack, dji products are not to be trusted and still light-years away from any sort of truly smart autonomy or trustworthy tracking capabilities.
It is my hope that the third version of the mavic Mavic 3.0) will greatly improve in this regard, but as things stand, the mavic 2.0 activetrack 2.0 is in my opinion less than useless and it almost cost me a loss of nearly $1600 usd. This is at best a total loss of confidence in dji's so-called activetrack tech and at worst almost criminal level of false advertising. Since i was using the "slow mode" which was pitched as being full sensor ultra-safe, and this was flown under the most ideal of circumstances, broad daylight, super slow, no wind, fully up to date firmware, etc)
To sum it up, we as consumers should welcome competition in the open market from all players and all angles, if skydio 2 can bring the best out of dji and finally force them to make mavic 3 with actually usable active track and real autonomy then all the better, but if dji fails to improve then i can foresee the day in which a skydio 3 could be a full on replacement for any dji mavic or other dji drones in the future.
Below you will find the email I sent to DJI. Not once, not twice, but three times. No one answered the emails only the twitter posts at @ViewsElevated where they did nothing but send me blanket responses. Oddly I received 2 responses, one where they were insinuating that nothing happened and they didn't know that firmware wrecked Osmo 2 Gimbals from DJI (which is a lie because it's all over the internet and their own forums). The other telling me that I was past 15 days out and because of that they wouldn't do anything. They later told me that I should ship it to a facility for them to determine if it was messed up. THIS is NOT feasible as DJI is known for taking peoples units and shipping back broken, or units missing parts. A youtube search of DJI Sucks will show these videos.
I simply asked their DJI Customer Support on twitter @DJIGlobal @DJIEnterprise @DJISupport to please send me a new unit since mine was only used twice before the firmware crashed it and send me a label to return the other unit. They told me no and gave me the reasons above and told me they absolutely would not help me out. I had an event last night, tonight and tomorrow (all of which I had to forefeit) becausse they would not replace the unit and I wasn't going to go buy another one of theirs.. and the unit I ordered from another company won't be here for 2 more weeks. I did NOT know DJI had a history of treating their customers horribly until I resesarched complaints over the last 2 days.
Again, all I wanted was the unit replaced with the same or upgraded unit for the trouble. They are crooks and by sending out firmware that is bricking and crashing units .. draw your own conclusion. #DJISucks Good afternoon,
I am not sure what is more disappointing, your product or your customer service "team" as you call them. I purchased the highly desired Osmo 2 Mobile from DJI from the Apple online store just a couple of months ago over the Osmo. Your marketing team did a solid job in selling me and many others a very weak piece of equipment. As well, the new firmware is a complete and utter failure, the motors make loud noises, and it's only been used 2 times prior. And then when I installed the new firmware that a lot of people stated bricked their device, I had the same result of the phone going "limp" - you can understand where this would be a problem right? A problem that no technical viagra can fix apparently...
To give a basic run down I installed your latest firmware that is supposed to resolve issues NOT BREAK the device. DJI GOs red banner popped up, we installed it, and it looked fine until we went to calibrate the phone. After calibration it requested a reboot of the Osmo2 and we did that. It restarted, the phone swung around like it normally does then boom LIMP like an 80 year old man in an cooler. I restarted the phone, the osmi, I rebalanced the iPhone X, and - AND it swung around, and LIMP! So, took my small case off my phone and it did the same thing, I tried my Note 8 and nothing. I did on occasion get some motor noises but that was about the extent of it. So, I then looked up on the forums to see if anyone else had these issues. And to my surprise, MANY people had these problems with their units being bricked etc... (Imagine that!) So I figured I would give this customer care a shot, maybe, just maybe it would be as good as 3Dr's when I had their drone and it had issues... Nope, just epic failure written all over it. I first explained to your customer service agent "who spoke very little english" yet was taking calls from the US, that I have an event tomorrow and Friday. He didn't seem to care much and simply followed his script. I explained to this rep all that I had done so that we could skip most of these steps YET he preceeded to ask me the same question 3x in a different form. Not sure why, but he did. After going back and fourth with him on this amazingly well service call (sarcasm) I then just requested to get to a supervisor. We can only imagine how well this went since support reps must learn their lack of ability from the TOP.
So, after 30 minutes of waiting I get this young lady on the phone who (yup) followed pretty much the same script, telling me that this is all they can do and that I would have to send it in for replacement or fix. I told her this was not an option that I needed a working device for my event tomorrow and she pretty much gave me a simulated, digital middle finger through the phone. Hardly appropiate for service staff to be this way but this is how she was. I was fuming at this point because I now have a device that hasn't been used and now doesn't work at all and I am screwed. Maybe I should have purchased the OSMO but then now knowing what kind of service I would receive, maybe not. I now wonder if my P4P+ is going to get the same service level as I received here after 54 minutes of total support time.
I know you all don't care, I can see it on your twitter responses. I dealt with it first hand there and on my phone call. But maybe, just maybe.. someone out there in DJI Land will take a look around and instead of enjoying this market share, you will look after your customers. I come from a service background with the best in the world at delivering service "Disney, Ritz Carlton, Marriott" so maybe I expect to be treated like a client vs a stain on the ground. That did not happen here though and the support level seems to be across the board.. BAD. All I wanted was a workind device, no one that grinded and made motor noises then killed it self once I did a firmware update. Thats all... It's really a shame that did not happen. Thanks for listening,