Sign in to follow this  
Followers 0
phuz

Network Faults and Idle Packets

5 posts in this topic

We have a Powerflex 755 and Powerflex 4 on the same network. Our ControlLogix and Panelview are also on this network. Everything is connected to an 8-port Stratix switch. Every so often (about 30-60 minutes if I had to guess), we will get a "Net Idle Fault" on the Powerflex 755 and F071 Comm. Fault on the Powerflex 4. We have no problem communicating with the drives. Other than checking the terminations of the patch cables, what else can we look at? EDIT: This is happening every time we do a download to the ControlLogix Edited by phuz

Share this post


Link to post
Share on other sites
Thanks for posting the additional information: the fact that this happens when you're downloading to the ControlLogix is normal default behavior. You can configure a drive's behavior when the network connection goes into Idle or Fault mode. The default behavior is to fault in both states, so when you download to the ControlLogix the I/O connections are broken and the drive faults. You see a "net idle" fault instead of a "net loss" fault because the controller goes into Program Mode (the connections go Idle) before breaking the connection during download. You can configure most drives to hold last state or just to Stop (rather than Faulting) when the network connection goes idle or faults. I almost always configure the drives to Stop. It's a parameter in the PowerFlex comm module on the 755, and part of the comms parameter group on the PowerFlex 4. There are separate parameters for Idle mode and Fault mode.

Share this post


Link to post
Share on other sites

What is the parrametters to change the settings on the powerflex 753....? 

Share this post


Link to post
Share on other sites

Cause ive been having a net idle problem past few days and want to over ride it to stop so we dont need to come to the panel and reset and can just reset it on the scada 

Share this post


Link to post
Share on other sites

We have a few drives (PowerFlex 700) that are critical to keep running so we have them configured to "hold last" on network loss.  Their run/start/stop commands are hard wired.  The only thing we're doing with the network is reading back the speed and fault/diagnostic information.  Another drive in the same system also receives its speed reference via network, but nothing else.  In this system, it made sense to have it "hold last".  We have some 525s on another machine that receive all of their commands via the network, including run/stop.  We left them in the default state, "fault".  If we were to change that, we would set them to "Stop".

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0