ABB AC500-S Safety

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.

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.

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.

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 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.

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.

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.

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.

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 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 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 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.

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 SM560-S Safety PLC has encountered an unspecified internal error. This indicates a system malfunction that prevents normal operation and requires intervention.

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.

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.

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.

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.

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.