I reported this issue on this forum weeks ago with my 8k
Evo 2. Same problem as yours, as soon as it passes a waypoint it changes direction to face south and film south NO MATTER WHAT I PRGAMME THE WAYPOINT to do. This has ONLY started happening since the latest firmware update and again after much research on here it is now not possible to roll back.
After 4 week of waiting for Autel to come back to me they said:
"Hello Steve,
Thank you for your patience.
Today, I have received a response from our repair team after reviewing your video and your concern. Please find the attached file below. The resolution provided is to "please set the yaw angle for each waypoint in the waypoint task. The user needs to set the yaw angle in the action option when editing each waypoint."
Let me know if you have any more questions, comments, or concerns. Feel free to contact us at
[email protected] or you can check our website at
Store | Autel Robotics for more information.
Best Regards,
Gian
Customer Support
www.autelrobotics.com
WELL THAT WAS FUC*ING USELESS!!!!!! My response:
"That is no help at all.
I know all about changing camera angles and actions at each waypoint through the waypoint settings.
I have now found out that when I have entered all my waypoints in and finished setting up my mission I need to go back into the overall mission settings screen and change the heading from custom to route. If I don't do this the drone points and films south after each waypoint.
You have also not solved the other problem I reported when flying in missions the video starts and stops recording at each waypoint. Again I have found a workaround where I press record AFTER waypoint 2 it records the whole mission in one video (sometimes but not always). If I don't manually stop and start recording myself after waypoint 2 it records each waypoint journey as a separate video file, so if i have 40 waypoints it will have 40 videos. I am a member on the Autel Forum where several other users tell me they have this same problem too.
None of the above happened until I upgraded the firmware.