-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The robot do jerky sound. #9
Comments
Hi, Which robot are you using? I noticed this behavior, too, with our Franka Panda in joint position control mode. What seemed strange to me was that even when I commanded the current joint position If you would like to investigate this issue further, I suggest doing two things:
traj = []
def cb(robot_state: franky.RobotState, time_step: float, rel_time: float, abs_time: float, control_signal: franky.ControlSignal):
# This function will get called for every control update the robot does (1kHz).
# Time, current pos, desired pos, current vel, desired vel, desired acc, next commanded pos
traj.append((abs_time, robot_state.q, robot_state.dq, robot_state.dq, robot_state.dq_d, robot_state.ddq_d, control_signal.q))
m1.register_callback(cb)
robot.move(m1)
# Plot the trajectories, e.g. with matplotlib I am happy to help if you need any assistance with this. Best, |
I am currently also facing this problem using franky with libfranka 0.8.0. Furthermore i observe that the robot is stopping between the waypoints even when the whole JointWaypointMotion object is passed into the move() method. Is this the expected motion when using waypoints? My goal is to drive a fluent trajectory. |
Hi, Stopping at the waypoints is expected. Unfortunately, the free version of the ruckig motion planning software does not support automatically calculating optimal velocities for intermediate waypoints. Hence, those have to be set manually and default to 0. What you can do is set the target velocity of the intermediate waypoints to a value different from 0, as shown in the Readme (motion m3). You could calculate those waypoint velocities with a spline interpolation, e.g., using scipy. Regarding the jerky sound, I remember spending some time investigating it. Strangely, the robot does this even when it is commanded just to hold its current position, and it only does it in the first motion of a sequence of waypoints. I assume it is somehow related to the robot switching to the joint controller. Best, |
Hi, @TimSchneider42. In the code snippet above for registering the callback, you mentioned:
I am trying to understand what is the control frequency used by the |
Hey, The time between waypoints is not static. The Ruckig motion planner will always compute a time-optimal trajectory between waypoints within the configured jerk, acceleration, and velocity limits. Best, |
Got it! Thanks for the quick reply. |
Issue: The franka emika robot doing jerky sounds.
when the robot is moving from one waypoint to other way point.
Observations:- 5 different robots in my lab do same sounds.(probably not a hardware issue)
what code?:- The default code of moving from m1 to m2.
What language:- python sample code
Whole code.
The text was updated successfully, but these errors were encountered: