Welcome, Autel Pilots!
Join our free Autel drone community today!
Join Us

Autel EVO II Feature Requests – Submit Here

gschulzuio said:
The following is for android:

1. Copy your kml to autel explorer folder on your device.

Note: If you have an extra microsd card(s) in your device, make sure you point to one where explorer located).

2. E.g. if explorer on default/main device (e.g. phones memory/storage) then something like:

device -> Android -> data -> com.autelrpbotics.explorer -> files

3. Open autel explorer app, go into missions, look for small import (not intuitive) icon middle right (see yellow circled on image) and click that.

View attachment 12266
4. Assuming you have placed kml in proper location, it should appear as in image with applicable name, select that.

View attachment 12267

5. If properly formatted kml, a new mission will open that you can edit, save etc.

Notes:
1. Before flying, verify your altitudes are correct or update them, also verify if MSL or AGL.
2. You might also have duplicate waypoints, you can clean those out as needed.
3. First time you try the above do it in an open area clear of obstructions, and verify altitude and waypoint settings, particular if in MSL vs. AGL to avoid surprises...

Good luck.
Click to expand...
Thanks GSCHULZUIO - Yes I have attempted that very process - The closest I have come to success is when I created a folder in GE and added waypoints and paths under that folder and then highlight the folder and Save Place As a kml file. When I try to load the kml file in AE I see the mission planning view but no waypoints or paths. I have made several attempts. It's possible that my process for creating the file in GE is not correct but i can't seem to create a file that will properly load into AE. I'm using an iPhone btw.

I updated this to include screenshots. (The reason that the terrain looks different in the Mission screen is because that is from applemaps,. I guess).

Any tips that would help me figure out where I went wrong would definitely be appreciated.
 

Attachments

  • 1.png
    1.png
    3.2 MB · Views: 5
  • 2.png
    2.png
    49 KB · Views: 5
  • IMG_3345.PNG
    IMG_3345.PNG
    188 KB · Views: 5
  • IMG_3346.PNG
    IMG_3346.PNG
    103.2 KB · Views: 5
  • Screenshot 2021-11-08 at 10.51.41 AM.jpg
    Screenshot 2021-11-08 at 10.51.41 AM.jpg
    89.8 KB · Views: 5
  • IMG_3350.PNG
    IMG_3350.PNG
    57.7 KB · Views: 5
  • IMG_3348.PNG
    IMG_3348.PNG
    1.1 MB · Views: 5
Last edited:
provide a custom Panorama function:
... make width and height in degrees settable (could be done by pointing the camera at opposite corners or by entering degrees)
... make camera settings definable (including burst or HDR shooting mode, for instance)
... allow option for disabling stitch process
 
Last edited:
  • Like
Reactions: gschulzuio
pwaitzman said:
How do you import a file with waypoints? I've tried importing kml's from google earth but have not yet been successful. Hopefully, I don't have the process down yet.
Click to expand...
Saw your note about the kml import using steps I mentioned other day not working with a GE kml you created. Went into GEP (should work with GE as well), created a folder with four waypoints, WPT1, WPT2, WPT3, WPT4. For each, assigned an altitude relative to ground (default is something else) in meters. Then saved the folder as a kml (note default is kmz). Copied the kml to app/device per my notes from other day and put in the autel explorer folder. Opened missions, imported kml, all was good, all four waypoint and their alt, saved it as a different name, etc.

The following is what the kml looks like:

<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2" xmlns:gx="http://www.google.com/kml/ext/2.2" xmlns:kml="http://www.opengis.net/kml/2.2" xmlns:atom="Atom Syndication Format namespace">
<Document>
<name>DowntownStillwater.kml</name>
<StyleMap id="m_ylw-pushpin">
<Pair>
<key>normal</key>
<styleUrl>#s_ylw-pushpin</styleUrl>
</Pair>
<Pair>
<key>highlight</key>
<styleUrl>#s_ylw-pushpin_hl</styleUrl>
</Pair>
</StyleMap>
<Style id="s_ylw-pushpin">
<IconStyle>
<scale>1.1</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
</Style>
<Style id="s_ylw-pushpin_hl">
<IconStyle>
<scale>1.3</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
</Style>
<Style id="s_ylw-pushpin_hl0">
<IconStyle>
<scale>1.3</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
</Style>
<StyleMap id="m_ylw-pushpin0">
<Pair>
<key>normal</key>
<styleUrl>#s_ylw-pushpin0</styleUrl>
</Pair>
<Pair>
<key>highlight</key>
<styleUrl>#s_ylw-pushpin_hl0</styleUrl>
</Pair>
</StyleMap>
<Style id="s_ylw-pushpin0">
<IconStyle>
<scale>1.1</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
</Style>
<Folder>
<name>DowntownStillwater</name>
<open>1</open>
<Placemark>
<name>WPT4</name>
<open>1</open>
<LookAt>
<longitude>-92.80122997210027</longitude>
<latitude>45.05551847171713</latitude>
<altitude>0</altitude>
<heading>1.582849244737425</heading>
<tilt>42.79317963865753</tilt>
<range>447.6557441501732</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-92.80341385667415,45.05549823202078,50.00000000000001</coordinates>
</Point>
</Placemark>
<Placemark>
<name>WPT3</name>
<open>1</open>
<LookAt>
<longitude>-92.80156942084959</longitude>
<latitude>45.0572025499004</latitude>
<altitude>0</altitude>
<heading>1.582609018330471</heading>
<tilt>42.7931787432212</tilt>
<range>447.5090078370976</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-92.79970861411709,45.05713786669462,70</coordinates>
</Point>
</Placemark>
<Placemark>
<name>WPT1</name>
<LookAt>
<longitude>-92.80372842165717</longitude>
<latitude>45.05861813038249</latitude>
<altitude>0</altitude>
<heading>1.581111387851459</heading>
<tilt>42.83385512269637</tilt>
<range>430.483021297643</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin0</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-92.80458492905071,45.05880671281025,39.99999999999999</coordinates>
</Point>
</Placemark>
<Placemark>
<name>WPT2</name>
<LookAt>
<longitude>-92.80353065241725</longitude>
<latitude>45.05759828154165</latitude>
<altitude>0</altitude>
<heading>1.5816972076382</heading>
<tilt>51.48706590935318</tilt>
<range>310.0276532931038</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin0</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-92.8045410805169,45.05727630966438,39.99999999999999</coordinates>
</Point>
</Placemark>
</Folder>
</Document>
</kml>
 
gschulzuio said:
Saw your note about the kml import using steps I mentioned other day not working with a GE kml you created. Went into GEP (should work with GE as well), created a folder with four waypoints, WPT1, WPT2, WPT3, WPT4. For each, assigned an altitude relative to ground (default is something else) in meters. Then saved the folder as a kml (note default is kmz). Copied the kml to app/device per my notes from other day and put in the autel explorer folder. Opened missions, imported kml, all was good, all four waypoint and their alt, saved it as a different name, etc.

The following is what the kml looks like:

