Skip to main content

Error Code

ForceControl

CodeError MessageCauseSolution
41410The actual observed force exceeds the allowed limit for this motionThe observed force (Fx、Fy、Fz) in the Cartesian space exceeds the limitCheck the configuration and torque sensor status, modify the program to decrease the total external force acting on the robot
41411The actual observed torque exceeds the allowed limit for this motionThe observed torque (Mx、My、Mz) in the Cartesian space exceeds the limitCheck the configuration and torque sensor status, modify the program to decrease the total external force acting on the robot
41412The position exceeds the allowed limit for this motionThe position in the JOINT space exceeds the limitChange current position a few increments to allowed area
41413The position exceeds the allowed limit for this motionThe position in the Cartesian space exceeds the limitChange current position a few increments to allowed area
41414The linear velocity exceeds the internal limit for this motionYou cannot proceed without removing the causes of this errorReduce speed, use fine point, increase AccSet, avoid singularity, inc. dynamic resolution
41415The angular velocity exceeds the internal limit for this motionYou cannot proceed without removing the causes of this errorReduce speed, use fine point, increase AccSet, avoid singularity, inc. dynamic resolution
41416Too close to singularity with respect to numerical resolutionThe destination or current position is too close to singularityChange destination position a few increments. During jogging, use axis by axis. During program execution, use MoveAbsJ
41417The current joint position exceeds the limit,movement can cause damageNo operation will be possible until after correcting the fault.Verify that the joint position is within allowed region
41418The total torque command exceeds the limitThe default force supervision has triggered because the programmed or measured external forces are larger than the safety limit for the robot typeCheck the configuration and modify the program to decrease the total external force acting on the robot
41419Failed to initialize the force controlThe TCP length exceeds limitation, or the current reference coordinate system is NOT validReview the limits for the tool and detailed definitions in the Product manual
41420Force control activation failedSee details below1.Check whether the current Tool settings match the actual configuration and if the set tool mass and center of mass are reasonable; 2. Check the monitoring window to verify the robot's coordinate system and posture are consistent with reality; 3. Confirm the current robot model and RD parameters are correct; 4. Try returning to the mechanical zero position, clear the sensor, and then attempt dragging; 6. Ensure no external force is applied to the robot when enabling dragging; 7. For other details, refer to the 《Dragging Fault Troubleshooting Manual》
41421Failed to pause the force controlThe robot force control is NOT executedCommand execute only after starting FC
41422Failed to restart the force controlThe robot force control is not pausedPause or Stop the FC before restarting the force control tasks
41423Failed to set the sensor usage methodThe force control is uninitializedCheck the configuration and initialize the FC
41424Failed to calibrate torque sensorThe dynamic compensation is executed, and a manual calibration is NOT allowedTo use the manual calibration, please change the sensor usage mode to calibration
41425Failed to set the sine overlayThe overlay is paused in the non-impedance control mode, or the command is NOT allowed when the program is executingEnsure that it is in the impedance control mode and that the overlay is stopped
41426Failed to set the Lissajous overlayThe overlay is paused in the non-impedance control mode, or the command is NOT allowed when the program is executingEnsure that it is in the impedance control mode and that the overlay is stopped
41427Failed to start the overlayThe overlay is not set, or it is not in the Cartesian impedance control modeCheck control mode command and set the overlay parameters before restarting.
41428Failed to pause the overlayThe overlay is not started, or it is not in the Cartesian impedance control modePlease ensure that the overlay is started and it is in the Cartesian impedance control mode
41429Failed to restart the overlayThe overlay is not paused, or it is not in the Cartesian impedance control modePause the current FC mission and check control mode command. Switch to cartesian impedance control before restarting.
41430Failed to set the impedance control typeThe impedance control mode is uninitializedStop the current FC mission and initialize control parameter again
41431Failed to initialize the joint impedance controlNot in the joint impedance control mode; the initialization command is not executedExecute the Joint impedance control mode before restarting FC
41432Failed to initialize the Cartesian impedance controlNot in the Cartesian impedance control mode; the initialization command is not executedExecute the Cartesian impedance control mode before restarting FC
41433Failed to set the null-space impedanceIt is not in the Cartesian impedance control mode, or the impedance is uninitializedCheck the control mode and try again. Do not restart system until a valid force calibration or cartesian impedance mode is made.
41434Failed to set the desired force in the joint spaceIt is not in the joint impedance control mode, or the impedance is uninitializedCheck the control mode and try again. Do not restart system until a valid force calibration or joint impedance mode is made.
41435Failed to set the desired force in the Cartesian spaceIt is not in the Cartesian impedance control mode, or the impedance is uninitializedCheck the control mode and try again. Do not restart system until a valid force calibration or cartesian impedance mode is made.
41436Failed to switch the mode of the impedance moduleCannot switch impedance mode when in FC Execution stateStop the current FC mission and initialize control parameter
41437The robot flange is beyond the virtual wall, and the virtual wall cannot be activatedThe robot flange is beyond the virtual wall, which does not meet the virtual wall constraintsPlease move the robot flange into the virtual wall range and then activate the virtual wall
41438The robot is not in the drag mode and the virtual wall cannot be activatedThe virtual wall can be activated only in the drag modeReactivate the virtual wall after the drag mode is enabled
41439The current state of the robot does not support the virtual wall function, and the virtual wall cannot be activatedThe current state of the robot does not support the virtual wall function
41442When the impedance mode is enabled, the robot does not meet the joint position limitation requirement; the impedance mode cannot be enabledWhen the impedance mode is enabled, the robot does not meet the joint position limitation requirement; the impedance mode cannot be enabledPlease ensure that the robot is within the joint position limitation when the impedance mode is enabled for the robot
41446Identification Exception, result will be replaced by default standardsException occurs during Identification, some results will be replaced by default standardsResults will be replaced by default standards, please follow up hardware qualification
41447Failed to dragThere is a large deviation between the feedback and the model torque, and the drag can not be activated1. Check whether the current Tool setting is consistent with the actual situation and whether the set tool mass center is reasonable; 2. Check the monitoring window to see whether the robot coordinate system and pose consistent with the actual situation; 3. Confirm that the current robot model and RD parameters are consistent with the actual parameters; 4. Try to return to the mechanical zero and zero the sensors before dragging; 5. For more detail, refer to the Drag Fault Troubleshooting Manual
41448Failed to initialize the force controlFcinit is not allowed to be powered off during force controlClick pptomain and run again
41449Failed to initialize the force controlFc Commands from last time are not finished, new command will be refused.Calling Fc Commands too quickly, please increase the time interval between FcStop and FcInit for next time.
41450Failed to dragThe voltage of the sensor is abnormal,and the drag can not be activated.Please check the status of sensors.
41451Force control mode triggered protection, controller powered offSee details
41454ForceControl Stopped When PowerOff,Back To Position Control Mode
41455In Force Control,Dont Check Path Deviation
41456Resume in Postion Control Mode
41458The time setting cannot be negative or greater than 600Please check the time format
41459In force control mode, unsupported instruction
41460The virtual wall area setting is too small
41461TCP length is too large(norm<=0.15m),the ref point of force control will be setted at flange
41462Calibrate Sensor failed,please check the load settingThe bias between dynamics model trq and sensor measured is too largePlease check the load setting
41463Dragging is prohibited in handheld workpiece mode
41464Failed to drag,the joint position limitation setting is error,there is a risk of dragging out the joint position limitationThe range of the joint position limitation is to small to open drag modeCheck the joint position limitation, make sure the the range of the soft limit is beyond 25°
41465Sensor torque differs too much from theoretical torque, calibration failedPlease check load settings
41472SetFcJointVelMax execution failed.Command parameter is invalidPlease check parameter settings and correct SetFcJointVeLMax parameters
41473SetFcCartVeLMax execution failed .Command parameter is invalidPlease check the command parameter settings and correct the SetFcCartVeLMax parameters
41474SetFcJointMomentumMax execution failed.Command parameter is invalidPlease check the command parameter settings and correct the SetFcJointMomentumMax parameters
41475SetFcJointEnergyMax execution failed.Command parameter is invalidPlease check the command parameter settings and correct the SetFcJointEnergyMax parameters
41476Program execution has been denied due to the activation of force control protectionForce control protection has been triggeredPlease re-run the program from pptomain
41477In the command parameters, the lower limit exceeds the upper limit.The command parameters are invalid.Please check the command parameter settings and correct the parameters.
41478Before starting the identification, the robot is not at the mechanical zero pointBefore starting the identificationPlease manually jog to the mechanical zero point and then start the identification
42001Admittance motion exceeds safe range.Exceeds safe range1. Please check the safety range parameters. 2. Please check if the admittance control parameters are reasonable.
42002当前机器人距离负载辨识初始点位较远当前机器人距离负载辨识初始点位较远请点击运动至到辨识初始点位

HardWare

