unfortunately Dronelink cannot export flight plans in a format, which can imported into Litchi. This is the reason why I have both windows - Dronelink and Litchi - side by side in Step 2, as you have to draw the flight plan manually in Litchi. I also tried the "export to google earth" functionality in Dronelink. Here you will get a kmz file (sounds good as the RC2 need kmz files as well), but the format of the downloaded kmz file from Dronelink is not compatible with the RC2 :-(

Recently I had the problem (again), but it seemed I was too impatient and plugged the controller in before booting was finished. Maybe you can try the following steps: - unplug the RC2 and shut it down - log out the current user (MacOS) - log in again - boot your RC2 (and wait until it is ready) - and THEN plug it into the Mac At least this procedure worked in my case

To be able to download the CSV file from Litchi you need a license: if you don’t have a license yet, you‘ll have to download the litchi app (for Android or ios) and purchase a license from there. This is a one time payment, if I remember correctly around USD 25,-

unfortunately Dronelink cannot export flight plans in a format, which can imported into Litchi. This is the reason why I have both windows - Dronelink and Litchi - side by side in Step 2, as you have to draw the flight plan manually in Litchi. I also tried the "export to google earth" functionality in Dronelink. Here you will get a kmz file (sounds good as the RC2 need kmz files as well), but the format of the downloaded kmz file from Dronelink is not compatible with the RC2 :-(

Furthermore, your comparison between the Air 3 and Air 3S cameras is undeniably a vital undertaking. From my own experience, I noticed that the Air 3 struggled with strong sunlight, such as during sunrises or sunsets, and I wondered if it was just my imagination. However, seeing your thorough comparison tests clarified and validated my observations.

I will continue to support your work and look forward to your future endeavors. Thank you, and I wish you continued success. (I wrote a new comment because my comment didn't show up in a direct reply to you. Thank you again.)

Glad I could help! I'm also a long time Litchi user since the first Mavic Pro. But DJI's decision to stop updating the mobile SDK for consumer drones made me search for alternatives, and there I figured out how to upload kmz files to the RC2 to import waypoint missions

@@stefanwoermcke6828 What a great idea!!! Do you have a video or blog article that explains how to export csv, convert to kmz, and upload to the controller? I would love to learn how to do this!

Some time ago I made a video explaining in detail how to convert a Dronelink mission into a kmz file that can be uploaded to the controller: kzbin.info/www/bejne/gIS2ep2FhrF_mpo For you I would recommend to watch from 05:05, where I export the flight path from Litchi as a CSV file, convert it into a kmz file and import it into the RC2. Seems a bit complicated at first, but after a few times it becomes a simple process!

A while ago I created a detailed video how to do a waypoint mission in dronelink, re-draw it in Litchi (as you cannot import dronelink missions into Litchi), and import it into the controller: kzbin.info/www/bejne/gIS2ep2FhrF_mpo For you I would recommend to watch from 05:05, where I export the flight path from Litchi as a CSV file, convert it into a kmz file and import it into the RC2. Let me know if you need any more info, happy to help!

Mr. @@stefanwoermcke6828 Great. Your efforts are truly remarkable. Many people are struggling with compatibility issues with existing software, and your contributions have brought hope to many, including myself. I have been a longtime user of Litchi, but its unavailability for the Air 3 and later models left me feeling lost.

Thanks for pointing this out: just double-checked, it seems they have changed the way they process airdata logs: while I created the video the option was named "Desired Number of waypoints", but it is now renamed to "Minimum Distance between Waypoints": similar results, but with a different approach: you define the minimum distance between two waypoints, which will then determine the total number of waypoints. If you use the slider to set the minimum distance between waypoints, max value for "feet/metres" will be 100, but if you use the up/down arrows next the value for the minimum distance, you can set even higher values! This way I just testet with 300 as minimum distance between waypoints, which gave me quite a reasonable number of waypoints - maybe you want to give it a try with a value between 200 and 300?

@ thank you so much for coming back to me I really appreciate it.

What MacOS version are you running? I double-checked this morning and did an upgrade to MacOS Sequoia 15.1 on my iMac (M3)- still working! My Mac Mini 2020 (Intel) is running Sonoma 14.5, also connecting without issues. (RC2 latest version). Mabye worth comparing your MacOS version?

Now I had the problem again: plugged it in while the RC2 was booting - and the problem was back! What helped here: unplugged RC2 and shutdown, log out the user (MacOS), log in again, boot RC2 (and wait until it is ready), and THEN plug it into the Mac: voila, everything is working again!

@@stefanwoermcke6828 Macbook Air M2 - MacOS Sequoia 15.0.1

I tested premium for a while (the 14 days trial period), but now I am back on "Fremium". I prefer the "pay as you go" method of Skyebrowse when I need a more accurate model.

Definitely on my list!

I guess also very similar (test will follow) ! But here be aware of „DJI Marketing“: DJI Air3S with ISO from 100 to 12800 (DJI Air 3 from 100 to 6400): correct, but the DJI Air 3 has a special „Night Shot“ mode, and looking up the specs for that it states „ISO from 100 to 12800“ - so same max ISO, but in a separate shooting mode! I did a night shot last year with the DJI Air 3, and I was blown away by the superb quality of the video!

In der Zwischenzeit ist es mir auch passiert, dass die Neuinstallation von DJI Assistance 2 keine Verbindung per Android File transfer mehr zustande gebracht hat. Auf dem iMac (M3) hat es sporadisch mal nicht funktioniert, meist aber problemlos.Der Mac Mini (Intel, 2020) konnte lange Zeit überhaupt keine Verbindung zur RC 2 aufbauen, funktioniert aber seit ein paar Wochen wieder problemlos - ohne DJI Assistance neu instaliert zu haben! Ich vermute das Problem liegt in der Kombination von Apple und DJI Fy Software Versionen. Aktuell funktioniert die Verbindung (wieder) auf beiden (Mac: Sonoma 14.5) und DI RC2 (1.15.0). Falls noch nicht gemacht, würde ich mal ein Update des RC2 auf 1.15.0 durchführen. Wenn das auch nicht hilft, gibt es ja immer noch die Option, Dateien auf eine SD Card im Controller zu kopieren, wie hier beschrieben: kzbin.info/www/bejne/opyliZ2naZKqabcsi=4eYuW_a7T6wZvqzd (ab 06:40 erklärt).

@@stefanwoermcke6828 FW ist 04.01.0000 / APP 1.15 der RC2. Mit der RC der Mini3 pro klappt es übrigens ohne Probleme immer. Das ist doch schräg, oder?

ja, in der Tat. Obwohl die Mini 3 eine "RC" Steuerung, und keine "RC2" ist.. habe irgendwann mal gesehen, dass die beiden sich nicht ganz gleich verhalten, wenn man sie an einen Desktop anhängt!

@@stefanwoermcke6828 Ich habe ja beide und die RC2 geht nicht, die RC der Mini ja ;)

In the meanwhile I experienced that it stopped working from time to time, even with re-instaling of DJI Assistance 2. On my Mac Mini 2020 (Intel) it completely stopped for months, but is working again since a few weeks without doing anything. I suspect this is a combination of MacOS and DJI Fly App versions, more on DJI's firmware updates. My RC2 controller is updated to: App Version 1.15.0, and is currently connecting fine to MacMini (Intel) as well as to iMac M3. So maybe try to update? And if it's urgent to get the footage, try inserting an SD card in the RC2 and copy your footage to the card, as described in this video: kzbin.info/www/bejne/opyliZ2naZKqabcsi=4eYuW_a7T6wZvqzd (watch from 06:40) hope this helps as a workaround!

As described in the video, you have to draw the dronelink flightpath (manually) in Litchi, export the Litchi mission, convert it into a KMZ file and then import it into the DJI RC2 controller.

Hi, If you have a KML file, you will first have to convert it to a KMZ file. Then you can import your waypoint mission as a "kmz" file into the DJI controller. If you're interested in the details how to do the import, I described the detailed steps in this video: kzbin.info/www/bejne/gIS2ep2FhrF_mpo (Fast forward to 08 minutesd 3 seconds you can see how to do the import)

@@stefanwoermcke6828 thanks 🙏🏻

Hi, short answer: Dronelink does not support the DJI Air3, so closest model to pick was the DJI Air 2, and this setting works quite well ! Long Answer: since last year DJI decided to provide mobile SDKs only for Enterprise drones from DJI. With this decision made, third party apps developer like Dronelink cannot create apps to control the latest consumer drones like DJI Air 3, DJI Mini 4 pro etc. anymore. So to get a flight path to cover the entire area to map I did a bit of testing, and finally figured out that selecting „DJI Air 2“ as camera settings works best. Nevertheless Dronelink cannot control the DJI Air 3, and therefor we have to re-draw the flight path in Litchi. Not the perfect solution, but as long as DJI won‘t change their mind we have to live with this workaround.

@@stefanwoermcke6828 thank you for your answer.Your video are nice but I have difficulties to follow with video,ages probably,do you have like a power point of that explanation to use AIR 3 for photogrametrie .like a course?Im ready to paid

Thanks for the hint! So far I only did the "Edit options", but never checked the drop-down menu! I will give it a try and report back here!

Hi @OlivierGalizzi, unfortunately from Dronelink to Litchi is a manual step: you have to draw the flightpath in Litchi, trying to match the path as closely as possible to the Dronelink path. It doesn´t have to be "pixel perfect", but as a minimum keeping the number of turns suggested by Dronelink should be good enough. Another user mentioned the possibility to do a direct export from Dronelink as a KMZ file ("Google Earth export"), but for this to work you need the "elite plan" from Dronelink: app.dronelink.com/pricing/hobbyist/compare

Hi @WoodRobinson-oi8wi, just double-checked my flight logs from recent mapping missions, but when using waypoints the Air 3 will keep the exact altitude as defined in the mission. It seems terrain follow mode is only available for DJI Enterprise Drones: www.heliguy.com/blogs/posts/benefits-of-terrain-mode-with-dji-drones-for-aerial-surveying#:~:text=Terrain%20Follow%20allows%20the%20drone,as%20hilly%20or%20mountainous%20regions.

@@stefanwoermcke6828 Thanks Stefan! I know terrain aware limits that - but i'm wondering if there's a back end way of setting altitude for each waypoint in Litchi? For example, could one add an elevation point at several waypoints according to an imported DEM?

@@WoodRobinson-oi8wi Good question - in Litchi you can import DEM files, but I am not sure how this will affect the Waypoint Mission: even if you´re take-off spot according to DEM is e.g. 400m above ground, your Drone will mark the take-off spot as 0m.. and if the first waypoint is according to DEM 450m above ground we have a problem.. Do you have a DEM file at hand? Would be interested to know how this will change your waypoint mission planning!

Hi @craig_Dronepilotsqld , when I took photos of the exact same field for stitching in an altitude of 40m last year, WebODM wasn´t able to stich the photos together. After a bit of research I learned that WebODM has problems when stitching photos taken in a low altitude and a field with no major distinguishing features. So my take on that (so far) is that WebODM needs photos from a higher altitude, whereas Skyebrowse gives better results with a video in a lower altitude. I also created the same mapping with Skyebrowse in 4K in 35 m altitude, but comparing it with the (Skyebrowse) mapping in 1080p in 35m I cannot see any significant improvements! Finally, WebODM is able to work with GCP´s (Ground Control Points), and this would definitely improve the quality of the result.

Glad you find my videos useful! Indeed Dronelink has no equivalent drone for planning with the 3x lens, there is only the "Mavic 3 Enterprise (Zoom)", which is a 162mm lense - no exact match, but maybe a good starting point for some tests. I agree with you that the Air 3 is a good combination of holiday use and photogrammetry, not only for the 3x lens, but also for the higher wind resistance: as I live in an area with strong winds, for me the Air 3 was the obvious choice over the Mini 4 pro.

Thanks for the hint, depending on your dronelink plan (starter/elite/..) it seems possible. Nevertheless keep in mind if you do a direct import from a dronelink export to the controller, DJI will convert straight lines into curved lines, which is not optimal for a field mapping. This is also mentioned here, and obviously the same problem for Mavic 3 pilots: forum.dji.com/forum.php?mod=viewthread&tid=286066 So this is the reason I added additional waypoints to the edges of my flight path in Litchi, to straighten the lines as good as possible, as described in my video in chapter 2 (Flight planning with Litchi).

@@stefanwoermcke6828 ok tq info

Glad you like my video! Further testing is underway: I just subscribed for a 2 week trial at Skyebrowse.com to compare mapping with 1080p vs 4k Videos. As soon as weather permits, I plan to do the same field mapping as described in my step-by-step tutorial I published a while ago: kzbin.info/www/bejne/gIS2ep2FhrF_mpo As soon as I finished my testing I´ll comment here!

Cheers! If you have any info regarding skyebrowse with Avata 2 that would be great too!

Are you looking for Interior Mapping? Then the tutorial for the Avata maybe of use for you: www.skyebrowse.com/news/2024/1/24/interior-mapping-tutorial

@@stefanwoermcke6828 i was curious if avata can be used for both exterior n interior, so we can just buy 1 drone to do both of the task

@MarkAngel86 I can only speak for the Avata 1, where you would have to fly your mapping missions manually, as there is no automatic flight planning like Waypoints. And as for a mapping of huge fields (where you will have to point your camera 90 degrees downwards), it will be hard to fly a regular pattern (with 70-80% overlap) to cover the whole field just by looking through the goggles. An alternative for interior mapping maybe with a phone or a DJI Osmo Pocket (also on my list for testing).

Yes, indeed litchi is easier to use! Just out of interest: will the litchi mission be uploaded to the m3p? With my Mavic Air 2, the litchi up won´t upload the mission upfront, but instead will give constant commands from the App (via the remote), which (depending on signal strength) leads to jerky videos, especially when cornering. In contrast, waypoint missions with the Air3 seem to be uploaded upfront, resulting in buttery smooth videos without any jerks!

Gerne!

Leider wird die DJI Air 3 von Dronelink nicht unterstützt: www.dronelink.com/supported-drones Somit ist eine direkte Steuerung der Air 3 durch Dronelink nicht möglich

I´m afraid dronelink does not offer to create an account for free

For litchi it seems you can create an account without paying for the Litchi App - which makes sense as without the app you won´t have the benefit of automated syncing: flights planned on the desktop will be automatically available on the Litchi App. For our use case we don´t need the litchi app, as we only use the export function