High resistance in loose or corroded power cable connections (terminals U, V, and W) can mimic an overload condition. Bad contact points create localized voltage drops, forcing the SERVOPACK to supply higher current loops to sustain the commanded motor performance. 🛠️ Step-by-Step Troubleshooting and Resolution
While "A910" is commonly mistaken for a Yaskawa code, it is actually a frequent alarm on Siemens SINAMICS and Micromaster drives. On these systems, indicates that the Vdc-max controller has been deactivated because the DC-link voltage has exceeded its limits. Troubleshooting the A910 Alarm
Intermittent connections or high resistance mimic mechanical overload states inside the drive's current-sensing circuitry.
| Scenario | Recommended Action | | :--- | :--- | | | Perform an Autotune (Tune the motor parameters). This ensures the drive knows the exact electrical characteristics of the motor. | | Genuine Overload | 1. Reduce the mechanical load. 2. Increase acceleration time (C1-01, etc.) to reduce current spikes during start. 3. Consider replacing the motor with a larger frame size. | | Cyclic Loads | If the load pulses (e.g., a press machine), the RMS current might be fine, but the peak current triggers the alarm. Adjust the L3-03 (Overload Limit Level) . | | Warning Annoyance | If the operator is aware of the load and wishes to ignore the warning (not recommended), parameter L3-01 can be changed from "Enabled" to "Disabled" (Value 0), provided external thermal protection exists. |
The warning level setting for the overload (often Parameter Pn52B) might be set too low for the application. yaskawa error code a910 link
The primary function of the A.910 warning is to monitor the continuous root-mean-square (RMS) load of the motor. When the drive detects that the torque requirements have exceeded the continuous rating of the specific motor-drive combination for a sustained period, it throws the A.910 code.
The is fundamentally a communication handshake problem between the drive’s brain and its add-on card. It is rarely a catastrophic failure; more often, it is a loose screw, a dirty contact, or a parameter mismatch.
Check for tight spots, resistance, or grinding noises along the entire length of travel. Re-lubricate components or realign linear rails if binding is detected. Step 2: Review and Adjust Parameter Pn52B
The "link" in this error refers to the connection between the physical motor performance and the drive’s monitored overload characteristics. The most common causes are: High resistance in loose or corroded power cable
: Offers customizable thresholds via specific internal parameters, allowing engineers to dictate exactly when the pre-overload warning triggers. Primary Causes of the Yaskawa A.910 Code
If the machine is mechanically clear but still errors out, the performance expectations may exceed the physical limits of the system.
The drive’s serial port may be damaged, requiring drive repair/replacement.
Monitor the motor's torque reference percentage via the Un002 monitor parameter using the Yaskawa SigmaWin+ software. If the value consistently rests above 100% during operation, the application profile is too demanding. On these systems, indicates that the Vdc-max controller
The alarm threshold parameter Pn52B may be set too low. If the factory default is modified down prematurely, normal operation spike currents trigger the warning. 5. Hardware Degradation within the SERVOPACK
Route encoder cables away from high-voltage cables and VFDs to minimize electromagnetic interference (EMI). 3. Replace the Encoder Cable
is one of the more cryptic yet critical alarms in the Yaskawa drive ecosystem. If you are seeing A910 flash across your HMI (Digital Operator), your drive is not dead—but it is signaling a fundamental breakdown in communication between its internal control board and the optional communication card.
To resolve the A910 link error, follow these step-by-step troubleshooting procedures: