Siemens DAsl Diagnostics

The sum of active offsets for geometry axes or rotary axes does not equal zero. This indicates an inconsistency in the programmed offsets, potentially affecting translatory or rotary components, leading to incorrect tool positioning or axis movements. The specific error type (A, B, C, D, E) is indicated by the %4 parameter.

The workpiece probe or its tool edge data is either inactive or contains incorrect values, specifically if the length L1 is zero. This issue prevents the system from accurately using the probe for measurement or calibration, potentially causing measurement errors or collisions. The error code A indicates an inactive probe/tool edge, while B indicates L1 is zero.

The system encountered an error when attempting to create a log file. This can be caused by an excessive number of log files in the current directory (more than 99, Error code A) or by existing log files being too large (Error code B). This prevents the system from recording operational data or events, hindering diagnostics and traceability.

A rotary measuring axis (either axis 1 or 2) is not in its required basic or intended position during a measurement operation. This can occur on the first measurement (Error A or B) or during subsequent measurements when comparing positions (Error C or D). This will lead to inaccurate measurements or prevent the measurement cycle from proceeding correctly.

The Sensor Module's existing software and/or hardware is not compatible with the higher-level control's safe motion monitoring function. This prevents the safe motion monitoring features from functioning correctly, potentially impacting safety-critical operations. Note that this specific fault does not immediately result in a safety stop response.

The checksum calculated by the drive for safety-relevant parameters (r9728) does not match the reference checksum (p9729) saved during the last machine acceptance. This indicates that safety-relevant parameters have been altered or an internal fault is present, compromising the integrity of the safety monitoring functions. This fault results in a STOP A that can be acknowledged.

The asymmetry of line currents in the infeed is too high, most likely due to a failure in one of the line phases. This imbalance can lead to improper operation of the infeed unit and potentially damage components if not resolved. It indicates an issue with the quality or integrity of the incoming power supply.

The smoothed total of the phase currents (i1 + i2 + i3) exceeds 4% of the maximum power unit current (r0209). This severe condition often indicates a DC link ground fault, which can introduce a DC component into the line currents, potentially damaging or destroying the power unit, line reactor, or line filter. Other causes include uncalibrated current measurement or a defective current measurement in the power unit.

The system is attempting to use a configuration that the power unit does not support. This can be caused by requesting autonomous operation on an unsupported unit, incompatible DRIVE-CLiQ timing, an older PM260 PS-ASIC version, failed initialization due to premature Control Unit withdrawal, or an unsupported combination of power unit and Control Unit/Adapter. The fault value in r0949 provides specific details on the cause.

The EnDat encoder's internal fault word has set fault bits, indicating a problem with the encoder's internal operation. This could relate to the lighting system, signal amplitude, position value accuracy, or issues with the encoder's power supply (over/undervoltage, overcurrent). The exact fault is detailed in r0949, where each bit represents a specific cause, ranging from a failed lighting system to encoder power supply issues.

The heat sink temperature of the HF damping module has exceeded its permissible limit. This is typically caused by insufficient cooling (e.g., fan failure), sustained overload conditions on the module, or an ambient temperature that is too high. Sustained overtemperature can lead to premature component failure or reduced performance of the damping module.

The temperature of the HF reactor module has exceeded its permissible operating limit. Common causes include inadequate cooling (fan failure), system overload causing excessive heat generation, or an elevated ambient temperature in the installation environment. Prolonged overtemperature can degrade the reactor module's performance and significantly shorten its lifespan.

The heat sink temperature of the HF reactor module has surpassed its maximum permissible limit. This condition is often due to insufficient cooling (e.g., fan malfunction), an overloaded system causing the module to generate excess heat, or an ambient temperature that is too high for safe operation. Persistent high temperatures can lead to damage and failure of the reactor module.

The reactor module has detected an overtemperature condition or a failure in its cooling fan. This alarm serves as a warning for a potential thermal issue. If this alarm persists for longer than 30 seconds, it will escalate to fault F37313 (likely 237313), indicating a more critical and sustained thermal problem that requires immediate attention.

This fault is triggered when alarm A37312 (237312), indicating an overtemperature or fan failure in the reactor module, has been active for more than 30 seconds. This signifies a persistent and critical cooling problem that could lead to severe damage or shutdown of the reactor module if not addressed. Reaction is OFF2, requiring an immediate power on acknowledge.

The damping voltage within the HF damping module has exceeded its alarm threshold. This can be caused by a motor harmonic with high amplitude coinciding with the output filter's resonance frequency, or by the current controller excessively exciting the output filter's resonance. If the damping voltage continues to rise to an unacceptably high level, it will trigger fault F37002 (likely 237002).

