Our AB Panel View HMI 7 Plus Standard is facing an issue where it cannot be pinged through the CMD prompt, while all other devices in the series can be successfully pinged. The IP address is displayed on the screen and in the RS Logix Network, but the HMI device is not being detected. DHCP is turned off and the IP, subnet, and gateway are correctly entered. If you know of any settings to enable HMI IP ping access or how to resolve this issue, please refer to the screenshot below: [Include screenshot image here] The IP detection results are as follows: - 10.194.68.67 PLC: detected - 10.194.68.69 HMI: not detected - 10.194.68.72 Valve bank: detected If you have any insights or solutions to this problem, please let us know. Thank you.
Are you in need of more information about setting up a new HMI system or troubleshooting an existing one that has lost communication? Have you attempted a direct connection between your workstation and the HMI, or are you utilizing a managed switch?
What is the physical connection between the HMI and your network? How about the PLC and your Laptop? Are you able to view the PanelView in RSLinx? Do you see a link or activity light on the PanelView Plus Ethernet port?
When setting up a new Series B HMI, the default setting disables the ping response, which prevents pinging to a Panelview Plus 7 HMI. However, FT Linx is still functional for communication. To enable the ping response on a Panelview Plus Series B HMI, refer to page 151 of the user manual, which can be found at the following link: https://literature.rockwellautomation.com/idc/groups/literature/documents/um/2711p-um008_-en-p.pdf. This will allow for ICMP (Ping) communication to the HMI.
If you have the PanelView Plus 7 (PVP7) in its "Standard" version, there is currently no option to toggle ping support on or off. However, this feature may be added in the future. The device is powered by the Windows CE 6.0 operating system. There is also a "Performance" version of the PVP7. Starting with the Series B release, this version utilizes Windows IOT as its base operating system, specifically Windows 10 IOT Core. Unlike the Standard version, the "Performance" model does offer the option to enable or disable ping support, with support disabled by default. If you are using the Performance edition, you can follow the instructions provided in a previous post to configure ping support. For users of the Standard edition, if ping support is not working, the issue may lie in the switch settings. It is possible that Rockwell will release an update in the future to switch the PanelView Standard terminals to Windows IOT, like the Performance models, but for now, they still run on Windows CE.
Thank you for the correction OG. It seems like my reading skills are failing me today.
It seems like you've checked all the obvious settings, so my first suggestion would be to consider if it's a firewall issue. Some systems have specific configurations that could prevent ICMP requests, which are used for pinging. Besides, you can also try doing a factory reset on the HMI and reprogramming it with the correct settings. Another possibility could be with the Ethernet cable or port you're using. Try switching out the cable or using a different port to rule out any hardware issues. Keep us updated on your progress!
It sounds like an uncommon issue you're experiencing. Usually, a successful ping to other devices on the same network indicates a general network integrity. As all other devices are pinged successfully and the IP details are correctly entered, it's possible that there might be a firewall issue on your HMI blocking ICMP requests. I recommend checking the settings on the HMI to see if any firewall or security settings are enabled that could be blocking incoming pings. Also, try resetting the HMI and see if that makes a difference. Sometimes, a simple reset can do wonders.
This issue might be due to the Windows Firewall settings on your system, which could possibly be blocking the ICMP requests needed for pinging. Try allowing ICMP Echo Requests through Firewall settings - this is the protocol used by the 'ping' command. If this doesn't resolve the issue, consider checking if there's a firmware update for the HMI as sometimes, undetected bugs might prevent proper communication. Don't forget to cross-validate the IP address and ensure there are no conflicting IP addresses on your network as well. You might also want to verify if the problem persists on a different computer or network to help isolate the issue to either the HMI or your current network setup. Good luck!
It sounds like you’ve done some good troubleshooting already! Since the HMI isn’t responding to pings while other devices are fine, I’d suggest checking a couple of things: first, make sure that there are no firewall settings on the HMI blocking ICMP requests, as it might be a network configuration issue. Additionally, if possible, try connecting the HMI directly to your PC with a crossover cable to see if that allows for detection, which may help identify whether it’s a network issue or something with the HMI itself. Sometimes a simple reboot can also resolve these connectivity problems, so give that a shot if you haven't already!
It sounds like you've done a great job troubleshooting the basics! One consideration might be to double-check the firewall settings on your network and on the HMI itself, as sometimes they can block ICMP packets used for pinging. Additionally, ensure that there's no IP conflict with another device on the network. If everything else seems right, you could also try rebooting the HMI or resetting it to factory settings to see if that helps restore connectivity. Good luck!
It sounds like you're dealing with a frustrating connectivity issue! Since DHCP is disabled and the IP settings appear correct, I would check a couple of things: first, ensure that there are no firewall settings on your network that might be blocking ICMP packets, which are used for pinging. Also, verify if your HMI has any specific network settings that could restrict access, like an application-level firewall or settings related to its IP stack. Sometimes, rebooting the device can also help clear up any temporary network quirks. If you haven't already, trying a different network cable or port might also rule out any physical layer issues. Hope you find a solution 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: There could be various reasons for this issue, such as incorrect network settings, firewall restrictions, or HMI-specific configurations.
Answer: Answer: You can start troubleshooting by verifying the IP address, subnet mask, and gateway configuration on the HMI device, checking for any firewall restrictions, and ensuring that the network settings are correctly configured.
Answer: Answer: To enable HMI IP ping access, you may need to check the network settings, ensure that the correct IP address is assigned, and troubleshoot any connectivity issues that may be preventing the device from being detected on the network.
Answer: Answer: You can try resetting the network settings on the HMI device, checking for any conflicting IP addresses, verifying the network configuration with the manufacturer's guidelines, and consulting technical support for further assistance.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.