Yes. Once again, note these two screen shots from the 'Flight Record', taken 1 second before, and 1 second after, I did "Home Point Me":
No.
You had any response from DJI yet?
Yes. Once again, note these two screen shots from the 'Flight Record', taken 1 second before, and 1 second after, I did "Home Point Me":
No.
No, not yet. But I'll be sure to update this thread once I do.You had any response from DJI yet?
Yes, it's probably your faultIt's probably my fault but I'm still trying to understand where 's supposed to be the bug..
Sure, but mine it's still in my backpack..Yes, it's probably your fault
Have the same problem: See Home Point to RC not registered .No, not yet. But I'll be sure to update this thread once I do.
Can you share your DJI contact, since my posting on forum.dji.com elicited silence? See Recurring run-away problems with Mavic & DJI Go 4 Under iOS
Please go to DJI Support - Here for You and use the "Email" support option. You'll get your logs analyzed by DJI. If everyone who runs into this problem does this, it'll put pressure on DJI to address the issue.This happened to me yesterday
I have very clear evidence of a serious bug in the Mavic Pro’s "Home Point Me” function (initiated from the DJI GO 4 iPhone app). To summarize: When I did “Home Point Me” (on three separate occasions), the Mavic Pro set its home point not to the location of the controller, but instead to the location of the previous flight’s home point - which, in my case, was more than 7000 feet (2000m) away from the controller. Not realizing what had happened, I then did a “Return to Home’ - which caused my Mavic to fly away.
I have uploaded the flight log here: DJI Flight Log Viewer - PhantomHelp.com
The cached flight video (from my controller) is here:
I would be happy to provide additional flight data - from my controller - if necessary to help resolve/fix this bug. (Unfortunately, because my Mavic was lost, I don’t have any video or data from the Mavic itself.)
Here is a summary of key events from the flight log and/or cached controller video:
Flight time Time in cached video Event
0:02 n/a Takeoff (GPS mode); Home Point recorded at [36.608828,-121.711527]
0:56 0:00 Video starts
1:31 0:35 Follow Me mode enabled
7:07 6:11 Error: "Satellite Signal Lost. Acquire signal and retry." (This is a confusing message; I’m guessing that it refers to the loss of GPS coordinates of the *controller*, not the GPS coordinates of the Mavic (because the Mavic was seeing 18 satellites).)
7:10 6:14 Speed drops to zero; Mavic’s GPS location: [36.613579,-121.700561]
~8:40 ~7:44 I stop riding, and realize that my Mavic has stopped following me. I (and the controller) are at [36.61499,-121.69624]
9:26 8:30 Break in downlink (& cached video)
9:39 8:30 Downlink (& cached video) resumes
9:45 8:36 Break in downlink (& cached video)
11:01 8:36 Downlink (& cached video) resumes
11:15 8:50 I use “Home Point Me” to reset the home point, supposedly to the Remote Controller (i.e., my) position, which is at [36.61499,-121.69624]. But instead, the ‘home point' gets set to [36.607533,-121.724625], which was my home point of my *previous* flight - more than 1.6 miles (2.6 km) away from me! (Find My Drone also reports this as the “Aircraft Missing Coordinates”)
11:22 8:57 Without realizing what has actually happened to the home point, I do a RtH
11:49 9:24 Mavic finishes ascending, and starts moving ‘home’. In reality, it’s moving away from me, at a speed of 22 miles per hour (35 km/h)!
12:05 9:40 Confused and concerned about what’s happening, I did “Home Point Me” once again. But the home point remained unchanged; it’s still the home point of my *previous* flight; and my Mavic is still flying away from me at 22 mph!
12:17 9:52 The Mavic switches from “Go Home” mode to P-GPS mode. (I think I may have pressed the “Pause” button here; I’m not sure)
12:20 9:55 Speed drops to zero
12:29 10:04 Forward speed resumes
12:34 10:09 I get a “Weak Signal” warning
13:06 10:41 I do “Home Point Me” once again. But the home point is still wrong (but unfortunately I don’t realize this)!
13:12 10:47 I do a RtH once again (this turned out to be a fatal mistake, because I didn’t appreciate that the home point was wrong, and I’m now near the edge of transmission range)
13:15 10:50 The Mavic starts returning ‘home’ once again. But yet again, it’s moving away from me
13:21 10:56 The cached video ends
13:42 n/a I lose connectivity. The Mavic is moving away from me at 22 mph!
Comments:
- There’s unquestionably a bug in “Home Point Me”. Why did it reset the ‘home point’ to a point that was far away from the controller, and why did it choose the point that happened to be the home (starting) point for my *previous* flight?
- The RtH speed of around 22 mph (35 km/h) seems unusually large. There weren’t strong winds, and I was not in ‘sport mode’. This behavior appears similar to some ‘fly aways’ that have been reported by other people.
The bottom line: Do not use the “Home Point Me” function until DJI fixes this bug.
- Unfortunately I wasn’t able to find my Mavic. It didn’t return to what it thought was the ‘home’ point (nor to the actual ‘home’ (i.e., starting) point of this flight). I searched along the line from its last known position to its assumed ‘home’ point (and beyond, in case it ended up overshooting this point). Unfortunately it wasn’t possible to do an exhaustive search, because the area is filled with long grass, thick chaparral, large oak trees, and 'poison oak'.
(I have also posted this report to DJI’s forum, but I’m also posting it here, in case DJI ignores or deletes it.)
I have seen that option but never used it myself. Now I don't know that I'd ever attempt it. As long as you have your DJI care they will replace your drone. You shouldn't have any issues with them doing that for you specially after seeing the footage.FYI, my Mavic was quite new - bought in July 2017.
No, I never entered 'sport mode' (which makes the 22 miles-per-hour 'RtH' speed strange).
If I'd had a better appreciation that 'Home Point Me' had failed, then I would have been able to recover my drone. But because I was near the edge of transmission range, and because my drone was moving away from me so quickly, it flew out of range before I could come to my senses :-(
I have seen that option but never used it myself. Now I don't know that I'd ever attempt it. As long as you have your DJI care they will replace your drone. You shouldn't have any issues with them doing that for you specially after seeing the footage.
There is no question that the RTH and the "Home Point" issue is serious. I have already lost two Mavic's due to the failure of RTH. After spending well over a month dealing with DJI; sending them the flight logs they are sending me a new Mavic under warranty. But, for all of you with Mavic Pro's beware! DJI refuses to admit there is something amiss with their firmware and that "fly aways" can occur at anytime. All the speculation on this forum for the reasons that this is happening is a waste to everyone's time. If you own a Mavic Pro and it is more than one year old and therefore not under warranty, I wish you all the best of luck. Sort of like cars that have recalls. Some will crash and others will never have a problem. I will say this - my first one fly off and I blamed myself for flying it in an area with a lot of interference. It was only 2,500' away but RTH failed and off it went. I was able to find it using latitude and longitude on the flight log but it was completely smashed. Insurance covered it. The second one was within 200' and I hit RTH and off it went, never to be found. I wish you all luck!I have very clear evidence of a serious bug in the Mavic Pro’s "Home Point Me” function (initiated from the DJI GO 4 iPhone app). To summarize: When I did “Home Point Me” (on three separate occasions), the Mavic Pro set its home point not to the location of the controller, but instead to the location of the previous flight’s home point - which, in my case, was more than 7000 feet (2000m) away from the controller. Not realizing what had happened, I then did a “Return to Home’ - which caused my Mavic to fly away.
I have uploaded the flight log here: DJI Flight Log Viewer - PhantomHelp.com
The cached flight video (from my controller) is here:
I would be happy to provide additional flight data - from my controller - if necessary to help resolve/fix this bug. (Unfortunately, because my Mavic was lost, I don’t have any video or data from the Mavic itself.)
Here is a summary of key events from the flight log and/or cached controller video:
Flight time Time in cached video Event
0:02 n/a Takeoff (GPS mode); Home Point recorded at [36.608828,-121.711527]
0:56 0:00 Video starts
1:31 0:35 Follow Me mode enabled
7:07 6:11 Error: "Satellite Signal Lost. Acquire signal and retry." (This is a confusing message; I’m guessing that it refers to the loss of GPS coordinates of the *controller*, not the GPS coordinates of the Mavic (because the Mavic was seeing 18 satellites).)
7:10 6:14 Speed drops to zero; Mavic’s GPS location: [36.613579,-121.700561]
~8:40 ~7:44 I stop riding, and realize that my Mavic has stopped following me. I (and the controller) are at [36.61499,-121.69624]
9:26 8:30 Break in downlink (& cached video)
9:39 8:30 Downlink (& cached video) resumes
9:45 8:36 Break in downlink (& cached video)
11:01 8:36 Downlink (& cached video) resumes
11:15 8:50 I use “Home Point Me” to reset the home point, supposedly to the Remote Controller (i.e., my) position, which is at [36.61499,-121.69624]. But instead, the ‘home point' gets set to [36.607533,-121.724625], which was my home point of my *previous* flight - more than 1.6 miles (2.6 km) away from me! (Find My Drone also reports this as the “Aircraft Missing Coordinates”)
11:22 8:57 Without realizing what has actually happened to the home point, I do a RtH
11:49 9:24 Mavic finishes ascending, and starts moving ‘home’. In reality, it’s moving away from me, at a speed of 22 miles per hour (35 km/h)!
12:05 9:40 Confused and concerned about what’s happening, I did “Home Point Me” once again. But the home point remained unchanged; it’s still the home point of my *previous* flight; and my Mavic is still flying away from me at 22 mph!
12:17 9:52 The Mavic switches from “Go Home” mode to P-GPS mode. (I think I may have pressed the “Pause” button here; I’m not sure)
12:20 9:55 Speed drops to zero
12:29 10:04 Forward speed resumes
12:34 10:09 I get a “Weak Signal” warning
13:06 10:41 I do “Home Point Me” once again. But the home point is still wrong (but unfortunately I don’t realize this)!
13:12 10:47 I do a RtH once again (this turned out to be a fatal mistake, because I didn’t appreciate that the home point was wrong, and I’m now near the edge of transmission range)
13:15 10:50 The Mavic starts returning ‘home’ once again. But yet again, it’s moving away from me
13:21 10:56 The cached video ends
13:42 n/a I lose connectivity. The Mavic is moving away from me at 22 mph!
Comments:
- There’s unquestionably a bug in “Home Point Me”. Why did it reset the ‘home point’ to a point that was far away from the controller, and why did it choose the point that happened to be the home (starting) point for my *previous* flight?
- The RtH speed of around 22 mph (35 km/h) seems unusually large. There weren’t strong winds, and I was not in ‘sport mode’. This behavior appears similar to some ‘fly aways’ that have been reported by other people.
The bottom line: Do not use the “Home Point Me” function until DJI fixes this bug.
- Unfortunately I wasn’t able to find my Mavic. It didn’t return to what it thought was the ‘home’ point (nor to the actual ‘home’ (i.e., starting) point of this flight). I searched along the line from its last known position to its assumed ‘home’ point (and beyond, in case it ended up overshooting this point). Unfortunately it wasn’t possible to do an exhaustive search, because the area is filled with long grass, thick chaparral, large oak trees, and 'poison oak'.
(I have also posted this report to DJI’s forum, but I’m also posting it here, in case DJI ignores or deletes it.)
I have very clear evidence of a serious bug in the Mavic Pro’s "Home Point Me” function (initiated from the DJI GO 4 iPhone app). To summarize: When I did “Home Point Me” (on three separate occasions), the Mavic Pro set its home point not to the location of the controller, but instead to the location of the previous flight’s home point - which, in my case, was more than 7000 feet (2000m) away from the controller. Not realizing what had happened, I then did a “Return to Home’ - which caused my Mavic to fly away.
I have uploaded the flight log here: DJI Flight Log Viewer - PhantomHelp.com
The cached flight video (from my controller) is here:
I would be happy to provide additional flight data - from my controller - if necessary to help resolve/fix this bug. (Unfortunately, because my Mavic was lost, I don’t have any video or data from the Mavic itself.)
Here is a summary of key events from the flight log and/or cached controller video:
Flight time Time in cached video Event
0:02 n/a Takeoff (GPS mode); Home Point recorded at [36.608828,-121.711527]
0:56 0:00 Video starts
1:31 0:35 Follow Me mode enabled
7:07 6:11 Error: "Satellite Signal Lost. Acquire signal and retry." (This is a confusing message; I’m guessing that it refers to the loss of GPS coordinates of the *controller*, not the GPS coordinates of the Mavic (because the Mavic was seeing 18 satellites).)
7:10 6:14 Speed drops to zero; Mavic’s GPS location: [36.613579,-121.700561]
~8:40 ~7:44 I stop riding, and realize that my Mavic has stopped following me. I (and the controller) are at [36.61499,-121.69624]
9:26 8:30 Break in downlink (& cached video)
9:39 8:30 Downlink (& cached video) resumes
9:45 8:36 Break in downlink (& cached video)
11:01 8:36 Downlink (& cached video) resumes
11:15 8:50 I use “Home Point Me” to reset the home point, supposedly to the Remote Controller (i.e., my) position, which is at [36.61499,-121.69624]. But instead, the ‘home point' gets set to [36.607533,-121.724625], which was my home point of my *previous* flight - more than 1.6 miles (2.6 km) away from me! (Find My Drone also reports this as the “Aircraft Missing Coordinates”)
11:22 8:57 Without realizing what has actually happened to the home point, I do a RtH
11:49 9:24 Mavic finishes ascending, and starts moving ‘home’. In reality, it’s moving away from me, at a speed of 22 miles per hour (35 km/h)!
12:05 9:40 Confused and concerned about what’s happening, I did “Home Point Me” once again. But the home point remained unchanged; it’s still the home point of my *previous* flight; and my Mavic is still flying away from me at 22 mph!
12:17 9:52 The Mavic switches from “Go Home” mode to P-GPS mode. (I think I may have pressed the “Pause” button here; I’m not sure)
12:20 9:55 Speed drops to zero
12:29 10:04 Forward speed resumes
12:34 10:09 I get a “Weak Signal” warning
13:06 10:41 I do “Home Point Me” once again. But the home point is still wrong (but unfortunately I don’t realize this)!
13:12 10:47 I do a RtH once again (this turned out to be a fatal mistake, because I didn’t appreciate that the home point was wrong, and I’m now near the edge of transmission range)
13:15 10:50 The Mavic starts returning ‘home’ once again. But yet again, it’s moving away from me
13:21 10:56 The cached video ends
13:42 n/a I lose connectivity. The Mavic is moving away from me at 22 mph!
Comments:
- There’s unquestionably a bug in “Home Point Me”. Why did it reset the ‘home point’ to a point that was far away from the controller, and why did it choose the point that happened to be the home (starting) point for my *previous* flight?
- The RtH speed of around 22 mph (35 km/h) seems unusually large. There weren’t strong winds, and I was not in ‘sport mode’. This behavior appears similar to some ‘fly aways’ that have been reported by other people.
The bottom line: Do not use the “Home Point Me” function until DJI fixes this bug.
- Unfortunately I wasn’t able to find my Mavic. It didn’t return to what it thought was the ‘home’ point (nor to the actual ‘home’ (i.e., starting) point of this flight). I searched along the line from its last known position to its assumed ‘home’ point (and beyond, in case it ended up overshooting this point). Unfortunately it wasn’t possible to do an exhaustive search, because the area is filled with long grass, thick chaparral, large oak trees, and 'poison oak'.
(I have also posted this report to DJI’s forum, but I’m also posting it here, in case DJI ignores or deletes it.)
We use essential cookies to make this site work, and optional cookies to enhance your experience.