DroneDude8146
lvl.2
Flight distance : 2358698 ft
United States
Offline
|
Tuxtard Posted at 7-9 02:28
Did you set signal loss action to descend?
We can only speculate what happened here. Here are some theories.
Yes, I had set it to RTH if signal was lost.
Your theories are both good ones, IMO. Thank you for providing. My thoughts on each:
1. I was flying within commuting distance to the Washington D.C. area, though not in any restricted airspace and not around any government facilities (that I know of). There are all kinds of government folks that reside in my area (secret service, 3 letter agencies, Homeland Security, etc.). It was the 4th of July (US Holiday) with many parties occurring. I was hoovering in one spot for a few minutes before loosing connection and the Drone descending. Could someone with access to a jamming device, annoyed or just wanting to show off for some family/friends decided to jam my drone? I think certainly possible. I googled this, but not a ton of info. on capabilities or anecdotes based on my quick search so I wasn't sure.
2. Also a very valid theory. I wasn't aware of the overheating details and specifically drone actions it takes when it does overheat. I appreciate you providing those details. It was a hot night, but the sun was down and not nearly as hot as I've flown during the day. But, this was my second flight of the evening, so the drone could very well have gotten too hot just from operation. Weather was 75 degrees (F), 23.9 (C), at 75% humidity when I took off. I wasn't flying the drone especially hard, but had started 1 22 minute flight prior to the incident flight, landed, changed batteries, then immediately flew for 17 additional minutes when I lost all contact with the drone. You mentioned based on my older firmware version at the time that links would likely be severed and no specific record of the overheating condition would be logged, but would there be indication of the drone approaching the upper limit of its capability? Would it be battery temp?
You have provided some good insight, so I do have one follow-on question that I'm curious as to your opinion. In either of the above scenarios, would it cause the controller to forget the drone and have to re-pair after recovery? Specifically, when I took off, I was warned I had 3x flights left before being required to bind the controller to the aircraft (I was using RC-N1 w/ iPad instead of usual controller). After I recovered the drone, I had to re-pair the ipad and RC-N1 to the drone. After I did, the controller/iPad had forgotten how many unbound flights I had taken as it warned me I had 5x flights remaining before being required to bind the controller to the aircraft. I was surprised by that, but maybe it's typical. |
|