Recent content by Fracapouille

Roger that. Thanks for your interesting feedback. The survey was done in a touristic place, and I demanded the intervention to take place while the site was closed to both tourists and workers. The only people allowed were land surveyors that were attending the flight and surveying GCPs...

This is not what I meant. To stay with the image of the vector, you won't consider the length of said vector. It's not like I'm just pushing softly, I'm 3s full throttle. When starting this input (B), the track heading is 287.2°. So it's 143° (70+360-287) angle between trajectory heading and...

Ok, sorry about that, I didn't know this expression. I overreacted, and tend to lose my sense of humor when I feel cornered. I appologize.

Really, thanks for your warm welcome, bro. Plus for your general contribution to this topic, you've been really helpful. I won't even make the effort to report a drawing of me pictured as a horse beaten to death, it's suggestive enough.

"As expected", seriously? A 3 s full throttle input, orthogonal to its direction (it's not even orthogonal, it's more opposite, but wathever...), and it just very smoothly changes its trajectory? You would expect that? Ok, I give up. Wind explains eveything. It must have been particularly...

OK, here is what I got from overlaying the stick inputs (with their strength) on the path followed by the drone, every second (gif delay between frames also 1s, so the movements are synched what happened "real time"). It records the movements during 60s before the crash. Here is what I...

Well, I've gone further in the analysis, and it shows clearly that there is something going wrong with the drone, and nothing I could do about as a pilot. I'll share that ASAP, it's been quite a tough work, so I still need a few hours (days) to make it available.

Thanks a lot sar104, you've been really helpful. Could you please confirm that the vertices of the track are positions measured at a regular interval? I would try to better understand the drone movements synched with the stick inputs... Considering the interval is homogenuous, the picture...

The image I'm talking about is the one in post 25. These 4 images are available when loading the txt file (attached in post #1) with Airdata UAV log reader: "The following files were extracted from the log. The log contains only up to the last 4 photos/video thumbnails, in low-resolution."

I don't think there were many later pictures, this is one of the latest. There are none just before the crash. IIRC there were the 4 last pictures thumbnails in the flight log? As mentionned in the post, the picture was taken around 802s. The orientation (yaw) of the drone shouldn't change much...

It was facing ENE actually. It was looking at me, so it was globally positioned a few meters west from me.

I am affirmative: the drone has gone to crash on a cliff that is situated on the north of its position. It has not gone to the south-east. The gimbal should still be at the bottom of this cliff... It is described in post #25, with one of the last picture (taken around 800s). Except the location...

I often have a stand next to Trimble at various events dedicated to land surveyors, and they're promoting the same model branded as Trimble. I've been discussing with them for a while. Quite an impressive tool, but you're right regarding the price, that's an expensive toy. senseFly's albris...

OK, OK, let's calm things down. It is totally accepted on my side that the drone won't know where it is in ATTI mode. If the wind blows, the drone moves, and its inertia makes it slower to rest in a position. The sensors can't operate, OK. This sensor thing is something I think is a bad...

Thanks for your balanced reply. I admit I could have been disoriented. But the drone can't? I mean, if I understand correctly, both gyro and compass didn't record any U-turn from the drone. Either both are wrong, and the drone made this U-turn, and crashed NW, or I'm a liar and the drone went to...