Siemens SINUMERIK 828D

The function requested by the PLC via the DBB30 interface could not be executed due to a specific underlying error. This fault disables NC Start in the affected channel and sets interface signals. The exact cause is specified by the error code parameter (%3).

An error occurred during the spindle's gear stage change operation. The specific cause is indicated by an error code (%3). This fault disables NC Start in the channel and sets interface signals, requiring attention to resolve the conflict.

This alarm indicates that a function request made by the PLC via the FC18 interface could not be executed. The alarm message includes a specific error code (e.g., 5 for switchover not possible, 23 for MD 30132 IS_VIRTUAL_AX set) that specifies the exact reason for the failure. This prevents NC Start in the affected channel, leading to production halts and potential process inconsistencies if the function is critical.

This alarm indicates that the cyclic transfer of the PUTFTOCF data block (fine tool compensation) failed because the transfer area is already occupied. This commonly occurs if another channel is simultaneously attempting to transfer a data block, creating a resource conflict. If left unaddressed, this prevents fine tool compensation from being applied, potentially leading to inaccuracies in machining and affecting product quality.

This alarm is triggered when a PRESET command (to set an axis position) is sent from the HMI or PLC while the specified axis is actively moving in JOG mode. Attempting to preset an axis while it's in motion can lead to incorrect position references or unexpected axis behavior. This prevents the PRESET operation, requiring the axis to be stationary for successful execution and avoiding potential positioning errors.

The sum of active offsets in the current block for geometry axes or rotary axes does not equal zero. This indicates a conflict in coordinate system transformations, which can lead to incorrect machine movements. The error code (%4) specifies the exact type of offset and axis affected.

The tool data for the active workpiece probe is either incorrect or the probe itself is inactive. This prevents accurate measurement operations. The error code (%4) indicates if the workpiece probe (or tool edge) is inactive, or if the length L1 of the workpiece probe is set to zero.

An error occurred while the system was attempting to create a log file. The error code (%4) specifies the cause: either the number of log files in the current directory exceeds 99, or the existing log files are too long. This issue prevents further logging until resolved.

A measuring axis (rotary axis 1 or 2) is not in its basic or intended position, particularly during the first measurement operation. The error code A specifically indicates that rotary axis 1 is not in its basic position. This fault prevents accurate measurements from being performed.

This alarm occurs when an attempt is made to change the number of Command Data Sets (CDS) or copy from a CDS while the master control is still active. Parameters related to BICO (Bi-directional interconnection) configurations cannot be altered under these conditions to maintain system integrity. This is a functional restriction rather than a critical fault, typically requiring no immediate action as the system prevents an invalid operation.

This alarm indicates that the configured service or maintenance interval for the motor has been reached, based on operating hours (p0650) against the set interval (p0651). While not an immediate operational fault, ignoring this alarm can lead to neglecting scheduled maintenance, increasing the risk of premature component wear, reduced performance, and eventual motor failure due to lack of upkeep.

This fault indicates that the drive-based Safety Integrated (SI) function in the Control Unit (CU) has detected an anomaly and initiated a STOP A, which involves pulse suppression via the safety shutdown path. This can be due to an unsuccessful forced checking procedure of the safety path, or a subsequent response to a monitoring channel defect (F01611). The fault value provides more detail, such as stop requests, pulse suppression issues, or feedback discrepancies. This safety-critical fault immediately inhibits motor operation to prevent hazardous situations.

The infeed unit has shut down because the filtered, steady-state value of the line supply voltage has dropped below the fault threshold defined by p0283. The fault value (r0949) indicates the current line supply voltage. This condition triggers an OFF2 (or OFF1) reaction, stopping the drive.

An alarm indicating that the filtered, steady-state value of the line supply voltage has dropped below the alarm threshold set by p0282. This is a warning condition, not a shutdown, meaning there is no immediate reaction. The alarm value (r2124) shows the current line supply voltage.

