Hello everyone! I recently purchased a Beckhoff CX9000 (N031) and am encountering issues reconnecting to the PLC after simulating a communication loss. To recreate this scenario, I unplugged the Ethernet cable from my PC and reconnected it after a 30-second wait. Unfortunately, I am now experiencing difficulties with the reconnection process. When I launch the System Manager, it displays a 'timeout' error, and my broadcast search does not detect the PLC at all. Additionally, I cannot successfully ping the PLC from the command prompt. I'm wondering if I might have overlooked any configurations or if anyone has insights on how to resolve this issue. After initially setting up the CX9000, I performed a factory reset, and the PLC immediately appeared during a broadcast search. I then assigned a static IP address and rebooted the PLC. Everything was functioning smoothly, and I even downloaded and ran a sample project without any problems. However, the issue arose after I disconnected the Ethernet cable. I am currently using TC V2.11, the free version from the official site, and have not registered yet. Any assistance or guidance would be immensely appreciated! Thank you!
Experiencing a lack of connection with your CX9000? That’s not ideal. It seems like the device isn't showing up in your router settings. Here are some recommended troubleshooting steps: First, try connecting the CX9000 to a different port on the router and use a different Ethernet cable. If that doesn’t resolve the issue, consider performing a factory reset on the device to revert it back to DHCP settings. Additionally, make sure you reboot the CX9000 after assigning a static IP address; this is essential for the changes to take effect properly.
Subject: Update on PLC Connection Issues Hello Ivo, Thank you for your prompt response. Here are my observations thus far regarding the PLC connectivity issue: I performed another factory reset, this time avoiding the assignment of a static IP address to the PLC. I disconnected the Ethernet cable, and the System Manager displayed a 'timeout' error. After waiting for approximately 50 seconds, I reconnected the cable, and the controller reappeared within about 20 seconds. I successfully downloaded my PLC program and then disconnected the cable again. Upon reconnecting the cable, the controller failed to show up this time, even after waiting for 5 minutes. In an attempt to troubleshoot, I rebooted my computer and reopened the System Manager. To my relief, I regained immediate connectivity with the PLC. It seems that a reboot is necessary after experiencing a connection failure. However, I require the PLC to have a static IP address. I will now test this configuration. When I set a static IP, the System Manager indicates that the PLC needs to restart, which I confirm by clicking 'OK.' The PLC initiates a restart, as indicated by the LED lights. Is this the reboot you were referring to, or do you suggest that I should also cycle the power to the PLC afterward? Looking forward to your guidance. Best regards.
PieterDM inquired: "When I assign a static IP address, the system manager indicates that the PLC must restart, so I click 'OK.' I notice the restart when the LEDs change. Is this the reboot you’re referring to? Or are you suggesting that I should also cycle the power of the PLC afterwards?" To clarify, the automatic restart you observe is indeed what I meant by a 'reboot.' Typically, restarting the PLC or any Ethernet device is essential to activate the new static IP address. My question for you is: What specific IP address and subnet mask are you using? Are you utilizing a Telenet or Proximus router, or is there a different router in your setup?
PieterDM commented: "After rebooting my computer and launching the system manager once more, I regained immediate access to the PLC. It appears that a reboot is necessary following a connection failure. Click here to expand... This issue shouldn't be occurring. Did you also restart the PLC simultaneously? Additionally, do you know the process for activating your configuration, downloading a program, and creating a boot project to ensure that the PLC restarts its program and settings after a power outage?"
Here are the connection details for my PLC setup: The IP address assigned to my PLC is 192.168.1.69, while my PC is configured with the IP address 192.168.1.70. Both devices share the subnet mask of 255.255.0.0. I connect my PLC directly to my PC without using a switch. I haven't rebooted the PLC, only my PC, before accessing the system manager. Yesterday, I assigned a static IP address to my PLC and downloaded a sample project, which consists of a single pulsing output. I can easily verify that my program is running by observing the LEDs on the output card. After confirming that my program was operational, I disconnected the cable, waited for about half a minute, and then reconnected it. However, since that moment, I have been unable to establish a connection with the PLC again. I'm beginning to suspect that there may be an issue with the CX. I haven't created a boot project yet, and I’m unsure of the process. Although I have some experience with Rockwell PLCs, this is my first time working with a Beckhoff PLC.
Hey there! It sounds like you've been troubleshooting quite a bit already. Since you're experiencing a timeout error and can't ping the PLC, I’d suggest double-checking the static IP configuration on both your PC and the CX9000 to ensure they’re in the same subnet. Sometimes, a temporary IP conflict can occur if the PLC was previously set to a different address before the reset. Additionally, it might help to power cycle the PLC after plugging back in the Ethernet cable, just to reset any communication issues. If you have access to a different Ethernet cable or port, trying those could also rule out any physical connection issues. Hope this helps, and good luck getting it sorted!
Hey there! It sounds frustrating what you're dealing with. Have you checked if the static IP address you assigned is still the same after reconnecting? Sometimes devices can lose their network configurations due to various issues. I’d also recommend checking the network settings on your PC and ensuring there are no conflicting IP addresses. Another thing to try is to power cycle both the CX9000 and your PC after reconnecting the Ethernet cable, as sometimes devices need a refresh to recognize each other again. Hope that helps you get it sorted!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: 1. Ensure the Ethernet cable is securely connected. 2. Verify that the network settings on your PC are correctly configured. 3. Perform a network reset on the PLC. 4. Use a direct connection with a crossover cable to rule out switch or router issues.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.