- Joined
- Jun 18, 2015
- Messages
- 6
- Reaction score
- 4
I just received conformation from 3dr that my post http://www.3drpilots.com/threads/pilot-erorr-solo-error.255/ was in a Solo Flyaway caused by GPS glitch and also motor failure on another flight.
This is email I received from 3dr today:
John,
Seem that one incident was caused due to a GPS glitch, I recommend you upgrade to the new version as it fixes the bugs in the GPS if for any reason the GPS signal is lost of gets weak the drone will switch to manual automatically.
Run a compass and level calibration.
On another log seems the crash was caused because motor#4 malfunctioned and motor #3saturated I will have 2 replacements send to you, please provide the address.
Did you break any props ?
And, Paul over at DIYdrones analyzed the same log files and reported:
"if you rename remove the .2 extension on the solo.tlog.2 file it can be replayed and plotted using mission planner. Doing this shows that the GPS thought it was moving away from the house to the NE, which caused the copter to pitch back and fly SW into the house.
The navigation data shows that there was a growing inconsistency between the GPS and inertial data at the time so all of this points to a GPS glitch.
Brake mode is selected together with forward stick after it starts moving, so the pilot responded correctly."
This is email I received from 3dr today:
John,
Seem that one incident was caused due to a GPS glitch, I recommend you upgrade to the new version as it fixes the bugs in the GPS if for any reason the GPS signal is lost of gets weak the drone will switch to manual automatically.
Run a compass and level calibration.
On another log seems the crash was caused because motor#4 malfunctioned and motor #3saturated I will have 2 replacements send to you, please provide the address.
Did you break any props ?
And, Paul over at DIYdrones analyzed the same log files and reported:
"if you rename remove the .2 extension on the solo.tlog.2 file it can be replayed and plotted using mission planner. Doing this shows that the GPS thought it was moving away from the house to the NE, which caused the copter to pitch back and fly SW into the house.
The navigation data shows that there was a growing inconsistency between the GPS and inertial data at the time so all of this points to a GPS glitch.
Brake mode is selected together with forward stick after it starts moving, so the pilot responded correctly."