Hi,
I want to use the RosAria package in order to send commands and interface with my robot. I have managed to successfully install and build this rosaria package and I have also tested it multiple times on simulation (by using MobileSim by MobileRobots).
Now I want to connect rosaria to the actual robot, Powerbot (a pioneer robot by Adept MobileRobots). I have successfully connected to the robot ONCE by running
rosrun rosaria RosAria _port:=/dev/ttyS0
Then I killed the node (^C) but when I tried to connect to it once again by re-running the same line (above), I got this error:
powerbot67@powerbot67-desktop:~/catkin_ws/src/rosaria$ rosrun rosaria RosAria
[ INFO] [1422444061.117081691]: RosAria: using port: [/dev/ttyS0]
Could not connect to simulator, connecting to robot through serial port /dev/ttyS0.
Syncing 0
No packet.
Syncing 0
No packet.
Trying to close possible old connection
Syncing 0
No packet.
Syncing 0
No packet.
Robot may be connected but not open, trying to dislodge.
Syncing 0
No packet.
Robot may be connected but not open, trying to dislodge.
Syncing 0
No packet.
Could not connect, no robot responding.
Failed to connect to robot.
[ERROR] [1422444067.613784823]: RosAria: ARIA could not connect to robot! (Check ~port parameter is correct, and permissions on port device.)
[FATAL] [1422444067.613882512]: RosAria: ROS node setup failed...
Now $USER is a member of the dialout group and I'm sure that the robot connection worked because:
(a) I had connected to the robot through rosaria ONCE during the first time and
(b) Before I installed rosaria I was working with the ARIA library directly and everything worked brilliantly.
In the error it is suggesting that I check that ~port parameter is correct, but I'm sure it is since I ran the same command previously.
Can somebody help me understand this please? Thanks!
Originally posted by RND on ROS Answers with karma: 133 on 2015-01-28
Post score: 0
Original comments
Comment by Orso on 2015-01-28:
I have had this problem before a dozen times or so in the past year. A dirty fix that worked for me was to hit the reset button. Then power off the P3AT, and repower P3AT. I may have restarted my GUI computer in one of the steps to regain the connection.
Comment by RND on 2015-01-29:
It worked thanks!
Comment by AlexR on 2015-01-29:
remember that you will have to run the sudo chmod command every time you start the robot. You can define the sudo permissions in your launch file for ease.
Comment by AlexR on 2015-01-29:
can you mark it as an answer if it helped you. Thanks
Comment by ReedHedges on 2015-01-29:
The reset button for Powerbot is in the panel on the top-rear of the robot. Newer firmware it will make periodic beep to indicate that it is still expecting software communication but data has stopped (reset maybe required in this case). Sound can be turned on/off in firmware configuration though.
Comment by anirban on 2015-07-07:
I cannot connect to pioneer robot using rosaria for several days. Although I was able to connect when I installed first. I tried powering of and turning power on of the robot but nothing changed. I also used restart button that also did not work. can any one help?
Comment by RND on 2015-07-08:
@anirban you can either follow the above comments, or check that the port you are using is valid. How are you connecting to rosaria?
Comment by anirban on 2015-07-08:
I am connecting P3 using a serial cable. I am running the following command line
$ rosrun rosaria RosAria _port:=/dev/ttyS2
S2 because I know this port worked well with aria example codes those are provided by Mobile robot.
So basically I am using a USB serial converter to connect to the robot.
Comment by RND on 2015-07-08:
can you specify the error that you are getting?
Comment by anirban on 2015-07-08:
I am getting a similar error as above but without the lines
Syncing 0
No packet.
These two lines are not coming for me. All other things are same.
While uploading the screenshot I am prompted that >5 points required to upload a file. So could not upload the screenshot.
Comment by anirban on 2015-07-08:
The detailed error message I posted here