wait command ignored or not working in markers
Hi,
I must say I found this in the dronelink webapp did not test it yet with the native app on a real mission. But this is what I found:
Situation: take off and fly to the start destination of a curved path. Set heading and gimbal pitch and start recording video.. Half way on the path is a marker. I created a component list as a marker parameter to wait for 20 seconds. That should give me a videoshot where the drone is stopped moving. Then it will speed up again and finishes the path.
In the simulated flight the wait command at the marker is completely ignored. It won't matter to remove the list and put the wait command directly as a component in the marker. In both situations the wait is ignored.
BTW flying the mission on Google Earth gives the same result.
Ruud
Comments
6 comments
This is by design. The wait component is intended to be used between components. For example, if you had a list of camera commands, with a wait between two of the commands, it would wait between those camera commands. The only time the wait component will affect flight motions is when you put it between two other motion components, such as a path and an orbit. In your case, I suggest you terminate your path and do whatever you want at that point, and then add another path component to keep going.
Hello Jim,
I guess this is still the case today. "Wait" command is effective only between 2 components ?
Would hope that an update taking into account "wait" during a path came into picture since that time.
Is there a reason the proposed solution (creating two paths) is not acceptable?
None.
It is just that for my first attempt I did the same as Ruud by adding a Marker. I estimated it was more "natural". As it did not work, I found this thread.
The workaround is to split the path to add the wait command in between. Right.
Maybe to be improved with low priority on DL side. Not sure it is that difficult to implement for you.
I would like to add a wait to allow the rotation of the yaw and the gimbal to end before starting the movement between WP "A" and WP "B"
video:
https://youtu.be/mb-AvzqEK90
You need to terminate your path and add a rotation component to accomplish this.
Please sign in to leave a comment.