Autel Evo II Pro Beta Firmware 2.5.11 and Beta iOS and Android Autel Explorer App Testing and Bug Report

[TheMann58]

Autel Evo II Pro Beta Firmware 2.5.11 and Beta iOS and Android Autel Explorer App Testing and Bug Report (Revised)

After successfully updating firmware of Autel Evo II Pro to beta version 2.5.11, I did the following:

• Performed two IMU Calibrations with aircraft on a stable, perfectly-level granite countertop in my kitchen
• Performed a compass calibration outdoors over grass using new 3-axis calibration procedure
• Performed two gimbal calibrations with aircraft sitting on a stable, perfectly-level granite countertop in my kitchen

Beta Firmware Version 2.5.11 dated Oct-09-2020
Observations

1. Number of reported GPS satellites by the Autel Explorer app in two separate locations (near my house and in an open grassy field adjacent to a park) has increased by approx. 6 vs. number of GPS satellites reported in the same locations with previous versions of firmware including 2.5.0. After installing beta 2.5.11 firmware and performing two IMU calibrations and a compass calibration, Autel Explorer app now reports 13-18 GPS satellites are visible with the aircraft on the ground and 23-25 GPS satellites are visible when the aircraft is above 50 feet altitude at both locations. Wow!
2. Aircraft no longer attempts to land 25-150 feet from takeoff home point on RTH as it regularly did with version 2.5.0 firmware. This improved GPS performance may be due to the new ability provided by the beta 2.5.11 firmware to perform a manual IMU calibration, which I did before flight testing.
3. With precision landing turned on in the app, aircraft consistently lands within 3 inches of takeoff home point correcting its position several times during final 30 feet of descent. Excellent!
4. Autel Evo II Pro camera autofocus works extremely well with sharp focus on center image in video frame achieved within less than a second and focus readjustment occurring as needed during flight.
5. Very stable aircraft hover observed both a few feet above ground and at much higher elevations - recorded video appears as stable as if camera were mounted on a rigid tripod.
6. When hovering or flying forward or backward at standard or ludicrous speed modes, very level gimbal horizon was observed. Excellent!
7. 4K 60 fps video recorded during flights is crisp, highly-detailed and sharply focused. Photos are equally detailed.

Firmware Bugs

1. GPS signal strength is not being measured/calculated and/or reported correctly (in my opinion) for graphical display in bar format on the Autel Evo Remote Control (RC). This was also the case for previous versions of Evo II firmware. For example, with 23-25 GPS satellites(!) reported and logged throughout flight records during multiple flights at 400 feet elevation in an open area on a sunny day, the RC display and the flight record (Android app) logs indicate only a maximum of 3 out of 5 bars of satellite signal strength. This does not make sense. It is not clear how GPS signal level is measured or quantified as bars of signal strength. I realize that the number of visible GPS satellites may not be directly a function of the GPS radio signal level detected by the GPS sensor module. On the other hand, assumming no sun spot activity, I can’t envision a scenario where a stronger GPS signal would be received than with aircraft in an open field at 400 feet elevation on a clear, sunny day! Unless, perhaps, the aircraft was launched from the top of a mountain! This bug is, I believe, the main cause of Bug #2.
2. On EVERY takeoff, I get a “GPS signal weak” warning message. This is true even after allowing the aircraft to sit on the ground for up to 5 minutes after battery power on, and even on the 5th takeoff on the same battery with the aircraft battery running continuously for 25 minutes, in an open field on a clear, sunny day with 18 satellites reported on the beta Explorer app when the aircraft is on the ground and 23-25 GPS satellites visible with the aircraft 50+ feet above ground.
3. When aircraft is rotating clockwise or counterclockwise or when the aircraft is turning left or right during forward flight, gimbal horizon tilts noticeably, but the gimbal will return to level horizon when turning stops. Further improvement in gimbal control performance during typical flight maneuvers is needed here.
4. With full obstacle avoidance turned ON, Evo II Pro aircraft is slow to accelerate even with full forward right stick and even when aircraft is at 200 feet elevation with no obstacles within 100 feet above, below or for 360 degrees around aircraft. In addition, the Evo II aircraft will intermittently slow down with full forward stick in standard speed mode (22 mph max speed) to as slow as 6 mph as if it were sensing an approaching obstacle and then slowly accelerate again. This results in less than cinematic video. I believe this MAY be an unavoidable consequence of aircraft having two OA cameras pointing in six directions (up, down, forward, backward, left and right) and sunlight on a clear day occasionally shining nearly directly into one of those 6 sets of cameras, thus confusing the firmware’s interpretation of the OA sensor’s data. To avoid this random deceleration/acceleration issue, OA can be disabled, which is now facilitated by the OA switch icon at the upper right of the beta Explorer app display, but then this useful aircraft safety system is bypassed.
5. Both the standard Orbit flight function (where pilot must first fly the aircraft directly over the center of object to be orbited) and the Program Orbit flight function (where target orbit object is selected by drawing a box around it with your finger on the Explorere app screen) are plagued by the following two performance issues:

• First, there is a quite noticeable jerk to the right at the beginning of each clockwise orbit as the app reports that the aircraft is calculating its orbit trajectory.
• Second, both the standard Orbit and Smart Orbit flight function fail to maintain the target orbit center in the center of the video frame in most, but not all, orbit flights. This is most apparent during orbits of several hundred feet diameter. By the 90 degree point in the orbit, the target object is slightly right of the center of the video frame; by the 180° point in the orbit, the target orbit center is noticeably above the center of the current video frame; and by the 270° point in the orbit, the original orbit center is significantly to the left of what is now the center of the video frame.
• This less-than-perfectly-centered orbit flight performance occurs on some standard Orbits and most Program Orbits. In closely reviewing the aircraft flight path and orientation as captured in flight records, the aircraft is indeed making a nearly perfect circular orbit around the target orbit center (great!), but the aircraft is pointing ever so slightly but increasingly to a position behind the original orbit center at the time it was identified prior to orbit initiation. This is most apparent with large orbit diameters of several hundred feet and if orbit diameter is increased during orbit flight. This is unfortunate, but certainly correctable by further firmware tweaking.

Autel Explorer App Beta iOS Version V1.7.5 dated Oct-09-2020
Bugs

1. During attempted synchronization of flight records while my iPhone 10Xs is connected to high-speed internet at home, message “No internet connection” was displayed and synchronization failed multiple times over two days. Later, synchronization succeeded and all 74 flight records were synchronized and displayed. Perhaps the Autel Flight Record server was down?
2. Not all flight records appear in chronological order - particularly, but not consistently, flights made on the current date or the day before appear out of sequence towards the bottom of the list of flight records. Why? A day or two later, these misplaced flight records appear in the correct chronological order after additional flights are logged and synchronized to the cloud.
3. Bars of GPS signal strength are not logged correctly in flight records - they show as 0 bars of GPS signal strength next to the number of GPS satellites. In addition, when viewing flight records on an iOS device that were originally recorded when running the beta Autel Explorer app on an Android device, the bars of GPS signal strength are reduced from the typical, in my case, 3 bars logged in flight records viewed on the Android beta app to 0 or 1 bar on the iOS beta app flight records. Again, flight records recorded on the iOS version of the beta Explorer app record as zero bars of GPS signal strength when there were three bars displayed on the RC during the flight.
4. Program Orbit function consistently fails to initiate on the iOS beta app running on my Apple iPhone Xs due to reported “Weak GPS signal” even though RC is currently reporting 23-25 satellites and 3 bars of GPS signal strength. This does NOT happen when using the latest beta Android version app. I believe this may be due to the GPS signal strength being incorrectly calculated as low in the firmware (firmware bug #1) and then further under-reported in the iOS beta app (iOS app bug #3) as evidenced in flight records.
5. In addition to the GPS signal strength being calculated incorrectly in the latest firmware as well as previous firmware versions (see firmware Bug #1), the incorrectly-calculated (in my opinion) GPS signal strength is then significantly under-reported by the iOS beta app - a double whammy. In flight records that are recorded using the Autel Explorer beta app running under iOS, the bars of GPS signal strength throughout the flight are consistently zero, i.e., no bars of GPS signal strength reported although RC displayed typically 3 bars during the actual flight. As noted above, If you are reviewing a flight record that was originally recorded on a device running the Android beta app of Autel Explorer, the GPS bars of signal strength show up as zero or one bar instead of the three bars that were recorded in the Autel Explorer Android version beta app.
6. When flight records recorded using an Android device and the Android Autel Explorer beta app are synchronized to and then viewed on an Apple phone or iPad running the iOS beta Autel Explorer app, the distance from home point is erroneously displayed as starting at 6569.83 miles from Home!!! This is true even though the Android device GPS sensor has correctly and accurately got a lock on Home Point and is linked to a WiFi hotspot to get real-time Google map data for current flight. The distance from home point continues to display correctly in flight records viewed using the Android beta version of the Autel Explorer app even after multiple flight record synchronizations.

Autel Explorer App Beta Android Version V1.1.7.8 dated Oct-11-2020
Bugs

1. After 71 of my flight records sync and the message “Synchronization Completed” is displayed, no flight records were displayed and the screen message “No flight records are found” is displayed. After flying three additional flights, synchronization now shows 74 flights synched but only the most recent three flights appear before and after “synchronization completed” is displayed. After clearing app data, deleting Autel Explorer app and reinstalling beta app, all 74 flight records are reported to be synchronized, but, again, the “No flight records are found” message appears after “Synchronization Completed” is displayed. List of flight records is now blank. The following day, after completing another 7 flights for a total of 81 flights, only the 7 flight records recorded after the beta Autel Explorer app was reinstalled appear in the list of flight records following synchronization although all 81 flights are reported as successfully synchronized. Very strange. Note, however, that after synchronization all flight records (both old and new) are displayed on the beta iOS version of the Autel Explorer app. That's strike one on accurate flight record syncing and data preservation.

Autel Explorer App Beta Android Version V1.1.7.9 dated Oct-13-2020
Bugs

1. After clearing app data, uninstalling Autel Explorer App Beta Android Version V1.1.7.8 and installing Autel Explorer App Beta Android Version V1.1.7.9, and synching my 82 flight records, all 82 flight records now appear in flight record list, BUT all flight records logged prior to Oct-11-2020 are erroneously dated "01/01/1970 00:00:00" and in the flight record list: the flight distance displays as "0ft," flight time displays as "0s," maximum altitude displays as "-3281ft," # of pictures taken displays as "0" and the recorded video length displays as "00:00." Not good! Fortunately, when viewing these "older" individual flight records, the gps Google map flight path, # of GPS satellites, bars of GPS signal strength, altitude, speed, flight length, battery level, distance flown, and distance from home point data throughout the flight appear intact, but the flight date is again erroneously shown as "01/01/1970" and the flight location is "Unknown Place." That's strike two on accurate flight record syncing and data preservation.

 

[parkgt]

Thanks for the detailed analysis and report. It is disappointing to see so many issues still remaining. The orbit performance you describe is also sadly what I found; making it of little value.

Autel has yet to make the Pro into a true Pro tool IMO. Great camera with a craft plagued by too many issues still. My M2P is still a more consistent trustworthy platform.

 

[alex_markov]

...

1. After clearing app data, uninstalling Autel Explorer App Beta Android Version V1.1.7.8 and installing Autel Explorer App Beta Android Version V1.1.7.9, and synching my 82 flight records, all 82 flight records now appear in flight record list, BUT all flight records logged prior to Oct-11-2020 are erroneously dated "01/01/1970 00:00:00" and in the flight record list: the flight distance displays as "0ft," flight time displays as "0s," maximum altitude displays as "-3281ft," # of pictures taken displays as "0" and the recorded video length displays as "00:00." Not good! Fortunately, when viewing these "older" individual flight records, the gps Google map flight path, # of GPS satellites, bars of GPS signal strength, altitude, speed, flight length, battery level, distance flown, and distance from home point data throughout the flight appear intact, but the flight date is again erroneously shown as "01/01/1970" and the flight location is "Unknown Place." That's strike two on accurate flight record syncing and data preservation.

Just to illustrate

 

[TheMann58]

Just to illustrate

View attachment 8763

Thanks, Alex. I’m glad (sort of) that you’re seeing the same thing with the older flight records. Fortunately, the records stored in the cloud server don’t appear to have been corrupted, as they still appear correctly on my iPad. I hope this is only a data formatting glitch just in the beta Android 1.1.7.9 Explorer app. But, I’m not synching records from my Android device until this issue is resolved.

 

[Gizmodrones]

I am brand new to Autel and today I installed the latest Evo Beta software and I am happy to report that the drift problem seems to be fixed. I flew in strong winds today and the Evo flight was rock solid from beginning to end without any nervous moments. After syncing my log (Android), today's log is still correct however prior logs downloaded from the cloud have lost their data and the date is 1970.

 

[bseasmd]

Excellent post - thanks for being so thorough.

I'm having similar log issues, for what it's worth.

I haven't flown with the firmware and Explorer updates just yet, but I did notice that they've added an artificial horizon (accessed by pulling the map out and tapping the icon in the upper left corner). I always found this feature handy with my old DJI, and I'd emailed Autel asking if they could add this for the Evo I; I'm glad they finally added it.

 

[Quad808]

You have a really, R E A L L Y old Evo II. 1970. wow. ?

 

[darkproximity]

when you look at your flight paths do yours appear odd in any way? i recently updated and flew today and noticed a few things that were off about mine.

My altitude was reported incorrectly at least in a few instances where it showed me below my take off point where i couldn't have possibly been lower. It also showed at one point that i was higher than 400ft which i did not go above.

Finally watching the flight path itself it shows very "blocky" movement as if i were only using the right stick to move. The lines were very straight with 90° bends. Not sure if this is normal.

 

[mdenhartog]

Have a customer that has updated to 2.5.11 now he has failure of all 4 ESCs, I believe the Firmware to be corrupt. We are currently trying to roll back the firmware and reinstall it. Has anyone else had these type issues?

 

[mdenhartog]

I have been told by Autel support that rolling back firmware is no longer possible. Does anyone have any idea how to clear the install 100% and refresh it.

 

[darkproximity]

Have a customer that has updated to 2.5.11 now he has failure of all 4 ESCs, I believe the Firmware to be corrupt. We are currently trying to roll back the firmware and reinstall it. Has anyone else had these type issues?View attachment 8860

Do you know how to generate an md5sum for the firmware binary file? If so I can post the md5sum of the firmware i downloaded that flashed successfully for me.

If you're on windows 10, navigate to the folder the firmware bin is located, hold shift and right click, select open powershell here.

in powershell type:

get-filehash -algorithm md5 Model

Once you've typed Model hit the tab key and it will autocomplete the filename. Then hit enter. This will produce a unique hash for the file, it should be A8E729919985A43BD7B98C8D0B79BB37. if it is not then the file is different from the one I downloaded.

 

[Florida Drone Supply]

D. If you can try the above, I will continue to see what I can find from Autel support.

 

[PingSpike]

I get the same hash for v2.5.11 : ping-spike/AutelEvo2Firmware

?

 

[Florida Drone Supply]

PingSpike what did you do to resolve? Were you able to roll it back, and reinstall?

 

[Ansia]

I have been told by Autel support that rolling back firmware is no longer possible. Does anyone have any idea how to clear the install 100% and refresh it.

Do a search on these forums. There is a way to rollback the firmware thanks to @Quad808 and his team.

 

[Gizmodrones]

I was running the latest Beta version and the latest firmware upgrade message popped up on the Android app however the upgrade failed for me so I downloaded the latest upgrade from the Autel downloads page, copied the file to the SD card, inserted the card back into the drone, rebooted controller and then then drone (in that order, don't connect your phone) and the latest firmware upgrade worked. Once upgraded you have to do it for each battery. My upgrade was successful although I haven't flown it yet due to the weather. Also the Android app keeps saying an upgrade is available but I have already upgraded. Tried the upgrade a few times and it was successful each time but the message kept coming up.

 

[lukappaseidue]

Autel Evo II Pro Beta Firmware 2.5.11 and Beta iOS and Android Autel Explorer App Testing and Bug Report (Revised)

After successfully updating firmware of Autel Evo II Pro to beta version 2.5.11, I did the following:

• Performed two IMU Calibrations with aircraft on a stable, perfectly-level granite countertop in my kitchen
• Performed a compass calibration outdoors over grass using new 3-axis calibration procedure
• Performed two gimbal calibrations with aircraft sitting on a stable, perfectly-level granite countertop in my kitchen

Beta Firmware Version 2.5.11 dated Oct-09-2020
Observations

1. Number of reported GPS satellites by the Autel Explorer app in two separate locations (near my house and in an open grassy field adjacent to a park) has increased by approx. 6 vs. number of GPS satellites reported in the same locations with previous versions of firmware including 2.5.0. After installing beta 2.5.11 firmware and performing two IMU calibrations and a compass calibration, Autel Explorer app now reports 13-18 GPS satellites are visible with the aircraft on the ground and 23-25 GPS satellites are visible when the aircraft is above 50 feet altitude at both locations. Wow!
2. Aircraft no longer attempts to land 25-150 feet from takeoff home point on RTH as it regularly did with version 2.5.0 firmware. This improved GPS performance may be due to the new ability provided by the beta 2.5.11 firmware to perform a manual IMU calibration, which I did before flight testing.
3. With precision landing turned on in the app, aircraft consistently lands within 3 inches of takeoff home point correcting its position several times during final 30 feet of descent. Excellent!
4. Autel Evo II Pro camera autofocus works extremely well with sharp focus on center image in video frame achieved within less than a second and focus readjustment occurring as needed during flight.
5. Very stable aircraft hover observed both a few feet above ground and at much higher elevations - recorded video appears as stable as if camera were mounted on a rigid tripod.
6. When hovering or flying forward or backward at standard or ludicrous speed modes, very level gimbal horizon was observed. Excellent!
7. 4K 60 fps video recorded during flights is crisp, highly-detailed and sharply focused. Photos are equally detailed.

Firmware Bugs

1. GPS signal strength is not being measured/calculated and/or reported correctly (in my opinion) for graphical display in bar format on the Autel Evo Remote Control (RC). This was also the case for previous versions of Evo II firmware. For example, with 23-25 GPS satellites(!) reported and logged throughout flight records during multiple flights at 400 feet elevation in an open area on a sunny day, the RC display and the flight record (Android app) logs indicate only a maximum of 3 out of 5 bars of satellite signal strength. This does not make sense. It is not clear how GPS signal level is measured or quantified as bars of signal strength. I realize that the number of visible GPS satellites may not be directly a function of the GPS radio signal level detected by the GPS sensor module. On the other hand, assumming no sun spot activity, I can’t envision a scenario where a stronger GPS signal would be received than with aircraft in an open field at 400 feet elevation on a clear, sunny day! Unless, perhaps, the aircraft was launched from the top of a mountain! This bug is, I believe, the main cause of Bug #2.
2. On EVERY takeoff, I get a “GPS signal weak” warning message. This is true even after allowing the aircraft to sit on the ground for up to 5 minutes after battery power on, and even on the 5th takeoff on the same battery with the aircraft battery running continuously for 25 minutes, in an open field on a clear, sunny day with 18 satellites reported on the beta Explorer app when the aircraft is on the ground and 23-25 GPS satellites visible with the aircraft 50+ feet above ground.
3. When aircraft is rotating clockwise or counterclockwise or when the aircraft is turning left or right during forward flight, gimbal horizon tilts noticeably, but the gimbal will return to level horizon when turning stops. Further improvement in gimbal control performance during typical flight maneuvers is needed here.
4. With full obstacle avoidance turned ON, Evo II Pro aircraft is slow to accelerate even with full forward right stick and even when aircraft is at 200 feet elevation with no obstacles within 100 feet above, below or for 360 degrees around aircraft. In addition, the Evo II aircraft will intermittently slow down with full forward stick in standard speed mode (22 mph max speed) to as slow as 6 mph as if it were sensing an approaching obstacle and then slowly accelerate again. This results in less than cinematic video. I believe this MAY be an unavoidable consequence of aircraft having two OA cameras pointing in six directions (up, down, forward, backward, left and right) and sunlight on a clear day occasionally shining nearly directly into one of those 6 sets of cameras, thus confusing the firmware’s interpretation of the OA sensor’s data. To avoid this random deceleration/acceleration issue, OA can be disabled, which is now facilitated by the OA switch icon at the upper right of the beta Explorer app display, but then this useful aircraft safety system is bypassed.
5. Both the standard Orbit flight function (where pilot must first fly the aircraft directly over the center of object to be orbited) and the Program Orbit flight function (where target orbit object is selected by drawing a box around it with your finger on the Explorere app screen) are plagued by the following two performance issues:

• First, there is a quite noticeable jerk to the right at the beginning of each clockwise orbit as the app reports that the aircraft is calculating its orbit trajectory.
• Second, both the standard Orbit and Smart Orbit flight function fail to maintain the target orbit center in the center of the video frame in most, but not all, orbit flights. This is most apparent during orbits of several hundred feet diameter. By the 90 degree point in the orbit, the target object is slightly right of the center of the video frame; by the 180° point in the orbit, the target orbit center is noticeably above the center of the current video frame; and by the 270° point in the orbit, the original orbit center is significantly to the left of what is now the center of the video frame.
• This less-than-perfectly-centered orbit flight performance occurs on some standard Orbits and most Program Orbits. In closely reviewing the aircraft flight path and orientation as captured in flight records, the aircraft is indeed making a nearly perfect circular orbit around the target orbit center (great!), but the aircraft is pointing ever so slightly but increasingly to a position behind the original orbit center at the time it was identified prior to orbit initiation. This is most apparent with large orbit diameters of several hundred feet and if orbit diameter is increased during orbit flight. This is unfortunate, but certainly correctable by further firmware tweaking.

Autel Explorer App Beta iOS Version V1.7.5 dated Oct-09-2020
Bugs

1. During attempted synchronization of flight records while my iPhone 10Xs is connected to high-speed internet at home, message “No internet connection” was displayed and synchronization failed multiple times over two days. Later, synchronization succeeded and all 74 flight records were synchronized and displayed. Perhaps the Autel Flight Record server was down?
2. Not all flight records appear in chronological order - particularly, but not consistently, flights made on the current date or the day before appear out of sequence towards the bottom of the list of flight records. Why? A day or two later, these misplaced flight records appear in the correct chronological order after additional flights are logged and synchronized to the cloud.
3. Bars of GPS signal strength are not logged correctly in flight records - they show as 0 bars of GPS signal strength next to the number of GPS satellites. In addition, when viewing flight records on an iOS device that were originally recorded when running the beta Autel Explorer app on an Android device, the bars of GPS signal strength are reduced from the typical, in my case, 3 bars logged in flight records viewed on the Android beta app to 0 or 1 bar on the iOS beta app flight records. Again, flight records recorded on the iOS version of the beta Explorer app record as zero bars of GPS signal strength when there were three bars displayed on the RC during the flight.
4. Program Orbit function consistently fails to initiate on the iOS beta app running on my Apple iPhone Xs due to reported “Weak GPS signal” even though RC is currently reporting 23-25 satellites and 3 bars of GPS signal strength. This does NOT happen when using the latest beta Android version app. I believe this may be due to the GPS signal strength being incorrectly calculated as low in the firmware (firmware bug #1) and then further under-reported in the iOS beta app (iOS app bug #3) as evidenced in flight records.
5. In addition to the GPS signal strength being calculated incorrectly in the latest firmware as well as previous firmware versions (see firmware Bug #1), the incorrectly-calculated (in my opinion) GPS signal strength is then significantly under-reported by the iOS beta app - a double whammy. In flight records that are recorded using the Autel Explorer beta app running under iOS, the bars of GPS signal strength throughout the flight are consistently zero, i.e., no bars of GPS signal strength reported although RC displayed typically 3 bars during the actual flight. As noted above, If you are reviewing a flight record that was originally recorded on a device running the Android beta app of Autel Explorer, the GPS bars of signal strength show up as zero or one bar instead of the three bars that were recorded in the Autel Explorer Android version beta app.
6. When flight records recorded using an Android device and the Android Autel Explorer beta app are synchronized to and then viewed on an Apple phone or iPad running the iOS beta Autel Explorer app, the distance from home point is erroneously displayed as starting at 6569.83 miles from Home!!! This is true even though the Android device GPS sensor has correctly and accurately got a lock on Home Point and is linked to a WiFi hotspot to get real-time Google map data for current flight. The distance from home point continues to display correctly in flight records viewed using the Android beta version of the Autel Explorer app even after multiple flight record synchronizations.

Autel Explorer App Beta Android Version V1.1.7.8 dated Oct-11-2020
Bugs

1. After 71 of my flight records sync and the message “Synchronization Completed” is displayed, no flight records were displayed and the screen message “No flight records are found” is displayed. After flying three additional flights, synchronization now shows 74 flights synched but only the most recent three flights appear before and after “synchronization completed” is displayed. After clearing app data, deleting Autel Explorer app and reinstalling beta app, all 74 flight records are reported to be synchronized, but, again, the “No flight records are found” message appears after “Synchronization Completed” is displayed. List of flight records is now blank. The following day, after completing another 7 flights for a total of 81 flights, only the 7 flight records recorded after the beta Autel Explorer app was reinstalled appear in the list of flight records following synchronization although all 81 flights are reported as successfully synchronized. Very strange. Note, however, that after synchronization all flight records (both old and new) are displayed on the beta iOS version of the Autel Explorer app. That's strike one on accurate flight record syncing and data preservation.

Autel Explorer App Beta Android Version V1.1.7.9 dated Oct-13-2020
Bugs

1. After clearing app data, uninstalling Autel Explorer App Beta Android Version V1.1.7.8 and installing Autel Explorer App Beta Android Version V1.1.7.9, and synching my 82 flight records, all 82 flight records now appear in flight record list, BUT all flight records logged prior to Oct-11-2020 are erroneously dated "01/01/1970 00:00:00" and in the flight record list: the flight distance displays as "0ft," flight time displays as "0s," maximum altitude displays as "-3281ft," # of pictures taken displays as "0" and the recorded video length displays as "00:00." Not good! Fortunately, when viewing these "older" individual flight records, the gps Google map flight path, # of GPS satellites, bars of GPS signal strength, altitude, speed, flight length, battery level, distance flown, and distance from home point data throughout the flight appear intact, but the flight date is again erroneously shown as "01/01/1970" and the flight location is "Unknown Place." That's strike two on accurate flight record syncing and data preservation.

about this issue
4)

• With full obstacle avoidance turned ON, Evo II Pro aircraft is slow to accelerate even with full forward right stick and even when aircraft is at 200 feet elevation with no obstacles within 100 feet above, below or for 360 degrees around aircraft. In addition, the Evo II aircraft will intermittently slow down with full forward stick in standard speed mode (22 mph max speed) to as slow as 6 mph as if it were sensing an approaching obstacle and then slowly accelerate again. This results in less than cinematic video. I believe this MAY be an unavoidable consequence of aircraft having two OA cameras pointing in six directions (up, down, forward, backward, left and right) and sunlight on a clear day occasionally shining nearly directly into one of those 6 sets of cameras, thus confusing the firmware’s interpretation of the OA sensor’s data. To avoid this random deceleration/acceleration issue, OA can be disabled, which is now facilitated by the OA switch icon at the upper right of the beta Explorer app display, but then this useful aircraft safety system is bypassed.

here the fix (for ANDROID)
Synchronize your data if you want/need
: go to settings - APP - AUTEL EXPLORER - :
1) clear cache,
2) clear ALL DATA
3) unistall AUTEL EXPLORER
4) with a file manager go to the Android device root and delete EXPLORER folder (check, before deleting, that it is related to Autel app - it is)
5) reinstall the latest app (beta or stable)
THIS STEPS have to be followed every time we update the app.

NEW BUG AUTEL EXPLORER APP (iOS Version)
Changing from 10 mhz to 20 mhz, try to take photos and than switch to video: the remote controller disconnect from the drone and RTH is engaged: After about 20 seconds, the connection is restabilished

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[Seated_Perspectives]

about this issue
4)

• With full obstacle avoidance turned ON, Evo II Pro aircraft is slow to accelerate even with full forward right stick and even when aircraft is at 200 feet elevation with no obstacles within 100 feet above, below or for 360 degrees around aircraft. In addition, the Evo II aircraft will intermittently slow down with full forward stick in standard speed mode (22 mph max speed) to as slow as 6 mph as if it were sensing an approaching obstacle and then slowly accelerate again. This results in less than cinematic video. I believe this MAY be an unavoidable consequence of aircraft having two OA cameras pointing in six directions (up, down, forward, backward, left and right) and sunlight on a clear day occasionally shining nearly directly into one of those 6 sets of cameras, thus confusing the firmware’s interpretation of the OA sensor’s data. To avoid this random deceleration/acceleration issue, OA can be disabled, which is now facilitated by the OA switch icon at the upper right of the beta Explorer app display, but then this useful aircraft safety system is bypassed.

here the fix (for ANDROID)
Synchronize your data if you want/need
: go to settings - APP - AUTEL EXPLORER - :
1) clear cache,
2) clear ALL DATA
3) unistall AUTEL EXPLORER
4) with a file manager go to the Android device root and delete EXPLORER folder (check, before deleting, that it is related to Autel app - it is)
5) reinstall the latest app (beta or stable)
THIS STEPS have to be followed every time we update the app.

