Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

trouble starting environment server for arm_navigation stack

I'm working with the new electric arm_navigation stack. I went through the wizard and am working with my auto generated launch and config files. So when I launch my arm_navigation launch file, everything seems fine except it continues to get hung up on:

[ INFO] : waitForService: Service [/register_planning_scene] has not been advertised, waiting...
[ INFO] : Robot frame is base_link
[ INFO] : Waiting for robot state ...
[ INFO] : Waiting for joint state ...
[ WARN] : Got joint state update but did not update some joints for more than 1 second.  Turn on DEBUG for more info
[ INFO] : Waiting for environment server planning scene registration service /register_planning_scene
[ INFO] : waitForService: Service [/register_planning_scene] has not been advertised, waiting...
[ INFO] : Waiting for environment server planning scene registration service /register_planning_scene
[ INFO] : waitForService: Service [/register_planning_scene] has not been advertised, waiting...
[ INFO] : Waiting for robot state ...
[ INFO] : Waiting for joint state ...

....If I don't include the environment server by commenting the following out of my launch file....

<include file="$(find planning_environment)/launch/environment_server.launch">
    <arg name="use_monitor" value="true" />
    <arg name="use_collision_map" value="false" />
</include>

....then it stops complaining. But of course if I don't include the environment server then I can't run any of my clients to move the arm.

I've already found this thread but I'm already doing a fake publisher and the problem persists even when I don't include the joints I'm having to fake publish.

Has anyone dealt with this issue before or do I seem to be forgetting a small but cruicial step in getting this to launch?

Thanks.

trouble starting environment server for arm_navigation stack

I'm working with the new electric arm_navigation stack. I went through the wizard and am working with my auto generated launch and config files. So when I launch my arm_navigation launch file, everything seems fine except it continues to get hung up on:

[ INFO] : waitForService: Service [/register_planning_scene] has not been advertised, waiting...
[ INFO] : Robot frame is base_link
[ INFO] : Waiting for robot state ...
[ INFO] : Waiting for joint state ...
[ WARN] : Got joint state update but did not update some joints for more than 1 second.  Turn on DEBUG for more info
[ INFO] : Waiting for environment server planning scene registration service /register_planning_scene
[ INFO] : waitForService: Service [/register_planning_scene] has not been advertised, waiting...
[ INFO] : Waiting for environment server planning scene registration service /register_planning_scene
[ INFO] : waitForService: Service [/register_planning_scene] has not been advertised, waiting...
[ INFO] : Waiting for robot state ...
[ INFO] : Waiting for joint state ...

....If I don't include the environment server by commenting the following out of my launch file....

<include file="$(find planning_environment)/launch/environment_server.launch">
    <arg name="use_monitor" value="true" />
    <arg name="use_collision_map" value="false" />
</include>

....then it stops complaining. But of course if I don't include the environment server then I can't run any of my clients to move the arm.

I've already found this thread but I'm already doing a fake publisher and the problem persists even when I don't include the joints I'm having to fake publish.

Has anyone dealt with this issue before or do I seem to be forgetting a small but cruicial step in getting this to launch?

Thanks.