Hi,

i have the following scenario:

- startup P3
- Google maps GPS  and dji go GPS show the exact same homepoint on their maps.
- My Remote-position is not moved at all and stays at homepoint/startingpoint of P3.
- P3 is 50m away, height 10m, 7 satellites available, no clouds, no wind.
- activating gohome:
"select return position" pops up:
"Your current position is far away from the original Home Point. Select a position the aircraft will return to, or click cancel to exit." - Although google maps and dji software STILL show the exact same homepoint on their maps !

As i can find only vage information on the internet i would like to know what is ment by
"original home point" and "current homepoint" and especially why the "select return position" pops up.
To my understanding "original home point" is the startpoint of the P3 at start (GPS from P3) and "current homepoint" is the position of the remote (GPS by tablet).
Is that right ?

Yesterday the P3standard (4 weeks old) flew away to a total new spot. After a short signal loss I hit the gohome command, when it was online again.
"select return position" popped up. I guess i chose "current homepoint".
But it did not react and flew away. Then a new homepoint - position was displayed. It was not possible to cancel. P3 was only 500m away on countryside - no obstacles.
Since yesterday the "select return position" keeps on popping up everytime the gohome button is pressed.
Very scary...
Luckily we found the P3 because the recorded flightmovements showed the "magical set new" homepoint which was 1.3 km away in an area we have never been before.

So i guess, something must be wrong with the GPS cordination.

Any ideas ?

P3S, latest FW, Nexus 7 2nd gen, DJI GO Android

Six months or more back, I saw two reports of P3 standards doing something like your explain and haven't seen any more since.
The flight data may help to see what is happening.
Go to http://www.phantomhelp.com/LogViewer/Upload/
Follow the instructions to upload your flight record.
Come back and post a link to the report it provides and perhaps that will help.

Ok, here is the link to the flightlog when it flew away:

http://www.phantomhelp.com/LogViewer/7QXD3J6Z21R328QQNYEI/#

And here is my updated picture of the landing point, because it seems to be not in the flightlog but was luckily displayed on the screen that day:

And this was the scenario one day later (test today) when the "select return position" popped up again on trying to select "gohome".
But i did not dare to use it.

http://www.phantomhelp.com/LogViewer/E4P4BYXP9GIT9NHGVD68/

formentera Posted at 2017-1-21 16:16
Ok, here is the link to the flightlog when it flew away:

http://www.phantomhelp.com/LogViewer/7QXD3J6Z21R328QQNYEI/#

This is very similar to the two cases I saw back then.
Both of them also involved the P3 Standard and having a Max Distance limit set.
I'm not sure but I think they happened straight after a new firmware release and a short time afterward, another update was released and we haven't heard of any more cases.
Are you using current or older firmware?

Part of the problem was the Max Distance limit because once the new home point was set, the Phantom thought it was outside the limit and wanted to go home to get back inside the limit.
If no limit was in place, the flight would have been uneventful (as long as you did not use RTH).

It's definitely disturbing that the homepoint has changed itself like that and if it was mine I'd be checking the firmware version first.
The reason the rest of the flight didn't show is that the Phantom went out of range.
But the new home point can clearly bee seen in the data.

Here's a screenshot showing the original and new homepoints

Today i have same problem and i have good luck because i could have lost my dron.
It is a serious problem, we have confidence in the RTH system  and if this fail....

Basically the problem is DJI GO is assign a failed GPS position, when start the DJI mark a real home point but if you see the distance between the point and your position is very long, for this reason when select the RTH button appear a popup quering you for use the current position or the original position. REMEMBER ALWAYS USE ORIGINAL POSITION, before, see in the map if the home point if near you.

I think the problem is the update 3.1.2 of the dji go app.

I attach 2 recent pictures and you can see the position register for a device with the 3.1.1 version and the 3.1.2 versión.
My correct position is the 3.1.1 versión, why the 3.1.2 are incorrect? only DJI have the response. In another app for example google maps my position are correct.

   

Error position [v.3.1.2]

This may be worth pinging DJI support on.. latest firmware everywhere, and the latest app? Scary!

OK - latest Go app 3.1.2 pops this up.

Old position is previous home position

Current position is the take-off home position recorded when you started this flight.

Its just bad wording on DJI part.

It confused me when I first saw it - so I tested at reasonable height .....

Old position tried yo go back to my house over 50kms away which was site of my last flight.

Current position landed at take-off point where I was.

Personally I cannot see point of the pop-up .....

Nigel

Hi Nigel,

are you sure with the definition of "old position" aka "original home point" ? Is it from a flight before  (i.e. day before)?
Does somehow not make sense to me.
When i hit  "original home point" it is coming back to the starting point of the actual flight - when hitting "current hp" it flew away.

NEWS:
So it seems: Now we are three in the Club !   Here is also a P3pro:

http://forum.dji.com/forum.php?m ... 6orderby%3Ddateline


My first incident happened on the 20.Jan.

History:

There was an update before on the 15. Jan
But RTH  was no problem or did not appear until 21.Jan.

Then there was this scary incident - police involved because it landed in a garden of a scared resident.
It was the first time that it happened.

I contacted DJI chat, they were friendly but i do not know if they took it serious or understood the problem.
They said they would make a case out of it and let me fill out formular in the end.
But i did not get any response or email yet.
They also told me to update the FW - what i did on 21. Jan.

But the RTH "select return position" persists as discribed above.

DJI Go (Android) is also the latest software 3.1.2 all the way through.

The RTH was the decisive reason for buying the P3 - but now we are scared to fly !!!!

[00172124]========== 2017.01.15 13:52:48. boot(0) ============
[00172245]Packet [C:\P3C_FW_V99.99.9999.bin] detected, card sn [0x53641d23].
[00172277]Packet upgrade start...

[00172312]Packet checking...
[00172354]Packet vlink 01.08.0100 <-> 01.07.0090.
[00172415]Done.

[00172445]Version checking[1]...
[00172535][03 06][00] v2.4.20.22 -> v2.4.20.28 need upgrade.
[00172615][09 00][00] v0.1.0.9 -> v0.1.1.0 need upgrade.
[00172646]Done.

[00174677]Waiting for user confirm...
[00184710]Timeout, start upgrade automatically.

[00184804]Firmware upgrading[1]...
[00185101][03 06] Firmware upgrade start...
[00565419][03 06] Firmware upgrade finished successfully.
[00565472][09 00] Firmware upgrade start...
[00591660][09 00] Firmware upgrade finish without reboot.
[00621699][09 00] Firmware upgrade finished successfully.
[00621730]Done.

[00621767]Version checking[2]...
[00621847][03 06][05] v2.4.20.28 -> v2.4.20.28
[00621903][09 00][05] v0.1.1.0 -> v0.1.1.0
[00621936]Packet upgrade finish successfully.



[00228084]========== 2017.01.21 11:11:26. boot(15) ============
[00228118]Packet [C:\P3C_FW_V99.99.9999.bin] detected, card sn [0x53641d23].
[00228154]Packet upgrade start...

[00228190]Packet checking...
[00228231]Packet vlink 01.08.0100 <-> 01.07.0090.
[00228266]Record vlink 01.08.0100 <-> 01.07.0090 (flow = 0).
[00228297]Done.

[00228330]Version checking[1]...
[00228440][11 01][00] v2.0.0.32 -> v2.0.0.33 need upgrade.
[00228472]Done.

[00230515]Waiting for user confirm...
[00240560]Timeout, start upgrade automatically.

[00240626]Firmware upgrading[1]...
[00240670][11 01] Firmware upgrade start...
[00304585][11 01] Firmware upgrade finished successfully.
[00304621]Done.

[00304652]Version checking[2]...
[00304774][11 01][05] v2.0.0.33 -> v2.0.0.33
[00304805]Packet upgrade finish successfully.

Mistake #9: It should read: "But RTH  was no problem or did not appear until 20.Jan."

Hi, I went for a fly this afternoon, and had a number of problems that were non existent yesterday!
For a start I did all my compass calibrations, then DJI Go reported "Intensive electromagnetic interference nearby. Ensure no magnets or metal objects are near the compass."
I was in the middle of a river bed and the only metal was my vehicle about 15m away.
I turned everything off and restarted, did the compass dance again and all reported fine.

