-
Notifications
You must be signed in to change notification settings - Fork 112
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
xArm Lite 6 motor temperature overheating #106
Comments
Hi, Did you install any end-effectors? What is the TCP payload? Actually, our software will detect the temperature in real-time and report an error when the motor temperature is out of limit, don't worry. And our firmware provides a motor protection algorithm, it will cut off the power of the motor to protect the motor if any Abnormal. |
Hi, Great that there are several layers of motor protection. The error code is: What are the software temperature limits per axis for the xArm 6 Lite? Thanks for the reply |
Following my message from above: After moving the robot permanently for 4h, the code lines below just printed the highest temperature of all 6 servos being 86°C. And I can still open your software and move the joints. Should it be like that? temperatures=arm.temperatures |
Hi , The temperature threshold is 90° in our software. BTW, please reduce the actual payload, the load of Lite6 is about 600g for long-term work. |
Thanks! It's a dynamic payload, and the maximum is a bit under 1kg; the average is around 600g. Is there a way to set a customized lower temperature threshold? |
Hello,
The motors of the xArm Lite 6 tend to overheat when permanently in motion for more than 4 hours. I am curious to hear about possible strategies to reduce overheating and of integrating a custom motion stop whenever a custom temperature threshold (under the error limit) is reached.
As in my previous issue, I am using the xArm 6 Lite with a customized version of the 2006-joint_online_trajectory_planning.py common example.
I tried to call & check the motor temperatures with "arm.temperatures()" in the same thread in which I am sending the motion commands, but this caused a significant lack in the motion command reactivity.
The text was updated successfully, but these errors were encountered: