Posting

2 pengikut Ikuti
0
Avatar

Flights taking too long due to lighting

I was using Map Pilot to do a survey over a 20ha area. The flight plan details specified that it would require 2 batteries and take 17min on the left panel. I ended up using 3.5 batteries to complete the mission which took around an hour to do. Is there something I'm not doing correctly that causes it to do this? How do I get more accurate mission details before going flying.

Secondly, I was flying in the evening so at the start of the flight there were shadows on the ground from the surrounding trees so the exposure was relatively low, towards the end of the flight and on a brand new battery I got a message saying something to the effect that there was an error in compensating for the ground speed. The drone thus raced through and completed the rest of the mission at around 12m/s with a ground blur of 100cm. The last few images are unusable from the blur. What I would like to know from this:

1) What caused this to happen? My guess is something to do with the exposure but shouldn't this be accommodated for?
2) How can I prevent this from happening in the future?
3) Is there any way to perform a section of a mission to re-capture the blurry images rather than doing the entire flight again?

I look forward to your response.

Adam

Komentar resmi

Avatar

Sorry to hear you experienced an issue with Map Pilot. The time estimates the app makes are purely based on distance and the anticipated speed. If the actually speed of the flight is lower due to lighting conditions it can certainly take longer. The only way to ensure the this extension of the flight time won't happen is to make sure you are collecting your data in the brightest conditions possible. We never recommend mapping anywhere near sunset as the shadows are changing far too rapidly to create usable results.

If you don't want the app to make the decisions for you that capability can be turned off in the settings menu.

The error you received was likely due to it trying to set the adjusted speed to a value outside the valid range where 2 m/s is the minimum possible flight speed and it defaulted back to its overlap and camera framing speed based speed. This certainly isn't ideal, but if the light conditions were that dark it wasn't going to be able to fly slow enough to capture the data properly anyway.

It can be possible to go back and capture data for a missed region and add it to the rest of the data if it is taken when the sun is high but when there are long shadows this tends not to work out as well. You will likely need to retake the full data set in order to process it all as one job.

Jay
Tindakan komentar Permalink

Harap masuk untuk memberikan komentar.

1 komentar