Litchi chit-chat ... What's Litchi? Should I use Litchi?

I think if you select one point, edit the actions, you can then ctrl click as many other points as you want to change and click ‘apply’.
What I’m not sure of off hand (will have to test) is if it overwrites all the other waypoint settings too, or just the ones you change.

Well that didn’t go according to plan, all in the learning I guess. First litchi flight and the flight itself was good. Just got gimbal angles wrong somehow. 0, -45 and -90. I had assumed 0 would be looking straight ahead? Can’t use a + number seemingly. I’ll have another shot tomorrow, it is a bank holiday afterall :smile:

I’ve tried with Interpolate and it makes no difference. The flight is still jerky. I’m not sure if it’s the speed I have set for the flight at 20mph?

Today I will try at 8-10mph and see if it makes any difference.

I’m after some help on a mission I want to fly, I’ve only just started using Litchi for missions so please be gentle. I am wanting to fly in a circle around Castle Roy and take enough photos to stitch together for a 360 pano of it. The structure is 25ft in height and 80ft x 53ft. I’m thinking two waypoints on each short side, 3 on each long side and one at each corner would be enough. Each waypoint will have 3 photos, one straight accross at 0 degrees, one at -45 and one at -90. Cant get litchi to look up for some reason?
What are the experts views on the above? Sound ok or is it likely to end in disaster :thinking:

Panoramas are done from a static position looking outwards from that point in the necessary directions with appropriate tilt - not by circling a point and looking inward toward it. So the images you take won’t stitch.

If you are after a 360 panorama from above it - then just fly there normally and initiate a 360 panorama … from Litchi or the Fly app.

1 Like

OK, thanks. Maybe I’m using the wrong terminology? Virtual tour is maybe more correct? Basically I want to be able to view the outside of the building, from all angles. About 40ft out and 40ft up so I can also see inside the walls

Thanks for clearing that up, I’m my 3rd coffee this morning on way out and scratching my nut thinking wow how can this be done but as I was thinking inside out how outside round.

I can now carry on the day clear headed not having @DazC question niggling at me as I wondered if there is a answer to it.

Edit: Oh no Darren’s asked another :scream:

Hopefully be answering next 5 mins otherwise my nut will hurt :rofl::rofl::rofl:

Are you using the app, or Mission Hub - Litchi in a computer browser, to create the mission? I’d recommend the browser for all planning when not at the location.

1 Like

yes on browser.

Where will you take off from - at the base of the castle or somewhere else?

Not sure yet where I’ll take off from but I don’t want to be in any of the pictures. I have permission to use anywhere on the site from the land owners

There is no ground height information in the mission once created.
The mission flies only using heights relative to take-off.
So, to get your flight heights correct, first you need to decide your take-off point.

in that case it would be from the ground at the main entrance to the structure, I’m away to check online.
The entrance is at north east

so I’ll be taking off from ground level

Chances are, at a sensible distance, you’ll only need to take pics directly at the castle.

  • 0° will be looking straight over the top
  • 90° down will only be looking at the boring ground immediately below the drone at whatever distance you are from the castle.
  • there’s only sky looking up.

You could just fly a circular mission and take images of the castle at regular intervals - but it sounds like you want them from specific directions?

If so …

Mission Settings

  • Heading Mode - Custom (WD)
  • Finish Action - your choice. I tend to use “None” and it ends the mission and goes into a hover, and I fly it back manually from the last waypoint. You could use “Back to 1” … ie “Waypoint 1” (see later), or RTH
  • Path Mode - Straight Lines. This will enable it to fly to the next WP, and stop, whilst it takes the next pic.
  • Cruising Speed - something sensible. 15mph-ish?
  • Max Flight Speed - probably the same, but no less.
  • Photo Capture Interval - Disabled.
  • Default Curve Size - will be ignored since you set Path Mode to Straight Lines
  • Default Gimbal Pitch Mode - Focus POI … although I always set as in the next bit, by selecting all WPs. Belt and braces if you set it here too. (Useful if most WPs are one option, and a few are the others.)
  • Use Online Elevations - Un-check. You are taking off at “zero altitude” and basing WP’s at your desired altitude relative to take-off, which is far more easy for a simple mission like this.

Mission
Set your POI (“POI 1”) to the centre of the castle (which should be near enough the same height at take-off) by Right-clicking at that location. (Zoom into the map well to get the location reasonably accurately.)
Set your first waypoint (“Waypoint 1”) at the take-off position. (If you use “Go to 1” as your finish action - it will fly to above your take-off point and hover for you to land.) Again - zoom in for good accuracy.
Add waypoints to create the route you want to fly at the distance you want to fly from POI 1.
“Select all waypoints”. (Windows - Click one WP, then Ctrl+Click another WP, then click “Select All” from the pop-up.)

  • Set their height to the height (above take-off) that you want to fly the mission.
  • Set POI to 1
  • Gimbal Pitch to Focus POI (Which will be POI 1 as set in the previous setting.)
  • Actions - Select Stay for and set to 1 sec (ensures the drone is in a stationary hover before taking a pic. Not essential - but with the drone stopping at the the WP, it just makes sense, when the “stopping” can create a wobble.
    - Select Take Photo
    So this bit looks like …
    image
  • Click Apply

Re-select just WP 1 and remove the Actions for that WP, since an almost straight down photo from above take-off probably makes little sense. Could leave it if you want to include.

Save the mission - and you should be good to go.

4 Likes

There is a Windows prog - Virtual Litchi Mission - which enables you to virtually “fly” the mission. Something I tend to use, because it’s a double check that everything’s set as you need to get the result you want.

An example : Flying in London! :wink: … albeit that’s for a video mission (that I was never going to actually fly!), even for stills you’d be able to confirm the angles.

1 Like

Wow, thanks for all the @OzoneVibe , much appreciated.
I went there yesterday, but decided to use the time to scout out the location properly. I took some more photos and videos that I’ll look at when I get a minute. Then at the weekend I’ll make another mission using your info.
Thanks again

1 Like

A very similar tool is available for Chrome or Firefox on MacOS: YetAnotherVirtaulLItchiMission

I am converting over to Litchi from Maven following a hardware change (going back to Android). Maven only runs in IOS so I have taken the plunge with Litchi. I am using an Air2S as my drone.

I need a little help understanding the “Above Ground” function and whether I should be using it by default, or why I might not want to use it.

It seems to me (and that doesn’t mean much), that if this function is turned off then Litchi will base the drone’s altitude off the altitude at the first Waypoint, in effect treating the flight path as a flat uniform surface and calculating it’s (the drone’s) height off that measurement.

My understanding of the “Above Ground” option is that this is based off some map data (maybe Google Earth Topographical) data and vary the height you set to always be “x” feet above the ground based on the topographical data. This means that the mission will see the ground as an undulating surface and calculate altitude accordingly.

I am either somewhat close to understanding or completely off, thus the reason for my confusion and the question?

Anyone? :face_with_spiral_eyes:

1 Like

Moved your post over to this thread that is more up-to-date than the 2+ year old thread.