One or several line phases have failed, or an overvoltage condition has persisted, causing the infeed to fault. This can occur during power-on if the PLL cannot synchronize due to incorrect phase assignment (e.g., with a VSM) or during operation after a significant voltage dip or overvoltage. Alarm A06205 usually precedes this fault, providing additional diagnostic information.

This alarm indicates a voltage dip or overvoltage in one or more line supply phases during operation, causing pulses to be inhibited for at least 8 ms. The operating signal of the infeed unit remains active, but pulse inhibition is displayed. The specific cause (e.g., line angle deviation, active current deviation, line overvoltage/undervoltage, peak current trip, or line asymmetry) is detailed by the alarm value in r2124. If unresolved, this can lead to unstable drive operation and potential damage to components due to irregular power supply.

This fault indicates excessively high asymmetry in the line phase currents, with the most probable cause being the failure of one or more line phases. This condition leads to imbalanced loading of the infeed unit. If left unaddressed, this can result in overheating of components, reduced efficiency, and potentially premature failure of the infeed unit or connected equipment due to prolonged electrical stress.

The closed-loop control parameters of the drive have been incorrectly parameterized, for example, parameter p0356 (L_spread) is set to 0. The fault value (r0949) includes the specific parameter number that is involved. This fault does not cause an immediate reaction but requires a POWER ON acknowledgement after correction.

A macro program could not be executed due to various underlying causes. The fault value (r0949, hexadecimal) provides detailed information, including the preliminary parameter number, supplementary information, and the specific fault cause. This can range from invalid files, incorrect data types, or unauthorized parameter writes, preventing the macro from completing its intended function.

This fault indicates that the power unit has detected an overvoltage condition in the DC link, leading to a pulse inhibit. Common causes include a device supply voltage that is too high or an incorrectly dimensioned line reactor, as indicated by the fault value in r0949. Persistent DC link overvoltage can damage power electronic components, reduce drive lifespan, and lead to complete drive failure if not corrected.

This fault signifies that the drive-based Safety Integrated (SI) function in the Motor Module (MM) has detected a critical anomaly, initiating a STOP A (pulse suppression via the safety shutdown path of the Motor Module). This can result from an unsuccessful forced checking procedure of the safety path, an internal software error (fault value 1020), or a response to a monitoring channel defect (F30611). This safety-critical fault immediately halts motor operation to prevent hazardous conditions, requiring immediate attention to restore safe functionality.

A write request for one or more Safety Integrated (SI) parameters on the Motor Module (MM) was rejected. This typically occurs because an attempt was made to enable a safety function (like STO, SBC, SS1, motion monitoring, or PROFIsafe) that the specific Motor Module does not support, or there is a version mismatch in PROFIsafe drivers. This fault does not trigger a safety stop.

The existing Control Unit software does not support the safe drive-based motion monitoring function, leading to a STOP A that cannot be acknowledged. The fault value (r0949) is typically for internal Siemens troubleshooting. This indicates a fundamental incompatibility between the CU's software version and the attempted safety function.

The EnDat absolute encoder (Encoder 2) has reported an internal fault via its fault word. The fault value (r0949, binary) indicates the specific issue, such as lighting system failure, low signal amplitude, incorrect position value, encoder power supply problems (overvoltage, undervoltage, overcurrent), or a low battery condition. This prevents reliable position feedback.

The encoder (Encoder 2) has transmitted a set error bit via its serial protocol, specifically in the position protocol. This indicates a communication or data integrity issue from the encoder, potentially leading to incorrect position feedback. For EnDat encoders, a related F31111 fault may provide further diagnostic details.

This error signifies a transfer fault within the serial communication protocol between Encoder 3 and its evaluation module. The specific cause can range from incorrect quiescent levels, encoder unresponsiveness, CRC errors, acknowledgment errors, internal driver errors, timeout, or issues with the data line or parameterization, as indicated by fault bits in r0949. Such communication errors will lead to loss of position feedback, rendering precise motor control impossible and potentially causing uncontrolled movement or system shutdowns if not resolved.

