Sakumar's post had nothing to do with meters. You were replying to the wrong post. Sakumar's post actually makes sense, relating to possibly not handling negative numbers correctly. Bigbells is the poster mistakenly thinking it was related to meters v. feet.
No it only shows 0 because I wasn't connected to the craft. If I connect my altitude max is set to 500 and RTH I set based on what is around me. (Always set higher than objects)
Except the DJI GO 4 app has absolutely no way of measuring AGL! The FAA 400 foot height limit is Above Ground Level. They don't care what your height above your launch site is when you are flying up a hillside! Conversely, if you are flying over descending ground level below your launch site, you may have to enter into negative values to remain under 400 feet AGL below the aircraft! You cannot rely upon the displayed elevation in the app to remain in compliance with the FAA 400 foot AGL. As the Pilot in Command, you must know the topography of the area you are flying over and stay within 400 feet above the ground below it, and not your launch site!
Good point. Pretty much a contract of adhesion entered into under duress, if you ask me! You need to fly up a hill more than 400 feet higher than your launch point with your new $1500+ investment, so you have to agree that DJI is not responsible, in any way, even though you have no understanding of what you are agreeing to, and that DJI's app does not display AGL!
It is an acknowledged bug. It has nothing to do with an incorrect RTH setting. If you are flying above the height set in RTH, it keeps ascending before it returns home.
That sure sounded logical, until I checked my settings and saw that I have max altitude set at 120 meters. So, that doesn't explain why my bird elevates to over 500' during RTH.
It does. As stated. It's a known bug. The craft will climb during RTH and will exceed/ignore both your RTH set height and will also exceed the max limit height you may have set. DJI is working to fix it.
Well, that's different than what GadgetGuy said. He said that it would rise to the maximum altitude setting entered by the user.
DJI knows why there is a bug. It's caused by the software thinking that the bottom sensors are telling it go to up over an object. This is what was told to me by a DJI rep, passed on by the DJI engineers. I assisted them in testing a few scenarios and providing DAT files to help nail the problem down. I'm not sure why you think there is "no indication that's true" regarding the OA? I've already posted all of this information in the thread multiple times. I am unsure why confusion remains on the issue. The bug occurs in very specific RTH situations, and ignores the preset RTH height as well as max flight height.
Because the screen data shown in the video I posted in post #1 does not show that the aircraft is perceiving any obstacle in any direction, as the aircraft rises uncommanded from 398 to 538 feet.
