Access Test Failed / Internal Error (SM560-S)

What does E2-17 mean?

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.

• Incorrect IP address or network settings configured for the SM560-S Safety PLC, preventing communication from the engineering workstation.
• Hardware malfunction within the Ethernet port or communication processor of the SM560-S PLC, preventing it from responding to access requests.
• Damaged or faulty Ethernet cable (e.g., Cat5e or Cat6) connecting the engineering workstation to the Safety PLC, causing intermittent or no communication.
• Firmware bug or internal operating system error in the SM560-S PLC preventing it from correctly handling communication requests or diagnostic tests.
• Network firewall settings on the engineering workstation or an intermediate network device blocking communication ports (e.g., Port 1200) required for PLC access.

Click steps to track your progress.

1. 1

   1. Verify the IP address and subnet mask settings of the SM560-S Safety PLC via its display or a direct connection, ensuring they match the engineering workstation's network configuration.

2. 2

   2. Replace the Ethernet cable connecting the engineering workstation to the Safety PLC's programming port with a known good, certified Cat5e or Cat6 patch cable.

3. 3

   3. Ping the Safety PLC's IP address from the engineering workstation's command prompt to verify basic network connectivity (e.g., 'ping 192.168.1.10').

4. 4

   4. Power cycle the SM560-S Safety PLC and attempt to access it again via the engineering software immediately after it restarts.

5. 5

   5. If direct access fails, attempt to connect via a different communication path (e.g., serial port, if available) to check basic functionality.

6. 6

   6. If all other steps fail, consider replacing the SM560-S Safety PLC CPU module with a known good spare.