This fault indicates that the EnDat encoder's internal fault word has set specific fault bits, signaling various internal issues such as lighting system failure, low signal amplitude, incorrect position values, or problems with the encoder's 5V power supply (overvoltage, undervoltage, or overcurrent). Additionally, it can indicate a need for battery replacement in battery-backed encoders. An unresolved internal encoder fault will lead to unreliable position feedback, preventing accurate motor control, causing potential uncontrolled movements, and ultimately stopping machine operation.

This fault signifies that Encoder 3 has sent a set error bit via its serial protocol, specifically a fault bit in the position protocol (Bit 0). This indicates a generic internal or communication-related error within the encoder system, which could mask a more specific underlying issue. Ignoring this fault can lead to unreliable position data, potentially causing incorrect axis positioning, loss of control, and system shutdowns.

This fault indicates that an issue has occurred at the drive object connected to DRIVE-CLiQ socket X100. The fault value (r0949) specifies the first fault that manifested for this particular drive object, providing a pointer to the specific problem. This general fault suggests a problem within the DRIVE-CLiQ communication or the connected component, potentially leading to loss of control or communication with the associated drive component if not addressed.

This fault indicates that an issue has occurred at the drive object connected to DRIVE-CLiQ socket X101. The fault value (r0949) specifies the first fault that manifested for this particular drive object, providing a pointer to the specific problem. This general fault suggests a problem within the DRIVE-CLiQ communication or the connected component, potentially leading to loss of control or communication with the associated drive component if not addressed.

This fault indicates that an issue has occurred at the drive object connected to DRIVE-CLiQ socket X102. The fault value (r0949) specifies the first fault that manifested for this particular drive object, providing a pointer to the specific problem. This general fault suggests a problem within the DRIVE-CLiQ communication or the connected component, potentially leading to loss of control or communication with the associated drive component if not addressed.

This alarm signals that a fault has been detected on a drive connected via PROFIBUS or PROFINET, and its fault memory contents have been reported. The alarm includes specific parameters: the drive identifier (%1), the fault code of the drive (%2), the fault value (%3), and the fault time (%4). This is a general indication of a drive-specific issue; the underlying fault must be diagnosed using the drive's own documentation to prevent process interruptions or damage to the drive.

This alarm indicates that a fault has occurred on an assigned PROFIBUS/PROFINET slave or device, and its fault memory contents have been reported. The alarm provides the bus number, slave/device number, DO ID (%1), the fault code (%2), fault value (%3), and fault time (%4) of the device. This signifies a device-level fault on the bus, which requires consulting the device's documentation to prevent communication failures and system downtime.

This alarm signals that the PROFIBUS/PROFINET bus configuration has changed, either due to initial commissioning or the recognition of a new slave/device on the bus. While not an error in itself, the new settings will only become active after a system restart. This requires a controlled restart to ensure the new configuration is properly loaded and the system operates as intended, avoiding potential communication inconsistencies.

This alarm indicates that a new SDB (System Data Block) with a modified configuration has been provided for the PROFIBUS/PROFINET bus. Similar to 380502, the new settings will only be activated upon the next bus power-up. This is an informational alarm requiring a system restart to apply the updated configuration, ensuring correct bus operation and avoiding potential communication errors.

The drive-based 'Safety Integrated' function in the Control Unit requires an acceptance test. This can be due to missing safety parameters for the Motor Module, checksum mismatches on the CU or MM, differing safety function enables, parameter changes, project downloads, hardware-related safety checksum changes, or subsequent safety-related faults during booting. This fault results in a STOP A that can be acknowledged.

A temperature sensor fault has been detected. This fault is output if alarm A07015 (temperature sensor fault) persists beyond the timer set in p0607, after at least 1 second. The fault value (r0949) indicates the number of the sensor channel that triggered the message.