This issue is driving me CRAZY! Please fix this waypoints bug!

Hey, Litchi developers, you need to focus your attention on this one! There is an issue with Litchi Waypoints engine where it gets “stuck” on a waypoint and then starts to fly round it in circles/lines and never proceeds with the mission. Tried everything, disabling obstacle avoidance, restarting the mission, sometimes that fixes the issue, like, it circles the waypoint around 30 seconds and then proceeds with the mission, but sometimes it just doesn’t…

Today it happened to me, here is the mission: Mission Hub - Litchi (
Here is the log: 13-05-2022 13:51 | General / Overview | Litchi log 4.23.0-g | Spain | Airdata UAV

After 3 failed attempts to restart the mission from waypoint 7, I just went into RTH and switched back to DJI Fly, that’s why the log ends there.

It got stuck on waypoint 7, and circled it…
It wasn’t windy during the mission, about 15 km/h winds.
I am happy to provide any other information you need :slight_smile:
But please, fix this!

1 Like

Your Homepoint is at: Lat. 39.585423 Lon. 3.378357 (WP8 in my screenshot)

When your Mavic Air-2 reaches WP7 the controlsignal is most likely (partially) blocked by the building at: Lat. 39.586563 Lon. 3.379030 (WP9 in my screenshot)

Have a look at this topic:

I had 4 bars of signal (both control and HD video) in Litchi app while this was happening. I had missions run successfully on this drone with much worse signal.

A quickie visualisation of your flight mission.

Looks like an intermittent signal fault from the controller
but not by buildings getting in the way.

Drone seems to have had a terminal heart attack at waypoint 7
suspect dodgy cable to the phone on the controller.

Maybe you should change the cable or try a different
Iphone / Ipad and try the same mission all over again.


1 Like

Damn thing works great on my M2P!

I have had a bit of a re-think here, maybe not a loss of signal at all.

There may be a glitch in the program preventing
smooth flight after waypoint 7.
The drone was going along quite good in the mission up to waypoint 7,
then it crashes.

Go back to litchi hub on the computer and move waypoint 7 around a bit,
check all the settings for waypoint 7, change the height a little.
Then re-load the mission.

“There may be a glitch in the program”

The glitch is not in the program, it’s in the control signals.
Signal strength has nothing to do with this issue.
Signal interruptions do.

Imagine a drone is some 30 meters away behind a big tree, branches and leaves moving with some wind.
Control signals get interrupted by the moving branches and leaves, but when not interupted, signal strength will be 5 out of 5 bars.

Besides that he’s flying in an urban area where there will be strong interference, certainly from the building beneath WP7 and the buildings surrounding the Homepoint, and the used protocol is CE, not FCC (Spain).

“Damn thing works great on my M2P!”

The M2P is NOT a VSC-drone, it will complete any waypoint mission even with the controller turned off.

1 Like

Yep … Tribar is correct = Signal interruption.
Blocked by building.

Video >

Yellow vertical line = take off from car park.
Line of sight is good from car park for waypoints 1 > 6.

Waypoint 7 is behind building on opposite side of street.

Yaroslav needs to stand under waypoint 1 to launch drone
for un-interrupted signals for entire mission.

1 Like

Just to mention, I was standing on the top, on the rooftop of my apartment, perfect signal from there on 120 meters height. I can fly to 6 km from there, and the drone wasn’t even 1 km away. Maybe it’s an issue with litchi not being able to control the drone because of the lack of commands, because the radio link slows down.

Guaranteed solution to this problem = Buy a Mavic Pro 2 :smiley:

1 Like

Create a waypoint mission using Litchi Mission Hub, and then go along for the ride by monitoring the Litchi screen during the mission.

If the RC signal disconnects during a Litchi waypoint mission, there is no cause for alarm because the drone will continue to follow the programmed flight path until it returns to within RC signal range, at which point your video feed will be restored, provided of course that you remembered to go into Litchi settings to insist that the drone continues the flight path if the RC signal is interrupted or lost.

You will get much smoother camera panning sweeps if you preset camera horizontal directions at each waypoint along the Litchi flight path, than if you fly manually and control the camera with RC yaw inputs. Also, you can throw in multi-loop orbits around points of interest with that same fluid and gradual camera panning action that Litchi does so well.

Check your flight path for obstacles by flying a trial run at say 240 feet AGL so as to allow adequate vertical clearance above cell towers, then after reviewing that exploratory footage, you can lower the altitude at each waypoint by gradual increments over subsequent flights.

This does NOT work with drones build for the DJI Fly App (VSC-drones).
Yaroslav is flying a Mavic Air 2 !

This only works when ‘Heading Mode’ is set to ‘Manual(UC)’,
at the same time:

You can not do this when ‘Heading Mode’ is set to 'Manual(UC).

NOT possible within a Waypoint Mission.

I must clarify that I only use Litchi’s waypoint mode and nothing else, so Heading Mode remains a mystery to me thus far. Also, I agree that newer drones utilizing the infamous Virtual Sticks protocol are not capable of flying waypoint missions beyond RC signal range. My drone squadron comprises a Phantom 3 Standard, Phantom 3 Pro, a Mavic Pro 1, and a Mavic Pro 1 Platinum, all of which are trusty museum pieces that store GPS waypoint data onboard and are therefore capable of completing waypoint missions far beyond RC signal range, unlike the newer drones which default to RTH the instant RC signal falters during a Litchi waypoint mission. Older DJI drones offer me a way better bang for my buck, and besides, I’d need to sell my mother-in-law to raise enough money for a newer drone.

All told, and after much trial and error, I have over time amassed a thorough working knowledge of Litchi’s waypoint capabilities so I can state without a shred of doubt that one can indeed program multi-loop orbits with the Litchi Mission Hub, before flying such missions with absolute reliability each and every flight.

Double Loop

Above is a simple double loop that I recently programmed with the Litchi Mission hub. By setting the house in the center of the loop as a Point of Interest, Litchi automatically adjusts the horizontal camera direction so the camera remains trained on that house during the entirety of both loops.

The above is a simple double loop flight segment, but I have many others that involve triple and even quadruple loops at varying altitudes around multiple points of interest in sequence, hence my certainty that sending the drone to fly highly complex looping orbits is a thing of ease and beauty to behold, with Litchi.

“so I can state without a shred of doubt that one can indeed program multi-loop orbits with the Litchi Mission Hub”

Part of the confusion is your use of terminology. The word “Orbit” in Litchi is used to describe a specific flight mode selectable from the main menu. Litchi’s orbit cannot be made part of a waypoint mission. What you have done is arrange a number of waypoints in a circular pattern with a POI at the center. That is simply a waypoint mission. Using the term “Orbit” makes us think of Litchi’s “Orbit” flight mode.

“I must clarify that I only use Litchi’s waypoint mode and nothing else, so Heading Mode remains a mystery to me thus far.”

Heading Mode is a setting within Litchi’s Waypoint Mode. It is not a separate flight mode. If you are familiar with waypoint missions, you should also be familiar with the various Heading Modes that can be used in waypoint missions. They can be specified near the top of the Settings dialog in the Mission Hub.

Ah, I see. I used the word orbit, without realizing it is a specific term used by Litchi, so yes I am referring to simply arranging waypoints in a circle around a point of interest. I need to read the manuals a bit more so I can avoid using ambiguous terms here.