A couple of days ago, I took my MM1 out for a fun flight. The previous day I had been out, did about 3 batteries of flying with no issues.
However, yesterday afternoon, everything was ok until I pressed video record. Within a couple of seconds, the phone screen greyed out, the controller continued to allow me to control for a few seconds, then stopped all control and lost connection, only returning intermittently, which confused me but I pressed RTH and it eventually did RTH land. Note, I was only about 15 Metres away, about 8-10 metres high, and in the centre of a very large and empty double-sized sports field.
I checked the drone over, no issues, rebooted the phone, controller, and drone, and took off, being wary of what had just happened. Flew out with video running but as soon as I got to the same distance and height, the same thing happened again. Note, I was definitely logged into the DJI site in the fly app and the weather was flying perfect, sunny with almost 0 wind. This happened no matter what direction I flew in.
After some failed attempts, got the drone back through RTH. Scratched head. As an ex-Military Radar, communications and computer systems maintenance, design and development engineer / Project manager, I know something about weird electronic behavior and was determined to try and figure this out. I swapped my flight phone (yes I have a dedicated phone just for flying), and used my regular phone which is also loaded with the fly app (usually this phone is turned off when flying). Same issue at almost exactly the same height and distance. but managed to manually fly back the short distance.
Put my last battery in and took off with the regular phone back in use. After a few meters, turned the recording on. The same issue again, so after about 1 minute I decided to go home and look in the forums. I pressed RTH. The drone came back but this time the drone just hovered above my head (I always use RTH land). Nothing I could do would bring it down or maneuver it, including canceling RTH. Then the situation turned tragic and gruesome.
Now I like bees, I really do. I never use pesticides in my garden, I grow bee attracting flowers and if they swarm in my yard, I just close the doors till they move on. After hovering for about 1 minute, a swarm of bees decided to attack/were attracted to my drone. Hundreds of them. The sound was like a chainsaw cutting through the swarm. I hated it but trying an emergency prop stop, cursing and fist-waving had no effect. Around 20 minutes of Bee carnage took place until the battery ran out and the Lewis Park genocidal Bee murderer HARD landed! Needless to say, I had a gruesome cleanup job to do last night. However, on checking the SD card, Photos but NO VIDEO on the card, but the controller had indicated recording??
So, after the cleanup, I did a complete factory reset of the drone and controller back to their "roll out" firmware and also the phone, and checked the drones data file. I never had less than 13 satellites and the data indicates forced landing.
Today took it out for a test to the same location. Same issues!! Turn on video record, lose control. I changed the sd cards and reformatted them. I also "in the field" "upgraded" back to the firmware operating the previous day when the trouble had started. In effect, the drone was back to its state when the problems started. But the problems remained.
Having booked in the drone for a service, I determined that my engineering days were definitely at an end. However, I then landed the drone on its way back and, for some reason, changed the video resolution from 2.7k to 1080 and took off. IT WORKED. Full control, distance out to 85 - 100 metres and 20-30 metres height AND RECORDING !!??. I then switched back to 2.7K and ran the full sweet of built-in auto maneuvers. Full recording and No Problems. Another 20 minutes of trouble-free test flying took place with perfect response. My "Old" baby bird was back!
The drone is still going back to my local service centre but has anyone else ever encountered such erratic behavior. Until yesterday I have never had so much as a single blip in performance and don't believe it was suburban wifi related as I have flown there many times and saw no telltale signs of video breakup. As I said, the drone was never more than 18-20 metres away when the problems occurred. My gut feeling is that somehow, overnight the firmware in either the drone or the controller became corrupted as they charged, but that does not answer everything.
As for the Bees, R.I.P ?
However, yesterday afternoon, everything was ok until I pressed video record. Within a couple of seconds, the phone screen greyed out, the controller continued to allow me to control for a few seconds, then stopped all control and lost connection, only returning intermittently, which confused me but I pressed RTH and it eventually did RTH land. Note, I was only about 15 Metres away, about 8-10 metres high, and in the centre of a very large and empty double-sized sports field.
I checked the drone over, no issues, rebooted the phone, controller, and drone, and took off, being wary of what had just happened. Flew out with video running but as soon as I got to the same distance and height, the same thing happened again. Note, I was definitely logged into the DJI site in the fly app and the weather was flying perfect, sunny with almost 0 wind. This happened no matter what direction I flew in.
After some failed attempts, got the drone back through RTH. Scratched head. As an ex-Military Radar, communications and computer systems maintenance, design and development engineer / Project manager, I know something about weird electronic behavior and was determined to try and figure this out. I swapped my flight phone (yes I have a dedicated phone just for flying), and used my regular phone which is also loaded with the fly app (usually this phone is turned off when flying). Same issue at almost exactly the same height and distance. but managed to manually fly back the short distance.
Put my last battery in and took off with the regular phone back in use. After a few meters, turned the recording on. The same issue again, so after about 1 minute I decided to go home and look in the forums. I pressed RTH. The drone came back but this time the drone just hovered above my head (I always use RTH land). Nothing I could do would bring it down or maneuver it, including canceling RTH. Then the situation turned tragic and gruesome.
Now I like bees, I really do. I never use pesticides in my garden, I grow bee attracting flowers and if they swarm in my yard, I just close the doors till they move on. After hovering for about 1 minute, a swarm of bees decided to attack/were attracted to my drone. Hundreds of them. The sound was like a chainsaw cutting through the swarm. I hated it but trying an emergency prop stop, cursing and fist-waving had no effect. Around 20 minutes of Bee carnage took place until the battery ran out and the Lewis Park genocidal Bee murderer HARD landed! Needless to say, I had a gruesome cleanup job to do last night. However, on checking the SD card, Photos but NO VIDEO on the card, but the controller had indicated recording??
So, after the cleanup, I did a complete factory reset of the drone and controller back to their "roll out" firmware and also the phone, and checked the drones data file. I never had less than 13 satellites and the data indicates forced landing.
Today took it out for a test to the same location. Same issues!! Turn on video record, lose control. I changed the sd cards and reformatted them. I also "in the field" "upgraded" back to the firmware operating the previous day when the trouble had started. In effect, the drone was back to its state when the problems started. But the problems remained.
Having booked in the drone for a service, I determined that my engineering days were definitely at an end. However, I then landed the drone on its way back and, for some reason, changed the video resolution from 2.7k to 1080 and took off. IT WORKED. Full control, distance out to 85 - 100 metres and 20-30 metres height AND RECORDING !!??. I then switched back to 2.7K and ran the full sweet of built-in auto maneuvers. Full recording and No Problems. Another 20 minutes of trouble-free test flying took place with perfect response. My "Old" baby bird was back!
The drone is still going back to my local service centre but has anyone else ever encountered such erratic behavior. Until yesterday I have never had so much as a single blip in performance and don't believe it was suburban wifi related as I have flown there many times and saw no telltale signs of video breakup. As I said, the drone was never more than 18-20 metres away when the problems occurred. My gut feeling is that somehow, overnight the firmware in either the drone or the controller became corrupted as they charged, but that does not answer everything.
As for the Bees, R.I.P ?
Last edited: