My current set-up utilizes an L83E system with mainly class 1 communication, along with approximately 30 HMI's that consist of basic IO buttons. Despite the straightforward nature of the HMI's, I am experiencing high levels of class 3 messaging on the PLC, reaching close to 100%. The customer's network topography appears to be messy, possibly due to the presence of loops causing such issues. Are there any additional steps I should take to address this issue? Are there any resources available to help identify the source of the network traffic congestion?
Which HMI brand should you choose? All HMI systems utilize class 3 messages to retrieve tag data from the PLC.
Inquiring about the brand of the HMI being used is crucial as all HMI systems rely on class 3 messages for retrieving tag data from the PLC. The Panelview interface is commonly used, but excessive bandwidth usage may be unexpected.
To optimize network performance and observe load, I recommend starting by disconnecting each HMI from the network individually and monitoring the impact. Then, reconnect them one by one to see if the load increases in a linear manner and to what extent. It's important to also consider the involvement of a SCADA system during this process.
Having 30 HMIs can significantly impact performance, especially considering the volume of tags and scan rate. It is crucial to consider the model of the PanelView being used, as older models may struggle with handling a high number of requests effectively.
Given that the high levels of class 3 messaging on the PLC seem to be causing some stress to your L83E system, double-checking and possibly revising your network infrastructure may work wonders. Ensuring that the communication paths are optimally configured and eliminating any redundancy or loops hampers unnecessary network traffic congestion. To trace the source of the network traffic, you could consider employing network monitoring tools like WireShark or PRTG. These tools could provide detailed insights into your network traffic and enable you to identify any data bottlenecks. Plus, they can be a great help when it comes to debugging and performing network audits. Remember that it's always essential to balance your network load to ensure smooth and efficient system operation.
Given your situation, one potential way to troubleshoot this network congestion issue might be to isolate segments of the network to identify potential problem areas. You can systematically disconnect different HMIs or other parts of the network topography and monitor the messaging on the PLC to pinpoint if a particular section is causing the high levels of class 3 messaging. Tools like Wireshark could be incredibly useful in capturing and analyzing your network traffic, helping to identify possible bottlenecks or misconfigured devices. Using Ethernet/IP CIP messaging might also reduce the amount of network traffic, thus potentially alleviating your issue. Best of luck in resolving this!
✅ 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: - The high levels of class 3 messaging could be due to network congestion caused by loops in the network topography.
Answer: - To address this issue, you may need to optimize the network topography to eliminate loops and reduce network traffic congestion.
Answer: - You can use network monitoring tools to analyze network traffic and identify sources of congestion, such as excessive class 3 messaging in your case.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.