<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2" xmlns:gx="http://www.google.com/kml/ext/2.2" xmlns:kml="http://www.opengis.net/kml/2.2" xmlns:atom="Atom Syndication Format namespace">
<Document>
<name>DowntownStillwater.kml</name>
<StyleMap id="m_ylw-pushpin">
<Pair>
<key>normal</key>
<styleUrl>#s_ylw-pushpin</styleUrl>
</Pair>
<Pair>
<key>highlight</key>
<styleUrl>#s_ylw-pushpin_hl</styleUrl>
</Pair>
</StyleMap>
<Style id="s_ylw-pushpin">
<IconStyle>
<scale>1.1</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
</Style>
<Style id="s_ylw-pushpin_hl">
<IconStyle>
<scale>1.3</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
</Style>
<Style id="s_ylw-pushpin_hl0">
<IconStyle>
<scale>1.3</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
</Style>
<StyleMap id="m_ylw-pushpin0">
<Pair>
<key>normal</key>
<styleUrl>#s_ylw-pushpin0</styleUrl>
</Pair>
<Pair>
<key>highlight</key>
<styleUrl>#s_ylw-pushpin_hl0</styleUrl>
</Pair>
</StyleMap>
<Style id="s_ylw-pushpin0">
<IconStyle>
<scale>1.1</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
</Style>
<Folder>
<name>DowntownStillwater</name>
<open>1</open>
<Placemark>
<name>WPT4</name>
<open>1</open>
<LookAt>
<longitude>-92.80122997210027</longitude>
<latitude>45.05551847171713</latitude>
<altitude>0</altitude>
<heading>1.582849244737425</heading>
<tilt>42.79317963865753</tilt>
<range>447.6557441501732</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-92.80341385667415,45.05549823202078,50.00000000000001</coordinates>
</Point>
</Placemark>
<Placemark>
<name>WPT3</name>
<open>1</open>
<LookAt>
<longitude>-92.80156942084959</longitude>
<latitude>45.0572025499004</latitude>
<altitude>0</altitude>
<heading>1.582609018330471</heading>
<tilt>42.7931787432212</tilt>
<range>447.5090078370976</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-92.79970861411709,45.05713786669462,70</coordinates>
</Point>
</Placemark>
<Placemark>
<name>WPT1</name>
<LookAt>
<longitude>-92.80372842165717</longitude>
<latitude>45.05861813038249</latitude>
<altitude>0</altitude>
<heading>1.581111387851459</heading>
<tilt>42.83385512269637</tilt>
<range>430.483021297643</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin0</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-92.80458492905071,45.05880671281025,39.99999999999999</coordinates>
</Point>
</Placemark>
<Placemark>
<name>WPT2</name>
<LookAt>
<longitude>-92.80353065241725</longitude>
<latitude>45.05759828154165</latitude>
<altitude>0</altitude>
<heading>1.5816972076382</heading>
<tilt>51.48706590935318</tilt>
<range>310.0276532931038</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin0</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-92.8045410805169,45.05727630966438,39.99999999999999</coordinates>
</Point>
</Placemark>
</Folder>
</Document>
</kml
Click to expand...
Yep - No luck - I performed the your same steps and got the same result that I saw before, When I try to load the kml file in AE I see the mission planning view but no waypoints or paths.

I think that I saw that the process crashes AE on an iPhone. I didn't get that result, but maybe there's an issue with AE in IOS reading kml files.
Here are the contents of my 4 waypoint file:

<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2" xmlns:gx="http://www.google.com/kml/ext/2.2" xmlns:kml="http://www.opengis.net/kml/2.2" xmlns:atom="Atom Syndication Format namespace">
<Document>
<name>Waypoints.kml</name>
<StyleMap id="m_ylw-pushpin">
<Pair>
<key>normal</key>
<styleUrl>#s_ylw-pushpin</styleUrl>
</Pair>
<Pair>
<key>highlight</key>
<styleUrl>#s_ylw-pushpin_hl</styleUrl>
</Pair>
</StyleMap>
<Style id="s_ylw-pushpin">
<IconStyle>
<scale>1.1</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
</Style>
<Style id="s_ylw-pushpin_hl">
<IconStyle>
<scale>1.3</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
</Style>
<Folder>
<name>Waypoints</name>
<open>1</open>
<Placemark>
<name>WPT1</name>
<LookAt>
<longitude>-87.80826797552166</longitude>
<latitude>34.82894786013029</latitude>
<altitude>0</altitude>
<heading>0.7546156834064845</heading>
<tilt>0</tilt>
<range>187.9451269149403</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-87.80830998954941,34.8289700518256,30</coordinates>
</Point>
</Placemark>
<Placemark>
<name>WPT2</name>
<LookAt>
<longitude>-87.80827805773586</longitude>
<latitude>34.82942683375924</latitude>
<altitude>0</altitude>
<heading>0.7546099191183637</heading>
<tilt>0</tilt>
<range>185.7607997272134</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-87.80812540741354,34.82896988887654,30</coordinates>
</Point>
</Placemark>
<Placemark>
<name>WPT3</name>
<LookAt>
<longitude>-87.80826797552166</longitude>
<latitude>34.82894786013029</latitude>
<altitude>0</altitude>
<heading>0.7546156834064845</heading>
<tilt>0</tilt>
<range>187.9451269149403</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-87.80810810466338,34.82875223258158,30</coordinates>
</Point>
</Placemark>
<Placemark>
<name>WPT4</name>
<LookAt>
<longitude>-87.80826797552166</longitude>
<latitude>34.82894786013029</latitude>
<altitude>0</altitude>
<heading>0.7546156834064845</heading>
<tilt>0</tilt>
<range>187.9451269149403</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-87.80831338401505,34.82875889578134,30</coordinates>
</Point>
</Placemark>
</Folder>
</Document>
</kml>
 
pwaitzman said:
Yep - No luck - I performed the your same steps and got the same result that I saw before, When I try to load the kml file in AE I see the mission planning view but no waypoints or paths.

I think that I saw that the process crashes AE on an iPhone. I didn't get that result, but maybe there's an issue with AE in IOS reading kml files.
Here are the contents of my 4 waypoint file:

<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2" xmlns:gx="http://www.google.com/kml/ext/2.2" xmlns:kml="http://www.opengis.net/kml/2.2" xmlns:atom="Atom Syndication Format namespace">
<Document>
<name>Waypoints.kml</name>
<StyleMap id="m_ylw-pushpin">
<Pair>
<key>normal</key>
<styleUrl>#s_ylw-pushpin</styleUrl>
</Pair>
<Pair>
<key>highlight</key>
<styleUrl>#s_ylw-pushpin_hl</styleUrl>
</Pair>
</StyleMap>
<Style id="s_ylw-pushpin">
<IconStyle>
<scale>1.1</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
</Style>
<Style id="s_ylw-pushpin_hl">
<IconStyle>
<scale>1.3</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
</Style>
<Folder>
<name>Waypoints</name>
<open>1</open>
<Placemark>
<name>WPT1</name>
<LookAt>
<longitude>-87.80826797552166</longitude>
<latitude>34.82894786013029</latitude>
<altitude>0</altitude>
<heading>0.7546156834064845</heading>
<tilt>0</tilt>
<range>187.9451269149403</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-87.80830998954941,34.8289700518256,30</coordinates>
</Point>
</Placemark>
<Placemark>
<name>WPT2</name>
<LookAt>
<longitude>-87.80827805773586</longitude>
<latitude>34.82942683375924</latitude>
<altitude>0</altitude>
<heading>0.7546099191183637</heading>
<tilt>0</tilt>
<range>185.7607997272134</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-87.80812540741354,34.82896988887654,30</coordinates>
</Point>
</Placemark>
<Placemark>
<name>WPT3</name>
<LookAt>
<longitude>-87.80826797552166</longitude>
<latitude>34.82894786013029</latitude>
<altitude>0</altitude>
<heading>0.7546156834064845</heading>
<tilt>0</tilt>
<range>187.9451269149403</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-87.80810810466338,34.82875223258158,30</coordinates>
</Point>
</Placemark>
<Placemark>
<name>WPT4</name>
<LookAt>
<longitude>-87.80826797552166</longitude>
<latitude>34.82894786013029</latitude>
<altitude>0</altitude>
<heading>0.7546156834064845</heading>
<tilt>0</tilt>
<range>187.9451269149403</range>
<gx:altitudeMode>relativeToSeaFloor</gx:altitudeMode>
</LookAt>
<styleUrl>#m_ylw-pushpin</styleUrl>
<Point>
<altitudeMode>relativeToGround</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-87.80831338401505,34.82875889578134,30</coordinates>
</Point>
</Placemark>
</Folder>
</Document>
</kml>
Click to expand...
Could be an ios issue, just load your kml with android 1.1.7.93 and it loaded ok, see image:Screenshot_20211109-073611_Autel Explorer.jpg
 
  • Like
Reactions: pwaitzman
gschulzuio said:
Could be an ios issue, just load your kml with android 1.1.7.93 and it loaded ok, see image:View attachment 12303
Click to expand...
Thanks - for the confirmation.

I loaded yours and got the same result as before. The mission screen opened but at my current location and with no waypoints.
And, btw, I'm using GEP (not GE as I earlier indicated) to create KML's.

This is beginning to sound more & more like a feature request. Luckily, we're in the right forum topic. Hopefully Autel sees this.
 

Attachments

  • Screenshot 2021-11-09 at 9.20.44 AM.jpg
    Screenshot 2021-11-09 at 9.20.44 AM.jpg
    356.1 KB · Views: 3
Last edited:
  • Like
Reactions: gschulzuio
pwaitzman said:
Thanks - for the confirmation.

I loaded yours and got the same result as before. The mission screen opened but at my current location and with no waypoints.
And, btw, I'm using GEP (not GE as I earlier indicated) to create KML's.

