I have posted the same question at the arduplane forum, but got no reply. So maybe this is a mission planner problem.
We recently got into trouble flying a mapping mission where we are loosing pictures and Emlid events.
I suspect the reason being that at the end of a leg, an un-planned camera trigger is generated extremely fast after the last planned trigger.
The mission seems to generates a camera trigger which is much shorter as the planned distance. It looks like the camera is being triggered at the end of each leg, regardless where the previous trigger took place.
Since we are flying with 65% overlap, the triggers already are close to the limit that the camera and the Emlid can handle. The camera needs about 600ms to process the previous picture, Emlid needs almost 1 second to record the event.
So in this case, we start to loose pictures and/or events during this mission.
I checked if there is an option in mission planner to disable this behavior, but I can’t find it (or it doesn’t exist).
So my guess is that Arduplane generates this trigger automatically.
- Is it possible to disable this behavior?
- Am I doing something wrong while planning?
- How to solve this issue?