I updated mission planner to the latest version on two notebooks. It seems that the update contains some bugs. I can’t send wp’s to the drone… also the auto pan function in the plan tab doesn’t work anymore.
It’s fix itself as soon as you fix your mission, which has an invalid altitude reference for the takeoff command. Guess you have an externally generated waypoints file. The third field of the takeoff command should be 0, 1 or 3 in the .waypoints file.
BTW, If I use Mission Planner 1.3.7 I can send a last weekend generated mission. If I’m using Mission Planner 1.3.71 I get the error. This should be the prove, that the problem is not only mission related.
OK, it seems that to write mission to AC you have to have a valid home position (At least a gps lock) because while writing mission, MP reads back the home location. (Write Fast does not do this) It timeout to read home position because there is none.
The tricky part is, that if you don’t have a gps lock (and ekf origin) you cannot set home manually because flight controller will refuse it.
So in summary, you have to have a GPS lock to write mission except using Write Fast.
(This is because from 1.71 the ambiguity of setting home via Flight Planner is fixed, the home marker set or moved in Flight Planner DOES not change the home position of the aircraft. Home position can be set only via arming or set home on the FlightData screen.
I tested it if Write Fast with the USB cable. It works, but If I’m reading back the misssion from my flightcontroller everything is changed from Terrain to Relative.