If i create a flight to map an area with my Air3S, i need to hover at the end of flight.
The drone hovers successfully, but continues taking pictures at hoverpoint.
Any hint to stop taking pictures at the end of mapping area automatically?
Change the Photo Capture Mode to ‘Interval’. It will take photos based on distance.
1 Like
I’ll give it a try 
I changed ‘Capture Mode’ to ‘Interval’.
There were no photos taken … 
The WPML language does support both timed and distance intervals for photo capture in waypoint missions. However, the DJI Fly implementation ignores those interval parameters. As a result, for an Air 3S, you must configure either timed or distance interval photo capture manually in DJI Fly. You must also manually start capturing photos manually as the waypoint mission begins and stop capturing photos manually when the waypoint mission is completed.
When you changed the capture mode to “interval”, can we assume that was done in DJI Fly? Did you also manually capture a photo to start the interval at the beginning of the mission?
Thanks for Reply
I changed the settings only in LITCHI-HUB.
And i didn’t start taking pictures manually.
So for me, it would be easy, to create the ‘MAP-AREA’ with ‘Interval’ and i have to stop taking pictures manually.
I’m not a programmer, that understand WPML or other languages 
Here is a summary of the options I tested:
As soon as I change the photo capture mode away from ‘AUTO’, even just once by selecting ‘INTERVAL’ or ‘WAYPOINT ACTION’, the AIR3S does not stop taking photos at the final waypoint.
If I leave the setting at the default ‘AUTO’ for this function, the drone stops taking photos at the final waypoint.
When flying with DJI Fly:
- Auto is the same as Waypoint Action. The drone will end the capture at the last waypoint where a photo should be taken.
- If you choose Interval you must start the capture manually. The drone will stop capturing when you end the capture.
If the drone continues taking photos at the end, it could maybe happen if the interval between photos is too short and photos queue up and are all taken at the end
1 Like
That queue up is something i observe in missions.
If the combination of front-overlap and velocity forces a capture interval faster than what the drone can handle, the drone will just capture as fast as it can and then continue capturing “after” the mission until the image count is correct.
The real issue in that case is not the images captured at the end, but that the images captured during the mission do not have the front overlap you expect them to have. So maybe rule that out before changing modes. The Litchi Hub has a warning for this “your camera can’t handle the speed situation”, but depending on image resolution, image format and SD-card speed you can run into the issue before that warning triggers.
Something does not work, as expected in Litchi-Hub.
GSD can be calculated.
Refer to Ground Sample Distance | FARMWISSEN
For the ‘DJI Air 3S’ i have to use (wide-angle lens):
GSD = (Sensorwidth * Flightheight) / (Picturewidth * focal length)
GSD = (13,2 mm * 74,5 m) / (8192 pix * 24mm) = 0,005 m/pix = 0,5 cm/pix
But this can’t configured in Litchi-Hub?
I set Flightheight to 74,5m, the GSD switches to 2,6 cm/pix …
If i set GSD to 0,5 cm/pix, the Flighthight switches to 14,4m …
Do i have an error in understanding GSD?
The focal length you are using in your equation is the 35mm equivalent. You would need to change that to the actual focal length for the Air 3S which may be 8.7mm. It is sometimes difficult to find reliable camera specs for DJI drones.
Also, Litchi may be using the 24MP size of the camera which is 4096x3072.
You mean 12MP? 
Anyway …
If i change the focal length to 35mm and use 12MP at 74,5m hight, so the formula gives me a GSD of 0,686.
Litchi-Hub gives me a 2.61 …
Why is there this difference? Why didn’t Litchi match to official GSD-Formula?
You either use the real sensorwidth and focal length, or the 35 mm equivalent.
35mm eqiv (35 mm sensor is 36 mm wide. If shooting in 12 MP you just have 4096 px):
36 mm x 75 m / (4096 px x 24 mm)
Real values:
13.2 mm x 75 m / (4096 px * 8.7 mm)
Both should come out to about 2.5 cm GSD
Thanks for explanation.
My one error was, to take pictures in 48MP and calculate with this …
I’ll check this in nature.
The solution should take me to the right config for mapping without taking pictures after last WP.