MAVCesium: Switch to newer fork #1480
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
peterbarker
previously requested changes
Nov 8, 2024
Signed-off-by: Ryan Friedman <[email protected]>
Ryanf55
force-pushed
the
fix-mavroxy-cesium-not-loading-or-running
branch
from
1bfbc65
to
e87be50
Compare
Ryanf55
changed the title
tridge
approved these changes
Nov 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Add my MAVCesium fork and expose it a bit better in MAVProxy.
Expectations
With
mavproxy.py --cesium, it will start the web server, which you can open athttp://0.0.0.0:5000/mavcesium/#.You can also still do
module load cesium.Currently, mavproxy does not connect properly when launched in this mode. It works best with the standalone mode, where you launch mavproxy, then launch mavcesium separately in another terminal.
I'll chase that down soon - it's likely a difference in default options because the websocket receives no data.
I'd like to propose merging this as-is with the known deficiency because it's still a large improvement.
Here's what you get:
Birds eye view of Kaga (default on open when you start SITL in Kaga)
Once you take off, the takeoff orbit is marked in pink.
There is a known issue of the vehicle model being yawed 90 off. I'll fix it later.
The forward facing view works too
If you switch to FBWB, you can turn on the camera projection, and get a good idea of what it looks like.
Follow up
I'd like to get it fully working (integrated as a mavproxy module) and fix any obvious bugs.