Was getting ready to fly my EVO II on Thanksgiving day and noticed there was a firmware update available. I downloaded it to my RC connected to my Android with the Autel EVO app on it. Knowing the drone has to be on to upload the firmware I turned it on (first mistake) indoors. Without any input from me the drone took off from my dining room table and (second mistake) I grabbed for it. Finally I got hold of it turned it on it side and it stopped. Off to the ER and 20+ stiches later decided to try again, this time outside. Again, it took off and went into a hover about 4 feet off the launch location. No response from the control sticks. Hit RTH and up it went to the RTH altitude and descended and landed in a normal RTH mode. The only thing I can figure is that the new firmware download had not finished downloading (giving rise to not being able to control it) but nothing I have found explains why it took off. I don't think I accidently hit the UP/DOWN automatic takeoff/land button, and I certainly didn't hit it on both occasions.
I let the firmware get completely processed via the controller/smartphone and got the ready to upload screen. Turned the drone on and it went through the upload process in what seemed like a normal manner. From that point it responded and flew normally.
Scoured the manual and the only thing I saw (p59 Chapter 5 Maintenance and Service) was that I initiated the firmware update via the controller/android rather than downloading to the SD card and inserting in the aircraft.
Has anyone else had any similar experience or can explain what I did wrong. (OK, in retrospect I probably should have not grabbed for it as it has omnidirectional obstacle avoidance and would have probably just hovered until I figured it out; but I wasn't thinking that quick)
I let the firmware get completely processed via the controller/smartphone and got the ready to upload screen. Turned the drone on and it went through the upload process in what seemed like a normal manner. From that point it responded and flew normally.
Scoured the manual and the only thing I saw (p59 Chapter 5 Maintenance and Service) was that I initiated the firmware update via the controller/android rather than downloading to the SD card and inserting in the aircraft.
Has anyone else had any similar experience or can explain what I did wrong. (OK, in retrospect I probably should have not grabbed for it as it has omnidirectional obstacle avoidance and would have probably just hovered until I figured it out; but I wasn't thinking that quick)