Yaskawa E7 Drive

The speed search function has attempted to retry more times than allowed by the b3-19 parameter. This typically indicates that the speed search settings in b3-17 and b3-18 are not correctly configured for the application, preventing successful speed identification within the set limits.

After initial communication was established, the connection to the option board was lost. This indicates a broken connection or the master device has stopped communicating, leading to loss of control or monitoring through the option card.

After initial communication was established, the connection to the option board was lost. This indicates a broken connection or that the master controller stopped communicating, preventing data exchange.

A serial communication transmission error has occurred, indicating that communication has not yet been established. This is typically due to improper connections or user software not configured to the correct baud rate or communication settings, preventing data exchange.

This fault indicates a loss of serial communication (e.g., Modbus) between the drive and its control system for more than 2 seconds, affecting parameters like H5-04 and H5-05. The drive will execute a programmed stopping method, becoming unresponsive to external commands. Prolonged communication loss can lead to process interruption and potential safety hazards if the drive is not properly controlled.

Control data was not received correctly for two seconds, indicating a breakdown in Modbus communication. This fault occurs when H5-05=1 and H5-04=0 to 2, typically due to a broken connection or the master stopping communication.

A torque limit was continuously reached for 3 seconds or longer during a ramp to stop while operating in open-loop vector control. This fault typically indicates that the motor parameters are not correctly set, preventing the drive from controlling torque effectively.

Transmission between the Drive and the digital operator cannot be established within 5 seconds after supplying power. This suggests issues with the digital operator cable, the operator itself, or the control board, preventing local interaction and display.

After communication started with the Digital Operator, it stopped for 2 seconds or more. This fault suggests issues with the Digital Operator cable, a defective operator unit, or a fault within the Drive's control board.

A baseblock circuit fault was detected at power-up, indicating a gate array hardware failure within the drive during its startup sequence. This is a critical internal drive component failure, rendering the drive inoperable.

The EEPROM check sum was not valid, indicating data corruption in the non-volatile memory. This can be caused by electrical noise or spikes on the control circuit input terminals, compromising the Drive's configuration data integrity.

A fault in the CPU's internal Analog-to-Digital converter was detected. This issue typically results from noise or electrical spikes on the control circuit input terminals, impairing the CPU's ability to accurately process internal analog signals.

A fault with the external Analog-to-Digital converter was detected. This problem is often caused by noise or electrical spikes on the control circuit input terminals, impacting the accurate conversion of external analog input signals.

A CPF5 fault indicates a critical internal issue with the drive's CPU Analog-to-Digital (A/D) converter. This is a hardware malfunction within the drive's control board, meaning the drive cannot accurately measure and process internal signals. If this fault occurs, the drive is unable to function correctly and requires internal repair or replacement.

The option board was not connected properly or has been damaged, indicating a problem with its physical integrity or functionality. This fault can also suggest damage to the Drive itself affecting the option board interface.

Control circuit failure or damage, specifically within the ASIC's internal RAM. This is a critical internal hardware fault indicating a memory integrity issue that can lead to unpredictable Drive behavior.

Control circuit failure or damage related to the watchdog timer. This critical internal hardware fault means the system's ability to monitor its own operation has failed, which can lead to unsafe conditions.

Control circuit failure or damage involving a mutual diagnosis fault between the CPU and ASIC. This is a critical internal hardware fault affecting the core processing units and indicates a severe internal malfunction.

An ASIC Version Fault was detected, indicating an issue with the ASIC's version identification or integrity. This points to control circuit damage, compromising the drive's fundamental operation.

This fault can be caused by an option card connector connection fault or an option card A/D converter fault. It indicates an issue with the option board's hardware or its connection, preventing proper functionality and communication.

A self-diagnosis fault was detected on the option board, potentially due to noise or spikes on the communication line or a defective option board itself. This indicates an internal issue with the option board's CPU, impacting its operation.

An unrecognizable option board is connected to the control board, indicating a type mismatch or an unsupported option card. This prevents the drive from correctly interfacing with the option card, leading to functional limitations or failure.

