The PowerFlex 527 Network Safety Drive experienced a malfunction with an internal fault SOS code that triggered an alarm. Unable to manually clear the fault or resolve it through logic, the module was replaced and the IP configuration was updated, resulting in successful downloading with the new drive. Are the faults being caused by hardware issues? This issue has been observed in multiple drives with the same problem.
I have yet to implement networked safety on PowerFlex drives, but I have a few important questions to consider: 1) Is this a new installation, or is it an existing system that used to be operational? 2) With networked safety in place, is the safety PLC connected and functioning properly? 3) If the safety PLC is connected, is there confirmation that it is successfully communicating with the drive? 4) Once communication is established, is the safety PLC sending the necessary "safety ok" signal? 5) When utilizing CIP Safety over Ethernet/IP, is it necessary to have the STO jumper installed on the drive? The manual for this specific drive may provide the answer.
Hello Joseph, I have an existing application running on a Safety PLC that is currently online and connected to a drive. However, I am experiencing a safety fault issue where the drive automatically inhibits and cannot be reset. Are there any options available for performing a factory reset? I attempted to utilize the Drive Executive application tool to connect to the drive, and while it was able to identify the drive's presence, I was unable to establish a connection.
The drives in question are not officially endorsed by Drive Executive. It is recommended to use Connected Components Workbench (CCW) instead. Are you equipped with the necessary safety PLC access?
SGPeruma reported an issue with the PowerFlex 527 Network-based safety drive displaying an internal fault SOS Code. Despite attempts to manually clear the fault or using logic, the issue persisted. After changing the module and configuring the IP, the fault was successfully cleared. However, similar problems have been encountered in three different drives. The specific fault code is actually S05, indicating a safe torque off fault. It is important to determine whether the drive is using CIP safety or wired safety with red terminals. If using red jumpers, check the safety circuit and ensure the terminals are receiving 24V. For CIP safety, double-check that the jumpers are removed as leaving them in can cause issues. It is essential to verify the safety program's integrity as it relies on internal logic for safety.
SGPeruma inquired about a possible solution for a safety PLC issue causing the drive to be unable to reset despite being online. Asking if a factory reset is possible and attempting to use the Drive Executive application tool, but encountering connectivity issues. joseph_e2 suggested using Connected Components Workbench (CCW) instead of Drive Executive for better compatibility. It was also mentioned that the drives are typically programmed directly in Studio 5000 with ControlLogix/CompactLogix, rather than with CCW or Drive Executive.
While it's possible that hardware issues are causing the faults you're observing, it also could be a result of a software glitch or a compatibility issue. Sometimes it's a misconfiguration or even an external interference (like power surges or environmental factors). Did you notice any patterns in the faults you've encountered such as during specific operations or conditions? Also, it might be beneficial to check if these units are running on the latest firmware version. Don't rule out the option to reach out to the manufacturer's technical support for help, they often deal with known issues and might be able to assist more quickly.
It certainly seems like a hardware issue if you've replaced multiple drives with the same fault. However, do consider firmware issues as well. Perhaps the modules are running on an outdated firmware version, causing system malfunction. I suggest reaching out to Rockwell Automation's support or check for any firmware updates to ensure your drives operate at their fullest potential. If the problem persists, then it's likely a hardware fault. Remember that environmental factors like dust, heat, and vibration can also cause repeated failures.
✅ 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: Internal faults like SOS codes in PowerFlex 527 drives can be caused by various factors, including hardware issues, software glitches, or configuration errors.
Answer: If manual clearing or logic-based resolutions don't work, replacing the module and updating the IP configuration, as done in the discussed case, can sometimes resolve the issue.
Answer: If the problem persists across multiple drives, it may suggest a potential common underlying cause, which could be related to hardware, software compatibility, or environmental factors.
Answer: While module replacement and reconfiguration can often solve internal faults, there might be instances where the issue reoccurs due to persistent hardware issues or compatibility issues. Regular monitoring and maintenance are advisable in such cases.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.