Adding Websocket Server for telemetry and status #3
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
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.
Summary
Adding a WebSocket server in MAVProxy instead of a REST API for low latency and small overhead update to the frontend.
Sharing a "message" queue across threads to constantly send data to the frontend
Testing
Run SITL (Tested on Mac):
docker run -itd --rm --name sitl_container cuairautopilot/private_repo:sitl_image -C --out=udp:host.docker.internal:14550Run MAVProxy (From root of the repo):
python -m MAVProxy.mavproxy --sitl=sitl_container:14550Run frontend (From frontend folder)
npm run startSee Logs on the terminal.
Notes
Still need to support the different kinds of messages