An option board was not correctly connected to the control board, or an incompatible option board was attached. This fault indicates a problem with the physical interface or compatibility between the option and control boards, preventing data exchange.

This fault occurs in Flux Vector control (A1-02=3) when the actual motor speed deviates from the reference speed by more than the F1-10 setting for longer than the F1-11 time. It often indicates a locked load or an inability for the motor to follow its command. Unresolved, this can lead to poor process control, mechanical stress on the system, or motor overheating due to sustained effort.

A communication error has occurred when the SI-F/G Option Card is designated as the source for run commands or frequency reference (b1-01=3 and/or b1-02=3), and communication with it is lost. This implies a failure in the communication link or configuration with the SI-F/G card. Without proper communication, the Drive cannot receive critical commands or references, leading to a stop.

This fault indicates a consistency error in received control data or a synchronization problem between the master controller and the Drive when using an SI-T option card. It signifies a breakdown in reliable communication, which can lead to unpredictable Drive behavior or complete loss of control. Such errors require immediate attention to restore stable operation.

Both the forward and reverse run commands were input simultaneously for 500ms or more, causing the motor to stop. This is an external sequencing logic error, which could lead to motor damage or unsafe operation if not corrected.

An external fault condition exists, originating from the communication option card. This suggests an issue with an external device or signal connected via the option card, potentially leading to incorrect drive operation. This can also appear as a flashing alarm.

This fault is triggered when an external condition connected to multi-function digital input terminal S3 activates the Drive's external fault function. The Drive will stop according to its programmed response (ramp, coast, or fast stop). This indicates an issue with the external device or process monitored by S3, potentially leading to unsafe operation if misconfigured.

This fault is triggered when an external condition connected to multi-function digital input terminal S4 activates the Drive's external fault function, causing the Drive to stop. It indicates an issue with the external device or process monitored by S4, which could lead to machine downtime or safety risks if misidentified.

This fault is triggered when an external condition connected to multi-function digital input terminal S5 activates the Drive's external fault function, causing the Drive to stop. It indicates an issue with the external device or process monitored by S5, which could lead to machine downtime or safety risks if misidentified.

This fault is triggered when an external condition connected to multi-function digital input terminal S6 activates the Drive's external fault function, causing the Drive to stop. It indicates an issue with the external device or process monitored by S6, which could lead to machine downtime or safety risks if misidentified.

An external fault condition exists connected to a multi-function digital input terminal S7. This implies an issue with an external device or wiring connected to this specific input, which could stop the drive or cause unintended behavior. This can also appear as a flashing alarm.

This fault is triggered when an external condition connected to multi-function digital input terminal S8 activates the Drive's external fault function, causing the Drive to stop. It indicates an issue with the external device or process monitored by S8, which could lead to machine downtime or safety risks if misidentified.

The rated current set value is set too high, or there's an excessive V/F set value, or a motor iron core saturation coefficient fault, causing the auto-tuning results to be invalid. This is an alarm that indicates incorrect motor or drive parameter settings post-tuning, which could lead to suboptimal performance or protection issues.

An error was detected in the data input for auto-tuning or in the relationship between the motor output and motor rated current. This prevents successful auto-tuning, which is crucial for optimal drive performance and motor control.

An alarm has been detected during the Auto-Tuning process, signaling a potential issue with the tuning setup or the motor/load configuration. While not a critical fault that stops the Drive, it warns of an incomplete or inaccurate auto-tuning result, which could lead to suboptimal motor performance or control issues.

The auto-tuning process was interrupted because the STOP key was pressed during its operation. This is a user-initiated stop, not an actual system fault, and prevents the tuning from completing.

Auto-tuning did not complete within the specified time, or the tuning result for resistance fell outside the parameter set range. This can be caused by incorrect input data, motor wiring issues, or a connected mechanical load interfering with the tuning.

During Auto-Tuning, this fault signifies that the process did not complete within the specified time or the measured no-load current was outside the expected range. This can be caused by incorrect motor data, wiring issues, or a connected load influencing the no-load measurement. An incorrect no-load current value will lead to suboptimal motor parameterization and control.

