I am having a problem with a flight plan.
I created a flight plan in Mission Planner flying up along rising terrain...out and back down...using altitudes where I would clear the terrain by 350 feet.
After I upload the flightplan to the Pixhawk, and then download it into Tower, the row of waypoints across the bottom of the editor screen show the correct altitudes.
But...
When I click on each waypoint, only the 1st couple and last couple (the lower altitude waypoints) show the correct altitude in the "altitude slider/selector" box...the others show ZERO.
There is no other warning statement or any other indication that waypoint altitudes have been rejected (and in fact, ARE they being rejected?...which should I believe, the altitudes in the row of waypoints along the bottom of the screen? Or the altitudes in the "altitude slider/selector"?)
I thought it might be that I had the geofence, etc, set so that my waypoint altitudes exceeded that number, but they do not.
Does anyone know why the waypoint editor in Tower would show ZERO as the altitude for all those (higher) waypoints in the middle?
Gradients seem fine as well...both up and down.
Thanks...
Bill
Replies
Alright...geez...I answered my own question.
Tower has IT'S OWN "max altitude" setting, which was set to 656 feet (for some reason)...any altitude I had Mission-Planner-flight-planned above that altitude, shows ZERO in the Tower waypoint editor. (Question still remains, would the Pixhawk have actually descended to ZERO? Or would the flight planned altitude prevailed?)
I would not have assumed that Tower would essentially over-ride the geofence (or other parameter) settings in Mission Planner...to me, that's confusing.
Anyway, hope this helps someone...
--
Bill
I don't think tower contain logic to check for geofence - geofence is something AP is handling.