 | 1 | initial version |
In the DRCSim 2.0, I have noticed that when sending position commands (to say for example the neck_ay joint), that the velocities reported by /atlas/joint_states are much higher than the velocity_limits defined in the URDF.
Can we expect this to be fixed for the VRC, or should we continue to assume that we can see velocity and/or effort values that exceed the URDF limits?
| | 2 | No.2 Revision |
In the DRCSim 2.0, I have noticed that when sending position commands (to say for example the neck_ay joint), that the velocities reported by /atlas/joint_states are much higher than the velocity_limits defined in the URDF.
Can we expect this to be fixed for the VRC, or should we continue to assume that we can see velocity and/or effort values that exceed the URDF limits?
| | 3 | No.3 Revision |
In the DRCSim 2.0, I have noticed that when sending position commands (to say for example the neck_ay joint), that the velocities reported by /atlas/joint_states are much higher than the velocity_limits defined in the URDF.
Can we expect this to be fixed for the VRC, or should we continue to assume that we can see velocity and/or effort values that exceed the URDF limits?
| | 4 | No.4 Revision |
In the DRCSim 2.0, I have noticed that when sending position commands (to say for example the neck_ay neck_ay joint), that the velocities reported by /atlas/joint_states /atlas/joint_states are much higher than the velocity_limits defined in the URDF.
Can we expect this to be fixed for the VRC, or should we continue to assume that we can see velocity and/or effort values that exceed the URDF limits?
Copyright Askbot, 2010-2011. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
