PM5x Configuration Data Error

What does E4-26 mean?

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.

• Communication failure between the PM5x CPU and the Safety PLC (e.g., SM560-S) preventing data transfer.
• Incorrect or mismatched hardware configuration of the Safety PLC module in the PM5x CPU's project.
• Corrupted configuration file stored on the PM5x CPU or transfer media.
• Incorrect network addressing (e.g., PROFINET device name) preventing the PM5x from locating the Safety PLC.
• Outdated firmware on either the PM5x CPU or the Safety PLC causing compatibility issues with configuration data.

Click steps to track your progress.

1. 1

   1. Verify the communication status between the PM5x CPU and the Safety PLC using the diagnostic tools in the engineering software.

2. 2

   2. Ensure that the hardware configuration of the Safety PLC (e.g., SM560-S module type, firmware version) in the PM5x CPU's project matches the physical device.

3. 3

   3. Check the network address settings (e.g., IP address, PROFINET device name) of the Safety PLC to ensure they are unique and correct.

4. 4

   4. Re-download the complete PM5x CPU project, including the Safety PLC configuration, to the PM5x CPU.

5. 5

   5. Inspect the communication cable (e.g., X2 PROFINET cable) connecting the PM5x CPU and the Safety PLC for damage or loose connections.

6. 6

   6. Check Parameter P-CONFIG_TIMEOUT (if applicable) in the PM5x CPU for too short a timeout value, and increase if necessary.