Approach vs Component Altitude
I may be missing something but is there a way to change the approach altitude of a component while keeping the component altitude at a different height? We regularly are mapping areas and fly a large overpass at around 300-400ft and then have a smaller area we do a grid and map at 100-150ft. When testing I found that if I change the approach altitude it automatically changes the component altitude. Ideally it would be great to do my large pass at 300-400ft, then move to the new grid location then drop to the 100-150ft height and start that project. I have been able to get around this by adding in a path component in between the two maps, but just wanted to see if there was a better way to do this, or if I was missing something?
Thanks
Comments
11 comments
Just use another destination component in between the maps, much easier than a path.
Awesome thanks. We are two days into testing the software and other than one crashed Mavic Pro 2 that was 100% our fault when setting things up we are loving it. One other question you might be able to answer. We created a massive map yesterday, it covered around 115ac, we had issues getting it to load onto our ipads. When we opened the mission is would allow us to start the project, but it just started to fly off somewhere, literally just headed out towards the approach area but kept going luckily we were able to cancel the project before the drone flew too far off course. We then noticed that in the smaller PIP screen the map didnt show any of the paths. Is this because the project was too large? It was going to be a 5-6 battery run, so not horrible, just wanted to know why this might have happened.
Can you share the mission plan?
I already got rid of the plan from yesterday unfortunately, but I did create a new one around the same size near our office. Not sure how to share, but I did make the repository the flight path is in public and named it REDLINE, not sure if thats how you do it or not. This is about the same size as the one we wanted to test yesterday and we couldn't get it to load on a iPad mini 5, iphone XS Max or iPhone 11 Pro. The scary thing that it allowed us to proceed with the flight then just started to fly past the approach destination is was suppose to turn around at.
Creating a public repo is one way. If the mission plan is in a public repo you can just copy and paste the link in your address bar here.
Another way (if the mission plan is in a private repo), is to click this button:
https://app.dronelink.com/david-mcnamara/flights/plan/x7yLok4UiRvHsaoT4X3w/4w3e7hqYPEV6v0mXKR0Y
Here you go. This is about the largest size mission we would ever fly. We wanted to see how well it worked since we have always had issues with Pix4D and multi battery flights. Sometimes it would resume sometimes not. To be safe we usually create multiple flights, but that had been such a pain since we have had people move the path over too much and miss an area.
Actually this is almost the exact flight plan we created yesterday. Two map areas, one large overpass and one smaller grid in the middle lower to the ground.
https://app.dronelink.com/david-mcnamara/flights/plan/jISOIbNxF3Hl5SneZwUQ/D1yoZQu5rwEvZSkNmE35
We are going to have to make some optimizations to support plans that large. What type of device are you trying to run this on?
Our normal flights are done with Mavic 2 Pros and a iPad Mini 5 at the moment. If larger flights like this can work I dont see any reason why we will not be able to pitch this as our new go to for flights and ditch Pix4D.
Team sharing flights alone is a game changer for our work flow. Once it stops raining here in NC we will be testing that out as well as multi battery flights. As long as it works we will be reaching out for either a few Teams licenses or even a Enterprise license.
Sounds good. The next minor release (1.2.0) is focused on some new functionality to enable real-time mission planning, and the next patch version (1.2.1) will probably include some optimizations like this one needed for large missions.
I messed around a little yesterday and it looks like we can create smaller area flights that last 2-3 hours and load them to our devices just fine. I then created another 15+ac run and it didnt load like before. Just wanted to let you know.
Please sign in to leave a comment.