We are currently experiencing some issues with our robot, such as:
Joint critical errors (C306A0:6)
System freezing (System was freeze without any messages)
After consulting with the Universal Robots local branch, one possible cause suggested was the size of the log_history.txt file, which may be affecting the robot’s health.
I would like to ask for your guidance on the following points:
1. Impact of log_history.txt Size on Robot Health
Questions:
Can an increased size of the log_history.txt file affect the robot’s health?
If so, what criteria determine when the file size becomes problematic? (e.g., exceeding a specific size threshold in megabytes).
2. Recommended Actions for Integrators
Questions:
If the robot’s health is compromised due to the increased size of the log_history.txt file, what steps should an integrator take to resolve this issue?
Could you provide specific examples, such as logging into the robot via SSH and deleting old logs?
Your guidance on these questions will be greatly appreciated and will help us take appropriate and timely measures to address the issue.
Thank you for your assistance.
Information
Robot model : UR3e
System Version : 5.19.0
You are aware that the forum consists of end-users and integratos, right? I believe your questions should be forwarded directly to UR themselves.
I have been providing support for the UR robots as a distributor/integrator for many years now, and I have never heard of this issue before.
But I would definitely be interested in hearing more about it, if it actually does prove to be an issue. Though, if it is an issue, it should probably be reported as a bug and mitigated in a future update.
Thank you for your quick response and for pointing that out. I truly appreciate your insight and your years of experience with UR robots.
I also found it unusual that this kind of issue has not been reported before, and I agree with your perspective on this. Your input reassures me that this might not be a common or widespread problem.
If this issue develops further or new findings arise, I will make sure to share the information here for the benefit of the community.
Thank you again for your prompt guidance and support!
I had similar issue on a UR10e with a camera that was sending too many messages to the log and the teach pendant froze. UR told us to remove all the messages sending to the teach and to disable the the message ,alarm and error button in the log interface on the teach.
It solved the freezing problem.
(For us when the teach was freezing, we could connect a mouse and keyboard to reboot the robot without pressing the power button)
For the joint critical errors, I don’t think that it comes from the same problem. Did you check your robot with the soft 'Ur Log Viewer" while its running to have some data of the motors ?
Thank you very much for your detailed response and for sharing your experience with a similar issue.
From your explanation, I understand that a large volume of logs could overwhelm the GUI, causing delays in rendering. It’s interesting that you could use a mouse and keyboard, which suggests that there may have been an issue specifically with the touch panel input.
In my case, during the freeze, the screen was still displayed, but the touch panel, power button, and even emergency stop switch were all unresponsive, and the +24V output was down. This might indicate that my situation involves a different phenomenon.
I am currently generating support file and, thanks to your advice, I remembered to use the Log Viewer to analyze the data. Upon examining the logs from the session where the freeze occurred, I discovered a large number of “Developer Messages” recorded. Specifically, the errors ‘C306A6’ and ‘C306A8’ appeared frequently, indicating that something abnormal is certainly occurring (please see the attached file).
While I do not fully understand the structure of the support files, I recognize that they are composed of multiple layers of zip files. For example:
robot_configurationYYYYMMDD_HH_mm_SS\files\log_history.txt is approximately 30MB when extracted.
robot_configurationYYYYMMDD_HH_mm_SS\files\log_history.bak is also approximately 30MB when extracted.
Thank you again for your guidance, which has helped me uncover these details. Your input has been very valuable in further understanding the issue.
I believe your questions should be forwarded directly to UR themselves.