So, I've been a user of Litchi since my Phantom 4 Pro. Used the waypoint flying a lot back then. Stopped flying for about 3 years and times had changed. New DJI consumer drones weren't able to fly waypoints except by "virtual sticks" which was unacceptable for me. Many times I'd lose signal from the Phantom 4 for up to 12 minutes and always breathed a sigh of relief when communication was re-established.
When I got my Mavic 3 Classic last year, I knew Litchi wouldn't work on it, but the DJI way of programming waypoints for an autonomous mission was many, many steps backward, and trying to set up a waypoint flight on the 5.5" screen on the RC Pro was just too tedious.
I've read of several web based flight planners that work, some free, some limited unless you pay a subscription for features that still don't measure up to the way Litchi, Litchi Virtual Mission and Google Earth all work together in creating and then flying the mission on Google Earth before an actual flight mission.
For the last week or so, I've wondered and thought about if it was possible to create a Litchi mission in the Litchi Virtual Mission app, import it into Google Earth then change the file structure from a .kml to a .kmz file that can be squirted into DJI Fly app as a waypoint mission like the web based solutions,
Today I started fooling around with Litchi Virtual Mission, Google Earth and my RC Pro/Mavic 3 Classic.
Since we're having a house built several block from our present residence, I've been sending up the bird for overflights to check on the progress of the build.Having a repeatable, consistent flight would be cool so this was my test bed.
So, I created a mission with two poi's and a 14 point waypoint mission, and tweaked it several times using Google Earth to check on camera angles, altitude settings, and then headings settings.
After I was satisfied, I then saved the flight as a .kmz file in Google Earth, then selected an existing waypoint file in the FLy app on my RC Pro. I copied the file name in a waypoint folder, re-named the Google Earth waypoint file to that file name that was copied, then inserted it into the folder that contained the original waypoint folder after deleting the original .kmz file.
The moment of truth had arrived. Turned on the drone, waited for sats, started up the waypoint feature, selected the proper file name and it was off to the races. Other than some slight differences in speed and camera angles, the flight was perfect and all I did was watch on the screen as the flight proceeded from take off to the RTH landing.
I'm happy,
When I got my Mavic 3 Classic last year, I knew Litchi wouldn't work on it, but the DJI way of programming waypoints for an autonomous mission was many, many steps backward, and trying to set up a waypoint flight on the 5.5" screen on the RC Pro was just too tedious.
I've read of several web based flight planners that work, some free, some limited unless you pay a subscription for features that still don't measure up to the way Litchi, Litchi Virtual Mission and Google Earth all work together in creating and then flying the mission on Google Earth before an actual flight mission.
For the last week or so, I've wondered and thought about if it was possible to create a Litchi mission in the Litchi Virtual Mission app, import it into Google Earth then change the file structure from a .kml to a .kmz file that can be squirted into DJI Fly app as a waypoint mission like the web based solutions,
Today I started fooling around with Litchi Virtual Mission, Google Earth and my RC Pro/Mavic 3 Classic.
Since we're having a house built several block from our present residence, I've been sending up the bird for overflights to check on the progress of the build.Having a repeatable, consistent flight would be cool so this was my test bed.
So, I created a mission with two poi's and a 14 point waypoint mission, and tweaked it several times using Google Earth to check on camera angles, altitude settings, and then headings settings.
After I was satisfied, I then saved the flight as a .kmz file in Google Earth, then selected an existing waypoint file in the FLy app on my RC Pro. I copied the file name in a waypoint folder, re-named the Google Earth waypoint file to that file name that was copied, then inserted it into the folder that contained the original waypoint folder after deleting the original .kmz file.
The moment of truth had arrived. Turned on the drone, waited for sats, started up the waypoint feature, selected the proper file name and it was off to the races. Other than some slight differences in speed and camera angles, the flight was perfect and all I did was watch on the screen as the flight proceeded from take off to the RTH landing.
I'm happy,
