Mini 2, Mini SE, and Air 2S Support + Android 12
Hey everyone!
Happy to announce that the latest Android beta (build 183) now has support for the Mini 2, Mini SE, and Air 2S. Unfortunately, DJI has not released an update to the iOS SDK (nor have they given a timeline), so these drones are Android only right now. Also, the SDK has several bugs in the DJI SDK which prevent the following functionality:
- Velocity-based rotation for the gimbal (such as interpolating between two markers on a path with different gimbal pitches) on the Air 2S
- Airdata integration (DJI changed the flight log format again).
This build also corrects the issues users were having with Android 12 (if you still see issues with Android 12, please provide feedback).
Comments
105 comments
Aaron D Ramsdell just tag Jim McAndrew in the post like this and he will. From what I have experienced, he is very attentive to the disucssions and the solutions!
Aaron D Ramsdell I'm having the same issue, but with a Mini 2.
Device is Samsung S20FE
Hey Jim,
Thanks for your efforts in getting the beta out so fast after the new SDK update. I have been waiting for months for the SDK release and I just brought an elite version of dronelink. However, it says the Air2S is not supported in the elite version. I'm pretty sure I have the beta version. It says I'm on the beta version on the app store and the app itself says Version 3.2.0 (183) | Kernel 3.2.0
You can add feature requests here. Please provide as much detail as possible as to what you expect the feature to do.
This is a well known, long standing issue that has been in production for years. Here is one thread of many discussing the issue. Ultimately we are planning to move away from DJI's UX SDK since they abandoned development on it, and we have already done this on iOS, which is why this issue is only on Android right now.
Don't worry, I see all the posts :) I also have to sleep at some point.
Thanks for the report, will look into it.
Should be corrected now.
Hey Jim, it is working now. There are two issues so far. The first one is minor and something that someone on youtube mentioned over a year ago and that is while orbiting a point, the yaw control isn't constant or smooth and it looks like a series of sharp yaw inputs. See this clip: https://youtu.be/w3UTzi_OEP4?t=318
The second one might be more android 12 / shitty Air2S SDK but I got about 3 frames total from the video feed and smooth telemetry for a test orbit this morning. One frame on the ground, one taking off and one about 1 minute in. I still have full remote control, just the video is screwing up. I haven't tried it again yet but thought I'd mention it here in case it rings any bells.
Cheers
When I go to video settings and I press the resolution to change the resolution the app crashes.
I tested it with Air 2S and Android 9
We haven't added the camera specs for the new drones so you can just select one that is closest or use the custom option. If you know the specs please post them.
https://support.dronelink.com/hc/en-us/articles/360052533153-Why-does-the-drone-fly-off-course-or-make-jerky-movements-during-certain-mission-plans-
Fun, sadly these UI screens are part of DJI's code and they have abandoned their UI library so we are going to have to eventually create our own set of screens, which is time consuming.
What mobile device are you using?
Hey Jim,
Thanks for the info on the controls. I'm using a pixel 6 pro. Dji had issues with them on Android 12 for their dji fly app which was probably only fixed 6 weeks ago.
Also, specs for the Air2S camera are here: https://www.dji.com/air-2s/specs
Unfortunately, they are using a different code base for their own apps, and whatever fix they made is not in the UXSDK because they have abanded development of it.
As usual, DJI doesn’t list the actual focal length, sensor width, or sensor height in mm. We will evetually dig for it but if you have it let us know.
Well I've created and flown a few successful missions now. Other than the 'weak video signal' message that has already been discussed, I've had no problems with flights.
I am having a problem with my log files not getting uploaded to Airdata though. Every time I open the Dronlink app or finish a flight I get 'Airdata update failed: invalid response'. I've been able to manually get the logs to Airdata, but would like to figure out why I'm getting this message. I've double checked the Airdata token and re-entered a couple of times but no luck. Hopefully someone can let me what I'm doing wrong.
See bullet two in the first post of this thread:
Sorry Jim, I read that a couple days ago when I was getting started and at that time it was not a deal breaker so it went in one ear and out the other. Thanks for the fast reply. I can manually import them for now.
I don't think manually uploading them is going to solve your problem because the issue is DJI changed the format and AFAIK Airdata can't read them yet.
It's working so far
Great!
Air 2S - 13.2 mm x 8.8 mm, focal length - about 8.5 mm (22mm - 35mm equivalent)
Mini 2 - 6.3 mm x 4.7 mm, focal length - about 4.5 mm (24mm - 35mm equivalent)
Mini SE should be the same ... and the same as the Mavic Mini, Mavic Air and others.
Mike Stead - You are my new hero!
If you are not opposed to a teaching moment, how did you figure these out? I know my use of Google does not count as "research", but I tried and failed to get these answers.
The weak signal message has been there a long time on the Mini. This has been discussed and apparently it’s only with Android devices. DJI was supposed to fix the SDK but still not solved. It’s believe it’s only on Mini’s and it’s only when using Android devices. As long as there is no messages or errors being reported while using in the DJI Fly app you should not worry about it. The new release of Beta for these drones is for Android only at this time so you will probably have this message, forever. But Who knows. Good luck.
https://support.dronelink.com/hc/en-us/community/posts/360049136053-Error-message-Image-Transmission-Signal-Weak-
That was my first impression, I had the warning so quickly tried DJI fly and Litchi and both were fine with the signal, so I assumed it was in the interface.
I've had no problems with actual signal loss beyond the normal stuff.
Tony Simek - you notice it says 'about'. I have had to figure this out on a few drones to figure out transect spacing for manual survey grids. You can divide the 35mm equivalent by the sensors crop factor. OR use the formula 35mm equivalent focal length = (some number near 35 * actual focal length) / sensor width.
The "some number near 35" is a problem as I have seen a few values used with no explanation. I just use 35 as at least there could be some imagined reason.
My actual calculations are about 4.3 and 8.2 (either method), but 4.5 and 8.5 will underestimate the GSD and give me lots of overlap.
Crop factor for the mini is 5.62 and for the 2S is 2.7
Also, when I look at the properties of images from the Mini 2 it gives the focal length as 4.0 mm.
Hi mike I have a Mini SE and have pictures and video I recorded. Is there any info I can get for you?
I also have both the dronelink and the Litchi betas.
Hi Aaron,
You could check the properties of any full resolution photo and see what it says for focal length. I would assume it will also say 4.0 mm. Pretty sure all Jim needs it for is figuring out transect spacing, and that he will find he can just use all the same code as the Mavic Mini or Mavic Air for the Mini 2 and SE and he can use the same code as the P4 Pro or M2 Pro for the Air 2S. Couldn't hurt to check and confirm.
This is a photo with my Air s2. It was in Auto Camera mode if that makes a difference to you. Hope it helps!
EDIT: Updated with accurate data from Photoshop
The above is for mavic SE.
Photoshop seems to give an exact Focal length of 4.49 for the mini SE.
You are right, Photoshop does give a much better measurement. I updated my post for the Air s2.
Great hopefully this will help https://support.dronelink.com/hc/en-us/profiles/381085491733-Jim-McAndrew and the other folks at Dronelink.
If the purpose of knowing the focal length is a simple as my supposition, it should be fine to use the 4.5 and 8.5... the downside will be you will end up with more overlap than you needed and this will worsen as you do surveys from a higher elevation.
It is interesting that the Mini SE reports 4.49 mm and the Mini 2 reports 4.0 mm. I think they are all the same sensor. Highlights the issue with trying for an exact number here and my reasoning on just erroring on the side of "caution". I don't like processing extra images, but better too many than not being able to create a model.
Please sign in to leave a comment.