ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

[rplidarNode-6] process has died

asked 2019-02-17 10:12:56 -0500

metobom gravatar image

Hello I am trying to run this, roslaunch evarobot_slam evarobot_slam.launch but when I do I get an error. Any ideas?

metobom@metobom-TULPAR-T5-V17-1:~$ roslaunch evarobot_slam evarobot_slam.launch
WARNING: Package name "metosPack" does not follow the naming conventions. It should start with a lower case letter and only contain lower case letters, digits, underscores, and dashes.
... logging to /home/metobom/.ros/log/008a4e1e-32cd-11e9-a3aa-b46bfc3ecfa1/roslaunch-metobom-TULPAR-T5-V17-1-11657.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.

WARNING: Package name "metosPack" does not follow the naming conventions. It should start with a lower case letter and only contain lower case letters, digits, underscores, and dashes.
xacro: Traditional processing is deprecated. Switch to --inorder processing!
To check for compatibility of your document, use option --check-order.
For more infos, see http://wiki.ros.org/xacro#Processing_Order
inconsistent namespace redefinitions for xmlns:xacro:
 old: http://ros.org/wiki/xacro
 new: http://www.ros.org/wiki/xacro (/home/metobom/metos_ws/src/evapc_ros/evarobot_description/urdf/evarobot_base.urdf.xacro)
redefining global property: pi
when processing file: /home/metobom/metos_ws/src/evapc_ros/evarobot_description/urdf/evarobot.urdf.xacro
xacro.py is deprecated; please use xacro instead
xacro: Traditional processing is deprecated. Switch to --inorder processing!
To check for compatibility of your document, use option --check-order.
For more infos, see http://wiki.ros.org/xacro#Processing_Order
inconsistent namespace redefinitions for xmlns:xacro:
 old: http://ros.org/wiki/xacro
 new: http://www.ros.org/wiki/xacro (/home/metobom/metos_ws/src/evapc_ros/evarobot_description/urdf/evarobot_base.urdf.xacro)
redefining global property: pi
when processing file: /home/metobom/metos_ws/src/evapc_ros/evarobot_description/urdf/evarobot.urdf.xacro
xacro.py is deprecated; please use xacro instead
started roslaunch server http://metobom-TULPAR-T5-V17-1:35549/

SUMMARY
========

PARAMETERS
 * /diag_agg/analyzers/controller/find_and_remove_prefix: evarobot_controller
 * /diag_agg/analyzers/controller/path: Controller
 * /diag_agg/analyzers/controller/timeout: 5.0
 * /diag_agg/analyzers/controller/type: diagnostic_aggreg...
 * /diag_agg/analyzers/motor/find_and_remove_prefix: evarobot_driver
 * /diag_agg/analyzers/motor/path: Motor
 * /diag_agg/analyzers/motor/timeout: 5.0
 * /diag_agg/analyzers/motor/type: diagnostic_aggreg...
 * /diag_agg/analyzers/sensors/analyzers/bumper/find_and_remove_prefix: evarobot_bumper
 * /diag_agg/analyzers/sensors/analyzers/bumper/path: Bumper
 * /diag_agg/analyzers/sensors/analyzers/bumper/timeout: 5.0
 * /diag_agg/analyzers/sensors/analyzers/bumper/type: diagnostic_aggreg...
 * /diag_agg/analyzers/sensors/analyzers/imu/find_and_remove_prefix: evarobot_minimu9
 * /diag_agg/analyzers/sensors/analyzers/imu/path: IMU
 * /diag_agg/analyzers/sensors/analyzers/imu/timeout: 5.0
 * /diag_agg/analyzers/sensors/analyzers/imu/type: diagnostic_aggreg...
 * /diag_agg/analyzers/sensors/analyzers/infrared/find_and_remove_prefix: evarobot_infrared
 * /diag_agg/analyzers/sensors/analyzers/infrared/path: Infrared
 * /diag_agg/analyzers/sensors/analyzers/infrared/timeout: 5.0
 * /diag_agg/analyzers/sensors/analyzers/infrared/type: diagnostic_aggreg...
 * /diag_agg/analyzers/sensors/analyzers/odom/find_and_remove_prefix: evarobot_odometry
 * /diag_agg/analyzers/sensors/analyzers/odom/path: Odom
 * /diag_agg/analyzers/sensors/analyzers/odom/timeout: 5.0
 * /diag_agg/analyzers/sensors/analyzers/odom/type: diagnostic_aggreg...
 * /diag_agg/analyzers/sensors/analyzers/sonar/find_and_remove_prefix: evarobot_sonar
 * /diag_agg/analyzers/sensors/analyzers/sonar/path: sonar
 * /diag_agg/analyzers/sensors/analyzers/sonar/timeout: 5.0
 * /diag_agg/analyzers/sensors/analyzers/sonar/type: diagnostic_aggreg...
 * /diag_agg/analyzers/sensors/path: Sensors
 * /diag_agg/analyzers/sensors/type: diagnostic_aggreg...
 * /hector_height_mapping/advertise_map_service: True
 * /hector_height_mapping/base_frame: base_link
 * /hector_height_mapping/map_pub_period: 0.25
 * /hector_height_mapping/map_resolution: 0.1 ...
(more)
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2019-02-17 11:38:01 -0500

renangm gravatar image

It seems the rplidar_ros package cannot bind the /dev/ttyUSB0 port:

RPLIDAR running on ROS package rplidar_ros
SDK Version: 1.5.7
Error, cannot bind to the specified serial port /dev/ttyUSB0.

Check if you have permission to read/write serial ports (your user must be in "dialout" group), or if the sensor has been assigned to another port (e.g., /dev/ttyUSB1).

This question might also help you.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2019-02-17 10:12:56 -0500

Seen: 832 times

Last updated: Feb 17 '19