https://www.phantomhelp.com/logviewer/4DLIDQO7B89BCF8XX5XP/

So I went out for a drive today and decided to whip out the MA2. All was going quite well for most of the flight regardless of the altitude ASL. However, around 11:20 into the flight, there was an error given in the log but not on the screen:

Current elevation above 9515ft. Fly with caution (Code: 30152).



The error happens again between 12:00 and 12:34 in the flight. All the errors were followed by the drone doing a hard stop and hover while I kept pushing the stick forward.

Am I correct in assuming the stopping was a failsafe due to the altitude?

I did get a few nice pictures though:

Am I correct in assuming the stopping was a failsafe due to the altitude?
It's not a failsafe.
Your drone has a service ceiling of 5000 metres (16400 ft) and it was far short of that altitude.

The message is an uncommon one and from the times it's been reported by flyers, it seems to be a nonsense false alarm.
It has been seen at low altitudes as well as high.

Splendid shots.  

Hello there, blue_canyon21. We really appreciate you for sharing these incredible shots that you had taken. Can you please confirm if you have captured a screenshot with the said error message? Kindly please try to fly to a different location and check whether the issue persists. Please keep us posted. Thank you.

Splendid views in any case.

Labroides Posted at 7-15 23:03
Am I correct in assuming the stopping was a failsafe due to the altitude?
It's not a failsafe.
Your drone has a service ceiling of 5000 metres (16400 ft) and it was far short of that altitude.

Yeah, I figured it was a nonsense error. But what would have caused the stop and hover response?

DJI Paladin Posted at 7-16 04:28
Hello there, blue_canyon21. We really appreciate you for sharing these incredible shots that you had taken. Can you please confirm if you have captured a screenshot with the said error message? Kindly please try to fly to a different location and check whether the issue persists. Please keep us posted. Thank you.

As mentioned in the post, there wasn't anything to screenshot. I only found the error message while analyzing the log to find out about the stop and hover behavior.

blue_canyon21 Posted at 7-16 05:28
Yeah, I figured it was a nonsense error. But what would have caused the stop and hover response?

The drone had been flying along at around 25 mph, with the right stick full forward.
At 11:20.0 the pitch angle suddenly went from around -20° to +50°.
This has the effect of slamming on the brakes and stops the drone dead in 1.6 seconds.
This is obstacle avoidance at work and given where the drone was, it's likely that the obstacle the drone avoided was the sun.

It would have been unrelated to the altitude notification message seen earlier.

Labroides Posted at 7-16 05:45
The drone had been flying along at around 25 mph, with the right stick full forward.
At 11:20.0 the pitch angle suddenly went from around -20° to +50°.
This has the effect of slamming on the brakes and stops the drone dead in 1.6 seconds.

Interesting.

That does make sense.

Hi,

Had a look at your log.

Pushing stick forward and your drone to stop hard ; Obstacle braking....
Guess Flying into direct sun light in APAS mode = false readings of obstacles.

See my chart of your data.

cheers
JJB