Siemens SINAMICS G120

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.

This alarm indicates that the settings transferred to the inverter are not compatible with the device. This commonly occurs during maintenance after component replacement or firmware updates when configuration data is loaded from an Operator Panel. Continuing operation with incompatible settings can lead to unexpected behavior or failure of the drive.

The selected service/maintenance interval for this motor has been reached. The alarm value (r2124) indicates the motor data set number. This alarm signifies that routine maintenance is due for the motor. Ignoring it can lead to decreased performance, potential component wear, or unexpected failures if the underlying maintenance is critical for continued operation.

The parameterization of the motor holding brake or Safe Brake Control (SBC) contains an illogical or contradictory configuration, such as p1215 = 0 or 3 while p9602 = 1. This prevents correct and safe brake operation, potentially leading to unintended motor movement.

The PROFIsafe configuration in the higher-level control differs from that in the drive. This inconsistency can lead to communication errors or safety function issues, preventing reliable and safe operation. Specific alarm values (r2124=1 or r2124=2) provide more detail.

The combination of the motor and power unit is unsuitable, specifically if the ratio between the rated power unit current (r0207[0]) and rated motor current (p0305) is not greater than 5. This mismatch can lead to sporadic C01711 or C30711 messages and suboptimal performance or even damage over time.

The set time (p9661) for monitoring the forced checking procedure (test stop) for the 'STO via Power Module terminals' function has been exceeded. This indicates an overdue safety test that must be performed to maintain the integrity of the Safe Torque Off function.

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 inverter's automatic self-test during power-up was interrupted because the 'STO via Power Module terminals' function is active. This prevents the drive from completing its initialization and starting normally, indicating an unintended or misconfigured safety state at startup.

The system is actively waiting for communication, likely with the F host. This alarm indicates a potential disruption or delay in the communication link, preventing the inverter from receiving necessary commands or operational data from the host controller.

The alarm threshold for the power semiconductor's depletion layer overtemperature within the AC converter has been reached. This indicates the semiconductor junction is overheating. If the temperature continues to rise by an additional 15 K, it will trigger fault F30025, which can lead to drive shutdown and potential component damage.

The alarm threshold for the air intake temperature of the power unit has been reached, typically at 42 °C. This indicates insufficient cooling or high ambient temperatures affecting the drive's internal environment. If the air intake temperature increases by an additional 13 K, it will lead to fault F30035, likely resulting in a drive shutdown.

The alarm threshold for the rectifier's overtemperature has been reached, indicating excessive heat generation in the input rectifier stage. This can be due to overload or cooling issues. If the rectifier temperature rises by an additional 5 K, it will trigger fault F30037, potentially causing the drive to trip and risking damage to the rectifier components.

This alarm indicates that the calculated temperature difference between the power chip and the heat sink has exceeded the permissible limit, primarily for blocksize power units. It signifies a potential thermal imbalance or overload condition that, if not self-corrected, can lead to fault F30024. The drive initiates an appropriate overload response based on p0290.

This alarm is initiated when the actual spindle temperature (r4105) exceeds the alarm threshold set in p4102[0] for the spindle's supplementary temperature evaluation. The alarm will clear once the temperature falls below this threshold value, factoring in a fixed 2 K hysteresis.

An external condition has triggered "External alarm 1," typically via binector input p2112. This alarm indicates an external issue that requires attention but does not immediately stop the drive. Ignoring this alarm risks escalation of the external problem, potentially causing a subsequent fault, damage, or process disruption if the root cause remains unaddressed.

This alarm indicates that the DC link voltage is too low, causing the load supply to be switched out. The alarm value (r2124) displays the DC link voltage at the time of the trip. A common cause is the AC line supply not being switched on or being inadequate. If ignored, the drive will be unable to operate.

The alarm threshold for the power unit's internal temperature has been reached. This indicates that the internal components are operating at elevated temperatures, potentially due to high ambient temperature, insufficient cooling, or a fan failure. If the temperature continues to rise, it may trigger fault F30036, leading to a drive trip and potential hardware damage.

The power supply voltage for the brake has dropped below 21.6V (24V - 10%) when the brake is commanded to open. The alarm value (r2124) indicates the detected voltage. This undervoltage can prevent the brake from opening properly, leading to mechanical binding, potential damage to the brake mechanism, or a failure to start the motor.

Frequencies detected on the DC link voltage suggest line asymmetry or the failure of a line or motor phase. If this alarm persists, it will eventually trigger fault F30011 after a specific duration. This condition causes imbalanced currents, increased losses, and premature component wear, and if unresolved, will lead to a drive trip, interrupting operation.

The power unit has detected an overvoltage condition in the DC link during a pulse inhibit state, likely due to an excessively high device supply voltage or an incorrectly dimensioned line reactor. Persistent DC link overvoltage can critically stress the power electronics, significantly reducing the drive's lifespan. If left unresolved, it can lead to catastrophic hardware failure.

A forced checking procedure (test stop) for the fail-safe digital output is currently in progress. This is a normal safety test to verify the output's functionality and indicates that the system is performing a self-check.

The system is waiting for the Safe Torque Off (STO) function of the extended safety functions to be deselected via Safety Monitor Module (SMM) as part of an automatic test stop procedure. This can also indicate active safety messages preventing STO deselection.

An error occurred during the evaluation of a temperature sensor connected to the power unit. This can manifest as a wire breakage or a disconnected sensor (e.g., KTY: R > 2120 Ohm) or a measured resistance that is too low (e.g., PTC: R < 20 Ohm, KTY: R < 50 Ohm). Accurate temperature monitoring is crucial for protecting the power unit from overheating. If unaddressed, this could lead to undetected overheating and potential damage to components.

This alarm indicates that an event occurred on the power unit which the Control Unit firmware cannot interpret. This typically happens when the power unit has newer firmware than the Control Unit, leading to unrecognized alarm codes. While not immediately critical, it signifies a firmware version mismatch that can obscure actual issues. The risk is that critical alarms might go uninterpreted, leading to delayed troubleshooting or missed underlying problems with the drive.

This alarm is initiated when the actual temperature (r4105[0]) for channel 0 on Terminal Module 120 (TM120) or Terminal Module 150 (TM150) exceeds its configured alarm threshold (p4102[0]). A timer (p4103[0]) is also started. The alarm will clear once the temperature falls below the threshold, factoring in the defined hysteresis (p4118[0]).

This alarm is initiated when the actual temperature (r4105[1]) for channel 1 on Terminal Module 120 (TM120) or Terminal Module 150 (TM150) exceeds its configured alarm threshold (p4102[2]). A timer (p4103[1]) is also started. The alarm will clear once the temperature falls below the threshold, factoring in the defined hysteresis (p4118[1]).

This alarm is initiated when the actual temperature (r4105[2]) for channel 2 on Terminal Module 120 (TM120) or Terminal Module 150 (TM150) exceeds its configured alarm threshold (p4102[4]). A timer (p4103[2]) is also started. The alarm will clear once the temperature falls below the threshold, factoring in the defined hysteresis (p4118[2]).

This alarm is initiated when the actual temperature (r4105[3]) for channel 3 on Terminal Module 120 (TM120) or Terminal Module 150 (TM150) exceeds its configured alarm threshold (p4102[6]). A timer (p4103[3]) is also started. The alarm will clear once the temperature falls below the threshold, factoring in the defined hysteresis (p4118[3]).

This alarm is initiated when the actual temperature (r4105[4]) for channel 4 on Terminal Module 150 (TM150) exceeds its configured alarm threshold (p4102[8]). A timer (p4103[4]) is also started. The alarm will clear once the temperature falls below the threshold, factoring in the defined hysteresis (p4118[4]).

This alarm is initiated when the actual temperature (r4105[5]) for channel 5 on Terminal Module 150 (TM150) exceeds its configured alarm threshold (p4102[10]). A timer (p4103[5]) is also started. The alarm will clear once the temperature falls below the threshold, factoring in the defined hysteresis (p4118[5]).

This alarm is initiated when the actual temperature (r4105[6]) for channel 6 on Terminal Module 150 (TM150) exceeds its configured alarm threshold (p4102[12]). A timer (p4103[6]) is also started. The alarm will clear once the temperature falls below the threshold, factoring in the defined hysteresis (p4118[6]).

This alarm is initiated when the actual temperature (r4105[7]) for channel 7 on Terminal Module 150 (TM150) exceeds its configured alarm threshold (p4102[14]). A timer (p4103[7]) is also started. The alarm will clear once the temperature falls below the threshold, factoring in the defined hysteresis (p4118[7]).

