Siemens SINAMICS G120 Variable Speed Drive

This alarm indicates that one phase of the inverter's output is disconnected, suggesting a break in the power path to the motor. This condition can lead to motor malfunction, reduced performance, or potential damage if operated under unbalanced conditions.

A large ripple in the DC-link voltage has been detected, which can indicate issues with the input power supply, filter capacitors, or excessive harmonic distortion. This condition can affect inverter performance, efficiency, and potentially lead to premature component failure.

This alarm signifies that the braking resistor is overloaded due to excessive braking energy, or the installed resistor's rating is insufficient for the application's demands. Continuous overload can damage the resistor, its associated circuitry, or the drive itself if heat dissipation limits are exceeded.

This alarm indicates that the motor data identification process (parameter P1910) is active or has been selected to run. This is a normal operational state during commissioning or motor tuning, where the drive is learning the motor's electrical characteristics.

This alarm indicates that the speed control optimization process (parameter P1960) is active or has been selected to run. This is a normal state when the drive is fine-tuning its speed control parameters to achieve optimal performance and responsiveness.

This alarm signifies that the actual motor speed has either exceeded its maximum limit or deviates significantly from the setpoint, as indicated by status bits r2197.12 or r2197.7. This often points to an excessive motoring or regenerative load on the drive, or poor tuning of the speed controller.

This alarm occurs when an MMC-PS (Multi Media Card) is inserted into the drive while it is operating, especially if no card was present at startup. This action can potentially corrupt the drive's current parameter dataset upon the next power cycle if automatic cloning at startup is enabled, leading to incorrect drive configuration.

This warning indicates a loss of signal from the motor encoder, potentially causing the inverter to switch to sensorless vector control. Causes range from physical disconnection or faulty encoder hardware to incorrect parameterization where an encoder is expected but not configured or selected, leading to imprecise speed or position control.

This warning indicates an internal time slice overrun within the drive's Real-Time Operating System (RTOS). This typically points to an internal processing delay, excessive computational load, or a software anomaly that could affect system stability and performance.

This alarm indicates an issue with the PROFIBUS communication, specifically that an incorrect parameter or configuration telegram was received. This prevents the drive from being properly controlled or configured via the bus, leading to communication failure with the master.

This alarm signals an error within the PROFIBUS double word reference table, which is critical for data exchange. This typically indicates a corruption or inconsistency in how PROFIBUS data is mapped within the drive, potentially leading to incorrect data interpretation.

The drive has experienced a PROFIBUS communication timeout, specifically indicating that no actual data is being received from the Control Unit Processor (CUP). This can lead to a loss of real-time operational data, affecting monitoring and control if not addressed promptly, potentially halting automated processes.

A fatal software error has occurred within the PROFIBUS communication module, potentially related to hardware checks, general communication issues, or problems with the V1SL stack. This critical error can lead to a complete loss of PROFIBUS connectivity and drive control, rendering the system inoperable via PROFIBUS.

The PROFIBUS address configured for the drive is incorrect at startup, either due to an improper DIP switch setting or an incorrect value in parameter P0918. This prevents the drive from communicating correctly on the PROFIBUS network, leading to a loss of control from the PROFIBUS master.

Communication has been lost with the Communication Board (CB) within the drive. This indicates a potential hardware fault with the CB or its connection, preventing proper data exchange and potentially disrupting external communication protocols, leading to a loss of control or monitoring capabilities.

The Communication Board (CB) has reported an internal configuration error. This suggests that the parameters or settings for the CB are incorrect or inconsistent, preventing it from functioning as intended and disrupting communication capabilities, hindering proper integration into the control system.

The DC-link maximum voltage controller has been deactivated. This typically happens if the main supply voltage is consistently too high, if the motor is regenerating power back to the drive due to an active load, or during deceleration with high inertial loads. This can lead to excessive DC link voltage and potential damage to the drive components if not managed.

A safety-related parameter has been modified either during safety commissioning or a safety reset. This warning is issued to ensure that all safety changes are intentionally acknowledged and finalized, as unresolved changes can prevent the drive from entering a safe operational state, potentially compromising machine safety.

An inconsistency has been detected in the safety input signals, specifically related to the Safe Limited Speed (SLS) function. The drive will initiate a controlled deceleration (SS1) and eventually enter a Safe Torque Off (STO) state, issuing a fault due to the potential compromise of safety integrity.

The motor speed has exceeded the configured Safe Limited Speed (SLS) threshold, either upon entering SLS or exceeding its tolerance. This triggers a controlled deceleration (SS1), followed by a Safe Torque Off (STO) and a drive fault, indicating a potential safety violation due to excessive speed that could lead to injury or damage.

