Hello everyone, I am currently utilizing an SLC 5/05 processor along with a PanelView Plus 1000 (model T10C4D1). Initially, I designed all the screens using FactoryTalk View and set up the RSLinx Enterprise communication. I assigned the SLC 5/05 an IP address of 10.82.1.21 and created an application running on firmware version 5.00. The PLC's IP address is 10.82.1.21, while the PanelView's IP is 10.82.1.20. I connected both devices through an Ethernet switch (Hitchmann). I successfully established a connection with the PLC and was able to download the application to the PanelView. I can confirm that I can ping both devices from my computer. However, I am puzzled as to why they aren't communicating effectively. The HMI screen displays several errors, but when I run the test application in FactoryTalk View, everything appears to be functioning correctly. Furthermore, I noticed that the screens on the PanelView were initially responsive, but after making an edit and re-downloading the application, the communication issue arose. Although I can still ping both devices using the command prompt, they are not interacting with each other. What could be the underlying problem? I would greatly appreciate any assistance or insights into resolving this issue. Thank you!
Ensure you verify the configurations in the Communications/RSLinx section of your FactoryTalk View (FTV) application. Within this area, you will find separate tabs for your workstation (your laptop) and for runtime settings. It is essential to specify the path to the PLC in the runtime tab, which should begin with the PV and direct towards the processor. Be aware that the test successfully operates using the other pathway designed for development purposes, rather than the runtime settings.
Mdim mentioned: "Be sure to check the settings in the Communications/RSLinx section of your FactoryTalk View (FTV) application. You'll find two tabs there: one for the station (your laptop) and another for runtime configurations. It's essential to specify the correct path to the PLC within the runtime tab, with the path beginning from the PV and directing towards the processor. I verified that the test is functioning correctly with the design path, but it's crucial to ensure that the runtime path is also set accurately." Thank you for your response! I've already confirmed that both the design and runtime paths are configured identically.
If you are following the same path and have configured the device shortcut to direct to the PLC (with the PLC clearly highlighted), it might be necessary for you to select the "Replace Terminal Communications" tab (or a similarly named option) when downloading your application.
User "mdim" suggests that if the path remains unchanged and you have set a device shortcut directing to the PLC (ensure the PLC is highlighted), you may need to select a tab labeled "Replace Terminal Communications" or something similar when downloading your application. Click to expand for more information. Thanks, it worked well! However, I'm unsure why it wasn't functioning correctly earlier. If I want to modify certain screens on a running HMI PV that is connected to a functioning PLC, what steps should I take? Should I disconnect the HMI from the PLC, or is it possible to connect directly while it's running?
Rehu09 expressed gratitude, stating, "Thank you, it worked well! However, I'm unsure why everything was functioning properly, yet it still had issues. If I need to modify some screens on the running HMI (Human-Machine Interface) that is connected to the PLC (Programmable Logic Controller) and currently operational, what steps should I take? Do I need to disconnect the HMI from the PLC, or can I connect it directly?" It's important to note that if you're operating a live plant, it’s advisable to disconnect the HMI before making any changes to avoid any unintended commands during initialization. However, in your specific situation, since it seems to be test equipment, disconnecting may not be necessary.
It sounds like you're dealing with a frustrating situation! Given that the connection was initially established, I would suggest double-checking the communication setup in your FactoryTalk View ME settings after making edits. It's possible that the tags in the application didn't link correctly following the changes, and that might be causing the errors you're seeing. Also, ensure that the IP addresses and subnet masks are correctly configured on both devices—sometimes, a single digit can throw things off. If all else fails, rebooting the switch might help reset any temporary glitches that could be impacting the connection. Good luck!
Hi there! It sounds like you're dealing with a tricky communication issue between your PLC and PanelView. Since everything was working initially and you can still ping both devices, it could be related to the configuration settings in FactoryTalk View after your last edits. I’d recommend double-checking the communication settings, especially the RSLinx Enterprise configuration for gaps or mismatches in the IP addresses or driver settings. Also, ensure that the application you downloaded to the PanelView is properly linked to the PLC tags, as any tag name changes or deletions could cause those errors. It might be worth going through the communication troubleshooting steps in the documentation too—sometimes a fresh perspective helps spot the problem. 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.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.