NEW BUG AUTEL EXPLORER APP (iOS Version)
Changing from 10 mhz to 20 mhz, try to take photos and than switch to video: the remote controller disconnect from the drone and RTH is engaged: After about 20 seconds, the connection is restabilished

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

The Facebook evo group is filling up fast with people who have recreated this 10mhz disconnect bug, some are even reproducing it on Android. Seems like a rather serious safety issue to me, some reporting no reconnect until the drone is completely rebooted...at this point I'm legitimatly afraid to fly this thing anymore, this is getting to be a comedy of errors with Autels updates.

 

[lukappaseidue]

The Facebook evo group is filling up fast with people who have recreated this 10mhz disconnect bug, some are even reproducing it on Android. Seems like a rather serious safety issue to me, some reporting no reconnect until the drone is completely rebooted...at this point I'm legitimatly afraid to fly this thing anymore, this is getting to be a comedy of errors with Autels updates.

I can confirm this
If you set 20mhz, RC and Aircraft will disconnect, but after about 20 seconds the connection is restablished
If you set 5mhz RC and Aircraft will disconnect, but no more connection: You need to restart Aircraft

 

[charmin]

I was running the latest Beta version and the latest firmware upgrade message popped up on the Android app however the upgrade failed for me so I downloaded the latest upgrade from the Autel downloads page, copied the file to the SD card, inserted the card back into the drone, rebooted controller and then then drone (in that order, don't connect your phone) and the latest firmware upgrade worked. Once upgraded you have to do it for each battery. My upgrade was successful although I haven't flown it yet due to the weather. Also the Android app keeps saying an upgrade is available but I have already upgraded. Tried the upgrade a few times and it was successful each time but the message kept coming up.

I have had the reminder saying upgrade available just about every time I update, as long as you have done it take no notice, it will disappear eventually. It seems to be more prolific if using a tablet rather than a phone, don't ask me why. Use it to good advantage as each battery will need to be installed during the upgrade to get the battery up to latest version.