penglongxiang

Hi, 1000mm/s limit is for Cartesian Planning speed limit (Linear, Circular, etc). For Joint space motion, this Cartesian speed limit is not applicable, there is chance that actual TCP speed...

Hi @WWimshurst, wait=False is only effective for Straight Line and joint space motions. For your case, you can try the API `set_cartesian_velo_continuous(on_off)`, refer [here](https://github.com/xArm-Developer/xArm-Python-SDK/blob/0fd107977ee9e66b6841ea9108583398a01f227b/xarm/wrapper/xarm_api.py#L3550), If argument `on_off` is set as...

Hi, unfortunately there is no such API available for now. The estimation of TCP force may be available in later versions by reporting through a new port. However as the...

C19 is the communication error between robot end module and the vacuum gripper, it has nothing to do with the robot position. Could you please cutoff the robot power by...

Hi, would you please reproduce this issue on your side and immediately download the log for us to diagnose? Thanks. Log compression file can be sent to [email protected]

Hi @joshuafishman, is there a background thread in your application that is constantly acquiring status like robot state, error code, TCP pose in a high frequency (up to 200Hz)? Maybe...

> Hi @penglongxiang, that's very interesting. Is the Automatic Status Report exposed through the SDK, or should we read from the port and parse the stream directly ourselves? @joshuafishman you...

Hi, in order for us to reproduce the exact issue you are encountering, please kindly provide a small piece of code that will trigger the error, and your log files...