I am using a PowerFlex 525 to control an agitator motor and need it to automatically restart after power or communication loss. The power restart is working well with a First Scan latch cycling the Start command until the drives are at reference. However, I am facing an issue with the Fault side. By incorporating the Input XIO PF_525:I.Faulted in an Interlock rung, the signal is dropping out and coming back up on Power Up. Is this a common issue with this drive input? Despite trying to prevent the bit from latching on first scan, the restart still occurs on power up. Removing the PF_525:I.Faulted bit from the interlock prevents the machine from starting unless the First Scan logic is running. Parameters A541 and A543 on the drive have also been checked and found to be disabled.
It is not advisable to start an agitator motor after a power cycle or fault without user input, such as using a reset/start pushbutton. Implementing an audible alarm to alert operators of power cycle or fault can help ensure safety by prompting them to start the motor in the usual manner.
SCADA expert Joe advised against starting an agitator motor without user input like a reset/start pushbutton after a power cycle or fault. He recommended using an audible alarm to alert operators of power issues and having them start the motor manually for safety. Can anyone explain why the Faulted XIO from the drive was cycling the input after a power loss?
It sounds like you're dealing with a tricky situation! The behavior of the PF_525:I.Faulted input during power-up is something that can catch many users off guard. It’s not uncommon for certain drives to briefly drop their fault signals on startup, which can inadvertently trigger unwanted restart sequences. One approach you might consider is implementing a delay or debounce timer for that interlock signal after power restoration, which can help ensure the drive is truly ready before allowing the restart logic to engage. Additionally, double-check any configuration settings related to how the drive handles fault recovery and startup behavior, just to be sure there aren’t any hidden settings affecting your setup. Hope this helps you get past the hurdle!
It sounds like you're dealing with a tricky situation! The behavior you're describing with the fault signal dropping and the interlock issue during power-up can definitely be a bit frustrating. One thing you could try is to add a delay to the input reading the fault signal; sometimes adding a small timer can help filter out transient issues during startup. Additionally, if your application allows for it, consider using a memory bit that locks the fault condition until your First Scan logic has fully initialized and established control. That should help with ensuring the drive doesn’t inadvertently restart until it’s fully ready. Have you also checked if there’s any specific setting in the drive that addresses fault behavior during power recovery?
It sounds like you're on the right track but hitting a few snags with the Fault input behavior. It's not uncommon for certain drives to exhibit this kind of behavior, especially with how they handle faults upon power restoration. One thing you might try is ensuring that the interlock isn't set to allow the restart until all conditions are met, regardless of the fault detection on startup. Also, double-check any timing or debounce parameters that could affect how quickly the drive signals state changes right after power-up. Sometimes manually resetting the fault status before re-initiating the interlock might help stabilize the behavior. If you've verified all your parameters and you're still having issues, it might be worth reaching out to Rockwell support; they might have deeper insights or experiences with similar setups. 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: Answer: The PF_525:I.Faulted signal behavior on Power Up could be due to how it is integrated into the Interlock rung or potential settings within the drive itself.
Answer: Answer: To prevent the PF_525:I.Faulted signal from triggering a restart on power up, you may need to review the interlock logic and ensure it is configured correctly for the desired behavior.
Answer: Answer: Removing the PF_525:I.Faulted signal from the interlock may impact the machine's startup sequence, indicating a dependency on specific logic conditions for proper operation.
Answer: Answer: Checking and adjusting parameters such as A541 and A543 on the PowerFlex 525 drive might be necessary to resolve the restart issue and ensure desired restart behavior in case of power loss or communication dropout.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.