This alarm is initiated when the actual temperature (r4105[8]) for channel 8 on Terminal Module 150 (TM150) exceeds its configured alarm threshold (p4102[16]). A timer (p4103[8]) is also started. The alarm will clear once the temperature falls below the threshold, factoring in the defined hysteresis (p4118[8]).

This alarm is initiated when the actual temperature (r4105[9]) for channel 9 on Terminal Module 150 (TM150) exceeds its configured alarm threshold (p4102[18]). A timer (p4103[9]) is also started. The alarm will clear once the temperature falls below the threshold, factoring in the defined hysteresis (p4118[9]).

This alarm is initiated when the actual temperature (r4105[10]) for channel 10 on Terminal Module 150 (TM150) exceeds its configured alarm threshold (p4102[20]). A timer (p4103[10]) is also started. The alarm will clear once the temperature falls below the threshold, factoring in the defined hysteresis (p4118[10]).

This alarm is initiated when the actual temperature (r4105[11]) for channel 11 on Terminal Module 150 (TM150) exceeds its configured alarm threshold (p4102[22]). A timer (p4103[11]) is also started. The alarm will clear once the temperature falls below the threshold, factoring in the defined hysteresis (p4118[11]).

A STOP A command has been initiated, typically as a consequence of another primary safety-related event such as C01701, C01706, C01714, or C01716 (or their C307xx equivalents). This action results in an uncontrolled stop by immediately removing power from the motor.

A STOP B command has been initiated, usually as a consequence of another primary safety-related event like C01706, C01714, or C01716 (or their C307xx equivalents). This action brings the drive to a controlled stop via a defined deceleration ramp.

The limit for Safe Acceleration Monitoring (SAM) or Safe Brake Ramp (SBR) has been exceeded. This indicates that the motor braking response is not within the parameterized tolerance, posing a risk of uncontrolled deceleration and potential mechanical damage or safety hazard.

This alarm signifies a defect within a safety monitoring channel, detailed by r2124 fault values. Causes include data cross-check errors between processors (0-2, 4-43, 58-999), difference in position actual value exceeding tolerance (p9542), differing monitoring function tolerance values (44-57), or an expired watchdog timer (1000) due to frequent F-DI signal changes. Initialization errors (1001), test stop issues (1005, 1011), cyclic communication failure (1020), or low current for encoderless acquisition (1041) can also trigger this alarm.

This alarm indicates a defect occurring during the processing of Fail-safe I/O (F-IO). This suggests a problem with the safety-related input/output circuitry or its configuration, potentially compromising safety functions if not addressed.

The inverter is currently performing a forced checking procedure (test stop) for its extended motion monitoring functions. This is a normal operational state during a safety test and indicates that the system is validating its safety capabilities.

The acceptance test mode is currently active, indicating that safety functions are being validated. This is a normal state during commissioning or re-validation of safety parameters and functions.

A defect has been detected in a monitoring channel, with fault value r2124 providing more detailed information. This condition often initiates a STOP response and an inverter fault, indicating a critical issue with the safety monitoring system that requires immediate attention.

A defect has occurred during the processing of fail-safe inputs/outputs (F-IO), potentially due to incorrect wiring or parameter settings. This can compromise the integrity of safety-related I/O signals, leading to unpredictable safety reactions or system failures.

The Safely Limited Speed (SLS) has been exceeded, meaning the motor is moving faster than the configured safe speed limit. This indicates a failure in speed monitoring or an incorrect speed setpoint from the higher-level control, posing a significant safety risk.

The tolerance for the 'Safe Direction of Motion' (SDI) function has been exceeded. This indicates that the motor is moving in an unintended or unsafe direction, or its deviation from the intended direction is too great, posing a safety risk if not immediately addressed.

A discrepancy error has been detected in either the fail-safe digital inputs or outputs, indicating inconsistent signals or faulty wiring. This compromises the reliability of safety-related I/O, potentially leading to incorrect safety reactions.

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.

The drive-integrated "Safety Integrated" function on the Control Unit (CU) has detected a fault, initiating a STOP A (Safe Torque Off via the safety shutdown path). This can be caused by an unsuccessful forced checking procedure of the safety shutdown path or as a subsequent response to a defect in a monitoring channel (F01611). The drive will react with an OFF2 state, requiring an immediate POWER ON cycle for acknowledgment.

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.

The drive-integrated "Safety Integrated" function on processor 1 has detected a fault in the crosswise data comparison between its two monitoring channels, initiating a STOP F. This often leads to fault F01600 as a subsequent response. A defect in a safety monitoring channel is a critical safety system failure that must be resolved to ensure the safe operation of the machine and compliance with safety standards.

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.

An error has occurred with the safety data's sign-of-life signal, indicating a potential communication or integrity issue within the safety functions. This can be caused by EMC disturbances or an inadmissible voltage at a Control Unit digital output. Such an error critically impacts the system's ability to maintain safe operation.

The motor holding brake control is malfunctioning, posing a risk of uncontrolled motor movement. This can stem from an incorrect p1278 setting, disconnected or interrupted brake cables, a ground fault, or a short-circuit in the brake winding. A fault in the Safe Brake Relay, Control Unit, or Power Module could also be the cause.

The system has detected that a component has been replaced, requiring acknowledgment and data saving to integrate the new part and ensure consistent operation. Failure to perform these steps can prevent proper functionality and lead to an inconsistent safety state.

This fault is part of a group (F01641, F01650, F01680, F30680) that is expected to occur temporarily during specific corrective maintenance procedures, such as replacing a Control Unit or the entire inverter. It does not indicate a persistent problem if the full replacement and recommissioning steps are followed. The risk is negligible if acknowledged as part of the procedure.

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.

Synchronization of safety time slices within the Control Unit was unsuccessful, which can prevent proper and safe operation of the drive. This might indicate a transient issue or a deeper problem with the unit's internal timing or processing, affecting safety integrity.

There is an error in the PROFIBUS or PROFINET configuration of the safety slot, either on the master side or the Control Unit. This prevents safe communication with the higher-level controller and can lead to system shutdown, compromising integrated safety functions.

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.

Parameter processor 2 is reporting an incorrect state or value, which could affect safety function processing. This can prevent proper configuration and operation of safety features, potentially leading to an unsafe state or system malfunction.

The PROFIsafe telegram number configured in p60022 is not suitable for the enabled safety functions. This indicates an inconsistency in PROFIsafe communication setup, which can prevent safe data exchange and lead to safety function failures.

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.

The simulation mode for the digital inputs of the Control Unit (F-DI) is currently active. Safety functions cannot operate reliably while in simulation mode, which could mask actual input conditions and lead to unsafe operation if not deactivated before live use.

An internal communication error has occurred within the Control Unit. This indicates a disruption in data exchange between internal components, which can lead to unpredictable behavior or system shutdown, compromising operational stability and safety.

The attempt to copy Safety Integrated (SI) parameters was rejected. This can happen if p9700 is not 0, or if safety functions (p9501, p9601) are active, preventing critical parameter changes. This can lead to an inconsistent or un-saved configuration, especially after modifying safety settings.

The inverter has detected a critical internal defect, which could be a hardware failure, persistent software issue within the Control Unit, or an unconfigured 'STO via Power Module terminals' with active terminals. This compromises system integrity and requires immediate attention to prevent operational failure.

A static '1' signal is present at the F-DI input designated for safe acknowledgment of safety functions. This indicates an incorrect input state, preventing proper acknowledgment or causing a fault, which can stop operations or prevent safety functions from being reset.

This fault is part of a group (F01641, F01650, F01680, F30680) that is expected to occur temporarily during specific corrective maintenance procedures, such as replacing a Control Unit or the entire inverter. It does not indicate a persistent problem if the full replacement and recommissioning steps are followed. The risk is negligible if acknowledged as part of the procedure.

An incorrect or invalid parameter value has been detected. The fault value (r0949) provides additional information about the specific parameter affected, which needs to be corrected for proper operation. An incorrect parameter can lead to misconfigured safety functions or drive behavior.

A configured monitoring function is not supported by the current hardware or software version. This indicates a mismatch between desired functionality and system capabilities, preventing the function from operating correctly or safely.

The Safely Limited Speed (SLS) function is not enabled, even though it's required or configured for the application. This prevents the system from limiting speed safely, potentially leading to hazardous overspeed conditions if the drive operates outside its safe limits.

A problem has occurred during data backup to the Non-Volatile RAM (NVRAM), potentially leading to loss of configuration data if power is removed. This indicates a critical memory or hardware issue that could result in needing to reconfigure the drive after a power cycle.

A parameter value is not permitted or is incorrect for encoderless operation, indicating an invalid configuration for the current operating mode. This can lead to improper motor control and potentially unsafe conditions if speed or position feedback is compromised.

