Failed to open port /dev/ttyUSB0
hey, i got some problems with getting my turtlebot started.
- have and ubuntu 11.10 running with ros on asus eeepc.
- started with the turotials at ROS Turtlebot Tutorial
- at the tutorial turtlebot_bringup i got the error Failed to open port /dev/ttyUSB0
to be a bit mor clear i tried rostopic echo /diagnostics whitch presents me this message as well as the Dashoard as well as if i type roslaunch turtlebot-bringup minimal.launch
4.i tried to solf this problem using with this possible solutions
but nothing changed
again more clear i changed the chmod of /dev/ttyUSB0, i tried udev rules, i have tested if there is an connection to this port with lsusb and dmesg | grep usb as well ass cd /dev/serial/by_id/ ls -al.
All confirm me my serial device converter (needed for the connection from pc to rommba cleaner) is attached to ttyUSB0
My anybody got some advices for me?
edit:
lsusb
Bus 004 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
dmesg|grep usb
[ 130.917744] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB0
cd /dev/serial/by_id/``ls -al
lrwxrwxrwx 1 root root 13 2012-10-29 15:07 usb-FTDI_FT232R_USB_UART_A900Y9QC-if00-port0 -> ../../ttyUSB0
rostopic echo /diagnostics
der:
seq: 4
stamp:
secs: 1351520860
nsecs: 565383911
frame_id: ''
status:
-
level: 2
name: TurtleBot Node
message: Failed to open port /dev/ttyUSB0. Please make sure the Create cable is plugged into the computer.
hardware_id: ''
values: []
---
roslaunch turtlebot_bringup minimal.launch
turtlebot@turtlebot-R002:~$ roslaunch turtlebot_bringup minimal.launch
... logging to /home/turtlebot/.ros/log/bf90e012-21d5-11e2-98d7-0008ca665690/roslaunch-turtlebot-R002-8292.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://192.168.0.156:42747/
SUMMARY
========
PARAMETERS
* /use_sim_time
* /robot_pose_ekf/sensor_timeout
* /diagnostic_aggregator/analyzers/sensors/path
* /robot_pose_ekf/imu_used
* /robot_pose_ekf/odom_used
* /robot/name
* /diagnostic_aggregator/analyzers/nodes/timeout
* /diagnostic_aggregator/analyzers/mode/timeout
* /diagnostic_aggregator/analyzers/sensors/timeout
* /diagnostic_aggregator/analyzers/power/type
* /turtlebot_node/update_rate
* /diagnostic_aggregator/analyzers/power/timeout
* /diagnostic_aggregator/analyzers/mode/type
* /diagnostic_aggregator/analyzers/digital_io/path
* /diagnostic_aggregator/analyzers/digital_io/timeout
* /diagnostic_aggregator/analyzers/nodes/path
* /rosdistro
* /robot_description
* /diagnostic_aggregator/base_path
* /robot_pose_ekf/freq
* /robot_pose_ekf/publish_tf
* /app_manager/interface_master
* /robot_pose_ekf/vo_used
* /diagnostic_aggregator/analyzers/sensors/type
* /diagnostic_aggregator/analyzers/digital_io/startswith
* /diagnostic_aggregator/analyzers/power/path
* /robot_pose_ekf/output_frame
* /diagnostic_aggregator/analyzers/mode/path
* /diagnostic_aggregator/analyzers/digital_io/type
* /diagnostic_aggregator/analyzers/mode/startswith
* /rosversion
* /diagnostic_aggregator/pub_rate
* /robot_state_publisher/publish_frequency
* /diagnostic_aggregator/analyzers/sensors/startswith
* /diagnostic_aggregator/analyzers/power/startswith
* /turtlebot_node/bonus
* /robot/type
* /diagnostic_aggregator/analyzers/nodes/type
* /diagnostic_aggregator/analyzers/nodes/contains
NODES
/
appmaster (app_manager/appmaster)
app_manager (app_manager/app_manager)
turtlebot_node (turtlebot_node/turtlebot_node.py)
turtlebot_laptop_battery (turtlebot_node/laptop_battery.py)
robot_state_publisher (robot_state_publisher/state_publisher)
diagnostic_aggregator (diagnostic_aggregator/aggregator_node)
robot_pose_ekf (robot_pose_ekf/robot_pose_ekf)
auto-starting new master
process[master]: started with pid [8310]
ROS_MASTER_URI=http://192.168.0.156:11311
setting /run_id to bf90e012-21d5-11e2-98d7-0008ca665690
process[rosout-1]: started with pid [8323]
started core service [/rosout]
process[appmaster-2]: started with pid [8335]
process[app_manager-3]: started with pid [8336]
process[turtlebot_node-4]: started with pid [8337]
process[turtlebot_laptop_battery-5]: started with pid [8338]
process[robot_state_publisher-6]: started with pid ...
First, post the output of the commands. Second, try opening the port in gtkterm or similar (or even cat first) to see if it can be opened in principle and send some chars.
i am dont know how i format the terminal output properly .. how do i do this?
gtkterm or here? Here, you can use <pre> tags or for code indent by 4 spaces.
I assume gtkterm is similar to minicom, but I always try minicom first.
To me it looks like everything is OK. Can you try just opening it using gtkterm or similar to see if you can open the port with the same parameters. If that works the only explanation I have is that the error msg might be misleading, i.e. the port could be opened, but commnucation fails (bad cable, protocol, etc.)
According to the error msg you added, there is a comm error. So, I would check at the other end, i.e. is there only one USB device (i.e. might it just try to connect to something else), is cables, hardware, etc. OK.
im not sure how i have to use gtkterm to open it how i do this? ... no there are no other usb devices connectet.
at this problem http://answers.ros.org/question/11400/error-opening-turtlebot_dashboard/ they say they "recommend to check roomba stack" .. what does this mean?