search

ros-naoqi / naoqi_dcm_driver

Hardware interface allowing control Nao, Romeo, and Pepper robots via ROS
4 stars 13 forks source link

Could not parse "LArmRArm" as a valid joint name, chain name or "Body" in pepper_bringup.launch #4

Open victorpaleologue opened 6 years ago

victorpaleologue commented 6 years ago

Reported in https://groups.google.com/d/msg/ros-sig-aldebaran/Cu18gewN41Y/xWXu9hSqAwAJ by Ariel Bistritsky, reproduced by Josef Gerauer-Aigner.

I tried to launch the pepper_bringup.launch but I hed the next error:

[ERROR] [1508861764.274247278]: Motion: Failed to get robot body names! Trace: ALMotion::getBodyNames Could not parse "LArmRArm" as a valid joint name, chain name or "Body" [naoqi_dcm_driver-2] process has died [pid 24774, exit code -11, cmd /opt/ros/indigo/lib/naoqi_dcm_driver/naoqi_dcm_driver name:=naoqi_dcm_driver log:=/home/peppercom/.ros/log/9cba558c-b8cf-11e7-abad-d8cb8a065d13/naoqi_dcm_driver-2.log]. log file: /home/peppercom/.ros/log/9cba558c-b8cf-11e7-abad-d8cb8a065d13/naoqi_dcm_driver-2*.log

does anyone else had the same problem? how can I fix it?

Happens on the the Debian package on ROS Indigo. Worked around by recompiling the dcm_driver.

nlyubova commented 6 years ago

Hello Victor, to fix this you need to compile all packages from source.

mikaelarguedas commented 6 years ago

@nlyubova I'm unfamiliar with the issue so maybe its not possible, but could this be fixed by releasing a new version of the Debian package?

nlyubova commented 6 years ago

@mikaelarguedas after checking it more carefully, it seams that all released dependencies are up to date. Also checked the released versions with apt-get on my PC and it works.

@victorpaleologue did you try to update your installed version? or remove and install again? which ROS version do you use? which Ubuntu?

victorpaleologue commented 6 years ago

@nlyubova I did not try it, I only reported it from the ROS Aldebaran group.

nlyubova commented 6 years ago

@victorpaleologue thanks Victor for reporting, I've answered in the group. There was already a similar issue reported here on GitHub some months ago and it was resolved. I would be glad to know about the current status now so that we can close it