Safety-related parameters have been modified, requiring a power cycle for the changes to take effect and be properly stored. Operating without a power cycle could result in an inconsistent or unapplied safety state, compromising machine safety.

The set time (p9559) for performing the forced checking procedure (test stop) of the extended functions has been exceeded. This indicates a required safety test is overdue, compromising safety integrity if not performed and potentially leading to a fault state.

An error has been detected in the evaluation of the motor temperature sensor configured in p0601. This could be due to a wire breakage, the sensor being disconnected (e.g., KTY resistance > 2120 Ohm), or the measured resistance being too low (e.g., PTC resistance < 20 Ohm, KTY resistance < 50 Ohm). The fault causes an OFF1 reaction and prevents proper motor temperature monitoring, risking motor damage from overheating if not resolved.

This fault is issued immediately if the actual spindle temperature (r4105) exceeds the fault threshold p4102[1]. Alternatively, if the alarm threshold p4102[0] is exceeded and the delay time set in p4103 expires without the temperature falling below the alarm threshold, this fault is also triggered. The fault requires acknowledgment and clears only when the temperature falls below the fault threshold, considering a fixed 2 K hysteresis.

The closed-loop control parameters have been incorrectly configured, for example, setting p0356 (L_spread) to 0. This fault prevents the drive's control algorithms from functioning correctly, potentially leading to erratic behavior or inability to operate. The fault value (r0949) indicates the specific parameter number that is incorrectly set.

This fault occurs when a macro cannot be executed due to various configuration or data errors. The fault value (r0949, hexadecimal) provides detailed supplementary information, indicating issues such as an invalid file for the trigger parameter, incorrect data types within the macro (e.g., index, number, or bit not U16), undefined error levels or modes, or attempts to write to parameters that are read-only or not available via macro. Such issues prevent automated configuration or specific functions from running.

This fault indicates that the drive has attempted to automatically restart after other faults, reaching the maximum number of attempts defined by parameter p1211. It means a recurring issue is present, and the automatic restart function has been deactivated. Manual acknowledgement and resolution of underlying faults are required to prevent continuous, potentially damaging, restart attempts and ensure safe operation.

A phase-to-phase short-circuit or a ground fault has been detected at the motor-side output terminals of the converter. The fault value specifies the exact short-circuit type or ground fault with current component. This is a critical electrical fault that can cause immediate and severe damage to the power module or motor, necessitating rapid isolation and repair to prevent costly failures and prolonged downtime.

No rated data is stored in the power unit's EEPROM, meaning the drive lacks essential operational parameters. Without this critical data, the power unit cannot be correctly configured, initialized, or operated. This fault renders the drive inoperable, as attempts to run it without appropriate parameters could lead to unpredictable behavior or damage.

An external condition has triggered "External fault 1," typically via binector input p2106. This fault indicates a critical external issue that has caused the drive to trip. The drive will cease operation, and the external problem must be identified and resolved before the drive can be reset and restarted, ensuring the safety and integrity of the overall system.

This fault indicates a phase failure in the motor feeder cable. It can also occur if the motor stalls in U/f control, leading to zero current in one phase due to current asymmetry, or if closed-speed control is unstable, generating oscillating torque. Note that chassis power units do not monitor this condition. If left unresolved, this can lead to motor damage, drive instability, and unexpected shutdowns.

This fault occurs when the hardware current limitation in a specific phase (U, V, or W, indicated by r0949) has been activated excessively. This points to issues such as incorrect closed-loop control parameters, faults in the motor or power cables, excessively long power cables, high motor load, or a defective power unit. Repeated current limiting causes stress on components and leads to drive shutdowns.

The air intake temperature in the power unit has exceeded the permissible limit, typically 55 °C. This condition signifies critical overheating of the incoming air, often caused by high ambient temperatures, insufficient airflow, or a fan failure. This fault forces an OFF1 or OFF2 reaction, stopping the drive, and cannot be acknowledged until the temperature falls below the alarm threshold of A05002.

The internal temperature of the drive converter has exceeded its permissible operating limit. This critical condition is typically caused by insufficient cooling, a fan failure, sustained overload, or an excessively high ambient temperature. The fault triggers an OFF2 reaction, shutting down the drive, and cannot be acknowledged until the internal temperature has fallen below the permissible limit minus 5 K.

An EEPROM data error has occurred within the power unit module, indicating either inconsistent data (fault values 0, 2, 3, 4) or data incompatible with the Control Unit firmware (fault value 1). This error implies a critical issue with the power unit's fundamental configuration or operational data. The drive cannot function correctly or safely until the corrupted data source is replaced.

An overcurrent condition has been detected in the braking chopper circuit. This signifies excessive current flow, often due to a short-circuited braking resistor or an improperly sized external resistor. An overcurrent can severely damage the braking chopper or resistor, leading to a complete loss of braking capability, uncontrolled deceleration, or even a fire hazard if sustained.

The internal cooling fan of the power unit has failed and is likely defective. Proper cooling is crucial for maintaining the power unit's operational temperature. A malfunctioning fan leads to inadequate heat dissipation, risking severe overheating, thermal trips, reduced performance, and potentially permanent damage to the power unit if not replaced.

At least one actual value channel on the Power Stack Adapter (PSA) has been detected as incorrect. This means the drive is receiving erroneous feedback for critical operational parameters, compromising its control algorithms. Inaccurate actual values can lead to unstable motor operation, incorrect control responses, or damage to the motor or drive due to misinterpretation of real-time conditions.

The drive-integrated "Safety Integrated" function on processor 2 has detected an error and initiated a STOP A. This is often caused by an unsuccessful forced checking procedure of the safety shutdown path or as a consequence of F30611. This fault indicates a critical issue within the safety system, preventing drive operation and requiring immediate resolution to maintain machine and personnel safety.

A defect has been detected in a monitoring channel. The fault value r0949 provides more detailed information on the specific issue. This indicates a critical problem with safety monitoring that needs further investigation to ensure safe operation.

The Safe Torque Off (STO) function is active, meaning the motor's torque-generating energy is prevented, and the motor is freely rotating or at a standstill. This is a safety state initiated to prevent unintended startup, not necessarily a fault.

The Safe Stop 1 (SS1) function is active, meaning the motor is brought to a standstill via a controlled ramp, and then STO is activated. This is a safety state initiated to safely stop the motor, not necessarily a fault.

A fault was detected during the inverter's power-up sequence, preventing it from starting correctly. This could be a hardware issue or a configuration problem encountered during initialization, which needs to be resolved for the drive to become operational.

This fault is part of a group (F01641, F01650, F01680, F30680) that is expected to occur temporarily during specific corrective maintenance procedures, such as replacing a Control Unit or the entire inverter. It does not indicate a persistent problem if the full replacement and recommissioning steps are followed. The risk is negligible if acknowledged as part of the procedure.

An error occurred during the forced checking procedure (test stop) for the fail-safe digital output, indicating a potential wiring issue or malfunction of the output itself. This means the safety test failed, and the fail-safe output cannot be trusted.

An unhandled internal software error has occurred within the power unit. The fault value (r0949) is intended for internal Siemens troubleshooting only. This indicates a critical software malfunction that prevents proper operation. The primary risk is complete drive failure and inability to operate the equipment.

This fault signifies a communication error on the I2C bus, typically with an EEPROM or an A/D converter within the power unit. The fault value (r0949) provides specific detail: 80000000 hex indicates an internal software error, while 00000001-0000FFFF hex points to a module fault. This can lead to incorrect readings, configuration issues, or unreliable operation. The risk is complete or partial failure of the affected module.

An internal software error has occurred within the power unit. The fault value (r0949) provides information about the fault source, intended for internal Siemens troubleshooting. This indicates a critical software malfunction within the power unit, preventing normal operation. The risk is complete drive failure and inability to operate the connected equipment.

This fault is triggered when the actual temperature (r4105[0]) for channel 0 on the Terminal Module 120 (TM120) or Terminal Module 150 (TM150) exceeds its configured fault threshold (p4102[1]), or if an associated timer (p4103[0]) expires. If a BICO interconnection exists, this fault will cause the drive to shut down. The fault will persist until the temperature falls below the threshold (minus hysteresis) and is acknowledged.

This fault is triggered when the actual temperature (r4105[1]) for channel 1 on the Terminal Module 120 (TM120) or Terminal Module 150 (TM150) exceeds its configured fault threshold (p4102[3]), or if an associated timer (p4103[1]) expires. If a BICO interconnection exists, this fault will cause the drive to shut down. The fault will persist until the temperature falls below the threshold (minus hysteresis) and is acknowledged.

