hyperlapse waypoint mission not working

[rormac]

hi all.
please help.
i programmed and saved a hyperlapse waypoint mission with my OG mavic 3.
my plan is a time lapse over a few months of a building site. first run was perfect on the day.
the next time i went back to site and loaded the mission and hit play the drone went to first waypoint but the altitude was completely incorrect and point was not the exact same...
what could the issue be?

 

[DJ Wes]

This appears to be a known issue. However, it may not be known by DJI, who have not provided a fix. See this thread:

K

Altitude not repeating on saved hyperlapse waypoint mission - Air 3

Feb 15, 2024

I need help regarding altitude on a saved hyperlapse waypoint mission.

Today I wanted to fly 3 missions back to back to back changing only the interval on a saved mission to see how it affected the result.

First battery: I flew to first waypoint at 300 feet, selected it and made all camera selections for exposure, gimbal, etc. and then flew to second waypoint, also at 300 feet and made all selections. I set interval and video length and then saved the mission to the library. I flew back to the homepoint, landed and changed to a fully charged battery.

Second battery: After changing to...

• KenG
• Replies: 28
• Forum: General Discussions

I have worked with the hyperlapse data (in JSON format) from DJI Fly drones. It would be interesting for you to export one of the JSON files from the hyperlapse folder on your flying device and examine its contents. You will need to run the JSON file through a JSON formatter (search the web for this) and look at the "height" and "altitude" values (always in meters).

Here is an example of a portion of a JSON hyperlapse mission:

{
"index": 1747007499241,
"px": 25.863846,
"py": -82.58746,
"pz": -162.21922,
"height": 16.660797,
"gimbal_pitch": -3.4,
"gimbal_roll": 0,
"gimbal_yaw": -63.008133,
"longitude": -1.3876699869292957,
"latitude": 0.7782552034686965,
"altitude": 231.22551,
"traj_id": 0
},

I have found that the "height" value appears to be the waypoint height in meters above take-off. There is also an "altitude" value. I don't know why they need two height/altitude values. The "altitude" was close to the MSL of the waypoint in my research. It would be interesting to hear how the values in your JSON hyperlapse mission compare to your original height.