As a self-taught individual, I appreciate your patience as I share my technical issue. Currently, I'm working with an archived program file for a PVP6, which I'm accessing through FT ME version 7. My primary goal is to update the IP address within the program's communication settings—this is the sole modification I am implementing. After making this change, I generate a new runtime file and upload it to the touchscreen. This process has been straightforward, and I have successfully completed it for several other touchscreens in the facility. However, I've encountered a problem with one specific touchscreen that fails to communicate after I upload the updated version. Do you have any insights on why this issue might be occurring? I would greatly appreciate any guidance or suggestions. Thank you in advance for your assistance. — Dana
Welcome to our discussion forum! Are you experiencing an issue where the HMI runs the application but fails to display any values from the PLC? If the application isn't running at all, it might be due to creating the runtime file in an incompatible version. Have you ensured that you updated the IP address in both the design and runtime sections of the communication settings? Additionally, did you instruct the transfer utility (or the HMI itself) to overwrite the existing RSLinx Enterprise configuration on the HMI with the new one from your updated file? I suspect this might be the root cause. The HMI can be set up to execute an application while using its default RSLinx Enterprise configuration instead of the one outlined in the .mer file. Therefore, if you've adjusted the settings in the .mer file, but the PanelView Plus (PVP) isn't pulling the IP address information from there, it won't function correctly.
Thank you, ASF. Yes, indeed! The program successfully runs on my end. I have updated both the design and runtime parameters, and I confirmed that the application is set to overwrite previous data. While the application loads without issue, it displays all output as errors. I'm currently at a loss and suspect it's a straightforward mistake that I’m not seeing. Any insights would be greatly appreciated!
Ensure the design communications are functioning properly by utilizing the test application button. Alternatively, select a screen and click the PLAY button to initiate the process. You will receive diagnostic information in the lower window section.
I will prioritize checking that first thing tomorrow morning.
Additionally, verify the RSLinx Enterprise setup present on the PVP itself to ensure that all configurations have been accurately transferred. Furthermore, are you able to ping both the PLC and the HMI devices from your laptop?
Hey Dana, it sounds like you've got a solid process, but I can understand how frustrating that one touchscreen must be! Have you checked if the problematic touchscreen has any unique settings or restrictions compared to the others? Sometimes, a device might have a static IP configuration or specific network settings that can conflict with your updates. It could also be worth double-checking the firmware version on that device to ensure it's compatible with the new runtime file. If everything seems right, try rebooting the touchscreen after the upload; sometimes a fresh start clears up communication hiccups. Good luck, and let us know how it goes!
Hi Dana! It sounds like you're doing a great job navigating those updates. Have you double-checked the communication settings on that specific touchscreen after uploading the new runtime file? Sometimes, it helps to ensure that the touchscreen's firmware is up to date or to verify that there aren’t any conflicting settings or cached data that might be causing the communication failure. Additionally, consider doing a power cycle on both the touchscreen and any associated hardware to see if that resolves the 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: - IP Address Conflict: Ensure that the new IP address does not conflict with other devices on the network. - Subnet Mask Mismatch: Verify that the subnet mask is correctly configured to allow communication within the network. - Gateway Issues: Check that the gateway address is correct and accessible. - Faulty Ethernet Cable or Port: Inspect the physical connection for any damage or loose connections. - Firewall or Security Settings: Review any firewall or security settings that might be blocking communication.
Answer: - Check Device Settings: Access the network settings on the touchscreen to ensure the IP address, subnet mask, and gateway are correct. - Ping Test: Perform a ping test from a computer or another device on the same network to see if the PVP6 is reachable. - Network Tools: Use network diagnostic tools to scan for devices on the network and confirm the PVP6 is visible.
Answer: 1. Double-check
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.