Siemens DCM

An attempt to write data to the removable data medium (e.g., an SD card) has failed. This could indicate a faulty medium, improper insertion, or write protection. Unsuccessful data backups mean that critical parameters or logs are not being saved, risking data loss if the system experiences a fault or power cycle.

The system failed to write data to the internal RAM disk. This typically happens if the RAM disk is full or its size is not adequately configured for the data being written, such as the system logbook. Failure to write to the RAM disk can lead to incomplete logging of events or operational data, making troubleshooting difficult and potentially hiding critical issues.

The downloaded parameterization file is incompatible with the currently installed module type (e.g., different Order No. or MLFB). This means the configuration settings do not match the hardware, preventing correct operation. Operating with an incompatible configuration can lead to erratic behavior or inability to start.

An error occurred during evaluation of the temperature sensor, which is expected to be an Ni1000 or PT1000 connected via an analog input (AI2 or AI3). Possible causes include wire breakage, the sensor not being connected, or a short circuit leading to a measured resistance that is too low. This can result in inaccurate temperature monitoring and potential overheating if not addressed.

The alarm threshold for overtemperature at the AC inverter's heat sink has been reached. This indicates that the power unit is operating at an elevated temperature. If the temperature increases by an additional 5 K, it will trigger fault F30004, potentially leading to a drive shutdown and component damage.

The alarm threshold for overtemperature of the power semiconductor's depletion layer chip in the AC converter has been reached. This indicates that the internal semiconductor components are experiencing high temperatures. If the depletion layer temperature increases by an additional 15 K, it will trigger fault F30025, which can lead to damage or failure of the power semiconductors.

For chassis power units, the alarm threshold for the air intake overtemperature has been reached, typically set at 42 °C with a 2 K hysteresis for air-cooled units. This indicates that the incoming air for cooling is too hot. If the air intake temperature increases by an additional 13 K, it will output fault F30035, risking critical overheating of the power unit.

This alarm signifies that the internal temperature within a chassis power unit has reached its alarm threshold. If the temperature increases by an additional 5 K, it will escalate to fault F30036, leading to a shutdown. It's crucial to address this to prevent potential damage and ensure continued operation.

The rectifier in the power unit has reached its overtemperature alarm threshold. If the temperature rises by an additional 5 K, it will trigger fault F30037, potentially causing a drive shutdown. Causes can include high ambient temperature, excessive load, fan failure, or issues with the line supply. Ignoring this can lead to rectifier damage.

This alarm indicates that the thermal model for blocksize power units has detected an excessive temperature difference between the semiconductor chip and its heat sink. While it often resolves automatically, if the temperature continues to rise, it can lead to fault F30024. Sustained high temperature differences can reduce the lifespan of power unit components.

This alarm indicates that the three phases of the braking chopper resistors are not symmetrical, meaning there's an imbalance in their resistance values. This could be due to issues with the feeder cables or an incorrectly set monitoring threshold. Asymmetry can lead to uneven current distribution and reduced effectiveness of the braking chopper, potentially causing other faults.

The internal thermal I2t model, primarily for synchronous motors, has detected that the motor's calculated temperature has exceeded an alarm threshold. This indicates that the motor is operating close to its thermal limits due to sustained load or environmental conditions. If ignored, this can lead to an actual motor overtemperature fault and potential damage.

This alarm indicates an issue with the motor temperature sensor signal, such as a wire break (high resistance) or a short circuit (low resistance), preventing accurate temperature monitoring. If unresolved within the timer p0607, it will escalate to fault F07016. The drive cannot reliably monitor motor temperature, risking overheating if other protective measures are not in place.

The BICO signal for 'external alarm 1' was triggered, indicating that the predefined condition for this alarm has been met. This is a user-configurable alarm tied to an external event, sensor, or logic input. The specific cause is defined by parameter p2112.

The BICO signal for 'external alarm 2' was triggered, indicating that the predefined condition for this alarm has been met. This is a user-configurable alarm tied to an external event, sensor, or logic input. The specific cause is defined by parameter p2116.

The BICO signal for 'external alarm 3' was triggered, indicating that the predefined condition for this alarm has been met. This is a user-configurable alarm tied to an external event, sensor, or logic input. The specific cause is defined by parameter p2117.

The motor is currently being braked using DC current, which is a normal operational state. This alarm appears when a message with a 'DCBRK' response is active, injecting the braking current (p1232) for a duration (p1233) or until the standstill threshold (p1226) is undershot. It can also be activated manually via binector input p1230. This is an informational alarm and does not indicate a fault.

After the inverter pulses are enabled, the absolute current value remains critically small, indicating that no motor is connected or properly detected by the drive. For vector control with an induction motor, this alarm is typically followed by fault F07902. This issue prevents motor operation and can be due to wiring problems or incorrect low-current settings.

This alarm indicates that the internal temperature within the power unit has reached its alarm threshold. If the temperature continues to rise, it could lead to fault F30036. Common causes include high ambient temperature or insufficient cooling due to fan failure. Unresolved, it risks power unit damage or shutdown.

This alarm indicates that the cooling fan in the power unit has reached or exceeded its specified maximum operating hours (typically 500 hours), as configured in p0252. While the fan may still be operational, this serves as a preventative maintenance alert. Continuing to operate with an aged fan increases the risk of fan failure and subsequent overtemperature faults, potentially damaging the power unit.

The internal cooling fan within the power unit has failed. This is a critical alarm as the fan is essential for dissipating heat. Continued operation without a functional fan will rapidly lead to overtemperature faults and potentially irreversible damage to the power unit's electronics.

A Cyclic Redundancy Check (CRC) error has been detected in the actuator's data, indicating corruption during data transmission or storage. This can lead to unreliable control signals or unexpected behavior in the power unit, affecting motor control and system stability.

During the booting process, it was detected that the cause of the previous system reset was an SAC (System Access Controller) watchdog timer overflow. This means a critical software process failed to acknowledge the watchdog timer within its allotted time, leading to an unexpected system reset. Repeated occurrences can indicate software instability or resource contention.

An unspecified internal software error has occurred within the Control Unit. The fault value (r0949) is typically provided for internal Siemens troubleshooting. This indicates a problem with the drive's operating system or application software, which can lead to unpredictable behavior or system shutdown.

An exception, such as an invalid operation, division by zero, overflow, underflow, or imprecise result, occurred during a FloatingPoint data type operation. This error can originate from the base system or a specific application like FBLOCKS or DCC. The fault value (r0949) and r9999 provide detailed information about the cause and program counter at the time of the exception, indicating a critical calculation error.

The module's booting process has been repeatedly interrupted, potentially due to power loss, a CPU crash, or invalid user data. Upon this fault, the module will revert to factory settings. Persistent interruptions indicate an underlying hardware or configuration issue, risking loss of custom parameters and operational instability.

An internal software timeout has occurred within the drive's control unit, indicating that a software task did not complete within its expected timeframe. This can be caused by transient software issues, corrupted firmware, or underlying hardware problems. An internal software timeout can lead to unpredictable drive behavior or complete system stoppage.

The drive has lost its "sign-of-life" signal from an active PC master control within the configured monitoring time, indicating a communication interruption. Consequently, master control has reverted to the BICO interconnection. This fault stops PC-based control, potentially leading to an uncontrolled state or production halt.

This fault indicates that the measured DC link voltage is outside the expected tolerance range after the pre-charging process, based on the parameterized supply voltage (p0210). This could be due to incorrect parameter settings or an actual issue with the incoming line supply voltage. Operating with incorrect voltage parameters or an unstable supply can lead to drive malfunction or damage.

This fault indicates a detected phase failure in one of the braking resistors. Depending on the fault value (U, V, or W), a specific phase's feeder cable may be open or disconnected. This can impair the drive's ability to dissipate regenerative energy, potentially leading to overvoltage faults or control issues.

