As you've probably noticed, there are new features added to the Mission Planner almost every day (Michael Oborne is amazing). I thought I'd just highlight today's, which is neat. In the Flight Planner screen, your current Waypoint radius (the "hit zone" that qualifies as having arrived at the waypoint, which you can set) is shown. That makes planning missions much easier!
You can get the latest version of the Mission Planner by clicking the update button in the software or downloading it here.
Other recent updates include:
- level command ack update
- y6 pic
- HUD now runs opengl / bitmap fonts
- add apvar checking
- add format_version checking (eeprom map change)
- change all log file names to YYYY-MM-DD - to save confusion.
- fix small issue on multiple planners open
As always, you can track changes and update to all the code here.
Comments
Rui, try updating you graphics card driver firstly. ive tested on several pcs and fullscreen works fine for me. the proble i was facing is when you made the old hud full screen it was taking over 100ms to draw the hud. ie less than 10 updates per second. with the opengl version its taking less than 10 ms, at fullscreen
please update your graphics card drivers
I cannot get this to load. OpenTK.graphicserrorexception.
Is there something I should load prior to trying to run it?
Yep, you got it!
I get it. :) Makes sense. And it's all in the wiki...
Just to make sure I understand. I want the plane to take a photo using the DO_SET_SERVO command after passing WP1. To achieve this i add the command after WP2 in the list of commands like this:
1 WAYPOINT
2 WAYPOINT
3 DO_SET_SERVO
To return to WP1 after passing WP 2:
1 WAYPOINT
2 WAYPOINT
3 DO_SET_SERVO
4 WAYPOINT (dummy)
5 DO_JUMP WP1
/Magnus
Magnus,
That's not a bug; it's the way waypoint logic works. What you're saying with WP3 is not "wait until you get to WP3, it's "start heading to WP 3". Once it starts heading in that direction, it then executes the next command, which is the jump, and that happens long before it arrives at WP3.
Waypoint logic can be a little counterintuitive sometimes, and we've all been tripped up by it in the past. But if you think about it, this makes sense. You wouldn't want the autopilot's command processor to freeze in-between waypoints!
Michael,
I did some more tests with DO_REPEAT_DELAY and now it works. I can't replicate the problem.
However i found a new issue. I don't know if it is related to Mission Planner or APM. It is the same in both live flying and in the simulator.
When flying a path which ends with a DO_JUMP command to an earlier waypoint the plane skips the waypoint before the jump command.
If the flight plan looks like this
wp1 WAYPOINT
wp2 WAYPOINT
wp3 WAYPOINT
WP4 DO_JUMP repeat 14
The plane will fly WP1->WP2->WP1->WP2 etc. and never reach WP3
If i should report this somewhere ells please say so and i will move it!
/Magnus
/Magnus
/Magnus
If you set wp radius to 1 and loiter to 1, will that make any problems? could it "stop" loitering and go wild?
Magnus, i cant repeat what you are describing. i can load and save DO_REPEAT_RELAY the waypoints and tags load fine.
Ahmed, as soon as the plane/quad hits the outside of the radius the next wp is loaded.
Thanks Chris it is very useful feature will it hit the exact way point or only circle radius . As in garmin gps it enters the hit radius and continues toward the way point until distance start to increase again then its done?
-
1
-
2
-
3
of 3 Next