Waypoint Engine Not Activating

Beta Feedback
1

I have been using Litchi on Mavic 3 Enterprise for 11 months with zero issues.

  1. Waypoint mission created on the Mission Hub and is unchanged from previous flights.
  2. Loaded Build 502 May 26.
  3. Attempted a weekly video on a construction site and had immediate issues.
  4. “WAYPOINT” is displayed in flight mode. “APAS” displayed prior to takeoff then “AUTO” after take off.
  5. At around 500 to 600m OR low signal the mission is interrupted with a message that the flight mode has changed. The mode at top of screen flicks between “APAS” & “AUTO” The drone hangs and the only remedy is RTH.
  6. Attempted several more times - same issue at slightly different but generally same location.
  7. Uninstalled Litchi from DJI controller and reloaded 1.0.0. Beta DJI 380.apk. Switched DJI Waypoint engine on and allowed mission continue if signal drops.
  8. Completed mission no issue.
  9. Reloaded Build 502 and experience same issue.
  10. Repeated once more.
  11. Back to Beta DJI 380.
  12. Repeated this whole process on a different site with a different but well used and tested mission with the same results.
    Am I missing a step somewhere? I have loaded all of the previous Beta updates with no problems.
2

With the latest beta build, now the default is Litchi Engine if no engine was selected at the flight planning stage (in the Hub).
If you want to use the Onboard engine (DJI engine), you will need to update the mission in the new Litchi Hub (at https://hub.flylitchi.com/), making sure to select the Onboard engine.
We understand this makes it impossible to fly older missions using the onboard engine, so we will soon introduce a way to change the flight engine on the fly in the app.

1 Like
3

Are you able to make the previous build available because I have too many missions that NEED to be flown as close as GPS limits allow week by week.

4

I would suggest updating your flight on the new Hub to use the onboard engine.

But if you must, you can download the previous build from here

5

I have attempted to update missions created on Hub 1 for Mavic 3E on Hub 2 but without success.
Then created a new test mission with varying results.

  1. I have set the Flight Engine to “ONBOARD”
  2. Using heading Mode in the settings “Follow Path” and “Follow Path” in the Waypoint menu
  3. Individual mission legs will orient the drone and camera to the leg bearing - NO problem
  4. Using heading Mode in the settings “Locked” and “Locked” in the Waypoint menu but setting a different heading to the route heading
  5. The drone adopts the INITIAL leg bearing and does not deviate through ALL the legs
  6. The same results from a “Follow Path” & “Locked” combination
  7. I have tried different permutations with no success
  8. The simulator has the drone performing as per intention but IS NOT translating to the Mavic 3E

Apologies if this is confusing but have tried to make it as simple as I can. Simply put, I want to be able to orientate the drone on a different bearing to the course heading and I do NOT want to use the “Point of Interest” .
Thanks

6

I have just tested creating a new flight on the new Litchi Hub, using onboard engine, and for me Locked and Follow Path heading modes work as intended, even when combined. I tested it in simulator with the Mavic 3E and it works as expected. The heading follows the path when set to Follow, and stays on a locked heading when set to Locked.

It is possible that the conversion from old hub flight to new hub flight is causing issues, so I would advise starting fresh.

7

Vico,
As I tried to explain:

  1. I have created a NEW mission on the new hub
  2. The mission DID work on the simulator
  3. But DID NOT work on the Mavic 3E drone

I will revert to old hub and version of litchi so not to bother anymore

8

please share the mission so we can test the same. Our own test found no issues with Locked/Follow heading
modes and worked as expected with both Hub and drone simulators

9

You are correct. Your description is confusing. Your bulleted list combines thing that do work and maybe some things that don’t work. It’s hard to tell if #4, #5, #6 are a problem or not. It would help if you simply stated what you are trying to do and what settings you have tried to accomplish that.

This is clear. You want to use the “Transition” heading mode only available in the configuration panel for each waypoint. Using the “Transition” mode, you can specify the heading at each waypoint.

10

Appreciate the input. I acknowledge this is confusing but this is “bug” reporting and am simply trying to give as much information as possible. What WORKS and what DOES NOT WORK.

11

I think in his case, and if I understand his needs correctly, Locked heading mode will be more suited. Like Transition, it lets you specify different headings for each waypoint too but it will stay locked on that heading until the next waypoint. Locked is a new heading mode with the new Hub.

12

This is my test mission. It works fine on the simulator. In the field, the Mavic 3E commences on a heading of 300° and stays on 300° on ALL legs.

13

We’ve found the issue, it is related to using curved turns. It will work fine if you use straight lines as path mode. We will fix the issue in the next build so it works with curved turns too.

Thank you for your feedback

14

Thanks Vico. Happy to help