This Auto-Tuning fault means the process did not complete within the specified time, or the calculated rated slip value was outside the parameter setting range. It can also occur if the motor rated voltage setting (T1-03) is higher than the Drive's actual input voltage. Incorrect slip data will negatively impact motor speed regulation and torque control.

This fault occurs during rotational Auto-Tuning if the motor fails to accelerate within the specified time (C1-01 + 10 seconds). It suggests insufficient torque, an excessive mechanical load, or incorrect acceleration parameters preventing the motor from reaching its target speed during the tuning sequence. Failure to accelerate properly will prevent accurate motor parameter identification.

Detected during rotational Auto-Tuning in vector control (A1-02=2 or 3), this fault indicates that the torque reference exceeded 100% during acceleration. This typically points to an issue with acceleration time, incorrect PG (encoder) pulse data, or an excessive mechanical load on the motor. Exceeding torque limits during tuning will lead to inaccurate motor parameterization and potentially inefficient operation.

The current flow exceeded the motor rated current, the current detection value symbol was reversed, or there is an open-phase condition on any of the U/T1, V/T2, and W/T3 output terminals. This indicates a severe issue with the motor wiring or the drive's internal current detection, risking motor or drive damage.

Auto-Tuning failed to complete within the expected time frame or the resulting leakage inductance value fell outside the acceptable parameter range. This indicates an inconsistency with the motor's electrical characteristics as measured during tuning, likely due to incorrect input data or motor wiring problems affecting the measurement.

This fault occurs when data written to the EEPROM does not match, often due to power supply being turned OFF unexpectedly or repeated parameter resets. It indicates potential internal data corruption that can prevent proper operation.

This alarm occurs when a serial communication option board, attached to the drive at the 2CN connector, detects a communication error, and parameter F6-01 is specifically set to '3: Alarm Only'. In this state, the drive acknowledges the communication issue without energizing the fault output or stopping operation, allowing for continuous monitoring despite communication problems.

This fault occurs when a serial communication option board, attached to the drive at the 2CN connector, detects a communication error. Unless parameter F6-01 is specifically set to '3: Alarm Only', this condition will energize the fault output and potentially stop the drive, indicating a critical problem with the communication link to the option board.

A fault with the Drive's internal cooling fan has been detected, leading to the activation of Drive overload protection due to excessive internal thermal value. This typically occurs when the fan stops running and the Drive continues operating under load, causing heat to build up. Unresolved, this will lead to repeated overheating faults and potential damage to the Drive's power components.

This fault occurs when PID Feedback Loss Detection is enabled (b5-12=2) and the PID feedback signal drops below the defined level (b5-13) for a specified time (b5-14). It signifies that the PID feedback source (e.g., transducer, sensor, building automation signal) is either incorrectly installed, malfunctioning, or disconnected. Loss of PID feedback means the Drive cannot maintain accurate process control, potentially causing system instability.

The Drive has detected an output grounding current exceeding 50% of its rated output current (L8-09 = 1 enabled), indicating a current leakage to ground. This is typically caused by a short in the motor leads, motor windings, or a defective internal current sensor. A persistent ground fault poses a safety risk and can lead to damage to the motor or Drive components.

An open-phase condition has been detected at the Drive's output, where the output current imbalance exceeds 5% (L8-07=1 enabled). This is commonly caused by a broken wire in the motor cable, a broken winding in the motor, or loose output terminal connections. Operating with an open phase can cause motor damage due to imbalanced currents and vibrations, as well as reduced performance.

The Drive's output current has exceeded its overcurrent detection level, typically around 200% of the Drive's rated output current. Common causes include phase-to-phase shorts in the motor or cables, a locked rotor, an excessively heavy load, or insufficient acceleration/deceleration times. Repeated overcurrent can cause damage to the Drive's power components or the motor.

The temperature of the Drive's heatsink has exceeded the programmed setpoint (L8-02, L8-03=0 to 2), indicating inadequate cooling or excessive ambient temperature. This can be caused by a nearby heat source, dirt buildup on fans/heatsink, or high room temperature. Persistent overheating will lead to nuisance trips, reduced performance, and can significantly shorten the Drive's lifespan.

