Yaskawa P1000 AC Drive

This alarm indicates a serial communications issue. It is shown when parameter BO 11 (Communication Fault Enable) is enabled and parameter AO 22 (Cable Loss Speed) is set to a value other than 0, allowing the drive to continue at the last speed.

A communication error has occurred on the MEMOBUS/Modbus network interface. This indicates a problem with data transmission or reception on the serial communication bus.

An error occurred during the analog-to-digital conversion process within the drive. This can affect the accuracy of sensor readings and internal measurements.

An issue was detected with the Pulse Width Modulation (PWM) data generation, which is critical for controlling the motor's voltage and frequency. This indicates an internal control problem.

An error was detected in the data stored or accessed from the drive's EEPROM memory. This can lead to corrupted parameters and incorrect drive operation.

The drive detected an improper connection or fault with the terminal board. This indicates that the main control board is not properly communicating with the terminal interface, affecting I/O.

A serial communication fault occurred during data exchange with the EEPROM memory. This prevents reliable parameter storage and retrieval, potentially causing incorrect drive settings.

A fault was detected in the drive's Random Access Memory (RAM), which is used for temporary data storage during operation. This can lead to unstable drive performance.

An exception occurred within the drive's flash memory circuit, which stores firmware and other critical data. This indicates a severe internal error that may require firmware reinstallation.

The internal watchdog timer circuit in the drive has triggered an exception. This typically indicates that the main processor is not responding or has entered an unexpected state, requiring a reset.

A general fault has been detected within the drive's control circuitry. This indicates an internal malfunction of the control logic, affecting overall drive operation.

An error has occurred with the internal clock circuit of the drive, which is essential for timing and synchronization of operations. This can cause timing inaccuracies and operational issues.

A timing fault has been detected within the drive's internal operations, indicating an issue with synchronized processes. This can lead to incorrect command execution.

A general fault has been detected within the drive's control circuitry. This indicates an internal malfunction of the control logic, affecting overall drive operation. (Similar to CPF14).

A general fault has been detected within the drive's control circuitry. This indicates an internal malfunction of the control logic, affecting overall drive operation. (Similar to CPF14).

A hardware fault was detected during the initial power-up sequence of the drive, preventing it from starting correctly. This indicates a critical issue with internal components.

A hardware fault related to communication circuits was detected during the drive's communication startup sequence. This can prevent the drive from establishing network communication.

A fault occurred within the analog-to-digital conversion circuitry of the drive. This affects the accuracy of input signal readings from sensors and other analog sources.

An error related to the current offset calibration or measurement has occurred within the drive. This affects the accuracy of current readings and motor control.

This fault occurs when the drive loses communication, and parameter F6-03 is configured to stop the drive. Specifically, if the time between messages exceeds the Cable Loss Timeout (AO 21) interval, the drive declares EF0 and sets the speed command (AO 1) to 0, stopping according to F6-03 settings.

An external fault signal has been received by the drive via digital input terminal S1. The specific cause depends on the external device wired to S1 and its fault condition.

An external fault signal has been received by the drive via digital input terminal S2. The specific cause depends on the external device wired to S2 and its fault condition.

An external fault signal has been received by the drive via digital input terminal S3. The specific cause depends on the external device wired to S3 and its fault condition.

An external fault signal has been received by the drive via digital input terminal S4. The specific cause depends on the external device wired to S4 and its fault condition.

An external fault signal has been received by the drive via digital input terminal S5. The specific cause depends on the external device wired to S5 and its fault condition.

An external fault signal has been received by the drive via digital input terminal S6. The specific cause depends on the external device wired to S6 and its fault condition.

An external fault signal has been received by the drive via digital input terminal S7. The specific cause depends on the external device wired to S7 and its fault condition.

The drive encountered an error while attempting to write data to its internal EEPROM memory. This can affect parameter saving and potentially lead to corrupted configurations.

The drive has detected that the connection is broken or the master device has stopped communicating with the drive. This fault indicates a loss of active communication, specifically related to Apogee FLN configurations.

The drive has detected a loss or significant deviation in the feedback signal for its PID control loop. This prevents proper process control, as the drive cannot accurately assess the controlled variable. This is another PID feedback loss detection, distinct from FbL (0028H) but with the same name.

