-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature requests to improve usefullness #6
Comments
Hi, |
I must say I played back a tlog from previous mission, I've seen before that mavproxy fail to get some/most waypoints when playing back tlog (that contain mission upload) rather than actually flying - I do not know whatever mavcesium reads mavproxy WP, or reads the stream(or requests) them by itself, but playback must be the reason.. |
By design mavcesium will keep in sync with the wp's that are stored in mavproxy. So if you can see them on the mavproxy map you should also see them in mavcesium... I haven't tried visualising log playback with mavcesium running. I'll add it to the list of things to try! |
I'm quite a fan of this HUD: http://gallinazo.flightgear.org/uas/autopilot-visualization-flight-track/
|
nope - that sounds too awesome to be true :) |
A quote from @SamPes capturing some really good ideas
|
Make web server executable
Please consider adding :
-wind speed & direction. (numerical with an arrow ?)
-xtrack and altitude error
heading, bearing , and next few waypoints
in the the mockup below heading is not very relevant, but in other views it may be.
Together, viewing turns with targets (WP right in the map) - would make it easy to evaluate turns when tuning.
![screenshot from 2017-02-13 11-01-43](https://cloud.githubusercontent.com/assets/1468842/22879073/8e9d3bd2-f1dc-11e6-8ba6-cc654c9bc5ea.png)
The text was updated successfully, but these errors were encountered: