Well, well, well. I just experienced a similar issue, only I did it on purpose. I was curious to see if the 520 would behave similarly to my Typhoon H when the battery reached a critically low point. In the case of my Typhoon H, it will take over control of the
UAV, land, and shut down. So I put the 520 into a hover over the landing pad at an altitude of less than a foot when the battery was winding down and waited. At the critical moment I heard "RTH" from the controller and the 520 attempted to go straight up. Having considered this might occur I was prepared for the possibility, or so I thought. I immediately reduced power, which I believed should have commanded the 520 to abort the RTH command. It stopped the ascension of the 520 but it then began to fly erratically in different directions and altitudes. I attempted to apply correcting inputs to counteract the 520 but was essentially unsuccessful. The 520 flew into the roof of my house, tumbled down where two roof lines come together, rolled off the edge of the roof and hit the sidewalk before I could get into position to catch it. The damage was not severe and can be repaired with the necessary replacement parts. My guestion is why it did what it did. I can't believe the 520 is programmed to go to its RTH altitude as doing so is only going to let it fall out of the sky from a higher altitude. Even if that is the case I expected that inputting a command would cancel the RTH command and I would be able to simply descend and land. I was surprised I was not able to control its flight. As a veterinary surgeon I learned many years ago to expect the worst and you are never disappointed. My disappointment here is that I was not able to successfully land the 520. I am not convinced it was pilot error, as far as the flying goes. Retrospectively, I should have set the RTH to about 10' which might have saved my butt, and the 520. I have attached the crash log from the controller, I think. My controller will not maintain the correct date and time and I neglected to reset it to the correct date and time before flying yesterday. I have the ulog and tlog files as well but they appear to be too large to attach to this post. I would appreciate any comments. I was aware of a Pix program that would open these files for review but have forgotten what it is and can't find the paper I wrote it down on so I have not viewed the file.
Thanks in advance.
Paul
UAV, land, and shut down. So I put the 520 into a hover over the landing pad at an altitude of less than a foot when the battery was winding down and waited. At the critical moment I heard "RTH" from the controller and the 520 attempted to go straight up. Having considered this might occur I was prepared for the possibility, or so I thought. I immediately reduced power, which I believed should have commanded the 520 to abort the RTH command. It stopped the ascension of the 520 but it then began to fly erratically in different directions and altitudes. I attempted to apply correcting inputs to counteract the 520 but was essentially unsuccessful. The 520 flew into the roof of my house, tumbled down where two roof lines come together, rolled off the edge of the roof and hit the sidewalk before I could get into position to catch it. The damage was not severe and can be repaired with the necessary replacement parts. My guestion is why it did what it did. I can't believe the 520 is programmed to go to its RTH altitude as doing so is only going to let it fall out of the sky from a higher altitude. Even if that is the case I expected that inputting a command would cancel the RTH command and I would be able to simply descend and land. I was surprised I was not able to control its flight. As a veterinary surgeon I learned many years ago to expect the worst and you are never disappointed. My disappointment here is that I was not able to successfully land the 520. I am not convinced it was pilot error, as far as the flying goes. Retrospectively, I should have set the RTH to about 10' which might have saved my butt, and the 520. I have attached the crash log from the controller, I think. My controller will not maintain the correct date and time and I neglected to reset it to the correct date and time before flying yesterday. I have the ulog and tlog files as well but they appear to be too large to attach to this post. I would appreciate any comments. I was aware of a Pix program that would open these files for review but have forgotten what it is and can't find the paper I wrote it down on so I have not viewed the file.
Thanks in advance.
Paul