Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing Serial Port #111

Closed
hofes opened this issue Oct 31, 2013 · 5 comments
Closed

Changing Serial Port #111

hofes opened this issue Oct 31, 2013 · 5 comments

Comments

@hofes
Copy link

hofes commented Oct 31, 2013

Isn't there a better way of changing the serial port (from ttyUSB0 to ttyS0) than changing the launch/includes/mobile_base.launch.xml.
Doing so always makes it necessary to change the launch file after every update of the turtlebot stack or to copy the turtlebot_bringup to a different (e,g. myrobot_bringup) package. Couldn't a environment variable be a better solution than hardcoding the port in the launch file.

@tfoote
Copy link
Contributor

tfoote commented Oct 31, 2013

The parameter is set for the default configuration of the TurtleBot. The clean way to do this is to use launch arguments with a default value. Which get passed down to the lower level launch files. In practice very few people use a different port. which is why we have not taken the time to make it parameterizable. If you'd like to do that a patch would be appreciated. However I think it will be easier work around for you to simply update your system to symlink ttyS0 to ttyUSB0.

@bit-pirate
Copy link
Member

I don't know your exact use case, but for Kobuki we added extra information to the FTDI chip, what let's automatically create the right symlink using a UDEV rule.

I assume you are using the Create. You might be able to create such a script for your specific Create as well (if you do, please share it here with the other create users).

@mayrjohannes
Copy link

In this particular case a roomba is used and we are directly connected to a serial port of the on board mainboard. So there is no USB Serial converter in between. I think just creating a symlink can cause troubles if using an additional USB Serial converter. The best solution would be to add the parameter as proposed by tfoote as an launch argument. We will change this and supply a patch the next days.
What is the correct way to do so? A pull request on github?

@tfoote
Copy link
Contributor

tfoote commented Nov 4, 2013

Yeah, A pull request on github will get this taken care of the quickest.

jihoonl added a commit that referenced this issue Mar 3, 2014
Added serial port as parameter to launch files (Issue #111)
@jihoonl
Copy link
Member

jihoonl commented Mar 3, 2014

#112 fixed.

@jihoonl jihoonl closed this as completed Mar 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants