I'm getting "failed to receive data from Create. Check if robot is powered!" error about create_robot HOT 8 CLOSED

For me all it took was to uncomment the baud parameter line in the default.yaml file. Left everything else 'as is', even the baud rate. I'm using a Roomba 560 running on a Pi 3.

from create_robot.

I have encountered a similar issue on 18.04 + ROS Melodic where the driver would fail to connect with serial error - Operation cancelled.

The solution in this case was a fix in libcreate:

In libcreate/include/create/serial.hpp:

#include <boost/enable_shared_from_this.hpp>
class Serial : public boost::enable_shared_from_this<Serial> {

and in libcreate/src/serial.cpp, replace all uses of

boost::bind(&Serial:onData, this, _1, _2)

with

boost::bind(&Serial::onData, shared_from_this(), _1, _2)

from create_robot.

I am having the same issue with create 1. I will try the battery trick and get back to you though.

from create_robot.

from create_robot.

Still now working for me. I am using Ubuntu 16.04 on a RaspberryPi 3B and ROS Kinetic. Could that be a problem?

I have tried to connect it with a PC with the same version of ROS and Linux but to no avail.

Can it be anything to do with the baudrate the systems are suppose to communicate in?

from create_robot.

Can it be anything to do with the baudrate the systems are suppose to communicate in?

This could be the culprit. You could try changing the baud argument for the driver or on the Create itself (see the manual for instructions). The Create communicates with 57600 or 19200 (default) baud.

from create_robot.

I am unable to reproduce this issue with a Create 1 platform on Ubuntu 18.04, but I would be willing to accept AutonomyLab/libcreate#38 if others on this thread can confirm it fixes the issue for them.

from create_robot.

I'm going to close this with AutonomyLab/libcreate#38 merged. Let me know if there's still an issue.

from create_robot.