Build 375 advertises that waypoint actions will be carried out even if ‘path mode’ is set to curved. I’ve experimented with this build and my mini 3 pro. Taking photos works most of the time. Stopping and Starting recording isn’t consistent. Sometimes the recording will stop as instructed as the waypoint is passed. But it doesn’t always then resume recording as instructed. I have tried increasing the curve radius and adding gratuitous ‘stay for’ instructions hoping to trigger the desired action.
Is curved path waypoint behavior dependent on the radius of the curve? What other settings might need to be adjusted to trigger the action reliably?
Also, when you paused and unpaused the mission, the drone turns back and then turns toward the direction of the mission. It messed up if you’re recording video. It wasn’t like that until release 375.
@William_Shelley it sounds like the camera is busy when the drone passes the waypoint, and so may be unable to start or stop recording. The camera can be busy for several reasons such as if it is taking a photo, if it just switched camera mode etc. Please do send us a link to the mission where you have this issue so we can test it ourselves as it could also be a bug (make sure the mission is public so we can see it)
For actions in a curve, the drone will not stop if there is only one action (except if it is a ‘Stay For’). The radius of the curve does not affect actions.
@Emmanuel there were indeed changes to the pause/resume function to handle the fact you can now move the drone manually out of the waypoint path and resume from anywhere. If the distance between the resume location and the pause location is less than 10m away, the drone should not turn around, it should fly backwards and then resume. More than 10m distance, then it will indeed turn towards the pause location first
Here is my short mission. It has 2 failed waypoint actions (both ‘start recording’)
Camera pre-set to video, recording not started at take off
Path mode set to ‘curved turns’
Gimbal pitch set to ‘interpolate’ at each waypoint
Finish action: RTH
Waypoint 1
expected action: start recording;
observed action: recording started
Waypoint 2
expected action: Stop recording; stay for 2 seconds; take photo; stay for 2 seconds; start recording
observed action: Stopped recording. Stayed for 2 seconds; took photo; stayed for 2 seconds; MISSING ACTION: START RECORDING
Waypoint 3
expected action: Stop recording; stay for 2 seconds; take photo; stay for 2 seconds; start recording
observed action: < previous waypoint action ‘start recording’ was not initiated>; Stayed for 2 seconds; took photo; stayed for 2 seconds; recording started
Waypoint 4
expected action: Stop recording; stay for 2 seconds; take photo; stay for 2 seconds; start recording
observed action: Stopped recording; Stayed for 2 seconds; took photo; stayed for 2 seconds; MISSING ACTION: START RECORDING
It was working as you described, when paused and resumed it was not turning around before my last updates. I’m using an M3E and I did the firmware update to 10.01.0017 and also the update for Litchi Pilot the same day. In my tests, I found out that using DJI Pilot 2 with the same imported mission used on Litchi, did the same thing of turning back while resumed. It looks like is a DJI firmware issue rather than Litchi Pilot.
@William_Shelley thank you for sharing the mission - we can reproduce and the issue will be fixed in the next beta build
@Emmanuel
The DJI engine (which you can enable in the settings) does cause the drone to turn around.
For the Litchi waypoint engine, it did not do it before but now we made changes so it behaves the same. However with the Litchi engine, if the distance between pause location and resume location is less than 10 meters, it should go backwards rather than turn around. We will double that to 20m in the next beta build.
I have issues with the new version 375 when having a fly to point wit 3 actions (pause/take photo/pause). It does it well on the first two waypoints, but then just stops and does not continue the mission.
Since I was on a comercial job, I was glad to still have Version 321 on my old phone.
Is there any way, I can get the APK of version 321 again, until the next beta release?
Thanks
Thomas
Please, when reporting an issue, make sure to share with us the faulty mission (uncheck private in the mission hub mission menu) and the drone model used.
Thanks for the quick reply! The mission is now public (Name: BS00366-Baden-Original1). I was flying it with a DJI Mini 3 Pro.
The exact same Mission works on Build 321, but not on 375.
Thanks for your effort, amazing job guys!
I have just tested that mission in the simulator within the app (long press on the flight mode top of the screen to enable simulator) and it works fine for me with Mini 3 pro. It does not stop at waypoint 3, using build 375 of the beta
Interesting, even after restarting app and drone, it did not work for like 3 tries with the real drone. I’ll give it another shot with the next update.
Thanks for testing.
I can confirm that build 380 did perfectly execute all the camera commands on a mission today. My short test mission completed without errors. It is the same mission that build 375 had trouble with.
