i realized that i don't have enough skill to do the piloting and filming things at the same time. thats why i need waypoints feature to help me out, and then i only need to focus on the camera heading when the waypoint mission being accomplished.
first try, i made a very simple scenario with 3 waypoints. 1st starting point at 20m altitude, moving to 2nd point about 30m away from the 1st one and at lowest alt allowed by the go.app. the 2nd point was successfully recorded at about few inches above my head. then i move it to the 3rd (last point) straight away about 40m from the 2nd point at 20m alt. we can imagine how the path i created as a straight line with altitude variation.
then i started the mission, and i was expecting to arrange the camera heading to my self standing near to 2nd point.
but i watched the phantom movement doesn't seem to correctly follow the altitude i have designed before. i am pretty sure the lowest altitude (2nd point) was recorded few inches above my head under the electric powerline. but this is what happened.....
only few inches above the powerlines which i measured about 6-7meters above the ground level. that was really close to crash....
so, my conclusion is, this feature has very wide margin of error, my be due to the GPS calculation at the current time. as same as what happened when we try it to automatic RTH+landing after we fly it some distance from the home point. we can see the telemetries also not accurately reported as the actual situation.
so, give the phantom some space (above 5meters) to anything (obstacles) when we design the path of the waypoints.
Sent from my SCL23 using
PhantomPilots mobile app