Air 2S Spinning

Hmmm. We will give that a look.

It could just be a bad compass calibration. I really doubt the flight stuff would have anything to do with the inherit setting. 

It sounds like you changed the battery and the inherit setting at the same time. Could it be an issue with that battery? Check the firmware version on that. We have had a lot of people having issues with battery firmwares lately.

The problem with the inherit setting is that you can't really just choose any settings you want and have it work. It really is better to have Map Pilot Pro manage it for you. 

Since you turned the inherit setting off, Map Pilot Pro was setting the exposure for you, either auto or by your manual setting in the app. The motion blur number is calculated by looking at the current exposure value and the current aircraft speed. 

Thank you for your step by step. We will give it a look. It certainly sounds like something weird is going on there. 

It happened with 2 different batteries, including the one I used without issue yesterday. I'll check the firmware though, I didn't realize that the battery firmware was updatable too.

Regarding the camera settings, I was trying to fix 100 ISO and 1000 shutter, but I could see on the screen when it was taking the pic it was changing it, and they blur number going red. If I can't keep the motion blur within a reasonable number, not sure this will work for me. Maybe you can see something in the logs or point me somewhere to a help page that can resolve that issue for me?

Sometimes you can't trust the exposure numbers that get reported by the SDK. It gets weird when it changes sometimes. The only real way to verify is to check the exposure numbers in the image tag. 1/1000 exposure is 1 millisecond. There is not going to be much smear going on at 1 ms. The aircraft's maximum speed while doing automated flight is 15 m/s. At that speed for 1 ms exposure time you would be looking at 1.5 cm of ground smear. Unless you are flying really low that isn't going to matter much and if you are flying that low you likely aren't flying at 15 m/s. 

The camera preview panel is not going to be using 1/1000 because the image would likely be very dark unless you are operating somewhere extremely bright. 

I checked the EXIF for the photos and it looks like most were taken at 1/1000 or faster, though a few did come in a little slower, so that's not an issue, and flight speed looks to be 4.66m/s, which seems slow to me, but I guess the blur turning red on the screen isn't accurate. Question about reading the log/csv, the notes field says Photo then about 16 lines later gives the photo file name. Which one of those lines is the actual photo taken?

Regarding the spinning, I'll recalibrate the compass and make sure all the firmware is up to date, but it seems more like it was a virtual stick issue. I hope you can figure it out.

If you are flying low the speed of the aircraft is going to be limited by the overlap you have selected and the camera's SD card write speed value you have selected in the Settings. It is also possible the speed is being limited due to the amount of available light. You can read more about this here:

https://support.dronesmadeeasy.com/hc/en-us/articles/211398963-Determining-the-Flight-Speed

Where it says 'Photo' in the log file is when the camera is triggered. The filename that happens after that photo mark is where the file eventually got written to. It being 16 lines later is a bit slow. Usually this is around 10 lines (1 second). You may want to format your SD card or look into using a faster card because this slow write speed will be somewhat limiting. 

Interesting. I'll try and reformat the card. It's a new SanDisk Extreme (UHS-1 U3 / V30) A2 128GB MicroSD with 90MB/s write speed, which is the fastest I've found.

Test it with the intervalometer in the DJI app for a few minutes. Set it to 5 minutes taking a picture every 2 seconds and make sure you get 150 images. 

Many of us with similar problems flying AIR 2S with MPP, but the problem is always our drones/equipments... 