The drive is unable to switch on and remains in the READY state because its start is inhibited. This can be caused by a deactivated gate driver, an active safety function such as Safe Torque Off (STO), Safe Stop 1 (SS1), or Safe Limited Speed (SLS), or another inhibit condition, preventing motor operation.

A semaphore problem occurred during startup, preventing the drive from loading its last saved safety parameters and forcing it to load default values instead. This indicates a data integrity issue or timing problem, compromising the intended safety configuration and requiring immediate attention to restore safe operation.

The safety reset or safety commissioning process is currently active, indicated by parameter p0010 = 95. This prevents normal drive operation until the safety procedure is properly concluded, ensuring that all safety configurations are finalized and verified for safe machine control.

The dynamisation timer (r9660) for safety functions has expired, requiring a new dynamisation test. This test verifies the integrity of the safety circuit, and without performing it, the safety functions may not be fully trusted, preventing safe operation and potentially leaving the machine in an unsafe state.

The motor temperature sensor has an open or short circuit, causing a loss of its signal. This results in the drive's temperature monitoring switching to a thermal model instead of direct sensor input, which can lead to inaccurate temperature protection if the underlying issue is not resolved. Continuous operation with a faulty sensor could lead to motor overheating and damage.

One or more of the three-phase AC input power lines to the drive is disconnected or has failed while the drive is enabled and under load. This can lead to unbalanced operation, component stress, and potential damage to the inverter or motor if not corrected, causing reduced performance and premature equipment failure.

An earth fault has been detected, indicating an insulation breakdown where current is flowing to ground. This occurs when the sum of the phase currents exceeds 5% of the inverter's nominal current, potentially causing personnel hazard, equipment damage, or fire if left unresolved.

A critical hardware fault has occurred within the inverter's power stack, likely due to a short circuit in an IGBT or the chopper circuit, leading to excessive DC-link current. This indicates severe internal damage to the inverter power components and requires replacement to prevent further system failure and potential safety risks.

One of the inverter's output phases to the motor is disconnected or open-circuited. This causes unbalanced current flow to the motor, leading to excessive motor heating, reduced torque, and potential damage to both the motor and the inverter if operation continues.

Significant voltage ripple has been detected on the DC link of the inverter. This can be caused by issues with the input power supply, damaged DC link capacitors, or an internal power circuit problem. Large ripples lead to unstable operation and potential damage to the inverter's power components, risking system failure.

The gate driver, which controls the inverter's power transistors (IGBTs), is not enabled. This critical internal fault prevents the inverter from generating output voltage and can be indicative of a hardware issue with the gate drive board or a synchronization problem within the safety state machines. This renders the drive inoperable.

A read or write failure occurred in the EEPROM of the Basic Operator Panel (BOP) during parameter cloning or saving. This could be due to a faulty BOP, an EEPROM that is too small for the stored parameters, or an incompatibility, leading to an inability to store or retrieve non-volatile parameters essential for drive configuration.

An attempt was made to initiate a parameter cloning operation without a Basic Operator Panel (BOP) being physically connected to the drive. This prevents the cloning process from starting, as the BOP is required for this function, meaning parameters cannot be loaded or saved via this method.

The Basic Operator Panel (BOP) is either empty (no parameters stored) or contains invalid data, causing a failure during parameter cloning. This prevents the drive from being configured correctly using the BOP, potentially leading to incorrect operation or startup issues.

An attempt was made to clone parameters using a Basic Operator Panel (BOP) that contains parameters created on a different type of drive. This incompatibility prevents successful parameter transfer, as the configurations are not designed for the current drive, leading to configuration errors.

An internal communication failure between the inverter's power module and control unit has occurred, indicated by an ASIC timeout. This can be caused by loose connections, electromagnetic interference (EMC), or a faulty internal component, leading to a loss of control and drive shutdown, impacting operational reliability.

The parameter cloning process using the MMC-PS (Memory Card Parameter Save) has failed due to various reasons, including an incorrectly formatted or missing MMC-PS, an inability to write to the MMC, or a corrupted cloning file. This prevents successful transfer of drive parameters, impacting drive configuration and operation.

The parameter cloning file on the MMC-PS exists but its contents are corrupt or invalid, specifically affecting the control word data. This prevents the drive from correctly loading parameters, potentially leading to incorrect operation or failure to start due to an invalid configuration.

The parameter cloning file found on the MMC-PS is from an incompatible drive type. Although the file exists, its parameters cannot be applied to the current drive, preventing proper configuration and startup due to a mismatch in hardware or firmware versions.

The drive attempted to perform an automatic parameter clone during startup but failed because the `Clone00.bin` file was not found in the `/USER/SINAMICS/DATA` directory on the MMC. This prevents automatic configuration, requiring manual intervention to either provide the file or disable the cloning function.

