On my 23rd flight yesterday the P3s lost signal and went into RTH Mode but failed to climb to the set 40m RTH Alttitude. Flight Record shows it stayed at 64' and accelereated from 0 to 16mph in the 13 seconds of Go Home Mode without climbing. Also some strange message right before it went into RTH:
To takeoff in non-P modes, toggle Flight Mode Switch to another mode and then toggle it back.


Then

RTH: Braking to avoid   obstacle

Signal Lost. Aircraft   returning to Home Point

RTH: Backing up to avoid   obstacle

RTH: Cruise

Then 6 seconds of acceleration from 0 to 16mph at 64'. Never climbed to 40m RTH Height.

Has anyone else had this problem?

I haven't.

Please upload your flight log here and paste the link and somebody will likely comment.

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

site credit:  msinger

It's hard to understand properly what the issue might be from the description.
If you touched the left joystick once the Phantom was above 20 metres while it was ascending to RTH, you would have cancelled the climb - as is described in the RTH section of the manual.
It will be easy to see if that was a factor from your flight data.

Go to http://www.phantomhelp.com/LogViewer/Upload/
Follow the instructions there to upload your flight record.
Come back and post a link to the report it provides

"RTH: Backing up to avoid obstacle"

The P3 standard has better obstacle avoidance than my P4?!

Nigel_ Posted at 2017-9-26 07:51
"RTH: Backing up to avoid obstacle"

The P3 standard has better obstacle avoidance than my P4?!

Woooah! Thought you got a P3P?  Anyway, I've noticed this anomaly as well as others in my flight logs lately. Don't think it ever got answered.

Did you double check to make sure that the settings height for return to home was adjusted as such?

Thats very curious, as the P3Standard has no obstacle avoidance.

Kneepuck Posted at 2017-9-26 10:06
Thats very curious, as the P3Standard has no obstacle avoidance.

My P3S started adding this msg to the logs after one of the recent GO App upgrades.
Seems like it's developing multiple personalities.

Palladous Posted at 2017-9-26 10:33
My P3S started adding this msg to the logs after one of the recent GO App upgrades.
Seems like it's developing multiple personalities.

I don't have any messages like this,but I also haven't updated and probably wont as long as it still fly's good. with no obstacle avoidance gear on the P3S I am inclined to think the firmware is corrupt with P4 firmware somehow at DJI. This isn't a fluke as I've seen this on many posts over the past couple weeks.

Mark The Droner Posted at 2017-9-26 05:51
I haven't.

Please upload your flight log here and paste the link and somebody will likely comment.

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

Labroides Posted at 2017-9-26 05:53
It's hard to understand properly what the issue might be from the description.
If you touched the left joystick once the Phantom was above 20 metres while it was ascending to RTH, you would have cancelled the climb - as is described in the RTH section of the manual.
It will be easy to see if that was a factor from your flight data.

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

DJI-Mark Posted at 2017-9-26 08:25
Did you double check to make sure that the settings height for return to home was adjusted as such?

I have had it set @ 40m since my first non beginner flight which was I believe # 8.
I have 23 flights

Kneepuck Posted at 2017-9-26 10:06
Thats very curious, as the P3Standard has no obstacle avoidance.

Agree.  
Here is the flight record
http://www.phantomhelp.com/LogViewer/AP5A7IDW60Y068XNRXME/

fans8a1d5757 Posted at 2017-9-26 17:10
http://www.phantomhelp.com/LogViewer/AP5A7IDW60Y068XNRXME/

Here is the flight record
http://www.phantomhelp.com/LogViewer/AP5A7IDW60Y068XNRXME/

Epicdoom Posted at 2017-9-26 16:21
I don't have any messages like this,but I also haven't updated and probably wont as long as it still fly's good. with no obstacle avoidance gear on the P3S I am inclined to think the firmware is corrupt with P4 firmware somehow at DJI. This isn't a fluke as I've seen this on many posts over the past couple weeks.

Here is the flight record
http://www.phantomhelp.com/LogViewer/AP5A7IDW60Y068XNRXME/

Palladous Posted at 2017-9-26 10:33
My P3S started adding this msg to the logs after one of the recent GO App upgrades.
Seems like it's developing multiple personalities.

