It’s clear to me that the problem is in the information you entered in your mission. Camera behavior is normal when the drone is heading to the first waypoint. However, upon reaching it, the drone makes a hovering flight (which this information is certainly included in the mission of that waypoint) and turns its camera down and keeping heading to POI 3 (which I believe is also part of the setup of the mission that was created) until the drone reaches the second waypoint. After that, you can see that the drone keeps heading to POI 3 and continues with the camera down. Only after the mission is canceled and the FPV function is chosen, the camera returns to the horizon line. Send some screenshots of the mission setup. Maybe we can identify something. Hugs.
I saw your mission. Well, I’ve never setup like you when it comes to Gimble. For each waypoint the Gimble has a configuration. Now Focus on POI and on other Disabled and also Interpolated. I can’t guarantee it, but it might solve the camera problem if you choose only one type of Gimble Pitch. If that works, try out small changes one by one. It might solve it. Try it and then let us know the result. Good luck and good flights.
Good morning Brian, I don’t know if you performed your new flight but I saw that you changed the settings of your mission about gimble pitch mode. I hope it worked. Searching the internet I found a very interesting article about Interpolate. Read on this link - Learn about the Litchi Mission Hub - Drone Photography Services - specically the part about Gimbal Pitch Mode. Let me know the results.
“For “Interpolate” to work, the previous or next waypoint need to be set to “Interpolate” as well. Litchi will then automatically adjust the gimbal pitch angle to start and end at the specified angles, and smoothly transition while travelling between the two waypoints.” https://flylitchi.com/help#waypoints-p3
Update : I flew 3 new WP missions today. No issues, which is great
Just a guess, but more than likely updating to the latest RC firmware
probably fixed my 90 degree camera issue and/or maybe reinstalling the Litchi app helped too.
I tried each of the suggestions that wesbarris suggested above
Curved turns and straight lines with photos, stop and starting recording, 5 second pauses.
No issues with either now.
Also setting the Default Gimbal Pitch Mode to ‘Disabled’ and ‘Focus POI’ .
As long as each WP was configured for Focus POI, I don’t believe the Default Gimbal Pitch mode effected the Gimbal / camera position during these 3 missions.
All 3 missions were successful.
Camera stayed focused on the POI.
Action lists were completed successfully(if configured).
Note : I did have to turn off Collision Avoidance(APAS) off before I was able to start the mission.
Error : ‘Flight Mode changed’ when I would try to start the mission with
Collision Avoidance set to ‘Bypass’.
And I was able to turn Collision Avoidance (APAS) off in the Litchi App,
and that allowed the WP mission to go into ‘Joystick’ mode and execute the mission
There was also a small bit of tilted horizon in the photos and video. But I did neglect to
do a gimbal calibration after the firmware update.
Robson/Tribar : thank you for the info on Gimbal Pitch Mode.
Very much appreciate everyone’s suggestions and help.
Hi Brian, good morning. I’m glad you found the solution. Unfortunately there was no certainty that it was the update that solved that little problem. Can you on a next mission try that old setup on the gimble pitch? It’s just an attempt to have conviction of what really solved the problem. Was it the new setup in the gimble pitch or the firmware update? Hugs.
Re-flew the shared mission.
I think this YT video proves the point that setting Default Gimbal Pitch mode
to Disabled or FocusPOI did not resolve my initial problem with the camera pointing directly down vs at the POI.
At the ~5:45 mark in the video I change Default Gimbal Pitch mode to FocusPOI and increased the flight speed. Both of these flights look identical regardless of the Default Gimbal Pitch mode setting.
IMHO - My issue was resolved due to the firmware upgrade and/or reinstalling the Litchi app.