Error at kobuki_node minimal.launch: "could not contact master"

asked 2017-11-28 21:22:12 -0600

robolearning gravatar image

When I run

roslaunch kobuki_node minimal.launch

I get the following output

... logging to /home/ubuntu/.ros/log/8e8d5c0c-d4b3-11e7-836c-902e1cfcc74f/roslaunch-tegra-ubuntu-2175.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://localhost:58965/

SUMMARY

PARAMETERS * /diagnostic_aggregator/analyzers/input_ports/contains: ['Digital Input',... * /diagnostic_aggregator/analyzers/input_ports/path: Input Ports * /diagnostic_aggregator/analyzers/input_ports/remove_prefix: mobile_base_nodel... * /diagnostic_aggregator/analyzers/input_ports/timeout: 5.0 * /diagnostic_aggregator/analyzers/input_ports/type: diagnostic_aggreg... * /diagnostic_aggregator/analyzers/kobuki/contains: ['Watchdog', 'Mot... * /diagnostic_aggregator/analyzers/kobuki/path: Kobuki * /diagnostic_aggregator/analyzers/kobuki/remove_prefix: mobile_base_nodel... * /diagnostic_aggregator/analyzers/kobuki/timeout: 5.0 * /diagnostic_aggregator/analyzers/kobuki/type: diagnostic_aggreg... * /diagnostic_aggregator/analyzers/power/contains: ['Battery'] * /diagnostic_aggregator/analyzers/power/path: Power System * /diagnostic_aggregator/analyzers/power/remove_prefix: mobile_base_nodel... * /diagnostic_aggregator/analyzers/power/timeout: 5.0 * /diagnostic_aggregator/analyzers/power/type: diagnostic_aggreg... * /diagnostic_aggregator/analyzers/sensors/contains: ['Cliff Sensor', ... * /diagnostic_aggregator/analyzers/sensors/path: Sensors * /diagnostic_aggregator/analyzers/sensors/remove_prefix: mobile_base_nodel... * /diagnostic_aggregator/analyzers/sensors/timeout: 5.0 * /diagnostic_aggregator/analyzers/sensors/type: diagnostic_aggreg... * /diagnostic_aggregator/base_path: * /diagnostic_aggregator/pub_rate: 1.0 * /mobile_base/base_frame: base_footprint * /mobile_base/battery_capacity: 16.5 * /mobile_base/battery_dangerous: 13.2 * /mobile_base/battery_low: 14.0 * /mobile_base/cmd_vel_timeout: 0.6 * /mobile_base/device_port: /dev/kobuki * /mobile_base/odom_frame: odom * /mobile_base/publish_tf: True * /mobile_base/use_imu_heading: True * /mobile_base/wheel_left_joint_name: wheel_left_joint * /mobile_base/wheel_right_joint_name: wheel_right_joint * /rosdistro: indigo * /rosversion: 1.11.19

NODES / diagnostic_aggregator (diagnostic_aggregator/aggregator_node) mobile_base (nodelet/nodelet) mobile_base_nodelet_manager (nodelet/nodelet)

auto-starting new master process[master]: started with pid [2186] ERROR: could not contact master [ http://192.168.0.107:11311/ ] The traceback for the exception was written to the log file [master] killing on exit

and when I look at the logs it appears that it does connect to the master for a short time but then for some reason looses the connection. What's weird is that I tried this a few days ago and it worked successfully. I really hope this isn't a hardware failure. Any suggestions?

edit retag flag offensive close merge delete

Comments

bueller???

robolearning gravatar image robolearning  ( 2017-12-04 17:48:42 -0600 )edit