Hello, we are currently experiencing issues with FactoryTalk Linx on one of our two standalone FactoryTalk Site Edition clients. The problem arose after a power failure, causing the software to stop working. To resolve this issue, we uninstalled and reinstalled all FactoryTalk software. Initially, the software appeared to be functioning properly, but we soon noticed that the FactoryTalk Client was intermittently freezing. When examining the Diagnostics Viewer during these freezing episodes, we received messages such as: "Driver Ethernet re-established a session to IP" and "Driver Ethernet lost communications to IP: connection reset by peer." These messages pertain to IP addresses that are not crucial to our operations, as we only use PLCs in the Communication Setup. These messages are specific to one station only, even though the FactoryTalk Linx drivers and devices on both stations are almost identical. Despite attempting to remove the problematic devices, it seems that the Ethernet driver automatically scans the network, and we are unsure how to modify this setting. We would greatly appreciate any assistance or insights you can provide to help us troubleshoot this issue. Thank you for your help.
I attempted to remove all shortcuts and recreate them, but unfortunately, that did not resolve the issue. Next, I tried uninstalling the RSLinx Enterprise server, but that also did not produce any results.
I faced a similar issue with a FactoryTalk SE client a while back and here's what worked for me. FactoryTalk Linx does indeed scan the entire subnet by default, but you can fine-tune it. Open FactoryTalk Linx and go to 'RSWho'. Go to the Ethernet driver you're using, right click and select 'Properties'. Under the 'Settings' tab, you should see an option to add specific IP addresses rather than scanning the entire subnet. Add the IP addresses of the PLCs you're using there and it should stop these unneeded devices from causing problems. Don't forget to restart the service afterward for changes to take effect. Hope this helps!
It sounds like you're dealing with a challenging situation! Given the issue arose after a power failure, it's possible some of your system settings got affected. I suggest you look into the FactoryTalk Linx settings, there should be an option to adjust your Ethernet Driver settings. This may allow you to stop the automatic network scan. Alternatively, you could check if there are any specific firewall settings that can control this. Furthermore, double check your communication settings in the PLC to ensure everything is in order. You might also want to look into "Garbage Collection" and "Destination Table Refresh" settings in FactoryTalk as these can affect communications. Lastly, ensure your network is healthy and there aren't IP address conflicts. Hope this provides some direction for troubleshooting, good luck!
It sounds like you're experiencing a bit of a difficult situation. When dealing with issues like these, one possibility is that the power failure may have caused some hardware or network damage that's affecting FactoryTalk Linx. However, since this appears to be a communication issue, it could also be IP related. Have you tried checking the Ethernet cable connection, or replacing it in case of physical damage? Additionally, you've mentioned that you have two standalone FactoryTalk Site Edition clients. Is it possible to run the setup on the other client to rule out specific machine-based issues? As for the automatic scan of network by the Ethernet driver, try going into the RSLinx Classic driver configuration and unchecking the "Automatically Browse Nodes Upon Startup". This should stop the driver from scanning the network.
It sounds like a frustrating situation! One thing you might want to check is whether there are any rogue devices on the network that could be causing those intermittent communication issues. Sometimes, software can pick up devices it shouldn't if there's a scanning function enabled. If the Ethernet driver is automatically scanning your network, you might find an option in the driver settings to limit the scanning to only active devices or specific IP ranges. Also, reviewing the communications settings in both FactoryTalk Linx and the corresponding PLCs for any discrepancies could help. Good luck, and I hope you get it sorted out soon!
✅ 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: Answer: The freezing issue could be related to messages in the Diagnostics Viewer such as "Driver Ethernet re-established a session to IP" and "Driver Ethernet lost communications to IP: connection reset by peer" that pertain to non-critical IP addresses.
Answer: Answer: You can try removing the problematic devices and investigating how the Ethernet driver automatically scans the network, as modifying this setting might help resolve the freezing problem.
Answer: Answer: The issue could be related to the network configuration or specific settings on that particular station, which may need to be reviewed and adjusted to address the freezing problem.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.