Here is the flight record
http://www.phantomhelp.com/LogViewer/AP5A7IDW60Y068XNRXME/

Labroides Posted at 2017-9-26 05:53
It's hard to understand properly what the issue might be from the description.
If you touched the left joystick once the Phantom was above 20 metres while it was ascending to RTH, you would have cancelled the climb - as is described in the RTH section of the manual.
It will be easy to see if that was a factor from your flight data.

Here is the flight record
http://www.phantomhelp.com/LogViewer/AP5A7IDW60Y068XNRXME/

Mark The Droner Posted at 2017-9-26 05:51
I haven't.

Please upload your flight log here and paste the link and somebody will likely comment.

Not sure if this is working. Posting link again
http://www.phantomhelp.com/LogViewer/AP5A7IDW60Y068XNRXME/

F5 key is handy when you're not sure if you posted...

Palladous Posted at 2017-9-26 10:33
My P3S started adding this msg to the logs after one of the recent GO App upgrades.
Seems like it's developing multiple personalities.

Phantom 3 Sybil?

fans8a1d5757 Posted at 2017-9-26 17:16
Here is the flight record
http://www.phantomhelp.com/LogViewer/AP5A7IDW60Y068XNRXME/

No mystery - The flight data shows it is as I described in post #3 above.

Go to p.13 of your manual and you'll find this:  if you move the throttle stick after the aircraft rises above 65 feet (20m), the aircraft will stop ascending and immediately return to the Home Point.

Look at the flight data and you see that you pushed the left stick hard forward from 10:43.5-10:48.4
At 10:46 RTH was initiated.
The Phantom was already at 20 metres altitude, so the Phantom came home as it is programmed to.

Labroides Posted at 2017-9-26 18:09
No mystery - The flight data shows it is as I described in post #3 above.

Go to p.13 of your manual and you'll find this:  if you move the throttle stick after the aircraft rises above 65 feet (20m), the aircraft will stop ascending and immediately return to the Home Point.

Re your comment:
Look at the flight data and you see that you pushed the left stick hard forward from 10:43.5-10:48.4
At 10:46 RTH was initiated.
10m 42s        P-GPS        63.3ft       
10m 45s        P-GPS        63.3ft         
10m 45.8s                63.0ft        .
10m 46s        Go Home 63.0ft         
10m 46.1s        Go Home        63.0ft       
10m 47s        Go Home                64.0ft

