xArm-Developer / xarm_ros

ROS packages for robotic products from UFACTORY
https://www.ufactory.cc/
BSD 3-Clause "New" or "Revised" License
196 stars 147 forks source link

Maximum acceleration . #226

Closed Akumar201 closed 2 months ago

Akumar201 commented 2 months ago

Hi, I would like to know what is the maximum safe acceleration er value for the xarm , I have seen somewhere that the maximum speed is default to 1000 mm/ seconds and 5000 mm/ sec^2 for acceleration. As sometimes maximum acceleration, joint velocity error pops up.

Maximum acceleration is not defined

"# request: command specification for motion executions.
# Units:
#   joint space/angles: radian.
#   Cartesian space: mm, mm/s, and mm/s^2.
#   time: sec

# pose: target coordinate. 
#   For Joint Space target,pose dimention is the number of joints. element as each target joint position.
#   For Cartesian target: pose dimention is 6 for (x, y, z, roll, pitch, yaw)

float32[] pose

# mvvelo: (value range: 0 ~ 1000) specified maximum velocity during execution. linear (0 to 1000 mm/s)  or angular (range 0~1000 for 0 to 3.14 rad/s) velocity.

float32 mvvelo

# mvacc: specified maximum linear acceleration (mm/s^2) during execution. (angular acceleration is fixed currently).

float32 mvacc

# mvtime: currently do not have any special meaning, please just give it 0. 
# PLEASE NOTE: after firmware version 1.5, For servo_cartesian motion, mvtime will be used as indicator of coordinate system. (0 for BASE coordinate, non-zero for TOOL coordinate)  

float32 mvtime

# mvradii: this is special for move_ineb service, meaning the blending radius between 2 straight path trajectories, 0 for no blend.

float32 mvradii

---

# response: 
#   ret is 0 for successful execution and others for errors or warnings occured
#   message is a string returned by function, indicating execution status.

int16 ret

string message
penglongxiang commented 2 months ago

Hi, there is no general maximum safe acceleration we can provide, since it depends highly on the specific command path in your application. Sometimes the joint over-speed error is due to the singularity in the path. If there is potential singularities in your Cartesian path, you may consider lower the max speed first.