ABB AC500

The configured PROFIsafe destination address (F_Dest_Add) for the safety PLC is invalid or incorrectly set. This prevents the safety PLC from establishing secure and correct communication with its intended safety partner, risking unmonitored or failed safety functions. The system's overall safety integrity is compromised if this address mismatch persists.

The configured PROFIsafe source address (F_Source_Add) for the safety PLC is invalid. This prevents the safety PLC from properly identifying itself to other safety devices in the network, leading to potential communication failures and a compromised safety chain. The risk is that other safety components might not correctly process data from this PLC.

The configured discrepancy time for redundant inputs has elapsed, meaning that the states of redundant channels did not synchronize within the expected timeframe. This indicates a fault in the sensors, wiring, or configuration, preventing valid safety signal evaluation.

The input signal measurement at the I/O module has exceeded its maximum measurable range (overflow). This indicates that the sensor input is providing a value higher than the module can process, potentially leading to incorrect or invalid safety-related readings.

The input signal measurement at the I/O module has fallen below its minimum measurable range (underflow). This indicates that the sensor input is providing a value lower than the module can process, potentially leading to incorrect or invalid safety-related readings.

This diagnostic code (represented by value 16#7FFF) indicates a severe internal error within a PLCopen Safety function block. This implies a malfunction in the block's internal logic or execution, preventing it from performing its intended safety function correctly and potentially leading to a safe state.

The measured process voltage at the I/O module has exceeded the permissible upper limit. This can indicate an overvoltage condition in the field wiring or power supply, potentially damaging connected sensors or actuators and leading to unsafe operating conditions.

The measured process voltage at the I/O module has fallen below the permissible lower limit. This suggests an undervoltage condition, which can cause connected sensors or actuators to operate unreliably or fail, compromising system safety.

An error was detected during the generation or detection of test pulses on an I/O channel. Test pulses are critical for diagnostics and ensuring the integrity of safety circuits, especially in detecting wiring faults. This fault indicates a potential wiring problem or sensor issue, compromising safety functionality.

This error indicates either a test pulse cross-talk between channels on Module 0 or a readback error on channels of Module 2. Cross-talk implies signals interfering between channels, while readback errors indicate faulty signal verification. Both compromise the isolation and integrity of safety signals, leading to unreliable operation and potential unsafe states.

The PROFIsafe F-Host library, responsible for managing safety communication, is unable to verify the safety source addresses of connected devices. This typically indicates an outdated or incompatible F-Host library version, which compromises the system's ability to validate the authenticity and integrity of safety messages. Consequently, safety communication cannot be reliably established.

A Cyclic Redundancy Check (CRC1) fault has been detected in PROFIsafe communication, indicating data corruption during transmission between safety components. This means safety messages are not being received reliably, which could lead to incorrect safety decisions or commands. The integrity of safety-critical data is compromised.

A communication error has occurred on the PROFIsafe bus, indicating a disruption in the safety communication between the I/O module and the Safety PLC. This fault prevents safe operation and will lead to a system shutdown to maintain safety.

A transmission error due to a timeout occurred in PROFIsafe communication, meaning that the expected response was not received within the specified F_WD_Time or F_WD_Time_2 watchdog period. This can lead to a safety function interruption if communication is critical.

An I/O channel is detected to be 'stuck' in a specific state, meaning its input signal is not changing as expected when it should. This indicates a potential wiring fault, sensor failure, or an internal issue with the I/O module. Such a condition compromises the reliability of the safety input and can lead to incorrect safety evaluations.

The PROFIsafe watchdog timer has expired, meaning the safety communication between the I/O module and the Safety PLC was not received within the expected timeframe. This indicates a loss of safety communication and will halt safe operations.

The safety PLC configuration specifies an F_Block_ID that is not recognized or supported by the system. This indicates an incompatibility or incorrect setting within the safety function block configuration, which can prevent safety functions from executing correctly.

Cross-talk has been detected between I/O channels, meaning signals from one channel are interfering with another due to electrical coupling. This issue compromises the independence and integrity of safety signals. It can potentially lead to incorrect readings or unintended activations/deactivations, posing a safety risk.

The version of the PROFIsafe parameter set loaded into the safety PLC is incorrect or incompatible with the current system environment or firmware. This can cause functional discrepancies, prevent proper operation of safety functions, or lead to unexpected behavior. Using an incorrect parameter set could introduce unknown safety risks.

The 'F_CRC_Length' parameter configured for PROFIsafe communication does not match the CRC length value generated internally by the device. This inconsistency in CRC configuration will lead to failed CRC checks, causing communication errors and compromising the integrity of safety data. Reliable safety communication cannot be established under these conditions.

An unrecoverable internal error has occurred within the I/O module itself, indicating a hardware or firmware malfunction. This fault prevents the module from operating correctly and requires immediate attention to restore safe system functionality.

The configured PROFIsafe destination address (F_Dest_Add) for the safety PLC is in violation of the defined PROFIsafe configuration rules. This issue prevents the proper establishment of safety communication, as the address does not conform to the protocol's requirements. Such a violation can lead to safety function failures and compromise the entire safety chain.

A significant discrepancy has been detected between redundant input channels, exceeding the configured tolerance window. This implies a potential sensor malfunction, wiring issue, or configuration error that could compromise the integrity of safety-critical inputs.

This error occurs when the measured signal value on an analog input channel exceeds the maximum range the I/O module can process. This often points to an incorrectly scaled sensor, an over-range input signal, or an issue with the sensor's power supply, leading to inaccurate measurements.

This error indicates that the measured signal value on an analog input channel is below the minimum range or threshold the I/O module expects. Possible causes include a disconnected sensor, a sensor providing too low a signal, or a problem with the sensor's power supply, resulting in no meaningful input.

This error indicates that the difference between redundant or monitored input channel values has exceeded the configured tolerance window. This suggests a discrepancy in sensor readings, a calibration issue, or a wiring fault affecting one of the channels, compromising redundant safety monitoring.

A channel readback error occurs when the actual state of an output channel, as read back by the module, does not match the commanded state. This can be due to a wiring issue, an external load problem, or an internal fault within the I/O module, leading to an unreliable output.

This error indicates unintended signal interference or coupling between different channels on the I/O module, potentially leading to incorrect signal interpretation and compromising safety functions. It's often due to improper wiring or internal module defects, resulting in false readings or outputs.

An unspecified internal error has occurred within the safety module, indicating a low-level hardware or firmware malfunction. This critical fault means the module is not operating correctly and cannot guarantee safety functions. Continued operation in this state poses a significant risk to machine and personnel safety.

An operation involving the Safety PLC has concluded, but it requires further action related to its switch address settings or the presence of an SD-Card in the non-safety PLC. This is a state indicating the PLC is not fully ready for safe operation until these parameters are correctly addressed and reset. Ignoring this can lead to incorrect PLC state or functionality.

The user-defined program or configuration data stored in the Safety PLC is incorrect, corrupted, or incompatible. This prevents the PLC from executing its intended safety logic or loading its correct parameters, posing a direct risk to machine operation and safety functions. The PLC cannot operate as programmed.

A critical internal error has occurred during the initialization sequence of the PROFIsafe functionality within the Safety PLC. This means the PLC cannot properly establish its safety-related communication and functions, making it unable to operate in a safe mode. The system's safety integrity is compromised from startup.

An error was detected while the Safety PLC attempted to read data from its internal flash memory. This often indicates corruption of the stored firmware, configuration, or boot project, or a hardware defect in the flash memory itself. This can prevent the PLC from booting up, loading its program, or maintaining persistent data, risking system failure.

An unspecified critical internal error has occurred within the Safety PLC. This points to a severe hardware or firmware malfunction that affects the fundamental operation of the PLC and its ability to guarantee safety functions. Continued operation with this error is highly risky and should be avoided.

An error occurred during the process of downloading the boot project to the Safety PLC. This means the PLC failed to properly receive or store the essential program required for its startup and initial operation. Consequently, the PLC may not boot correctly or execute any safety-critical applications, rendering it non-functional or unsafe.

The Safety PLC is currently operating with a firmware version that is incorrect, outdated, or incompatible with the loaded application or other system components. This mismatch can lead to instability, unexpected behavior, functional limitations, or failure of safety functions. Updating the firmware is essential for reliable and safe operation.

An unspecified internal error has been detected within the Safety PLC, indicating a potential hardware or firmware defect that impacts core functionality. This type of error can lead to unpredictable behavior and compromise the safety integrity level of the system. Prompt resolution is required to prevent hazardous conditions.

The Safety PLC has detected an abnormal power supply condition, specifically either an overvoltage or undervoltage. This issue can stem from an unstable power source, incorrect wiring, or a fault within the PLC's internal power conditioning circuitry. Prolonged exposure to incorrect voltage can damage the PLC or cause erratic behavior, compromising safety.

A critical, unspecified internal error has occurred within the Safety PLC, pointing towards a fundamental hardware or firmware fault. This compromises the PLC's ability to execute its safety program reliably and can lead to unexpected machine states or failure to perform safety actions. This error requires immediate attention to maintain system safety.

This indicates that the safety PLC's own user-defined program has intentionally initiated a safe stop condition. This is typically a designed response to a specific condition detected by the application logic, such as a sensor input or an internal process state deemed unsafe. It is usually not a fault of the PLC hardware itself, but rather a protective action taken by the software.

An unspecified internal error has occurred within the Safety PLC, indicating a fundamental hardware or firmware issue that prevents reliable operation. This type of error demands immediate attention as it directly impacts the PLC's ability to maintain safety functions and could lead to hazardous situations if left unaddressed.

A critical internal error has been detected within the PROFIsafe communication stack or functionality of the Safety PLC. This error directly compromises the PLC's ability to participate in safe communication and to process safety-critical data from other PROFIsafe devices. The entire safety system's integrity is at risk.

An unspecified internal error has been identified within the Safety PLC, signifying a potential hardware or firmware malfunction that affects the core functionality and reliability. This error can lead to unpredictable behavior and critically compromise the safety functions of the system. Immediate troubleshooting is required.

This error indicates that the measured process voltage supplied to the safety I/O module or its channels exceeds the permissible operating limits. This overvoltage condition can damage the module or connected components if not addressed promptly, posing a risk to system integrity.

This error indicates that the measured process voltage supplied to the safety I/O module or its channels has dropped below the minimum permissible operating limits. Insufficient voltage can lead to unreliable operation or complete failure of the module and connected components, compromising safety functions.

This error indicates that a plausibility check for internal parameters (iParameters) of the safety I/O module has failed. This usually means there's an inconsistency or invalid value in the module's configuration data, which prevents safe operation and can lead to incorrect behavior.

This error indicates that a checksum calculation for the safety-relevant configuration data (I-parameters or F-parameters) within the I/O module has failed. This signifies data corruption or an incorrect configuration download, which can compromise the integrity of the safety function and lead to unsafe conditions.

This error signifies a disruption or malfunction in the PROFIsafe communication between the safety CPU and the I/O module. This can be caused by network issues, incorrect addressing, or a faulty communication interface on the module, leading to a loss of safe data exchange.

The PROFIsafe watchdog timer has expired, meaning the safety I/O module did not receive a valid PROFIsafe telegram within the expected timeframe. This indicates a communication interruption or delay that prevents the safety system from functioning correctly, leading to a safe state.

This critical error indicates a severe, unrecoverable internal malfunction within the safety I/O module itself. This type of fault typically points to a hardware failure or a fundamental firmware issue that cannot be resolved through configuration or external checks, demanding immediate attention.

A static TRUE signal is detected at the Reset input of a safety function block (e.g., SF_EmergencyStop, SF_ESPE, SF_AOPD) while it is waiting for a primary safety input or during activation in a specific state (e.g., 8001). This condition prevents the safety function from resetting properly or clearing error states. Consequently, it keeps associated safety outputs in a safe (FALSE) state, inhibiting normal operation.

A static TRUE signal is detected at the Reset input of a safety function block (e.g., SF_EmergencyStop, SF_ESPE, SF_AOPD) while it is waiting for a primary safety input or during operation in a specific state (e.g., 8003). This condition prevents the safety function from resetting properly or clearing error states. Consequently, it keeps associated safety outputs in a safe (FALSE) state, inhibiting normal operation.

An error has been detected concerning the muting lamp for an AOPD (Active Opto-electronic Protective Device). A faulty muting lamp (indicated by S_MutingLamp = FALSE) prevents the proper visual signaling of the muting state, which is crucial for operator safety. This can lead to an unsafe condition if the lamp fails to indicate muting correctly, potentially allowing access to a hazardous area during muting.

This is a fatal error indicating that the safe function of the operating system is no longer guaranteed. It typically arises from critical issues such as a checksum error in the system Flash memory or a RAM error, compromising the CPU's core operations. This error demands immediate attention as the system will not operate reliably, potentially leading to unpredictable behavior or complete system failure.

This severe error signifies that while the operating system itself is functioning, the error-free processing of the user program cannot be guaranteed. A common cause is a checksum error detected in the user Flash memory, which impacts program execution stability. Unresolved, this can lead to incorrect program logic, unexpected machine behavior, or intermittent operational failures without crashing the entire OS.

This code can indicate that an operation has finished, or more critically, that a reserved switch address setting is being used. A reserved address setting is invalid and will prevent proper Safety PLC operation.

The user data on the Safety PLC is incorrect, corrupted, or an internal error related to user data handling has occurred. This prevents the PLC from correctly processing or storing application-specific information, affecting system functionality.

The SM560-S Safety PLC has encountered a fundamental internal error during PROFIsafe initialization or general PROFIsafe operation. This critical fault indicates a problem with the safety communication stack, preventing safe operation.

The SM560-S Safety PLC has encountered an unspecified internal error. This indicates a system malfunction that prevents normal operation and requires intervention.

The SM560-S Safety PLC has encountered an unspecified internal error. This indicates a system malfunction that prevents normal operation and requires intervention.

An error occurred while the Safety PLC was attempting to read from its internal flash memory. This indicates potential memory corruption or hardware failure, affecting PLC operation and potentially leading to data loss.

An error occurred while the Safety PLC was attempting to write to its internal flash memory. This indicates potential memory corruption or hardware failure, affecting PLC operation and the ability to save configurations or updates.

An access test to the Safety PLC has failed, or an internal error has occurred within the Safety PLC. This can be due to incorrect address settings or a hardware malfunction, preventing proper access or operation.

The SM560-S Safety PLC has encountered an unspecified internal error. This indicates a system malfunction that prevents normal operation and requires intervention.

A data integrity check (checksum) has failed within the Safety PLC, indicating corrupted configuration or firmware. This critical error affects the reliability of the Safety PLC's operation, potentially leading to unsafe states.

The SM560-S Safety PLC has encountered an unspecified internal error. This indicates a system malfunction that prevents normal operation and requires intervention.

An error occurred during the download of the boot project to the Safety PLC. This prevents the PLC from loading its operational program correctly and entering a run state, rendering it inoperative.

The PROFIsafe configuration for the I/O module is incorrect or corrupted. This prevents proper safe communication and operation of the safety I/O devices, making the safety system unreliable.

The Safety PLC's program execution time has exceeded the configured watchdog time (cycle time). This can lead to safety function violations, system halts, and an inability to maintain real-time control, compromising safety.

The SM560-S Safety PLC has encountered an unspecified internal error. This indicates a system malfunction that prevents normal operation and requires intervention.

The Safety PLC is operating with an incorrect or incompatible firmware version. This can lead to unexpected behavior, functional limitations, or complete system failure, compromising safety.

The SM560-S Safety PLC has encountered an unspecified internal error. This indicates a system malfunction that prevents normal operation and requires intervention.

The SM560-S Safety PLC has encountered an unspecified internal error. This indicates a system malfunction that prevents normal operation and requires intervention.

The Safety PLC has detected an abnormal power supply voltage condition (either too high or too low). This can lead to unstable operation or damage to the PLC components, compromising reliability.

The SM560-S Safety PLC has encountered an unspecified internal error. This indicates a system malfunction that prevents normal operation and requires intervention.

The SM560-S Safety PLC has encountered an unspecified internal error. This indicates a system malfunction that prevents normal operation and requires intervention.

A light error indicates a problem that may or may not require the user program to be stopped, depending on the application's design. Examples include issues where Flash memory could not be programmed or an I/O module has failed, but the CPU itself remains operational. The user must decide the appropriate reaction, as ignoring it might lead to impaired functionality of specific I/O or program segments without halting the entire system.

This fault indicates either a channel test pulse cross-talk error on Module 0 or a channel readback error on Module 2 of the safety I/O module. Both scenarios suggest a problem with the integrity or monitoring of safety signals within the I/O module, which can compromise the safety function.

This code indicates two distinct issues: either unintended signal interference between channels within the safety I/O module (cross-talk), or an inconsistency/invalidity in the iParameters during a plausibility check. Both can lead to incorrect signal interpretation or module malfunction, compromising safety.

A data integrity check (checksum) has failed within the I/O module, indicating corrupted configuration or firmware. This critical error affects both non-safety and safety I/O. For safety I/O, it means the safety configuration (CRCs for I- and F-Parameters) is compromised.

This code indicates either an issue with a parameter value (potentially in the master or configuration) or that the Safety PLC cannot read its configuration data. Both scenarios prevent the PLC from operating correctly, potentially due to incorrect settings or data corruption.

The Safety PLC is unable to read its configuration data, indicating corrupted or missing configuration. This will prevent the Safety PLC from operating correctly and performing its safety functions.

The configured F-Parameters for the I/O module do not align with the physical address switch setting on the module. This mismatch prevents proper communication and operation, potentially rendering safety functions inoperative.

This warning indicates an error in the periphery, such as an I/O module, which might only have future implications rather than immediate system failure. Specific examples include a short-circuit detected at an I/O module or an exhausted/missing battery. The user is responsible for deciding the necessary reaction, as ignoring it could lead to data loss (e.g., due to battery failure) or damage to peripheral components over time.

A reserved switch address setting is currently being used for the Safety PLC. This is an invalid configuration that prevents proper operation and initialization of the safety functions.

The Safety PLC failed to load its boot project, possibly due to reaching the maximum allowable power dip duration. This suggests an unstable power supply condition prevented the PLC from initializing correctly, compromising system startup.

A warning indicating an error occurred while writing data to the flash memory of the Safety PLC. This applies to various data types, including production data, boot project, boot code, firmware, password, and user data, as well as internal write operations. Such errors can lead to data corruption or prevent proper updates.

A Cyclic Redundancy Check (CRC) error was detected in the boot project. This indicates that the boot project data is corrupted, preventing the Safety PLC from loading it correctly and initializing its operations.

The Safety PLC has received either no configuration data or incorrect configuration data from the associated PM5x CPU. Without valid configuration, the Safety PLC cannot enter a run state and perform its safety functions.

During project download to the safety CPU, the download process may stall at 0 bytes or an error message might appear because the "Enable debug" parameter was incorrectly set to "OFF" for the safety CPU configuration and then downloaded to the non-safety CPU.

A user is unable to log in to the safety CPU immediately after logging out. This issue occurs if the login attempt is performed too quickly after a previous logout, indicating a temporary lockout mechanism.

A diagnosis message with severity level 3 reports "Measurement underflow at the I/O module" for an AI581-S input channel, even when an overcurrent condition was actually observed. The internal detection mechanism for AI581-S electronics is not always able to differentiate between over- and undercurrent because overcurrent can be followed by undercurrent effects.

The safety CPU fails to enter RUN mode after power-on, with the DIAG LED on and no boot project loaded. This often occurs if the power-off to power-on pause is less than 1.5 seconds, triggering a power dip detection that prevents the existing boot project from loading.

Debugging on the safety CPU is not possible even though the "Enable debug" parameter was set to "ON" and correctly loaded. This indicates that the safety project on your PC is not identical to the one currently loaded in the safety CPU, leading to a program mismatch.