mavlink: change mavlink output destination #6
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
chobitsfan
changed the title
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.
maybe related to #3
It allows user to add MAVLINK_DST_IP and MAVLINK_DST_PORT in WIFI.TXT to change mavlink output destination
In a swarm setup, drones are config to WiFi station mode, drones and GCS are connected to the same WiFi AP. If all drones broadcast mavlink to the same port 14550. It will create lots of traffic and each drone will spend unnecessary time to parse every packet (drone listen on 14550, so each drone will listen all broadcast packets from other drone). It may cause drone miss packets from GCS.
User can add MAVLINK_DST_IP and MAVLINK_DST_PORT in WIFI.TXT to specific output destination. Default value (broadcast to 14550) will be used if not specified.
For example, PC running GCS is act as WiFi AP (192.168.1.1). drones can be config to send mavlink to 192.168.1.1 on different port. It makes swarm setup easier.
Test flight video is here
2 skyviper v2450, one output to GCS_IP:14550, another output to GCS_IP:14551. Two mavproxy is acted as GCS on the same PC