The drive is not receiving setpoint values from the PLC (Programmable Logic Controller) within the configured telegram off time. This indicates a communication issue or incorrect timing, causing the drive to lose its command reference and cease controlled operation, impacting automation sequences.

The drive has failed to receive setpoint values via the USS (Universal Serial Interface) communication protocol within the configured telegram off time. This suggests a problem with the USS master device or the communication settings, causing the drive to lose its operational commands and halt controlled operation.

The drive has failed to receive setpoint values via the USS (Universal Serial Interface) communication protocol within the configured telegram off time. This suggests a problem with the USS master device or the communication settings, causing the drive to lose its operational commands and halt controlled operation.

The drive is not receiving setpoint values from the Control Panel within the specified telegram off time. This indicates a communication issue or incorrect timing between the control panel and the drive, causing a loss of command signals and controlled operation, thus preventing manual control.

An external fault has been triggered, typically through a command input such as control word 2, bit 13. This indicates an issue originating outside the drive itself, requiring investigation of the external control logic or connected devices that are signaling the fault, which can stop the drive unexpectedly.

The drive has lost feedback from the encoder, which is critical for precise speed and position control. This can be caused by physical disconnections, a faulty encoder, incorrect parameter settings (like p0400 or p1300), or the encoder signal being outside expected limits, leading to uncontrolled motor operation or a complete shutdown.

A watchdog timer reset has occurred, indicating a critical software error within the drive's control unit. This signifies that the software has become unresponsive or entered an unexpected state, leading to a system reset and potential loss of control over the connected motor.

A stack overflow error has occurred, indicating a severe software fault or processor failure within the drive's control unit. This is a critical internal error where memory allocated for program execution has been exhausted, leading to system instability or crash and making the drive inoperable.

The feedback signal for the PID controller has dropped below its configured minimum threshold (p2268). This indicates an issue with the feedback sensor, its wiring, or an incorrect parameter setting, causing the PID loop to lose its reference and potentially leading to unstable control or undershoot.

The feedback signal for the PID controller has exceeded its configured maximum threshold (p2267). This indicates an issue with the feedback sensor, its wiring, or an incorrect parameter setting, causing the PID loop to lose its reference and potentially leading to unstable or overdriven control.

The drive failed to validate its configuration vector (SZL vector) during startup, indicating a mismatch between the programmed configuration and the actual hardware, or an internal data integrity issue. This critical fault prevents the drive from starting and operating, potentially due to incorrect power modules or IO boards.

An inconsistency has been detected in the EEPROM data, particularly related to safety parameters. This means the critical safety configuration was not written correctly to persistent memory, which can compromise the drive's safety functions and prevent safe operation, potentially leading to unsafe machine behavior.

A critical data exchange error has occurred between the internal processors, indicating a defect in the cross-comparison function or processor communication, often related to safety functions. This can be caused by EMC interference or internal hardware issues, leading to unsafe operating conditions or a drive shutdown.

The drive's internal hardware (safety or non-safety related) could not be correctly identified during startup or runtime. This indicates a mismatch between the expected and detected hardware configuration or a fundamental issue with processor communication, preventing the drive from operating safely.

The drive has detected that the motor's operating frequency has exceeded the configured maximum limit, as monitored by one or both internal processors. This can occur due to an application anomaly, incorrect parameterization of speed limits, or an issue with the safety monitoring system, potentially leading to overspeed and mechanical damage.

This fault indicates an internal software issue, likely a buffer overflow during checksum calculations for parameter access or an endless safety loop within the P1 or P2 processors. Errors with r0949 > 100 are for Siemens internal diagnostics. This is a critical internal system error that requires specialized attention.

This fault signals an error during safety parameterization, which can happen during startup, commissioning, or a safety reset. It's often related to checksum mismatches, internal parameter transfer failures, buffer finalization issues, or problems saving data to EEPROM. It can also indicate communication channel problems between processors, pointing to a drive's safety configuration integrity issue.

This fault indicates a timeout during a safety reset operation on either the P1 or P2 processor, meaning the system failed to reset within the expected timeframe. This can prevent the drive from reinitializing correctly, often caused by an unexpected system hang during the reset process.

This fault occurs when the drive rejects a write request for one or more safety parameters, often due to problems finalizing parameters, an incorrect safety password, or an insufficient tolerance setting (p9691/p9891 too small). The drive may revert to previous settings, indicating an issue with security or parameter validation within the safety configuration.

This fault occurs when checksums related to safety commissioning are inconsistent, preventing the drive from exiting the commissioning state. This indicates that safety parameters in p9798, p9799, p9898, or p9899 do not match as required, signaling a configuration error that must be resolved for safe operation.