Proceeded to do an auto takeoff and the drone jumped backwards and tumbled across the ground for about 5 metres.  Soon as it started to move sideways I dropped the throttle stick to the bottom but it would not stop.
Checked the AC for damage and put new props on. (Old habit from helis, if they touch they're in the bin)
Round two. Everything Ok, took off and headed away only to notice on the map I was 192m away from the home point.. (I was standing about 2m away from it!).
Anyway flew about 600m and came back and landed so I could go home and check recording and logs to see what was wrong..  Everything worked OK yesterday.

Guess what I found..  The damn thing (Android tablet) auto updated the DJI Go app overnight!!  I am now on 3.1.2 App. The Positions on my map are wrong and after reading the posts above I am now more nervous about fly it.
What happens if it thinks home is nowhere near you and signal drops. It could end up anywhere. I am lucky mine would probably crash in the the middle of nowhere but the guys that fly near cities would have be concerned.

I think all these issues are from the updated Go app.  Now I need to figure out how to get the previous version back.  Not waiting for a fix from DJI as I have only had the thing a month and haven't had a day flying with it with out an issue with Firmware, Batteries, Updates or now the App!

I only purchased this one as I could not get a Mavic in Aust, so thought I would learn to operate this one until the Mavic was available.

Dave

Hey guys,

Looks like I experienced the wrath of the new update, same thing calibrate compass etc check everything working, however it set my setpoint 200 meters away from myself when I was about to get back...

This is my initial flight plan: http://www.phantomhelp.com/LogViewer/6D7W36FI1O1M2W09NLO1/

Crash land:  http://www.phantomhelp.com/LogViewer/I4P0EYXMDGJQDNICYD64/

Tried looking for it, didn't find, crashed on the roof most likely..

Ps I had a low battery and suddenly it started landing and just simply couldn't connect to it anymore, perhaps signal interference. it shouldn't have ended 200 m away from me!

I am trying to see whether I can do anything about this..so unfortunate

Have a goodnight guys.

MsTron Posted at 2017-1-21 19:42
Today i have same problem and i have good luck because i could have lost my dron.
It is a serious problem, we have confidence in the RTH system  and if this fail....

I have serious doubts about this "problem" case.
I explained the situation on your other post about it.  http://forum.dji.com/forum.php?m ... 9&fromuid=10818

formentera Posted at 2017-1-22 01:28
Hi Nigel,

are you sure with the definition of "old position" aka "original home point" ? Is it from a flight before  (i.e. day before)?

"So it seems: Now we are three in the Club !   Here is also a P3pro:"

I also have doubts about this one.
There are some possible explanations but the OP there has not supplied any flight data which would probably make the cause clear.
Don't assume that there is a problem just because a user says they think there is a problem.

DaveH_au Posted at 2017-1-22 04:43
Hi, I went for a fly this afternoon, and had a number of problems that were non existent yesterday!
For a start I did all my compass calibrations, then DJI Go reported "Intensive electromagnetic interference nearby. Ensure no magnets or metal objects are near the compass."
I was in the middle of a river bed and the only metal was my vehicle about 15m away.

"I think all these issues are from the updated Go app.  Now I need to figure out how to get the previous version back.  Not waiting for a fix from DJI as I have only had the thing a month and haven't had a day flying with it with out an issue with Firmware, Batteries, Updates or now the App!"

Don't jump to conclusions.
What you describe is unlikely to be related to either firmware or the app and it probably has a logical explanation that could be discovered by examining flight data.
We seem to have several people convincing themselves of an imaginary problem due to confusion.
I've explained some of this here:  http://forum.dji.com/forum.php?m ... 9&fromuid=10818

If you want to get to the bottom of your incident, go to http://www.phantomhelp.com/LogViewer/Upload/
Follow the instructions to upload your flight record.
Come back and post a link to the report it provides and someone might be able to analyse it and give you an understanding of the cause of the incident.

fans19f5e8e3 Posted at 2017-1-22 05:23
Hey guys,

Looks like I experienced the wrath of the new update, same thing calibrate compass etc check everything working, however it set my setpoint 200 meters away from myself when I was about to get back...

I haven't gone over the complete records yet (it's slow and takes quite a while) but I can see your Phantom made new home points three times during your flight at 5:48, 8:47 and 12:44.
I don't know the cause of the jumping home point but I notice you also used the Max Distance limit and this seems to always be involved in these cases.
Here's a screenshot showing the final homepoint it was aiming for - on top of a roof 300 metres south of the original home.