EDIT: As soon as possible I will record my screen flying AIR 2S with MPP in a sunny day and I`ll share the video.

Mauricio: We looked at your account and saw nothing but perfect flights. If you have a specific issue please make sure it is synced so we can see what is going on like Scott did.

And yes, it is frequently a hardware issue that causes problems. There are thousands of flights executed with that aircraft every day that do not have any issues. There are lots of variables that are aircraft and location specific that must be contended with and corrected for before we can ignore the thousands of other flights go off without a hitch and blame something in the software. 

There are 151 photos at 5 min, probably because I started the timer at the first photo and it took one at the 5 min mark, so 2 seconds per photo isn't an issue. It's just odd that it's taking ~16 lines instead of 10, but it's probably not an issue since it can still get to the next photo in time.

I did see a few other threads on here regarding the spinning issue, but decided to start my own since they were a little older and I had another question. Raining here today, so I probably can't test again for a while.

Zane, 

When I was flying these "perfect flights":

1) The screen with the drone camera was frozen with the last image taken. After a while (2 min) it was updated by the next image. I couldnt see the video streaming, like usual;

2) The motion blur values jumps to red and returns to green frequently (Inherit Camera Settings - Disabled);

3) I set the Speed to 10 m/s, but the drone couldnt fly at this speed, probably braked by the high motion blur values;

The weather was clear and sunny in all flights.

Samsung A54 256GB (8 GB RAM).

SD card: new Samsung EVO plus 128GB

Scott: The issues you are having are different than what others have reported. We can tell that from your log files. For the imaging, as long as images aren't getting dropped it should be OK. 

Mauricio: 1. This is likely caused by having not enough system resources available. Try closing all other apps when running Map Pilot Pro. Also, make sure the device is nice and cool. It is good that the flight continue successfully. 2. This was discussed previously in this thread. The Motion Blur number is derived from the exposure time and the speed. If there is a jump in the exposure due to lighter or darker scenes it can cause that value to change. All that really matters is the exposure times of the images themselves. 3. Also addressed previously. There are lots of things that affect the speed. https://support.dronesmadeeasy.com/hc/en-us/articles/211398963-Determining-the-Flight-Speed

We still don't see any log files that show the spinning issue you are pressing about. Make sure those are synched so we can see what is causing them. 

The color options for the Motion Blur readout are white, red or yellow. There is no green readout. 

Since DJI hasn't updated the iOS SDK in a few years but has continued to update the firmware there are likely small incompatibilities. One of them that we know about is how the exposure readout has unsupported values in it now that get returned as UNKNOWN. This causes Map Pilot Pro to return a default exposure time of 1/100. With that happening it will make the Motion Blur number get calculated as the same value as your flight speed. So if you are flying at 9.9 m/s it will report a ground smear of 9.9 cm/pixel.

If your firmware is newer that the latest version listed below that would be the issue. 

From https://developer.dji.com/document/2c6f3a26-412e-45d2-a312-eb82e72411e7

We will try to account for that case if we can but there are likely other weirdnesses that are going to pop up if you are using the latest firmwares. 

There have been 2 firmware updates since that one. I'm on the current 02.04.27.00 Annoying they haven't updated the SDK to account, but maybe the updates don't affect the SDK, but then again they should update the supported firmware to the current value? 

I was able to fly a mission today and it flew with no problems, so it seems intermittent, which I'm sure as a developer makes troubleshooting more difficult. Hopefully the logs will show where things went wrong and allow a fix to be rolled out. The GSD did turn red at every photo, but checking the log it was consistently 0.4 which is expected, so I'll just ignore that going forward. Shutter speed and ISO of the pics was great as well. Still showing 15-16 rows to save the photo, but that's still withing the 2 second shot timing.

DJI stopped supporting iOS for 3rd party developers about 3 years ago at this point. They have done one update since then to fix something that would have stopped everyone in their tracks but there has been no new development or maintenance since then. 

We recommend doing a quick test out flight after every battery with the Air 2S. This makes sure you are logged in properly and allows you to make sure everything is working well in the DJI app before closing that and switching over to Map Pilot Pro. This could have been something as simple as a compass calibration issue that is easily identified in the DJI app but isn't really something we can display in MPP.

We hope we have a fix for the GSD calculation issue in the future.  

Had this happen again today. Calibrated compass and IMU before flight, killed DJI Fly, upon takeoff spinning on the way up. Landed, killed Map Pilot Pro, started the mission and it spun on the way up and once it got to altitude, started towards the start point but was spinning still, so I ended the mission. Rebooted the ipad, controller, and drone. Started the mission and it worked as expected.  Logs synced to the account.