JJB*
 Captain
Flight distance : 10968488 ft
Netherlands
Offline
|
fans02a71ddf Posted at 9-15 03:04
There's a couple of issues with the report.
Firstly, the starlight does not correspond with the actual flight - I didn't launch it from the point that it indicates on the report. However, the crash point appears to be accurate.
Hi,
Had a look at your flightlog.
Flight started with only 6 satellites and a zero for signal quality use. (range = 0 to 5)
This means that your drone is stabilized by the vision system.HomePoint was never set in this flight, for this drone needs 4 or 5 in that range.
IR height sensor measured up to 5 meter height, at 20s in flight could not measure height.
ATTI mode for just 1 second.
Hard to say why your drone moved away on its own.
I do not see rapid changes on the compass data, so hard to tell if a compass/yaw error was the cause of this bad flight.
Do you remember wich heading your drone was facing at take-off?
Seen few logs where when GPS signal at start in not there, in flight GPS is 'getting there'...kind of move away from position did happen.Warning "Position mismatch" in the log indicates that the calculated position of a drone is not the actual position.
ALways check the GPS icon top right FlyApp before take-off
Red = not enough sats
Yellow = enough sats for GPS lock, bit not enough for setting HP
White = enough sats + HP set.
Plus
Always check before each flight drone heading in the flyapp map view, compare with actual heading.
If not the same DO NOT FLY
EDITyour heading on the ground : 280. Log shows 316, 36 degrees wich is 'corrected' after takeoff can cause a fly away from position.
See chart of your heading changes and RC yaw input, drone follows your input.Large change in Pitch and Roll before the yaw RC input, see the chart.
If a compass/yaw is the reason for this than the conflict happend at start of your flight, see the orange marker.
See chart 3, large roll and pitch at the time GPS was getting data, in the orange marker the distances from record to record, 46 en 79 meter travel in distance in 0.1 seconds is ofcourse not real, it shows the GPS incorrect LAT LON data.
cheers
JJB [ Charts by FRAP ; the 'best' software for data and visual flightlog analysis (www.jjbfrap.eu) ]
|
|