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

'Unable to initialize' group in MoveIt Commander

asked 2018-12-18 11:45:38 -0600

hbirdj gravatar image

Hi, I've been working on developing a pick and place operation using a Fanuc M10iA, but I've run into a wall while working through this tutorial. I can get demo.launch working as expected with planning and executing paths in RViz, but the python script can never initialize a group.

From the command: use <group_name>

I always get the response: Unable to initialize <group_name>

I tried creating new groups in the srdf using different naming schemes, and I also got the same issue switching to the panda arm used in the tutorial

I did have some issues with pyassimp getting the python script to run initially, and wondering if it's a continuation of that.

Using Kinetic and Ubuntu 16.04

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2018-12-19 10:42:05 -0600

aPonza gravatar image

Trying with my own Panda I can see it should work if you use manipulator, assuming the correct srdf is this one. At the very least, this is my own IO:

$ rosrun moveit_commander moveit_commander_cmdline.py
[ INFO] [1545237637.362904035]: Loading robot model 'panda'...
[ INFO] [1545237637.427494951]: Loading robot model 'panda'...

Waiting for commands. Type 'help' to get a list of known commands.

> use panda_arm
[ INFO] [1545237642.953916840]: Ready to take commands for planning group panda_arm.
OK
panda_arm>
edit flag offensive delete link more

Comments

Yep, that's where I'm trying to reach. After inputting 'use' I get tab completion for the active groups, so it knows they're around, it just can't initialize. I'm trying to work backward through the code, but I'm not sure where to go beyond here...

hbirdj gravatar image hbirdj  ( 2018-12-20 04:54:13 -0600 )edit

I see, I had not understood. I don't know if there's a better way to debug the issue, but I know you could try rosrun rqt_logger_level rqt_logger_level, setting the logging level to Debug for /move_group_commander_wrappers_(...) to see which connection isn't enstablished.

aPonza gravatar image aPonza  ( 2018-12-20 07:25:18 -0600 )edit
1

Thanks! I had hadn't learned how to enable that logging yet. And it led me to the real issue, which is that I needed to try in a new terminal. Still unsure what the core issue was though.

hbirdj gravatar image hbirdj  ( 2018-12-20 09:17:09 -0600 )edit

Question Tools

2 followers

Stats

Asked: 2018-12-18 11:45:38 -0600

Seen: 1,091 times

Last updated: Dec 19 '18