You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have found what I think is an oversight/bug in MoveIt Setup Assistant. The gist of it is that if you never click on the ros2_control URDF Modifications section of the MSA, it seems to assume that you are not using ros2_control. But if you do click on the ros2_control URDF Modifications section of the MSA, it seems to assume that you are using ros2_control, and there is no way to "reset" it so it doesn't generate files assuming you will not use ros2_control other than to restart the MSA.
For context, I am working on MotoROS2, which does not use ros2_control. But while generating config files using the MSA, I noticed that ros2_control stuff kept on getting populated even though I didn't want it to be. For example motoman_gp12.ros2_contro.xacro, initial_positions.yaml, and motoman_gp12.urdf.xacro were being created. Not only that, but files that I did want to be created were getting modified with ros2_control information. For example, .setup_assistant had ros2_control stuff.
I believe that there should be a toggle button "Configure to use ros2_control" or something to that effect. Somebody not using ros2_control could easily click on the ros2_control URDF Modifications section accidentally or just to check what it is/if they need to disable it. And even if they deselect the ros2_control components in the last step, some of the generated files that they do want (e.g. .setup_assistant) will not be properly generated.
ROS Distro
Humble
OS and version
Ubuntu 22.04
Source or binary build?
Binary
If binary, which release version?
2.5.7
If source, which branch?
No response
Which RMW are you using?
None
Steps to Reproduce
Go through the MSA process without EVER clicking on ros2_control URDF Modifications and it should look like this at the last step:
Then generate the files and take a look at the generated .setup_assistant file. It should look like this:
Description
I have found what I think is an oversight/bug in MoveIt Setup Assistant. The gist of it is that if you never click on the
ros2_control URDF Modifications
section of the MSA, it seems to assume that you are not usingros2_control
. But if you do click on theros2_control URDF Modifications
section of the MSA, it seems to assume that you are usingros2_control
, and there is no way to "reset" it so it doesn't generate files assuming you will not useros2_control
other than to restart the MSA.For context, I am working on MotoROS2, which does not use
ros2_control
. But while generating config files using the MSA, I noticed thatros2_control
stuff kept on getting populated even though I didn't want it to be. For examplemotoman_gp12.ros2_contro.xacro
,initial_positions.yaml
, andmotoman_gp12.urdf.xacro
were being created. Not only that, but files that I did want to be created were getting modified withros2_control
information. For example,.setup_assistant
hadros2_control
stuff.I believe that there should be a toggle button "Configure to use
ros2_control
" or something to that effect. Somebody not usingros2_control
could easily click on theros2_control URDF Modifications
section accidentally or just to check what it is/if they need to disable it. And even if they deselect theros2_control
components in the last step, some of the generated files that they do want (e.g..setup_assistant
) will not be properly generated.ROS Distro
Humble
OS and version
Ubuntu 22.04
Source or binary build?
Binary
If binary, which release version?
2.5.7
If source, which branch?
No response
Which RMW are you using?
None
Steps to Reproduce
Go through the MSA process without EVER clicking on
ros2_control URDF Modifications
and it should look like this at the last step:Then generate the files and take a look at the generated
.setup_assistant
file. It should look like this:Go through the MSA process while clicking on the
ros2_control URDF Modifications
and it should look like this at the last step:Then generate the files and take a look at the generated
.setup_assistant
file. It should look like this:I have also tried setting the command interfaces and state interfaces to all be empty, but that does not fix the problem.
Expected behavior
I can generate config files that do not use
ros2_control
Actual behavior
ros2_control
config files are generatedBacktrace or Console output
No response
The text was updated successfully, but these errors were encountered: