Troubleshooting PowerFlex 755 Drives: Resolving F926 Error Code and Optimizing Network Setup

Question:

I am encountering issues with PowerFlex 755 drives in my small network, specifically the F926 error code related to network traffic overload on the Main Control Board. To address this, Rockwell suggests using an ENETR card to prevent shutdowns. Moving forward, I am exploring the best way to configure PLCs/Drives/Devices to avoid similar problems. My network setup includes an FTView SE Network Distributed with servers, clients, and various devices, all connected via Moxa Managed switches on a single VLAN. As I seek solutions, questions arise: How to determine the RPI for devices, identify broadcast messaging sources, optimize switch settings for traffic, and address any overlooked factors.

Top Replies

While necroposting is generally frowned upon, I am currently experiencing a similar issue with a PowerFlex 755 and am seeking help from the collective wisdom of the internet. Are there any suggested methods for monitoring this issue or identifying the source of unwanted broadcast messages?

Rockwell may be hesitant to acknowledge it, but the issue lies within firmware version 16. Thus, I have taken the initiative to downgrade all of my PF755s to revision 14.x. This adjustment has successfully resolved the issue in all drives that have undergone the fix.

It shouldn't have come as a surprise. Strangely, after disconnecting the cabinet with PLC, 755, and Siemens HMI from the network, the faults ceased. We reconnected it a week later for monitoring purposes, and the drive has been fault-free ever since. It is still running on V16 firmware.

During a troubleshooting session, JankyPLC discovered that by disconnecting their cabinet with PLC, 755, and Siemens HMI from the network, they were able to stop faults from occurring. After reconnecting the cabinet a week later to monitor traffic, they observed that the drive had not faulted once since then. Despite still being on V16, they found that reducing network traffic could help V16s operate smoothly. However, since this was not feasible for their situation, they ultimately had to downgrade.

After being stable for a week, V16 experienced faults when connected to the building network with drive and PLC. Despite a thorough packet capture analysis revealing no clear issues, the system went down inexplicably. The drive was reverted back to V14 to rectify the problem. Time will tell if this adjustment proves effective in resolving the issues.

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

To add a comment, please sign in or register if you haven't already..   

Frequently Asked Questions (FAQ)

FAQ: 1. What is the F926 error code on PowerFlex 755 drives, and how can it be resolved?

Answer: Answer: The F926 error code indicates network traffic overload on the Main Control Board. To resolve this issue, Rockwell suggests using an ENETR card to prevent shutdowns.

FAQ: 2. How can I configure PLCs/Drives/Devices to prevent network traffic overload issues like the F926 error on PowerFlex 755 drives?

Answer: Answer: Configuring devices with appropriate RPI (Requested Packet Interval), identifying broadcast messaging sources, optimizing switch settings for traffic, and considering other factors can help avoid network traffic overload issues.

FAQ: 3. What are some tips for optimizing network setup to prevent network traffic overload on devices like PowerFlex 755 drives?

Answer: Answer: Determining the RPI for devices, identifying and managing broadcast messaging sources, optimizing switch settings for traffic flow, and ensuring no factors are overlooked are essential steps to optimize the network setup and prevent issues.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  â†’