Hello there, I currently have multiple Omron PLCs connected to my KepserverEx, which in turn communicates data to my InTouch system. I have noticed a recurring issue where the connection drops roughly every 40 seconds, causing KepserverEx to log an error stating 'Device is not connected'. However, within a few seconds, the connection automatically reestablishes and starts logging data again. Interestingly, during this time period, the ping status of the device appears to be functioning correctly. I have checked and adjusted both the PLC and KepserverEx settings, but the issue persists across all Omron PLCs. Can anyone provide assistance with resolving this connectivity problem?
If you are utilizing the Ethernet/IP tag protocol, you may encounter a similar issue with Omron NJ communications. Through my experience, I have found that enhancing performance can be achieved by closing the TCP socket connection after each communication and reopening it for the next one. It is unclear if Kepware offers this as a configurable option.
How did you activate that feature?
I am implementing it within my C programming code without utilizing Kepware. It is recommended to verify if Kepware offers the necessary functionality for your project.
Do you know the maximum number of connections that can be established on an Omron PLC? I currently have 4 OPC servers - 2 Kepware KEPServerEx servers with 1 in operation and 1 as a standby, and 2 Industrial Gateway servers for MES. The configuration of both KEPServerEx servers is identical, but when running an OPC client on both servers, one goes into a "bad data" state while the other remains in a "good data" state. I am having trouble identifying the root cause of this issue.
From my personal experience, this could be an issue related to excessive traffic or network latency, especially if you're running multiple PLCs on the same network. Consider dedicating a specific subnet for your PLCs to avoid packet collisions and traffic congestion. Another possible cause might be your KepserverEx's scan rate. If it's too high, it might be overloading the PLCs. Try adjusting the scan rate to see if the situation improves. Lastly, remember to double-check the timeout settings on both the PLCs and the KepServerEx, as too short timeouts might lead to such drops.
It sounds like you’ve done a solid job troubleshooting already! Since the connection drops every 40 seconds, it might be worth checking if there's a timeout setting in either the PLC or KepserverEx that's set too low. Sometimes, network congestion or intermittent issues can cause these brief disconnections, so ensuring that your network is stable could help too. Additionally, consider running some diagnostics on the network traffic to see if there are any patterns during those disconnects—tools like Wireshark can be useful for that. If everything seems fine, it might also help to reach out to Omron support for any firmware updates or known issues with the models you’re using. Good luck!
It sounds frustrating to deal with those intermittent connection drops! Since you've already checked the settings on both the PLC and KepserverEx, it might be worth looking into the network stability itself. Sometimes, network switches or routers can cause issues if they're overloaded or misconfigured. You could also try increasing the timeout settings in KepserverEx to see if that helps; at times, the default settings can be too aggressive for certain network conditions. Lastly, check for any firmware updates for both the PLCs and KepserverEx, as updates can often resolve underlying bugs. Hope you find a solid solution soon!
Have you tried checking the network configuration and ensuring there's no interference or bottleneck that might be causing the timeouts? Sometimes it's worth looking into the Ethernet settings on your Omron PLCs, especially the timeout and keep-alive settings. Also, ensure that your firewall or any security software isn't intermittently blocking the connection. If the ping is stable, it may not be a network issue but rather a configuration or resource limitation in KepserverEx. It might also be helpful to look at whether there are any firmware updates for your PLCs or KepserverEx that could address this issue. Good luck!
✅ 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: - This could be due to network issues, communication settings, or compatibility problems. Troubleshooting steps may involve checking network stability, adjusting communication settings, or updating firmware.
Answer: - To maintain a stable connection, verify network configurations, ensure proper communication protocols are in place, monitor for any interference or traffic congestion, and consider updating software or drivers if necessary.
Answer: - Start by checking individual PLC settings, reviewing KepserverEx configurations, monitoring network traffic, verifying cable connections, and investigating any potential software conflicts or updates required.
Answer: - In cases where the ping status is normal but connectivity drops persist, focus on checking for intermittent issues like network latency, signal interference, or software glitches that may not be reflected in the ping status. Further investigation and testing may be needed to pinpoint the root cause.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.