Siemens FC176

An error occurred during a gear stage change operation for a spindle, with the specific cause detailed by an error code. This fault disables NC Start for the affected channel and sets interface signals. Potential sub-causes include issues with switching to command/PLC axis or specific MD parameter settings.

This alarm indicates that the sum of active offsets in geometry axes, fine offsets, or rotary components does not equal zero, leading to an inconsistency in the machine's positional calculations. Specific error codes (A-E) identify the type of offset problem (translatory, fine, or rotary for different axes). If not resolved, this can lead to incorrect machine movements, inaccurate positioning, and potentially damage to the workpiece or machine.

This alarm signals that the data for the currently active workpiece probe is either incorrect or the probe itself is inactive. Error code 'A' indicates an inactive workpiece probe or tool edge, while 'B' signifies that the probe's length L1 is zero. This issue prevents accurate workpiece measurement and can lead to machining errors if not corrected, impacting precision and quality.

This alarm indicates a problem with the system's ability to create log files. Error code 'A' points to too many log files (over 99) in the current directory, while 'B' suggests that existing log files are excessively long. Failure to resolve this can prevent important diagnostic data from being recorded, hindering effective troubleshooting and system monitoring.

This alarm indicates that a rotary measuring axis is not in its expected basic or intended position during measurement operations. Error codes 'A' and 'B' relate to rotary axis 1 and 2 not being in basic position on the first measurement. Error codes 'C' and 'D' indicate that rotary axis 1 or 2 are not in their intended positions during subsequent measurements. This can cause inaccurate measurements, leading to incorrect machining outcomes and potential scrap parts.

The drive's Safety Integrated (SI) function on the Control Unit (CU) has detected a brake control fault, leading to a STOP A reaction. Causes vary widely depending on the fault value, encompassing issues such as incorrect parameter p1278, missing or broken brake connections, ground faults in the brake cable, short-circuits in the brake winding, or internal faults within the CU's brake control circuit or its communication with the Motor Module.

The Sensor Module's existing software and/or hardware is not compatible with the higher-level control's safe motion monitoring function. This could be due to outdated firmware or an unsuitable hardware version that does not support the required safety features. While this fault does not immediately trigger a safety stop, it prevents the safe motion monitoring features from functioning correctly, potentially compromising machine safety if not upgraded.

This fault indicates a discrepancy between the drive's calculated checksum for safety-relevant parameters (r9728) and the reference checksum saved during the last machine acceptance (p9729). This means that safety-relevant parameters have either been changed inadvertently, or a fault exists in the system impacting their integrity. This fault results in a STOP A, requiring immediate attention to maintain safety integrity and prevent unsafe machine operation.

This fault occurs when the smoothed total of the phase currents (i1 + i2 + i3) exceeds 4% of the maximum power unit current (r0209). Primary causes include a ground fault in the DC link leading to high summation current, unperformed zero point calibration of current measurement, or a defective current measurement in the power unit. A high DC component in line currents can severely damage the power unit, line reactor, or line filter if left unaddressed, posing a risk of component failure.

An error was detected during the evaluation of the motor temperature sensor (configured via p0600 and p0601). This alarm triggers a timer (p0607), after which if the condition persists, a critical fault (F07016) is output. Common causes include wire breakage, disconnected sensor, or the measured resistance being outside acceptable ranges (e.g., KTY: R > 1630 Ohm or R < 50 Ohm, PTC: R < 20 Ohm).

A critical error was detected during the evaluation of the motor temperature sensor (configured via p0600 and p0601). This fault is typically issued if Alarm A07015 persists beyond the configured time in p0607, indicating a sustained issue such as wire breakage, disconnected sensor, or out-of-range resistance values (e.g., KTY: R > 1630 Ohm or R < 50 Ohm, PTC: R < 20 Ohm).

This fault signifies that the requested configuration for the power unit is not supported by its hardware or firmware. Possible causes include requesting unsupported autonomous operation, an impermissible DRIVE-CLiQ timing, detection of an incompatible PM260 PS-ASIC version, or an incompatible combination of power unit and Control Unit/Adapter. Initialization failure due to premature Control Unit withdrawal can also trigger this. Operating with an unsupported configuration can lead to system instability, malfunction, or prevent the drive from starting altogether.

An internal fault has been detected within Absolute Encoder 1 (EnDat), as indicated by set bits in its fault word. This can signify issues such as a failed lighting system, low signal amplitude, incorrect position values, or problems with the encoder's 5V power supply (overvoltage, undervoltage, overcurrent). If applicable, it could also mean the encoder battery needs replacement.

