Error Type: Communication error between the drive and the keypad, option board, or host controller.
Common Causes:
Typical Solutions:
| Step | Action | |------|--------| | 1 | Power cycle the drive – sometimes clears temporary comm glitches. | | 2 | Check connections – reseat keypad cable, option module, or network cable. | | 3 | Inspect for damage – replace any frayed or crushed cables. | | 4 | Verify parameters – ensure baud rate, parity, and stop bits match between drive and master. | | 5 | Reduce noise – separate control wiring from power cables; use shielded twisted pair cable. | | 6 | Test without option board – if error stops, the board may be faulty. | | 7 | Replace keypad or cable if error persists with local keypad only. |
Affected Yaskawa Series:
Common on V1000, J1000, GA700, GA800, U1000, and A1000 drives.
Manual Reference:
See Yaskawa Technical Manual TOEP C710606 (V1000) or relevant series manual – section on "Faults and Alarms" (A910 = "Keypad/Communication Option Error").
Symptom: A910 appears every Monday morning after a weekend washdown. Root Cause: Humidity condensation on the option card pins. Fix: Installed dielectric grease on the card edge and changed the drive location from below the wash zone to a NEMA 4X enclosure.
For 90% of A910 applications involving hoists or high-inertia fans, the "Speed Search" function is the fix.
If the motor is standing still but the drive trips instantly on A910, you likely have a noise issue.
The factory hummed like a living thing—motors whispering, conveyors breathing, and the faint, patient tick of a clock that kept everyone honest. Lin, the night-shift technician, liked to think of it as orchestral: every servo a violin, each sensor a cymbal. Tonight, however, a sour note cut through the music: a steady orange lamp on Panel H, and the display reading A910.
Lin set down her toolbox and ran a practiced hand over the panel. "Link," the fault code read. She loved machines for their blunt honesty; when they failed, they told you where it hurt. A910. Link failure. The words conjured images of broken chains and mismatched parts—things that could be fixed.
She flashed back to the day she first learned to read error codes. Her mentor, Old Mateo, had said, "An error code is the machine whispering. Don't shout back—listen." Lin bent closer and listened: the Ethernet LEDs blinked irregularly, a nervous stutter. The network map on her tablet showed a dark patch where Servo B should have been singing in green.
The line had to run by dawn—the order queue would bankrupt them if a whole pallet station stayed down. Lin pulled on gloves and walked the cable runs. Connectors were snug, then fretted; the patch panel showed no obvious damage. She reseated a plug, and the A910 flickered into a new annoyance—A102, then vanished. Progress.
"Come on," she murmured, following the digital breadcrumbs to the servo drive itself. The drive's casing felt warm, not hot—telling her this wasn't an overcurrent crisis. She traced the communication chain: PLC to switch to drive. The managed switch’s log revealed a pattern—intermittent link drops at 2:17 a.m., 2:34 a.m., 2:51 a.m., exactly every seventeen minutes. yaskawa error code a910 link
Seventeen minutes. Not a coincidence. Lin shuffled through the plant’s maintenance calendar and found the culprit: at 2:30 a.m., the HVAC system ran a self-calibration that pinged the building network, flooding the switch with traffic. The timing matched the switch hiccups. The A910 was not a dead wire; it was being drowned out by noise.
She could have alerted the engineers and scheduled a formal fix, but the clock was merciless. Lin jacked into the switch console and set a quality-of-service rule to prioritize PLC traffic—small, surgical, and temporary. The LED on the drive steadied from a tense blink to a calm, reliable pulse. Panel H exhaled as its orange light died.
By three in the morning, the conveyor flowed again. Lin watched packages slip smoothly onto the pallet, and for a moment the whole factory felt like it had forgiven her. She logged the incident: A910—intermittent link loss due to HVAC network surge; temporary QoS fix; recommended permanent VLAN segmentation and shielded cabling. Old habits die hard; she wrote the note in her neatest hand.
Mateo found her at the vending machine, sipping tepid coffee. He grinned at the log on her tablet. "You fixed the whisper."
"I filtered the shout," she corrected. "But it's only a bandage."
He nodded. "Machines use codes because they lack patience for stories. You gave it one tonight anyway."
Weeks later, the engineering team upgraded the network: dedicated plant VLANs, new shielded cable runs, and a firmware update for the switch. When they closed the ticket, they stamped it with A910 and a concise summary. Lin printed the final report and tucked it into a binder labeled INCIDENTS—like a captain stowing away a map.
On the next quiet night shift, Lin reopened the binder and read the A910 entry. In the margin she had written a small note: "Listen for patterns. Machines lie in timing."
A freight truck rolled past the loading bay, and the factory's orchestra resumed its steady, honest hum. The lights on Panel H stayed green. Lin walked the line once more, listening, because sometimes the most human thing you can do for a machine is simply to pay attention.
Understanding the Yaskawa A.910 Error Code: Causes and Solutions
The Yaskawa A.910 error code is a common overload warning primarily associated with Sigma-series servo drives, such as the Sigma-7 and Sigma-3. Unlike a critical "fault" that stops the motor immediately, this code acts as an alarm or minor fault, signaling that the system is approaching its operational limits.
If left unaddressed, an A.910 alarm typically escalates into a full-system shutdown (such as an A.710 or A.720 overload fault) to prevent hardware damage. What Does Error A.910 Mean?
In technical terms, A.910 indicates that the drive has detected an overload condition where the load on the motor is nearing its maximum rated capacity. Error Type: Communication error between the drive and
Warning Nature: It is a pre-alarm designed to give operators a chance to adjust the process before a complete trip occurs.
Trigger Point: The alarm is triggered based on the Overload Warning Level (Pn52B) parameter setting. If the motor operates at a torque exceeding its rating for several seconds, the drive flags this code. Primary Causes of the A.910 Alarm
Several factors—ranging from mechanical issues to electrical wiring—can trigger this warning:
Mechanical Overload: The most frequent cause is a physical obstruction or excessive load on the motor that exceeds its torque specifications.
Incorrect Wiring: Faulty contact or incorrect wiring in either the servomotor or encoder cables can cause the drive to misread the load or lose efficiency.
Parameter Settings: If the Overload Warning Level (Pn52B) is set too low for the specific application, the alarm will trigger prematurely.
Environmental Factors: High temperatures inside the SERVOPACK panel (exceeding 55°C) can reduce performance and trigger overload warnings.
Hardware Failure: In some cases, an internal fault within the SERVOPACK unit itself may cause erroneous A.910 readings. Step-by-Step Troubleshooting and Remedies
To resolve an A.910 error and prevent a full system trip, follow these steps:
Check Mechanical Load: Inspect the machinery for jams, excessive friction, or unexpected weight. Ensure the motor capacity is correctly sized for the operation.
Verify Wiring: Inspect all connections between the drive, motor, and encoder. Tighten loose terminals and replace damaged cables.
Adjust Parameters: Verify the setting of parameter Pn52B. If the application requires higher temporary torque, consider increasing this warning threshold within safe limits.
Monitor Temperature: Ensure the control panel has adequate ventilation. You may need to install cooling fans or an air conditioner if the internal temperature exceeds 55°C. Typical Solutions: | Step | Action | |------|--------|
Reset the Drive: Once the physical cause is removed, use the digital operator or SigmaWin+ software to clear the alarm. If the code persists after a power cycle, the SERVOPACK may require replacement.
For complex issues or persistent alarms that cannot be cleared, it is recommended to contact a certified repair center like Precision Zone for a full diagnostic. Yaskawa Servo Drive Alarm Codes Guide | PDF - Scribd
The Yaskawa error code A.910 is an Overload Warning (pre-alarm) primarily found in Sigma-series servo drives (Sigma-3, Sigma-5, and Sigma-7). It serves as a precursor to more severe faults like A.710 (instantaneous overload) or A.720 (continuous overload). Error Summary
Definition: The drive has detected that the motor is approaching its overload protection limit.
Behavior: In many configurations, the drive will continue to run while the alarm flashes, but it will trip (stop) if the load is not reduced. Common Causes & Troubleshooting Potential Cause Recommended Action Excessive Mechanical Load
Check for mechanical jams, binding, or friction in the system. Incorrect Wiring
Inspect the servomotor and encoder wiring for loose contacts or incorrect phases. Tight Duty Cycle
The operation pattern (acceleration/deceleration) may exceed the motor’s rated capacity. Parameter Settings
Check Pn52B (Overload Warning Level). If set too low, it triggers the warning prematurely. Environmental Heat
High temperatures inside the SERVOPACK panel (above 55°C) can trigger thermal-related warnings. Hardware Failure
If the load is normal and wiring is secure, the internal current detection circuit in the SERVOPACK may be faulty. Recommended Tools
SigmaWin+: Use this software to monitor the accumulated load ratio (Un009) and view the alarm trace to see exactly when the overload occurs.
Yaskawa Manuals: Refer to the specific troubleshooting manual for your drive series (e.g., Sigma-7 Troubleshooting Manual) for detailed parameter lists. To help you further, could you let me know: Which drive series are you using (e.g., Sigma-7, Sigma-5)?
Is this happening during startup or while the machine is running?
Have there been any recent mechanical changes to the machine? Σ-7C SERVOPACK - Troubleshooting Manual