The reason I chose Litchi over autopilot is that Litchi completes a mission even if the signal is lost. For long range runs out over open countryside it is great as the signal could easily get dropped depending on terrain / tree cover etc.
I asked Litchi on their forum about the consequences of a user specifying impossible actions (See below) and after reading their answer it sounds like they may not have all that much control over their program and leave much up to the DJI SDK.Any rising speed can be converted to two components: Horizontal speed and vertical speed. You got to use geometry concepts to do it. Once you separate out these components, check if both are within the limits of P3 discounting the effects of wind.
I suggest to Litchi developers to warn users if the computed components cross the set limit. Currently Litchi has no parameter for vertical speed limit. A good program should compute internal hidden values and should warn users if they cross limits.
Similarly I request Litchi dev to warn users if the ground clearance goes below a set clear value. Litchi should automatically compute along the route and warn users if needed.
That's is the scary part for me! But I'm sure I will relax more eventually. Whenever I see "weak signal " I just about crap my pants. My biggest fear is losing it even with RTH. Never had it happen yet. Maybe I need to so I over come this . I remember being about 2.8 miles out and trying the RTH. Worked beautiful coming back . Climbing to 250ft and landing 3ft from where it took off. I was so impressed. These things still amaze me! Once I learn the video editing and way points etc I'm going to doing this so much more!I bought Litchi for two reasons; The ability to pre-programme missions and the POI capability.
Both work fantastically well. I'm working on two projects currently; mapping the route of a canal (30 odd miles) from Lough Neagh to Carlingford Lough; and a study of a big oak tree that I'm orbiting every two weeks and stitching together to make a video clip of the changing of the four seasons.
Both are a doddle using Litch, but for ordinary flying I still prefer the Go app. On Saturday, I set the phantom off on a Litchi mission, furthest point was 2.5km away, go a quick rotate around, then curve smoothly back in to pick up the entry point of the canal. So off it goes, and gets out to the extreme point, does the wee circle and heads back. Great stuff, but then I got the warning 'SD card full, recording stopped'. Schoolboy error! Forgot to format the card before taking off. So I had to RTH and redo the mission. But it worked perfectly.
On one other section, I lost signal for about a minute as it went out of range / behind trees, but it just flew right back as programmed. No problem, but you do have to learn to trust the technology.
The reason I chose Litchi over autopilot is that Litchi completes a mission even if the signal is lost. For long range runs out over open countryside it is great as the signal could easily get dropped depending on terrain / tree cover etc.
I don't quite understand what you are saying about WP differences between Litchi and AutoPilot. With Litchi I can place all the POIs I want (only one can be used per WP, of course) - put them anywhere and drag them around and change the focus altitude. Choosing a curved path will smoothly transition the camera from one WP to the next. Is that different than Auto Pilot?Autopilot now has the LCMC (lost connection mission completion) that they were lacking before - but for that to work (with both Litchi and Autopilot), they have to rely on the DJI SDK.
If you're not worried about a lost connection - Autopilot affords a much greater degree of control during a waypoint mission because they use their own flight controller. Being able to define focus points anywhere on the map is the big one for me. With Litchi/DJI Go- you are limited to using the waypoints themselves as your Focus points. Being able to place them anywhere gives a lot more control and can produce a smoother, better video. On the other hand - Litchi (reportedly) has more actions that can be performed at each waypoint.
For creating a cinematic sequence that can be shot/framed *exactly* the way you need it - you can't beat AutoPilot.
The only right answer here is to own both products. Each product is better than the other in certain areas. If you only own one of them, you aren't able to get the most out of your Phantom!
Yes, I agree. I flew a mission this past Sunday morning with a altitude of 16' and a speed of 12.1MPH. The mission required me to increase altitude to 131' to navigate over some power lines. In the attached picture, you can see WP 11 is where I needed to program the altitude for 131'. The distance from WP 10 @16' to WP 11 @ 131' is only 62' in horizontal distance. The P3 was able to overcome that vertical climb and get me over the power lines (red line in picture).
That's a climb of 61.67° or ~150% grade.
I am wondering if Litchi ignores the horizontal speed and places altitude as a higher priority. In other words, Litchi tells the craft to be at altitude no mater what the horizontal speed. It slows down in speed until it gets to the desired altitude. A question for the developer, unless someone know for sure.
Flight Data answers question.......
I just downloaded the flight data from Sunday's flight. The data shows that the P3 slowed from 12.1 MPH to about 7 MPH in order to gain 115' of altitude in just 62' of distance. So it appears that Litchi or the DJi firmware places priority on altitude over distance. See the attached picture. The red dots on the Map window and the Charts window is centered between WP 10 and WP 11.
The mission speed was set to 12.1 MPH, which it held throughout the flight, until I had to abruptly increase altitude to clear some power lines.
View attachment 52517
View attachment 52519
I don't quite understand what you are saying about WP differences between Litchi and AutoPilot. With Litchi I can place all the POIs I want (only one can be used per WP, of course) - put them anywhere and drag them around and change the focus altitude. Choosing a curved path will smoothly transition the camera from one WP to the next. Is that different than Auto Pilot?
Flight Data answers question.......
I just downloaded the flight data from Sunday's flight. The data shows that the P3 slowed from 12.1 MPH to about 7 MPH in order to gain 115' of altitude in just 62' of distance. So it appears that Litchi or the DJi firmware places priority on altitude over distance. See the attached picture. The red dots on the Map window and the Charts window is centered between WP 10 and WP 11.
The mission speed was set to 12.1 MPH, which it held throughout the flight, until I had to abruptly increase altitude to clear some power lines.
View attachment 52517
View attachment 52519
Yes - different in a number of ways. In Autopilot, you can drop a focus point anywhere on the map - or you can have it focus on a moving person, or specify a direction angle relative to north or relative to the course that the Phantom is travelling. I'm not 100% sure what Litchi has for focus options but I believe you can only focus on waypoints themselves and maybe one arbitrary POI that is not a waypoint?
So it appears Litchi/DJI FW slows down the mission to climb over obstacles instead of hitting them, right? Good.Here's the video with a data overlay. The maneuver takes place at the ~7:10 mark into the video.
Thanks, but it might be a bit too complicated for this operator. I guess it's a matter/mixture of what you want or need and what you're used to.
I suppose AP has a feature like Litchi's browser Hub where you can prepare or tweak your missions on another computer and retrieve them later.
Does AP display the actual ground elevation of each WP? I find that very helpful around here.
We use essential cookies to make this site work, and optional cookies to enhance your experience.