POI during Approach to Path?
Is there a way to point the drone/gimbal at a POI during the "Approach" portion of a Path component?
With a Destination component, the drone focuses on the first POI defined in the Destination while on it's way to the Destination point. An Approach mostly behaves as a Destination component, but defining a POI within the Approach doesn't seem to have any effect.
Should a defined POI within an Approach have the same effect as it does in a Destination?
If not, is there an alternate way to point the drone at a POI during the Approach part of the Path component? Once past the approach and into the Path itself, I can use Markers -- but I haven't found a way to place a Marker on the Approach segment of a Path.
Comments
5 comments
Works for me. Share example?
Ok, I figured out what I was doing wrong.
I had clicked on the "Approach" waypoint, which actually shows a list of items contained in the Path (i.e., Approach, Points of Interest, Waypoints, Markers). I was clicking on the "Points of Interest" there and defining the POI at the Path level, which has no effect.
What I needed to do.... Click on the "Approach >" to drill down into the Approach, then add the POI there. That works as it should, focusing on the POI while on the way to the Approach Destination.
Is some error checking warranted here? If a POI defined at the Path level does nothing, then perhaps adding one should elicit some kind of warning/error message (or be disallowed entirely)? Same with adding a 2nd (or successive) POI to a regular Destination component, since only the first one is acted upon (2nd and successive do nothing, as far as I can determine).
Would be nice to have (like so many other things).
I see v 2.5.0 of the web app helps with this -- by now disallowing more than (1) POI on Orbits and Destinations (including Approaches). Thanks!
That doesn't eliminate the original trap I fell into, i.e., clicking the Approach and defining the POI at the Path level, rather than inside the Approach. But probably no way around that, since a Path can legitimately have a bunch of POIs. And in fact, I've found it useful to define multiple POIs on a Path, even though the ones not associated with a Marker do nothing, because that allows a generic plan that I can quickly "customize" by updating a Marker to use one of the other pre-defined POIs just prior to running the mission.
Thanks for the update!
Exactly
Please sign in to leave a comment.