The EnDat encoder fault word supplies various fault bits indicating internal issues. These can range from a failed lighting system, low signal amplitude, incorrect position values, or power supply irregularities (over/undervoltage, overcurrent) affecting the encoder. Additionally, serial communication errors like incorrect quiescent levels, a non-responsive encoder, CRC errors, or acknowledgment errors can occur. If these encoder or communication issues persist, they can lead to inaccurate position feedback, impacting drive control and potentially causing operational halts or unexpected machine behavior.

An internal fault has been detected within Absolute Encoder 3 (EnDat), as indicated by set bits in its fault word. This can signify issues such as a failed lighting system, low signal amplitude, incorrect position values, or problems with the encoder's 5V power supply (overvoltage, undervoltage, overcurrent). If applicable, it could also mean the encoder battery needs replacement.

This alarm indicates that the heat sink temperature of the HF damping module has exceeded its permissible limit. Common causes include insufficient cooling due to fan failure or blockage, excessive module overload, or an excessively high ambient temperature in the enclosure. While initially an alarm, prolonged overtemperature can lead to component degradation, reduced lifespan, and eventual failure of the damping module, impacting drive performance and potentially leading to a system shutdown.

This alarm signals that the temperature of the HF reactor module has surpassed its safe operating limit. Causes typically include inadequate cooling due to a malfunctioning fan or blocked airflow, an overload condition on the module, or an elevated ambient temperature in the operating environment. Persistent overtemperature can compromise the integrity of the reactor module, leading to premature component wear or failure, and potentially affecting the overall drive system's stability and performance.

This fault indicates that the heat sink temperature of the HF reactor module has exceeded the permissible limit, triggering an OFF2 reaction and stopping the drive. Causes include insufficient cooling (e.g., fan failure), module overload, or an ambient temperature that is too high, leading to a critical thermal condition. This fault requires immediate attention as sustained overtemperature can lead to irreversible damage to the reactor module and impact the drive's operational integrity and safety.

This alarm indicates that the reactor module has detected an overtemperature condition or a fan failure. The immediate causes can include a disconnected or defective connector between the reactor and damping module, a malfunctioning reactor module fan, or an excessively high ambient temperature. If this alarm persists for longer than 30 seconds, it will escalate to fault F37313, indicating a more critical condition. Continued operation under these conditions risks permanent damage to the module.

This fault is triggered when alarm A37312 (overtemperature or fan failure in the reactor module) persists for more than 30 seconds, leading to an OFF2 reaction and stopping the drive. The underlying issues are typically a disconnected/defective connector between the reactor and damping module, a faulty reactor module fan, or an ambient temperature that exceeds safe limits. This fault indicates a critical condition requiring immediate attention to prevent severe damage to the HF reactor module and ensure system safety.

This alarm indicates that the damping voltage in the HF damping module has exceeded its alarm threshold. This can happen if a motor harmonic with high amplitude coincides with the resonance frequency of the output filter or if the current controller excessively excites the output filter's resonance. If the damping voltage continues to rise to an unacceptably high level, it will escalate to fault F37002. High damping voltage can lead to component stress, reduced lifespan, and potential failure of the damping module or related components.

This is a general group alarm indicating that the HF damping module has detected at least one internal fault. It serves as a consolidated signal rather than a specific fault message, meaning the exact nature of the problem is not specified by this code alone. Further investigation of other individual alarms or fault messages related to the HF damping module is required to pinpoint the exact issue. Without addressing the underlying fault, the module's functionality may be compromised, potentially leading to drive performance issues or failures.

A fault has been detected at the drive object connected to DRIVE-CLiQ socket X103. The fault value (r0949) will indicate the first specific fault that occurred for this connected drive object. This generic fault requires further investigation of the device attached to X103.

A fault has been detected at the drive object connected to DRIVE-CLiQ socket X104. The fault value (r0949) will indicate the first specific fault that occurred for this connected drive object. This generic fault requires further investigation of the device attached to X104.

A fault has been detected at the drive object connected to DRIVE-CLiQ socket X105. The fault value (r0949) will indicate the first specific fault that occurred for this connected drive object. This generic fault requires further investigation of the device attached to X105.

An alarm has been detected at the drive object connected to DRIVE-CLiQ socket X100. The alarm value (r2124) will indicate the first specific alarm that occurred for this connected drive object. This generic alarm indicates a warning condition that warrants further investigation of the device attached to X100.

A fault has occurred during the test stop procedure on the Control Unit (CU) side, specifically related to the evaluation of states for Fail-safe Digital Outputs (F-DOs). This indicates that the expected states of the DOs or diagnostic DOs were not fulfilled, or an internal timer/state issue occurred, often a mismatch between expected and read-back signals during a test state.

A fault has occurred during the test stop procedure on the Motor Module (MM) side, specifically related to the evaluation of states for Fail-safe Digital Outputs (F-DOs). This indicates that the expected states of the DOs or diagnostic DOs were not fulfilled, or an internal timer/state issue occurred, often a mismatch between expected and read-back signals during a test state.