ABB AC500 Function Block Libraries

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 'F_SIL' parameter configured within the safety PLC, which defines the Safety Integrity Level, is set higher than what the specific device application supports. This mismatch indicates an over-specification or misconfiguration that could lead to unexpected behavior, non-compliance with safety standards, or incorrect safety function execution. The system may not operate within its validated safety limits.

The PROFIsafe watchdog time parameter (F_WD_Time) in the safety PLC configuration is set to 0 milliseconds. A zero value is invalid and effectively disables the watchdog, which is critical for monitoring the timeliness of safety communication. Without a functioning watchdog, communication failures or system freezes might go undetected, posing a significant safety risk.

A test pulse error indicates a problem with the safety module's ability to generate or detect test pulses on its input channels. This mechanism is crucial for detecting short circuits to supply voltage or ground, or open circuits, and its failure means a potential undetected wiring fault.

This error suggests that a test pulse intended for one channel is being incorrectly detected on another, or vice-versa, indicating signal interference between channels. This can be caused by faulty wiring or internal issues within the I/O module, leading to unreliable input detection.

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.

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.

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.

A transmission error occurred, specifically indicating data inconsistency (CRC2 error) during PROFIsafe communication. This suggests corruption or incorrect data during transmission, which is critical for maintaining safety integrity.

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.

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.

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.

A mismatch has been detected in the PROFIsafe destination address (F_Dest_Add) configured for the safety PLC. This indicates that the PLC's intended communication partner cannot be correctly identified or addressed, leading to communication failures and potentially disabling critical safety functions. Incorrect addressing could result in unintended machine behavior.

This error occurs when the configured discrepancy time for inputs has been exceeded. This typically indicates a mismatch or delay in signals from redundant input channels, suggesting a sensor or wiring issue, or an incorrectly set discrepancy time, which can compromise the safety function's reliability.

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.

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 internal error has occurred within the PROFIsafe F-Device functionality of the safety PLC. This indicates a critical malfunction that could compromise the integrity and reliability of safety functions within the system. If left unaddressed, the safety PLC may not operate correctly or may fail to perform its safety-critical tasks.

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.

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.

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.

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.

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.