Problems arming with v3.3rc5

I'm a latecomer to beta testing v3.3.

I've had many successful flights with v3.2 but with v3.3rc5 I often cannot get it to arm. APM Planner says it needs a "3D Fix", yet I have 8 or more satellites and hdop of 1.6 - 1.9. I've even cranked up the HDOP threshold to 400 (i.e., 4.00)

First thing this morning I did get it to arm (after quite some time) so I successfully did the autotune process. After landing I changed the battery and tried to do another flight but couldn't get it to arm. I've had "prearm chk mask" = 1 (everything) so I tried to exclude only the GPS check but APM Planner doesn't seem to let me upload a number greater than "127" (an unsigned char??).

Could the "Need 3D Fix" message be generated by the failure of something else beside the GPS? I'm using a HKPilot32 (Pixhawk clone) with Ublox M8N gps on a F450 frame. 

Can anyone shed some light on this?

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Activity