This fault is triggered when the actual temperature (r4105[2]) for channel 2 on the Terminal Module 120 (TM120) or Terminal Module 150 (TM150) exceeds its configured fault threshold (p4102[5]), or if an associated timer (p4103[2]) expires. If a BICO interconnection exists, this fault will cause the drive to shut down. The fault will persist until the temperature falls below the threshold (minus hysteresis) and is acknowledged.

This fault is triggered when the actual temperature (r4105[3]) for channel 3 on the Terminal Module 120 (TM120) or Terminal Module 150 (TM150) exceeds its configured fault threshold (p4102[7]), or if an associated timer (p4103[3]) expires. If a BICO interconnection exists, this fault will cause the drive to shut down. The fault will persist until the temperature falls below the threshold (minus hysteresis) and is acknowledged.

This fault is triggered when the actual temperature (r4105[4]) for channel 4 on the Terminal Module 150 (TM150) exceeds its configured fault threshold (p4102[9]), or if an associated timer (p4103[4]) expires. If a BICO interconnection exists, this fault will cause the drive to shut down. The fault will persist until the temperature falls below the threshold (minus hysteresis) and is acknowledged.

This fault is triggered when the actual temperature (r4105[5]) for channel 5 on the Terminal Module 150 (TM150) exceeds its configured fault threshold (p4102[11]), or if an associated timer (p4103[5]) expires. If a BICO interconnection exists, this fault will cause the drive to shut down. The fault will persist until the temperature falls below the threshold (minus hysteresis) and is acknowledged.

This fault is triggered when the actual temperature (r4105[6]) for channel 6 on the Terminal Module 150 (TM150) exceeds its configured fault threshold (p4102[13]), or if an associated timer (p4103[6]) expires. If a BICO interconnection exists, this fault will cause the drive to shut down. The fault will persist until the temperature falls below the threshold (minus hysteresis) and is acknowledged.

This fault is triggered when the actual temperature (r4105[7]) for channel 7 on the Terminal Module 150 (TM150) exceeds its configured fault threshold (p4102[15]), or if an associated timer (p4103[7]) expires. If a BICO interconnection exists, this fault will cause the drive to shut down. The fault will persist until the temperature falls below the threshold (minus hysteresis) and is acknowledged.

This fault is triggered when the actual temperature (r4105[8]) for channel 8 on the Terminal Module 150 (TM150) exceeds its configured fault threshold (p4102[17]), or if an associated timer (p4103[8]) expires. If a BICO interconnection exists, this fault will cause the drive to shut down. The fault will persist until the temperature falls below the threshold (minus hysteresis) and is acknowledged.

This fault is triggered when the actual temperature (r4105[9]) for channel 9 on the Terminal Module 150 (TM150) exceeds its configured fault threshold (p4102[19]), or if an associated timer (p4103[9]) expires. If a BICO interconnection exists, this fault will cause the drive to shut down. The fault will persist until the temperature falls below the threshold (minus hysteresis) and is acknowledged.

This fault is triggered when the actual temperature (r4105[10]) for channel 10 on the Terminal Module 150 (TM150) exceeds its configured fault threshold (p4102[21]), or if an associated timer (p4103[10]) expires. If a BICO interconnection exists, this fault will cause the drive to shut down. The fault will persist until the temperature falls below the threshold (minus hysteresis) and is acknowledged.

This fault is triggered when the actual temperature (r4105[11]) for channel 11 on the Terminal Module 150 (TM150) exceeds its configured fault threshold (p4102[23]), or if an associated timer (p4103[11]) expires. If a BICO interconnection exists, this fault will cause the drive to shut down. The fault will persist until the temperature falls below the threshold (minus hysteresis) and is acknowledged.

A general fault has been detected at the drive object connected to the DRIVE-CLiQ socket X100. The fault value (r0949) provides information about the specific underlying fault that first occurred for this drive object. This fault requires immediate acknowledgment.

A general fault has been detected at the drive object connected to the DRIVE-CLiQ socket X101. The fault value (r0949) provides information about the specific underlying fault that first occurred for this drive object. This fault requires immediate acknowledgment.

A general fault has been detected at the drive object connected to the DRIVE-CLiQ socket X102. The fault value (r0949) provides information about the specific underlying fault that first occurred for this drive object. This fault requires immediate acknowledgment.

A general fault has been detected at the drive object connected to the DRIVE-CLiQ socket X103. The fault value (r0949) provides information about the specific underlying fault that first occurred for this drive object. This fault requires immediate acknowledgment.