Comments (5)
I have a similar issue:
Could not find resource 'joint_back_right_steer' in 'hardware_interface::EffortJointInterface'.
from summit_xl_sim.
Do you have installed the package ros-kinetic-effort-controllers?
from summit_xl_sim.
Can you describe in detail about How you solve the controller manager problem? I meet the same.
Thanks in advance.
from summit_xl_sim.
Firstly, if you simply want a stable camera view at an appropriate angle, consider switching the PTZ Camera A's topic in RVIZ to /summit_xl_a/front_rgbd_camera/rgb/image_raw. If however, you want to be able to control the PTZ camera, read the rest of this post.
I found the problem to be in the package summit_xl_control.
in the config file: summit_xl_control/config/summit_xl_a_control.yaml
I changed the "type" field of the "joint_pan_position_controller" and "joint_tilt_position_controller" from velocity_controllers/JointPositionController to position_controllers/JointPositionController. The issue is that the sensor uses the PositionJointInterface which requires the position_controllers to be loaded and not the velocity_controllers. However, This causes the following errors, due to the "gravity bug":
[ WARN] [1549347112.630936629, 0.002000000]: The default_robot_hw_sim plugin is using the Joint::SetPosition method without preserving the link velocity.
[ WARN] [1549347112.630997293, 0.002000000]: As a result, gravity will not be simulated correctly for your model.
[ WARN] [1549347112.631032544, 0.002000000]: Please set gazebo_pid parameters, switch to the VelocityJointInterface or EffortJointInterface, or upgrade to Gazebo 9.
[ WARN] [1549347112.631067450, 0.002000000]: For details, see ros-simulation/gazebo_ros_pkgs#612
To fix this, I changed from position_controllers/JointPositionController to effort_controllers/JointPositionController. An additional change is required then in the robotnik_sensores package. In .../robotnik_sensors/urdf/axis.urdf.xacro, the 4 harwareInterface tags have to be updated from hardware_interface/PositionJointInterface to hardware_interface/EffortJointInterface. Also in this file, set the pan_joint's lower and upper limits to -1.5708 and 1.5708 to avoid problems with the controllers angle error calculation. This changes the controller from a position_controllers to effort_controllers and gets rid of the gravity bug. Stable PID values for the effort_controller are: {p: 100.0, i: 0.0, d: 12.5}
from summit_xl_sim.
Firstly, if you simply want a stable camera view at an appropriate angle, consider switching the PTZ Camera A's topic in RVIZ to /summit_xl_a/front_rgbd_camera/rgb/image_raw. If however, you want to be able to control the PTZ camera, read the rest of this post.
I found the problem to be in the package summit_xl_control.
in the config file: summit_xl_control/config/summit_xl_a_control.yamlI changed the "type" field of the "joint_pan_position_controller" and "joint_tilt_position_controller" from velocity_controllers/JointPositionController to position_controllers/JointPositionController. The issue is that the sensor uses the PositionJointInterface which requires the position_controllers to be loaded and not the velocity_controllers. However, This causes the following errors, due to the "gravity bug":
[ WARN] [1549347112.630936629, 0.002000000]: The default_robot_hw_sim plugin is using the Joint::SetPosition method without preserving the link velocity.
[ WARN] [1549347112.630997293, 0.002000000]: As a result, gravity will not be simulated correctly for your model.
[ WARN] [1549347112.631032544, 0.002000000]: Please set gazebo_pid parameters, switch to the VelocityJointInterface or EffortJointInterface, or upgrade to Gazebo 9.
[ WARN] [1549347112.631067450, 0.002000000]: For details, see ros-simulation/gazebo_ros_pkgs#612To fix this, I changed from position_controllers/JointPositionController to effort_controllers/JointPositionController. An additional change is required then in the robotnik_sensores package. In .../robotnik_sensors/urdf/axis.urdf.xacro, the 4 harwareInterface tags have to be updated from hardware_interface/PositionJointInterface to hardware_interface/EffortJointInterface. Also in this file, set the pan_joint's lower and upper limits to -1.5708 and 1.5708 to avoid problems with the controllers angle error calculation. This changes the controller from a position_controllers to effort_controllers and gets rid of the gravity bug. Stable PID values for the effort_controller are: {p: 100.0, i: 0.0, d: 12.5}
Has anyone fixed this issue using this solution? I am currently facing the same issue and the solution doesn't seem to work.
The config file summit_xl_control/config/summit_xl_a_control.yaml is nowhere to be found. I used the setup instructions mentioned in the git. I am using ROS Kinetic and gazebo 7 on ubuntu 16.04
from summit_xl_sim.
Related Issues (20)
- The model placed on gazebo is not moving with cmd_vel topics. HOT 2
- ImportError: dynamic module does not define module export function (PyInit__tf2) HOT 2
- pid_gains not defined HOT 3
- Simulation with diff_drive_controller/DiffDriveController not working properly
- Running simulation of the Summit X_WAM platform HOT 4
- LaserScan-Topic just shows INF using Gazebo HOT 3
- Gazebo simulation- Wheels of SUMMIT XL robot not rotating in gazebo HOT 6
- Gazebo- Front wheels of SUMMIT XL yields erratic motion (lifting upwards) when trying to move in straight line. HOT 1
- Summit XL does not move in the desired path in Gazebo. HOT 1
- Output odom response does not match the step input HOT 4
- Tuning PID in gazebo for SUMMIT XL Robot HOT 1
- Robot localization using aruco marker in gazebo
- robot_map is never published in simulation HOT 1
- Summit XL steel errors during launch
- The real-time angular velocity obtained by summit xl steel in the simulation is not consistent with the speed we released. HOT 6
- Error docker installation HOT 2
- Why the topic of battery is zero?
- an issue in summit_xls simulation: missing odom and map frames, no map received for local costmap
- Docker, rosdep update not working because of end-of-live
- on the humble branch, you are using ROS commands not ROS2 commands.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from summit_xl_sim.