An OH1 fault signals an overheat condition specifically caused by the failure or malfunction of the drive's internal cooling fan. When L8-32 is enabled, this fault will occur, indicating that the drive's ability to dissipate heat is compromised. Prolonged operation without adequate cooling will inevitably lead to damage of internal power components and system shutdown.

An OH2 fault occurs when any of the heatsink thermistors measure a temperature exceeding the level set in L8-02. This indicates that the drive's heatsink is overheating, typically due to insufficient cooling, excessive ambient temperature, or prolonged overload on the drive. Sustained high temperatures can severely degrade the lifespan of the drive's power components and lead to premature failure.

This alarm indicates that the motor's temperature, as monitored by an analog input (H3-09=E), has exceeded the OH3 alarm threshold (1.17V). It serves as an early warning of potential motor overheating, allowing for intervention before a more critical fault occurs that could lead to a drive stop.

The OH4 fault indicates a critical over-temperature condition in the motor, detected when the motor temperature analog input (H3-09=E) surpasses the 2.34V fault level. Upon activation, the drive will immediately stop the motor using a configured method to prevent damage. Operating a motor under this severe overheat condition risks immediate insulation breakdown, permanent motor failure, and safety issues.

This fault occurs when the motor current exceeds 110% of the value set in parameter E2-01 (Motor Rated Current) for a duration determined by L1-02 (Motor Overload Protection Time). It indicates the motor is drawing excessive current, risking overheating and potential damage if the condition is not resolved.

An OL2 fault indicates that the drive's internal overload protection level has been automatically reduced because the ambient temperature around the drive exceeds its specified rating, as configured in L8-12. This protects the drive's output power components from overheating under high load conditions. Continuous operation in an overly warm environment can lead to component degradation and drive failure.

The Drive output current exceeded the threshold set in L6-02 for longer than the time set in L6-03, indicating a motor overload condition. This fault protects the motor and mechanical system from damage due to excessive load.

This fault indicates that the motor load has exceeded the configured Overtorque 2 detection level (L6-05) for the set duration (L6-06). Similar to OL3 but using a secondary profile, it triggers based on L6-04 settings, causing the drive to shut down. This points to a mechanical obstruction, jamming, or excessive resistance in the driven equipment. If persistent, this can lead to motor and drive damage or mechanical failure of the connected machinery.

An Operator Programming Error occurs when the Drive's kVA setting is incorrect, usually after a control board replacement. The Drive will not operate until this parameter is corrected.

An Operator Programming Error indicating a parameter has been set above its allowable range. The Drive will not operate until the parameter is set correctly.

An Operator Programming Error due to duplicate multi-function input selections, conflicting up/down commands, or simultaneous speed search from maximum frequency and set frequency. The Drive will not operate until parameters are corrected.

An Operator Programming Error where a run command is selected via serial communication (2CN) but no option board is installed, or it's installed incorrectly. The run command selection parameter B1-02 is set to 3 but the option board is absent. The Drive cannot operate without the correct board and settings.

An Operator Programming Error indicating incorrect V/f parameter settings. This can happen if a minimum frequency/voltage value is set higher than the maximum frequency/voltage. The Drive will not operate until corrected.

An Operator Programming Error related to incorrect carrier frequency parameter settings, such as C6-05 > 6 and C6-04 > C6-03, or an upper/lower limit error for C6-03 (e.g., set above 5.0kHz). The Drive will not operate until corrected.

The Drive stopped because the digital operator was removed while the Drive was commanded to run through it. This indicates either the operator is not attached, its connector is broken, or parameter o2-06 is set incorrectly, preventing proper control.

An Overspeed (OS) fault occurs when the motor speed feedback, typically from the PG, exceeds the configured overspeed detection level (F1-08) for a duration longer than the delay time (F1-09). This indicates the motor is running faster than its allowed maximum, potentially due to incorrect control parameters, regenerative load conditions, or an encoder issue. Unresolved overspeed can lead to mechanical damage to the motor or driven equipment, and create safety hazards.

The DC bus voltage exceeded its trip point (≥400Vdc for 208-240Vac Drives; ≥800Vdc for 480Vac Drives). This is often caused by high input voltage, overly short deceleration times leading to regenerative energy, or the presence of power factor correction capacitors on the input. Overvoltage can severely damage drive components.

A PF fault indicates that one or more of the input AC phases to the drive has been lost. The drive's detection circuit monitors DC bus current ripple and activates if the difference (ΔV) between maximum and minimum DC bus voltage values reaches or exceeds an internal detection level for 0.5 seconds. This can lead to imbalanced current draw, potential damage to the drive's input rectifier, and motor instability.

This fault occurs when an open circuit condition is detected in the Pulse Generator (PG) feedback. This means the drive is not receiving proper speed or position feedback from the motor's encoder. This can lead to uncontrolled motor speed, position errors, or loss of precise control if left unaddressed.

This alarm occurs when the PI function's feedback signal is determined to be lost, as configured by parameter b5-12 set to '1: Alarm'. The drive acknowledges the loss of feedback but continues to operate without stopping, and it does not energize the fault output (MA-MB), indicating a degraded control state rather than a critical shutdown.

This fault occurs when the PI function's feedback signal is determined to be lost, as configured by parameter b5-12 set to '2: Fault'. Upon detection, the drive will coast to a stop and energize the fault output (MA-MB), indicating a critical loss of process control feedback that requires immediate attention.

The Drive detects that the DC bus fuse has opened. This is typically caused by shorted output transistor(s) or output terminals, indicating a severe internal fault in the power circuit. The fuse opens to protect upstream components but requires addressing the underlying short.

The protection for the dynamic braking resistor, based on setting of L8-01, has been activated. This fault is typically caused by an overhauling load, an extended dynamic braking duty cycle that exceeds the resistor's capacity, or a defective dynamic braking resistor, leading to overheating.

This fault indicates a failure of the dynamic braking transistor. Common causes include a shorted dynamic braking transistor, consistently high DC bus voltage, or a defective dynamic braking resistor. This condition can lead to uncontrolled energy dissipation or damage to the drive's power stage.

The motor position moved more than 10,000 revolutions during zero servo operation, indicating a loss of position control. This can be caused by an excessively small torque limit, an overly large load torque, or a fault within the control circuit, possibly due to electrical noise interfering with position feedback.

The drive detected that its output current was continuously below the threshold set in L6-02 for longer than the time specified in L6-03, when L6-01 was configured for undertorque detection. This fault indicates that the connected motor is operating under an unexpectedly low load, potentially due to a mechanical issue or process change.

Similar to UL3, this fault indicates the drive's output current was below the L6-05 threshold for longer than L6-06, with L6-04 set for undertorque detection. It signifies a motor running under an unexpectedly light load condition, potentially indicating a process issue or mechanical failure that needs investigation.

An Undervoltage (UV) alarm is displayed on the digital operator during a momentary power loss event, specifically after power loss but before a fault trip occurs. This indicates that the drive is actively attempting to ride through the power loss, maintaining operation as long as control power is sustained. It's a warning, not a fault that stops the drive immediately.

The DC bus voltage inside the drive has fallen below the trip point (e.g., 190Vdc for 240V AC input or 380Vdc for 480V AC input), which is adjustable via L2-05. Common causes include insufficient incoming AC power, excessively short acceleration times leading to voltage sag, or significant fluctuations in the input voltage quality.

An undervoltage condition was detected in the drive's internal control circuit while it was operating. This fault typically points to either an excessive load being drawn by external control wiring connected to the drive's power supplies, or an internal electrical fault, such as a short circuit, on the power or gate drive PCB.

The pre-charge contactor, responsible for managing the initial charging of the DC bus capacitors, opened unexpectedly while the drive was running. This often indicates a mechanical issue with the contactor itself, such as dirty or worn contacts, preventing proper mechanical operation or causing premature opening.