Establishing an Ethernet connection with X20CP1485

I am new to this system and I am having difficulty establishing an Ethernet Connection with the target for diagnostics. I can see the target on the router which shows an IP address of 162.168.0.3, however, the B&N automation software does not seem to see it on the network nor establish any sort of link. Even when I make a new connection with that IP address it will not connect. The unit is in boot mode and when I browse for target, the CPU does not come up. It does have a card in it and I don’t know what program it is running, however in boot mode it should not be running the card program. Any suggestions?

Steps to Resolve Connection Issues:

  1. Uninstall and Reinstall PVI:
  • Solution: Uninstall the current PVI (Process Visualization Interface) software and reinstall it.
  • Rationale: PVI is crucial for communication between AS and the PLC. A fresh installation can resolve issues caused by corrupted or outdated files.
  1. Check NPCAP Configuration:
  • Step: Ensure that NPCAP (Nmap Packet Capture) is enabled on your network interface.
  • Rationale: NPCAP is necessary for network communication and can sometimes be disabled or misconfigured, leading to connectivity issues.
  1. Firewall Configuration:
  • Step: Verify if a company firewall is blocking communication with non-Windows hosts.
  • Rationale: Firewalls can sometimes restrict communication between different types of devices on the network. Temporarily disabling the firewall can help diagnose if it is the cause of the issue.
  1. Ping the PLC:
  • Step: Use the command line (cmd) to ping the PLC to check if it is reachable.
  • Rationale: If the PLC is not reachable via ping, it indicates a network issue that needs to be addressed before attempting to connect via AS.
  1. Check the “npf” Driver:
  • Step: The “npf” driver, part of the WinPcap installation package, is essential for network communication in AS.
  • Rationale: If the driver is not running, reinstall WinPcap from the official website to ensure it is correctly installed and running.
  1. Verify SNMP Configuration:
  • Step: Ensure that SNMP (Simple Network Management Protocol) is active for the PLC.
  • Rationale: SNMP is necessary for the PLC to be discovered on the network.
  1. Check Network Layer 2 Connection:
  • Step: If a PLC is found using the “search for PLC” function but cannot be pinged, it indicates that the network layer 2 connection is working, but the network layer 3 (IP address layer) is not.
  • Rationale: This can be a sign that higher-level protocols like TCP, which the PLC’s online protocol uses, are not functioning properly.
  1. Network Configuration:
  • Step: Use the ipconfig /all command in the Windows Command Prompt to check your network settings and ensure that the IP configuration is correct.
  • Rationale: If you have multiple Ethernet interfaces on the PLC, ensure that they are configured for different IP subnets. If multiple interfaces are in the same subnet, it can cause IP communication issues.
  1. Additional Resources:
  • PVI Download: PVI can be downloaded from the B&R website here.
  • Rationale: Using the latest version of PVI ensures compatibility and resolves any known issues.

By following these steps, particularly the reinstallation of PVI and ensuring NPCAP is enabled, the connectivity problem should be successfully resolved.

Further Information:

1 Like