ABB PB610 Panel Builder 600 Programming Software

The safety destination address (F_Dest_Add) is not valid in an AC500 V2 non-safety CPU PM5xx system. This is a critical configuration error preventing safe PROFIsafe communication.

Parameter "F_SIL" exceeds the Safety Integrity Level (SIL) specified by the device application for an AC500 V2 non-safety CPU PM5xx system. This indicates a configuration that violates the safety requirements.

The safety watchdog time value (F_WD_Time) is 0 ms in an AC500 V2 non-safety CPU PM5xx system. This indicates an invalid or unconfigured watchdog timer, critical for maintaining safe PROFIsafe communication.

A fault was detected during the internal test pulse generation or reception on a safety I/O channel. This indicates a problem with the signal path, potentially due to faulty wiring or a malfunctioning sensor preventing the test pulse from being correctly evaluated. This is a severity 3 error.

Cross-talk was detected during the test pulse operation on a safety I/O channel, indicating unwanted signal interference between channels. This can be caused by improper shielding, close proximity of signal wires, or a faulty sensor/module. This is a severity 3 error.

The measured process voltage supplied to the safety I/O module exceeds the maximum permissible limit. This indicates an overvoltage condition from the external power source feeding the module's process voltage inputs. This is a severity 3 error.

The measured process voltage supplied to the safety I/O module is below the minimum permissible limit. This indicates an undervoltage condition from the external power source feeding the module's process voltage inputs. This is a severity 3 error.

A plausibility check for internal safety parameters (iParameters) failed within the safety I/O module. This indicates an inconsistency or corruption in the module's safety configuration data. This is a severity 3 error.

A checksum verification failed for data within the safety I/O module. This indicates data corruption in the safety configuration, I-Parameters, or F-Parameters, which are critical for the module's safe operation. This is a severity 3 error.

An error occurred in the PROFIsafe communication channel between the safety CPU and the I/O module. This can be caused by network issues, incorrect addressing, or a temporary fault in the I/O module's communication interface. This is a severity 3 error.

The PROFIsafe watchdog timer for the I/O module has expired, indicating a loss of cyclic communication or a prolonged period without expected safety messages from the F-Host. This can be due to network delays or a module responsiveness issue. This is a severity 3 error.

An unrecoverable internal fault has been detected within the safety I/O module itself. This indicates a hardware malfunction, firmware issue, or critical internal processing error that prevents the module from operating safely. This is a severity 3 error.

A reserved switch address setting has been detected on the SM560-S Safety CPU. This is a warning indicating a configuration that might conflict with system reserved addresses or future functionalities.

The boot project was not loaded on the SM560-S Safety CPU, likely because the maximum allowed power dip duration was reached. This indicates a power supply instability issue preventing proper boot-up.

Power dip data was missed or corrupted on the SM560-S Safety CPU, and default power dip data was flashed. This is a warning indicating potential data integrity issues related to power supply events.

A CRC error occurred in the boot project of the SM560-S Safety CPU, indicating data corruption of the boot files. This can prevent the Safety PLC from starting correctly.

A flash write error occurred during the writing of production data on the SM560-S Safety CPU. This is a warning indicating potential issues with the non-volatile memory of the Safety PLC.

The SM560-S Safety CPU received no or incorrect configuration data from the PM5x non-safety CPU, preventing it from entering the run state.

More than one instance of SF_WDOG_TIME_SET or SF_MAX_POWER_DIP_SET parameters have been detected on the SM560-S Safety CPU. This indicates a configuration error where these safety-related parameters are defined redundantly.

A flash write error occurred during the writing of the boot project on the SM560-S Safety CPU. This is a warning indicating potential issues with the non-volatile memory of the Safety PLC, affecting its boot sequence.

A flash write error occurred during the writing of the boot code on the SM560-S Safety CPU. This is a warning indicating potential issues with the non-volatile memory of the Safety PLC, affecting its fundamental boot firmware.

A flash write error occurred during the writing of the firmware on the SM560-S Safety CPU. This is a warning indicating potential issues with the non-volatile memory of the Safety PLC, affecting its operating system.

A flash write error occurred during the writing of password data on the SM560-S Safety CPU. This is a warning indicating potential issues with the non-volatile memory of the Safety PLC, possibly affecting user access security.

A flash write error occurred during the writing of user data on the SM560-S Safety CPU. This is a warning indicating potential issues with the non-volatile memory of the Safety PLC, affecting stored user-specific information.

A flash write error occurred during the writing of user data on the SM560-S Safety CPU. This is a warning indicating potential issues with the non-volatile memory of the Safety PLC, affecting stored user-specific information.

An internal flash write error occurred on the SM560-S Safety CPU. This is a warning indicating potential issues with the internal non-volatile memory components of the Safety PLC.

A CRC1-Fault has occurred in an AC500 V2 non-safety CPU PM5xx system. This indicates a data integrity error during PROFIsafe communication, suggesting corruption of safety-critical data telegrams.

An internal flash write error occurred on the SM560-S Safety CPU. This is a warning indicating potential issues with the internal non-volatile memory components of the Safety PLC.

An internal flash write error occurred on the SM560-S Safety CPU. This is a warning indicating potential issues with the internal non-volatile memory components of the Safety PLC.

The safety source address (F_Source_Add) is not valid in an AC500 V2 non-safety CPU PM5xx system. This indicates an incorrect configuration of the source address for PROFIsafe communication.

A PROFIsafe communication error has occurred with an AC500 V2 non-safety CPU PM5xx. This means the safety module cannot correctly exchange telegrams with the safety CPU, leading to a safe state.

A safety I/O channel is detected to be 'stuck' in a fixed state (e.g., permanently ON or OFF) and does not respond to changes as expected. This suggests a potential internal fault within the I/O module or an external wiring issue causing the channel to be latched. This is a severity 3 error.

