Hello, I was using AS 4.9 to connect with the X20CP0410 PLC via Ethernet. Everything was fine until I made a transfer to the target, which took a lot of time and the loading bar didn’t make any progress. I clicked ‘cancel’ and got a message which said something about losing connection to the target. Now I can’t find the PLC in Online → Settings while searching. I have already reinstalled AS, AR, PVi several times… I can ping him but nothing else.
Did the cancelation do something to the PLC ? Thanks for help in advance!
You can make an Offline-Transfer to CF-Card with a Cardreader and Boot the PLC again with the new CF.
After you can connect to the projected IP-Adress again.
Thanks for the reply! I will try it tomorrow and let you know if it worked .
Hi,
I am not sure if that applies to AS4.9.
But did you activate SNMP in the Ethernet Configuration?
Right click on yout Ethernet Port and “Configuration”.
It sounds like the CPU got a new IP Adress from transfering, the project (thats why you lost connection) and because SNMP is deactivated, AutomationStudio cannot find it anymore
If you can Ping the CPU, you should also be able to connect to it, just enter the IP Address directly into “Destination IP address” and click connect (in Online->Settings).
I’m sorry, but it seems that i can’t find any information about the location of the CF card slot in the PLC, do you know where it’s located?
Hello, thanks for the reply. Yes, SNMP is activated. Did you mean entering the IP directly like in the screenshot? Doing so I still canot do a transfer do the target.
Hi,
you can put the CPU into BOOT mode by the small button:
BOOT mode enables you to either ‘see’ the CPU with SNMP (Automation Studio Online dialog) again or to flash the CPU by an USB stick. In the latter case, you must of course first create the USB stick and then press the button.
Unfortunately it is a little bit tricky to enter this mode. If you press the button in the wrong way you could enter in SERV or DIAG.
1 Like
yes, that is what i meant. that way you at least should get a Connection to check the status of the cpu. As descripted by Christoph
Unfortunately the issue remains the same. Even in BOOT mode, i cannot see the PLC in Online Settings. We going to try to connect from a different laptop. It is weird that i can ping the PLC but can not see it in AS. Can it be that AS 4.9.2.26 is not compatible with Windows 10 Pro ?
I’m really running blank here, why did this happen in the first place.
Can’t see any mention about the CF card in X20CP0410
Martin, this was my mistake. There is’nt a CF-Slot. But you have to load the project with USB-Stick as described by Christoph Hilchenbach before.
1 Like
try to reinstall PVI 4.12
This comes with an installer for npcap driver which enables the CPU search via SNMP.
I reinastalled PVI 4.12, now i get an Error while opening AS “unable to start pvi manager error 12064 B&R”
Okay, I fixed the problem by connecting to the PLC per another laptop and changing his IP address. Now, on the first laptop where I couldn’t connect first, my Upgrade service won’t start. After trying to trigger it in services.msc i get a Windows error 3 saying the system cannot find the path specified.
I know that is too late. But for next time, here is the output of our conversational Help how to resolve problem with AS online connection.
To debug the problem with connecting Automation Studio (AS) to the PLC, even though you can ping it, follow these steps:
Steps to Resolve Connection Issues:
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Network Configuration:
- Step: Use the
ipconfig /allcommand 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.
- 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:
2 Likes
Again some tips from our conversational help:
To resolve the issue where the B&R Upgrades Service fails to start and you receive a Windows error 3 stating “the system cannot find the path specified,” follow these steps:
- Check Service Path:
- Open the Windows Services management console by pressing Win + R, typing
services.msc, and pressing Enter. - Locate the B&R Upgrades Service (specific to your Automation Studio version, e.g., AS412).
- Right-click on the service and select Properties.
- In the General tab, check the Path to executable. Ensure that the path specified is correct and that the executable file exists at that location.
- Correct the Service Path:
- If the path is incorrect or the executable is missing, you may need to reinstall the B&R Upgrades Service or correct the path manually.
- Navigate to the installation directory of Automation Studio and verify the presence of the upgrade service executable.
- Check for Missing Files:
- Ensure that all necessary files for the upgrade service are present in the installation directory. Missing files can cause the service to fail to start.
- Run as Administrator:
- Ensure that you have the necessary permissions to start the service. Right-click on the Automation Studio shortcut and select Run as administrator.
- Check System Updates:
- Ensure that your Windows system is up to date. Sometimes, missing system updates can cause services to fail.
- Review Event Viewer Logs:
- Open the Event Viewer by pressing Win + R, typing
eventvwr, and pressing Enter. - Navigate to Windows Logs > System and look for any error messages related to the B&R Upgrades Service. This can provide more detailed information about why the service is failing to start.
By following these steps, you should be able to resolve the issue with the B&R Upgrades Service and successfully start it to install upgrades in Automation Studio. If the problem persists, consider reaching out to B&R support for further assistance.
Further Information:
1 Like