CodeError MessageCauseSolution
31001Configuration Parameter Error of EtherCAT MasterMismatched EtherCAT configuration filesRe-import the configuration files, and restart the control system
31002Failed to read the EtherCAT authorization file correctly, please checkThe authorization file does not exist or the read and write permissions are incorrectRe-import the authorization file
31003Failed to authorize EtherCAT. Please check whether the authorization code is correct. The robot can only operate for one hour without authorizationEtherCAT not AuthorizedPlease check the EtherCAT authorization code and try to reauthorize it on the EtherCAT authorization interface. After the authorization is successful, restart the robot to take effect
31004Failed to configure the EtherCAT master. Please check whether the configuration files matchThe master configuration fails due to mismatched EtherCAT configuration filesRe-import the configuration files, and restart the control system
31005EtherCAT fails to configure DC. Please check whether the configuration files matchThe configuration fails due to mismatched EtherCAT configuration filesRe-import the configuration files, and restart the control system
31006EtherCAT fails to configure DCM. Please check whether the configuration files matchThe configuration fails due to mismatched EtherCAT configuration filesRe-import the configuration files, and restart the control system
31007Failed to scan the bus. Please check whether the configuration files matchThe configuration fails due to mismatched EtherCAT configuration filesRe-import the configuration files, and restart the control system
31008The controller fails to start as a result of the number of configured slaves does not match that of scanned slaves ()1. The configuration fails due to inconsistency between the EtherCAT configuration and the actual network topology; 2. Hardware failure in the EtherCAT network from the slave equipment1. Re-import the configuration files, and restart the control system; 2. Contact the manufacturer's technical support
31009Failed to enable the EtherCAT bus, EtherCAT status of each slave stationDue to errors in EtherCAT bus startup process, some slaves cannot switch to OP mode correctly, resulting in bus failureTry to restart the control system; contact the manufacturer's technical support
31010Initialization of internal axis servo drive failed, with the axis No. of []The drive malfunctions internallyCheck whether the servo drives are disconnected from each other
31011Failed to initialize IO slave, please check the hardware connection1. The IPC and general IO modules are disconnected from each other; 2. General IO modules and safety IO modules are disconnected from each otherRestart the control system after reconfiguring the IO signal according to the failure reason
31012Tailboard Slave Initialization FailureThe IPC and the general tailboard slave module is disconnected from each other, or the tailboard slave hardware failsCheck the hardware connection, or replace the tailboard slave hardware
31013Failed to initiate the safety board slaveThe IPC and the safety board slave modules are disconnected from each otherCheck hardware connections
31014Abnormal Communication with Slave Devices1. The communication between IPC and slave module is interrupted; 2. The slave device malfunctions1. Confirm whether the EtherCAT debug cable is unplugged from the robot side; 2. Check the hardware connections and restart the control system; 3. Please contact the technical support
31015Servo alarm occurs, and the error code reported by servo isThe servo drive sends an alarm, and the specific reason for the alarm needs to find the corresponding drive manual according to the error code reported by the servo1. Find the corresponding drive manual according to the error code, and handle it according to the manual guidance; 2. Contact the technical support
31017Ethercat is not Authorized, and the Trial Period EndsEthercat is not authorized and can only be used for one hourPlease contact the technical support to ask for the Ethercat authorization code and authorize on the EtherCAT authorization interface. After the authorization is successful, restart the robot to take effect
31018Abnormal connection between slave device () and controller1. The cable between the slave device and the controller malfunctions; 2. The slave malfunctions1. Please check whether the cables between the slave devices fail; 2. Please contact the technical support
31019Failed to Initialize the CClink Gateway SlaveThe hardware connection is abnormal or the hardware malfunctionsCheck hardware connections
31020The Ethercat IO slave module that has not been adapted is usedThe Ethercat IO slave module that has not been adapted is used, therefore the controller has no information about the current IO slave. Users need to ensure that the IO module is configured and used correctlySince the PDO setting of the IO module that has not been adapted is unknown, there is a certain risk in direct use. Please use it with caution. Generally, digital IO modules with less than 64 channels can be used directly; however, the analog IO module is not recommended to be used directly because the controller is unknown to its analog quantity type, range and accuracy parameters, and the PDO settings of various equipment manufacturers may also be different. Please contact the technical support for adaptation before using it
31021Safety Board Slave Initialization FailureThe safety board firmware version configured by the eni file is inconsistent with the actual firmware versionCheck whether the safety board firmware version of the eni file is consistent with the actual firmware version
31022Tailboard slave Input Current Signal OverloadWhen the tailboard slave channel AI is set to current mode, make sure that the actual input is current and does not exceed the limit parameter, otherwise the hardware may be damagedPlease disconnect the input signal of the corresponding channel and enter the xpanel configuration interface to set as Voltage Mode
31024xPanel terminal slave station hardware test failed,test error code()xPanel terminal slave station hardware test process is incorrect,hardware connection is incorrect or hardware is faultyPlease confirm the xPanel test process is correct. If the fault persists,contact R&D for troubleshooting
31025Safety Board Type Configuration ErrorThe safety board type of the configuration is inconsistent with the actual safety board typeCheck whether the safety board type of the configuration is inconsistent with the actual safety board type
31026Initialization of internal axis servo drive failed, the server drive version in the ENI file of the master configuration is inconsistent with the server drive configuration scanned, with the axis No. of []The server drive version in the ENI file of the master configuration is inconsistent with the server drive configuration scannedReplace the main site ENI file to confirm that the correct ENI file is used.
31027Unable to read the master station ENI file correctly. Please check the master station ENI file.The master ENI file was not found in the systemRe upgrade the ENI file corresponding to the current model
31028EtherCAT failed to scan the bus, and the scan slave information does not match the slave information in the configuration ENI fileThe configuration of slave information or topology in the ENI file of the master station is inconsistent with the scanned EtherCAT slave stationReplace and upgrade the correct ENI file
31029EtherCAT scan bus failed with cross wiring from the slave stationEtherCAT slave station wiring errorPlease check whether the wiring of EtherCAT slave station is correct
31030Initialization of external axis servo drive failed, with the axis No. of []1. An unconnected external axis, such as a guide rail, was mistakenly opened 2.The drive malfunctions internallyAccording to the cause of the error, close the external axis that was opened incorrectly or check if the connection with the external axis is interrupted
31031Initialization of external axis servo drive failed, the server drive version in the ENI file of the master configuration is inconsistent with the server drive configuration scanned, with the axis No. of []The server drive version in the ENI file of the master configuration is inconsistent with the server drive configuration scannedReplace the main site ENI file to confirm that the correct ENI file is used.
31032The ESI file and controller version of the safety board RSC do not matchThe controller version is 3.0, and the ESI file of the safety board RSC does not match the controller version. Some of RSC's safety functions will not function properly.We need to upgrade the ESI file of the RSC security board and the ENI file of the main control
31033The firmware version of the safety board (RSC) does not support the current model.The firmware version of the safety board (RSC) does not support the current model. Please upgrade the RSC firmware versionUpgrade the RSC firmware version
32001Power-on failed. Specific reasonServo faults, STO circuit open, power-on aborted, etc.1. Confirm operation procedure; 2. Check servo status; 3. Clear servo alarms before power-on retry
32002Power-on Failed, STO not Connected
32003The communication thread between master and slave device is blocked, and the communication with slave device is abnormalThe communication between the controller and the slave device is abnormal due to software reasons1. Soft restart of controller; 2. Contact the technical support
32004EtherCAT Thread Blocked, Scheduling TimeoutInternal system errorRestart control system
32005The EtherCAT Thread was Blocked and Timed Out over 5000 Times in a RowInternal system errorRestart control system
32006The position command to be sent to the servo has a big jump and the position command is rejectedThe position command to be sent to the servo has a big jump, and the generated speed exceeds the maximum speed of the motor, which may cause danger. To be safe, perform the power-off operationRe-power on to operate
32007Ethercat Thread Event Execution TimeoutInternal alarmInternal state record, which can be ignored
32008Error while writing Servo ZeroOnly support CR joints, confirm whether it is a CR robot and whether the firmware is correct
32010Axis () Encoder Battery Voltage Low WarningEncoder Battery Voltage InsufficientPlease replace encoder battery in time
35001Axis ()Short circuit of the driveOutput to output, output to ground, internal PWM bridge errorTroubleshoot circuit problems and eliminate short circuit
35002Axis ()Over-temperature of the driveThe internal temperature of the drive reaches the set valueReduce the drive temperature below the set value
35003Axis ()Over-voltage of the driveThe bus voltage exceeds specified voltage limitThe bus voltage is restored within the specified voltage range
35004Axis ()Under-voltage of the driveThe bus voltage is below the specified voltageThe bus voltage is restored within the specified voltage range
35005Axis ()Over-temperature of the motorThe motor over-temperature switch shows the over-temperature errorRestore the temperature switch to normal state
35006Axis ()Error of the encoder feedback1. 5V output inside the drive is over-current; 2. The resolver or analog encoder is not wired; 3. The level exceeds the error range; 4. The incremental encoder differential signal is not wired1. The encoder power supply is restored to the specified voltage range; 2. The feedback signal is restored to the specified level range; 3. The differential signal is connected well
35007Axis ()Error of the drive phaseThe phase angle based on the encoder fails to match with the switch state of the HALL. This error occurs only when the brushless motor is configured to be sinusoidal. This error does not occur during the resolver feedback or when the HALL correction function is stopped.The phase angle based on the encoder is consistent with the switching state of the HALL
35008Axis () Drive reached the current limitMotor overload or abnormal circuit1. Check whether the motor is overloaded; 2. Check the circuit; 3. Contact the technical support
35009Axis () Drive reached the voltage limit1. The set speed is too high; 2. The motor is abnormal1. Check whether the set speed is abnormal; 2. Check whether the motor is abnormal; 3. Contact the technical support
35010Axis ()Power-on of the drive at positive limitThe drive is over positive limitRestore the drive limit
35011Axis ()Power-on of the drive at negative limitThe drive is over negative limitRestore the drive limit
35012Axis () Drive following error out of toleranceBeyond the following error set by the userCheck whether the upper instruction fails and check the robot state
35013Axis () Position counter in placeInternal error of driveTry to restart. If the problem is not solved, please contact the technical support
35014Axis () Suitable for fault without other emergenciesInternal error of driveTry to restart. If the problem is not solved, please contact the technical support
35015Axis () Node errorInternal error of driveTry to restart. If the problem is not solved, please contact the technical support
35016Command Error of Drive1. This error is not accurate and can be ignored; 2. There is no PWM or other command signalsRecover to input signal
35100Axis ()Under-voltage of the drive DC bus (0x3220)The servo detects that the bus voltage is less than the set under-voltage protection threshold in real time possibly due to insufficient bus supply voltage1. Check whether the power supply voltage of the robot is normal; 2. Check whether the drive capacitance is normal; 3. Replace the servo drive
35101Axis ()Over-voltage of the drive DC bus (0x3210)The servo detects that the bus voltage is higher than the set over-voltage protection threshold in real time, possibly because: 1. The bus power supply voltage is too high; 2. The robot decelerates too quickly; 3. The handling of base power supply is abnormal1. Check the power supply voltage of the robot; 2. Check the deceleration of the robot; 3. Check the robot power management loop
35102Axis ()Over-current of the drive (0xFF80)The amplitude of servo real-time detection current vector is larger than the set safety protection threshold, possibly because the current is raised up due to the sudden stop of the motor during operation1. Check whether the three-phase line and 48V power line of the motor are connected correctly; 2. Check whether the motor deflection angle is correct
35103Axis ()Over-load of the drive (0xFF81)The joint motor continuously exceeds the rated torque protection threshold range, possibly because of the servo closed-loop control. If the actual position of the motor cannot track the given position, the torque current will be too large, and the error will be reported when the duration reaches a certain degree1. Check whether the three-phase line and band-type brake cable of the motor are connected correctly; 2. Check whether the motor deflection angle is correct
35104Axis () Drive motor magnetic over limit (0xFF82)Determine whether the excitation current amplitude is less than the set value, otherwise, an error will be reported. For field weakening control, it is necessary to change the excitation current to reach a higher speed. At present, the bus voltage of the motor adapted by low-voltage servo is enough, without requiring field weakening, so this error report has been blockedUpdate the servo drive to the latest firmware version and update the servo drive to the latest parameter version
35105Axis ()Stall alarm of the drive (0xFF90)If the joint speed tracking error is greater than the set threshold and lasts for more than 1s, an error will be reported. Stall is reported in the start-up stage, and the motor needs to find the deflection angle again for normal operation. When stall is reported during motor operation, it is necessary to check hardware configuration, software version and parameters1. Check whether the three-phase line and band-type brake cable of the motor are connected correctly; 2. Check whether the motor deflection angle is correct; 3. Check the hardware configuration; 4. Check the servo software version
35106Axis ()Out of tolerance of the drive position (0x8611)The joint position tracking error exceeds the set threshold, so it is necessary to check whether the hardware and software are configured correctly with suitable version1. Check whether the wiring harness is connected correctly; 2. Check whether the joint encoder is normal; 3. Replace joint hardware, motor, reducer and drive; 4. Confirm whether the instructions issued by the master station are reasonable
35107Axis () Drive zero current alarm (0xFFA0)The zero current value needs to exceed the set threshold, and the current is abnormal when it is not enabledUpdate the servo drive to the latest firmware version, update the servo drive to the latest parameter version and replace the servo drive
35108Axis ()Phase A over-current of the drive (0x2310)1. The phase A current of the motor exceeds the sampling range of the drive current; 2. The locked rotor for motor; 3. The load is too large or the speed is too fast; 4. The resistance of joint mechanism is large1. First check whether the harness is connected correctly; 2. Check whether the motor deflection angle is correct; 3. Check whether the band-type brake is opened correctly when enabling; 4. When the load is too much, reduce the speed and check whether the fault disappears; 5. Observe whether the fault joint during operation makes abnormal noise due to excessive resistance
35109Axis ()Phase B over-current of the drive (0x2311)1. The phase B current of the motor exceeds the sampling range of the drive current; 2. The locked rotor for motor; 3. The load is too much or the speed is too fast; 4. The resistance of joint mechanism is high1. First check whether the harness is connected correctly; 2. Check whether the motor deflection angle is correct; 3. Check whether the band-type brake is opened correctly when enabling; 4. When the load is too much, reduce the speed and check whether the fault disappears; 5. Observe whether the fault joint during operation makes abnormal noise due to excessive resistance
35110Axis ()Phase C over-current of the drive (0x2312)1. The phase C current of the motor exceeds the sampling range of the drive current; 2. The locked rotor for motor; 3. The load is too much or the speed is too fast; 4. The resistance of joint mechanism is high1. First check whether the harness is connected correctly; 2. Check whether the motor deflection angle is correct; 3. Check whether the band-type brake is opened correctly when enabling; 4. When the load is too much, reduce the speed and check whether the fault disappears; 5. Observe whether the fault joint during operation makes abnormal noise due to excessive resistance
35111Axis ()IGBT over-current of the drive (0xFFA1)1. The motor current exceeds the set threshold; 2. The locked rotor for motor; 3. The load is too much or the speed is too fast; 4. The resistance of joint mechanism is high1. First check whether the harness is connected correctly; 2. Check whether the motor deflection angle is correct; 3. Check whether the band-type brake is opened correctly when enabling; 4. When the load is too much, reduce the speed and check whether the fault disappears; 5. Observe whether the fault joint during operation makes abnormal noise due to excessive resistance
35112Axis ()Object overflow of the drive (0xFF01)
35113Axis ()Image overflow of the drive (0xFF02)
35114Axis ()Thread H timeout of the drive (0xFF03)
35115Axis ()Thread M timeout of the drive (0xFF04)The servo software scheduling is abnormal, and the program has not been completed within the specified time, possibly because the firmware version or parameter version is not the latest oneUpdate the servo drive to the latest firmware version, update the servo drive to the latest parameter version and replace the servo drive
35116Axis ()Thread L timeout of the drive (0xFF05)
35117Axis ()Thread C timeout of the drive (0xFF06)
35118Axis ()Interrupt and crash of the drive (0xFF07)The servo software scheduling is abnormal, and the program has not been completed within the specified time, possibly because the firmware version or parameter version is not the latest oneUpdate the servo drive to the latest firmware version, update the servo drive to the latest parameter version and replace the servo drive
35119Axis ()Main task crash of the drive (0xFF08)
35120Axis ()Illegal hardware of the drive (0xFF09)
35121Axis ()Timeout in debug version of the drive (0xFF0A)
35122Axis ()Object ID timeout of the drive (0xFF11)
35123Axis ()Thread ID error of the drive (0xFF12)
35124Axis ()PV variable ID error of the drive (0xFF13)
35125Axis ()VV variable ID error of the drive (0xFF14)
35126Axis ()VU variable ID error of the drive (0xFF15)
35127Axis ()Data type error of the drive (0xFF16)
35128Axis ()Existence of data object of the drive (0xFF17)
35129Axis ()Non existence of data queue of the drive (0xFF21)
35130Axis ()Full data queue of the drive (0xFF22)
35131Axis ()Empty data queue of the drive (0xFF23)
35132Axis ()Application version error of the drive (0xFF30)
35133Axis ()Parameter verification error of the drive (0xFF31)
35134Axis ()Parameter number error of the drive (0xFF32)
35135Axis ()PN parameter ID error of the drive (0xFF33)
35136Axis ()UN parameter ID error of the drive (0xFF34)
35137Axis ()FN parameter ID error of the drive (0xFF35)
35138Axis ()SPI communication error of the drive (0xFF40)The communication between DSP and parameter memory is abnormal, possibly due to the firmware version or the parameter version is not the latest one; or the servo drive hardware is abnormalUpdate the servo drive to the latest firmware version, update the servo drive to the latest parameter version and replace the servo drive
35139Axis ()E2P overflow of the drive (0xFF41)Too many parameters are read by the parameter memory, possibly due to the firmware version or the parameter version is not the latest one; or the servo drive hardware is abnormalUpdate the servo drive to the latest firmware version, update the servo drive to the latest parameter version and replace the servo drive
35140Axis ()Empty dynamic memory of the drive (0xFF50)Logic error occurs in the servo software operation, possibly due to the firmware version or the parameter version is not the latest oneUpdate the servo drive to the latest firmware version, update the servo drive to the latest parameter version and replace the servo drive
35141Axis ()Instruction code error of the drive (0xFF51)Logic error occurs in the servo software operation, possibly due to the firmware version or the parameter version is not the latest oneUpdate the servo drive to the latest firmware version, update the servo drive to the latest parameter version and replace the servo drive
35142Axis ()Instruction length error of the drive (0xFF52)Logic error occurs in the servo software operation, possibly due to the firmware version or the parameter version is not the latest oneUpdate the servo drive to the latest firmware version, update the servo drive to the latest parameter version and replace the servo drive
35143Axis ()Meter channel number error of the drive (0xFF53)
35144Axis ()OSCI channel number error of the drive (0xFF54)
35145Axis ()Static mode error of the drive (0xFF60)Error occurs in the servo operation mode, possibly due to the servo firmware and parameters are not the latest version; or the servo parameters are not successfully writtenUpdate the servo drive to the latest firmware version and replace the servo drive
35146Axis ()Dynamic mode error of the drive (0xFF61)Error occurs in the servo operation mode, possibly due to the servo firmware and parameters are not the latest version; or the servo parameters are not successfully writtenUpdate the servo drive to the latest firmware version and replace the servo drive
35147Axis ()Mode change error of the drive (0xFF62)Error occurs in the servo operation mode, possibly due to the servo firmware and parameters are not the latest version; or the servo parameters are not successfully writtenUpdate the servo drive to the latest firmware version and replace the servo drive
35148Axis ()IPM alarm of the drive (0xFF70)It is possibly because the servo firmware and parameters are not the latest versionUpdate the servo drive to the latest firmware version and replace the servo drive
35149Axis ()Module overheating alarm of the drive (0x4310)The joint temperature exceeds the temperature range for safe and reliable operationCarry out corresponding cooling treatment
35150Axis ()Disconnection of the STO switch of the drive (0x3181)The servo has been detecting the STO signal level, which is inconsistent with the setting logic, so an error is reported, possibly due to the robot enabling handle is not effective1. Press the manual enabling handle; 2. Re-plug the STO cable; 3. Replace the STO cable and the servo drive
35151Axis () Encoder error (0x7371)The QEP encoder reports an error and the ABZ cable is disconnected, possibly due to the servo has not been upgraded to the latest firmware and parameter versionUpdate the servo drive to the latest firmware version and update the servo drive to the latest parameter version
35152Axis () Encoder error (0x7372)
35153Axis () Encoder error (0x7373)
35154Axis () Encoder error (0x7374)
35155Axis () Encoder error (0x7375)
35156Axis () Encoder error (0x7376)
35157Axis () Encoder error (0x7377)
35158Axis () Encoder error (0x7378)Encoder chip reports an error: Biss2 communication abnormal1. Check the joint encoder cable; 2. Replace the encoder; 3. Replace the encoder cable; 4. Replace the servo drive
35159Axis ()Encoder error (0x7379)Encoder chip reports an error: Biss1 communication is abnormal, and the encoder decoding chip cannot be found1. Check the encoder cable at the joint motor side; 2. Replace the encoder; 3. Replace the encoder cable; 4. Replace the servo drive
35160Axis ()Encoder error (0x737A)1. CRC error of encoder communication; 2. Encoder communication is abnormal1. Re-plug the encoder cable; 2. Replace the encoder; 3. Replace the encoder cable; 4. Replace the servo drive
35161Axis ()Encoder error (0x737B)The encoder communication is abnormal: CRC verification of encoder passed, but encoder chip reported an error1. Re-plug the encoder cable; 2. Replace the encoder; 3. Replace the encoder cable; 4. Replace the servo drive
35162Axis ()Encoder error (0x737C)1. Single encoder hardware fault; 2. The encoder battery is exhausted.1. If a single encoder reports an error and cannot be recovered after restart, it is necessary to contact after-sale maintenance. 2. All axes report errors at the same time. Contact the after-sale maintenance to replace the encoder battery.
35163Axis ()TZ trigger (0xFF71)
35164Axis ()Internal error (0xFF91)
35165Axis ()The upper enabling current loop is set as 0 (0xFFA2)
35166Unable to Track the Master Station Position Command (0x8612)
35201Axis ()The power supply on the 5v secondary encoder has exceeded the preset current limit of the power supply provided by the drive. This fault disables the drive.CDHD can provide a maximum current of 250 mA to the secondary encoder. Check whether the encoder is short-circuited, and whether the encoder drawing exceeds the current limit
35202Axis () Over-current is detected from the drive output.1. Drive or motor fault; 2. The robot load exceeds the limit; 3. Send collision, etc.Check whether the motor connection is short-circuited and whether there is overshoot in the current circuit
35203Axis ()Motor is overloaded.1. Drive or motor fault; 2. The robot load exceeds the limit; 3. Send collision, etc.Check the specifications of the drive-motor. This fault may occur if the capacity (power) of the motor is too small.
35204Axis () Drive is overloaded.Check the specification of the drive-motor. This alarm may occur if the capacity (power) of the drive is too small. Check whether the commutation angle is correct (i.e., whether the rectification is balanced)
35205Axis ()The offset or compensation amount of the current sensor is out of range. This fault disables the drive.The drive malfunctionsRestart. If the fault still exists, the driver may need to be repaired. Please contact the technical support
35206Axis ()One of the motor phase is disconnected. The current command is greater than 100, but the motor current of one phase is actually 0, and continuously exceeds 160 of electrical angle.The drive malfunctionsCheck the wiring of the motor phase
35207Axis () Over-current is detected on a digital output. This fault disables the drive.The drive malfunctionsVerify the correct wiring of the digital output and ensure that the output circuit is not shorted.
35208Axis ()The bus voltage exceeds the maximum value. This fault disables the drive.Check whether regenerative resistance is required
35209Axis ()The bus voltage is lower than the minimum value. If the value of the variable UVMODE is 1 or 2, an under-voltage warning is issued when the drive is enabled.Check whether the main AC voltage power supply is connected to the drive and turned on. The under-voltage limit can be read by the UVTHRESH command
35210Axis ()The preset current limit of the regenerative current has been exceeded. This fault disables the drive.Increase the regenerative resistance
35211Axis ()When used as a drive, the STO signal is not connected. This fault disables the drive.Check whether the STO connector (P1) is correctly connected
35212Axis ()The circuit for measuring the bus voltage failed. The drive cannot be used at this time.Restart. If the fault still exists, the driver may need to be repaired. Please contact the technical support
35213Axis ()At least one of the main power supplies powered by the bus is not connected.Please check the wiring or contact the technical support
35214Axis ()The regenerative resistance of exceeds its permissible power. This fault disables the drive.Check whether regenerative resistance characteristics are suitable for this application
35215Axis ()The temperature inside the integrated power module exceeds the preset limit. This state makes the drive unusable.Check whether the ambient temperature exceeds the drive specification. Otherwise contact the technical support.
35216Axis ()The temperature of the control panel exceeds the preset limit. This state makes the drive unusable.Check whether the ambient temperature exceeds the drive specification. Otherwise contact the technical support.
35217Axis ()Temperature sensor fault. This state makes the drive unusable.Restart the power supply. If the problem persists, please contact the technical support
35218Axis ()The temperature of the power panel exceeds the preset limit. This state makes the drive unusable.Check whether the ambient temperature exceeds the drive specification. Otherwise contact the technical support.
35219Axis ()The motor is overheating or the motor temperature sensor is not set correctly. This fault disables the drive.Check whether the drive is properly configured (using THERMODE,THERMTYPE,THERMTHRESH and THERMTIME), and if necessary, check whether the motor temperature sensor is properly connected to the drive. If the drive is correctly configured and wired, check whether the motor specification is too small.
35220Axis () The internal power supply is out of range. This fault disables the drive.The drive may need to be repaired. Please contact the technical support
35221Axis ()5v is too low or the power is off. This fault disables the drive.It may happen during power failure. In other cases, please contact the technical support.
35222Axis ()Power panel EEPROM fault. The drive cannot be used at this time.Contact technical support.
35223Axis ()Control panel EEPROM fault. The drive cannot be used at this time.Contact technical support.
35224Axis ()CAN bus core voltage supply fault. This fault makes the driver unusable.The driver may need to be repaired, please contact the technical support.
35225Axis ()Self-test failed and the driver cannot be used at this time.Contact technical support.
35226Axis ()Parameter memory verification failed, possibly due to the save operation is not completed when the power is off.Reconfigure the drive, or download the parameter set and save the parameters. If the problem persists, please contact the technical support.
35227Axis ()Failed to write memory. There is an internal problem in accessing the flash memory. At this time, the drive cannot be used.Contact technical support.
35228Axis ()The target position command of one controller is rejected because it may cause the motor to exceed its speed limit. This fault disables the drive.Enable the drive and send a valid position command
35229Axis ()The drive needs configuration. Any determined parameters need to be configured after modification. The determined parameters still need to be configured after being transmitted to the driver, even if the parameters have not been changed.Execute CONFIG after setting drive parameters
35230Axis (): FPGA configuration failed. The code for the FPGA did not load. Drive cannot be enabled.Contact technical support.
35231Axis (): Motor Setup procedure failed. MOTORSETUPST will show the cause. This fault disables the drive.Check phase and motor wiring. Make sure the correct feedback type is selected. Check MOTORSETUPST for hints.
35232Axis (): Commutation initialization has failed. This fault occurs in systems that do not have commutation information (e.g., Hall signals) in the motor feedback device. This fault disables the drive.Check whether the motor feedback type and the phase-finding parameters are set correctly for the application.
35233Axis (): FPGA version does not match the hardware version. This fault disables the drive.Update either FPGA version or driver version.
35234Axis (): Input defined as Emergency Stop indicator has been activated. This fault disables the drive.Turn off the input.
35235Axis (): EtherCAT - the Microblaze version does not match the version specified by drive. This fault disables the drive.Make sure the correct version has been downloaded to the drive.
35236Axis (): EtherCAT - the ESI version does not match the version specified by drive. This fault disables the drive.Make sure the correct version has been downloaded to the drive.
35237Axis (): Internal error of BiSS-C encoder.Refer to BiSS-C Encoder User Manual.
35238Axis (): HIPERFACE encoder data error.Enter the command HSAVE 1 using the drive software.
35239Axis (): ESI manufacturer mismatched. The drive may be equipped with other different motors. This fault disables the drive.Make sure the correct manufacturer data has been downloaded to the drive.
35240Axis (): Encoder index line is not connected. This fault disables the drive.Check whether the drive is configured for working with the index signal (using MENCTYPE), and check if the index signal is connected.
35241Axis (): Power brake load is open.
35242Axis (): Short circuit of the power brake.
35243Axis (): A stall condition occurs when [I > MICONT] and [I > 0.9×ILIM] and [V < STALLVEL]. A stall fault occurs whenever a stall condition persists for a duration greater than STALLTIME. This fault disables the drive.Remove the stall condition, and take care to prevent stall conditions.
35244Axis (): Secondary encoder index line not connected. This fault disables the drive.Check whether the drive is configured for working with the index signal on the secondary encoder, and check if the index signal is connected.
35245Axis (): One of the secondary feedback signals is not connected. This fault disables the drive.Check whether all signals from the secondary encoder are properly connected to the drive.
35246Axis (): One of the Pulse & Direction signals is not connected. This fault disables the drive.Check whether all signals to the P&D inputs are properly connected to the drive.
35247Axis (): A fault occurred on the power brake. This fault disables the drive.Replace the motor brake.
35248Axis (): The motor moves in negative direction although the commanded current is positive. Commutation is incorrect. (Algebraic signs of actual current, acceleration and velocity do not match). This fault disables the drive.Correct MPHASE setting. Activate and improve the phase find process.
35249Axis (): Communication between the drive and the motor encoder did not initialize correctly.1. The circuit connection between the robot body and the control cabinet is poor. 2. The encoder or drive may be faultyCheck whether the feedback device is wired correctly. Check whether the correct encoder type (MENCTYPE) is selected.
35250Axis (): Communication with the Nikon feedback device did not initialize correctly. This fault disables the drive.Check whether the feedback device is wired correctly. Check whether the correct encoder type (MENCTYPE) is selected.
35251Axis (): The initialization process with the Tamagawa feedback device has failed. This fault disables the drive.Check whether the wiring to the encoder is correct.
35252Axis (): One of the primary feedback signals is not connected. This fault occurs in incremental encoder, resolver, and sine encoder feedback types. This fault disables the drive.Refer to the section Sine Encoder and Resolver Diagnostics. Check whether all signals from the primary feedback device are properly connected to the drive.
35253Axis (): The drive has detected either 000 or 111 state on the Hall feedback signals. This fault disables the drive.Check whether the Hall signals are all properly connected. While turning the motor, read the Halls state (using HALLS) to see which signal is not connected. If the feedback type is Tamagawa, check whether the feedback wiring is correct.
35254Axis (): The encoder battery voltage is low, please replace the battery.The battery is a consumable that must be replaced regularly. To purchase, please contact the manufacturer.Replace the battery and then reset the drive. If the battery is replaced while the drive is on, the position information is retained.
35255Axis (): Controller synchronization signal is missing or not stable. The fault is detected only when synchronization is enabled by SYNCSOURCE command.Check for controller synchronization signal. Check the cable connection and wiring.
35256Axis (): The computed equivalent encoder output frequency exceeds the upper limit for this signal, which is 4 MHz. This fault disables the drive.Check the parameters used for setting up the equivalent encoder output. If using a sine encoder, check the ENCOUTRES parameter settings.
35257Axis (): Several faults are indicated by the feedback device and include one or more of the following: battery low/error, over-speed, counting error, multiturn error. This fault disables the drive.Check the battery voltage and feedback wiring. Make sure the motor did not move at a high velocity during encoder initialization.
35258Axis (): Several possible issues are indicated by this feedback device fault: battery low or error; over-speed; counting error; multiturn error. This fault disables the drive.Check the battery voltage and feedback wiring. Make sure the motor did not move at a high velocity during encoder initialization.
35259Axis (): Line break in differential Hall sensors. This fault disables the drive.Make sure HALLSTYPE matches the Hall sensors in use (single-ended or differential). Check whether all signals from the differential Hall sensors are properly connected to the sensor.
35260Axis (): In normal incremental encoder operation, quadrature inputs A and B are 90 degrees out of phase. The phase error occurs when edge transition is detected simultaneously on the A and B signals. This fault disables the drive.Set MENCAQBFILT to 0 to remove the filter on A and B signals. If problem persists, it may be due to a faulty encoder.
35261Axis (): Loss of commutation/encoder counts for AqB encoder. The index signal serves as a reference position for detecting loss of commutation/pulses. The AqB encoder counter is compared at different index positions. Between index position captures the count must be exactly MENCRESx4 (or 0 counts if moved back to same index position). This fault disables the drive.If a fault occurs shortly after motion begins, check MENCRES settings. If a fault occurs after some time it is likely due to EMI noise. Improve the installation. Make sure ground is connected. Make sure shield is connected on feedback and motor cables.
35262Axis (): The drive has detected an internal fault on the SensAR encoder through communication. This fault disables the drive.Use command SRVSNSINFO to identify the fault.
35263Axis (): Communication problem between the drive and the EnDat encoder. This fault disables the drive.Check whether the data and clock signals to the EnDat encoder are connected properly. The cable must be shielded.
35264Axis (): Feedback analog signal is out of range. This fault is related to resolver and sine encoder feedback. The drive checks whether the amplitudes of the sine and cosine signals are correct, based on the calculation sin2 + cos2 = 1. This fault disables the drive.Refer to the section Sine Encoder and Resolver Diagnostics. Check the amplitudes of the sine and cosine signals.
35265Axis (): One or more faults are indicated by the feedback device, including: battery low or error, over-speed, counting error, multiturn error. This fault disables the drive.Check the battery voltage and feedback wiring. Make sure the motor did not move at a high velocity during encoder initialization.
35266Axis (): Mismatch between calculated and actual encoder quadrature information. This fault disables the drive.Check the feedback device wiring. Make sure the correct encoder type (MENCTYPE) is selected.
35267Axis (): The sine/cosine calibration parameters are out of range. This fault is related to resolver and sine encoder feedback. This fault disables the drive.Re-execute the sine/cosine calibration process.
35268Axis (): The current supplied by the drive on the 5V primary encoder supply has exceeded the preset current limit. The drive allows this fault to occur up to 3 times in succession. After 3 faults, the drive forces a delay of 1 minute before it can be reenabled.The CDHD can source a maximum current of 250 mA to the primary encoder. Check for short-circuit at the encoder. Check if the encoder is drawing more than the current limit.
35269Axis (): The drive could not detect the proper gain setting or sampling point for the sine/cosine signals. This fault disables the drive.Check resolver wiring and gain value.
35270Axis (): CRC error occurred while drive was communicating with EnDat encoder. Also caused by EnDat encoder setting Alarm bit/s to indicate an encoder problem. This fault disables the drive.Reset the encoder including encoder power off.
35271Axis (): The connection between controller and drive was removed. This fault disables the drive.Reestablish the connection between controller and drive.
35272Axis (): The fieldbus controller has not sent a target command in 3 instances. This fault disables the drive.Clear the fault and allow the controller to send new commands.
35273Axis (): Drive detected disconnection between CAN master and drive. This fault disables the drive.Reconnect master and slave, and power cycle the drive.
35274Axis (): Security code and key do not match. Drive cannot be enabled.Contact technical support.
35275Axis (): EtherCAT packets have been lost. This fault disables the drive.Make sure the EtherCAT master (controller) sends the packets within the time defined (by the master).
35276Axis (): Torque feedback out of limit.
35277Axis () An unexpected high current overshoot has been detected. This fault disables the drive.Check and modify current controller settings.
35278Axis (): Actual velocity exceeded 1.2 times the velocity limit. The velocity limit is set using VLIM. This fault disables the drive.Check whether VLIM is set to match the application requirements. Using velocity loop tuning, check for excessive overshoot.
35279Axis (): The velocity error (VE) has exceeded the velocity error limit (VEMAX). This fault disables the drive.Change drive tuning to improve velocity tracking, or increase VEMAX to allow a greater velocity error.
35280Axis (): The position error (PE) has exceeded the position error limit (PEMAX). This fault disables the drive.Change drive tuning to improve position tracking, or increase PEMAX to allow a greater position error.
35281Axis (): Position deviation between motor and load is too great. This fault disables the drive.Increase SFBPETHRESH, STBPETIME.SFBPEMAX, or improve position tuning.
35282Axis (): The position error (PE) has reached the software numerical limit. This fault disables the drive.Check tuning.
35283Axis (): Drive was enabled and in an operational state upon receiving a command to move to a lower state of communication. This fault disables the drive.Make sure the controller does not switch to a lower state of communication while the drive is disabled.
35284Axis (): Internal error due to an endless while loop or a numerical issue. This fault disables the drive.Contact technical support.
35285Axis (): Motor type nameplate data cannot be read. This fault disables the drive.Reconnect the feedback device. Make sure the motor type nameplate data is present.
35286Axis (): Parameter was changed, and requires SAVE and power cycle to take effect. This fault disables the drive.SAVE and then cycle power to the drive.
35287Axis (): CPU has exceeded its computational limit. Realtime execution takes longer than 31.25 µs. This fault disables the drive.Contact technical support.
35288Axis (): The calculated checksum of the PFB backup data does not match the expected checksum. This fault disables the drive.If required by the application, home the machine.
35289Axis (): Multiturn data of the PFB cannot be restored due to axis movement. This fault disables the drive.If required by the application, home the machine.
35290Axis (): PFB backup memory is empty. This fault disables the drive.If required by the application, home the machine.
35291Axis (): The external pulse train frequency has exceeded the maximum specified input frequency. This fault disables the drive.Reduce the frequency of the gearing pulses commanded from the controller.
35301Axis (): Short circuit of the drivei. The U, V, and W outputs of the drive are short-circuited; ii. The drive is disturbed, which causes the DI signal to be abnormal. This is a false alarm; 1. The ground wire is not connected well; 2. The parameter setting of the current loop regulator is not suitable, causing current oscillation and interference; iii. The drive is damaged (such as IGBT short circuit, abnormity in detecting circuit by the current).i. Check the U, V, and W wiring of the drive (for example, after disconnecting the motor power cable, observe whether the drive still reports a short-circuit fault. It must be done under the premise that the motor's band-type brake is disconnected to ensure mechanical safety); ii. Check the drive IGBT with a multimeter to confirm whether it is short-circuited; iii. Standardize the wiring, especially ground wire; iv. Adjust the parameters of the current loop; v. Replace the drive.
35302Axis (): Drive output short circuited to groundi. The U, V, and W outputs of the drive are short circuited to ground; ii. The drive is damaged (such as abnormity in detecting circuit by the current).i. Check the U, V, and W wiring of the drive; ii. Replace the drive.
35303Axis (): Abnormal encoder datai. Hiperface encoder fault; ii. Encoder wiring error; iii. The internal AD calibration parameters of the drive are abnormal.i. Replace the encoder; ii. Check the encoder wiring and ensure that it is correct; iii. Replace the drive.
35304Axis (): Rotor positioning errori. The setting of position loop, velocity loop, and current loop regulator parameters is unreasonable; ii. The motor parameters are set incorrectly; iii. The parameter 0x20D2 is set too small; iv. The parameter 0x2003 is set incorrectly; v. The peripheral wiring of the drive is incorrect (such as the motor power cable and the motor encoder cable); vi. The internal circuit of the drive is abnormal; vii. The parameter 0x2207 static balance torque compensation value is not set properly.i. Check the peripheral wiring of the drive and ensure that it is correct. ii. Adjust the parameters of the position loop, velocity loop, and current loop regulator parameters of the drive, and ensure that the motor parameters are set correctly; iii. Re-detect the rotor position compensation angle; iv. Increase the setting value of parameter 0x20D2; v. Replace the drive; vi. Reduce the setting value of parameter 0x2207 static balance torque compensation value.
35305Axis (): Abnormal motor's band-type brakei. The motor's band-type brake itself is abnormal; ii. When the motor is operating at high velocity, the servo suddenly turns OFF; iii. The servo parameters 0x2233 and 0x20D2 are set too small; iv. A short circuit occurs in the motor's band-type brake circuit.i. Replace the motor's band-type brake; ii. Increase parameters 0x2233 and 0x20D2; iii. Check the motor's band-type brake circuit.
35306Axis (): EtherCAT PDO configuration errori. PDO is configured incorrectly.i. Correct the EtherCAT PDO configuration.
35307Axis (): Abnormal encoder internal communicationa. A fault occurs in the encoder; b. The motor encoder wiring is abnormal (such as line break, the shielded twisted pair cable is not used, and it is coupled with the motor power cable); c. The ground wire of the drive is not reliably connected; d. Strong interference sources exist around the drive.a. Check the wiring of the motor encoder and ensure that the wiring is standard and correct; b. Add magnetic rings to the encoder cable and the motor power cable; c. Reliably connect the ground wire of the drive; d. Replace the motor encoder; e. Remove the strong interference sources around the drive, or independently supply power to the drive and the surrounding strong interference sources; f. Add a line filter to the input power supply of the drive.
35308Axis (): Encoder type changei. The encoder type has been changed.i. Re-power on or soft reset the drive.
35309Axis (): Drive phase U over-currenti. The parameter setting of the current loop regulator is unreasonable, leading to the current control oscillation; ii. The motor parameters are set incorrectly; iii. The internal current sampling circuit of the drive is abnormal.i. Adjust the parameters of the current loop regulator; ii. Set motor parameters correctly; iii. Replace the drive.
35310Axis (): Drive phase V over-currenti. The parameter setting of the current loop regulator is unreasonable, leading to the current control oscillation; ii. The motor parameters are set incorrectly; iii. The internal current sampling circuit of the drive is abnormal.i. Adjust the parameters of the current loop regulator; ii. Set motor parameters correctly; iii. Replace the drive.
35311Axis (): Drive phase W over-currenti. The parameter setting of the current loop regulator is unreasonable, leading to the current control oscillation; ii. The motor parameters are set incorrectly; iii. The internal current sampling circuit of the drive is abnormal.i. Adjust the parameters of the current loop regulator; ii. Set motor parameters correctly; iii. Replace the drive.
35312Axis (): DC bus over-voltagei. The input power supply voltage of the drive is too high; ii. The dynamic braking energy is excessive when the motor stops quickly; 1. The deceleration is excessive when the motor stops; 2. The wiring of the dynamic braking resistor is incorrect; 3. The value of the dynamic braking resistance is too high; iii. The internal voltage sampling circuit of the drive is abnormal; iv. The internal dynamic braking circuit of the drive is abnormal.i. Adjust the input power supply of the drive to the permissible range; ii. Reduce the motor deceleration when stopping; iii. Check the wiring of the dynamic braking resistor and ensure that it is correct; iv. Properly reduce the resistance of the dynamic braking resistor (the resistance shall not be lower than the minimum allowable value), and increase the power of the dynamic braking resistor.
35313Axis (): Control power supply under-voltagei. The 24V control power supply is abnormal; ii. The wiring of the 24V control power supply is incorrect, such as poor wiring; iii. The load of the 24V control power supply is excessive; iv. The internal circuit of the drive is abnormal.i. Check the wiring of the 24V control power supply and ensure that it is reliable; ii. Check the load of the 24V control power supply and ensure that the capacity of the 24V control power supply can meet the load consumption under all working conditions. iii. Replace the 24V control power supply; iv. Replace the drive.
35314Axis (): Drive continuous overloadi. The motor load is excessive; 1. The actual mechanical load is excessive; 2. There is jamming in the mechanical load; 3. The motor's band-type brake is not released; ii. The motor acceleration and deceleration time is too short; iii. The internal current sampling circuit of the drive is abnormal; iv. The band-type brake circuit of the drive is abnormal.i. Reduce the actual mechanical load of the motor; ii. Increase the motor acceleration and deceleration time; iii. Check the transmission mode of mechanical load to ensure that there is no jamming or other abnormal phenomena; iv. Check the wiring of the motor's band-type brake to ensure reliable wiring; v. Replace the motor; vi. Replace the drive.
35315Axis (): Encoder wiring errori. For CDA8 V1 products, pin 8 and pin 15 of the encoder terminal connector are not short-circuited; ii. For CDA8 V2 products and CDR series products, pin 6 and pin 8 of the encoder terminal connector are not short-circuited; iii. The encoder cable is poorly wired.i. For CDA8 V1 products, pin 8 and pin 15 of the encoder terminal connector are short-circuited; for CDA8 V2 products and CDR series products, pin 6 and pin 8 of the encoder terminal connector are short-circuited, and reliable encoder cable wiring shall be ensured.
35316CPU Overloadi. The drive operation is disturbed; ii. The internal circuit of the drive is abnormal; iii. The data collection of DriveStarter is excessive.i. Standardize the peripheral wiring of the drive and add anti-interference measures; ii. Replace the drive; iii. Close some DriveStarter data collection channels.
35317Axis (): Drive output phase lossi. Line break and poor wiring occur in the U, V, and W outputs of the drive; ii. The motor impedance is excessive; iii. The internal current sampling circuit of the drive is abnormal.i. Check the U, V, and W wiring of the motor and ensure that it is reliable; ii. Replace the motor (or disable drive output phase loss detection); iii. Replace the drive.
35318Axis (): Instantaneous overload of the drivei. The motor load is excessive; ii. The internal temperature sampling circuit of the drive is abnormal; iii. The operating environment temperature of the drive exceeds the permissible operating range; iv. The drive operation is disturbed (such as out of sync); v. The motor acceleration and deceleration are set too large, and the acceleration and deceleration time are set too short.i. Reduce the actual mechanical load of the motor; ii. Standardize the peripheral wiring of the drive and add anti-interference measures; iii. Reduce the ambient temperature, such as improving the cooling conditions of the cabinet; iv. Replace the drive.
35319Axis (): Abnormal external communication transmission of the encodera. The motor encoder wiring is abnormal (such as line break, the shielded twisted pair cable is not used, and it is coupled with the motor power cable); b. The ground wire of the drive is not reliably connected; d. Strong interference sources exist around the drive.a. Check the wiring of the motor encoder and ensure that the wiring is standard and correct; b. Add magnetic rings to the encoder cable and the motor power cable; c. Reliably connect the ground wire of the drive; d. Remove the strong interference sources around the drive, or independently supply power to the drive and the surrounding strong interference sources; e. Add a line filter to the input power supply of the drive.
35320Axis (): Abnormal external communication reception of the encodera. The motor encoder wiring is abnormal (such as line break, the shielded twisted pair cable is not used, and it is coupled with the motor power cable); b. The ground wire of the drive is not reliably connected; d. Strong interference sources exist around the drive.a. Check the wiring of the motor encoder and ensure that the wiring is standard and correct; b. Add magnetic rings to the encoder cable and the motor power cable; c. Reliably connect the ground wire of the drive; d. Remove the strong interference sources around the drive, or independently supply power to the drive and the surrounding strong interference sources; e. Add a line filter to the input power supply of the drive.
35321Axis (): Drive hardware over-currenti. There is jamming or locking in the mechanical load; ii. The rotor compensation angle is set incorrectly; iii. Encoder wiring error; iv. The current loop regulator parameters are set unreasonably, resulting in current control oscillation; v. Motor parameter setting error (wire resistance, wire inductance, counter electromotive force, etc.); vi. The internal current detection circuit of the drive is abnormal; vii. The drive's band-type brake circuit is damaged, without 24V output; viii. The motor's band-type brake is damaged; ix. The motor load is too large, or the motor acceleration and deceleration are set too large, and the acceleration and deceleration time are set too short; x. The setting of 0x60B2 torque compensation value or 0x2207 static balance torque compensation value is unreasonable.i. Check the transmission mode of mechanical load to ensure that there is no jamming or other abnormal phenomena; ii. Re-detect the rotor compensation angle; iii. Check the wiring of the motor encoder and ensure that the wiring is standard and correct; iv. Adjust the parameters of the current loop regulator; v. Set motor parameters correctly; vi. Replace the drive; vii. Replace the motor; vii. Check the transmission mode of mechanical load to ensure that there is no jamming or other abnormal phenomena; viii. Confirm whether the mechanical design is reasonable; optimize motor acceleration and deceleration, and extend the acceleration and deceleration time; ix. Optimize the dynamics model of the upper controller and the torque compensation value of the given 0x60B2; or reasonably reset the 0x2207 static balance torque compensation value.
35322Axis (): Abnormal band-type brake circuit of the drivei. The drive's band-type brake output is short circuited; ii. Excessive band-type brake output current of the drive causes over-temperature; iii. The drive's band-type brake output is open circuit; iv. The internal detection circuit of the drive is abnormal.i. Check the wiring of the drive's band-type brake output and ensure it is correct and reliable; ii. Replace the drive.
35323Axis (): Abnormal resolver circuit of the drivei. The internal resolver circuit of the drive is abnormal; ii. The resolver parameter setting of the drive does not match the actual resolver.i. Correctly set the resolver parameters of the drive; ii. Replace the drive.
35324Axis (): Control mode setting errori. When the servo is enabled, the controller sets the control mode that the drive does not support (see the object dictionary 0x6502 for the control mode supported by each product).i. Before enabling the servo, set the controller to the correct control mode.
35325Axis (): Input phase loss faulti. The input power supply of the drive is poorly wired; ii. The drive servo parameter "power circuit setting" is set to three-phase input, but the actual power supply input is single-phase; iii. The front end uses an electronic transformer, which has abnormal harmonics and cannot be identified by the servo.i. Check the input power wiring of the drive and ensure that it is reliable; ii. Set the servo parameter "power circuit setting" correctly; iii. Add a filter to the front end of the servo drive.
35326Axis (): DC bus under-voltagei. The input power supply voltage of the drive is too low; ii. The internal voltage sampling circuit of the drive is abnormal; iii. Servo parameter 0x202C is set incorrectly, 220V power supply is set as 380V power supply; iv. The input power cord of the drive is disconnected.i. Adjust the input power supply of the drive to the permissible range; ii. Replace the drive; iii. Set 0x202C drive parameters correctly; iv. Check the input power cord wiring of the drive.
35327Axis (): Inverter power module over-temperaturei. The motor load is excessive; ii. The internal temperature sampling circuit of the drive is abnormal; iii. The operating environment temperature of the drive exceeds the permissible operating range.i. Reduce the actual mechanical load of the motor; ii. Reduce the ambient temperature, such as improving the cooling conditions of the cabinet; iii. Replace the drive.
35328Axis (): Dynamic braking overloadi. The motor performs frequent quick stop operations, resulting in excessive dynamic braking energy; ii. The servo parameters "resistance of the dynamic braking resistor" and "power of the dynamic braking resistor" are set incorrectly.i. Correctly set the servo parameters "resistance of the dynamic braking resistor" and "power of the dynamic braking resistor"; ii. Change the operating conditions of the motor to avoid frequent quick stop operations of the motor, such as extending the stop time of the motor.
35329Axis (): Continuous motor overloadi. The motor load is excessive; 1. The actual mechanical load is excessive; 2. There is jamming in the mechanical load; 3. The motor's band-type brake is not released; ii. The motor acceleration and deceleration time is too short; iii. Motor parameters are set incorrectly; iv. The internal current sampling circuit of the drive is abnormal; v. The band-type brake circuit of the drive is abnormal; vi. The selected motor type is not suitable and the power is too small (for example, high-power drives with small-power motors, which operate at high velocity with full load for a long time).i. Reduce the actual mechanical load of the motor; ii. Increase the acceleration and deceleration time when the motor is running; iii. Check the transmission mode of mechanical load to ensure that there is no jamming or other abnormal phenomena; iv. Check the wiring of the motor's band-type brake to ensure reliable wiring; v. Check the motor parameters to ensure that they are set correctly (such as the rated current and thermal time constant of the motor); vi. Replace with a high-capacity motor; vii. Replace the drive.
35330Axis(): Rectifier power module over-temperaturei. The motor load is excessive; ii. The internal temperature sampling circuit of the drive is abnormal; iii. The operating environment temperature of the drive exceeds the permissible operating rangei. Reduce the actual mechanical load of the motor; ii. Reduce the ambient temperature, e.g. improve the heat dissipation conditions of the cabinet; iii. Replace the drive.
35331Axis (): Motor U–phase instantaneous overloadi. The motor load is excessive; 1. The actual mechanical load is excessive; 2. The mechanical load leads to jamming or locking; 3. The motor's band-type brake is not released; ii. The motor acceleration and deceleration time is too short; iii. The rotor offset angle is set incorrectly; iv. The motor parameter is set incorrectly. v. The internal current sampling circuit of the drive is abnormal; vi. The drive's band-type brake circuit is abnormal; vii. Inadequate capacity of the motor model selected; viii. Poor or detached contact of one phase of the motor power line.i. Reduce the actual mechanical load of the motor; ii. Increase the acceleration and deceleration time durations during motor operation; iii. Check the transmission mode of mechanical load to ensure that there is no jamming or other phenomena; iv. Re-check the rotor offset angle; v. Check the wiring of the motor's band-type brake to ensure reliable wiring; vi. Check the motor parameters to ensure that they are set correctly (such as the rated current, fast overload protection threshold, and fast overload protection time duration of the motor); vii. Change to a high–capacity motor; viii. Replace the drive; ix. Check whether the wiring of motor power line is reliable.
35332Axis (): Motor V–phase instantaneous overloadi. The motor load is excessive; 1. The actual mechanical load is excessive; 2. The mechanical load leads to jamming or locking; 3. The motor's band-type brake is not released; ii. The motor acceleration and deceleration time is too short; iii. The rotor offset angle is set incorrectly; iv. The motor parameter is set incorrectly. v. The internal current sampling circuit of the drive is abnormal; vi. The drive's band-type brake circuit is abnormal; vii. Inadequate capacity of the motor model selected; viii. Poor or detached contact of one phase of the motor power line.i. Reduce the actual mechanical load of the motor; ii. Increase the acceleration and deceleration time durations during motor operation; iii. Check the transmission mode of mechanical load to ensure that there is no jamming or other phenomena; iv. Re-check the rotor offset angle; v. Check the wiring of the motor's band-type brake to ensure reliable wiring; vi. Check the motor parameters to ensure that they are set correctly (such as the rated current, fast overload protection threshold, and fast overload protection time duration of the motor); vii. Change to a high–capacity motor; viii. Replace the drive; ix. Check whether the wiring of motor power line is reliable.
35333Axis (): Motor W–phase instantaneous overloadi. The motor load is excessive; 1. The actual mechanical load is excessive; 2. The mechanical load leads to jamming or locking; 3. The motor's band-type brake is not released; ii. The motor acceleration and deceleration time is too short; iii. The rotor offset angle is set incorrectly; iv. The motor parameter is set incorrectly. v. The internal current sampling circuit of the drive is abnormal; vi. The drive's band-type brake circuit is abnormal; vii. Inadequate capacity of the motor model selected; viii. Poor or detached contact of one phase of the motor power line.i. Reduce the actual mechanical load of the motor; ii. Increase the acceleration and deceleration time durations during motor operation; iii. Check the transmission mode of mechanical load to ensure that there is no jamming or other phenomena; iv. Re-check the rotor offset angle; v. Check the wiring of the motor's band-type brake to ensure reliable wiring; vi. Check the motor parameters to ensure that they are set correctly (such as the rated current, fast overload protection threshold, and fast overload protection time duration of the motor); vii. Change to a high–capacity motor; viii. Replace the drive; ix. Check whether the wiring of motor power line is reliable.
35334Axis (): Abnormal communication of the power supply unit modulei. Poor connection of the control cable between the power supply unit module and the motor module; ii. The control port between the power supply module and the motor module is burnt due to short circuit of the motor's band-type brake cable or external 24V (STO) to ground.i. Check the control cable connection between the power supply unit module and the motor module and ensure the wiring is reliable; ii Check for short circuit to ground on the motor's band-type brake cable or external 24V (STO); iii. Replace the drive.
35335Axis (): Hardware STO1 triggeredi. STO1 is triggered or is poorly wired.i. Check STO1 wiring and make sure the wiring is reliable; ii. Verify that the STO1 circuit (e.g. emergency stop switch) is not triggered.
35336Axis (): Hardware STO2 triggeredi. STO2 is triggered or is poorly wired.i. Check the STO2 wiring and make sure the wiring is reliable; ii. Verify that the STO2 circuit (e.g. emergency stop switch) is not triggered.
35337Axis (): Abnormal STO wiringi. STO1/STO2 is poorly wired.i. Check STO1/STO2 wiring and make sure the wiring is reliable.
35338Axis (): Drive external faulti. Fault of other axes. ii. Abnormal internal circuit of the drive.i. Check other axes and make sure they are free of fault; ii. Such fault can be disabled by modifying the servo parameter "Fault operation switch"; iii. Replace the drive.
35339Axis (): Excessive position tracking errori. The mechanical load of the motor leads to jamming or locking, so that the motor cannot operate; ii. The planned acceleration for the target position value of the host computer is too high; iii. The servo parameters 0x6065 and 0x6066 are too small; iv. Unreasonable setting of the drive regulator parameters leads to unsatisfactory position tracking performance; v. The internal circuit of the drive is abnormal.i. Check the transmission mode of mechanical load to ensure that there is no jamming or other issue; ii. Appropriately reduce the planned acceleration for the target position value of the host computer; iii. Appropriately increase the setting value of the servo parameters 0x6065 and 0x6066; iv. Optimize regulator parameters to improve position tracking performance; v. Replace the drive.
35340Axis (): Position control overflowi. The actual or target value of the position exceeds the maximum permissible range.i. Execute the "encoder multi-turn zeroing" command and ensure that the motor operating range does not exceed the maximum permissible range; ii. If it is necessary to operate the motor in a large range, the unlimited position control mode can be enabled through the servo parameter "position control switch".
35341Axis (): Excessive velocity tracking errori. The mechanical load of the motor leads to jamming or locking, so that the motor cannot operate; ii. The setting values of the servo parameters 0x20A3 and 0x20A4 are too small; iii. Unreasonable setting of the drive regulator parameters leads to unsatisfactory velocity tracking performance; iv. The internal circuit of the drive is abnormal.i. Check the transmission mode of mechanical load to ensure that there is no jamming or other phenomena; ii. Appropriately increase the setting values of the servo parameters 0x20A3 and 0x20A4; iii. Optimize the regulator parameters to improve velocity tracking performance; iv. Replace the drive.
35342Axis (): Control cycle parameter setting errori. Unreasonable setting of the EtherCAT communication cycle, position control cycle and velocity control cycle.i. Set the EtherCAT communication cycle, position control cycle and velocity control cycle correctly.
35343Axis (): EEPROM writing failedi. The internal circuit of the drive is abnormal; ii. The drive is interferedi. Replace the drive; ii. Re-power on the drive and improve the anti-interference measures of the drive.
35344Axis (): Origin searching failedi. Unreasonable parameter setting of origin searching (objects 0x6098, 0x6099, 0x609A); ii. The motor is already in the limit switch trigger state when the origin searching is activated; iii. Switch to non-HM mode during origin searching.i. Set the origin searching parameters correctly (objects 0x6098, 0x6099, 0x609A); ii. Ensure that the motor is not in the limit switch trigger state when the origin searching is activated.
35345Axis (): Illegal EtherCAT bus instructioni. The EtherCAT communication state machine is incorrectly matched with the control word time sequence.i. The host computer correctly handles the EtherCAT communication state computer and control word time sequence.
35346Axis (): Abnormal DriveStarter communicationi. The drive commissioning cable is disconnected or is poorly contacted. ii. The communication of the drive commissioning serial port is interfered.i. Check the wiring of the drive commissioning cable and ensure reliable connection; ii. Replace isolated serial port commissioning cable; iii. Strengthen anti-interference measures for the commissioning cable, such as adding magnetic rings, reliable grounding of commissioning computer, and provide power supply for the debugging computer and the drive separately.
35347Axis (): Abnormal communication of the EtherCAT busi. The EtherCAT communication is interfered; ii. Disconnection or poor contact of EtherCAT network cables; iii. Insufficient real-time performance of the host computer; iv. Mismatch between the underlying DC synchronization mechanism of the EtherCAT master of the host computer and the drive requirements; v. The internal circuit of the drive is abnormal.i. Optimize EtherCAT communication wiring and strengthen anti-interference measures, such as using Category 5E shielded twisted pair network cables and ensuring reliable grounding of the controller; ii. Check the connection of EtherCAT network cables to ensure reliable connection; iii. Change to the host computer with stronger real-time performance, or extend the EtherCAT communication cycle; iv. Appropriately increase the servo parameter 0x20D3 setting value; v. Modify the underlying DC synchronization mechanism of the EtherCAT master of the host computer to ensure that the RxPDO data sent by the host computer is at least 130 μs ahead of the DC synchronization signal; vi. Replace the drive.
35348Axis (): The position exceeds the hardware limitationi. Limit switch input triggered.i. Check the state of the limit switch and ensure that it is not triggered.
35349Axis (): Positive software limitationi. The actual position value exceeds the threshold set by the servo parameters 0x2004 and 0x2005.i. Appropriately increase the setting value of the servo parameters 0x2004 and 0x2005; ii. Operate the motor within the range specified by the servo parameters 0x2004 and 0x2005; iii. If users do not want to use this function, they can disable the software limitation detection function through the servo parameter "Position control switch".
35350Axis (): Negative software limitationi. The actual position value exceeds the threshold set by the servo parameters 0x2004 and 0x2005.i. Appropriately increase the setting value of the servo parameters 0x2004 and 0x2005; ii. Operate the motor within the range specified by the servo parameters 0x2004 and 0x2005; iii. If users do not want to use this function, they can disable the software limitation detection function through the servo parameter "Position control switch".
35351Axis (): Excessive deviation of the power-on positioni. After the drive is powered off, the motor position is shifted; ii. For motor encoders with batteries, the external battery is unavailable or the battery is under-voltage.i. For motor encoders with batteries, ensure the battery is connected and the battery voltage is normal; ii. If users don't want to use this function, they can set the servo parameter 0x200E to 0, and disable the detection function of excessive power-on position deviation.
35352Axis (): Power-on position control overflowi. For motor encoders with batteries, the external battery is unavailable or the battery is under-voltage; ii. The drive is powered off in any of the following control mode: the unlimited position control mode, velocity mode, or torque mode, and the position has exceeded the permissible range.i. Re-power on the drive after the encoder multi-turn zeroing command is executed; ii. In the unlimited position control mode, if users do not want to use this function, they can modify the servo parameter "Position control switch" to disable the power-on position control overflow detection function.
35353Axis ():Encoder battery under-voltage faulti. The encoder is not connected with an external battery or the battery is poorly wired; ii. The encoder battery is under-voltage.i. Check the battery wiring of the encoder to ensure reliable wiring; ii. Replace the battery; iii. If a Panasonic or Tamagawa encoder is connected, the encoder multi-turn zeroing command needs to be executed for individual versions; iv. If users do not want to use this function, they can modify the servo parameter 0x2009 to disable the encoder battery under-voltage detection function.
35354Axis (): The Motor exceeds the velocity limiti. Unreasonable setting of drive regulator parameters leads to large speed tracking overshoot; ii. Poor wiring of the encoder; iii. The encoder data transmission is interfered; iv. The encoder is damaged; v. The internal circuit of the drive is abnormal.i. Optimize regulator parameters to improve speed tracking performance; ii. Check the encoder cable connection to ensure reliable wiring; iii. Strengthen the anti-interference measures of encoder cables, such as adding magnetic rings, using shielded twisted pair cables, and realizing reliable grounding; iv. Replace the encoder; v. Replace the drive.
35355Axis (): Excessive voltage limit position tracking errori. The mechanical load of the motor is jammed so that the motor cannot operate; ii. The planned acceleration of the host computer's target position value is too high; iii. The servo parameters 0x6065 and 0x6066 are too small. iv. Unreasonable setting of drive regulator parameters leads to unsatisfactory position tracking performance; v. The input power supply voltage of the drive is too low; vi. The internal circuit of the drive is abnormal.i. Check the transmission mode of mechanical load to ensure that there is no jamming or other phenomena; ii. Appropriately reduce the planned acceleration of the host computer's target position value; iii. Appropriately increase the setting value of the servo parameters 0x6065 and 0x6066; iv. Optimize regulator parameters to improve position tracking performance; v. Ensure that the input power supply voltage of the drive is within the specified range; vi. Replace the drive.
35356Axis (): Encoder over-speed faulti. Unreasonable setting of drive regulator parameters leads to large speed tracking overshoot; ii. Poor wiring of the encoder; iii. The encoder data transmission is interfered; iv. The encoder is damaged; v. The internal circuit of the drive is abnormal; vi. When the servo motor is enabled, an external force rotates the motor shaft.i. Optimize regulator parameters to improve speed tracking performance; ii. Check the encoder cable connection to ensure reliable wiring; iii. Strengthen the anti-interference measures of encoder cables, such as adding magnetic rings, using shielded twisted pair cables, and realizing reliable grounding; iv. Replace the encoder; v. Replace the drive; vi. Check the mechanical load at the end of the motor shaft to ensure that the motor shaft is not subjected to gravity or external mechanical forces.
35357Axis (): Operation error of position planningi. Unreasonable setting of position planning parameters, such as the target position value and the planned target deceleration (0x6084).i. Set position planning parameters correctly.
35358Axis (): Multi-axis synchronization exceptioni. The internal circuit of the drive is abnormal.ii. Replace the drive.
35359Axis (): EtherCAT bus synchronization exceptioni. Unreasonable setting of the servo parameter 0x20D3; ii. The EtherCAT master synchronization mode is incorrectly configured.i. Set the servo parameter 0x20D3 correctly; ii. Correctly configure the synchronization mode of the EtherCAT master.
35360Axis (): EEPROM version changei. The drive firmware is upgraded.i. Re-power on the drive.
35361Axis (): Motor overload alarmi. The motor load is excessive; 1. The actual mechanical load is excessive; 2. The mechanical load leads to jamming; 3. The motor's band-type brake is not released; ii. The motor acceleration and deceleration time is too short; iii. The motor parameter is set incorrectly; iv. The internal current sampling circuit of the drive is abnormal; v. The drive’s band-type brake circuit is abnormal.i. Reduce the actual mechanical load of the motor; ii. Prolong the acceleration and deceleration time durations during motor operation; iii. Check the transmission mode of mechanical load to ensure that there is no jamming or other phenomena; iv. Check the wiring of the motor's band-type brake to ensure reliable wiring; v. Check the motor parameters to ensure that they are set correctly (such as the rated current and thermal time constant of the motor); vi. Change to a high-capacity motor. Vii. Replace the drive.
35362Axis (): Speed limit alarmi. In the speed mode, the target speed exceeds the maximum speed of the motor; ii. In the position mode, the planned speed exceeds the maximum speed of the motor; iii. Servo parameter setting is unreasonable.i. Reduce the target or planned speed; ii. Change to a motor with higher maximum speed; iii. Reset the maximum planned speed of the parameter 0x607F according to the actual situation.
35363Axis (): DC bus under-voltage alarmi. The input power supply voltage of the drive is too low; ii. The internal voltage sampling circuit of the drive is abnormal.i. Adjust the input power supply of the drive to the permissible range; ii. Replace the drive.
35364Axis (): Control mode setting unsupportedi. (Delete when the servo motor is enabled) The controller sets the control mode that the drive does not support (see the object dictionary 0x6060 and 0x6502 for the control mode supported by each product); ii. The control mode is not specified after the communication between the controller and the servo motor is established.i. Before enabling the servo, set the controller to the correct control mode.
35365Axis (): Effective parameters for re-power-on changedi. Servo parameters for re-power-on modifiedi. Re-power on the drive
35366Axis (): Encoder battery under-voltage alarmi. The encoder is not connected with an external battery or the battery is poorly wired; ii. The encoder battery is under-voltage; iii. The encoder battery cables are wired reversely or short circuited to ground due to the damaged sheath.i. Check the battery wiring of the encoder to ensure reliable wiring; ii. Replace the battery; iii. If a Panasonic or Tamagawa encoder is connected, the encoder multiturn zeroing command needs to be executed for individual versions; iv. If users do not want to use this function, they can modify the servo parameter 0x2009 to disable the encoder battery under-voltage detection function.
35367Axis (): Drive internal alarmi. The internal circuit of the drive is abnormal.i. Replace the drive; ii. Contact the after-sales for technical support.
35368Axis (): Mechanical zero uncalibratedi. The encoder battery failed due to under-voltage, and the servo parameter 0x2009.Byte3 is set to "Encoder battery under-voltage fault is detected and zero uncalibrated is informed"; ii. There is a fault of excessive deviation of the power-on position and the user determined that the mechanical zero is lost; iii. The motor features a single-turn absolute encoder and the driver failed to execute the origin searching instruction.i. Zero the drive.
35369Axis (): Encoder receiving external communication alarma. The motor encoder wiring is abnormal (such as line break, the shielded twisted pair cable is not used, and it is coupled with the motor power cable); b. The ground wire of the drive is not reliably connected; d. Strong interference sources exist around the drive.Encoder receiving external communication alarm
35370Axis (): Encoder sending external communication alarma. The motor encoder wiring is abnormal (such as line break, the shielded twisted pair cable is not used, and it is coupled with the motor power cable); b. The ground wire of the drive is not reliably connected; d. Strong interference sources exist around the drive.a. Check the wiring of the motor encoder and ensure that the wiring is standard and correct; b. Add magnetic rings to the encoder cable and the motor power cable; c. Reliably connect the ground wire of the drive; d. Remove the strong interference sources around the drive, or independently supply power to the drive and the surrounding strong interference sources; e. Add a line filter to the input power supply of the drive.
35371Axis (): Encoder internal communication alarmEncoder internal communication alarma. Check the wiring of the motor encoder and ensure that the wiring is standard and correct; b. Add magnetic rings to the encoder cable and the motor power cable; c. Reliably connect the ground wire of the drive; d. Replace the motor encoder; e. Remove the strong interference sources around the drive, or independently supply power to the drive and the surrounding strong interference sources; f. Add a line filter to the input power supply of the drive.
35372Axis (): Software limitation alarmi. The actual or target position value exceeds the threshold set by the servo parameters 0x2004 and 0x2005.i. Appropriately increase the setting value of the servo parameters 0x2004 and 0x2005; ii. Operate the motor within the range specified by the servo parameters 0x2004 and 0x2005; iii. Reduce the target position value so that it falls within the range specified by the servo parameters 0x2004 and 0x2005; iv. If users do not want to use this function, they can disable the software limitation detection function through the servo parameter "Position control switch".
35373Axis (): AD correction coefficient invalid alarmi. The drive is not subjected to AD correction.i. Reset the drive AD correction coefficient
35374Abnormal position planning parameter alarmi. Unreasonable setting of position planning parameters.i. Set position planning parameters correctly.
35375Excessive power-on position deviation alarmi. The motor position deviates after the drive is powered off.i. The drive executes the fault reset command; ii. Re-power on or perform the soft reset of the drive.
35401Axis (): Short circuit of the drive1. The U/V/W output cable of the drive is short-circuited, or short-circuited to ground; 2. The U/V/W output cable of the motor is short-circuited, or short-circuited to ground; 3. An internal cable of the drive is short-circuited, or short-circuited to ground; 4. False alarm is caused because the drive is interfered1. If a short circuit occurs between the cable's UVW phases, or between the cable's U/V/W and grounding, dispose or replace the cable; 2. If a short circuit occurs between the motor's UVW phases, or between the motor's U/V/W cable and grounding, replace the motor; 3. If faults still occur after disconnecting the drive U/V/W output wiring, replace the drive; 4. Improve the electromagnetic environment of the equipment by standardizing wiring and cabling, increasing the cross-sectional area of the grounding wire and adding magnetic rings.
35402Axis (): Excessive U-phase output current1. The parameter setting of the current loop regulator is unreasonable, leading to the current control oscillation; 2. The motor parameters are set incorrectly; 3. The internal current sampling circuit of the drive is abnormal.1. Adjust the parameters of the current loop regulator; 2. Set motor parameters correctly; 3. Replace the drive
35403Axis (): Excessive V-phase output current1. The parameter setting of the current loop regulator is unreasonable, leading to the current control oscillation; 2. The motor parameters are set incorrectly; 3. The internal current sampling circuit of the drive is abnormal.1. Adjust the parameters of the current loop regulator; 2. Set motor parameters correctly; 3. Replace the drive
35404Axis (): Excessive W-phase output current1. The parameter setting of the current loop regulator is unreasonable, leading to the current control oscillation; 2. The motor parameters are set incorrectly; 3. The internal current sampling circuit of the drive is abnormal.1. Adjust the parameters of the current loop regulator; 2. Set motor parameters correctly; 3. Replace the drive
35405Axis (): Drive hardware over-current1. Excessive motor load or motor acceleration and deceleration setting values, and too short acceleration and deceleration time durations set; 2. The rotor offset angle is set incorrectly, and fails to meet the rotor positioning error detection condition; 3. Abnormal jumps occur in the encoder feedback; 4. The current loop regulator parameters are set unreasonably, resulting in current control oscillation; 5. Motor parameters are incorrectly set (wire resistance, wire inductance, counter electromotive force, rotor inertia, etc.); 6. Current detection circuit inside the drive is abnormal or the drive's band-type brake circuit is damaged, without 24V output; 7. The motor's band-type brake is damaged; 8. The torque offset value or static balance offset value is not set properly.1. Check and handle the mechanical load driving to ensure that there is no jamming or other phenomena; 2. Re-detect the rotor offset angle; 3. Check the motor encoder wiring and ensure that it is standard and correct; 4. Adjust current loop regulator parameters; 5. Set motor parameters correctly; 6. Replace the drive; 7. Replace the motor; 8. Optimize the host controller dynamics model, and optimize the given value or set the value according to the actual load.
35406Axis (): Drive output short circuited to ground1. The drive U/V/W output cable is short-circuited to ground; 2. The motor U/V/W cable is short circuited to ground; 3. There is a short circuit inside the drive or a short circuit to ground.1. If a short circuit occurs between the cable's U/V/W and grounding, repair or replace the cable; 2. If a short circuit occurs between the motor's U/V/W cable and grounding, replace the motor; 3. If faults still occur after disconnecting the drive U/V/W output wiring, replace the drive.
35407Axis (): DC bus over-voltage1. Excessive input power supply voltage of the drive; 2. Excessive dynamic braking energy when the motor stops quickly; 3. The dynamic braking resistor is not connected or wired incorrectly; 4. The over-high resistance value of the dynamic braking resistor; 5. Internal malfunction of the drive.1. Adjust the input power supply of the drive to the permissible range; 2. Reduce the motor deceleration when stopping; 3. Correct the wiring of dynamic braking resistor to ensure correct wiring; 4. Reduce the resistance value of the dynamic braking resistor appropriately (the resistance value cannot be lower than the minimum permissible value) and increase the power of the dynamic braking resistor; 5. Replace the drive.
35408Axis (): DC bus under-voltage1. Excessively low input power supply voltage of the drive; 2. Abnormal voltage sampling circuit inside the drive; 3. The drive power loop is set incorrectly, and the 220 V power supply is set to 380 V power supply; 4. The input power supply cord of the drive is disconnected.1. Adjust the input power supply of the drive to the permissible range for normal working; 2. Replace the drive; 3. Set the drive power loop in consistent with the actual power supply; 4. Check and handle the wiring of the input power supply cord of the drive to ensure that the wiring is correct and secure.
35409Axis (): Power module over-temperature1. The motor load is excessive; 2. The internal temperature sampling circuit of the drive is abnormal; 3. The operating environment temperature of the drive exceeds the permissible range.1. Reduce the actual mechanical load of the motor; 2. Replace the drive; 3. Reduce the ambient temperature, such as improving the heat dissipation conditions of the cabinet.
35410Axis (): CPU1 watchdog overflowInternal malfunction of the drive.Replace the drive.
35411Axis (): CPU2 watchdog overflowInternal malfunction of the drive.Replace the drive.
35412Axis (): Dynamic braking resistor overload1. The frequent quick shutdown of the motor leads to excessive dynamic braking energy; 2. The power setting of the dynamic braking resistor is inconsistent with that of the actual resistor.1. Change the operating conditions of the motor to avoid frequent quick shutdown of the motor, such as extending the stop time of the motor. Or replace the dynamic braking resistor with one of a higher power; 2. Set the power of dynamic braking resistor correctly, with the value set in consistent with the actual power of the dynamic braking resistor.
35413Axis (): Continuous motor overload1. Excessive motor load; 2. Over-short acceleration and deceleration time durations of the motor; 3. Incorrect setting of motor parameters; 4. Abnormal release action of the band-type brake; 5. Wrong motor model with a smaller power (such as the high-power drive loaded with the small-power motor runs at full load and high speed for a long time); 6. Abnormal internal current sampling circuit of the drive.1. Reduce the actual mechanical load of the motor to ensure that the machinery is not jammed; 2. Prolong the acceleration and deceleration time durations during motor operation; 3. Check the motor parameters to ensure that the motor parameters are set correctly (such as the rated current and thermal time constant of the motor); 4. Check the line of the band-type brake of the motor to ensure normal action of the band-type brake; 5. Change to a high–capacity motor; 6. Replace the drive
35414Axis (): Excessive position tracking error1. Excessive motor load; 2. Inappropriate control parameters; 3. Abnormal release action of the band-type brake; 4. Too small threshold or time duration for judging excessive position tracking error.1. Reduce the actual mechanical load of the motor to ensure that the machinery is not jammed; 2. Optimize the control parameters and enhance the corresponding performance of the servo; 3. Check the line of the band-type brake of the motor to ensure normal action of the band-type brake; 4. Appropriately increase the threshold or time duration for judging excessive position tracking error.
35415Axis (): Positive software limitationPosition feedback value exceeds (positive software limitation value + positioning completion threshold).The range of motion should not exceed the setting value for positive software limitation. If the positive software limitation function is not needed, it can be prohibited by the parameter position control switch.
35416Axis (): Negative software limitationPosition feedback value exceeds (negative software limitation value - positioning completion threshold).The range of motion should not exceed the setting value for negative software limitation. If the negative software limitation function is not needed, it can be prohibited by the parameter position control switch.
35417Axis (): Encoder data overflowIn position mode, the encoder multiturn value exceeds the actual encoder multiturn bits when unlimited position control is not enabled.Perform the encoder multiturn zeroing operation, or enable the unlimited position control mode, or work in a non-position mode (torque mode or speed mode).
35418Axis (): CPU1 operation fault1. Operational malfunction of the drive firmware; 2. Internal malfunction of the drive.1. Upgrade the drive firmware; 2. Replace the drive.
35419Axis (): CPU2 operation fault1. Operational malfunction of the drive firmware; 2. Internal malfunction of the drive.1. Upgrade the drive firmware; 2. Replace the drive.
35420Axis(): CPU1 memory fault1. Operational malfunction of the drive firmware; 2. Internal malfunction of the drive.1. Upgrade the drive firmware; 2. Replace the drive.
35421Axis (): CPU2 memory fault1. Operational malfunction of the drive firmware; 2. Internal malfunction of the drive.1. Upgrade the drive firmware; 2. Replace the drive.
35422Axis (): CPU memory conflict1. Operational malfunction of the drive firmware; 2. Internal malfunction of the drive.1. Upgrade the drive firmware; 2. Replace the drive.
35423Axis (): Magnetic pole positioning error1. The setting value of the rotor position compensation angle of the motor is inconsistent with the detected value; 2. The detection sensitivity for rotor positioning fault is too low; 3. The setting of static balance torque compensation value is inconsistent with the actual load; 4. The wrong wiring of the motor leads to the change of rotor phase angle; 5. The motor malfunction leads to the change of rotor phase angle; 6. The gravity load causes rotation of the motor at the instant when the servo is enabled, and the speed exceeds the threshold of rotor positioning fault detection sensitivity.1. Re-detect the motor rotor position compensation angle and set it correctly; 2. Appropriately increase the sensitivity setting value of rotor positioning fault detection; 3. Set the static balance torque compensation value correctly according to the actual load; 4. Correct wiring, and re-detect the motor rotor position compensation angle; 5. Replace the motor; 6. Set the static balance torque compensation value correctly according to the actual load.
35424Axis (): Abnormal encoder data1. Abnormal encoder data; 2. Encoder cable sequence error or poor contact; 3. Abnormal encoder data due to noise interference.1. Replace the motor or encoder; 2. Correct the wiring sequence or reinforce the wiring; 3. Improve the electromagnetic environment of equipment by standardizing wiring and routing, increasing the cross-sectional area of grounding wire and adding magnetic rings.
35425Axis (): Abnormal Encoder communication1. Abnormal encoder data; 2. Encoder cable sequence error or poor contact; 3. Abnormal encoder data due to noise interference.1. Replace the motor or encoder; 2. Correct the wiring sequence or reinforce the wiring; 3. Improve the electromagnetic environment of equipment by standardizing wiring and routing, increasing the cross-sectional area of grounding wire and adding magnetic rings.
35426Axis (): Encoder communication timeout1. Abnormal encoder data; 2. Encoder cable sequence error or poor contact; 3. Abnormal encoder data due to noise interference.1. Replace the motor or encoder; 2. Correct the wiring sequence or reinforce the wiring; 3. Improve the electromagnetic environment of equipment by standardizing wiring and routing, increasing the cross-sectional area of grounding wire and adding magnetic rings.
35427Axis (): Encoder internal malfunction 1Abnormal encoder internal stateSoft reset of the encoder after zeroing or restart the drive
35428Axis (): Malfunction of other axes of the drive1. Malfunction of other axes; 2. Abnormal internal circuit of the drive1. Check other axes and reset those reported fault to ensure that other axes are free of fault, and such fault can be prohibited from detection by the parameter 0x2094; 2. Replace the drive
35429Axis (): Control encoder over-speed1. The encoder position feedback value variates excessively in a position sampling period, and exceeds 1.3 times of the highest speed of the motor; 2. Encoder malfunction; 3. Abnormal encoder data due to noise interference.1. Optimize motor parameters and control parameters. The maximum motor set speed is usually not less than the actual maximum motor speed; 2. Check the encoder settings and wiring; 3. Improve the electromagnetic environment of equipment by standardizing wiring and routing, increasing the cross-sectional area of grounding wire and adding magnetic ring.
35430Axis (): Drive continuous overload1. Excessive motor load or acceleration/deceleration time set is too short; 2. Actual mechanical load is excessive or it's jammed; 3. The motor's band-type brake is not released; 4. An exception in the motor or motor's band-type brake; 5. Internal malfunction of the drive.1. Reduce the actual mechanical load or increase the motor acceleration and deceleration time; 2. Check the transmission mode of mechanical load to ensure that there is no jamming; 3. Check the band-type brake wiring and ensure that it is reliable; 4. Replace the motor; 5. Replace the drive.
35431Axis (): Drive output phase loss1. The line break and poor wiring occur in the U, V and W outputs of the drive; 2. The motor impedance is excessive; 3. The internal current sampling circuit of the drive is abnormal.1. Check the wiring of motor U, V and W and ensure that it is reliable; 2. Replace the motor or turn off the drive output phase loss detection function; 3. Replace the drive.
35432Axis() Motor stall1. Unreasonable setting of drive regulator parameters leads to large speed tracking overshoot; 2. Abnormal encoder data due to electromagnetic and noise interference; 3. Abnormal encoder data due to damaged encoder; 4. Abnormal internal circuit of the drive.1. Optimize regulator parameters; 2. Improve the electromagnetic environment of equipment by standardizing wiring and routing, increasing the cross-sectional area of grounding wire and adding magnetic ring; 3. Replace the motor or encoder; 4. Replace the drive.
35433Axis () Excessive current tracking error1. Unreasonable setting of drive regulator parameters leads to large speed tracking overshoot; 2. Abnormal encoder data due to electromagnetic and noise interference; 3. Abnormal encoder data due to damaged motor; 4. Abnormal internal circuit of the drive.1. Optimize regulator parameters; 2. Improve the electromagnetic environment of equipment by standardizing wiring and routing, increasing the cross-sectional area of grounding wire and adding magnetic ring; 3. Replace the motor; 4. Replace the drive.
35434Axis () Abnormal target position value1. In CSP mode, the difference between the target position value and the actual position value exceeds the threshold set for the position tracking error when the servo is enabled; 2. In CSP mode, the target trajectory acceleration exceeds the threshold set for the maximum acceleration when the motor is running, and the difference between the target position value and the actual position value exceeds the threshold set for the position tracking error.1. Check and confirm that the target position value and the actual position value are normal, so that the difference does not exceed the set threshold for the position tracking error; 2. Check and confirm that the target position value is normal, or appropriately increase the set threshold for maximum acceleration or the position tracking error.
35435Axis () Encoder power-on data overflowThe feedback value of the position during drive power-up is beyond the range allowed by the encoder.Soft reset the encoder after zeroing or restart the drive.
35436Axis () Target position value overflowTarget position value exceeds the maximum permissible range when unlimited position control is disabled in the position mode.Perform the encoder multiturn zeroing operation, or enable the unlimited position control mode, or work in a non-position mode (torque mode or speed mode).
35437Axis (): Abnormal motor's band-type brake1. There is an exception in the motor band-type brake, and braking fails; 2. The servo is suddenly turned off when the motor is running at high velocity and the braking time is too long; 3. The set braking time for the motor band-type brake is shorter than the actual braking time; 4. The detection sensitivity for rotor positioning fault is too low.1. Replace the motor; 2. Optimize the process logic control to avoid sudden servo OFF when running at high speed; 3. The braking time set for the motor band-type brake should be not less than the actual braking time; 4. Properly increase the detection sensitivity for rotor positioning fault.
35438Axis (): Control power supply under-voltage1. The 24V control power supply is abnormal; 2. The wiring of the 24V control power supply is incorrect or poorly connected; 3. The load of the 24V control power supply is excessive; 4. The internal circuit of the drive is abnormal.1. Replace the 24V control power supply; 2. Check the wiring of the 24V control power supply and ensure that it is reliable; 3. Check the load of the 24V control power supply and ensure that the capacity of the 24V control power supply can meet the load consumption under all working conditions; 4. Replace the drive.
35439Axis () STO1 triggeredSTO1 is triggered or is poorly wired.Check the STO wiring to ensure that it is reliable and not triggered.
35440Axis () STO2 triggeredSTO2 is triggered or is poorly wired.Check the STO wiring to ensure that it is reliable and not triggered.
35441Axis () Positive hardware limit switch triggeredOne-way motion to the mechanical limit causes hardware limit triggering.The fault can be cleared directly through motion in the opposite direction until the mechanical limit is restored. Be careful to plan the position so that the hardware limit is not exceeded.
35442Axis () Negative hardware limit switch triggeredOne-way motion to the mechanical limit causes hardware limit triggering.The fault can be cleared directly through motion in the opposite direction until the mechanical limit is restored. Be careful to plan the position so that the hardware limit is not exceeded.
35443Axis (): The Motor exceeds the velocity limit1. The actual motor speed feedback value exceeds 1.1 times the maximum motor speed; 2. The encoder is abnormal.1. Optimize motor parameters and control parameters. The maximum motor speed set is usually not less than the actual maximum motor speed; 2. Check the encoder settings and wiring.
35444Axis () Emergency stop input switch triggeredEmergency stop input switch is triggered or is poorly wired.Check the emergency stop input switch wiring to ensure that it is reliable and not triggered.
35445Axis () Torque monitoring saturation fault1. The motor load is excessive and it exceeds the torque monitoring alarm threshold; 2. The torque saturation monitoring threshold set is too low.1. Reduce the actual mechanical load of the motor or increase the motor acceleration and deceleration time; 2. Increase the torque saturation monitoring threshold set. When the threshold is set to 0, the fault will not be detected.
35446Axis (): Excessive velocity tracking error1. Excessive motor load; 2. Inappropriate control parameters; 3. Abnormal release action of the band-type brake; 4. Too small threshold or time duration for judging excessive velocity tracking error.1. Reduce the actual mechanical load of the motor to ensure that the machinery is not jammed; 2. Optimize the control parameters and enhance the corresponding performance of the servo; 3. Check the line of the band-type brake of the motor to ensure normal action of the band-type brake; 4. Appropriately increase the threshold or time duration for judging excessive velocity tracking error.
35447Axis () Short circuit of the drive 21. The U/V/W output cable of the drive is short-circuited, or short-circuited to ground; 2. The U/V/W output cable of the motor is short-circuited, or short-circuited to ground; 3. An internal cable of the drive is short-circuited, or short-circuited to ground; 4. False alarm is caused because the drive is interfered1. If a short circuit occurs between the cable's UVW phases, or between the cable's U/V/W and grounding, dispose or replace the cable; 2. If a short circuit occurs between the motor's UVW phases, or between the motor's U/V/W cable and grounding, replace the motor; 3. If faults still occur after disconnecting the drive U/V/W output wiring, replace the drive; 4. Improve the electromagnetic environment of the equipment by standardizing wiring and cabling, increasing the cross-sectional area of the grounding wire and adding magnetic rings.
35448Axis (): Origin searching failed1. Unreasonable parameter setting of origin searching; 2. The motor is already in the limit switch trigger state when the origin searching is activated; 3. Switch to non-HM mode during origin searching.1. Set correct parameters of origin searching; 2. The sure that the motor is not in the limit switch trigger state when the origin searching is activated; 3. Do not switch to non-HM mode during origin searching.
35449Axis () EtherCAT process data errorThe PDO set value is beyond the target's allowable range.The PDO set value is within the target's allowable range.
35450Axis () Illegal EtherCAT bus instructionEtherCAT communication state machine is incorrectly matched with the control word time sequence.The host computer correctly handles the EtherCAT communication state computer and control word time sequence.
35451Axis () EtherCAT communication cycle error1. EtherCAT communication cycle is shorter than the servo control cycle; 2. EtherCAT communication period is not set to an integer power of 2 for 250 μs.1. Adjust the EtherCAT communication cycle or the servo control cycle so that the communication cycle is longer than the servo control cycle; 2. Set the EtherCAT communication cycle to an integer power of 2 for 250 μs.
35452Axis (): Operation error of position planning1. Target position value cache overrun when running PP mode under EtherCAT control; 2. Internal malfunction of the drive.1. Optimize the EtherCAT master control process to reduce the number of target position value caches, typically no more than 4; 2. Replace the drive.
35453Axis () Illegal EtherCAT synchronization mode1. EtherCAT communication DC mode is incorrectly configured; 2. DC mode is not activated for EtherCAT communication.1. Configure EtherCAT communication DC mode correctly; 2. Activate the DC mode for EtherCAT communication.
35454Axis () Target position value beyond the set rangeThe target position value exceeds the set range when the unlimited position control mode is enabled or disabled.Set the target position value to a value between the lower limit and the upper limit of the position range or use the normal unlimited position mode.
35455Axis () Motor U–phase instantaneous overload1. Excessive motor load; 2. Over-short acceleration and deceleration time durations of the motor; 3. Incorrect setting of motor parameters; 4. Abnormal release action of the band-type brake; 5. Wrong motor model with a smaller power (such as the high-power drive loaded with the small-power motor runs at full load and high speed for a long time); 6. Abnormal internal current sampling circuit of the drive; 7. The fast motor overload protection threshold and protection time duration set are too small.1. Reduce the actual mechanical load of the motor to ensure that the machinery is not jammed; 2. Prolong the acceleration and deceleration time durations during motor operation; 3. Check the motor parameters to ensure that the motor parameters are set correctly (such as the rated current and thermal time constant of the motor); 4. Check the line of the band-type brake of the motor to ensure normal action of the band-type brake; 5. Change to a high–capacity motor; 6. Replace the drive; 7. Increase the fast motor overload protection threshold and protection time duration appropriately.
35456Axis () Motor V–phase instantaneous overload1. Excessive motor load; 2. Over-short acceleration and deceleration time durations of the motor; 3. Incorrect setting of motor parameters; 4. Abnormal release action of the band-type brake; 5. Wrong motor model with a smaller power (such as the high-power drive loaded with the small-power motor runs at full load and high speed for a long time); 6. Abnormal internal current sampling circuit of the drive; 7. The fast motor overload protection threshold and protection time duration set are too small.1. Reduce the actual mechanical load of the motor to ensure that the machinery is not jammed; 2. Prolong the acceleration and deceleration time durations during motor operation; 3. Check the motor parameters to ensure that the motor parameters are set correctly (such as the rated current and thermal time constant of the motor); 4. Check the line of the band-type brake of the motor to ensure normal action of the band-type brake; 5. Change to a high–capacity motor; 6. Replace the drive; 7. Increase the fast motor overload protection threshold and protection time duration appropriately.
35457Axis () Motor W–phase instantaneous overload1. Excessive motor load; 2. Over-short acceleration and deceleration time durations of the motor; 3. Incorrect setting of motor parameters; 4. Abnormal release action of the band-type brake; 5. Wrong motor model with a smaller power (such as the high-power drive loaded with the small-power motor runs at full load and high speed for a long time); 6. Abnormal internal current sampling circuit of the drive; 7. The fast motor overload protection threshold and protection time duration set are too small.1. Reduce the actual mechanical load of the motor to ensure that the machinery is not jammed; 2. Prolong the acceleration and deceleration time durations during motor operation; 3. Check the motor parameters to ensure that the motor parameters are set correctly (such as the rated current and thermal time constant of the motor); 4. Check the line of the band-type brake of the motor to ensure normal action of the band-type brake; 5. Change to a high–capacity motor; 6. Replace the drive; 7. Increase the fast motor overload protection threshold and protection time duration appropriately.
35458Axis () Dynamic braking overloadThe interval between two adjacent dynamic braking stops is too short when the motor is running.If there is a dynamic braking stop when the motor is running, the interval must be at least 360*actual speed²/rated speed² (s).
35459Axis () Internal malfunction of the driveInternal malfunction of the drive.Replace the drive.
35460Axis () Abnormal limit switchThe limit switch is triggered or is poorly wired.Check limit switch wiring to ensure that it is reliable and not triggered.
35461Axis () Abnormal communication of the EtherCAT bus1. The EtherCAT communication is interfered; 2. Disconnection or poor contact of EtherCAT network cables; 3. Insufficient real-time performance of the host computer; 4. Mismatch between the underlying DC synchronization mechanism of the EtherCAT master of the host computer and the drive requirements; 5. Internal malfunction of the drive.1. Improve the electromagnetic environment of equipment by standardizing wiring and routing, increasing the cross-sectional area of grounding wire and adding magnetic ring; 2. Check the connection of EtherCAT network cables to ensure reliable connection; 3. Change to the host computer with stronger real-time performance, or extend the EtherCAT communication cycle, or increase the timeout detection sensitivity; 4. Modify the underlying DC synchronization mechanism of the EtherCAT master of the host computer to ensure that the SM2 event of the host computer is at least 125 μs ahead of the DC synchronization signal; 5. Replace the drive.
35462Axis () Interface encoder resolution changeInterface encoder resolution is changed.Re-power on or perform the soft reset of the drive.
35463Axis () Encoder overheating1. The actual encoder temperature is too high; 2. The encoder is abnormal.1. Bring down the encoder operating temperature to within the allowable range; 2. Replace the motor or encoder.
35464Axis ():Encoder battery under-voltage fault1. Encoder battery voltage too low; 2. The encoder battery is poorly wired.1. Replace the encoder battery; 2. Check and handle the battery wiring to ensure that the battery wiring is correct and secure.
35465Axis (): Control mode setting errorWhen the servo is ON, the control mode set is not supported by the drive, such as NM, VL or IP, or the control mode is set to PV or PT under EtherCAT control.When the servo is ON, set the control mode supported by the drive.
35466Axis (): Excessive deviation of the power-on positionWhen the drive is powered on, the position is different from the last position saved during power-off and it exceeds the set threshold.Check whether the mechanical position has been changed. Clear the alert after confirming that the mechanical zero point is normal.
35467Axis () Abnormal encoder acceleration1. Abnormal encoder data; 2. Encoder cable sequence error or poor contact; 3. Abnormal encoder data due to noise interference.1. Replace the motor or encoder; 2. Correct the wiring sequence or reinforce the wiring; 3. Improve the electromagnetic environment of equipment by standardizing wiring and routing, increasing the cross-sectional area of grounding wire and adding magnetic rings.
35468Axis () Motor rotor locked1. The mechanical load leads to jamming or locking; 2. The motor's band-type brake is not released.1. Check and handle the mechanical load transmission to ensure that there is no jamming or locking; 2. Check and handle the band-type brake circuit to ensure the band-type brake can be released properly.
35469Axis () EEPROM data write errorInternal malfunction of the drive.Replace the drive.
35470Axis () EEPROM data read errorInternal malfunction of the drive.Replace the drive.
35471Axis () Band-type brake control circuit error1. The motor band-type brake is short circuited or poorly wired; 2. There is a short circuit or poor wiring inside the band-type brake; 3. Internal malfunction of the drive.1. Check the wiring of the drive's band-type brake output and ensure it is correct and reliable; 2. Replace the motor; 3. Replace the drive.
35472Axis () CPU1 overload1. The drive operation is subject to noise interference; 2. Excessive data collected by the commissioning software; 3. The internal circuit of the drive is abnormal.1. Improve the electromagnetic environment of equipment by standardizing wiring and routing, increasing the cross-sectional area of grounding wire and adding magnetic ring; 2. Close some of the data collection channels of the commissioning software; 3. Replace the drive.
35473Axis () CPU2 overload1. The drive operation is subject to noise interference; 2. Excessive data collected by the commissioning software; 3. The internal circuit of the drive is abnormal.1. Improve the electromagnetic environment of equipment by standardizing wiring and routing, increasing the cross-sectional area of grounding wire and adding magnetic ring; 2. Close some of the data collection channels of the commissioning software; 3. Replace the drive.
35474Axis () CPU1 handshake failed1. Operational malfunction of the drive firmware; 2. Internal malfunction of the drive.1. Upgrade the drive firmware; 2. Replace the drive.
35475Axis () DriveMaster communication timeout1. The drive's commissioning cable is disconnected or poorly wired; 2. The drive's commissioning serial communication is interfered.1. Check the wiring of the drive commissioning cable and ensure a reliable connection 2. Improve the electromagnetic environment of the equipment by using isolated serial port commissioning cable, standardizing wiring and cabling, increasing the cross-sectional area of the grounding wire, and adding magnetic rings.
35476Axis () ESC configuration EEPROM errorInternal malfunction of the drive.Replace the drive.
35477Axis () ESC internal access errorInternal malfunction of the drive.Replace the drive.
35478Axis () Servo enabling not ready1. When the servo is ON, the drive is in actual motor and virtual encoder mode; 2. When the servo is ON, the encoder communication is disconnected; 3. When the servo is ON, the motor speed is higher than 30rpm; 4. When the servo is ON, the STO status is not lifted; 5. When the servo is ON, the DC bus voltage is too low and the charging relay is not closed; 6. When the servo is ON, the dynamic braking status is not lifted; 7. Internal error of drive.1. Check the drive motor mode to ensure that the drive is in actual motor and actual encoder mode when the servo is ON; 2. Check the encoder communication status to ensure that the encoder communication is normal when the servo is ON; 3. Check the motor operation status to ensure that the motor is still when the servo is ON; 4. Check the STO status to ensure that the STO status ends when the servo is ON; 5. Check the DC bus voltage status to ensure that the DC bus voltage meets the enable threshold when the servo is ON and the charging relay is closed; 6. Check the dynamic braking status to ensure that the dynamic braking status ends when the servo is ON; 7. Replace the drive.
35479Axis () CPU2 handshake failed1. Operational malfunction of the drive firmware; 2. Internal malfunction of the drive.1. Upgrade the drive firmware; 2. Replace the drive.
35480Axis () CPU1 main task timeout1. The drive operation is subject to noise interference; 2. Excessive data collected by the commissioning software; 3. The internal circuit of the drive is abnormal.1. Improve the electromagnetic environment of equipment by standardizing wiring and routing, increasing the cross-sectional area of grounding wire, and adding magnetic ring; 2. Close some of the data collection channels of the commissioning software.
35481Axis () DC bus charging relay errorCharging relay inside drive malfunctions.Replace the drive.
35482Axis () CPU internal error1. Operational malfunction of the drive firmware; 2. Internal malfunction of the drive.1. Upgrade the drive firmware; 2. Replace the drive.
35483Axis () Actual position value overflowActual position value exceeds the maximum permissible range when unlimited position control is disabled in the position mode.Perform the encoder multiturn zeroing operation, or enable the unlimited position control mode, or work in a non-position mode (torque mode or speed mode).
35484Axis () Encoder internal error 2Encoder internal status error.Soft reset the encoder after zeroing or restart the drive.
35485Axis () Encoder internal error 3Encoder internal status error.Soft reset the encoder after zeroing or restart the drive.
35486Axis () Excessive position 2 following error1. Excessive motor load; 2. Inappropriate control parameters; 3. Abnormal release action of the band-type brake; 4. Too small threshold or time duration for judging excessive position 2 following error.1. Reduce the actual mechanical load of the motor to ensure that the machinery is not jammed; 2. Optimize the control parameters and enhance the corresponding performance of the servo; 3. Check the line of the band-type brake of the motor to ensure normal action of the band-type brake; 4. Appropriately increase the threshold or time duration for judging excessive position 2 following error.
35487Axis () STO wiring errorSTO1/STO2 triggered or poorly wired.Check the STO wiring to ensure that it is reliable and not triggered.
35488Axis () Excessive velocity 2 following error1. Excessive motor load; 2. Inappropriate control parameters; 3. Abnormal release action of the band-type brake; 4. Too small threshold or time duration for judging excessive velocity 2 following error.1. Reduce the actual mechanical load of the motor to ensure that the machinery is not jammed; 2. Optimize the control parameters and enhance the corresponding performance of the servo; 3. Check the line of the band-type brake of the motor to ensure normal action of the band-type brake; 4. Appropriately increase the threshold or time duration for judging excessive velocity 2 following error.
35489Axis () Abnormal main power input1. The power input power supply of the driver is poorly wired; 2. The driver power circuit is set as three-phase input, but the actual power supply input is single-phase; 3. Electronic transformer is used in the front end, and the harmonic of electronic transformer is abnormal.1. Check the power input power wiring of the driver and ensure that the wiring is reliable; 2. Correctly set the driver power circuit, and the set value is consistent with the actual power supply input; 3. Wire according to the transformer manual, and install a filter at the front end of the servo driver if necessary.
35490Axis () Motor band brake disconnection1. The motor holding brake is not connected or has poor contact; 2. Motor holding brake is abnormal; 3. Drive internal exception.1. Check and handle the motor band brake wiring to ensure that the wiring is correct and firm; 2. Replace the motor; 3. Replace the drive.
35491Axis () Coprocessor communication exception1. Encoder cable sequence error or poor contact; 2. Encoder data is abnormal due to noise interference.1. Correct the wiring sequence or reinforce the wiring; 2. Improve the electromagnetic environment of equipment by standardizing wiring and wiring, increasing the sectional area of grounding wire, and adding magnetic ring.
35492Axis () Abnormal change of encoder AB signal1. Encoder cable sequence error or poor contact; 2. Encoder data is abnormal due to noise interference.1. Correct the wiring sequence or reinforce the wiring; 2. Improve the electromagnetic environment of equipment by standardizing wiring and wiring, increasing the sectional area of grounding wire, and adding magnetic ring.
35493Axis () Rectifier module overheating1. Abnormal temperature sampling circuit inside the driver; 2. Driver operating environment temperature is outside the allowable operating range.1. Replace the drive; 2. Decrease the ambient temperature, for example, improve the radiation conditions of cabinets.
35494Axis () Radiator overheating1. Abnormal temperature sampling circuit inside the driver; 2. Driver operating environment temperature is outside the allowable operating range.1. Replace the drive; 2. Decrease the ambient temperature, for example, improve the radiation conditions of cabinets.
35495Axis () Motor overheating1. The motor load is too large; 2. The operating environment temperature of the motor is too high to be allowed. 3. Error in setting thermocouple resistance value for motor overheat protection; 4. abnormal temperature sensor of the motor; 5. Drive internal exception.1. Reduce the actual mechanical load of the motor to ensure that the machine is free from jamming; 2. Enhance the heat dissipation of the motor to ensure that the operating environment temperature is within the allowable range; 3. Correctly set the setting value of thermocouple resistance for motor overheat protection; 4. Replace the motor; 5. Replace the drive.
35496Axis () Incremental Encoder Z Signal Exception1. The encoder's own data is abnormal; 2. Wrong encoder cable sequence or poor contact; 3. Abnormal encoder data due to noise interference.1. Replace the motor or encoder; 2. Correct the wiring sequence or reinforce the wiring; 3. Improve the electromagnetic environment of the equipment by standardizing wiring and wiring, increasing cross-section area of grounding wire, and adding magnetic rings..
35497Axis () Abnormal energy consumption brake circuitEnergy consumption brake selection for setting the server parameters is inconsistent with the actual connection of the energy consumption brake resistance.Correctly set the selected servo parameters for energy consumption braking to match the actual wiring of the energy consumption braking resistance.
35498Axis () CPU Overheat1. Abnormal temperature sampling circuit inside the driver; 2. Driver operating environment temperature is outside the allowable operating range.1. Replace the drive; 2. Decrease the ambient temperature, for example, improve the radiation conditions of cabinets.
35499Axis () Power failure of main power supply1. When the driver servo is ON, the power supply fails; 2. Abnormal power failure detection of main power supply due to noise interference; 3. The servo parameter main power failure detection time is set too small.1. Check the power supply and wiring of the driver to ensure that the power supply is normal and the connection is reliable; 2. Improve the electromagnetic environment of equipment by standardizing wiring and wiring, increasing the sectional area of grounding wire, and adding magnetic ring; 3. Properly increase the setting value of servo parameter main power failure detection time.
35500Axis () Abnormal diagnosis of STO1 circuit1. STO1 triggering or poor wiring; 2. Driver internal exception.1. Check the STO wiring to ensure that it is reliable and not in the triggered state; 2. Replace the drive.
35501Axis () Abnormal diagnosis of STO2 circuit1. STO2 triggering or poor wiring; 2. Driver internal exception.1. Check the STO wiring to ensure that it is reliable and not in the triggered state; 2. Replace the drive.
35502Axis () Hall signal is abnormal1. Hall sensor signal is abnormal; 2. Hall sensor wiring sequence error or poor contact; 3. Hall signal is abnormal due to noise interference.1. Replace the motor or Hall sensor, or prohibit Hall signal detection; 2. Correct the wiring sequence or reinforce the wiring; 3. Improve the electromagnetic environment of equipment by standardizing wiring and wiring, increasing the sectional area of grounding wire, and adding magnetic ring..
35503Axis () Abnormity of encoder AB signal under phase1. Hall sensor or AB encoder signal is abnormal; 2. Hall sensor or AB encoder wiring sequence error or poor contact; 3. Hall or AB encoder signal is abnormal due to noise interference.1. Replace the motor or hall sensor and encoder; 2. Correct the wiring sequence or reinforce the wiring; 3. Improve the electromagnetic environment of equipment by standardizing wiring and wiring, increasing the sectional area of grounding wire, and adding magnetic ring.
35504Axis () Drive internal exception 2Drive internal exception.Replace driver.
35505The robot cfg is incorrect and the robot is not allowed to use it. Please use the correct robot cfgThe robot cfg is incorrect.Use the correct robot cfg.
35506The soft limit exceeds the hard limit. Please modify the correct soft limit and restart the robotThe soft limit exceeds the hard limit.The soft limit exceeds the hard limit.
35507The configuration file has STOP_STO_TIME field and stop1 time greater than 760ms, but the firmware version of the security board is too lower. Please upgrade the firmware of the security boardThe configuration file has STOP_STO_TIME field and stop1 time greater than 760ms, but the firmware version of the security board is too lowerUpgrade the firmware of the security board
35508Failed to set the value of STOP_TIME to Saftey boardHardware failureCheck hardware
35509Failed to set the value of STOP_TIME!The value of STOP_TIME is too largeThe value of STOP0_TIME should be < manu STO_TIME-30,The value of STOP1_TIME should be < auto STO_TIME-60.
35600Axis () STO Switch Not Activated (0x3181)Robot enabling handle not effectivePress manual enable handle; Reconnect STO cables; Replace STO lines; Replace servo drive
35601Axis () Brake Voltage Overlimit (0x3182)Hardware brake voltage output exceeds standardVerify firmware & parameter versions; Replace drive board
35602Axis () Drive Module Overheat Alarm (0x4310)Joint temperature exceeds operational limitsPerform cooldown process; Update firmware; Replace servo drive
35603Axis () Encoder 1 Fault (0x737C)Motor-side encoder malfunctionFirmware validation; Recalibration; Replace joint assembly
35604Axis () Encoder 2 Fault (0x737F)Joint-side encoder anomalyFirmware verification; Recalibration; Replace joint
35605Axis () Encoder Signal Noise (0x7376)Line noise/drive board failure or EMI interferenceInspect connections; Replace drive board; Verify firmware
35606Axis () Phase A Overcurrent (0x2310)Phase A current exceeding thresholdCheck: Cable connections/Motor alignment/Brake status/Load parameters
35607Axis () Phase B Overcurrent (0x2311)Phase B current exceeding thresholdCheck: Cable terminations/Position calibration/Brake function/Load profile
35608Axis () Phase C Overcurrent (0x2312)Phase C current surpassing limitVerify: Wiring integrity/Motor offset/Brake operation/Load conditions
35609Axis () IGBT Overcurrent Protection (0xFFA1)Current exceeding preset thresholdInspect: Load conditions/Deceleration parameters/Mechanical resistance
35610Axis () Motor Overload (0xFF81)Excessive torque or motor stallCheck: Wiring/Acceleration settings/Winding resistance/Brake condition
35611Axis () Zero Current Alert (0xFFA0)Current detection anomaly in disabled stateUpdate firmware/parameters; Replace drive unit
35612Axis () DC Bus Undervoltage (0x3220)Insufficient bus voltage supplyVerify power input; Replace drive/power boards
35613Axis () DC Bus Overvoltage (0x3210)Voltage surge/Regenerative deceleration anomalyInspect power supply; Adjust deceleration profile
35614Axis () Position Deviation Alert (0x8611)Tracking error exceeding thresholdVerify connections/Hardware integrity/Command rationality
35615Axis () Master-Slave Disconnection (0x7500)EtherCAT communication failureCheck cabling; Validate firmware compatibility
35616Axis () Electrical Angle Calibration Error (0x5153)Wiring/parameter configuration errorInspect: Cable routing/Firmware version/Calibration parameters
35617Axis () High-Side Multi-Turn Error (0x5151)Firmware mismatch/EEPROM corruptionUpgrade firmware; Replace drive controller
35618Axis () Low-Side Multi-Turn Error (0x5152)Firmware mismatch/EEPROM corruptionUpgrade firmware; Replace drive controller
35619RSC firmware version mismatch with the controller version will disable RSC-related safety restriction functions‌RSC firmware version is incompatible with the controller versionCheck the RSC firmware version and upgrade it to the latest compatible version
35620Axis () Motor short-circuit (overcurrent) protection(0x2400)1.Excessive current triggers the current protection mechanism1.Check for any severe impacts; 2.Inspect for potential phase-to-phase short circuits in the motor
35621Axis () Power Board Bus Voltage Too Low(0x6200)1. Power cable disconnected or insufficient supply voltage; 2. Power board hardware failure;1. Check power connection; 2. Inspect servo driver hardware;
35622Axis () Power Board Bus Voltage Too High(0x6201)1. Incorrect power cable polarity causing overvoltage; 2. Power board hardware failure;1. Verify power input configuration; 2. Inspect power board components;
35623Axis () Power Board Main Relay Feedback Error(0x6202)1. Power board hardware malfunction;1. Check power board circuitry;
35624Axis () Power Board Leakage Current Overload(0x6203)1. Short circuit in body wiring harness or power cables; 2. Power board hardware failure;1. Inspect cable insulation integrity; 2. Test power board functionality;
35625Axis () Power Board Brake Overload(0x6205)1. Brake circuit open; 2. Brake mechanical failure; 3. Power board or servo driver module defect;1. Check wiring continuity; 2. Test brake mechanism; 3. Diagnose driver module;
35626Axis () Power Board User Power Overload(0x6206)1. External device wiring error or short circuit; 2. Exceeding rated power capacity;1. Verify peripheral connections; 2. Confirm device specifications;
35627Axis () Power Board EEPROM Write Error(0x6207)1. EEPROM component failure;1. Replace power board;
35628Axis () Power Board EEPROM Read Error(0x6300)1. EEPROM component failure;1. Replace power board;
35629Axis () Power Board Power Relay Error(0x6301)1. Power board hardware malfunction;1. Inspect relay contacts;
35630Axis () Power Board CR35 Heat Exchanger Fault(0x6302)1. Heat exchanger wiring short; 2. Power board failure;1. Check thermal management system wiring; 2. Test power board;
35631Axis () Power Board 48V Undervoltage(0x6306)1. Joint resistance abnormally high; 2. Power supply misconfiguration;1. Check joint mechanical operation; 2. Verify power input;
35632Axis () Power Board 48V Overcurrent(0x6307)1. Excessive mechanical load or acceleration;1. Optimize motion parameters;
35633Axis () Power Board CR35 Bleeder MOS Fault(0x6400)1. Power board component failure;1. Replace power board;
35634Axis () Power Board CR35 Bleeder Overcurrent(0x6401)1. Bleeder resistor failure;1. Replace bleeder module;
35635Axis () Power Board CR35 Bleeder MOS Short(0x6402)1. Power board hardware failure;1. Replace power board;
35636Axis () Power Board Bleeder I2T Fault(0x6403)1. Power board thermal overload;1. Check cooling system;
35637Axis () Power Board Communication Failure(0x6450)1. Power board hardware defect;1. Replace communication module;
35638Axis () FPGA Watchdog Fault(0x3200)1. Servo driver control board failure;1. Replace control board;
35639Axis () FPGA Leakage Current Alert(0x3201)1. Ground fault in cabinet wiring;1. Perform insulation resistance test;
35640Axis () Encoder Interpolation Error(0x7372)1. Verify encoder hardware integrity;
35641Axis () Encoder Multi-turn Value Error(0x7373)1. Encoder battery disconnection; 2. Low battery voltage;1. Check battery connectors; 2. Measure battery voltage;
35642Axis () Encoder Data Anomaly(0x7374)1. Verify encoder cable routing; 2. Check encoder magnetic gap;
35643Axis () Encoder Communication Failure(0x7375)1. Encoder cable disconnection;1. Re-seat encoder connectors;
35644Axis () High-Speed Encoder Overspeed(0x7376)1. Loose encoder connections; 2. Magnetic gap deviation;1. Secure cable terminations; 2. Adjust encoder alignment;
35645Axis () Sensor CRC Error(0x6500)1. Sensor data frame CRC mismatch;1. Inspect sensor wiring;
35646Axis () Sensor Null Data Frame(0x6501)1. All-zero data packets received;1. Check sensor power supply;
35647Axis () Sensor Speed Exceedance(0x6502)1. Significant deviation between calculated and actual joint speed;1. Verify sensor installation; 2. Calibrate speed parameters;
35648Axis()Sensor Zero Calibration Error(0x6503)1. Zero calibration data mismatch;1. Recalibrate sensor;
35649Axis()Reducer Slippage Error(0x7370)1. After startup, slippage was detected in the joint reducer, potentially accompanied by loss of zero reference.1. After manually returning to zero, perform the 'One-Key Write Zero' operation again. After powering off and restarting, recalibrate the zero point.
35650Axis()Encoder slippage fault(0x7371)1. During running, encoder slippage is detected, potentially accompanied by zero-point loss.1. After manually returning to zero, perform the 'One-Key Write Zero' operation again. After powering off and restarting, recalibrate the zero point.
35651Axis()Low-Speed Encoder Overspeed(0x737E)1. During running, abnormal values were detected in the low-speed encoder, with a rate of change far exceeding the motor's maximum set speed.1. Secure cable terminations; 2. Adjust encoder alignment;
35652Axis()Damping Plate Uncalibrated(0x8001)1. Damping Plate Uncalibrated1. Please calibrate the vibration-damping plate and try again.
35653Axis()Relief Status Fault(0x6605)1. Relief status feedback does not match servo release action1. Check whether the drive hardware or wiring is correct.

HMI_Interaction

CodeError MessageCauseSolution
10000Error in parsing HMI request packetIncorrect protocol of HMI request packetPlease check if the HMI and the control system version matches
10001JOG startup failed1. Not in the Manual mode; 2. Robot not powered on; 3. Robot in motion; 4. Not in the Position modePlease make sure that the robot is in the Manual mode and powered on
10002Quick adjustment startup failed1. Not in the Manual mode; 2. Robot not powered on; 3. Robot in motion; 4. Not in the Position modePlease make sure that the robot is in the Manual mode and powered on
10003Mechanical zero calibration failed1. Not in the Manual mode; 2. Robot in motion; 3. Not in the Position modePlease make sure that the robot is in the Manual mode and not in motion
10005Sensor zero calibration failed1. Not in the Manual mode; 2. Robot in motion; 3. The robot is not around the mechanical zero; 4. Not in the Position modeJog the robot to the mechanical zero and make sure that the robot is in the Manual mode and not in motion
10007Failed to reboot the controllerPlease stop the robot motion and the RL program
10008Failed to clear servo encoder alarmServo encoder faultRestart robot. If it's still present, contact ROKAE Technical Support
10010Failed to switch to the Manual modeMode switching is not allowed when the robot is in motion; or the robot is already in the Manual modeStop the motion and try again
10011Failed to switch to the Automatic modeBelow are some possible causes: 1. The robot is in motion; 2. The robot is in emergency stop; 3. Drag is already enabled; 4. Automatic mode is already enabled1. Not in motion; 2. Restore from emergency stop; 3. Drag is disabled
10012Power-on condition check failed. Power-on conditions not met. Reason1. Not in correct operation mode; 2. Robot in emergency stop state; 3. Robot in torque control mode; 4. Shutdown signal received; 5. Servo in critical fault state; 6. Controller initialization incomplete1. Switch to correct operation mode; 2. Reset emergency stop state; 3. Switch robot to position mode; 4. Check servo faults; 5. Wait for controller initialization to complete
10013Power-off failedThe robot is in motion or it is not in the Automatic modeStop the robot motion
10014Failed to enable drag!Drag cannot be enabled in the following cases: 1. Automatic mode; 2. Powered on; 3. Not in the Position mode; 4. In motion; 5. Not executing a routine task; 6. Safety monitoring or safety monitor triggered!Switch to the Manual mode, keep the power off, and switch to the Position Mode, and then try again; or try again after reboot.
10016Failed to disable drag!Wrong operating mode1. If the drag is enabled through RCI, it should be disabled through RCI; 2. Restart the robot and try to recover.
10018Failed to update the virtual wall1.The set area is too small; 2.The robot's current position is outside the set area; 3. Drag mode is not enabled1. Expand the virtual wall boundary; 2. Move the robot end-effector to the set area; 3. Enable the Drag mode
10020New teach pendant connection rejectedTeach pendant connection existsDisconnect existing connection
10021Network connection failure. Socket [] cannot connect to the serverConnection timeout1. Please check the device connection; 2. Please check whether the server is working properly
10022Wrong format of data received by the socketread instructionNetwork error
10023The IP address and port used to create the socket [] are already occupied. Socket creation failedRL program or external communication socket has already used the IP address and port number. Two sockets may not use the same IP address and port numberSet different IP address or port numbers
10024The created socket name is duplicatedThe created socket name is duplicatedChange another socket name
10025The socket fails to receive data1. Network connection error; 2. Server did not send data in time; 3. Wrong terminator; 4. Wrong data type1. Check the network connection; 2. Check whether the server sends data; 3. Check whether the terminator matches; 4. Check the type of data sent
10028SocketRead data length does not match the set lengthThe number of data received does not match the set numberSend the correct number of data
10029Failed to set input in the simulation mode
10030Failed to set DI/AI signal in the simulation mode1. Simulation mode is not activated; 2. The signal does not exist1. Activate the Simulation mode; 2. Check input signal setting
10031Failed to set GI signal in the simulation mode1. Simulation mode is not activated; 2. The signal does not exist; 3. The specified value is outside the signal's representable range.1. Turn on the simulation mode; 2. Check GI signal setting; 3. Verify the signal's configured valu
10032Failed to set DO/AI signal in the simulation mode1.The signal does not exist; 2.DO signal has been set as system output1.Check the output signal setting; 2. Simulation is not bound as the system output signal
10033Failed to set GO signal1. The signal does not exist; 2. The set value is beyond the allowable rangeCheck the GO signal setting
10034Incorrect length of the UDP message receivedUnable to parse for wrong message lengthPlease check the RCI instruction format
10038Failed to open RCI1. The IP address cannot be same as the robot address (192.168.0.160) and local host (127.0.0.1); 2. Wrong format of IP address; 3. Port number already occupied; 4. Robot in motion; 5. Not in the Position mode1. Please set the allowed IP address and port number; 2. Stop the robot motion
10039Failed to close RCI1. Robot in motion; 2. Not in the Position modeStop the robot motion and try to close again
10040Failed to dragThere is a large deviation between the feedback and the model torque, and the drag can not be activated1. Check whether the current Tool setting is consistent with the actual situation and whether the set tool mass center is reasonable; 2. Check the monitoring window to see whether the robot coordinate system and pose consistent with the actual situation; 3. Confirm that the current robot model and RD parameters are consistent with the actual parameters; 4. Try to return to the mechanical zero and zero the sensors before dragging; 5. For more detail, refer to the Drag Fault Troubleshooting Manual
10042Client already disconnected from RCIClient disconnection detectedPlease check the client
10043RCI is not responding. Please check auto and power-on status
10046Failed to update collision detection parameters
10049Load identification failed. The load exceeds Robot's rated loadThe load of installed tool or workpiece exceeds the robot's rated loadUse a tool or workpiece within the robot's rated load range
10050The load identification result failed. Wrong load identification result. Identification result discardedException in sensor torque feedbackCheck the sensor torque
10051Failed to set joint position limit1. The set angle is beyond the robot’s mechanical limit; 2. Not in the Manual mode; 3. Robot in motion; 4. Not in the Position mode1. Switch to the Manual mode and stop the robot motion; 2. Confirm the robot's mechanical limit and set the angle within the range
10055Failed to set servo filter parametersFailed to read servo filter dataRestart the robot. If the issue persists, please contact technical support.
10059This model of controller does not support upgrading to version 3.1 or higher!The command filter for the high-payload model has not been enabled.Keep the controller at the pre-upgrade version. If there are any issues, please contact technical support.
10060Setting of Maximum joint velocity over the limit1. The joint velocity range in the Collaboration mode is 0-15 degrees/s; 2. The maximum axial velocity of each axis cannot be exceeded in the Non-Collaboration modePlease check and set the value within the range
10061Setting of Maximum TCP velocity over the limit1. The TCP velocity range in the Collaboration mode is 0-250; 2. The maximum TCP velocity cannot be exceeded in the Non-Collaboration modePlease check and set the value within the range
10062Setting of Joint torque over the limitThe maximum joint torque of each axis is 3 times of the rated torquePlease check and set the value within the range
10063Drag out of virtual range,virtual wall failureDragging exerts excessive external torque1. Expand the virtual wall boundary; 2. Reduce the drag torque; 3. Increase virtual wall stiffness
10064After leaving the virtual wall then enter the virtual wall again ,the virtual wall takes effect againAfter leaving the virtual wall then enter the virtual wall again ,the virtual wall takes effect againno repair
10065NTP sync time failedNTP service not installed; Failed to sync time with serverInstall NTP service; Make sure NTP server is running
10067Total power over the limitThe maximum power of each axis is the maximum joint torque (Nm) × maximum joint velocity (radians/sec), where: 1. The maximum joint velocity in the Collaboration mode is 15 degrees/s; 2. The maximum axial velocity of each axis cannot be exceeded in the Non-Collaboration modePlease check the parameters and their unit
10068Industrial robots do not support pausing when collision detected for the moment. Please Switch to stopping
10070Enter the safety zone and stop the motion
10071Enter the safety zone and start the Collaboration mode
10072Trigger the Reduced mode and slow down the motion
10073Trigger the secondary Collaboration mode and slow down the motion
10074Exit the Reduced mode
10075Trigger the Reduced mode
10078Trigger limit during RCI operation If the robot is in motion, the power-off protection is activated1. Joint or Cartesian space position over the limit; 2. Joint velocity over the limit; 3. Joint or motor torque over the limit; 4. Large deviation between torque instruction and actual torque; 5. Robot in a singular positionPlease check the torque instruction and the initial status of the robot
10079Force control module protection triggered, exiting force control modeSee the "content"1.Check whether the robot status is normal in force control mode; 2. Configure force control protection parameters appropriately
10080Failed to enable drag: joint position over the limitCurrent position of the robot over the joint position limitJog the robot to a position within the joint position limit
10081socket failed to send dataNetwork failure causeCheck the network problem
10082socket data reception timeoutNetwork failure or code logic error1. Check the code logic; 2. Check whether data is properly received and sent at the other end of the network
10083Connection failed with external communication as a client. Trying to reconnect1. Wrong IP address and port number; 2. Server device not properly started; 3. Abnormal device connection1. Check whether the set IP address and port number are correct; 2. Reopen the server
10084Connection failed with external communication as a server1. Wrong IP address and port number; 2. Server device not properly started; 3. Abnormal device connection1. Set the IP address to blank or 0.0.0.0; 2. The port number cannot be set to 0
10085Socket creation failed. The same name as the external communication nameThe socket in the RL program cannot have the same as external communication socketsUse a name different from those of external communication sockets when creating a socket
10086Socket creation failed. The socket name exceeds 30 bytesSocket name too longShorten the socket name
10087Failed to open the external communicationProcess based on the cause prompt
10089Failed to create socket,the destination address and port of the socket are not allowed to connectthe destination address and port of the socket cannot be configured as the robot's address and used portModify the socket's address or port
10096Failed to set the collision detection trigger actionThe trigger behavior is not supportedPlease modify the trigger behavior
10097DH parameters are saved successfully. Please restart the robot for these parameters to take effect. In this version, only part of the linkage parameters can be modified
10098In this version, only part of the linkage parameters can be modified
10099Failed to save RD parameters. RD parameter changes over the limitRD parameter changes over the limitThe limit range of RD parameter changes is +/- 50
10100The IP address and port used to create the socket [] are already occupied. Socket creation failedRL program or external communication socket has already used the IP address and port number. Two sockets may not use the same IP address and port numberPlease use different IP address or port numbers
10101The ip:port used to create the socket [] are already occupied. Socket creation failedDuplicate or wrong IP address already used by the RL program and external communication socketsChange the Socket to a free IP:PORT of the host or check the network settings
10102Wrong port format used when creating the socket []. Socket creation failedWrong port number already used by the RL program and external communication socketsChange the socket port to a free port number from 0 to 65535
10103SocketSendString failedConnection not established or network errorPlease check the network connection or use a connected socket
10104SocketSendByte failedConnection not established or network errorPlease check the network connection or use a connected socket
10106Rapid motion failed. Not in the Manual modeWrong robot status. Not in the Manual modeSwitching to the Manual mode
10107Rapid motion failed. Program is runningWrong robot status. Program is runningPause the program
10108Rapid motion failed. Robot not powered onWrong robot status. Robot not powered onRobot enables Power On
10109Starting point not set. Error in Home instructionStarting point not set. Error in Home instructionSet the starting point through the Setup > Basic Settings > Quick Adjustment interface
10111Failed to set the calibration angleCalibration angle over the limitSet the angle within the limit
10112Failed to start end-effector quick adjustment. Please select the appropriate adjustment typeEnd adjustment is used for fine-tuning the end-effector pose. Calculation may fail for large-scale end-effector adjustment1. Check the robot’s current pose and tool/work object parameters, and select the appropriate type of end-effector adjustment; 2. The robot is already in the corresponding pose; 3. The specified pose is out of the range of motion; 4. The specified pose may move the robot to a singularity
10114Duplicate serial port names. Please enter againWhen creating a new serial port or modifying the name of a serial port, the name should be different from the system IO, the socket name or existing serial port namesCheck the system IO, socket name and existing serial port names, and re-enter the new serial port name
10116Failed to create the serial port1. Serial port hardware connection disconnected; 2. The serial port socket does not exist1. Please check the serial port hardware connection; 2. Delete the serial port variable from the variable list and recreate one
10117Failed to close the serial port1. Serial port hardware connection disconnected; 2. The serial port socket does not exist1. Please check the serial port hardware connection; 2. Click pptomain and run again
10119Serial port does not existThe serial port does not existPlease create a serial port in the Communication - Serial Port Setting interface
10121Serial port failed to send string1. Serial port hardware connection disconnected; 2. The serial port socket does not exist1. Please check the serial port hardware connection; 2. Delete the serial port variable from the variable list and recreate one, and ensure that the serial port communication is proper and available
10122Serial port failed to read byteData read cannot be converted to byte typePlease check the content sent
10123Serial port failed to send byte1. Serial port hardware connection disconnected; 2. The serial port socket does not exist1. Please check the serial port hardware connection; 2. Delete the serial port variable from the variable list and recreate one, and ensure that the serial port communication is proper and available
10124Serial port failed to clear buffer1. Serial port hardware connection disconnected; 2. The serial port socket does not exist1. Please check the serial port hardware connection; 2. Click pptomain and run again
10125Serial port failed to obtain the buffer length1. Serial port hardware connection disconnected; 2. The serial port socket does not exist1. Please check the serial port hardware connection; 2. Click pptomain and run again
10126serial data reception timeoutNetwork failure or code logic error1. Check the code logic; 2. Check whether data is properly received and sent at the other end of the network
10127serial failed to receive data1. Abnormal serial port connection; 2. Opposite end failed to send data in time; 3. Mismatch of parameters configured for both ends of the serial port1. Check the serial hardware connection; 2. Check whether the opposite end has sent data; 3. Check the parameters configured for both ends of the serial port
10128xDiagnose version too old. Unable to view the dataxDiagnose version too oldCan use xDiagnose version 0.3.8 or above
10129The wait time of the conveyor belt for the work object over the limit1. The conveyor belt stops but the tracking is still on; 2. The photoelectric switch functions abnormally and it cannot capture the work object trigger signal1. Check whether the conveyor belt is moving properly; 2. Check whether the photoelectric switch captures the trigger signal properly
10130When waiting for the work object, there is a work object beyond the startup window. The work object is no longer tracked
10131Work object beyond the working areaWork object beyond the working area. Unable to keep trackingPlease adjust the work object position
10132Conveyor belt speed below the thresholdThe conveyor belt stops moving or the encoder is disconnectedPlease check whether the conveyor belt stops moving or the encoder is disconnected
10133Failed to switch to the hot-swapping modeHot-swapping is not supported by the model, control cabinet or safety board firmware1. Check whether the current robot model is an industrial model with the XBC5 control cabinet or a collaborative CR model; 2. Check whether the robot safety board is a mini board and the firmware is upgraded to 2.0; 3. Check whether the ENI file is correctly configured
10134Failed to switch to the hot-swapping mode1. Safety board failed to switch the status correctly; 2. Communication errorPlease contact the supplier for support
10136Rapid motion failed. Angle over the mechanical limitJoint angle over the mechanical limitModify the angle value and make sure it is within the mechanical limit
10137Work object on the conveyor belt have been associated twiceExecute WaitWobj again when DropWObj is not executedPlease check the instruction. The same work object should be associated only once
10138Waitwobj instruction is not allowed to be executed continuously in the Manual modeCaused by continuous execution in the Manual modeSingle-step execution in the Manual mode or continuous execution in the Automatic mode
10139There are no associated work objects1. There is no work object being tracked; 2. There is no conveyor belt with the specified namePlease place the work object on the conveyor belt and trigger the photoelectric switch. The status monitoring shows whether the work object is in the correct position
10140The viscous friction force & Coulomb friction coefficient identified are negativeContact the Control Team
10141The mass input should be between 0 and the maximum loadThe mass input should be between 0 and the maximum load
10142Please perform load-free identification first and then loaded identificationPlease perform load-free identification first and then loaded identification
10143Failed to set speed before moving to a point position or force control identification
10145When the PCB 3/4 axis robot is set to trigger the Reduced mode after entering the safety zone, there will be no trigger actionPCB 3/4 axis robots do not support the Reduced mode for the moment
10147Error occurs when verifying the license keySee the contentPlease contact the administrator of licensing
10148The axis max speed exceeds the limit, data won't be savedSee the contentPlease edit the axis max speed setting on HMI
10149Socket disconnected, pause program according to the socket settingSocket disconnectedCheck socket connection status
10150Socket disconnected, pause program and power down motors according to the socket settingSocket disconnectedCheck socket connection status
10151Failed to move to point, invalid setting of tool and wobjInvalid to set "handheld" or "external" for both the tool and the wobjSelect the correct tool and wobj
10152Failed to save DH parameters. DH parameter changes over the limitDH parameter changes over the limitThe limit range of DH parameter changes is: length +/- 50mm , angle +/- 10°
10153Calibration failed. user frame id errorCalibration failed. user frame id errorSelect the correct user frame system and recalibrate.
10154The robot is in a safe retraction state and cannot perform the current operation.The robot is in a safe withdrawal state and is not allowed to perform the current operation.After the jog robot has safely retracted in manual mode, try again.
10200Electronic nameplate does not exist. No electronic nameplate is detected1. The body has no electronic nameplate; 2. Hardware damage of the electronic nameplate; 3. The serial port of electronic nameplate configured incorrectly1. Check the hardware connection of the electronic nameplate serial port; 2. Check the electronic nameplate hardware; 3. Check the serial port configuration of the electronic nameplate
10201Error in electronic nameplate data reading1. Wrong protocol address of the electronic nameplate; 2. Hardware damage of the electronic nameplate1. Check whether the protocol matches; 2. Check the electronic nameplate hardware
10202Error in electronic nameplate data writing1. Wrong protocol address of the electronic nameplate; 2. Hardware damage of the electronic nameplate1. Check whether the protocol matches; 2. Check the electronic nameplate hardware
10203Electronic nameplate data mismatch1. The robot body has been changed; 2. The control cabinet has been changedData overwrite after confirmation
10204Encoder battery voltage too low1. Running for too long; 2. Encoder battery is damagedReplace the encoder battery
10205The duration of the robot motion exceeded the warranty periodNot maintained in timeRegular maintenance
10207Electronic nameplate data overwrite not allowed1. Electronic nameplate does not exist; 2. Model, ID or hardware version do not matchPlease check the electronic nameplate according to the log
10208RC data overwrite not allowed1. The controller model does not match with the body; 2. Data has not been burnt to the electronic nameplate or wrong data is burnt1. Select the correct model and restart the controller; 2. Burn the correct data to the electronic nameplate
10209socket communication failed:socket resource has been used by external communication1.IP and port are already used by external communication 2.The socket name has the same name as the external communication, the default SYS_SOCKET name is already used by the external communication.1.Change the port or IP of the socket 2.Change the name of the socket
10210Switching precision compensation state not allowedZero point data errorCheck zero point data
11000The drive has duplicate aliasesThe drive has duplicate aliasesChange alias
11001Unknown drive, unable to set drive informationUnknown drive, unable to set drive informationChange driver name
11002The drive bound to the axis does not existThe drive bound to the axis does not existModify the drive bound to the axis
11003When the mechanical unit with the axis enabled is in use, the driver cannot be emptyWhen the mechanical unit with the axis enabled is in use, the driver cannot be emptyBind the drive for the axis
11004The drive of the axis has been bound/the data bit has been boundThe drive of the axis has been bound/the data bit has been boundChange the drive/data bit bound to the axis
11005The driver/data bit is inconsistent with the existing welding gunThe driver/data bit is inconsistent with the existing welding gunChange the driver/data bit bound to the servo welding gun axis to match the existing welding gun
11006The maximum number of additional axes has been reached, and no more additional axes can be addedThe maximum number of additional axes has been reached, and no more additional axes can be added
11021Failed to add/modify mechanical unit, the number of axes under the mechanical unit exceeds the limitThe number of axes under the mechanical unit exceeds the limitModify the number of axes in the mechanical unit
11022Failed to add/modify mechanical unit, The mechanical unit name is not composed of English or English plus numbersThe mechanical unit name is not composed of English or English plus numbersModify the mechanical unit alias to consist of English or a combination of English and numbers
11023Axis does not existAxis does not existReplace the bound axis
11024Failed to add/modify mechanical unit, Axis is not bound to a driverAxis is not bound to a driverBind the drive for the axis
11025Failed to add/modify mechanical unit, The axis of the servo welding gun unit must be the servo welding gun axisThe axis of the servo welding gun unit must be the servo welding gun axisModify the bound axis to ensure it is the servo welding gun axis
11026Failed to add/modify mechanical unit, The mechanical unit name already existsThe mechanical unit name already existsModify the name of the mechanical unit
11027Failed to add/modify mechanical unit, the axis has been used by other mechanical unitsThe axis has been used by other mechanical unitsModify the bound axis
11028Failed to add/modify mechanical unit,The current number of mechanical units has reached its maximumThe current number of mechanical units has reached its maximum
11029Mechanical unit does not existMechanical unit does not exist
11040Coordinate system calibration result confirmation failed, input exceptionInput exception, mechanical unit does not existaxis does not exist
11050Jog's mechanical unit does not have the axisJo's axis number is not within the range of degrees of freedom of the selected mechanical unit
11060Abnormal mechanical unit enabled, please restartAbnormal mechanical unit enabled, please restartRestart the robot
13013Emergency stop triggeredManually resume emergency stop
13014Safety gate openedManually close the safety gate
13016Error in program lexical or grammar checkGrammatical error in RL programPlease check the RL program
13017Program PP_to_main failed1. Task destroyed; 2. Project file not loaded; 3. main function missing1. Reinitialize the task; 2. Reload the project; 3. Check if there is a main function in the file
13018Program PP_to_func failed1. Task destroyed; 2. Symbol table not yet established for the task; 3. The function to be jumped to does not exist1. Reinitialize the task; 2. Check if there is a grammatical error in the function and recreate the symbol table; 3. Check if the function exists
13019Program PP_to_line failed1. Task destroyed; 2. Symbol table not yet established for the task; 3.The program PP_to_line jump is only allowed inside the same PROC/FUNC1. Reinitialize the task; 2. Check if there is a grammatical error in the function and recreate the symbol table; 3.Please check if the jump is inside the same PROC/FUNC
13020All RL tasks have been stopped. Please check the error message or click PPToMain1. The single loop mode task is finished; 2. When an error occurs, the task will stop1. Check the program for logical errors; 2.Click pptomain to run again
13021Wrong base coordinate system. Failed to setThe controller can not parse the instruction to set the base coordinate system, possibly because the controller version is not compatible with the HMIPlease check whether the control system version matches with HMI
13022Next step run failed,task [] not loadedCheck the corresponding task in the project's task list and execute pptomain.
13023Wrong base coordinate system. Failed to setThe controller can not parse the instruction to set the base coordinate system, possibly because the sum of the squares of the quaternions is not equal to 1 or that the Euler angles are out of bounds.Please check the values of the quaternion or the degrees of the Euler angles
13030RSC detects that the robot exceeds the limit of power, and triggers a safe stopThe robot power exceeds the limit, or the power of configuration in RSC is too low, or the RSC failsCheck whether the RSC robot power limit range is reasonable, or close the RSC robot power limit
13031RSC detects that the robot exceeds the limit of momentum, and triggers a safe stopThe robot momentum exceeds the limit, or the momentum of configuration in RSC is too low, or the RSC failsCheck whether the RSC robot momentum limit range is reasonable, or close the RSC robot momentum limit
13032RSC detects that the robot exceeds the limit of Elbow or TCP force, and triggers a safe stopThe robot Elbow or TCP force exceeds the limit, or the Elbow or TCP force of configuration in RSC is too low, or the RSC failsCheck whether the RSC robot Elbow or TCP force limit range is reasonable, or close the RSC robot Elbow or TCP force limit
13033RSC detects that the robot exceeds the limit of TCP velocity, and triggers a safe stopThe TCP velocity of robot exceeds the limit, or the TCP velocity of configuration in RSC is too low, or the RSC failsCheck whether the RSC robot TCP velocity limit range is reasonable, or close the RSC robot TCP velocity limit
13034RSC detects that the robot exceeds the limit of position, and triggers a safe stopThe position of robot exceeds the limit, or the RSC failsCheck whether the RSC robot position limit range is reasonable, or close the RSC robot position limit
13035RSC detects that the robot exceeds the limit of posture, and triggers a safe stopThe posture of robot exceeds the limit, or the RSC failsCheck whether the RSC robot posture limit range is reasonable, or close the RSC robot posture limit
13036RSC detects that the robot exceeds the limit of collision force, and triggers a safe stopThe collision force of robot exceeds the limit, or the RSC failsCheck whether the RSC robot collision force limit range is reasonable, or close the RSC robot collision force limit
13037RSC detects that the robot exceeds the limit of joint[] power, and triggers a safe stopThe joint power of robot exceeds the limit, or the RSC failsCheck whether the RSC robot joint power limit range is reasonable, or close the RSC robot joint power limit
13038RSC detects that the robot exceeds the limit of joint[] position, and triggers a safe stopThe joint position of robot exceeds the limit, or the RSC failsCheck whether the RSC robot joint position limit range is reasonable, or close the RSC robot joint position limit
13039RSC detects that the robot exceeds the limit of joint[] velocity, and triggers a safe stopThe joint velocity of robot exceeds the limit, or the RSC failsCheck whether the RSC robot joint velocity limit range is reasonable, or close the RSC robot joint velocity limit
13040RSC detects that the robot exceeds the limit of joint[] torque, and triggers a safe stopThe joint torque of robot exceeds the limit, or the RSC failsCheck whether the RSC robot joint torque limit range is reasonable, or close the RSC robot joint torque limit
13041RSC detects the communication of joint[] is abnormal, and triggers a safe stopThe joint communication of robot is abnormal, or the RSC failsTry to reboot the robot, or contact the manufacturer to check the hardware failure
13042RSC detects the operation of joint[] is abnormal, and triggers a safe stopThe joint operation of robot is abnormal, or the RSC failsTry to reboot the robot, or contact the manufacturer to check the hardware failure
13043The Communication between RSC and Controller is errorThe communication between RSC and controller is errorTry to reboot the robot, or contact the manufacturer to check the hardware failure
13044Failed to Synchronize Sdo Data Between Controller and RSCFailed to synchronize sdo data between controller and RSCTry again, or contact the manufacturer to check the hardware failure
13046The security limit of RSC is exceeded when draggingWhen dragged, TCP speed exceeds 250mm/s, triggering safe stop
13047RSC initialization process detected parameters inconsistent with the master controller parameters, RSC parameters have been updated according to the master controller parameters, require a hard restart of the robot or control cabinet to take effect.The basic security parameters of RSC are inconsistent with those of the master controllerHard restart the robot or control cabinet
13048The communication between the RSC and the master controller enters a secure data state (0x08)The communication between the RSC and the master controller enters a secure data state (0x08)
13049The parameter of joint position limit for RSC is invalidThe set angle is beyond the robot’s mechanical limitConfirm the robot's mechanical limit and set the angle within the range
13050The parameter of safety home position for RSC is invalidThe set angle is beyond the robot’s mechanical limitConfirm the robot's mechanical limit and set the angle within the range
13052Safety gate is opened, and the RL program cannot be continuedSafety gate is openedReset the safety gate, and try again
13053RSC detected Axis trigger Flying speed protectRobot experience flying speed
13057RSC detected a short circuit fault in the channel of safety outputThe safety output channel is short-circuited to the 24V power supplyPlease check if there is any wiring error. After the fault is restored, power off and restart
13058RSC has detected inconsistency between the two channels of the safety DI signal. The specific signal isRSC safety DI signal dual channel signal is inconsistentPlease check and repair the wiring of the corresponding DI signal, then reset it to 0, and then set it to 1 at the same time to recover the fault
13059RSC detected a dual machine communication failureIf it persists, it is recommended to replace the RSC
13060RSC detected MCU address faultIf it persists, it is recommended to replace the RSC
13061RSC detected inconsistent output data faultThe data information output by the host and slave computers is inconsistentIf it persists, it is recommended to replace the RSC
13062RSC detected voltage exceeding the limitThe voltage of the power supply is not between 20~30VCheck RSC power supply voltage
13063RSC detected algorithm library malfunction
13064RSC detected that Bamboo is not running properlyPower off and restart. If the issue persists after restarting, it is recommended to replace the RSC
13065RSC detects FSOE internal communication failureRe power on for testing. If the issue persists, it is recommended to replace the RSC
13066RSC detected communication failure in FSOE departmentRe power on for testing. If the issue persists, it is recommended to replace the RSC
13067RSC detected abnormal communication from station
13068RSC detected that the slave station is not in the FSOE data state
15000Execute drag path playback. No available drag data in the bufferExecute drag path playback. No available drag data in the bufferRecord the drag path again
15001Failed to save the drag data. No available drag data in the bufferNo available drag data in the bufferPlease record the drag path again
15002Execute drag path playback. Drag data file does not existDrag path record deleted accidentallyRecord the drag path or import the path again
15003Failed to execute drag path playback. Error in drag file dataPlayback path from another type of robotsImport the correct drag playback path or record the trajectory again
15004Failed to save the drag data. Failed to write the drag data into the fileFailed to drag the replay serialized data to the hard disk filePlease record the drag path again or restart the robot
15010Fewer than two robot path waypoints collected in this segment. Unable to form a pathToo few drag path waypointsPlease record the drag path again
15011Failed to record path data: joint angle over the limitJoint in the drag path exceeds the joint position limitPlease record the drag path again
15012Failed to record path data: joint velocity over the limitJoint velocity in the drag path exceeds the limitPlease record the drag path again
15013Failed to record the path data: the speed is not zero when recording endsThe speed is not zero when path recording endsClick end recording after the robot stops
15014Failed to record path data: The speed is not zero when recording startsThe speed is not zero when recording startsMake sure the robot is stopped before recording starts
15015Failed to record the path data: motor not powered onMotor not powered onRobot Power-On
15017Execute drag path playback. Failed to read pathFailed to parse the drag path data. The path data may be tamperedImport the path or record the trajectory again
15018Path playback. The speed set exceeds the limitThe playback speed set is too fastDecrease the path playback speed
15019Path playback. The path waypoint exceeds the joint position limit set for the playbackPlayback path waypoint exceeds the joint position limitAdjust the current joint position limit
15020Path playback failed, path playback is not allowed when the track is turned on!Path playback is not allowed when the track is turned on.Path playback after closing the tarck.
17001Register () failed to read data1. The register does not exist; 2. The register does not match the variable type; 3. The array subscript is out of rangePlease check the register settings
17002Register () failed to write data1. The register does not exist; 2. The register does not match the variable type; 3. The array subscript is out of rangePlease check the register settings
17003modbus failed to read the input register
17004Failed to load register configurationFailed to parse register configuration file (registers.json). See the "content" for reasonsPlease try to reconfigure the register or erase the configuration
17005modbus communication failed, modbus link not established
17008Failed to parse modbus configuration. Cause of the errorError in modbus register configurationCheck the modbus register configuration
17009Failed to load the bus device configuration fileFailed to parse the bus device configuration file (fieldbus_device.json). See the "content" for reasonsPlease try to reconfigure the bus device or erase the configuration
17100Failed to turn on cclink. cclink gateway module not retrievedcclink gateway module not configured or an exception in the device linkingImport and configure cclink gateway module
17102Failed to turn on cclink
17200There is no any set of servo params files that meet the rules in the controller,Please import a set of servo paramsEach function of servo parameter switching can only be used if there is at least one set of servo params in the controller
17201Power on failure, power on is prohibited during servo parameter switchingPower on failure, power on is prohibited during servo parameter switching
17202It is prohibited to switch servo parameters while robot is power onIt is prohibited to switch servo parameters while robot is power on
17205Electroplating line visual socket, IP cannot be empty or '0.0.0.0', port cannot be empty
17206Quick adjustment of custom pose beyond limit.
17207The system is powered on and cannot proceed:SWITCH_AUTO_MOTORON
17300RL program customization stopped and cannot continue runningAfter pptomain、pptoline or pptofunc,start run program
17310Servo parameter acquisition failed,()
17312Servo parameter download failed,()
17314Cfg file is incomplete and does not contain the 'STOP1_TIME' fieldCfg file is incompleteplease update the cfg file
17315Fail to change IP, the reason isSee contentEnter the appropriate IP
17316Rail zero calibration failed1. Not in the Manual mode; 2. Robot in motion; 3. Not in the Position modePlease make sure that the robot is in the Manual mode and not in motion
17318Soft estop state does not allow power onThere is currently a read-only register bound to ctrl_soft_estop function code and low level, no power on allowedReset the register bound with the ctrl_soft_estop function code
17319Soft emergency stop triggerednoneResume soft emergency stop by register
17320Motion commands status is inconsistent with the operationSee the contentDo PPtoMain or reset cache
17321disconnect from the controller, stop moving and/or disable dragSet HMI/SDK disconnection options
17400OpcUA variable() read failed1.The variable is not existed; 2.The variable type is different from the parameterPlease check the RL command and the OpcUA variable configuration
17401OpcUA variable() write failed1.The variable is not existed; 2.The variable type is different from the parameterPlease check the RL command and the OpcUA variable configuration
17402Soft calibration failed1. Not in the Manual mode; 2. Robot in motion; 3. Not in the Position modePlease make sure that the robot is in the Manual mode and not in motion
17406Axis () Soft calibration failed1. Not in the Manual mode; 2. Robot in motion; 3. Not in the Position modePlease make sure that the robot is in the Manual mode and not in motion
17407Opening rail failed, please close the safety area first
17408Safety area open failedWhen the rail is opened, the safety area cannot be opened
17500The driver is in a critical error state. It's not allowed to clear alarm and power on. ()The driver is in a critical error state, hardware may in error state.Try to power off and restart the control system; Contact the manufacturer's technical support.
17507Conveyor start tracking failed..
17508Conveyor stop tracking failed..
17509Conveyor calibration failed, the number of points in the X direction is not 3.Please check the calibration process
17510Conveyor calibration failed, transmission ratio is 0.1.The conveyor belt is not turned on,2.Encoder value abnormality
17511The safety stop parameters are set incorrectlyThe safety stop parameters may be set to zeroPlease set The safety stop parameters to proper values
17512During the tracking process of the conveyor belt, it is prohibited to execute ordinary motion commands
17513The conveyor belt stopped during tracking and cannot continue runningAfter pptomain, rerun the program
17520OPC UA server start failed1.Port is wrong or occupied; 2.Error Configuration1.Use the right port; 2.Change the configuration
18002The robot has entered the occupied shared area and is slowing down and stopping at maximum capacity
18003The robot is about to enter the occupied shared area, slowing down and pausing, waiting for the shared area to be released
18004The robot has entered the prohibited zone and has slowed down to a maximum capacity to stop
18005Robots are about to enter the prohibited zone, plan to stop
18006Shared area failure, robot continues to operate
18007When switching the reduction mode, the current joint axis angle has exceeded or is nearing the reduced joint positionPlease reset the reasonable reduction joint position
18008Cannot change the dimension of the arrayDo not modify array dimensions
18009controller log corruption is detected, use backup logsmay be caused by a power failure or abnormal restartno need to fix
18011Locking machine authorization failedSee the contentPlease contact the administrator of licensing
18013Load information setting failedThe set load information will cause the inertia or torque at the end effector to exceed 1.5 times the limitThis setting is dangerous. Please check the input or replace the tool
18014Load information setting abnormalThe set load information will cause the inertia or torque at the end effector to exceed 1~1.5 times the limitThis setting poses a risk. It is recommended to check the input or replace the tool
18015Friction calibration failed saraThe hot machine has not reached the set threshold value.Restart the hot machine.
18017Shutdown recovery failedPlease check the specific error message for detailed informationReload the project and run the RL project
18018Shutdown recovery failed (previous shutdown was abnormal)The previous shutdown was not performed through the proper procedure, preventing the system from fully saving its stateAlways shut down the system using standard methods—such as the shutdown button on the teach pendant or the power button on the control cabinet. Avoid abruptly cutting power or forcibly turning off the device to ensure smooth recovery at the next startup
18022CrossConnection Check Failed1.Bind to a non-existent signal; 2.Signal port mismatch; 3.Output signal binding system IO eventsPlease check the cross-connect signal configuration
18030database error, add log failed, check log detailsadd log to data base failed, check log detailsreboot
30060Joint velocity over the limit
30061TCP velocity over the limit
30062Joint torque over the limit
30063Momentum over the limit
30064Total joint power over the limitTotal joint power exceeds the value set in the safety monitor1. Slow down the motion speed; 2. Reduce the load and inertia; 3. Turn off the safety monitor
30065Dual encoder position deviation over the limit
30066Dual channel data deviation of the torque sensor exceeds the limit
30067joint power over the limit
30068TCP angular speed over the limit
30069elbow speed over the limit
30070elbow angular speed over the limit
30071moment over the limit
30072tool attitude over the limit

IO

CodeError MessageCauseSolution
14010The register () is bound to the system functional register. Write operation is not allowed in RL programThe register is bound to the system functional register. Write operation in RL program is not allowedPlease use another register or unbind this register
14011Failed to open fieldbus device []. Corresponding Ethercat slave not foundNo Ethercat slave is configured or there is an exception in the device linkingImport and configure Ethercat slave
14012The register () is readonly register, Write operation is not allowedThe register is readonly register, Write operation is not allowedPlease use writeonly register,or modify the register attribute
14021Failed to open fieldbus deviceSee the "content"Please check the fieldbus device configuration and make sure that the corresponding device is correctly connected
14023The serial port is already occupied by the fieldbus deviceThe serial port is already used by modbus RTU fieldbus deviceClose the fieldbus device or use another serial port
14030Error in profinet fieldbus model configurationThe data model selected for the slot does not match the PLCReconfigure the data model of the slot
14031Error in data recovery for holding registersError in crc validation for holding register files. Files are corruptedDelete holding register file
14032Failed to open fieldbus device [].SDO setup failedSDO setup failedCheck if SDO initialization settings meet device requirements
14501The port of () is bind to system IO and cannot be setDO signal is a system IO signal or is bind by CrossConnection and cannot be setPlease use other output signals or unbind this signal in the system IO/CrossConnection
14502Failed to set GO signal ()The value set is beyond the valid range of the signal or its ports has been bind to System IO/CrossConnectionPlease check the value and its ports
14503Failed to set AO signal (). The value set is beyond the valid range of the signalThe value set is beyond the valid range of the signalPlease check the value
14504Failed to set PulseDO. Wrong pulse time: () SWrong pulse time, [0.001, 2000] S rangeRe-enter the pulse time
14505Failed to set PulseReg. Wrong pulse time: () SWrong pulse time, [0.001, 10] S rangeRe-enter the pulse time
14510Failed to load the output signal ()The mapped physical port is in conflict with other signals or system output signals1. Check if the output port is occupied; 2. Reconfigure the system IO
14511Failed to set the system input signal. There is a conflictViolation of system input configuration rules. Possible causes: 1. Duplicate system IO is configured; 2. The corresponding IO is already occupied by the RL project; 3. IO signal does not exist1. Configure independent system IO; 2.Modify the system IO occupied by the RL project; 3.Open or create IO device
14512Failed to set the system output signal due to a conflictViolation of system output signal configuration rules. Possible causes: 1. Duplicate system IO is configured; 2. The corresponding IO is already occupied by the RL project; 3. IO signal does not exist; 4.Is bind by CrossConnection1. Configure independent system IO; 2.Modify the system IO occupied by the RL project; 3.Open or create IO device; 4.UnBind from CrossConnection
14521Failed to initialize Ethercat IO device []. Corresponding Ethercat slave not foundNo Ethercat slave is configured or there is an exception in the device linkingImport and configure Ethercat slave
14530The status of the safety panel expansion IO device [] becomes unavailableHardware damage or abnormal linking for the expansion IO devicePlease check the hardware status and link status of the expansion IO devices on the safety panel
14531The status of the safety panel expansion IO device [] becomes availableNew expansion IO device connected
14532IO device [] becomes closedIO device configuration connected
14534IO device [] becomes abnormalIO device connection error
14535The imported register variable uses a bus device that does not exist on the current machine: []The bus device is not configured on the current machineManually edit the register variable and change the device name to a bus device that exists on the current machine
14536Empty signal name ()Used an empty signalUse the signal with the normal name
14537Signal () type invalidAn invalid type of signal was usedUse the correct signal type
14538Signal () mapping device not existedThe signal is bound to a non-existent deviceBind the signal to the correct device
14539Signal () mapping device is disabledThe device for signal mapping is disabled1.Bind other normal devices 2.Re-enable disabled devices
14540New group signal () mapping invalid, Port mapping errorThe relationship between the starting port and ending port of the group signal is incorrectThe group signal end port number should be greater than the start port number; 2.The port number of the signal should not exceed the device port range
14541New group signal () mapping invalid, Port number should not be greater than 32Too many signal ports in the groupThe number of signal ports in the group should not exceed 32
14542New signal () mapping invalid, Port mapping errorSignal port setting error1.Change the starting and ending ports of the signal to make them consistent; 2.The port number of the signal should not exceed the device port range
14543New signal () mapping invalid, Output physical port is already usedThe port used by the signal is occupied1. Configure independent system IO; 2.Modify the system IO occupied by the RL project; 3.Open or create IO device
20000Profinet AlarmMULL
20003Profinet Device Open Failed

Motion

CodeError MessageCauseSolution
30400Robot stopped due to collision. Check the robot operating environment and confirm that the staff and devices are safe before restartRobot collision1.Check the robot operating environment, confirm that the staff and devices are safe, and power on the robot, before restart
30401Robot stopped due to collision. Check the robot operating environment and confirm that the staff and devices are safe before restartRobot collision1. Check the robot operating environment, confirm that the staff and devices are safe, and power on the robot, before restart; 2. Check whether the current Tool setting is consistent with the actual situation and whether the set tool mass center is reasonable
30402Robot stopped due to elbow force collision. Check the robot operating environment and confirm that the staff and devices are safe before restartRobot collision1. Check the robot operating environment, confirm that the staff and devices are safe, and power on the robot, before restart; 2. Check whether the current Tool setting is consistent with the actual situation and whether the set tool mass center is reasonable
30402Robot stopped due to elbow force collision. Check the robot operating environment and confirm that the staff and devices are safe before restartRobot collision1. Check the robot operating environment, confirm that the staff and devices are safe, and power on the robot, before restart; 2. Check whether the current Tool setting is consistent with the actual situation and whether the set tool mass center is reasonable
30403Robot stopped due to tcp force collision. Check the robot operating environment and confirm that the staff and devices are safe before restartRobot collision1. Check the robot operating environment, confirm that the staff and devices are safe, and power on the robot, before restart; 2. Check whether the current Tool setting is consistent with the actual situation and whether the set tool mass center is reasonable
50000Blending cancelingThe threshold for canceling the blending is exceeded1. Increase the angle between the two trajectories; 2. Increase the length of the two trajectories; 3. Increase the zone
50001Controller status is abnormal. Run PPtoMain to reset projects or reload programsThe controller status is abnormalRun PPtoMain to reset projects or reload programs
50002Target point exceeds range of motion1. The target point exceeds the range of motion of the robot. 2. The target point is the singular position in the Cartesian coordinate system1. Check the target point position. 2. Move the robot by using its joints. 3. Check CONFDATA configuration
50003Failed to generate a trajectory if two adjacent target points are too closeTwo adjacent target points are too closeCheck whether two adjacent Move commands use the same target point
50004The start point of arc is too close to the end point. Failed to generate arc. Trajectories will be ignoredThe start point of arc is too close to the end point. Failed to generate arc. Trajectories will be ignored1. Adjust the distance between the point positions of the start point and the end point of the arc
50005The start point of arc is too close to the auxiliary point. Failed to generate arcThe start point of arc is too close to the auxiliary point. Failed to generate arc1. Adjust the distance between the point positions of the start point and the auxiliary point of the arc
50006The end point of arc is too close to the auxiliary point. Failed to generate arcThe end point of arc is too close to the auxiliary point. Failed to generate arc1. Adjust the distance between the point positions of the end point and the auxiliary point of the arc
50007The angle between the start point, the auxiliary point, and the end point is too small. Failed to generate arcIf the distance between any two of the start point, the auxiliary point, and the end point is too short, the angle between them will be very small1. Adjust the distance between the point positions of the start point, the end point, and the auxiliary point of the arc
50008The start point, the auxiliary point, and the end point of the arc are on the same straight line. Failed to generate arcThe start point, the auxiliary point, and the end point are on the same straight line. Failed to generate arc1. Adjust the distance between the point positions of the start point, the end point, and the auxiliary point of the arc
50009The radius of the arc is too small. Failed to generate arcThe distance between the start point, the end point, and the auxiliary point of the arc are too short1. Adjust the distance between the point positions of the start point, the end point, and the auxiliary point of the arc
50010Conditions for generating an arc are not met. Failed to generate arcThe distance between the start point, the end point, and the auxiliary point of the arc are too short, or the start point, the auxiliary point, and the end point of the arc are on the same line1. Adjust the distance between or the orientation of the point positions of the start point, the end point, and the auxiliary point of the arc
50011The start point of the trochoid is too close to the end point. Failed to generate trochoidThe start point of the trochoid is too close to the end point. Failed to generate trochoid1. Adjust the distance between the point positions of the start point and the end point of the trochoid. 2. Conditions for generating a trochoid are as follows: the specified radius is more than 1 mm; the specified feed is more than 1 mm; the trochoid length is more than the sum of two radii and one and a half feeds. Note that the trochoid length depends on the distance between the start point, the auxiliary point, and the end point
50012The start point of the trochoid is too close to the auxiliary point. Failed to generate trochoidThe start point of the trochoid is too close to the auxiliary point. Failed to generate trochoid1. Adjust the distance between the point positions of the start point and the auxiliary point of the trochoid. 2. Conditions for generating a trochoid are as follows: the specified radius is more than 1 mm; the specified feed is more than 1 mm; the trochoid length is more than the sum of two radii and one and a half feeds. Note that the trochoid length depends on the distance between the start point, the auxiliary point, and the end point
50013The end point of the trochoid is too close to the auxiliary point. Failed to generate trochoidThe end point of the trochoid is too close to the auxiliary point. Failed to generate trochoid1. Adjust the distance between the point positions of the end point and the auxiliary point of the trochoid. 2. Conditions for generating a trochoid are as follows: the specified radius is more than 1 mm; the specified feed is more than 1 mm; the trochoid length is more than the sum of two radii and one and a half feeds. Note that the trochoid length depends on the distance between the start point, the auxiliary point, and the end point
50014The start point, the auxiliary point, and the end point of the trochoid are on the same straight line. Failed to generate trochoidThe start point, the auxiliary point, and the end point of the trochoid are on the same straight line. Failed to generate trochoid1. Adjust the distance between the point positions of the start point, the auxiliary point, and the end point of the trochoid. 2. Conditions for generating a trochoid are as follows: the specified radius is more than 1 mm; the specified feed is more than 1 mm; the trochoid length is more than the sum of two radii and one and a half feeds. Note that the trochoid length depends on the distance between the start point, the auxiliary point, and the end point
50015The specified radius is too small. Failed to generate trochoidThe specified radius is too small. Failed to generate trochoid1. Increase the specified radius. 2. Conditions for generating a trochoid are as follows: the specified radius is more than 1 mm; the specified feed is more than 1 mm; the trochoid length is more than the sum of two radii and one and a half feeds. Note that the trochoid length depends on the distance between the start point, the auxiliary point, and the end point
50016The specified feed is too small. Failed to generate trochoidThe specified feed is too small. Failed to generate trochoid1. Increase the specified feed. 2. Conditions for generating a trochoid are as follows: the specified radius is more than 1 mm; the specified feed is more than 1 mm; the trochoid length is more than the sum of two radii and one and a half feeds. Note that the trochoid length depends on the distance between the start point, the auxiliary point, and the end point
50017The specified radius of the trochoid is less than the feed. Failed to generate trochoidThe specified radius of the trochoid is less than the feed. Failed to generate trochoid1. The specified radius should not be less than the specified feed. 2. Conditions for generating a trochoid are as follows: the specified radius is more than 1 mm; the specified feed is more than 1 mm; the trochoid length is more than the sum of two radii and one and a half feeds. Note that the trochoid length depends on the distance between the start point, the auxiliary point, and the end point
50018The trochoid is too short. Failed to generate trochoidThe radius and feed are specified, if the distance between the start point and the end point is short, a trochoid will not be generated1. Reduce the specified radius or feed. 2. Increase the distance between the start point and the end point. 3. Conditions for generating a trochoid are as follows: the specified radius is more than 1 mm; the specified feed is more than 1 mm; the trochoid length is more than the sum of two radii and one and a half feeds. Note that the trochoid length depends on the distance between the start point, the auxiliary point, and the end point
50019Internal error generating pathInternal error generating path1. Re-adjust the target point position, pose, and arm angle. Note that the arm angle only needs to be considered for 7-axis robots
50020The set tool coordinate system cannot match the features of the current model. Failed to generate the pathThe specified tool coordinate system does not support the model1. The tool coordinate system of the current model must meet the following two requirements – the method for holding: hand-held, and position: x=0, y=0
50021The target point with the specified confdata has no solution, and the robot could not reach the target point with the specified confdata. Please calibrate the target point parameters or re-teach the point position.1. The target point with the specified confdata has no solution1. Use the instruction ConfJ off to cancel confdata; 2. Re-teach the point position
50022Illegal Instructions. The number of parameters entered is incorrect.1. Illegal Instructions1. Re-teach the point position; 2. Restart the robot
50023As the target point chooses inverse kinematics of a singular position, the robot is unable to move to the target point precisely1. The target point has no teaching, or its conf information is incorrectModify the target point conf
50024The incorrect trajectory type can make it impossible for the robot to translate along the specified direction, please re-teach the point positionThe current robot can only translate on the xz plane of the base coordinate, and cannot deviate from the xz plane of the base coordinate systemRe-teach the point position
50025The incorrect trajectory type can make it impossible for the robot to rotate along the specified direction, please re-teach the point positionWhile the current robot rotating, its rotation axis must be in parallel with the y-axis of the base coordinate systemRe-teach the point position
50026Waiting for the next motion instruction to be resolved for a long time will automatically cancel the turning area,line number isInsert too many non-motion commands between two motion commands,automatically cancel the turning area1. Run the RL command "AotoIgnoreZone Off",The system will not automatically cancel the turning zone. 2.Simplify the non-motion instruction between two motion instructions
50028The spiral's initial radius is less than zero. Failed to generate spiralThe spiral's initial radius is less than zero. Failed to generate spiral1. Increase the spiral's radius step. 2. Conditions for generating a spiral are as follows: the initial radius is not less than 0; the radius step is more than 0.0001 mm/deg; the cumulative rotation angle is between 0.1 and 3600 deg;
50029The spiral's radius step is too low. Failed to generate spiralThe spiral's radius step is too low. Failed to generate spiral1. Increase the spiral's radius step. 2. Conditions for generating a spiral are as follows: the initial radius is not less than 0; the radius step is more than 0.0001 mm/deg; the cumulative rotation angle is between 0.1 and 3600 deg;
50030The spiral's cumulative rotation angle is illegal. Failed to generate spiralThe spiral's cumulative rotation angle is illegal. Failed to generate spiral1. Increase the spiral's cumulative rotation angle. 2. Conditions for generating a spiral are as follows: the initial radius is not less than 0; the radius step is more than 0.0001 mm/deg; the cumulative rotation angle is between 0.1 and 3600 deg;
50031Trajectory error. Spiral trajectory does not support handheld work objectsSpiral trajectory does not support handheld work objectsReplace with handheld tools
50033Wrong trajectory,the endpoint deviates from lock axis angleThe endpoint deviates from lock axis angle(0,180,-180)Adjust the endpoint or close lock axis
50034Unable to reach the target in the locked axis state or 5-axis robot.Please change the targetUnable to reach the target in the locked axis state or 5-axis robot.Please change the targetUnable to reach the target in the locked axis state or 5-axis robot.Please change the target
50035Unable to generate identification trajectory in the locked axis state. Please close lock axistrajectory couldn't be generated correctly in the locked axis statePlease close lock axis
500365 axis robot unable to do load identification5 axis robot unable to do load identificationnone
50040Unable to do identification because the soft limit is not enabledThe soft limit is not enabledPlease enable the soft limit
50041The joint position limitation is not set within the upper/lower limit range of 5 degrees so identification is not allowedThe joint position limitation is incorrectly setPlease set the joint position limitation correctly
50042The stating point of this trajectory is incorrect,this robot needs to keep flange parrallel to the baseThe stating point of this trajectory is incorrect,this robot needs to keep flange parrallel to the baseRe demonstrate teaching points
50043The target point of this trajectory is incorrect,this robot needs to keep flange parrallel to the baseThe target point of this trajectory is incorrect,this robot needs to keep flange parrallel to the baseRe demonstrate teaching points
50044The back direction is wrong. Please move towards the work area direction.The back direction is wrong. Please move towards the work area direction.Please move towards the work area direction.
50045Additional axis parameter error,only one base type additional axis mechanical unit is allowed to be setAdditional axis parameter error,only one base type additional axis mechanical unit is allowed to be setAdditional axis parameter error,only one base type additional axis mechanical unit is allowed to be set
50046Additional axis parameter error,duplicate axis data mappingAdditional axis parameter error,duplicate axis data mappingAdditional axis parameter error,duplicate axis data mapping
50047Additional axis parameter error,axis type errorAdditional axis parameter error,axis type errorAdditional axis parameter error,axis type error
50048Additional axis parameter errorAdditional axis parameter errorAdditional axis parameter error
50101During the lookahead, the axis exceeds the motion range. Stop the motion in advanceThe axis-angle motion exceeds the motion range1. Cancel the joint position limitation 2. Manually move each axis of the robot to the normal working range
50102If there are singularities during the lookahead of the trajectory, please avoid the singularitiesThere are trajectories across singularitiesPlease avoid singularities (refer to the manual for the relevant information): 1. Re-teach the point position, and change the target point; 2. Or change the Cartesian space motion instruction to the joint space motion instruction
50103The end point of the planned Cartesian path cannot match the given ConfDataInability to move to the target point of the given ConfData through the planning of the Cartesian space1. Change the target point ConfData; 2. Change to MoveJ or MoveAbsJ
50104During the lookahead, the joint torque exceeds the limit1.The load value is set too high, exceeding the robot's load-bearing capacity; 2. The friction coefficient of the robot is too high. 3. The electric overload coefficient or transmission overload coefficent of the robot is too small.1.Check if the load values match the actual situation. 2. Check parameters such as friction coefficent,motor overload coefficient,transmission overload coefficient; 3. Try to change the type of the instruction, for instance, change the Cartesian space instruction to the joint space instruction;
50105Lookahead points are not continuous1. Program logical problems; 2.Dynamic parameters errors, there are parameters not covered in the reasonable range1. Modify program logic; 2. Check dynamic parameters; 3. Change the point position or the blending
50106$arThe starting point of the trajectory is greater than the ending point one, and the trajectory is unreasonable. Please execute PPToMain to reset the project or reload the programProgram logical problemsFor program logical problems, modify the point position of the program, or modify its blending
50107Generate the incorrect trajectory of the blendingInternal ErrorCancel the blending, change the size of the blending or the target point
50108The new trajectory was not obtained in time, and the motion stoppedSystem failure
50109The empty queue of the trajectory makes it impossible to execute the planningSet trajectory errorsAvoid generating the blending between the two reversed trajectories or reduce the length of the blending
50110Unable to get the initial position of the programUnable to get the initial position of the program1. Modify program logic; 2. Modify the size of the blending of the first trajectory
50111The positions of the two trajectories cannot connectThe positions of the two trajectories cannot connect1 Re-teach the point position; 2. Modify the size of the blending
50112Incorrect entered posesIncorrect entered poses1. Re-teach the pose, 2. If the current model is 3-axis or 4-axis robot, please check whether the entered pose matches the features of the current model
50113[WristSing]During the lookahead of the trajectory, the change of robot posture is over the limitation, the max change of posture is[WristSingthe change of robot posture is over the limitationPlease avoid singularities (refer to the manual for the relevant information):1. Re-teach the point position, and change the target point 2. Reset larger posture limitation 3. Try different type singular avoidence
50114During the lookahead, the axis exceeds the motion range. Stop the motion in advanceThe axis-angle motion exceeds the motion range1. Cancel the joint position limitation 2. Manually move each axis of the robot to the normal working range
50115There are singularities during the lookahead of the trajectory. Please avoid the singularitiesDuring the lookahead, the trajectory goes across the singularityPlease avoid singularities (refer to the manual for the relevant information): 1. Re-teach the point position, and change the target point; 2. Or change the Jog Mode and try to use Joint space Jog; 3. Or change the Cartesian space motion instruction to the joint space motion instruction
50116During the lookahead of the trajectory, if the joint of trajectories is a singularity , please avoid itThe joint of trajectories is a singularityPlease avoid singularities (refer to the manual for the relevant information): 1. Re-teach the point position, and change the target point; 2. Add wait0 after the incorrect trajectory
50117[WristSing]There are shoulder/elbow singularities during the lookahead of the trajectory. Please avoid the singularities or try different sing type[WristSing]During the lookahead, the trajectory goes across the shoulder/elbos singularityPlease avoid singularities (refer to the manual for the relevant information):1. Re-teach the point position, and change the target point 2. Try different sing type
50118[WristSing]During the lookahead of the trajectory, the end pos dose not match required value[WristSing]During the lookahead of the trajectory, the end pos dose not match required value, unable get a certain pathPlease avoid singularities (refer to the manual for the relevant information):1. Re-teach the point position, and change the target point 2. Try different sing type
50119Unable to open the singular avoidance when using trackUnable to open the singular avoidance when using trackclose the track
50120[WristSing]Search end point joint failed, unable to get end point joints degree, line num =[WristSing]Search end point joint failed. Probabaly because the end point is singular point or approach position limitation.Please avoid singularities (refer to the manual for the relevant information):1. Re-teach the point position, and change the target point 2. Try different sing type
50121[WristSing]Search path point failed because algorithm failed or target pose can't reach from recent position, unable to get path point joints degree[WristSing]Search path point joint failed. Probabaly because the end point is singular point or approach position limitation.Please avoid singularities (refer to the manual for the relevant information):1. Re-teach the point position, and change the target point 2. Try different sing type
50122Unable to open the singular avoidance when using fc modelUnable to open the singular avoidance when using fc modelclose the fc model
50123Singular avoidance doesn't support recent path type, please change to cartesian linear pathSingular avoidance doesn't support recent path type, please change to cartesian linear pathPlease change path type to cartesian linear
50124The angle between the upper and lower arms exceeds the safe rangeThe angle between the upper and lower arms exceeds the safe rangePlease change target point
50125The angle between the upper and lower arms exceeds the safe rangeThe angle between the upper and lower arms exceeds the safe rangePlease change motion type
50126During the lookahead, joint max speed exceeds limit1.The joint speed is set too small1.Increase the maximum joint speed
50127During the lookahead, joint max acceleration exceeds limit1.The joint acceleration is set too small1.Increase the maximum joint acceleration
50128During the lookahead, joint max jerk exceeds limit1.The joint jerk is set too small1.Increase the maximum joint jerk
50129The additional axis exceeds the range of motion,Its data mapping position isThe additional axis exceeds the range of motionModify ths soft limit or change the point
50201The Cartesian path encounters the unreachable pointThe Cartesian path encounters singularitiesChange the trajectory, or move to the target position through the joint space
50202The Cartesian path encounters illegal posesThe target point in the Cartesian path cannot match the configuration of the current robotRe-teach the target point, and change it the teaching point if the target point is manually entered
50203The sampling point is not on the sampling trajectoryInternal Error
50204Insufficient sampling points during the process of planning1. There are too many logic judgments or too much calculation of point positions inserted between the two motion instructions; 2. The state of the IPC is unstable, please check whether there is the non-xCore program operating in the robot1. Modify the RL project, and restart its operation; 2. Close the Linux background program of the non-xCore control system
50205Too much difference in adjacent instruction points during motion planningController error, there is a great difference in adjacent instruction points during motion planning, exceeding the limit1. Re-teach the target point position of the trajectory; 2.Try to change the type of the instruction, for instance, change MoveL to MoveJ; 3. Add wait0 after the incorrect trajectory to refresh the state
50206Incorrect internal calculation of path planningThe calculation of controller planning is incorrect1. Re-teach the target point position of the trajectory; 2.Try to change the type of the instruction, for instance, change MoveL to MoveJ; 3. Try to change the size of the blending of the trajectory and the expected speed; 4. Add wait0 after the incorrect trajectory to refresh the state
50207Not stopped at the end point of the pathIncorrect planning, and stop somewhere in the middle of the robot pathChange the specified motion parameters (the size of the blending, and the position of the target point), or change the pose of the target point, or change the motion instruction (such as change MoveL to MoveJ)
50208Trajectory internal errorTrajectory internal error1. Expand or reduce the blending. 2. Teach point positions again
50209The specified stopping distance is too short. Failed to stop within the specified stopping distanceThe specified stopping distance is too shortIncrease the stopping distance
50210The actual rotation angle reached in the Cartesian path differs significantly from the point's set value.The actual rotation angle reached in the Cartesian path differs significantly from the point's set value.Use the ConfL·off command to avoid this warning, or re-teach the target point with a rotation angle closer to the starting point.
50211During planning, constraints were found to be exceeded while stationary.1.The load value set is too high, exceeding the robot's capacity; 2. The robot's friction coefficient is too high; 3. The motor overload coefficient or transmission overload coefficient is too low; 4. Internal planning calculation error.1.Check whether the load value matches the actual load condition; 2. Check parameters such as the robot's friction coefficient, motor overload coefficient, and transmission overload coefficient; 3. Try changing the command format, such as switching from Cartesian space commands to joint space commands; 4. Please contact technical support.
50301The thread for motion planning is blocked. Execution timed outThe thread for motion planning is blocked. Execution timed outUse PPtoMain again to run projects or restart the controller
50302The thread for motion planning is blocked. Scheduling timed outSystem failureUse PPtoMain again to run projects or restart the controller
50303The thread for motion planning is blocked. Consecutive timeout over 5000 timesSystem failureUse PPtoMain again to run projects or restart the controller
50304No sufficient commands are sent from the planner to the EtherCAT threadSystem failure
50401Set max torque limit failedThe max torque limit is out of range, set parameter failedSet correct max torque limit
50501Tool and work object coordinate system settings conflictSet "handheld" for both work objects and toolsSelect correct tool and wobj
50502Tool and work object coordinate system settings conflictSet "external" for both work objects and toolsSelect correct tool and wobj
50503Robot motion failed. Tools and work objects have conflicting settings and are set as "handheld"Set "handheld" for both work objects and toolsSelect correct tool and wobj
50504Robot motion failed. Both tools and work objects have conflicting settings and are set as "external"Set "external" for both work objects and toolsSelect correct tool and wobj
50506Robot motion failed. Category 1 internal mode error of motion modulesInternal errorRestart robot. If the problem persists, contact technical support
50507Robot motion failed. Category 2 internal mode error of motion modulesInternal errorRestart robot. If the problem persists, contact technical support
50508Robot motion failed. Failed to reset module statusInternal errorRestart robot. If the problem persists, contact technical support
50509Robot motion failed. Failed to set motion start pointInternal errorRestart robot. If the problem persists, contact technical support
50510Robots motion failed. Failed to generate trajectoriesInternal errorRestart robot. If the problem persists, contact technical support
50511Failed to execute motion command.Current robot state does not permit to execute any movement.1.Interrupt current project and restart it from beginning 2.Reboot robot. If the problem persists, contact technical support
50512Robot motion failed. Number of axes mismatchesSoftware errorPlease contact the technical support
50513Robot motion failed. Invalid speed settingsSoftware errorPlease contact the technical support
50514Robot motion failed. Invalid step length settingsSoftware errorPlease contact the technical support
50515Robot motion failed. Invalid settings of coordinate systemsSoftware errorPlease contact the technical support
50516Robot motion failed. Invalid settings of motion axesSoftware errorPlease contact the technical support
50517End-effector rapid adjustment failed. Failed to calculate target point positions1. End-effector rapid adjustment failed due to special or extreme positionsTeach point positions again within the normal working range of robots
50518Motions failed. The current point position may be the target point positionThe current point position may be the target point position
50519Failed to generate trajectories. Unqualified target pointsTarget point positions may be out of robot working rangeTeach point positions again within the normal working range of robots
50520JOG mode error. Robot cannot translate in the specified direction. Modify the JOG modeThe current robot can only translate on the xz plane of the base coordinate, and cannot deviate from the xz plane of the base coordinate systemIt is recommended that to choose the base coordinate system or the joint coordinate system when modifying the JOG mode
50521JOG mode error. Robot cannot rotate in the specified direction. Modify the JOG modeThe rotating axes of the robot must be parallel to the Y-axis of the base coordinate system, or the robots rotate along the Z-axis of the flange coordinate systemIt is recommended that to choose the base coordinate system or the joint coordinate system when modifying the JOG mode
50522Trajectory error. 4-axis PCB robots do not support handheld work objects and external tools4-axis PCV robots do not support handheld work objects and external toolsReplace with handheld tools
50524JOG failed to open, missing key motion parametersThe current robot configuration file lacks key motion parameters and does not allow JOGConfirm that the configuration file is updated
50525The axis4 angle is not 0 or 180 degrees,please jog j4 to 0 or 180 degrees firstlyThe robot's axis4 angle is not 0 or 180 degrees,please jog j4 to 0 or 180 degrees firstlyThe robot's axis4 angle is not 0 or 180 degrees,please jog j4 to 0 or 180 degrees firstly
50526The flange is not parallel to the base,Please jog J4 and Ry first to make the flange parallel to the baseThe flange is not parallel to the base,it is not allowed to jog x y zPlease jog J4 and Ry first to make the flange parallel to the base
50527In the locked state, it is not supported to hold the workpieceIn the locked state, it is not supported to hold the workpieceit is supported to hold the tool
50528The flange is not parallel to the base,Please jog Ry to make the flange parallel to the baseThe flange is not parallel to the base,it is not allowed to jog x y zPlease jog Ry to make the flange parallel to the base
50529Robot motion failed. Invalid load settingsInvalid load settingsPlease check the load setting
50530Robot motion failed. The button is being clicked too frequently.The previous motion has not yet fully stopped, so the current motion cannot be initiatedIncrease the time interval between consecutive motions to prevent overly rapid clicks.
50531Rapid end-effector adjustment failed, please select the correct tool or the correct coordinate system1. The tool is an external tool, and the adjustment is based on a coordinate system that is the robot's base coordinate systemSelect the correct tool or the correct coordinate system
50532accuracy compensation status enabled, does not support singular avoidance and parallel pedestal jogWhen the precision compensation state is enabled, singular avoidance and parallel pedestal jog cannot be enabledTurn off precision compensation state
50533Failed to enter the lock axis state.Please check the current status and configuration of the robot and check the logsFailed to enter the lock axis state.Please check the current status and configuration of the robot and check the logsFailed to enter the lock axis state.Please check the current status and configuration of the robot and check the logs
50534The calibration error is too large to provide a reasonable calibration result.Please recalibration.The calibration error is too large to provide a reasonable calibration result.Please recalibration.The calibration error is too large to provide a reasonable calibration result.Please recalibration.
50535The workpiece coordinate system of the trajectory is incorrect,and it is bound to an additional axis that is not enable or does not exit,the error line num isThe workpiece coordinate system of the trajectory is incorrect,and it is bound to an additional axis that is not enable or does not exit.The workpiece coordinate system of the trajectory is incorrect,and it is bound to an additional axis that is not enable or does not exit.
50536Unactivated additional axis,not allowed to jog,please active the additional axis first.Unactivated additional axis,not allowed to jog,please active the additional axis first.Unactivated additional axis,not allowed to jog,please active the additional axis first.
50537When the workpiece is set to be held,it is not allowed to bind the workpiece to the additional axisWhen the workpiece is set to be held,it is not allowed to bind the workpiece to the additional axisWhen the workpiece is set to be held,it is not allowed to bind the workpiece to the additional axis
50601Dynamics disabled. Resetting the torque feedforward may cause a sudden power-on jitterTorque feedforward disabled. Torque feedforward resetEnable torque feedforward
50603VirbrationSuppression Failed
50604GravityCompensation Failed
50605Open Collision Detection delay compensation parameters identification failed, torque feedforward is closedtorque feedforward is closedOpen torque feedforward
50701$Command data lost during transmissionCommand data lost during transmissionRestart the program
50702The current configuration file does not match the controller version. The current configuration file version isThe configuration file does not match the controller version;Please download the latest version of the configuration file on the SW website and upgrade it to the controller;
50801Trajectory type is not supported in weaving modeWeaving mode does not support joint-space trajectory, pure rotation trajectory or trochoid trajectoryDo not use cartesian-space trajectory, pure rotation trajectory or trochoid trajectory
50802When the network is disconnected or unstable, the robot will stop moving.During JOG, motion to or quick adjustment, stop the robot movement to prevent machine collision due to network disconnection or network instability.Please check that the network connection is normal, ensure that the network environment is stable, and retry the JOG, motion to, or quick adjustment operation.

RL_Task

CodeError MessageCauseSolution
60000RL instruction parameter errorRL instruction parameter errorModify the instruction and enter the correct parameter.
60001SocketReadBit parameter errorRL encounters an error while running.Parameters of SocketReadBit must be multiples of 8.
60002SocketReadBit failed to read data.RL encounters an error while running.SocketReadBit failed to read data (data length mismatch).
60003SocketReadDouble illegally reads data.RL encounters an error while running.SocketReadDouble illegally reads data.
60004SocketReadDouble failed to read data.RL encounters an error while running.SocketReadDouble failed to read data (data length mismatch).
60005Failed to load RL project at .1. rsync configuration file is incorrect or missing. 2. The hmi version does not match. 3. The RL project file is accidentally modified. 4. Network failure.1. Configure the correct operating environment. 2. Check the corresponding HMI version. 3. Contact technical support.
60006Robot is running, unable to execute pptomain.Robot is running, pptomain is not allowed.Press Pause or Emergency Stop to shut down the robot.
60007The joint position limitation is not enabled. Single-step debugging is not allowed.The joint position limitation is not enabled. Single-step debugging is not allowed.Open joint position limitation settings in the setting interface.
60008Running speed synchronization failed. Cancel the next step.Running speed synchronization failed. Cancel the next step.Pause and restart the controller.
60009RL is running or the actuator encounters an error. The next step is rejected.RL is running or the actuator encounters an error. The next step is rejected.If RL is running, wait for RL to stop or click Pause; If the actuator encounters an error, click pp_to_main to re-execute.
60010Failed to start interpreter, unable to perform the next step.Failed to start interpreter, unable to perform the next step.Restart the controller or contact technical support.
60011An error occurred during RL task execution. The task stopped.An error occurred during RL task execution. The task stopped.Switch to the corresponding task to check the logic error near the program pointer, and after eliminating the error, pptomain will run again.
60012GetSocketConn() failed.The connection does not exist or has been disconnected.Execute this command after SocketConnect is connected.
60013GetSocketServer() failed.The connection does not exist or has been disconnected.Execute this instruction after SocketServer is in listening state.
60014Unable to start running the RL program.The program failed to start running because: 1) the robot is not powered on; 2) the robot is running.Make sure the robot is powered on and is not running.
60015Hot update of variables failed: the number of variables has exceeded the threshold.During hot update, the total number of global variables exceeded 20000.Please adjust array dimensions and remove redundant variables and data points to ensure the total number of variables does not exceed 20000.
60016Behavior tree overtime()Behavior tree work overtime.Check robots log has any other error
60017Reload project failed,variables are too much.1.Project variable overlimit 20000.Project variable overlimit
60100Parameter error of HexToDecRL encounters an error while running.The string entered by HexToDec must be a hexadecimal integer.
60101StrToByte parameter errorRL encounters an error while running.The string entered by StrToByte(string, \Hex) must be a hexadecimal integer.
60102StrToByte parameter errorRL encounters an error while running.The string entered by StrToByte(string) must be a decimal integer.
60103StrToByte parameter errorRL encounters an error while running.The string entered by StrToByte(string, \Okt) must be an octal integer.
60104StrToByte parameter errorRL encounters an error while running.The string entered by StrToByte(string, \Bin) must be a binary integer.
60105StrToByte parameter errorRL encounters an error while running.The string entered by StrToByte(string, \Char) must be ASCII characters.
60106The result of StrToByte overflows.RL encounters an error while running.The string data entered by StrToByte(string HEX) overflows.
60107The result of StrToByte overflows.RL encounters an error while running.The string data entered by StrToByte(string DEC) overflows.
60108The result of StrToByte overflows.RL encounters an error while running.The string data entered by StrToByte(string OKT) overflows.
60109The result of StrToByte overflows.RL encounters an error while running.The string data entered by StrToByte(string BIN) overflows.
60110The result of StrToByte overflows.RL encounters an error while running.The string data entered by StrToByte(string CHAR) overflows.
60111The range of the StrPart string exceeds the limit.RL encounters an error while running.The range of the StrPart string exceeds the limit.
60112The StrMatch parameter is too large to find.RL encounters an error while running.The StrMatch parameter is too large to find.
60113The value range of BitPos parameter of BitCheck instruction exceeds the limit.RL encounters an error while running.The value range of BitPos parameter of BitCheck instruction exceeds the limit.
60114The value range of BitPos parameter of BitClear instruction exceeds the limit.RL encounters an error while running.The value range of BitPos parameter of BitClear instruction exceeds the limit.
60115The value range of ShiftSteps parameter of BitLsh instruction exceeds the limit.RL encounters an error while running.The value range of ShiftSteps parameter of BitLsh instruction exceeds the limit.
60116The value range of ShiftSteps parameter of BitRsh instruction exceeds the limit.RL encounters an error while running.The value range of ShiftSteps parameter of BitRsh instruction exceeds the limit.
60117The value range of BitPos parameter of BitSet instruction exceeds the limit.RL encounters an error while running.The value range of BitPos parameter of BitSet instruction exceeds the limit.
60198Command failed
60200An error occurs during FcInit execution.An error occurs during FcInit execution.Modify the FcInit instruction to the correct instruction parameter.
60201An error occurs during FcStart execution.An error occurs during FcStart execution.Modify the FcStart instruction to the correct instruction parameter.
60202An error occurs during FcPause execution.An error occurs during FcPause execution.Modify the FcPause instruction to the correct instruction parameter.
60203An error occurs during FcRestart execution.An error occurs during FcRestart execution.Modify the FcRestart instruction to the correct instruction parameter.
60204An error occurs during FcStop execution.An error occurs during FcStop execution.Modify the FcStop instruction to the correct instruction parameter.
60205An error occurs during ClearFcError execution.An error occurs during ClearFcError execution.Modify the ClearFcError instruction to the correct instruction parameter.
60206An error occurs during SetControlType execution.An error occurs during SetControlType execution.Modify the SetControlType instruction to the correct instruction parameter.
60207An error occurs during SetJntCtrlStiffVec execution.An error occurs during SetJntCtrlStiffVec execution.Modify the SetJntCtrlStiffVec instruction to the correct instruction parameter.
60208An error occurs during SetCartCtrlStiffVec execution.An error occurs during SetCartCtrlStiffVec execution.Modify the SetCartCtrlStiffVec instruction to the correct instruction parameter.
60209An error occurs during SetCartNSStiff execution.An error occurs during SetCartNSStiff execution.Modify the SetCartNSStiff instruction to the correct instruction parameter.
60210An error occurs during SetLoad execution.An error occurs during SetLoad execution.Modify the SetLoad instruction to the correct instruction parameter.
60211An error occurs during StartOverlay execution.An error occurs during StartOverlay execution.Modify the StartOverlay instruction to the correct instruction parameter.
60212An error occurs during StopOverlay execution.An error occurs during StopOverlay execution.Modify the StopOverlay instruction to the correct instruction parameter.
60213An error occurs during PauseOverlay execution.An error occurs during PauseOverlay execution.Modify the PauseOverlay instruction to the correct instruction parameter.
60214An error occurs during SetSineOverlay execution.An error occurs during SetSineOverlay execution.Modify the SetSineOverlay instruction to the correct instruction parameter.
60215An error occurs during SetLissajousOverlay execution.An error occurs during SetLissajousOverlay execution.Modify the SetLissajousOverlay instruction to the correct instruction parameter.
60216An error occurs during SetJntTrqDes execution.An error occurs during SetJntTrqDes execution.Modify the SetJntTrqDes instruction to the correct instruction parameter.
60217An error occurs during SetCartForceDes execution.An error occurs during SetCartForceDes execution.Modify the SetCartForceDes instruction to the correct instruction parameter.
60218An error occurs during RestartOverlay execution.An error occurs during RestartOverlay execution.Modify the RestartOverlay instruction to the correct instruction parameter.
60219An error occurs during SetSensorUseType execution.An error occurs during SetSensorUseType execution.Modify SetSensorUseType to the correct parameter.
60220An error occurs during CalibSensorError execution.An error occurs during CalibSensorError execution.Modify CalibSensorError to the correct parameter.
60221An error occurs during FcCondForce execution.An error occurs during FcCondForce execution.Modify the FcCondForce instruction to the correct instruction parameter.
60222An error occurs during FcCondPosBox execution.An error occurs during FcCondPosBox execution.Modify the FcCondPosBox instruction to the correct instruction parameter.
60223An error occurs during FcCondTorque execution.An error occurs during FcCondTorque execution.Modify the FcCondTorque instruction to the correct instruction parameter.
60224An error occurs during FCCondWaitWhile execution.An error occurs during FCCondWaitWhile execution.Modify the FCCondWaitWhile instruction to the correct instruction parameter.
60225An error occurs during FcCondOrient execution.An error occurs during FcCondOrient execution.Modify the FcCondOrient instruction to the correct instruction parameter.
60226An error occurs during FcCondPosSphere execution.An error occurs during FcCondPosSphere execution.Modify the FcCondPosSphere instruction to the correct instruction parameter.
60227An error occurs during FcCondPosCylinder execution.An error occurs during FcCondPosCylinder execution.Modify the FcCondPosCylinder instruction to the correct instruction parameter.
60228An error occurs during FcCondTcpSpeed execution.An error occurs during FcCondTcpSpeed execution.Modify the FcCondTcpSpeed instruction to the correct instruction parameter.
60229Inverse kinematics of CalcJointT failed.The conf error of Cartesian coordinatesModify the entered Cartesian coordinates.
60300ReplayPath playback rate exceeded limit.RL encounters an error while running.ReplayPath playback rate exceeded limit.
60400RL call hierarchy exceeds limit.RL encounters an error while running.RL call hierarchy exceeds limit.
60500Cannot load multiple motion tasks.Cannot load multiple motion tasks.Assign only one task as the motion task.
60501The predecessor task cannot be itself[].The predecessor task cannot be itself.Modify predecessor tasks to other tasks.
60502Motion task is not allowed to set predecessor task[].Motion task is not allowed to set predecessor task.Motion task is not allowed to set predecessor task.
60503The motion instruction cannot hold the workpiece and the tool at the same time.The motion instruction cannot hold the workpiece and the tool at the same time.Modify the instruction for the tool and wobj parameter.
60504Invalid Search instruction input signalThe signal type is neither a DI signal nor registerUse the correct DI signal or register.
60505The Search instruction failed to record the point position.The tool and the workpiece are simultaneously hand-held or external.Modify parameters and use tools and workpieces at different positions.
60506The RL instruction [] failed to register the IO event.The DI signal does not exist or has been set as the system input.Modify the parameter and use the DI signal that is not set as the system input.
60507SearchL \Stop instruction, the speed is greater than v100.The robot can be stopped quickly only when the speed is less than or equal to v100.Use a smaller speed parameter.
60508SearchC \STOP instruction, the speed is greater than v100.The robot can be stopped quickly only when the speed is less than or equal to v100.Use a smaller speed parameter.
60509Wrong program state, cannot perform the next step.1. Cannot reach the motion instruction point; 2. Move through a singular point;1. Check the list of point positions; 2. Optimize the motion trajectory; 3. Click PPtoMain.
60510The RL instruction runs too slowly .Tcp < 1μm/s or ori < 1e-6°/s or jnt < 1%;The motion instruction adopts a proper speed parameter.
60511The drag playback path is missing/does not exist .The drag playback path is missing/does not exist.Record/use a valid playback path.
60512Enabling the drag playback failed .Drag playback function errorCheck whether the drag playback function is effective.
60513HomeSet instruction range error .Setting the home point angle exceeds the limit.Modify the angle of the Home point to be within the hard limit range of the robot.
60514Saving the Home parameter failed. instructionRobot configuration module errorTry restarting the robot or contact the manufacturer.
60515The axis specified by HomeSetAt does not exist.The axis specified by HomeSetAt does not exist.Modify the parameters of HomeSetAt.
60516The HomeClr instruction failed.Robot configuration module errorTry restarting the robot or contact the manufacturer.
60517Wrong number of HomeSet parametersWrong number of HomeSet parametersModify the number of parameters to that of the robot axes.
60518Wrong number of Hordr parametersWrong number of Hordr parametersModify the RL file and transfer the correct Hordr parameters.
60519Hordr parameters are limited to 0~10 .Hordr parameter value errorModify the RL file and transfer the correct Hordr parameters.
60520HordrAt 0 <= Parameter < = Number of robot axes, input []HordrAt parameter value errorModify the RL file and transfer the correct Hordr parameters.
60521GetEndtoolTorque tool is not compatible with the workpiece.The tool and the workpiece are simultaneously hand-held or external.Modify the GetEndtoolTorque instruction and transfer the correct tool, wobj parameter.
60522GetEndtoolTorque end coordinate system type errorUndefined end coordinate system typeModify the GetEndtoolTorque instruction and transfer the correct type parameter of coordinate systems: 0-2.
60523AccSet parameter exceeds the limit range of 30% ~ 100%.AccSet acceleration and jerk are limited to 30% ~ 100%.Modify the AccSet instruction parameter.
60524Variable quaternion parameter errorThe sum of squares of quaternions of variables should be equal to 1.Modify the corresponding quaternions to correct value.
60525OpenDev port format errorAvailable ports [0, 65535]Modify the OpenDev port to the correct value.
60526Starting program failed due to robot is in error state. Please check recently error record.Starting program failed due to robot is in error state. Please check recently error record.1.Fix RL-Language error or logic error; 2.PPtoMain and restart program
60527Trigger instruction parameter errorThe trigdata set by TrigVar instruction does not existCreate the target var to modify and set the trigdata with TrigVar instruction.
60528Trigger instruction parameter errorThe DO/GO/register variable set by trigdata does not exist; or the output signal is not set; or the register is not writable; or is bind by CrossConnectionCreate the output signal (or a writable register) and set it with TrigIO/TrigReg instruction.
60529Failed to start RL program. The robot is busy.1. The robot is running and cannot be started repeatedly; 2. The RL file is being parsed and cannot be started.Wait for the register function code "sta_robot_is_busy" to turn to 0 before sending the start instruction
60530Userframe [] is duplicated, this userframe may work incorrectlyThe input userframe is duplicated by exist userframe, this userframe may work incorrectlyPlease check the userframe list and make sure which frame is needed and delete the wrong frame
60531Tray data update failed1. Tray name or workpiece No. Error. 2. Failed to obtain data from tray module. 3. Tray variable value update1. Check whether the parameter input in the "TrayUpdate" function is incorrect. 2. Contact after-sale.
60532Failed to obtain workpiece quantity of tray1.Tray name error. 2. Failed to obtain data from tray module.1. Check if tray name error occurs. 2. Contact after-sale.
60533Failed to update palletizing data1. The stacking name or workpiece number is wrong or the layer number is wrong. 2. Failed to obtain data from the palletizing module. 3. Stack variable value update failed.Check whether the parameter input in the "PalletUpdate" function is incorrect
60534Failed to get the number of palletizing layers, the name"" does not existWrong palletizing nameCheck the "PalletLayerCount" function input parameter
60535Failed to get the number of palletized workpiecesWrong palletizing name or layer numberPlease check the "PalletWobjCount" function input arguments
60537Invalid tool or wobj or userframe, check the log content for reasonTool or wobj load error, possible reasons: 1. Tool or tool_load has wrong quaternion parameter; 2. Wobj or its related userframe has wrong quaternion parameter; 3. Wobj failed to relate userframe, need to re-edit wobj.Edit and update related tools or wobjs or userframes
60538Movement trajectory param is error.Movement trajectory param is errorPlease reset the correct motion parameters.
60600Failed to obtain parameters during laser weldingFailed to obtain laser welding configuration parameters. Procedure1. Check whether the laser welding process parameter table is created. 2. Check whether the corresponding parameters in the laser welding process parameter table are correct. 3. An internal laser welding error occurs. Contact the manufacturer
60601Laser welding setup parameters failedError in laser welding setup parameters1. Check the laser welding port configuration to confirm whether the register or IO configuration of the error signal is wrong
60602After the laser welding single step, please perform the PPToMain operation first before continuing the operationAfter a single step of laser welding, the switch is not allowed to continue runningAfter a single step of laser welding, it is not allowed to switch to continue running, please perform PPToMain operation first
60603Laser welding does not support running from the cursorLaser welding does not support running from the cursorLaser welding does not support running from the cursor
60604Laser welding process documentation [] does not existThe laser welding process file does not existPlease check that the process file in the laser welding instruction has been created
60605The current moving target point coincides with the laser welding start or end pointThe current moving target point coincides with the laser welding start or end point, and the laser welding timing cannot be triggered normally1. Check the target point of the error motion command so that the target point does not coincide with the current robot position
60606The laser welding function is turned off, do not use the laser welding commandThe laser welding function switch is off1.Turn on the laser welding function switch 2.Delete the laser welding instruction
60607Unable to respond to external program start signal, there is currently an error alarm in the controller, which needs to be manually cleared before startingThere is an error alarm in the current controllerManually clear the alarm before starting
60608Failed to switch project through socket instruction1.Switch to non-existent projects, 2.There are non semi static tasks running1.Switch existing projects, 2.Stop the running task before proceeding with project switching
60610Currently, registers or system IO with program pause function do not reset, and program startup is not allowed. SpecificallyCurrently, there are registers or system IO with program pause function do not resetReset the registers and system IO bound with program pause function
60611Robot is saving diagnose data, can't start run programRobot is saving diagnose data, can't start run programWait 10s and restart again
60612Configure tool and wobj are conflict, using the last correct configurationThe tool-wobj configured in the upper right corner of the teach pendant (HMI) cannot be calculated by the robot. They are both rob-hold or not rob-holdCorrectly configure the rob-hold tool or rob-hold wobj to avoid conflicts
60613Configure tool and wobj are conflict and robot cannot moveThe tool-wobj configured in the upper right corner of the teach pendant (HMI) cannot be calculated by the robot. They are both rob-hold or not rob-holdCorrectly configure the rob-hold tool or rob-hold wobj to avoid conflicts
60614Joint position limitation is disabled, can't start run programJoint position limitation is disabledEnable joint position limitation
60615Soft shutdown is triggered, can't start run programSoft shutdown is triggeredIt is not suggested to start program at this state
60700Command execution of Jodell device failedThe command execution fails due to the abnormal communication between the terminal and the Jodell deviceCheck the hardware connection and retry the execution
60701Command execution of RM device failedThe command execution fails due to the abnormal communication between the terminal and the RM deviceCheck the hardware connection and retry the execution
60702Command execution failure for opening fourth axis lockFailure to meet the fourth axis locking opening conditions resulting in opening failurePlease check if the current angle of the fourth axis is 0 ° or 180 °
60703Command execution failure for closing fourth axis lockFailure to meet the fourth axis locking closing conditions resulting in closing failure
60704Command execution failure for opening SingAreaWristFailed to open SingAreaWrist due to not meeting the opening conditionsPlease check whether the openning conditions are met
60705Command execution failure for closing SingAreaWristFailed to close SingAreaWrist due to not meeting the closing conditions
60706Command execution failure for opening SingAreaJointWayFailed to open SingAreaJointWay due to not meeting the opening conditionsPlease check whether the openning conditions are met
60707Command execution failure for closing SingAreaJointWayFailed to close SingAreaJointWay due to not meeting the closing conditions
60708Robots that are not in standard six axis configuration or CR six axis configuration are not allowed to use the SingAreaLockAxis4 commandRobots that are not in standard six axis configuration or CR six axis configuration are not allowed to use the SingAreaLockAxis4 commandDo not use the SingAreaLockAxis4 command or replace the robot
60709Robots that are not in standard six axis configuration or CR, ER six axis configuration are not allowed to use the SingAreaWrist commandRobots that are not in standard six axis configuration or CR, ER six axis configuration are not allowed to use the SingAreaWrist commandDo not use the SingAreaWrist command or replace the robot
60710Robots with non-standard six axis configurations are not allowed to use the SingAreaJointWay commandRobots with non-standard six axis configurations are not allowed to use the SingAreaJointWay commandDo not use the SingAreaJointWay command or replace the robot
60711The SingAreaLockAxis4 command is not allowed in non motion tasksThe SingAreaLockAxis4 command is not allowed in non motion tasksMove the SingAreaLockAxis4 command to a motion task
60712The SingAreaWrist command is not allowed in non motion tasksThe SingAreaWrist command is not allowed in non motion tasksMove the SingAreaWrist command to a motion task
60713The SingAreaJointWay command is not allowed in non motion tasksThe SingAreaJointWay command is not allowed in non motion tasksMove the SingAreaJointWay command to a motion task
60714Unable to resume continuous operation, a special emergency stop or collision detection has occurred1.Emergency stop planning timeout, controller anomaly; 2.Emergency stop or collision detection occurred during the process of returning to the pathPPToMain and restart
60716Device initialization execution failedHardware model mismatch or incorrect connectionCheck the connection or if the tool model matches
60717Command execution of Dh device failedThe command execution fails due to the abnormal communication between the terminal and the Dh deviceCheck the hardware connection and retry the execution
60800Unsupported move typesThe conveyor wobj only supports MoveL and MoveC motion typesChange to MoveL or MoveC
60801Conveyor belt, rail, and positioner do not support backward step.Conveyor belt, rail, and positioner do not support backward step.Use pptoline or jog instead of backward step.
60802The current controller state does not allow mode switching.The current controller state does not allow mode switching.Try pptoline to reset advance pointer
60803Task() is not a motion task, can not stepbackTask is not a motion task, can not stepbackChoose a motion task for debug in RL editor
60804Task() was finished, can not stepbackTask was finished, can not stepbackTry pptomain or pptoline instead of stepback
60805Task was finished or the task pointer was in the status that can't change work modeTask was finished or the task pointer was in the status that can't change work modeTry pptomain or pptoline to debug
60806Trajectory first command failed in stepback modeTrajectory first command failed in stepback modeTry reset teaching point position
60807Trajectory move failed in stepback modeMovement command's arguments was invalid1.Try reset teaching point position 2.Check RL program's input or logic
60900Unsupported tool or wobjThe tool and wobj cannot be both handheld or external at the same time
60901Robotiq 2F_85 Init failed1.Abnormal communication between the end and Robotiq device resulted in instruction execution failure;2、Robotiq device ID Error1.Check the hardware connection and execute it again;2.Enter the correct ID and execute again
60902Robotiq 2F_85 Get status failed
61000Torque threshold setting failedCondition not met, torque threshold setting failed
61001Collision detection not enabled, MotionSup On command cannot be usedCollision detection not enabled, MotionSup On command cannot be usedEnable collision detection
61002Error getting envelope informationIncorrect getting of envelope information
61003Obtaining the nickname of the pallets failedFunction stack number errorPlease enter the correct number number
61004Failed to trigger interrupt:. Task does not exist.Task does not exist.
61005Failed to trigger interrupt:. Non sports tasks do not trigger interrupts.Non sports tasks do not trigger interrupts.Please set interrupts in the exercise task.
61006Failed to trigger interrupt. There are interrupts that have been triggered but not executed.There are interrupts that have been triggered but not executed.Please trigger another interrupt after one interrupt is completed
61007Failed to trigger interrupt. Single step mode, \DEBUG option not selected, this interrupt will not trigger.Single step mode, \DEBUG option not selected, this interrupt will not trigger.If you want to trigger an interrupt in single step mode, please select the \DEBUG option.
61008Failed to trigger interrupt, in continuous mode pause state, the interrupt is not triggered.Continuous mode - paused state, the interrupt is not triggered..If you want to trigger an interrupt in pause mode, select the \ \ DEBUG option and switch to single step mode
61009Failed to trigger interrupt. Task is resetting, this interrupt will not trigger.Task is resetting, this interrupt will not trigger.
61010Failed to trigger interrupt. Task is executing interrupt, this interrupt will not trigger.Task is executing interrupt, this interrupt will not trigger.Please trigger another interrupt after one interrupt is completed
61011Failed to trigger interrupt:. The interrupt function does not exist.The interrupt function does not exist.Please check if the interrupt function exists.
61012Failed to trigger interrupt. Interpreter coroutine is full.Interpreter coroutine is full.
61013Failed to trigger interrupt. Please trigger an interrupt during task execution.Task runs to the endproc.Please trigger an interrupt during task execution.
61014Failed to trigger interrup. Interrupt is turned off, note: if triggered once, it should not respond.Interrupt closed by IDisablePlease trigger the interrupt after IEable
61015An instruction that is not allowed to be executed within the interrupt function has been executedAn instruction that is not allowed to be executed within the interrupt function has been executedDo not execute instructions that are not allowed within interrupt functions
61017Trigger interrupt failed, does not respond to interrupt
61018The program is not synchronized to the controller, and starting the program via system IO, register function code, or external communication is prohibited.The program changes in the HMI have not been synchronized to the controller, and starting the program via system IO, register function code, or external communication is prohibited.Please click pptomain or perform a reload operation via the teach pendant before executing the program startup operation.
61019The tool used by recipe was found to be inconsistent with the tool currently used in the project when running the programThe tool configuration used in the project was changed, but the recipe file was not synchronized and updatedUpdate the recipe to match the tool used in the project, and then rerun the program
61020This model does not currently support this functionThis model does not currently support the vibration suppression function
61030Execution of motion command failedPathRecStart has been executed and path recording has been enabled. This instruction cannot be recordedCannot execute unrecorded motion commands between PathRecStart and PathRecStop
61031Record path related instruction execution failed
61032Failed to update palletizing data1. The stacking name or workpiece number is wrong or the layer number is wrong. 2. Failed to obtain data from the palletizing module. 3. Stack variable value update failed.Check whether the parameter input in the "PalletUpdateByUniversal" function is incorrect
61033Failed to get the number of palletizing layers, the name"" does not existWrong palletizing nameCheck the "PalletLayerCountByUniversal" function input parameter
61034Failed to get the number of palletized workpiecesWrong palletizing name or layer numberPlease check the "PalletWobjCountByUniversal" function input arguments
61035DataToBytes instruction parameter errorPlease check the parameters passed to the "DataToBytes" function
61036BytesToData instruction parameter errorPlease check the parameters passed to the "BytesToData" function
61037SetVDI instruction parameter errorSetVDI instruction Error, Possible reasons: 1.The signal is not a virtual DI signal; 2.The signal has already been bound to a cross-connection.Please check the parameters passed to the "SetVDI" instruction
61038PulseVDI instruction parameter errorPulseVDI instruction Error, Possible reasons: 1.The signal is not a virtual DI signal; 2.The signal has already been bound to a cross-connection.Please check the parameters passed to the "PulseVDI" instruction
61050Hardware status alarmHardware status alarm
61060Mechanical unit activation failed, existing servo welding gun is in an activated stateThe servo welding gun is already in an activated statePlease set other servo welding guns to inactive state before activating this welding gun
61061Mechanical unit activation status change failedThe mechanical unit does not existPlease enter the correct mechanical unit
61062Failed to modify the activation status of the mechanical unit.Mechanical unit not enabledEnable the mechanical unit and then modify its activation status
61063The mechanical unit is enabled and path recording cannot be performedThe mechanical unit is enabled and path recording cannot be performedAfter the mechanical device is stopped, record the path
61064Wobj update failed, the selected mechanical unit cannot bind the wobjThe selected mechanical unit cannot bind the WobjModify associated mechanical units
61065The modification of the mechanical unit activation status failed, as the selected mechanical unit is associated with a non-existent servoThe selected mechanical unit is associated with a non-existent servoCheck the servos associated with the selected mechanical unit