Parameter "F_Block_ID" is invalid or not supported in this configuration for an AC500 V2 non-safety CPU PM5xx. This indicates a mismatch in the identifier for the safety function block.

The input measurement on a safety I/O channel has exceeded its maximum detectable range. This typically occurs when the signal from the connected sensor or device provides a value higher than the module's input specification, or due to incorrect wiring. This is a severity 3 error.

The input measurement on a safety I/O channel has fallen below its minimum detectable range. This can be due to an under-range signal from the sensor, incorrect wiring, or an issue with the sensor's power supply. For AI581-S input channels, the internal detection mechanism might not differentiate between over- and undercurrent effectively, as overcurrent can be followed by undercurrent effects in the electronics. This is a severity 3 error.

Cross-talk was detected on a safety I/O channel, indicating unwanted signal interference between channels. This can be caused by improper shielding, close proximity of signal wires, or a faulty I/O module. This is a severity 3 error.

The safety destination address (F_Dest_Add) for F-device instance <n> in an AC500 V3 non-safety CPU PM56xx system is not valid. This is a critical configuration error preventing safe PROFIsafe communication.

The safety source address (F_Source_Add) for F-device instance <n> in an AC500 V3 non-safety CPU PM56xx system is not valid. This indicates an incorrect configuration of the source address for PROFIsafe communication.

Parameter "F_SIL" for F-device instance <n> in an AC500 V3 non-safety CPU PM56xx system exceeds the Safety Integrity Level (SIL) specified by the device application. This indicates a configuration that violates the safety requirements.

The F-device instance <n> for AC500 V3 non-safety CPU PM56xx is configured with a safety watchdog time value (F_WD_Time) of 0 ms. This indicates an invalid or unconfigured watchdog timer, critical for maintaining safe PROFIsafe communication and preventing the module from going to a safe state.

A CRC1-Fault has occurred in F-device instance <n> for AC500 V3 non-safety CPU PM56xx. This indicates a data integrity error during PROFIsafe communication, suggesting corruption of safety-critical data telegrams.

A PROFIsafe communication error has occurred for F-device instance <n> with AC500 V3 non-safety CPU PM56xx. This means the safety module cannot correctly exchange telegrams with the safety CPU, leading to a safe state.

The PROFIsafe watchdog for F-device instance <n> with AC500 V3 non-safety CPU PM56xx has timed out. This indicates that safety communication telegrams are not being received within the expected time, potentially due to communication issues or an incorrectly configured watchdog timer.

Parameter "F_Block_ID" for F-device instance <n> in an AC500 V3 non-safety CPU PM56xx system is invalid or not supported. This indicates a configuration mismatch for the safety function block identifier, preventing correct safety function execution.

The safety destination address (F_Dest_Add) for F-device instance <n> in an AC500 V3 non-safety CPU PM56xx system does not match the expected value. This is a critical configuration error preventing safe PROFIsafe communication.

The version of the F-Parameter set for F-device instance <n> in an AC500 V3 non-safety CPU PM56xx system is incorrect. This indicates a mismatch between the configured safety parameters and the expected version, which can compromise safety integrity.

Parameter "F_CRC_Length" for F-device instance <n> in an AC500 V3 non-safety CPU PM56xx system does not match the generated values. This indicates a misconfiguration in the CRC length parameter for PROFIsafe communication, leading to data integrity errors.

An internal PROFIsafe error has occurred for F-device instance <n>. This indicates a fault within the PROFIsafe communication stack or processing logic of the F-device, leading to compromised safety communication.

The time difference between input signals from redundant sensors connected to a safety I/O module has exceeded the configured discrepancy time limit. This indicates a potential issue with sensor synchronization, signal integrity, or incorrect timing configuration. This is a severity 3 error.

The difference between redundant channel values (e.g., from two sensors monitoring the same safety function) has exceeded the configured tolerance window. This indicates a significant discrepancy in sensor readings or a potential issue with one of the channels. This is a severity 3 error.

The safety program is not started, or no application is running in the SM560-S Safety Module. This prevents the safety CPU from performing its intended safety functions.

The version of the F-Parameter set is incorrect in an AC500 V2 non-safety CPU PM5xx system. This indicates a mismatch between the configured safety parameters and the expected version, which can compromise safety integrity.

Parameter "F_CRC_Length" does not match the generated values in an AC500 V2 non-safety CPU PM5xx system. This indicates a misconfiguration in the CRC length parameter for PROFIsafe communication, leading to data integrity errors.

An error occurred during the internal readback verification process of a safety I/O channel. This suggests a problem with the module's internal diagnostic capabilities, or a discrepancy between the commanded state and the actual state of the output. This is a severity 3 error.

Cross-talk was detected on a safety I/O channel, indicating unwanted signal interference between channels. This can be caused by improper shielding, close proximity of signal wires, or a faulty I/O module. This is a severity 3 error.

A transmission error indicating inconsistent data due to a CRC2 error has occurred in an AC500 V2 non-safety CPU PM5xx system. This signifies a loss of data integrity during PROFIsafe communication.

A transmission error due to a timeout has occurred in an AC500 V2 non-safety CPU PM5xx system, meaning either F_WD_Time or F_WD_Time_2 has elapsed without receiving expected communication. This indicates a communication failure or an incorrectly configured watchdog timer.

This diagnostic code indicates that the SF_ESPE safety function is in a state where it is waiting for a reset. The `Activation` and `S_EStopIn` input signals are TRUE, but the safety output `S_EStopOut` is FALSE, signifying that the safety function is active and outputs are disabled. A reset is requested (`ResetRequest = TRUE`) to allow the system to transition back to an operational state.