Transitions between Path Actions?
Very basic question re. transitions from one Path Action to another...
For example, I want to start a mission with a POI at a specific location and maintain that POI up to the next Waypoint, then beyond that Waypoint, transition to a new POI. Unless I'm missing something I need to add the second Path Action pointing the same POI as shown here in this quick sample, then a 3rd Path Action pointing to the new POI?
So in general, if I have two Path Actions setting a particular value, once the flight passes the 1st Action, it immediately starts to transition to the 2nd?
https://app.dronelink.com/tim-b/mh-paths/plan/VdFe7qQ4aR1ssIaj7FPi/CTfjvfdfcH5PWRuCVb3v
Comments
15 comments
Generally I like to keep path actions as explicit path actions rather than embed the action in a waypoint as you have done for waypoints A and B then the added the 3rd command as an explicit path action. I think it just keeps the plan more simple when waypoints are basically GPS coordinates and all other commands are path actions.
As for transitions, just experiment until you learn the details. That's what I did to learn that a point of interest will begin the transition to the next point of interest as soon as it passes the first command IF there are no other path actions separating the 2 POI commends. If you add a path action after a POI path action at the point you want the POI stop its rotation it will hold the first rotation until that marker/path action command. Just add a path action with some specific drone heading. The next POI command will then start only when it reaches the command. When you want the POI to cease just add another path action heading.
Try it with you plan by adding explicit path actions between the POI commands. Experiment with different headings. Also keep transitions as curves rather than straight line.
I belive its made like that for smooth transition. If it started rotating at your last path, your mission will be over before it gets there or transition would be too fast so you wouldnt be able to see anything.
This is how i do it:
https://app.dronelink.com/dejan/public/plan/6hHuy2MF8q4C2B9HpOtc/jDfZ4JD7U49PMlekZnXd
You must find some middle spot for another path action(so you use 2 per POI)
Maybe someone has better advice. But i had same troubles when i was making first mission :)
I can see you plan but maybe you could explain what you WANT to happen at each point along the path. How long do you want the drone the maintain it's POI focus and when you you really want the drone to lock onto the next POI. It's hard to make a suggestion without know exactly what you want to happen. Just explain it in words.
you can also change the way that the drone changes from one heading to another by changing the rotation mode:
Lots of helpful input-- thanks!
Somewhere along the line that initial link got messed up. Below is another try with no particular location but just a path to demonstrate what I'm asking about. Hopefully this makes sense...
Start with a Waypoint POI at A.
Stay focused on A until toward the end of the mission, then switch focus to a 2nd POI but rather than transitioning to that 2nd POI as soon as the first POI is passed, stay focused on the initial POI until a point determined by the position of that 2nd Path Action with a new POI. Stay focused on that POI until the end.
Here I've overlaid POI B on top of A to accomplish that. Seems to work as I want in preview but not sure it's the best method.
https://app.dronelink.com/tim-b/mh-paths/plan/XQD3qgmwGbIh7Zkq9aUn/oPwycJM3n5u7Xe9TOyZY
I'll take Dave's suggestion going forward:
Martin's suggestion:
Also sounds good but will require some additional learning on my part given I've never paid much attention to Rotation Mode! One step at a time I guess... :-)
Ok had a play, and tweaked it a bit, so this is what I've done:
https://app.dronelink.com/martin-reading/beta-4/plan/cF4K2ANkKfGSmeGRCMbn/kT6yMIlzd6iAQYpzO6L9
That's what I assumed you wanted to happen--maintain a POI. So, I eliminated Path Action (PA) 2 and unlinked POI
B. Then, a short distance before what is now PA 1 (to POI C) add a new PA and set the drone heading to 45° to path. This will start the drone heading to match what will be needed for POI C. When it gets to the new PA 2 (POI C) It will gradually lock onto the POI until the end.
In settings you can control how fast the drone rotates.
Martin/David,
Very interesting. From what I had thought was a very basic question, I've actually learned a number of things.
There's obviously often more than one way to accomplish your objective. For example, having PA3 point to the same POI used in PA2 simply by selecting it on the drop down. No need to overlay a 2nd POI as I had done.
Adding a new PA to set the drone heading and maintain focus, and the ability to set how fast the drone rotates-- did not see that as an option before but good to know.
Thanks much for the input!
Tim B, you're welcome
Yep, that's the great thing about forums like this, folk pass their knowledge on happily, I think its how most of us have learnt, by asking questions here.
Yes on many things, there's more than one way to achieve the same result, I mean I can think of at least 3 ways to achieve continuous capture on a multiple component plan
Barry Houldsworth, posted a FMF video on this subject in another thread
https://vimeo.com/514729532
Thanks, Martin. I actually meant to post it in this thread but...messed it up.
Hopefully it helps :)
Barry Houldsworth
Yep I actually have watched that video. Just watched again to refresh my memory. Good info.
Question: I've set up some missions previously where I had to go back and change the transition from Linear to Smooth. Wondering why Linear is the default for the Waypoint missions? Under what circumstances would Linear or even None be preferable?
I guessed as much ;)
Hey Tim. Your question: “Under what circumstances would Linear or even None be preferable? “
It Depends on the plan and the pilots preference. In Some situations you may not want the component to to start until it arrives at the marker or waypoint. Otherwise the component will start interpolating a ways back on the path. An Example is if you want a path to fly over a 100’ tall building at 185’ altitude and drop down to 50’ you may not want it to descend until you get to the desired location. If it’s set to linear or curved it will start descending along the path and may crash into the building. Many other examples but if it was defaulted to either of them you would still need to change for other situations.
Ah, I did not realize that. I'm pretty sure crashing into a building could indeed ruin one's day. :-)
I'll do some simple tests to actually see the difference between the various options and add that my personal KB.
Thanks Mike.
Please sign in to leave a comment.