endotherm
First Officer
Flight distance : 503241 ft
Australia
Offline
|
Milty Posted at 2017-2-24 14:46
Ok I read these replies and there are a lot of assumptions. There was no 7 m break wall behind us it was a fairly flat beach and why didn't it nosedive the previous 2 flights, just spun around wildly ..is that wind as well ? . This winds were also very low so much so that the nosseums were in and out. I was flying as I normally do and have done repeatedly before the firmware upgrade. Never before had the unit spun out of control and never before did it do a nose dive straight into the water. To say I was sitting idle while it did this is ridiculous lol. Perhaps the software issue contributes also to faulty flight records? Of all the times I flew this bird, these were the best conditions and the least weight. If you can fly in 25 mph winds as per specs, the roughly 8 mph with about 6 oz weight and crash makes this drone a piece of garbage !! Maybe why it appears to be phased out ? I flew several times with double the weight or more in much higher winds and no issues. The technology for these things has obviously not been developed enough for them to even be on the market, and then all the firmware upgrades ? Give me a break. I would be willing to be more are crashed in the first week then not.
I am a scientist and I know how to evaluate.
I don't think much of your scientific method, when the proof is staring you in the face and all you have to offer is that you have an opinion about the maturity of the firmware and your own assumptions. You aren't the first person on the forums to have formed an incorrect assumption and refused to look at the data impartially. I'm sure you won't be the last. You haven't provided any proof but you cling to your own conclusion as infallible. The other scientists out there don't agree with you.
Ok I read these replies and there are a lot of assumptions.
The assumptions are valid observations based on the data and evidence. Look at the facts and tell us why they are wrong. Tell us how the conclusions were wrong and how the facts lead to a different conclusion.
There was no 7 m break wall behind us
Yeah, there was. According to the facts provided by your GPS coordinates, we are able to determine that your home point on the beach was at 3m ASL (above sea level). Behind you was land mass and foliage that ascended up to 7m ASL. This provides you with an effective windbreak, 4m taller than your home position, and 7m above the water. Refer to this cross-section of the land and take it up with Google if you disagree with their data, images and 3D modeling.
There are many studies of fluid dynamics that confirm wind behaviour leeward of a windbreak manifesting in rolling turbulence. This model perfectly explains the behaviour of your aircraft at this location, and in the absence of any other credible theory is the likely explanation.
why didn't it nose dive the previous 2 flights
I don't know, maybe the wind behaved differently on those flights? What the wind did yesterday, or 5 minutes before or after has no bearing on what it is doing now. Much like flipping a coin, previous and later results do not influence the outcome of the current flip. Have a read about the wind shear phenomenon. Thankfully this does not strike every aircraft coming in for a landing, but it occasionally does, with catastrophic results. I don't think anyone can tell you why this situation occurs, and neither can they predict when it will happen.
is that wind as well ?
Most likely. Adding considerable weight payloads does not help either. Any reserve power that the aircraft had to counter any wind forces is spent on keeping a heavy airframe aloft. All it needs is a sudden gust or change of direction to catch you out.
This winds were also very low
On the ground. Unless you are Superman flying around in the airstream you really have no idea how strong the winds were at altitude.
Never before had the unit spun out of control
Saying that it had never done something before is not evidence that it could not do it now. You have been provided with a scenario which fits your observation, which is backed up with data from the flight recorder. Come up with another scenario that explains what happened. I have no idea how one would program the firmware to randomly crash one aircraft without crashing the thousands of other aircraft out there that fly without problem, time after time.
To say I was sitting idle while it did this is ridiculous
No. From around 30 to 33 seconds you applied moderate forward and upward input. At 33 seconds it shows the altitude decreasing all the way to the ground and your sticks were centered, aside from some insignificant movements at impact at 36 seconds. You made no attempt to counter the unexpected altitude descent. This is clearly shown in the flight data. They were left at idle and you left the aircraft to hover.
Perhaps the software issue contributes also to faulty flight records?
There is absolutely no evidence to suggest there is a fault with the software, or that the flight records are erroneous and unreliable. Please show where you have examined the software code and discovered an error.
The technology for these things has obviously not been developed enough for them to even be on the market, and then all the firmware upgrades ?
The technology has been developed since the Phantom 1 and the firmware has been improved to change functionality and improve performance and reliability. These aircraft have been tested and developed adequately for them to be on the market, as evidenced by the number of machines sold, with DJI being the market leader in consumer drones. Product improvements and upgrades are a good sign of a manufacturer that is prepared to support and improve their product, not an admission of a faulty product. Clearly you are lashing out because you are disappointed having crashed it. Your objectivity is suffering as a result, and you are seeing problems where none exist. Claiming there are hundreds of cases of similar errors is just plain wrong and misleading. |
|