The HF damping module has detected at least one fault within its system. This code serves as a general indicator that a problem exists within the damping module and requires further investigation. It is a consolidated alarm, implying that more specific, underlying faults are present.

The filtered (steady-state) value of the line supply voltage at the infeed unit has dropped below the configured alarm threshold (p0282 multiplied by p0210). This indicates a potential issue with the incoming power supply, which could lead to operational instability or trigger more severe faults if not resolved promptly.

An error was detected during the evaluation of the motor temperature sensor (configured via p0600 and p0601). This alarm indicates potential issues such as wire breakage, a disconnected sensor (KTY resistance > 1630 Ohm), or excessively low measured resistance (PTC < 20 Ohm, KTY < 50 Ohm). If this alarm persists for the duration set in p0607, it will escalate to fault F07016, potentially leading to motor damage.

An alarm has been detected at the drive object connected to the DRIVE-CLiQ socket X100. The alarm value (r2124) indicates the first alarm that occurred for this specific drive object. This signals a potential issue with the communication or connected component on this DRIVE-CLiQ interface that requires attention to prevent escalation to a fault or performance degradation.

The drive-integrated 'Safety Integrated' (SI) function on the Control Unit (CU) has detected an error in the sign-of-life of safety data between the CU and a Motor Module (MM), or a time slice overflow of the safety software occurred. This indicates a critical communication error that initiates a STOP A, posing a safety risk and halting operation until resolved.

The drive-integrated 'Safety Integrated' function on the Control Unit (CU) has detected an error in the brake control, initiating a STOP A. Causes include incorrect parameter p1278, wire breakage, no brake connected, a ground fault in the brake cable, or a short-circuit in the brake winding. This fault prevents safe operation and indicates a critical issue with the holding brake system that must be resolved.

A safety test stop fault has occurred on the Control Unit (CU) side, specifically indicating that the expected states of the Digital Outputs (DOs) were not fulfilled during a safety test. This means the external readback signal was not set correctly for a given test stop state (e.g., state 7), where an expected value was not observed. This issue compromises the validation of safety functions.

One or more line supply phases have failed, or an overvoltage condition has occurred. This fault can manifest during power-on due to incorrect phase assignment between a VSM and the power unit, or during operation due to a voltage dip, prolonged overvoltage, severe overload, or a missing line reactor. This immediate OFF2 reaction halts operation and indicates a serious power supply instability or hardware misconfiguration that requires immediate attention to prevent damage.

A critical error was detected during the evaluation of the motor temperature sensor (configured via p0600 and p0601). This fault signifies severe problems like wire breakage, a disconnected sensor (KTY resistance > 1630 Ohm), or measured resistance that is too low (PTC < 20 Ohm, KTY < 50 Ohm). This fault often occurs after alarm A07015 has been active for the time specified in p0607, posing a direct risk of motor overheating and damage if left unaddressed.

A safety test stop fault has occurred on the Motor Module (MM) side. This fault indicates that while the MM's internal states may be as expected, the required state was not present on the readback input of the other channel (Control Unit). This suggests an inconsistency in the safety test routine between the CU and MM, affecting the overall safety integrity and requiring investigation.

The EnDat absolute encoder has detected an internal fault, indicated by set bits in its fault word (r0949). This can include failures such as the lighting system, low signal amplitude, incorrect position values, or issues with the 5V encoder power supply (overvoltage, undervoltage, overcurrent). If the encoder has battery backup, a low battery condition can also trigger this fault. This critical error affects position feedback accuracy and can lead to unreliable drive operation.

A fault has been detected at the drive object connected to the DRIVE-CLiQ socket X102. The fault value (r0949) indicates the first fault that occurred for this specific drive object. This signifies an issue with the communication or the connected component on this particular DRIVE-CLiQ interface, which can lead to system malfunction or halt operations.

A fault has been detected at the drive object connected to the DRIVE-CLiQ socket X103. The fault value (r0949) indicates the first fault that occurred for this specific drive object. This signifies an issue with the communication or the connected component on this particular DRIVE-CLiQ interface, which can lead to system malfunction or halt operations.

A fault has been detected at the drive object connected to the DRIVE-CLiQ socket X104. The fault value (r0949) indicates the first fault that occurred for this specific drive object. This signifies an issue with the communication or the connected component on this particular DRIVE-CLiQ interface, which can lead to system malfunction or halt operations.

A fault has been detected at the drive object connected to the DRIVE-CLiQ socket X105. The fault value (r0949) indicates the first fault that occurred for this specific drive object. This signifies an issue with the communication or the connected component on this particular DRIVE-CLiQ interface, which can lead to system malfunction or halt operations.