The whole day was like a mystery. I had a 16-minute flight in the morning just fine.
At home, I wanted to send the log to AutelRobotic, but I couldn't log in to AutelSky. I applied a forgotten password and name about 15 times. It didn't help, so I wrote for support. I tried again in the late afternoon but still couldn't log in.
Finally, I tried logging in with the old password and it was OK. However, the upload of the morning flight failed, so it seems that it does not exist, even though I have 4k video from the SD card and from my mobile phone.
I was alerted to the existence of a new firmware, so I went through the whole procedure - with no problems. Then I took the drone outside, in front of the house for a test so that I could go out into the field early the next morning.
I recalibrated the compass, IMEI, controller, and gimbal - no problems. The first start was just so up and down. On the second start, I probably went up until I received a confirmation about the setting of the new "homepoint".
I swerved a bit to the right and a few meters back. Satisfied I set the RTH .... and now I couldn't stop wondering. Following the announcement that the RTH will take place at the same height (or similar), the drone turned towards the roof of the house. When it started flying there, I tried to use the "PAUSE" button, but it didn't help. At the moment, the drone was above the roof, it started to fall, and all I could hear was the rumble of falling onto the roof and then falling to the ground.
The drone is scratched, the front sensors are displaced, and the motors work but the propellers are damaged. Although the gimbal is tested, it otherwise does not respond to commands from the controller. The battery was pulled out but the 256MB SD card popped up and I couldn't find it.
Although I have finished flying, I wonder if the error was in the firmware upgrade (it went normally for many users) or in me. I, therefore, ask for your opinions, advice, and experience. I will be happy to add the necessary information. From the log of both short flights, it can be seen that I kept the right stick in the left position for the entire duration of the flight, which is nonsense. The log of every normal flight starts - both sticks at an angle to each other.
Today I was again with the injured drone to test the RTH function - without problems, several times.
PrnScr
Expensive entertainment - for pensioners
Edit:
After reading the new enKoDed contribution, where the emphasis is on updating the batteries, I did one more test. I still have one battery left that has not been updated. I refused the update and tried to fly it. No difference, no disaster!
It's paradoxical that I don't know how to force her to decline now. Is there any possibility for an additional update?
At home, I wanted to send the log to AutelRobotic, but I couldn't log in to AutelSky. I applied a forgotten password and name about 15 times. It didn't help, so I wrote for support. I tried again in the late afternoon but still couldn't log in.
Finally, I tried logging in with the old password and it was OK. However, the upload of the morning flight failed, so it seems that it does not exist, even though I have 4k video from the SD card and from my mobile phone.
I was alerted to the existence of a new firmware, so I went through the whole procedure - with no problems. Then I took the drone outside, in front of the house for a test so that I could go out into the field early the next morning.
I recalibrated the compass, IMEI, controller, and gimbal - no problems. The first start was just so up and down. On the second start, I probably went up until I received a confirmation about the setting of the new "homepoint".
I swerved a bit to the right and a few meters back. Satisfied I set the RTH .... and now I couldn't stop wondering. Following the announcement that the RTH will take place at the same height (or similar), the drone turned towards the roof of the house. When it started flying there, I tried to use the "PAUSE" button, but it didn't help. At the moment, the drone was above the roof, it started to fall, and all I could hear was the rumble of falling onto the roof and then falling to the ground.
The drone is scratched, the front sensors are displaced, and the motors work but the propellers are damaged. Although the gimbal is tested, it otherwise does not respond to commands from the controller. The battery was pulled out but the 256MB SD card popped up and I couldn't find it.
Although I have finished flying, I wonder if the error was in the firmware upgrade (it went normally for many users) or in me. I, therefore, ask for your opinions, advice, and experience. I will be happy to add the necessary information. From the log of both short flights, it can be seen that I kept the right stick in the left position for the entire duration of the flight, which is nonsense. The log of every normal flight starts - both sticks at an angle to each other.
Today I was again with the injured drone to test the RTH function - without problems, several times.
PrnScr
Expensive entertainment - for pensioners
Edit:
After reading the new enKoDed contribution, where the emphasis is on updating the batteries, I did one more test. I still have one battery left that has not been updated. I refused the update and tried to fly it. No difference, no disaster!
It's paradoxical that I don't know how to force her to decline now. Is there any possibility for an additional update?
Last edited by a moderator:
