Yaskawa E7 Drive

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.

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.

Control data was not received correctly for two seconds over the Modbus connection. This implies a broken Modbus connection or the master device has stopped communicating, preventing proper control and data exchange.

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, a communication fault occurred for 2 seconds or more. This indicates a problem with the digital operator cable, the operator unit, or the control board, leading to intermittent or lost local control.

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.

An EEPROM fault was detected, meaning the checksum is not valid, potentially due to noise or spikes on the control circuit input terminals. This critical memory fault can lead to incorrect parameter storage or drive operation.

A fault in the CPU's internal A/D converter was detected, often caused by noise or spikes on the control circuit input terminals. This affects the drive's ability to accurately read internal analog signals, potentially leading to incorrect control or protection responses.

A fault in the CPU's external A/D converter was detected, often caused by noise or spikes on the control circuit input terminals. This affects the drive's ability to accurately read external analog signals, potentially leading to incorrect control or protection responses.

An internal RAM fault was detected within the ASIC (Application-Specific Integrated Circuit) of the drive. This is a critical internal hardware failure, indicating control circuit damage and rendering the drive inoperable.

A Watchdog Timer Fault was detected, indicating an issue with the drive's internal timing and supervision mechanism. This is a critical internal hardware failure, suggesting control circuit damage and leading to drive malfunction or shutdown.

A mutual diagnosis fault between the CPU and ASIC was detected, indicating an internal communication or functional inconsistency between these core components. This implies control circuit damage, making the drive unreliable or inoperable.

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 of the communication option card occurred, possibly due to noise or spikes on the communication line or a defective option board itself. This fault indicates a critical internal problem with the communication option card, leading to communication failure.

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 is not correctly connected to the control board or an option board that is not made for the Drive is attached. This indicates a physical connection issue or hardware mismatch, risking improper communication or drive malfunction.

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.

An external fault condition exists connected to a multi-function digital input terminal S3. 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.

An external fault condition exists connected to a multi-function digital input terminal S4. 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.

An external fault condition exists connected to a multi-function digital input terminal S5. 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.

An external fault condition exists connected to a multi-function digital input terminal S6. 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.

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 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.

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.

A minor fault was detected during the auto-tuning process. This could indicate slight discrepancies in input data, wiring issues, or problems with the mechanical load connected to the motor, impacting the accuracy of tuning.

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.

The motor did not accelerate as specified during the auto-tuning process. This may be due to an acceleration time setting that is too short, torque limits set too low, or the motor being connected to a heavy mechanical load.

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 did not finish within the set time, or the tuning result for leakage inductance fell outside the parameter setting range. This typically points to issues with motor wiring, preventing the drive from accurately determining motor inductance.

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.

This fault occurs when PI Feedback Loss Detection is programmed to fault (b5-12 = 2) and the PI Feedback is below the PI Feedback Loss Detection Level (b5-13) for the PI Feedback Loss Detection Time (b5-14). The PI Feedback source (e.g., transducer, sensor, building automation signal) is not installed correctly or is not working, risking unstable control.

The Drive output grounding current has exceeded 50% of the Drive's rated output current. This indicates a motor lead shorted to ground or a defective DCCT (Direct Current Current Transformer), posing risks of electrical shock, equipment damage, or fire.

This fault indicates an excessive current draw, which can lead to motor and drive damage if not promptly addressed. It can occur during momentary power loss recovery, DC Injection Braking, or during acceleration if the mechanical load is too large or the acceleration time is set too short. The drive will trip and stop operation upon detection of this fault.

The Overheat (OH) Pre-Alarm indicates that the drive's cooling fin temperature has exceeded the threshold set in parameter L8-02. Depending on the setting of L8-03, this condition can either trigger a fault detection (with the fault contact activating) or function as an alarm only. Ignoring this pre-alarm can lead to a more severe overheat fault (like OH1) and potential damage to the drive if the temperature continues to rise.

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.

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.

This fault signifies a critical motor overtemperature condition where the analog temperature input (H3-09=E) has exceeded the OH4 fault threshold (2.34V). This level typically triggers a drive stop (based on L1-04) to prevent severe and permanent motor damage due to excessive heat.

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.

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.

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.

The Drive input power supply has an open phase or a large imbalance of input voltage. This can be caused by a missing phase, loose terminal screws, momentary power loss, or significant input voltage fluctuations. Operating with phase loss can lead to drive component stress and damage.

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 Drive output current dropped below the threshold set in L6-02 for longer than the time set in L6-03, indicating a motor underload condition. This often signifies a mechanical failure such as a broken belt or coupling, or a sudden loss of load on the motor.

This is a warning displayed on the digital operator during a momentary power loss event. It indicates that incoming AC power has been interrupted, but the drive's control power supply is still being maintained. The alarm signifies the drive is in a ride-thru state and will precede a UV1 fault if power is not restored within the configured ride-thru time (L2-02).

The DC bus voltage fell below its trip point (≤190Vdc for 208-240Vac Drives; ≤380Vdc for 480Vac Drives). This is often due to low input voltage at the R/L1, S/L2, and T/L3 terminals, an acceleration time set too short, or excessive input voltage fluctuations, risking drive instability or shutdown.

An undervoltage condition detected in the Drive's control circuit while it is running. This can be caused by an external load connected to the drive pulling down its internal power supplies, or a fault within the control board itself, indicating a problem with the internal 24VDC or 15VDC supply.

The pre-charge contactor opened while the Drive was running, indicating a problem with the soft charge circuit. This is often caused by dirty contacts on the soft charge contactor, preventing it from functioning mechanically, and can lead to immediate shutdown and failure to start.