ros2_0_galactic: configure device #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
In our platform, physical access to the MTi is challanging so we want to configure the MTi through the driver parameters. A previous patch added the ability for output configuration. This may lead to higher bandwidth requirements, hence the need to configure the baudrate. To ensure the device can be detect initialy, and after potential factory resets, an additional baudrate parameter is added to the configuration and scan process. To ensure the device can be detected.
renemoll
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.
In cases where the MTi is build in and cannot be accessed easily, we want to be able to change certain settings via parameters. This series of patches adds the abilities to configure:
(this time against the galactic branch as intended)