This is one that should be referred to DJI.
Upload the flight records to DJI (click on the cloud icon on the flight record page)
Go to DJI online help and tell them the story.

formentera Posted at 2017-1-21 16:16
Ok, here is the link to the flightlog when it flew away:

http://www.phantomhelp.com/LogViewer/7QXD3J6Z21R328QQNYEI/#

This is also one that should be referred to DJI.
Upload the flight records to DJI (click on the cloud icon on the flight record page)
Go to DJI online help and tell them the story.

hi to all i have been having the same problem. i whet to fly my drone today but found that the home point was set a 1000 m away from were i was stood but on google maps it was right but now i am to reluctant to take my drone out of the box can i just clarify that latest firmware came out on the 21 jan as this is my replacement drone as my first one had gimble fault and i sent it back last week  and i received my new yesterday i just wanted to make sure that it is not a drone defect but firmware related

fans7da59d27 Posted at 2017-1-22 07:42
hi to all i have been having the same problem. i whet to fly my drone today but found that the home point was set a 1000 m away from were i was stood but on google maps it was right but now i am to reluctant to take my drone out of the box can i just clarify that latest firmware came out on the 21 jan as this is my replacement drone as my first one had gimble fault and i sent it back last week  and i received my new yesterday i just wanted to make sure that it is not a drone defect but firmware related

The simplest way to check is to go to http://www.phantomhelp.com/LogViewer/Upload/
Follow the instructions to upload your flight record.
Come back and post a link to the report it provides.
If the home point is jumping (or not), it will be clearly shown there.

Please, check it : https://forum.dji.com/forum.php? ... D394%26typeid%3D394

http://www.phantomhelp.com/LogViewer/8GD849LU3R7Y3Y6LOOUC/#

http://www.phantomhelp.com/LogViewer/UBJDR5RZPNC3PUBQBK0H/

these are two to compare

DaveH_au Posted at 2017-1-22 04:43
Hi, I went for a fly this afternoon, and had a number of problems that were non existent yesterday!
For a start I did all my compass calibrations, then DJI Go reported "Intensive electromagnetic interference nearby. Ensure no magnets or metal objects are near the compass."
I was in the middle of a river bed and the only metal was my vehicle about 15m away.

i am getting the same problem

i will not be held responsible if you want to try the link below  but i will have fly check tomorrow if you roll back to previous dji go app i think it is a temporary fix but will let you know

https://apkplz.com/android-apps/dji-go/dji-go-3-1-1

I have rolled back Go to 2.9.1 ..... cached Google maps ... disabled apps updates but left them to warn me if any available etc.

Hopefully that will solve the video lag problem ....

The range reduction due to 1.8.10 will be dealt with another way ...

Nigel

I believe it is not the firmware rather the App. The latest version shows I am located up to a 1000 metres away from my actual position.

The controller does not have a gps and uses the gps from your tab or phone for location. If the app is not correct your position is also wrong.
Sitting at home the app shows me on a roof near 800m away!  
On my apple I7 it is correct and on the android tab it is totally wrong.
I swapped back one version of the app and my position is reported correct.

Do not risk using android v3.1.2 app.

Can't wait to see the response from the US tonight. We are ahead by time zones so there will be a delay before they find the problem.
Regards Dave

Seems that I may have experienced a similar issue on a flight today.  No crash landing and I was able to get my P3S back to the original home point, but got the question of "old home or current home" when selecting the RTH function.  Had it out about 2300'' ft, experienced "magnetic field" and went into atti mode while still locating 14 satellites, but got it back okay.  
Current app version 3.1.2 and still running 1.7.9 FW.  

New to posting, so not sure how to upload screenshots yet.

I am going to do some more tests with the drone, espacially with gps settings on the Nexus 7.
In preperation to that:  Can anyone clearly confirm or contradict my assumption mentioned above:

"To my understanding "original home point" is the startpoint of the P3 at start (GPS from P3) and "current homepoint" is the position of the remote (GPS by tablet).
Is that right ?"

Please no answers like: "to my opinion" ... or "i believe"....  ;-)

formentera yes it is correct.
Original home point is the startpoint  and current homepoint is the position of your device (mobile, Tablet....).
In the map you can see, original home point as H and Current Home Point as a blue/red circle.

In flight test yesterday with an observer - I had exactly this dialogue box.

I selected Old and AC zoomed of away from me in direction of my house where I flew her flight before. I cancelled that and then selected Current - she landed at my feet.

I will no longer be trusting 3.1.2 Go app at all .... whether I am right or not there is no need for this box ... we already had the LAND and RTH tabs to select at left side. Why add this crappy box ?

I have rolled back to 2.9.1 to avoid this rubbish App .... I suggest others do same until DJI actually come up with a better solution.

Nigel

We'd like to analyze the flight records and check what happened.
If you have not contacted our tech support, please sync your flight records through DJI GO APP, then send an e-mail to support@dji.com with your APP account and the exact time it happened, then provide me your ticket number, we'll help you follow up the case, thanks.

i have sent mine to wear it should stay back in a very large warehouse as i am not going to take any chances with £450 in the air i do hope you guys get the help you need from dji but dont hold your breath that is my experience after wasting time on the phone with poor support staff

I'm not so easy beaten down ! I take this as a challenge. I can interpret the Flight Logs without DJI help ... and reckon I'll get a solution quicker.

I agree that typical result of DJI support is not reassuring .... and I feel sorry for Natalie and others here who try to keep it together.

Nigel

I've got the same problem. It all started after that freaking update. Until this get's fixed, I'm really not comfortable with flying my Phantom.

Unfortunately i chatched a cold with some fever, so i could not continue testing the drone outside  today, but it gave me the chance to search the internet and play store reviews for "3.1.2".

I found that there are many more pilots with this problem.

My conclusion for today is:  the guilty is NOT the FW but the DJI GO app (at least on android).
It seems to affect the "follow function" as well as the "homepoint" = every gps related function.
All have in common that the GPS on the DJI GO  map since 3.1.2.  is sometimes offset  to the GOOGLE MAP which is always correct in all cases i have read.
So it can not be the android GPS in my opinion.

Another proof could be my timescedule:

15.1. FW2.4.20.22 -> v2.4.20.28

P3 works just fine

18.1. update DJI GO on android from previous to 3.1.2

no flight until

20.1. FLY AWAY  and "select return position" problem

21.1. FW v2.0.0.32 -> v2.0.0.33

21.1. ...."select return position" problem persists

Why in Google maps is right and in DJI Go is wrong?

I have the same problem that  I never had till upgrade my app my home point is almost 2 miles away from were I really am  and I have never took flight there ever

I'm not Taking Flight till this is fixed

Stupid question but does anyone know where I can find and how to roll. Back to 2.9.1.dji Go app for Samsung Arnold system

I had a bit of a problem too. Not sure if it's related.

Have been flying in very open areas to get used to it and get some experience. So far no problems.

The other evening I wanted to get some images of my own house from above. This involves taking off in quite a confined area until I get above the trees. Set the P3S up and calibrated the compass. All FW is up to date. Have done a few flights with the new App and FW without an issue. I okk off and positioned the drone to start taking photo's. It would not take images, so changed to video and it once again would not record, even though I could see the camera feed. Flew it back and landed using RTH and manual adjustments on decent. I then shut everything down and checked the SD card but there was no data. Refitted it and started everything back up. This time I shot some frames on the ground before starting the motors. All OK so far. Green light was on and ready to fly with GPS on. Started to take off but this time it lifted off about 10cm and started to drift sideways. I immediately shut down the motors but not before it hit an obstacle and flipped on to it's back. One of the propellers snapped but everything else seems OK.

More props now being sent and no apparent damage but why would it drift like that rather than ascend like the previous flight?