Re your comment
The Phantom was already at 20 metres (65.6') altitude, so the Phantom came home as it is programmed to.
I was flying at 62.3 feet & the aircraft never rose above 64' altitude in go Home Mode @ 10m46s.... How could a left stick throttle affect the RTH 40m altitude setting if the aircraft never achieved the 65.6' altitude required from a left stick throttle to halt an RTH ascent?

fans8a1d5757 Posted at 2017-9-26 19:30
Re your comment:
Look at the flight data and you see that you pushed the left stick hard forward from 10:43.5-10:48.4
At 10:46 RTH was initiated.

Where does the flight data show that I pushed the left stick forward from 10:43.5-10:48.4? Is this a different menu?

fans8a1d5757 Posted at 2017-9-26 19:38
Where does the flight data show that I pushed the left stick forward from 10:43.5-10:48.4? Is this a different menu?

Click on the Download CSV link and you get to see all the dat including joystick info.
You were at 19.5 metres which is near enough to 20m for it to not make any difference.

The drone will not ascend if you move the throttle sticks when the drone is above 20 meters during RTH. Please leave the sticks and test again.

DJI Susan Posted at 2017-9-26 22:46
The drone will not ascend if you move the throttle sticks when the drone is above 20 meters during RTH. Please leave the sticks and test again.

would love to do this but the drone is gone. the flight record just ends with the drone heading home @ 16 mph in open water in the middle of the channel. No obstructions anywhere.

Labroides Posted at 2017-9-26 20:20
Click on the Download CSV link and you get to see all the dat including joystick info.
You were at 19.5 metres which is near enough to 20m for it to not make any difference.

Are you referring AG Column to this section  If yes it appears I back off the throttle when the RTH starts. Also: how can a P3S brake to avoid an obstacle? It doesn't have sensors, correct?
Plus the GPS map shows I am in the middle of a channel 63' over water. What obstacle?

1684                Braking to avoid obstacle                        RTH: Braking to avoid obstacle
1684                Braking to avoid obstacle        Signal Lost. Aircraft returning to Home Point               
1684                Braking to avoid obstacle                       
1665                Braking to avoid obstacle                       
1654                Braking to avoid obstacle                       
1654                Braking to avoid obstacle                       
1654                Braking to avoid obstacle                       
1654                Braking to avoid obstacle                       
1684                Braking to avoid obstacle                       
1671                Braking to avoid obstacle                       
1642                Backing up to avoid obstacle                        RTH: Backing up to avoid obstacle
1664                Backing up to avoid obstacle                       
1654                Backing up to avoid obstacle                       
1654                Backing up to avoid obstacle                       
1656                Backing up to avoid obstacle                       
1656                Backing up to avoid obstacle                       
1642                Backing up to avoid obstacle                       
1633                Backing up to avoid obstacle                       
1633                Backing up to avoid obstacle                       
1633                Backing up to avoid obstacle                       
1646                Backing up to avoid obstacle                       
1646                Backing up to avoid obstacle                       
1652                Backing up to avoid obstacle                       
1652                Backing up to avoid obstacle                       
1652                Backing up to avoid obstacle                       
1024                Backing up to avoid obstacle                       
1024                Backing up to avoid obstacle                       
1024                Backing up to avoid obstacle                       
1024                Backing up to avoid obstacle                       
1024                Backing up to avoid obstacle                       
1024                Backing up to avoid obstacle                       
1024                Backing up to avoid obstacle                       
1024                Backing up to avoid obstacle                       
1024                Backing up to avoid obstacle                       
1024                Backing up to avoid obstacle                       
1024                Backing up to avoid obstacle                       
1024                Backing up to avoid obstacle                       
1024                Backing up to avoid obstacle                       
1024                Cruise                        RTH: Cruise
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1054                Cruise                       
1054                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
984                Cruise                       
984                Cruise                       
984                Cruise                       
984                Cruise                       
984                Cruise                       
984                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       
1024                Cruise                       

fans8a1d5757 Posted at 2017-9-27 05:31
Are you referring AG Column to this section  If yes it appears I back off the throttle when the RTH starts. Also: how can a P3S brake to avoid an obstacle? It doesn't have sensors, correct?
Plus the GPS map shows I am in the middle of a channel 63' over water. What obstacle?

Are you referring AG Column to this section  If yes it appears I back off the throttle when the RTH starts.
Yes, column AG is throttle data
No, it doesn' show you backing off until well after RTH has initiated.  (1024 is the centre stick position - 1684 is full forward)
You started pushing the left stick forward at 10.43 and held it until 10:48.4.
RTH initiated in the middle of that at 10:46

Also: how can a P3S brake to avoid an obstacle? It doesn't have sensors, correct?
Plus the GPS map shows I am in the middle of a channel 63' over water. What obstacle?
Obviously it a false alarm.

If you had a P4 pro with sensors, the downward sensors only work to 10 metres but the forward looking sensors work further than that

fans8a1d5757 Posted at 2017-9-27 05:20
would love to do this but the drone is gone. the flight record just ends with the drone heading home @ 16 mph in open water in the middle of the channel. No obstructions anywhere.

did it crash into the water ? or into something on the RTH trip

fans8a1d5757 Posted at 2017-9-27 05:31
Are you referring AG Column to this section  If yes it appears I back off the throttle when the RTH starts. Also: how can a P3S brake to avoid an obstacle? It doesn't have sensors, correct?
Plus the GPS map shows I am in the middle of a channel 63' over water. What obstacle?

If you didn't get the Phantom back, here is why.
You flew behind a 33 ft high (plus tree height) point at Stage Neck and lost signal.
At 64 ft, it looks like your Phantom probably got stuck in one of those trees out on the point.

Labroides Posted at 2017-9-27 06:24
If you didn't get the Phantom back, here is why.
You flew behind a 33 ft high (plus tree height) point at Stage Neck and lost signal.
At 64 ft, it looks like your Phantom probably got stuck in one of those trees out on the point.

That would make sense. I will check with the owner of the house on the point tomorrow when I am back in Maine. Thanks for all your help on this!

Had same issue last week. Lost signal RTH came on and it didn't climb. Thank goodness you can still control the drone even in RTH mode and I made it climb before a tree took care of it.

I reviewed this again and here is the problem: we are talking about seconds on my reaction to a loss of video signal that is not shown on the flight record.  My mini pad goes dark and I get a loss of connection alert. My first reaction knowing that I am at 63 ft altitude is to climb to re-establish connection. Meanwhile within 2 seconds of that decision to save my aircraft the RTH kicks in. I have already commited to gaining altitude by moving the left stick. My screen is dark and I have no reports back from the aircraft on my iPad. During this time period which is seconds, the aircraft goes into RTH and ignores my attempt to regain altitude 2 seconds earlier. It follows its program and cancels the RTH 40m altitude directive.  Meanwhile I still have a dark screen and have no idea that RTH has been initiated.  
All flyers should take note of this issue. You have a dark screen and know your best chance is to climb. Meanwhile the quad RTH feature kicks in an cancels your command to gain altitude. Then you fly into a tree

DustMan Posted at 2017-9-27 15:16
Had same issue last week. Lost signal RTH came on and it didn't climb. Thank goodness you can still control the drone even in RTH mode and I made it climb before a tree took care of it.

My flight record show a full throttle left stick an no altitude change  RTH kicks in while I am at full throttle climb. Doesn't go up an inch!

DustMan Posted at 2017-9-27 15:16
Had same issue last week. Lost signal RTH came on and it didn't climb. Thank goodness you can still control the drone even in RTH mode and I made it climb before a tree took care of it.

My flight record show a full throttle left stick an no altitude change  RTH kicks in while I am at full throttle climb. Doesn't go up an inch!

fans8a1d5757 Posted at 2017-9-27 16:04
I reviewed this again and here is the problem: we are talking about seconds on my reaction to a loss of video signal that is not shown on the flight record.  My mini pad goes dark and I get a loss of connection alert. My first reaction knowing that I am at 63 ft altitude is to climb to re-establish connection. Meanwhile within 2 seconds of that decision to save my aircraft the RTH kicks in. I have already commited to gaining altitude by moving the left stick. My screen is dark and I have no reports back from the aircraft on my iPad. During this time period which is seconds, the aircraft goes into RTH and ignores my attempt to regain altitude 2 seconds earlier. It follows its program and cancels the RTH 40m altitude directive.  Meanwhile I still have a dark screen and have no idea that RTH has been initiated.  
All flyers should take note of this issue. You have a dark screen and know your best chance is to climb. Meanwhile the quad RTH feature kicks in an cancels your command to gain altitude. Then you fly into a tree

Flying behind obstacles that will cause you to lose signal is always very risky.
In this case the close distance to the obstacle meant the time involved between loss of signal and RTH  was very small but your joystick input was received for long enough to cancel the climb.

With later Phantoms you get programming that causes the Phantom to try retracing its path after signal loss to try to reconnect.

My joystick command was received long enough to cancel the RTH 40m climb?  If this is correct why wasn't my joystick command to climb initiated by the aircraft?   Makes no sense. The controller is telling RTH 40m altitude to cancel but it it is not telling the aircraft to climb?

fans8a1d5757 Posted at 2017-9-27 16:33
My joystick command was received long enough to cancel the RTH 40m climb?  If this is correct why wasn't my joystick command to climb initiated by the aircraft?   Makes no sense. The controller is telling RTH 40m altitude to cancel but it it is not telling the aircraft to climb?

Perhaps DJI can give you a better explanation?
If you recover the Phantom, the internal data recorder will give more info on what happened especially after loss of signal.

Look at the flight record Google maps does not show an obstacle anywhere The tree that  may have taken down my p3s is over 100m away on the point.  This entire sequence happened 63' above water after loss of signal. There was no obstacle involved before the RTH initiation.

Thanks to all for your time and comments!  Hopefully this discussion adds more to the knowledge base!