add statustext message in mavlink receiver #12540
Closed
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
|
Sorry, I didn't make this clear before. I think that's the wrong approach. In order to forward messages, all that we need to do is to enable forwarding between mavlink instances and that way the statustext messages are taken care of. Have a look at these params: |
|
Great, I'll try that. Thanks! |
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.
This PR adds a listener to the mavlink message StatusText. The received message will republished as a statustext stream.
This enables sending messages from other systems to be displayed on QGroundcontrol. E.g. in our case we could like to send CPU warnings from the companion computer. Now any string sent on the ROS topic
/statustext/sendwill go through mavros into the firmware and from there to QGC