Hello, I am seeking assistance regarding the Kinetix 5500 S33 Fault. I have a group of three drives configured as follows: 2198-H025-ERS2 Shared AC/DC, 2198-H008-ERS2 Shared DC, and 2198-H008-ERS2 Shared DC. All drives are set to Bus Regulator Action: Shunt Regulator Internal within Group 1. Drive 1 is running FW 7.014 while the two H008 drives are on FW 5.3.7. I am using Studio5000 Rev28.011. The incoming AC voltage measures at a satisfactory 450V, within the 460-3 Phase setup. However, all three drives fault with S33 when the Bus Regulator Action is set to Shunt Regulator Internal for all drives. Interestingly, only the H008 drives fault when this setting is applied to the H025 drive. Any assistance would be greatly appreciated. Thank you, James.
The problem with the DCBusUnderVoltageFactoryLimit tripping was caused by a safety scanner activating, resulting in the contactor in front of the Leading drive dropping out. The intermittent issue was due to the bleed off time of the Kinetix capacitors. The third-party code I am utilizing did not monitor the fault or reset it after the DCBus recharged. This situation reinforces the importance of monitoring and addressing faults promptly. Remember to always track your faults to prevent unexpected shutdowns.
The top-mounted STO connector on these drives is likely the recommended method for safety wiring, as opposed to placing the contactor in front of the drive. This configuration ensures optimal safety measures are in place for operation.
Shilok noted that these drives feature a STO connector on top, making it the preferred method for safety wiring (rather than placing a contactor in front of the leading drive). These drives are ERS2 models, equipped with CIP STO over Ethernet for added safety measures. There is no hardwired STO present in these drives. Thank you for the suggestion.
When it comes to safety PLCs that support CIP safety over Ethernet, utilizing the STO function is a more reliable option compared to dropping line power. While I haven't had the chance to try out the ERS2 drives yet, I'm curious if they only offer CIP STO over Ethernet without the possibility of hard wiring it. Dropping line power can put a strain on the power stage of a drive, potentially leading to premature failure of the bus caps or inrush circuits. The STO function on its own is generally effective up to PLd or CAT 3 safety levels. For higher safety requirements, some users incorporate load side contactors with a short delay before opening to ensure the drive's output stage stops conducting first.
Joseph_e2 mentioned that utilizing the STO function is superior to disconnecting line power if your safety PLC supports CIP safety over Ethernet. While he has not yet worked with ERS2 drives, he inquired whether they exclusively offer CIP STO over Ethernet without the possibility of hard wiring it. Disconnecting line power can strain a drive's power stage, potentially leading to premature failures of the bus caps or inrush circuits. The STO function alone typically meets standards up to PLd or CAT 3, with some instances requiring load side contactors with a short delay to ensure the drive's output stage ceases conducting first. While agreeing on the importance of an in-line contactor in the power supply, Joseph_e2 noted the limitations when integrating into third-party systems where the original machine design has already been established. Despite personal preferences for a different design approach, his company is adapting the existing process in the opposite direction. Addressing his query, ERS2 drives do support STO over Ethernet and can be linked to Guardlogix processors. The valuable insights provided by others have been greatly appreciated.
Hi James, the S33 Fault you're encountering is often indicative of high bus voltage. Though your incoming AC voltage seems within range, you might want to check for any voltage spikes during operation that might be causing the fault. Moreover, you mentioned you're using different firmware versions for the H025 and H008 drives. It's generally advisable to keep all drives on the same firmware version for better synchronization and to prevent discrepancies that could provoke errors. Try updating your H008 drives to match the H025's firmware and see if that resolves the issue.
Hi James, I've encountered similar issues with this set up before. The S33 fault is typically due to an overvoltage problem on the DC bus, which can be triggered by a quick deceleration or the use of large loads. I'd suggest checking the DC bus voltage of each drive when they're running to ensure they're within the allowed range. Another possibility might be inconsistency in the firmware versions between drives. Try updating all of your drives to the latest firmware version, maintaining uniformity across the group. You might also want to look at your regen resistors and how they are configured, as incorrect settings can trigger this fault. Your setup seems to be tad complex, so it's possible there is some interplay between these issues. Hope this helps!
Hey James, it's quite a complex configuration you're dealing with there. The issue might be related to firmware inconsistencies between your drives. One thing I would try is to ensure that all drives are running the same firmware version. You might also want to check on your bus configuration and make sure each of your drives is correctly set within their respective function. And sometimes, it might just come to down to a simple power cycle. Give these a try and see if the S33 fault clears. Hope this helps!
Hi James, from your description, it seems like the issue could be related to a firmware disparity or setting inconsistency among the drives. You mentioned Drive 1 is running on a different firmware (FW 7.014) compared to the H008 drives (FW 5.3.7). Try updating the H008 drives to the same firmware as the H025 drive to ensure compatibility. Also, the Bus Regulator setting could be causing this issue - if different drives require different settings for optimal operation, they may fault when a universal setting is applied. Analyze each drive's requirement and set the Bus Regulator Action accordingly. Always remember to back up your configurations before making any changes. Good luck!
✅ 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 Kinetix 5500 S33 Fault typically indicates a DC Bus Under Voltage issue within the drive system.
Answer: - The configuration involves three drives: 2198-H025-ERS2 Shared AC/DC, 2198-H008-ERS2 Shared DC, and 2198-H008-ERS2 Shared DC.
Answer: - The Bus Regulator Action is set to Shunt Regulator Internal for all drives within Group 1.
Answer: - Drive 1 is running FW 7.014, while the two H008 drives are on FW 5.3.7.
Answer: - Studio5000 Rev28.011 is being used for programming the drives.
Answer: - The incoming AC voltage measures at a satisfactory 450V, within the 460-3 Phase setup.
Answer: - The drives fault with S33 when the Bus Regulator Action is set to Shunt Regulator Internal due to potential issues related to this configuration.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.