Fixed swiftpro code and launch files to be more ROS-like and not hard… #17
Conversation
This file contains hidden or 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
…code the USB device to use to connect to the uArm.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
…code the USB device to use to connect to the uArm.
My uArms don't always use /dev/ttyACM0 for the serial port. Sometimes they use /dev/ttyACM1 or ACMn. The Bluetooth dongle shows up as /dev/ttyUSB0 or /dev/ttyUSB1.
My changes let you specify _port: as a parameter in the launch file which gets passed into the swiftpro read/write programs.
This would be useful for having multiple USB devices connected to your host system or having multiple uArms connected to a single host via USB.