unable to setup reemc simulation env
Hi,
1) first question: I have a fresh installation of ubuntu 16.04 and of ROS kinetic. I'm following these instructions to get the necessary packages:
http://wiki.ros.org/Robots/REEM-C/Tutorials/Installation/Simulation
At the stage where I need to check the dependencies with the following command:
rosdep install --from-paths src --ignore-src --rosdistro kinetic --skip-keys="opencv2 pal_laser_filters speed_limit_node sensor_to_cloud hokuyo_node libdw-dev gmock walking_utils rqt_current_limit_controller simple_grasping_action reemc_init_offset_controller walking_controller"
I get the error:
rosdep install --from-paths src --ignore-src --rosdistro kinetic --skip-keys="opencv2 pal_laser_filters speed_limit_node sensor_to_cloud hokuyo_node libdw-dev gmock walking_utils rqt_current_limit_controller simple_grasping_action reemc_init_offset_controller walking_controller"
When I build the workspace the following (obviously) occurs:
Failed << pal_walking_msgs:cmake [ Exited with code 1 ]
Failed <<< pal_walking_msgs [ 1.3 seconds ]
Abandoned <<< reemc_moveit_config [ Unrelated job failed ]
Abandoned <<< teleop_tools_msgs [ Unrelated job failed ]
Abandoned <<< tf_lookup [ Unrelated job failed ]
Abandoned <<< twist_mux_msgs [ Unrelated job failed ]
Abandoned <<< combined_robot_hw [ Unrelated job failed ]
Abandoned <<< controller_interface [ Unrelated job failed ]
Abandoned <<< joint_limits_interface [ Unrelated job failed ]
Abandoned <<< pal_hardware_interfaces [ Unrelated job failed ]
Abandoned <<< transmission_interface [ Unrelated job failed ]
Abandoned <<< ros_control_monitor [ Unrelated job failed ]
Abandoned <<< rqt_joint_trajectory_controller [ Unrelated job failed ]
Abandoned <<< gazebo_plugins [ Unrelated job failed ]
Abandoned <<< gazebo_ros [ Unrelated job failed ]
Abandoned <<< pal_web_msgs [ Unrelated job failed ]
Abandoned <<< reemc_asr_tutorials [ Unrelated job failed ]
Abandoned <<< reemc_tts_tutorials [ Unrelated job failed ]
Abandoned <<< pal_carbon_collector [ Unrelated job failed ]
Abandoned <<< pal_statistics [ Unrelated job failed ]
Abandoned <<< actuator_state_controller [ Unrelated job failed ]
Abandoned <<< controller_manager [ Unrelated job failed ]
Abandoned <<< controller_manager_tests [ Unrelated job failed ]
Abandoned <<< combined_robot_hw_tests [ Unrelated job failed ]
Abandoned <<< diff_drive_controller [ Unrelated job failed ]
Abandoned <<< force_torque_sensor_controller [ Unrelated job failed ]
Abandoned <<< forward_command_controller [ Unrelated job failed ]
Abandoned <<< effort_controllers [ Unrelated job failed ]
Abandoned <<< four_wheel_steering_controller [ Unrelated job failed ]
Abandoned <<< gripper_action_controller [ Unrelated job failed ]
Abandoned <<< imu_sensor_controller [ Unrelated job failed ]
Abandoned <<< joint_state_controller [ Unrelated job failed ]
Abandoned <<< joint_torque_sensor_state_controller [ Unrelated job failed ]
Abandoned <<< joint_trajectory_controller [ Unrelated job failed ]
Abandoned <<< joy_teleop [ Unrelated job failed ]
Abandoned <<< mode_state_controller [ Unrelated job failed ]
Abandoned <<< pal_gazebo_plugins [ Unrelated job failed ]
Abandoned <<< dynamic_introspection [ Unrelated job failed ]
Abandoned <<< position_controllers [ Unrelated job failed ]
Abandoned <<< play_motion [ Unrelated job failed ]
Abandoned <<< realsense_gazebo_plugin [ Unrelated job failed ]
Abandoned <<< reemc_basic_tutorials [ Unrelated job failed ]
Abandoned <<< reemc_bringup [ Unrelated job failed ]
Abandoned <<< reemc_controller_configuration [ Unrelated job failed ]
Abandoned <<< reemc_controller_configuration_gazebo [ Unrelated job failed ]
Abandoned <<< reemc_description [ Unrelated job failed ]
Abandoned <<< reemc_gazebo [ Unrelated job failed ]
Abandoned <<< reemc_motion_tutorials [ Unrelated job failed ]
Abandoned <<< reemc_perception_tutorials [ Unrelated job failed ]
Abandoned <<< reemc_vision_tutorials [ Unrelated job failed ]
Abandoned <<< rqt_controller_manager [ Unrelated job failed ]
Abandoned <<< temperature_sensor_controller [ Unrelated job failed ]
Abandoned <<< gazebo_ros_control [ Unrelated job failed ]
Abandoned <<< pal_hardware_gazebo [ Unrelated job failed ]
Abandoned <<< pal_transmissions [ Unrelated job failed ]
Abandoned <<< reemc_effort_control [ Unrelated job failed ]
Abandoned <<< reemc_hardware_gazebo [ Unrelated job failed ]
Abandoned <<< twist_mux [ Unrelated job failed ]
Abandoned <<< velocity_controllers [ Unrelated job failed ]
Finished <<< pal_wifi_localization_msgs [ 4.1 seconds ]
Finished <<< play_motion_msgs [ 5.7 seconds ]
Finished <<< pal_visual_localization_msgs [ 6.4 seconds ]
[build] Summary: 29 of 87 packages succeeded.
[build] Ignored: 8 packages were skipped or are blacklisted.
[build] Warnings: None.
[build] Abandoned: 57 packages were abandoned.
[build] Failed: 1 packages failed.
[build] Runtime: 1 minute and 8.4 seconds total.
[build] Note: Workspace packages have changed, please re-source setup files to use them.
I initially tried to set up ubuntu 16.04 and the rest in a docker, which didn't work the way I described it above, so I installed everything in the usual in a separate partition on my computer, and I face the same issue.
Any idea how I could get these packages installed?
2) second question: if I go on from there and launch reemc-gazebo with the command:
roslaunch reemcgazebo reemcempty_world.launch
I get as error:
... logging to /home/reavhen/.ros/log/1fb4025a-fb09-11ec-89a8-b88a60b44b5f/roslaunch-BenPC-5335.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
xacro: Traditional processing is deprecated. Switch to --inorder processing!
To check for compatibility of your document, use option --check-order.
For more infos, see http://wiki.ros.org/xacro#Processing_Order
inconsistent namespace redefinitions for xmlns:xacro:
old: http://www.ros.org/wiki/xacro
new: http://ros.org/wiki/xacro (/home/reavhen/reemc_ws/src/reemc_robot/reemc_description/urdf/leg/leg.urdf.xacro)
inconsistent namespace redefinitions for xmlns:xacro:
old: http://www.ros.org/wiki/xacro
new: http://ros.org/wiki/xacro (/home/reavhen/reemc_ws/src/reemc_robot/reemc_description/urdf/torso/torso.urdf.xacro)
variable filename is supported with --inorder option only None None
when processing file: /home/reavhen/reemc_ws/src/reemc_robot/reemc_description/robots/reemc_full_ft_hey5.urdf.xacro
while processing /home/reavhen/reemc_ws/src/reemc_simulation/reemc_gazebo/launch/reemc_gazebo.launch:
while processing /home/reavhen/reemc_ws/src/reemc_simulation/reemc_gazebo/launch/reemc_spawn.launch:
while processing /home/reavhen/reemc_ws/src/reemc_robot/reemc_description/robots/upload_reemc.launch:
Invalid <param> tag: Cannot load command parameter [robot_description]: command [xacro '/home/reavhen/reemc_ws/src/reemc_robot/reemc_description/robots/reemc_full_ft_hey5.urdf.xacro' head_version:=v0 leg_version:=v0] returned with code [2].
Param xml is <param command="xacro '$(find reemc_description)/robots/reemc_$(arg robot).urdf.xacro' head_version:=$(arg head_version) leg_version:=$(arg leg_version)" name="robot_description"/>
The traceback for the exception was written to the log file
I did read the following:
And corrected the .launch file with the following:
<param name="robot_description" command="rosrun xacro xacro --inorder '/path/to/workspace/reemc_ws/src/reemc_robot/reemc_description/robots/reemc_full_ft_hey5.urdf.xacro' head_version:=$(arg head_version) l$
I don't understand why this error is still in the package and hasn't been corrected. Any idea how I could convey this information to the right person so that this gets corrected?
Thanks, hope I could make myself understandable, first post here.
Cheers
Benoit
Asked by Benoit on 2022-07-03 15:11:44 UTC
Answers
Hello @Benoit,
As you can see from the tutorials page of REEM-C it currently supports only Melodic and you are trying to compile the packages in Kinetic, it doesn't support it anymore. I recommend you to upgrade your machine to install Melodic or use melodic dockers to compile and use the tutorials.
Thank you
Asked by saikishor on 2022-07-05 03:19:56 UTC
Comments
Hi Saikishor,
Thanks for following up. I solved the issue by installing missing dependencies one by one with the command:
catkin_make - - pkg packageName
Then while debigging with a colleague we realized I initially built my workspace using catkin build instead of catkin_make. I'm not sure this is related but I thought I'd mention it. We cleared the built ws and rebuilt it, still didn't work until I installed the packages one by one.
I had previously tried the Docker option but ran into beginner's issues and thought I might as well start with a fresh system.
It works not so thanks for your support - cheers
Asked by Benoit on 2022-07-08 11:38:29 UTC
Comments
Regarding the issue with the robot_description param, I am not able to reproduce it. It is strange that you are facing it
Asked by saikishor on 2022-07-06 03:00:07 UTC