The drive has detected a loss or significant deviation in the feedback signal for its PID control loop. This prevents proper process control, as the drive cannot accurately assess the controlled variable.

A ground fault has been detected in the motor, motor cables, or the drive output. This indicates current leakage to ground, posing a safety risk and potential equipment damage.

The drive has detected a loss of one or more phases at its output terminals, typically indicating a motor cable break, poor connection, or motor winding issue. This prevents proper motor operation.

The drive detected an imbalance in the current magnitudes across its output phases. This can indicate a motor issue, output wiring problem, or unbalance in the motor load.

The drive has detected an error related to its internal PLC functionality or communication, specifically PLC Detection Error 1. This affects programmed logic execution.

The drive has detected an error related to its internal PLC functionality or communication, specifically PLC Detection Error 2. This affects programmed logic execution.

The drive has detected a loss of one or more phases in its incoming AC power supply. This can lead to improper operation, reduced motor performance, or drive damage.

The drive has attempted to perform a speed search restart multiple times consecutively without success, exceeding the allowed limit. This suggests an underlying issue preventing stable motor operation.

The drive has detected that the motor has pulled out of synchronization, often due to severe overload or insufficient torque. This results in the motor losing speed control.

The drive detected that the motor torque has fallen below a preset undertorque threshold. This can indicate a broken shaft, loss of load, or belt slippage, suggesting a mechanical failure.

The motor has been operating under an underload condition, where the current drawn is significantly lower than expected for the commanded speed. This can indicate a broken belt, pump cavitation, or loss of load.

The drive detected an undervoltage condition in the main circuit power supply. This indicates that the incoming AC voltage is below the acceptable operating threshold.

The drive detected an undervoltage condition specifically in the control power supply circuit. This affects the internal logic and control functions of the drive.

An issue with the drive's internal soft charge circuit has been detected. This circuit manages the initial charging of the DC bus capacitors, preventing high inrush currents.

A communication error has occurred with an installed option board. This suggests an issue with the option board itself or its communication with the main drive, potentially preventing external device control.

An issue occurred during the setup or configuration of the network node for the drive. This indicates a problem with network initialization, preventing proper communication.

An overcurrent condition has occurred, indicating that the output current exceeded the drive's permissible limits. This fault can also be displayed in the event of an IGBT failure, suggesting internal power component damage.

A general hardware fault has occurred within the drive. This category includes faults such as oFx, indicating an internal component malfunction and requiring internal diagnosis.

The temperature of the drive's heatsink has exceeded its safe operating limit. This indicates insufficient cooling for the drive's power components.

The temperature of the drive's heatsink has exceeded its safe operating limit, indicating insufficient cooling. This is another heatsink overheat detection, distinct from oH (0009H) but with the same name.

The motor's internal PTC thermistor input has triggered, indicating that the motor has exceeded its safe operating temperature. This protects the motor from thermal damage.

The motor's internal PTC thermistor input has triggered, indicating that the motor has exceeded its safe operating temperature. This is another motor overheat detection, distinct from oH3 (001DH) but with the same name.

The motor connected to the drive has been operating under an overload condition, exceeding its thermal limits. This can lead to motor damage or reduced lifespan.

The drive itself has been operating under an overload condition, exceeding its continuous current rating. This can lead to drive shutdown or damage if not addressed.

The drive detected that the motor torque has exceeded a preset overtorque threshold. This indicates a mechanical issue, excessive load, or incorrect parameter settings.

An overload condition occurred during high slip braking, indicating excessive regenerative energy or an issue with the braking process. This can lead to component overheating.

An issue related to the connection or operation of the digital operator (keypad) has occurred. This could be due to improper connection or a communication problem between the operator and the drive.

The drive's DC bus voltage has exceeded the maximum permissible limit. This typically occurs during deceleration of high inertia loads or due to a high input voltage.

The external braking resistor connected to the drive has overheated. This indicates excessive energy dissipation, potentially due to frequent or heavy braking, or inadequate resistor sizing/cooling.

An error has occurred in the drive's internal output voltage detection circuit, leading to an inability to accurately measure output voltage. This impacts motor control and protection.