I have done many successful MME mapping jobs over various terrain and conditions, mostly at flying height of 100m and 70% overlap. The last 2 jobs have processed incomplete and all that is different is a battery change part way through the flight. Could this be affecting the processing in some way? For the second incomplete job I even increased the overlap to 80% as recommended for areas with mostly trees, but the incomplete area looks to be over the section of the first battery.
Your most recent job doesn't look it was done with Map Pilot at all or if it was, your RC connection was really bad and the aircraft barely ever took images. When this is the case you want to use Connectionless mode.
The second to last one has a completely non-overlapping section of imagery which isn't going to work.
Iniciar sesión para dejar un comentario.
The most recent job was definitely done with Map Pilot and with a minimum of 90% connection. For this job there was 156 images taken yet only 78 were processed. For the second last job 149 images were captured during the imaging run yet only 62 have been processed, none on the first battery. Is there a way of giving you access to the single photos, DropBox perhaps?
90% connection isn't actually very good for some reason. The camera triggers start to drop out around there. They definitely get dropped heavily at 87% which is where the Map Pilot starts making a beeping sound to let you know the signal is bad. Either way, you should be using the Connectionless mapping mode when there are connection issues like this. You should have seen the spacing start to get irregular in the grey dots in Map Pilot.
All of the images that were received were processed. Only 62 were included in the output because they were non-contiguous.
We do not currently offer a Dropbox import feature, only export.
I really don't think the connection is an issue in this case, I could see the aircraft the whole time and the furthest separation distance would have only been 500m, there was never any loss of connection beeping sound for any of the flights. A warning that did occur occasionally was a "photo error" and on the map display there were a few single photo "gaps" but I thought the amount of overlap would cover this? This was the only spacing in photo capture points in Map Pilot, otherwise it was all covered. I think I may have set the flying speed too high and downwind it may have been flying too fast for the card to save the photo?
Regardless of the cause, there is clearly a triggering issue going on. It can be caused by low signal strength, slow SD card write speed or a bunch of other things.
Give Connectionless mode a try as recommended before to trouble shoot the connection strength issue.
Use a slower SD card write speed in the settings to troubleshoot that.
"Photo Error" happens when the camera isn't writing the images to the SD card fast enough to keep up. You can slow the write speed down or limit the maximum speed of the flight to something the camera can support.
It turns out there was an issue with the micro SD card used in the Phantom 4.
I have since changed cards and completed 2 mapping jobs without any problems.
Thanks for the responses and suggesting alternative solutions.
