pal-robotics / talos_simulation

GNU Lesser General Public License v3.0
3 stars 1 forks source link

talos gazebo simulation error!!:( #1

Closed cnun02 closed 4 years ago

cnun02 commented 4 years ago

I have truble talos gazebo simulation..

errors are these..

my simulation environment setting is

ubuntu 18.04, ros melodic, gazebo9

[ERROR] [1589464868.833742426, 0.377000000]: No p gain specified for pid. Namespace: /gazebo_ros_control/pid_gains/arm_left_5_joint [ WARN] [1589464868.833771882, 0.377000000]: Transmission wrist_left_trans has more than one joint. Currently the default robot hardware simulation interface only supports one. [ WARN] [1589464868.833782669, 0.377000000]: Joint arm_left_1_joint of transmission arm_left_1_trans specifies multiple hardware interfaces. Currently the default robot hardware simulation interface only supports one. Using the first entry [ERROR] [1589464868.834261038, 0.377000000]: No p gain specified for pid. Namespace: /gazebo_ros_control/pid_gains/arm_left_1_joint [ WARN] [1589464868.834282492, 0.377000000]: Joint arm_left_2_joint of transmission arm_left_2_trans specifies multiple hardware interfaces. Currently the default robot hardware simulation interface only supports one. Using the first entry [ERROR] [1589464868.834666258, 0.377000000]: No p gain specified for pid. Namespace: /gazebo_ros_control/pid_gains/arm_left_2_joint [ WARN] [1589464868.834682895, 0.377000000]: Joint arm_left_3_joint of transmission arm_left_3_trans specifies multiple hardware interfaces. Currently the default robot hardware simulation interface only supports one. Using the first entry [ERROR] [1589464868.835072522, 0.377000000]: No p gain specified for pid. Namespace: /gazebo_ros_control/pid_gains/arm_left_3_joint [ WARN] [1589464868.835088401, 0.377000000]: Joint arm_left_4_joint of transmission arm_left_4_trans specifies multiple hardware interfaces. Currently the default robot hardware simulation interface only supports one. Using the first entry [ERROR] [1589464868.835500019, 0.377000000]: No p gain specified for pid. Namespace: /gazebo_ros_control/pid_gains/arm_left_4_joint [ WARN] [1589464868.835515336, 0.377000000]: Joint arm_right_5_joint of transmission arm_right_5_trans specifies multiple hardware interfaces. Currently the default robot hardware simulation interface only supports one. Using the first entry [ERROR] [1589464868.835897955, 0.377000000]: No p gain specified for pid. Namespace: /gazebo_ros_control/pid_gains/arm_right_5_joint [ WARN] [1589464868.835918271, 0.377000000]: Transmission wrist_right_trans has more than one joint. Currently the default robot hardware simulation interface only supports one. [ WARN] [1589464868.835930403, 0.377000000]: Joint arm_right_1_joint of transmission arm_right_1_trans specifies multiple hardware interfaces. Currently the default robot hardware simulation interface only supports one. Using the first entry [ERROR] [1589464868.836296266, 0.377000000]: No p gain specified for pid. Namespace: /gazebo_ros_control/pid_gains/arm_right_1_joint [ WARN] [1589464868.836317376, 0.377000000]: Joint arm_right_2_joint of transmission arm_right_2_trans specifies multiple hardware interfaces. Currently the default robot hardware simulation interface only supports one. Using the first entry [ERROR] [1589464868.836649358, 0.377000000]: No p gain specified for pid. Namespace: /gazebo_ros_control/pid_gains/arm_right_2_joint [ WARN] [1589464868.836668838, 0.377000000]: Joint arm_right_3_joint of transmission arm_right_3_trans specifies multiple hardware interfaces. Currently the default robot hardware simulation interface only supports one. Using the first entry [ERROR] [1589464868.836951201, 0.377000000]: No p gain specified for pid. Namespace: /gazebo_ros_control/pid_gains/arm_right_3_joint [ WARN] [1589464868.836966200, 0.377000000]: Joint arm_right_4_joint of transmission arm_right_4_trans specifies multiple hardware interfaces. Currently the default robot hardware simulation interface only supports one. Using the first entry [ERROR] [1589464868.837247980, 0.377000000]: No p gain specified for pid. Namespace: /gazebo_ros_control/pid_gains/arm_right_4_joint [ WARN] [1589464868.837261638, 0.377000000]: Joint gripper_left_joint of transmission gripper_left_trans specifies multiple hardware interfaces. Currently the default robot hardware simulation interface only supports one. Using the first entry [FATAL] [1589464868.837274054, 0.377000000]: No matching hardware interface found for 'hardware_interface/JointStateInterface' while loading interfaces for gripper_left_joint [FATAL] [1589464868.837343497, 0.377000000]: Could not initialize robot simulation interface [ INFO] [1589464868.841352957, 0.377000000]: Loading gazebo WORLD ODOMETRY RPY plugin [ INFO] [1589464868.841410781, 0.377000000]: world odometry plugin missing <updateRate>, defaults to 1000.000000 [spawn_model-4] process has finished cleanly log file: /home/asl/.ros/log/59775c74-95eb-11ea-ab56-9f4e2488a24e/spawn_model-4*.log [ WARN] [1589464873.737680800, 5.222000000]: Waiting for left_arm_controller/follow_joint_trajectory to come up [ WARN] [1589464879.771947921, 11.222000000]: Waiting for left_arm_controller/follow_joint_trajectory to come up [ERROR] [1589464885.818546179, 17.222000000]: Action client not connected: left_arm_controller/follow_joint_trajectory [ WARN] [1589464890.884902002, 22.234000000]: Waiting for right_arm_controller/follow_joint_trajectory to come up [ WARN] [1589464896.926266775, 28.234000000]: Waiting for right_arm_controller/follow_joint_trajectory to come up [WARN] [1589464897.034166, 28.339000]: Controller Spawner couldn't find the expected controller_manager ROS interface. [bringup_controllers_spawner-7] process has finished cleanly log file: /home/asl/.ros/log/59775c74-95eb-11ea-ab56-9f4e2488a24e/bringup_controllers_spawner-7*.log [ERROR] [1589464902.978780837, 34.234000000]: Action client not connected: right_arm_controller/follow_joint_trajectory [ WARN] [1589464908.083560282, 39.296000000]: Waiting for head_controller/follow_joint_trajectory to come up [ WARN] [1589464914.122971743, 45.296000000]: Waiting for head_controller/follow_joint_trajectory to come up [ERROR] [1589464920.152785285, 51.296000000]: Action client not connected: head_controller/follow_joint_trajectory [ WARN] [1589464925.285662446, 56.398000000]: Waiting for torso_controller/follow_joint_trajectory to come up [ WARN] [1589464931.316867145, 62.399000000]: Waiting for torso_controller/follow_joint_trajectory to come up [ERROR] [1589464937.354294532, 68.399000000]: Action client not connected: torso_controller/follow_joint_trajectory [ WARN] [1589464942.397247918, 73.412000000]: Waiting for left_gripper_controller/follow_joint_trajectory to come up [ WARN] [1589464948.445179575, 79.412000000]: Waiting for left_gripper_controller/follow_joint_trajectory to come up [ERROR] [1589464954.508591370, 85.412000000]: Action client not connected: left_gripper_controller/follow_joint_trajectory

and...

WTF!!!!!!

default_gzclient_camera(1)-2020-05-14T23_06_06 362335

please help me.....:(

v-lopez commented 4 years ago

Hello, let's see if we can find out what is going on.

Are you using our tutorials? http://wiki.ros.org/Robots/TALOS/Tutorials

Make sure you follow all the steps carefully. Specially the installation steps.

In case it still happens, we need the commands you execute and the full properly formatted output.

cnun02 commented 4 years ago

hi~ v-lopez!

I used that tutorials.

but, my environment is melodic..

how can i solve that problem in my environment?

v-lopez commented 4 years ago

Let us take a look and hopefully we'll have a working version by the end of next week.

cnun02 commented 4 years ago

I fixed previous errors!!

but,

I want talos walking control real-time using F710 ..

so, I launched roslaunch talos_controller_configuration_gazebo walking_controller.launch

but, [ERROR] [1589627840.474410154, 1096.683000000]: Could not load controller 'walking_controller' because controller type 'walking_controller/ReemcControl' does not exist.

How can I solve these problem??

(rosrun play_motion run_motion wave was activated successfully)

please help me!!

v-lopez commented 4 years ago

At the moment our walking controller is not open source, we're collaborating in a ROSIN initiative to make an open source walking controller: https://www.rosin-project.eu/ftp/open-source-balancing-and-walking-control-framework-for-humanoid-robots-in-ros-openwalker