Ewrong, the censored brand of remote access, is causing some frustration as I try to troubleshoot a connection issue. Despite being able to ping everything at a remote site I have never visited before, I am unable to get the programmable logic controller (PLC) to show up in RSLinx. My coworker made changes via Teams before Ewrong was activated, leaving me wondering if I am missing something obvious in this remote access dilemma.
When setting up your network, it is important to use the Ethernet Devices driver instead of the Ethernet I/P driver. The Ethernet I/P driver relies on broadcast packets for device discovery, which inherently prevents them from being routed through a network. This distinction is crucial for ensuring proper connectivity and network communication.
I came across this information in a different discussion thread, but unfortunately overlooked a vital component. In my rush, I neglected to include the crucial detail of the IP address. Thank you for pointing that out.
Being a devoted fan of The Simpsons, I always appreciate you and thank you for visiting.
eWon technology provides innovative solutions for remote access and monitoring, optimized for industrial applications.
The MSP's comment was clever and intriguing.
It certainly sounds like a challenging situation you're in. Ewrong can definitely be a bit finicky at times. If you're able to ping everything at the remote site, it most likely means the issue lies with the PLC recognition in RSLinx rather than the remote access itself. You may want to consider a couple of things: Double check the IP addresses, subnet mask and default gateway, also whether the driver is correctly set up in RSLinx. It's also possible your coworker's changes somehow affected the controller's visibility (firewall settings, perhaps?). Unfortunately, remote troubleshooting can be a trial and error process, but I bet you'll find your answer soon. Good luck!
It sounds like you’re facing a tricky situation! Since you can ping everything, it’s a good sign that the network is functioning, but issues with RSLinx can often come down to configuration settings or permissions. Have you checked the protocol settings in RSLinx to ensure they match what’s expected for the PLC? Sometimes, remote access tools can introduce unexpected quirks, so it might also be worth verifying that the right drivers are installed and that the PLC is actually set to allow remote connections. If it's feasible, a quick call with your coworker to clarify the changes made could shed some light on any specifics that might have been overlooked.
✅ 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. Q: Why am I unable to see the programmable logic controller (PLC) in RSLinx despite being able to ping everything at a remote site? This could be due to a configuration issue related to the Ewrong remote access software or settings specific to the PLC or RSLinx.
Answer: You can start by verifying the settings and configurations in Ewrong, checking if any changes made via Teams could have affected the connection, and ensuring the correct project path is set in RSLinx.
Answer: It is important to review the changes made by your coworker, confirm if they could be related to the remote access issue, and check if any settings need to be adjusted to establish a successful connection.
Answer: One common issue could be a mismatch in network configurations or firewall settings that are impacting the communication between Ewrong, the PLC, and RSLinx. Checking these settings could help resolve the problem.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.