# MoveIt errors when setting up Rosject

**URL:** <https://get-help.theconstruct.ai/t/moveit-errors-when-setting-up-rosject/32967>\
**Category:** ROSDS Support\
**Tags:** error, moveit\
**Created:** [October 11, 2024, 4:23pm UTC](https://get-help.theconstruct.ai/t/moveit-errors-when-setting-up-rosject/32967 "2024-10-11T16:23:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dorteel](https://get-help.theconstruct.ai/user_avatar/get-help.theconstruct.ai/dorteel/32/6967_2.png) [@dorteel](https://get-help.theconstruct.ai/u/dorteel)\
**Post date:** [October 11, 2024, 4:23pm UTC](https://get-help.theconstruct.ai/t/moveit-errors-when-setting-up-rosject/32967/1 "2024-10-11T16:23:29Z")

</div>

I’m trying to set up my Locobot Wx250s arm with MoveIt using the MoveIt Setup Assistant.  
There are two issues, one of them is an annoyance, the other one critical.

1. When trying to load the urdf through the GUI of the assistant, sometimes I get an error that the ros master can’t be contacted.

```auto
[INFO] [1728662961.240113530]: Loaded locobot robot model.
[INFO] [1728662961.245363550]: Setting Param Server with Robot Description
[ERROR] [1728662961.246092479]: [setParam] Failed to contact master at [2_xterm:11311]. Retrying...

```

Sometimes starting a roscore in another terminal helps, sometimes it doesn’t.

When I get through error 1, I continue setting up my robot using the GUI, but when I click on Author Information, the Setup Assistant crashes with the following error:

```auto
================================================================================REQUIRED process [moveit_setup_assistant-1] has died!
process has died [pid 30808, exit code -11, cmd /opt/ros/noetic/lib/moveit_setup_assistant/moveit_setup_assistant __name:=moveit_setup_assistant__ log:=/home/user/.ros/log/1f26ecc8-87eb-11ef-8e86-0242ac150008/moveit_setup_assistant-1.log].
log file: /home/user/.ros/log/1f26ecc8-87eb-11ef-8e86-0242ac150008/moveit_setup_assistant-1*.log
Initiating shutdown!
================================================================================

```

Clicking on Configuration Files instead also results in the same crash.

Any help would be greatly appreciated.

Steps to reproduce:  
Fork the rosject: [https://app.theconstruct.ai/l/65720807/](https://app.theconstruct.ai/l/65720807/)  
`roslaunch moveit_setup_assistant setup_assistant.launch`

urdf of the robot is locobot.urdf.xacro in the urdf folder (also pinned as a shortcut)

---

<div class="post-metadata">

**Author:** ![roalgoal](https://get-help.theconstruct.ai/user_avatar/get-help.theconstruct.ai/roalgoal/32/7280_2.png) [@roalgoal](https://get-help.theconstruct.ai/u/roalgoal)\
**Post date:** [October 14, 2024, 10:29am UTC](https://get-help.theconstruct.ai/t/moveit-errors-when-setting-up-rosject/32967/2 "2024-10-14T10:29:29Z")

</div>

Hi @dorteel, I was able to reproduce the first error you are describing. I think the terminal is not connecting correctly to the master which, in the rosjects, runs at `ROS_MASTER_URI=http://1_xterm:11311` by default (`1_xterm` is the hostname)

I was able to get around the error simply by killing the MoveIt setup assistant and running it again in the same terminal. Once I loaded the URDF, I was able to input info in `Author Information` and `Configuration Files`:

![moveit-assistant-noetic](https://get-help.theconstruct.ai/uploads/default/original/2X/e/e0f2176fa67998af445d7daa791f0390d2ffa21e.gif)

---

<div class="post-metadata">

**Author:** ![system](https://get-help.theconstruct.ai/uploads/default/original/2X/9/9d3ce8305cc0d0d9b6e07d15767a6f245c526f1b.jpeg) [@system](https://get-help.theconstruct.ai/u/system)\
**Post date:** [October 24, 2024, 10:29am UTC](https://get-help.theconstruct.ai/t/moveit-errors-when-setting-up-rosject/32967/3 "2024-10-24T10:29:50Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.