In Yaskawa systems, the code A.910 is an Overload Warning. This minor fault or alarm typically indicates that the motor is drawing current near its rated capacity and is on the verge of a critical overload trip (such as A.710 or A.720). Report for Yaskawa Error Code A.910 Description Alarm Name Overload Warning Status Minor Fault/Warning (ALM LED usually flashes) Primary Meaning
The drive has detected a load that exceeds the motor's continuous rating for a specific duration, but has not yet reached the trip point. Common Causes
Mechanical Issues: Excessive load due to mechanical friction, binding, or a sudden obstruction in the machine.
Operating Conditions: The starting torque exceeds the maximum allowed torque, or the motor is operating at peak capacity for too long.
Wiring Faults: Incorrect or loose contact in the servomotor or encoder wiring.
Environmental Factors: High ambient temperature inside the SERVOPACK panel (exceeding 55∘C55 raised to the composed with power C
Parameter Settings: The overload warning level (parameter Pn52B) is set too low for the current application. Recommended Corrective Actions
Check Mechanical Load: Inspect the connected machinery for jams, lack of lubrication, or increased friction.
Verify Wiring: Ensure all motor and encoder cable connections are secure and correctly pinned.
Adjust Parameters: If the load is normal but the warning is premature, verify the setting of Pn52B (Overload Warning Level).
Cooling Check: Ensure panel fans are operational and the temperature is within the specified range ( 55∘C55 raised to the composed with power C
Monitor Operation: Use the monitor function (e.g., Un006 for motor load ratio) to see how close the system is to a full overload alarm. Note on Robot Controllers DX100 ALARM CODE 0910 CPU ERROR (YCP01)
DX100 ALARM CODE 0910 CPU ERROR (YCP01) – Yaskawa Motoman. Yaskawa Knowledge Center NX100 ALARM CODE 0910 CPU ERROR (NCP01)
In the world of high-precision motion control, the Yaskawa error code A.910 is a specific warning signal used primarily in Sigma-5 and Sigma-7 series servo drives.
While it may seem urgent, A.910 is technically a warning (minor fault) rather than a hard alarm. It serves as a preemptive notification that the system is approaching an overload condition. Ignoring this warning typically leads to a full system shutdown via A.710 (Instantaneous Overload) or A.720 (Continuous Overload) alarms. What Does Error Code A.910 Mean?
The A.910 error signifies an Overload Warning. By default, Yaskawa drives trigger this warning when the system reaches 20% of the time required to hit a critical overload alarm threshold. It is a safety feature designed to protect the servomotor from overheating or mechanical damage by giving operators time to adjust the load or duty cycle before a shutdown occurs. Primary Causes of A.910 yaskawa error code a910
Several factors can trigger this warning, ranging from mechanical fatigue to improper parameter configuration:
Excessive Mechanical Load: The most common cause is a load that exceeds the motor's rated torque capacity due to mechanical binding or increased friction in the system.
Aggressive Duty Cycles: High-frequency acceleration and deceleration or operating at peak torque for extended periods can build up heat faster than the motor can dissipate it.
Improper Parameter Settings: The threshold for this warning is controlled by parameter Pn52B (Overload Warning Level). If this is set too low (e.g., 10–20%), the warning may appear prematurely during normal operation.
Wiring or Feedback Issues: Faulty contact in the motor or encoder cables can cause the drive to "misread" the torque requirements.
Capacity Mismatch: If the SERVOPACK and servomotor capacities are not properly matched, the drive may struggle to maintain current levels, triggering an early warning. Troubleshooting & Remediation Steps
To resolve an A.910 error and prevent it from escalating to a hard stop, follow these diagnostic steps: Yaskawa.eu.com Σ-7C SERVOPACK - Troubleshooting Manual
The Yaskawa error code A.910 is not a fatal "fault" that stops the machine immediately, but a Warning for Overload. It is essentially the drive’s way of saying, "I am working too hard, and if this continues, I will shut down to protect myself."
Here is a story of a long night on the factory floor, illustrating how this error occurs and how to fix it. The Ghost in the Assembly Line: A Tale of A.910
The clock on the wall of the automotive plant read 2:14 AM when the line stuttered.
Jack, the head maintenance tech, didn't need to hear the alarm to know something was wrong. He could feel it in the floorboards—a subtle change in the vibration of the Sigma-7 servo motors that powered the main conveyor. He walked over to the control panel of the lead SERVOPACK. The small seven-segment display was blinking a steady, rhythmic code: A.910. The Warning Before the Storm "At least it's not an A.710 yet," Jack muttered.
He knew A.910 was the "Overload Warning". It meant the motor was drawing more torque than it was rated for, but hadn't yet reached the breaking point where it would trigger a hard fault (A.710 or A.720) and crash the line. The drive was giving him a chance to fix it before the thermal protection kicked in. The Investigation
Jack started his mental checklist, knowing the common culprits for an A.910: Mechanical Friction: Was a bearing seizing up?
Wiring Issues: Was there a loose contact in the motor or encoder cables?
Parameter Sensitivity: Was the warning level (Pn52B) set too low for the current job? Environment: Was the control cabinet overheating? In Yaskawa systems, the code A
He grabbed his infrared thermometer. The SERVOPACK panel was at 48°C—warm, but well below the 55°C limit. Heat wasn't the ghost tonight. Finding the Friction
Jack moved to the conveyor belt itself. He noticed a slight buildup of debris near the drive pulley—metal shavings from the day shift had wedged themselves into the guide rail. Every time the servo tried to accelerate the heavy pallet, it had to fight through that extra resistance. The motor was pulling 110% of its rated torque just to keep up. "There you are," he said. The Resolution
Jack cleared the debris and reapplied high-temp grease to the rails. He returned to the panel and watched the load monitor (Un002). The torque percentage dropped from the "danger zone" back down to a comfortable 65%.
He didn't even have to reset the drive; because A.910 is a warning, it cleared itself once the operating conditions returned to normal. The conveyor sped back up, the "Ghost" was gone, and the factory floor returned to its steady, industrial hum. Technical Summary of A.910 🛠️ Alarm Name Overload Warning Severity
Minor (Warning) - Does not always stop the motor immediately. Triggers
Occurs when torque or current exceeds the rated level for a period of time. Next Step
If ignored, will lead to hard faults A.710 (High Load) or A.720 (Low Load). Common Fixes
Check Mechanicals: Look for jams, binding, or lack of lubrication.
Verify Wiring: Ensure U, V, and W power phases and encoder cables are secure.
Adjust Parameters: Check Pn52B (Overload Warning Level). If the application naturally runs high, this may need to be increased slightly.
Resize Motor: If the load is consistently too heavy, a higher-capacity motor/drive combo may be required. If you are currently facing this error, let me know:
Which Yaskawa series are you using (Sigma-5, Sigma-7, etc.)?
Does the error happen at startup or during a specific movement? Have you recently changed the load or the program? Table 1 - Yaskawa
The Yaskawa A.910 error code is a common Overload Warning typically found on Sigma-series servo drives, such as the Sigma-7, Sigma-5, and Sigma-3. It serves as a pre-alarm notification that the motor or drive is operating near its thermal limit, allowing operators to intervene before a full shutdown (like an A.710 or A.720 fault) occurs. Understanding the A.910 Alarm
Unlike a hard "Fault," the A.910 is classified as a Warning. This means the motor will generally continue to run, but the drive’s digital operator will flash the code to indicate that the operation has exceeded the overload protection characteristics. Primary Causes and Remedies Potential Cause Recommended Remedy Mechanical Obstruction A: Unlikely
Check the machine for jams, excessive friction, or worn bearings that increase the physical load on the motor. Wiring Issues
Verify that the servomotor and encoder cables are correctly wired and that there are no faulty contacts or loose connections. Operational Overload
Reduce the operation speed, lower the cycle frequency, or decrease the overall load applied to the motor. High Ambient Temp
Ensure the SERVOPACK panel temperature is below 55°C. Check cooling fans and ventilation filters for clogs. Parameter Settings
Check parameter Pn52B (Overload Warning Level). If it is set too low for your application, it may trigger the warning prematurely. Troubleshooting Steps
Monitor Current Consumption: Use the drive's monitor mode (e.g., Un002 for torque reference) to see if the motor is consistently drawing current near its rated limit.
Clear the Warning: If the cause is temporary, you can often clear the warning by cycling the power or using a "Warning Reset" command via the digital operator or SigmaWin+ software.
Check Hardware Integrity: If the warning persists even with no load, the internal current detection circuit of the SERVOPACK may be faulty, requiring a replacement of the drive unit.
For robotic applications specifically using the FS100 controller, a similar code (0910) may indicate a CPU Error, typically requiring a controller restart or hardware inspection.
Here is the detailed content regarding the Yaskawa Error Code A910.
This error appears primarily on Yaskawa V1000, J1000, U1000, and GA800 series drives.
A: Unlikely. As noted in Step 3, if the error persists with the motor disconnected, the motor is not the cause. However, a faulty motor (phase-to-phase short) can sometimes trigger the fault. Test with motor disconnected first.
For drives powered by separate control terminals (e.g., S1, S2 for 24VDC), an unstable control supply can sometimes miscommunicate with the main board, indirectly causing a main circuit undervoltage detection logic fault.
Check Parameter Settings:
Inspect the Mechanical Load:
Adjust Acceleration Times: