Popular Resources
-
<% blocks.forEach(function(block, index) { %>
-
<% if (imageHeight) { %>
<% } %>
<% if (block.name) { %><% if (block.html_url) { %> <%= block.name %> <% } else { %> <%= block.name %> <% } %>
<% } %> <% if (block.description) { %><%= block.description %>
<% } %>
<% }) %>
Comments
19 comments
I have a path that I’m blending into an orbit and I want to record in one complete take.
The drones yaw during the path into the orbit is jerky and fast and I’m aware that currently there’s not a way to really smooth this out so I did a work around by rotating the orbit starting point to line up with the path and also I have set a point of interest in the orbits approach settings to match what the paths point of interest is.
But once the orbit approach completes it then quickly yaws to the orbits center point instead of a slow smooth transition.
I noticed that you can add points of interest to an orbit but I don’t see any way of using them.
So two questions:
1) Is there a plan in the future to be able to control the yaw speed when transitioning from one component to another incase you want to record the entire mission from start to finish in one camera take.
And 2) What is the purpose of allowing points of interest in an orbit component? Points of interest only appear to be usable during the approach.
You can add a POI to an orbit if you want to look at something besides the center point. You can also add markers in the path to interpolate to a POI near the same POI that the orbit uses. Share a link to your mission plan and I can show you.
Could you make a simple mission with an orbit and a poi? The one I have is a mess I’m starting over. I just downloaded it yesterday. I can make another.
How about this:
https://app.dronelink.com/dronelink/demo/plan/ARUunqC0QeYqUVdltbyO
Well this is odd. I went in and made a basic Orbit with a POI and THAT worked.
But when I add one to my other mission is does not work
The problem mission is in a private repository so I am not sure if i can share it.
I took some snapshots though:
POI added to Orbit component:
the preview shows that the orbit is not locked onto the POI:
I deleted the Orbit heading and that looks like it resolved the issue.
Heading takes precedence over the POI if you provide it.
I didn't provide one at first and thought POI wasn't working but i DID alter the heading after I changed the direction to counterclockwise because that changed the heading to point outworks instead of inwards..
I'm a total newb here though so who knows.
The only other issue now is I wanted to be able to smooth out the transition from he path to the orbit when the drone does the yaw to the next POI.
*awesome app BTW and surprised how fast you got Mini support in the app store!... I'm a developer and it took weeks get get apple to approve my apps, have they sped that process up or what?
You can see a smooth transition in the example mission plan I sent.
Apple added more resources to their review team a few years ago and it usually takes about a day now.
I'll have look. I just ran my first test mission. I guess it's a bad idea to have DJI Fly also running.
I see, you have a marker at the end of the path that points to the orbits POI
If you look a little closer you will see there are actually two POIs right on top of each other, one at the end of the path and one for the orbit.
I did try zooming in. I zoomed as far in as I could but could not see the 2nd path POI. It’s too perfectly on top of the orbits POI. But I figured that’s what you were doing. I did the same.
I was able to get the transitioning pretty smooth. The only other issue I had was when I added a marker to my path to do the yaw over to the orbits POI area the yaw was going clockwise and needed to go counterclockwise to make everything smooth. I resolved this by adding one more marker to the path a little earlier then set the heading to 45 degrees. This got the yaw going in the correct orientation and then it hit the next marker and headed to the POI properly.
Not sure if this was the right way to do it but it worked.
If it gets the shot you want, it is the right way :)
when transitioning from the path to the orbit is there a way to get it to not slow to a stop before starting the orbit so its one complete smooth transition? can I adjust the deceleration / acceleration curves between the two components?
Not right now. You might want to consider just using a path with curved waypoints and making the Orbit "by hand". You can leave the Orbit in there while you put waypoints down as a reference. We may even create a macro like Autopilot where it places waypoints for you to get a perfect circle. In fact this could already be done with a function.
That’s exactly what I did after I killed the other flight plan. It’s much better now. Also on the markers I changed the interpolation to curved. I think that adds an ease in and ease out to the yaw if I understand it correctly.
Yep, and you can change the curve if you expand the advanced settings.
Yeah I haven't been messing around with that. I haven't noticed much of a difference when sliding the curve slider yet but yeah I figured it was the acceleration / deceleration (easing / ease out).
Please sign in to leave a comment.