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

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

Join diydrones

Email me when people reply –

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.

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @a1k0n: Sync'd @joshu's GoPro w/ my datalogging; video is 2.5X speed, Google imagery upper-right. Found out my track boundaries are WAY…
yesterday
DIY Robocars via Twitter
RT @a1k0n: Also, at 45mph, the front tires literally blow up like a balloon and it doesn't have much front traction, so the car becomes fai…
yesterday
DIY Robocars via Twitter
RT @a1k0n: Okay, some datalogs! Green dots are precalculated racing line (from my crummy optimizer -- it veers to the middle after 2 for Re…
yesterday
DIY Robocars via Twitter
RT @a1k0n: Welp my @selfracingcars entry, hastily conceived heading filter and all, actually worked! Heading home, datalogs and videos to f…
yesterday
DIY Robocars via Twitter
yesterday
DIY Robocars via Twitter
Friday
DIY Robocars via Twitter
RT @f1tenth: What can we learn from autonomous racing? Actually, a lot! To get an idea what you can do in this field and where the research…
Oct 11
DIY Robocars via Twitter
Oct 11
DIY Robocars via Twitter
RT @a1k0n: It's aliiiiiive! Less than a week until @selfracingcars and I'm just now digging this bad boy out. Been a crazy few months. Hope…
Oct 10
DIY Robocars via Twitter
RT @OttawaAVGroup: Mark your calendars. CAV Canada is happening on Dec. 2nd, 10am-4pm EST. And guess what - admission is FREE! Get your ti…
Oct 6
DIY Robocars via Twitter
RT @f1tenth: Our new 1:10 scale 3D racetrack is here. We will implement it in the @SVLSimulator in the next weeks so everybody can use it.…
Oct 6
DIY Robocars via Twitter
RT @DAVGtech: Received sweet autonomous Ferrari's that we plan to demo at the @IndyAChallenge on our portable @donkey_car track. Let us kno…
Oct 6
DIY Robocars via Twitter
Sep 30
DIY Robocars via Twitter
Sep 9
DIY Robocars via Twitter
RT @chr1sa: We've got another virtual @DIYRobocars race tomorrow at 9:00am PT. Two dozen autonomous cars will compete, four at a time. Ther…
Sep 4
DIY Robocars via Twitter
Sep 1
More…