Website internal page banner

Robot Alarm Codes 5064-5082 Repair

During the operation of the OTC DAIHEN Welding Robot, if the system experiences abnormalities such as missing weaving condition file, lost connection with feed control device, cooling water pump exception, multiple device program conflict, or insufficient resources, the teach pendant will usually display a hardware and control-level alarm in the 5064 to 5082 range. If these faults are not investigated promptly, they may cause serious operational safety hazards or damage to core components such as the reducer.

To help on-site engineers and mechanics quickly locate problems, we have organized the diagnostic terminology from the official maintenance manual to provide you with the following intuitive fault quick reference table. We recommend using the search function, entering the error code (e.g., 5064), to accurately obtain troubleshooting and processing suggestions.

I. OTC Robot Alarm Code Real-Time Quick Reference Table (5064-5082)

Alarm Code Fault Phenomenon Fault Cause Analysis Countermeasures & Solutions
5064 Weaving Condition File Does Not Exist The weaving condition file specified by the weaving function in the program does not exist. Enter file management to create the corresponding weaving condition file, or edit the job program, and then perform an exception reset.
5065 Power of Feed Control Device Not Turned On During the system self-test, it was found that the communication with the external feed control device was not established or interrupted. Turn on the power switch of the feed control device; if it is already turned on, check the device communication connection line, and perform an exception reset.
5066 Pump Exception Occurred in Welding Power Source When using a water-cooled welding torch, the water circuit sensor detects that there is not enough cooling water flowing. Refer to the welding power source manual (pump error section), eliminate the water pump fault or water circuit blockage, and perform an exception reset.
5067 Arc Retry Condition File Does Not Exist The arc retry condition file specified by the arc welding function in the program does not exist. Enter the system to create an arc retry condition file, or edit the job program to delete this call, and perform an exception reset.
5068 Arc Robot Condition File Does Not Exist The arc robot condition file specified by the arc welding function in the program does not exist. Enter the system to create a robot condition file, or edit the job program, and then perform an exception reset.
5069 Robot Movement Condition File Does Not Exist The robot movement condition file specified by the arc welding function in the program does not exist. Enter the system to create a robot movement condition file, or edit the job program, and then perform an exception reset.
5070 Welding RS Status File Does Not Exist The dedicated welding RS status file specified by the advanced welding function is not created. Enter the system to create a new RS status file, or edit the executing task program, and then perform an exception reset.
5080 Unable to Ensure Information Resources at Startup When the main control system allocates task resources, the waiting time to ensure information resources has timed out. Modify the robot’s startup process and the execution sequence of the branch command outside the component, and press the exception release key.
5081 Cannot Edit/Regenerate the Specified Program There is a program with the same number in the system (e.g., caused by external import), resulting in an execution conflict. Use the system file operation menu to delete or rename the duplicated and conflicting program, and then perform an exception reset.
5082 Cannot Execute Operations or Commands for Multiple Devices The option for multi-mechanism is not set and enabled in the constant parameters of the control system. Enter the system underlying parameter menu, correctly check and set the multi-mechanism option, and then press the exception release key.

II. Get Professional Technical Support and Maintenance Services

When the robot frequently displays the above hardware-level alarms, and routine reset attempts are ineffective, do not forcefully pull the robot arm or repeatedly force restarts, so as not to cause secondary irreversible damage.

Contact Anhui Oujie for Technical Guidance

Scroll to Top