Brief period of missing images during a mapping, what should I check?
Ok, brief details here - flying with Mavic 2 Pro, and flying a pretty good sized mapping mission with numerous battery changes. I found that there were several places I had to create a new mission and re-fly it to get the coverage on those spots. I was not dealing with wind or anything like that.
I had just noticed that the drone was flying the course, but not firing the camera briefly. It started again on it's own. A few minutes later, I did get a "telemetry delayed" which I understand is a signal interference related issue of virtual joystick. Is the region where pictures not being taken perhaps due to signal issue?
Looking for all advice or guidance you can give on making quality mapping missions where this does not happen. Specifically, if the element is marked as "required" shouldn't Dronelink make sure the file is created at each place expected on the mission? Thanks for any thoughts. I am relatively new to using Dronelink for mapping scenarios.
Comments
6 comments
Hi Tony. If you can share the plan it may help them to check it and test. I don’t do mapping but they may want a look at it.
There was really only the one component, so not very interesting to look at. Map. Standard grid, even shaped like a rectangle, and no funky commands or settings. During a stretch of one of the legs, the camera just stopped shooting...but mission did not stop or fail. It just failed to capture images. Then later on, six or seven minutes later, did get the telemetry message I reported.
If the element is marked as required then it should capture or give an error if not. Was the capture mode set to time or distance?
Do you have Verify File Created enabled?
Barry Houldsworth I had it set to required. Capture priority was set to distance, which admittedly I left at default, and now that I have researched the meaning, probably should have been time.
Jim McAndrew Verify File Created was enabled, and Required were checked.
As @Mike suggeted, here is the mission in my public repo.
https://app.dronelink.com/southwestern-aerial-studios/tsimek-public/plan/e7AWWZSHXaL9FAAzGtwy
So flew a similiarly sized mission today and had no such issue, so my feeling is that it may have been something introduced by a signal issue. Not really worried about it, although I think as a best practice, I am going to compare the expected file count from the simulation of the mission with the actual file count produced.
Please sign in to leave a comment.