The motor has exceeded its programmed temperature fault threshold, or the I2t thermal model indicates overtemperature. This can be caused by motor overload, high ambient temperature, or issues with the temperature sensor itself (wire breakage, incorrect connection). Prolonged overtemperature risks permanent motor damage.

An error was detected during the evaluation of the motor temperature sensor (configured in p0601). Possible causes include a wire breakage (KTY: R > 2120 Ohm), the sensor not being connected, or a measured resistance that is too low due to a short circuit (PTC: R < 20 Ohm, KTY: R < 50 Ohm). If alarm A07015 was present, this fault was output after the timer p0607 expired, indicating a prolonged issue.

One or more closed-loop control parameters have been parameterized incorrectly, such as setting p0356 (L_spread) to 0. The fault value (r0949) indicates the specific parameter number involved, which can vary for vector drives or synchronous motors. Incorrect parameters can lead to unstable operation, poor performance, or drive malfunction.

For PM250 and PM260 blocksize power units, the regenerative rated power (r0206[2]) was continuously exceeded for more than 10 seconds. This indicates that the drive is generating excessive energy back into the DC bus or supply, which can lead to overvoltage and potential damage if the regeneration capability is insufficient.

A phase-to-phase short-circuit has been detected at the motor-side output terminals of the converter. This is a critical fault that can severely damage the power unit if not resolved. It can also be triggered if the line (input) and motor (output) cables are accidentally interchanged, creating a short circuit condition.

No rated data is stored in the power unit's EEPROM, which is essential for the drive to operate correctly. This can indicate a faulty EEPROM, an uninitialized power unit, or a replacement unit that has not been properly configured. Without this data, the drive cannot determine its nominal operating characteristics.

An external monitoring device or system has triggered the "external fault 1" input signal to the drive. This indicates a critical condition detected by equipment outside of the drive's internal monitoring, requiring investigation of the connected external safety chain or process. Ignoring this fault can lead to equipment damage or unsafe operating conditions.

An external monitoring device or system has triggered the "external fault 2" input signal to the drive. This indicates a critical condition detected by equipment outside of the drive's internal monitoring, requiring investigation of the connected external safety chain or process. Ignoring this fault can lead to equipment damage or unsafe operating conditions.

An external monitoring device or system has triggered the "external fault 3" input signal to the drive. This indicates a critical condition detected by equipment outside of the drive's internal monitoring, requiring investigation of the connected external safety chain or process. Ignoring this fault can lead to equipment damage or unsafe operating conditions.

The motor has been operating at its torque limit for an extended period while remaining below a defined speed threshold, indicating a mechanical blockage or severe overload. This could also be caused by speed oscillations at the controller limit or thermal derating of the power unit. Continued operation in this state can lead to motor overheating, mechanical damage, or damage to the drive.

The motor's actual speed has exceeded its configured maximum permissible limit, either in the positive or negative direction. This indicates a potential loss of speed control, incorrect parameterization, or an external force driving the motor. Exceeding the motor's rated speed can lead to mechanical failure, rotor damage, or safety hazards.

This fault indicates a deviation between expected and actual motor performance. If p2193=1, the torque deviates from the defined torque/speed envelope characteristic. If p2193=2, the speed signal from an external encoder (p3230) deviates from the internal speed (r2169). This suggests a mechanical issue, an incorrect encoder setup, or improper drive parameterization.

The load monitoring function has detected a significant failure in the mechanical load connected to the drive. This indicates a deviation from expected load conditions, potentially caused by a broken belt, coupling, or other mechanical issue in the driven machinery. If unaddressed, this can lead to production downtime or further mechanical damage.

The motor parameters were incorrectly entered during commissioning, such as setting p0300 (Motor type) to 0, indicating no motor. The fault value (r0949) specifies the particular parameter number involved. Incorrect motor parameters can lead to inefficient operation, instability, motor damage, or the drive failing to start.

The power unit's hardware current limit has been triggered repeatedly in one or more phases, indicating persistent overcurrent conditions. This can be due to incorrect control parameters, faults in the motor or power cables (short-circuit/ground fault), excessive cable length, or an overloaded motor. Frequent hardware current limiting can degrade power unit components and lead to premature failure.

The power unit has detected a ground fault in the output circuit. This can originate from insulation breakdown in the power cables or motor windings, a defective current transformer (CT), or even a specific issue related to the brake application. An unresolved ground fault poses a severe risk of electric shock, equipment damage, and fire.

The monitoring of the collector-emitter voltage (U_ce) in the power unit's semiconductors has detected an abnormal condition. This often indicates a short circuit at the power unit output, a defective IGBT, a problem with the IGBT gating module's power supply (24V), or an interrupted fiber-optic cable. This is a critical fault that can lead to immediate and severe damage to the power unit's IGBTs if not addressed.

The temperature at the power unit's air intake has surpassed its permissible limit, typically 55°C for air-cooled units. This is often caused by high ambient temperatures or a malfunctioning cooling fan. Continued operation above this limit can lead to hardware damage and system shutdown.

The internal temperature of the drive converter, specifically in the control or power electronics, has exceeded its safe operating limit. This can be caused by inadequate cooling (fan failure), motor overload, or excessive ambient temperatures. Continued operation risks severe damage to the power unit.

The rectifier component within the power unit has overheated beyond its permissible temperature limit. Potential causes include insufficient cooling (fan failure), excessive motor load, high ambient temperatures, or a failure in one of the line supply phases. Prolonged overtemperature can lead to rectifier failure and drive malfunction.

An error has occurred with the EEPROM data in the power unit module, either due to inconsistent data or incompatibility with the Control Unit (CU) firmware. This indicates a critical issue with the module's stored configuration or its ability to communicate properly with the CU. The power unit module cannot function correctly, and risks system instability or non-operation.

An excessive current has been detected flowing through the braking chopper circuit. This is typically caused by a short circuit within the braking resistor itself or if the external braking resistor is undersized for the application's regenerative energy requirements. An overcurrent condition can quickly damage the braking chopper or connected components.

The internal cooling fan of the power unit has failed, indicating it is likely defective. This is a critical condition as the fan is responsible for preventing the power unit from overheating. Continued operation will quickly lead to severe overtemperature faults and potential, irreversible damage to the power unit's electronic components.

The Control Unit has failed to receive multiple actual value telegrams from the Power Module, indicating a communication breakdown. This means the drive is not receiving critical feedback data necessary for operation. This loss of communication will halt drive operation and can lead to unstable control or system shutdown.

The Control Unit has failed to transmit multiple setpoint telegrams to the Power Module, indicating a communication failure. This means the drive is unable to receive commands to control its operation. This loss of communication will prevent the drive from functioning as commanded and can lead to system shutdown.

An error has occurred during the power unit's booting process, preventing it from starting up correctly. The fault value (r0949) is provided for internal Siemens troubleshooting. This issue can cause the drive to remain offline or fail to respond to commands.

A time slice overflow has occurred within the power unit, indicating that a critical internal process exceeded its allocated computational time. This can lead to system instability, incorrect operation, or a complete shutdown. The fault requires immediate attention to prevent further operational issues.

Internal parameter data stored in the power unit's EEPROM is corrupted, as evidenced by a checksum error. This means critical configuration or operational parameters are invalid, leading to system malfunction. The fault value may indicate an EEPROM access error or too many blocks within the EEPROM.

For 3P gating units, the end ID for the last switching status word in the setpoint telegram was not found. This signifies a communication or data integrity issue with the switching information, which is critical for the correct operation of the gating unit. This can lead to incorrect or no switching action of the power semiconductors.

The power unit has detected at least one underlying fault, triggering this general group signal. This code serves as an indication that a more specific fault or alarm message should also be present, which contains the actual details of the problem. Ignoring this group signal means overlooking the specific fault that initiated it.