Yaskawa J1000 AC Drive

This minor fault indicates that serial communication has not been established between the drive and the master, or that communication was interrupted. It is often caused by faulty wiring, incorrect termination resistor settings, or programming errors on the master side. If left unresolved, the drive will not be able to receive commands or send status updates, leading to system operational failure.

This minor fault indicates that control data was not received correctly for two seconds, primarily due to noise interference or incompatible communication settings. Noise can corrupt data transmission, while incorrect protocol settings or a too-short CE detection time can prevent proper communication. Unresolved, this fault prevents the drive from receiving critical control commands, leading to loss of control over the connected equipment.

A self-diagnostic error has occurred within the drive's control circuit. This indicates an internal problem with the drive's core control logic, which is critical for all operations. This fault can lead to unpredictable drive behavior, unstable control, or complete operational shutdown if not addressed.

A self-diagnostic error has occurred within the drive's control circuit, or the connector on the digital operator is damaged. This indicates an internal problem with the drive's control logic or a faulty operator interface, both of which are critical for proper operation and can lead to unreliable control or complete drive shutdown.

An Analog-to-Digital (A/D) conversion error or a control circuit error has occurred, indicating a potential issue or damage within the drive's control circuit. This means the drive cannot accurately convert analog input signals (e.g., current, voltage, feedback) into digital values for processing, risking unstable operation, incorrect control, or damage to connected equipment.

There is a connection error between the control board and the main drive unit, or the drive is experiencing operational issues due to significant electrical signal interference (noise). This can lead to intermittent faults, unreliable control, or a complete failure to operate properly, impacting machine safety and production.

An error has occurred in the data stored in the drive's EEPROM (Electrically Erasable Programmable Read-Only Memory), or the power supply was unexpectedly cut off while parameters were being saved. This can result in corrupted drive settings, incorrect operation, or the drive defaulting to factory settings, posing a risk to consistent machine control.

There is a faulty connection between the terminal board and the control board. This critical connection is necessary for processing all input/output signals (e.g., start/stop commands, speed references, fault outputs). A poor connection can lead to unreliable control, intermittent operation, or a complete lack of response from the drive, affecting machine safety and performance.

There is a faulty connection between the terminal board and the control board. This critical connection is necessary for processing all input/output signals (e.g., start/stop commands, speed references, fault outputs). A poor connection can lead to unreliable control, intermittent operation, or a complete lack of response from the drive, affecting machine safety and performance. This fault may also indicate an EEPROM serial communication fault within the terminal board itself.

Hardware damage has occurred within the drive's RAM (Random Access Memory), which is essential for temporary data storage and processing during operation. This indicates a serious internal hardware failure that will prevent the drive from functioning correctly, leading to immediate operational failure and potentially unsafe conditions.

There is a problem with the drive's internal ROM (FLASH memory), which stores the firmware and critical operating system programs. This indicates a serious internal hardware failure that prevents the drive from booting, executing its core functions, or operating reliably, rendering it inoperable.

A self-diagnostics problem has occurred within the watchdog circuit, which is responsible for monitoring the CPU's operation and resetting it if it becomes unresponsive. This indicates an internal hardware failure where the CPU is not responding as expected, causing the drive to enter a fault state and cease operation.

A CPU error has occurred, meaning the Central Processing Unit is operating incorrectly, potentially due to severe electrical noise or internal hardware damage. This is a critical internal control failure that prevents the drive from processing commands and controlling the motor, posing a significant operational and safety risk.

A standard clock error has occurred within the drive's internal timing circuits. Precise timing is absolutely crucial for many drive operations, including PWM generation, communication protocols, and internal synchronization. This indicates a critical hardware fault that will severely impair or prevent proper drive function, making it inoperable.

This minor fault occurs when a fault reset command is issued while the Run command is still active. The drive will disregard any attempts to reset the fault until the Run command is removed. If not resolved, the drive will remain in a fault state and will not restart, preventing operation.

This minor fault indicates that the upper controller is attempting to use a MECHATROLINK communication cycle that is outside the allowable setting range for the drive's MECHATROLINK option. This incompatibility prevents proper synchronized communication between the controller and the drive. If unaddressed, the drive will not be able to communicate effectively with the MECHATROLINK master, hindering coordinated machine operation.

The MECHATROLINK communication watchdog timer has timed out because the drive did not receive expected data from the PLC within the specified timeframe. This indicates a loss of communication or a significant delay in data exchange over the MECHATROLINK network, which can lead to a complete loss of control over the drive.

Both the forward run and reverse run commands were detected as closed simultaneously for over 0.5 seconds. This indicates a critical sequence error in the control logic or wiring, leading to a minor fault that causes the motor to ramp to a stop to prevent conflicting commands or potential damage.

An external fault condition has been received by the drive from the PLC via an option card. The drive's response (stopping or continuing to run as an alarm) depends on the F6-03 parameter setting. This fault typically points to an issue originating from an external device, a problem with the PLC program's fault handling, or a communication issue.

An external fault has been triggered at multi-function input terminal S1. This signifies that an external device connected to S1 has activated an alarm function, or there's an issue with the wiring or configuration of terminal S1. This fault will typically cause the drive to stop operation.

An external fault has been triggered at multi-function input terminal S2. This signifies that an external device connected to S2 has activated an alarm function, or there's an issue with the wiring or configuration of terminal S2. This fault will typically cause the drive to stop operation.

An external fault has been triggered at multi-function input terminal S3. This signifies that an external device connected to S3 has activated an alarm function, or there's an issue with the wiring or configuration of terminal S3. This fault will typically cause the drive to stop operation.

An external fault has been triggered at multi-function input terminal S4. This signifies that an external device connected to S4 has activated an alarm function, or there's an issue with the wiring or configuration of terminal S4. This fault will typically cause the drive to stop operation.

An external fault has been triggered at multi-function input terminal S5. This signifies that an external device connected to S5 has activated an alarm function, or there's an issue with the wiring or configuration of terminal S5. This fault will typically cause the drive to stop operation.

An external fault has been triggered at multi-function input terminal S6. This signifies that an external device connected to S6 has activated an alarm function, or there's an issue with the wiring or configuration of terminal S6. This fault will typically cause the drive to stop operation.

An external fault has been triggered at multi-function input terminal S7. This signifies that an external device connected to S7 has activated an alarm function, or there's an issue with the wiring or configuration of terminal S7. This fault will typically cause the drive to stop operation.

An external fault has been triggered at multi-function input terminal S8. This signifies that an external device connected to S8 has activated an alarm function, or there's an issue with the wiring or configuration of terminal S8. This fault will typically cause the drive to stop operation.

The drive encountered an error while attempting to write data to its internal EEPROM. This can be caused by electrical noise during the write operation, corrupted data, or a hardware defect within the EEPROM chip or the control board. Persistent EEPROM errors can prevent parameter saving, configuration changes, or proper drive initialization.

The drive's internal cooling fan or its associated magnetic contactor has failed to operate correctly. This fault is detected based on parameter L8-32 settings. A malfunctioning cooling fan can lead to excessive heat buildup within the drive, potentially causing thermal damage, reduced operational life, and further component failures if not addressed promptly.

The PID feedback input signal has continuously exceeded the threshold set in parameter b5-36 for a duration longer than specified in b5-37. This fault occurs when PID fault detection (parameter b5-12) is enabled (e.g., set to 1, 2, 4, or 5). Common causes include incorrect PID parameter tuning, faulty feedback wiring, or a malfunctioning feedback sensor, leading to unstable process control.

The drive's IGBTs (Insulated Gate Bipolar Transistors) have reached 50% of their expected performance life, indicating they are halfway through their typical operational lifespan. This is a pre-alarm for scheduled maintenance rather than an immediate fault, but if left unaddressed, it can lead to component degradation, unexpected failure, and costly downtime.

No PG (Pulse Generator/encoder) pulses were received for a duration longer than the setting in F1-14. This indicates a physical disconnection or incorrect wiring of the PG cable, insufficient power to the PG encoder, or a brake preventing encoder movement, leading to a loss of speed/position feedback.

A hardware fault related to the PG has been detected, specifically indicating a disconnected PG cable when using a PG-X3 option card. This means the drive is not receiving the necessary encoder feedback signals due to a physical connection issue.

A short-circuit or ground fault is detected on the drive output side, which could be due to motor insulation damage, a shorted motor cable, or a hardware fault within the drive's output transistors (IGBTs). If unresolved, this fault can lead to significant damage to the drive's internal circuitry.

The drive has attempted Speed Search more times than the limit set in parameter b3-19. This typically indicates that the Speed Search parameters are incorrectly configured or that the motor is coasting in the opposite direction of the commanded run.

The motor has exceeded its pull-out torque, resulting in a motor pull-out or step-out condition. This can be caused by an incorrect motor code for PM motors, an excessively heavy load, high load inertia, or acceleration/deceleration times that are too short for the system's dynamics.

Position deviation has occurred during zero servo operation. This fault typically arises from the torque limit being set too low for the application, an excessively high load torque on the motor, or electrical signal interference affecting the PG encoder wiring.

The thermistor used to detect motor temperature has become disconnected. This prevents the drive from accurately monitoring motor temperature, posing a significant risk of motor overheating and damage if the condition is not resolved.

The motor current has fallen below the minimum value set for torque detection (L6-02) for longer than the allowable time (L6-03). This indicates either inappropriate parameter settings for the current load conditions or a mechanical fault on the machine side, such as a loss of load or broken coupling.

The motor current has fallen below a secondary minimum value set in L6-05 for longer than the allowable time specified in L6-06. Similar to UL3, this suggests either incorrect parameter tuning for the current load or a fault in the machine's mechanical system that is causing reduced torque.

The operating conditions detected by the drive matched the criteria for mechanical loss detection set in parameter L6-08. This suggests an undertorque condition due to potential mechanical weakening or a problem on the load side that needs investigation to prevent further damage.

The internal current sensor has detected an unbalanced current flow on the motor phases. This could indicate issues with motor wiring, damaged internal power transistors (IGBTs) within the drive, or short-circuits/grounding problems on the connected motor, leading to inefficient operation or potential drive damage.

The DC bus voltage fell below the undervoltage detection level (e.g., ~190V for 200V class, ~380V for 400V class) while the drive was running, or specific parameter conditions were met. Common causes include input power phase loss, loose wiring, unstable voltage supply, or worn main circuit capacitors.

The voltage supplied to the control drive input power is too low. This can occur if parameter L2-02 is changed from its default value without installing a Momentary Power Loss Ride-Thru unit, or if there is damage to the control power supply wiring or internal control circuitry, impacting drive control stability.

The soft-charge bypass circuit has failed, typically due to a damaged relay or contactor within this circuit. This failure can prevent proper charging of the DC bus, leading to the drive being unable to start or operate correctly.

A voltage drop has occurred in the gate drive board circuit, indicating insufficient power supply to the board. This prevents the IGBTs from switching correctly, leading to immediate drive stoppage and potential damage if the underlying power issue is not resolved.

This minor fault occurs when the deviation between the speed reference and the actual speed feedback (typically from a PG option card) exceeds the threshold set in F1-10 for a duration longer than F1-11. Common causes include excessive load, improperly set acceleration/deceleration times, mechanical lock-ups, or incorrect parameter scaling. Failure to resolve this can lead to unstable motor operation, mechanical stress, or an inability to maintain desired process speeds.

This minor fault indicates that the 'Drive Enable' signal, which is typically assigned to a multi-function contact input (H1- = 6A), has been switched off. This action intentionally disables the drive, preventing it from operating. If this occurs unexpectedly, it implies an issue with the control sequence or external input.

The temperature of the drive's heatsink has exceeded the pre-alarm level, typically set between 90-100 °C by parameter L8-02. This condition can be caused by high ambient temperatures, a malfunctioning internal cooling fan, or restricted airflow around the drive, leading to inadequate heat dissipation and potential damage to internal power components if ignored.

An external device has triggered an overheat warning signal, which was input to a multi-function input terminal (S1 through S8) configured for this purpose (H1- = B). This indicates an overheat condition originating from an external component connected to the drive. Failure to address the external overheat can lead to damage to that device or related process disruptions.

The motor overheat signal, typically from a PTC thermistor input to a multi-function analog terminal (H3-02, H3-06, or H3-10 = E), has exceeded its alarm level. Possible causes include faulty motor thermostat wiring, a locked-up machine, or the motor itself overheating due to excessive load or an inappropriate V/f pattern. Continued operation with an overheated motor risks winding insulation breakdown and costly motor failure.

The motor temperature, as directly monitored via an NTC thermistor input, has exceeded the alarm level set in parameter L1-16 (or L1-18 for motor 2). This indicates the motor itself is running excessively hot, likely due to prolonged overload or high ambient temperatures. Sustained overheating can lead to irreversible damage to motor windings and premature motor failure.

The drive's output current (or calculated torque in OLV, CLV, AOLV/PM, CLV/PM modes) has exceeded the threshold set in L6-02 for longer than the time specified in L6-03. This fault typically indicates either incorrect parameter settings for torque detection or a mechanical issue on the machine side causing excessive load on the motor. Ignoring this can lead to damage to the motor, gearbox, or driven equipment.

The drive's output current (or calculated torque in OLV, CLV, AOLV/PM, CLV/PM modes) has exceeded the threshold set in L6-05 for longer than the time specified in L6-06. Similar to Overtorque 1, this suggests either parameter misconfiguration or a significant mechanical overload on the driven equipment. Sustained overtorque conditions can result in mechanical stress, equipment damage, or shortened lifespan of motor and machine components.

Overtorque occurred, matching the conditions for mechanical weakening detection specified in parameter L6-08. This suggests a mechanical problem on the load side that is causing increased torque demands on the motor, potentially leading to component wear or system inefficiency.

The motor speed feedback exceeded the F1-08 setting, indicating an overspeed condition or excessive overshoot. This can be caused by incorrect speed control parameters, inappropriate speed feedback scaling, or an incorrectly set PG pulse number, leading to unstable or uncontrolled motor speed.

The DC bus voltage exceeded its trip point (e.g., ~410V for 200V class, ~820V for 400V class). This can result from surge voltage in the drive input power, a short-circuited motor, ground current over-charging the main circuit capacitors, or electrical signal interference affecting measurements.

A command to switch motors was entered while the drive was still in run mode. This operation is typically disallowed to prevent incorrect motor control, unexpected behavior, or potential damage to the motors or drive components.

A problem has been detected with the voltage on the output side of the drive, indicating internal hardware damage. This fault prevents the drive from operating correctly and consistently, requiring component replacement to restore full functionality.