Hello, I am in the process of setting up a Prosoft AN-X4 to enhance communication for a new PanelView Plus 7. Currently, we have a communication setup from a SLC-500 through DH+ to a PanelView 600C terminal, and I am looking to upgrade to a newer HMI with Ethernet capability using the Prosoft unit. I am facing challenges in configuring the communication path for the AN-X4 in FactoryTalk View for the runtime application. Any advice on how to successfully configure this setup would be greatly appreciated.
I utilize a few of these devices for Ethernet to DeviceNet Plus communication via radio frequency. While I lack knowledge about FactoryTalk View, I observed that the endpoint appears as a pathway in RSLinx, much like any other device once configured.
After testing FactoryTalk Linx on DH+ networks, I found that its subscription-based nature can lead to overwhelming data traffic and lack of control over update frequencies. When I tried out the new functionality in V12, I ran into issues with my test program running on my laptop using FTView SE with FactoryTalk Linx as the OPC Server. Commands sent to the PLC through the test screens caused the PLC to stop responding to both my laptop and the PanelView Plus 7 HMI. Switching to RSLinx as the OPC server for FTView SE allowed me to manage packet transmission and tag updates effectively. Rockwell suggests limiting packets to no more than 10 at once on DH+ networks and creating multiple topics for different tag update speeds. The PanelView Plus 7 I installed had fewer issues with this problem, possibly due to differences in firmware compared to Windows 10. In my opinion, using a Panel PC with FTView SE and RSLinx OEM/Single Node is the best solution if you are keeping the 5/04 in place. Otherwise, consider upgrading to a PanelView Plus 7 with a 5/05 processor or migrating to compactlogix for smoother operations.
During my desk testing with a SLC 5/04 connected to the Prosoft AN-X4 and then to the PanelView Plus 7, I noticed a slow response time for the numeric display, taking around 1-3 seconds to update the screen. The communication setup is currently configured to communicate with the SLC simulated in FactoryTalk Linx within the runtime application. I am using FactoryTalk View ME for this setup.
While testing on my desk with a SLC 5/04 connected to a ProSoft AN-X4 and then to a PanelView Plus 7, I noticed that the response time for the numeric display was quite slow, taking about 1-3 seconds to update the screen. I am currently using FactoryTalk View ME, with communications set up to go to the SLC simulated in FactoryTalk Linx in the runtime application. In my experience, older technologies such as RSLinx, RSView32, and PanelView/PV+/PV+6 tend to outperform any migration efforts. With the old tech, you had full control over update times for each tag and were directly connected to the network. On the other hand, with newer technology, you are dependent on registry keys in FTLinx and firmware of the new HMI and gateways. It is advisable to convert the PLC to an Ethernet-based processor for optimal performance with FTView. While I have witnessed good performance with the ProSoft gateway over DH+ networks and excellent performance over RIO networks, there is a greater risk of issues arising, especially with firmware that is beyond your control. I had a positive experience with a technician from Tech Connect in the past and would recommend reaching out to them for additional tips and support.
RedSoxFan3 mentioned that the older technology (RSLinx, RSView32, PanelView/PV+/PV+6) outperforms any migration process. With the old tech, you had complete control over update times for each tag and direct network connectivity. However, with the new technology, you are reliant on registry keys in FTLinx and the firmware of the new HMI and gateways. It is suggested to convert the PLC to an Ethernet-based processor for better performance in FTView. Although good performance has been observed with the Prosoft gateway over DH+ networks and excellent performance over RIO networks, there is a higher risk of things going wrong, particularly with firmware you cannot control. Contacting Tech Connect may provide more insights and tips for improving performance. Testing the new PanelView in the field with the Prosoft gateway will help determine if there are any improvements in response times. It may be beneficial to contact Rockwell regarding intentions to upgrade, and an update will be provided on the outcome.
Hey there, it sounds like a complex setup you're working on, but I believe you're on the right track with upgrading to Ethernet capabilities. When setting up your Prosoft AN-X4, ensure that the IP address is set and matches with your HMI device. In FactoryTalk View, under the 'communications' setup, set up the 'device shortcuts' to match the name for the HMI display on the AN-X4. Remember to communicate through the Bridge module and not directly with the PLC. Testing ping from your PC to the Prosoft unit is a great way to troubleshoot connection issues. Also, don't forget to download your configuration into the gateway after you've made changes, it can be easy to overlook! Good luck with your project!
Hi there! I've worked with Prosoft AN-X4 in the past and I understand the type of challenges you might be facing. One important thing to remember is to fully understand the communication hierarchy of the system - the AN-X4 is essentially a bridge converting the DH+ signals into Ethernet/IP. To configure the communication path in FactoryTalk View, you'll want to specify the AN-X4 gateway as a device on your Ethernet network first. Depending on the specifics of your system, you might need to set up the SLC-500, the PanelView terminal, and the AN-X4 in your RSWho configurations, each with their proper addresses. Make sure that the Ethernet side of the AN-X4's settings align with the rest of your Ethernet network as any discrepancies can lead to communication issues. Hope this initial advice helps a bit, and don't hesitate to ask if you need more details or specific instructions!
Hi there, I'd first ensure that your Prosoft unit is configured to correctly communicate on your DH+ network. Then, in FactoryTalk View, your communication setup should be similar to your current setup but instead pointed at the ethernet path of the Prosoft unit. Now, here's the tricky part - since FT View doesn't support AN-X series right away, you might need to create a 'shortcut' pathway under the RSLinx Enterprise configuration. Just point the shortcut to the DH+ path through the AN-X4. It might take a few attempts to fine-tune the settings. Let me know how it goes!
✅ 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. How can I enhance communication for my PanelView Plus 7 using a Prosoft AN-X4 DH+ to Ethernet Gateway? - To enhance communication for your PanelView Plus 7, you can set up a Prosoft AN-X4 DH+ to Ethernet Gateway. This device will allow you to bridge the communication between your SLC-500 through DH+ to the newer HMI with Ethernet capability.
Answer: - Challenges in configuring the Prosoft AN-X4 in FactoryTalk View for a runtime application may include setting up the correct communication path, ensuring compatibility between devices, and configuring network settings properly. It is important to follow the manufacturer's guidelines and seek assistance if needed.
Answer: - When configuring the Prosoft AN-X4 for communication with the PanelView Plus 7, ensure that you have the necessary documentation and software tools to set up the communication path correctly. Follow the step-by-step instructions provided by Prosoft and make sure to test the setup thoroughly before deploying it in a production environment.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.