This is beginning to sound more & more like a feature request. Luckily, we're in the right forum topic. Hopefully Autel sees this.
Click to expand...
No worries, it might just be an ios bug vs feature request, either way, wish they would add the ability to export/save a mission (with waypoint actions, etc), and enable an improved import for missions, and then get it working on both ios and droid.
 
  • Like
Reactions: Ladiver and pwaitzman
advexure said:
Autel EVO II Pilots,

As our Advexure team and the Autel team continues to receive many different emails, calls, chats and messages with different feature requests for the EVO II. The goal of this thread is to create a centralized discussion and means of sharing feature requests, bugs and feedback on the feedback.

We are working in close coordination with the Autel team to share and advocate user feedback, requests and wishes for review and potential implementation. Both of our teams will monitor this thread closely and share updates and feedback regarding the requests submitted. Keep your request short, sweet and to the point, we will ask if further clarification is needed on a certain request.

Thank you for all of your input and contributions! :)

–The Advexure Team
Click to expand...
The ability to pan the camera left or right.
 
Is there a way to soften the stop motion of the drone or sticks like a speed ramp in editing to make them a smooth stop instead of a hard stop. It doesn't have to be a slow stop; just not hard.

I think this is what differentiates the DJI controls from the Autel controls.
 
  • Like
Reactions: AirStag, Andrew01 and gschulzuio
Eagle928 said:
Is there a way to soften the stop motion of the drone or sticks like a speed ramp in editing to make them a smooth stop instead of a hard stop. It doesn't have to be a slow stop; just not hard.

I think this is what differentiates the DJI controls from the Autel controls.
Click to expand...
Something more and beyond what is capable with basic stick adjustment settings assume?

This would be handy in other modes as well for example:
Vertical up and down
forward push in, pull back/push out
pan left/right (aircraft fly sideways)
pan with twist (aircraft stationary, twist from side to side)
gimbal up/down slow to fast, fast to slow
among others

Ideal would be to have available in standard camera modes, as well as in missions
 
  • Like
Reactions: Andrew01 and Eagle928
gschulzuio said:
Something more and beyond what is capable with basic stick adjustment settings assume?

This would be handy in other modes as well for example:
Vertical up and down
forward push in, pull back/push out
pan left/right (aircraft fly sideways)
pan with twist (aircraft stationary, twist from side to side)
gimbal up/down slow to fast, fast to slow
among others

Ideal would be to have available in standard camera modes, as well as in missions
Click to expand...
Yes. I'm thinking it would be across the board with every function of the sticks and scroll wheel and not adjustable other than, say, a smoothness setting. The idea, like I hope I made clear, is to stop the hard stop in all functional moves and replace with a smoother ramped stop.
 
Last edited:
  • Like
Reactions: AirStag and gschulzuio
I would add that reviewers of the new Nano and Lite drones appear to imply they have this built-in so maybe it would simply be a matter of copying some of the code to make the Evo 1 and 2 drones feel and act the same way in a FW update.
 
  • Like
Reactions: gschulzuio
How many times do we keep repeating our issues when Autel people are so thick headed and refuse to follow our help !
I have stopped video taping with Autel EVO 2 Pro due to Jerky movements. We are not all Drag Racers and we bought the Autel EVO2 Pro for smooth cinematic video coverage that they don't understand nor care to understand !
 

Similar threads

T
EVO II (Any/all version) and High Voltage transmission lines
Replies
3
Views
708
General Discussions
AirStag
AirStag
S
V2 Evo II Pro 6K
Replies
2
Views
833
EVO II Pro V2
ethelsnakes
E
TN Drone Services
Evo II V1/V2 Thermal Incompatibility
Replies
10
Views
1K
EVO II Dual
Adam I & Evo II
A
S
$4800 - Evo II Dual 640T Enterprise v3 (BRAND NEW, unopened)
Replies
9
Views
2K
Classifieds
SARty
S
GFields
UPDATE: EVO II Series V1 & V2 End of Life & Service
Replies
1
Views
1K
News
kenautelevo2pro
K

Latest threads

Members online

No members online now.
Total: 202 (members: 0, guests: 202)

Forum statistics

Threads
11,281
Messages
102,957
Members
9,880
Latest member
chuckster58