Recent content by electronicstuff

Yea I mainly use Litchi and sync to Air data (healthy drones) it was definitely not a power issue as I was directly over head. So I'm going for a no fly zone altitude limit as it only happened above 400ft

Ok I thought you definitely know what you are talking about. I think it's all about safe flight and keeping your altitude low, looking at nats map I can see what you are saying. But obviously not a complete no fly zone to the point at which the P3 will not take off, but an area to be mindful of...

This shows me just outside, so not sure

Also agree on not the best place, I tend to get low down shots but went for a higher up gimbal pointing down one. I'll keep my altitude low next time

Ok so we are looking at the P3 reaching 400ft and aborting the assent by auto landing. Makes me think if you were out of controller range, say flying a Litchi mission which went to that height at some point the craft would just land wherever it was and you would have no control if you had lost...

Yes I checked AirData logs and nothing, so I'll have to check the stored flight data from the drone it's self. I will try with the go app next time

So east of Luton Airport (minsden chapel Langley)

Yes quite aware, but as said it's guidance and not something I make a regular habit if doing

Took the Phantom 3 Standard out for a flight today, compass calibrated and GPS locked throughout the flight but twice at around 65% Battery 459 feet and at 45% again a little over 400 feet it changed modes to auto landing, the altitude limit is set at 1650 ish feet, so not sure if it was because...

Try re-seating the flatflex connection to main board at top of the gimbal, I had similar problems when I replaced the flatflex cable

I had to replace the yaw arm on my gimbal, here's my video detailing how I did it. Sorry it's over an hour long due to the complexity.

P3S Letchworth Hertfordshire Sent from my Nexus 5X using PhantomPilots mobile app