QUOTE (Rod_Hackney @ Oct 21 2009, 02:00 PM)

We are currently using controlnet to network our drives to Controllogix PLC systems. I had a vendor wanting to use Ethernet/IP for a network of VFDs on a Controllogix project. It would be a dedicated network. I wanted to get the opinions on this issue. Thanks for your input in advance.
If it's fans and pumps and the like, hands down, go Ethernet/IP. Watch out if you are using 20-COMM-E's or 22-COMM-E's. They are very sensitive to packets per second limitations (very limited processors). If you overshoot, you lose control over the drive. I just put in an application this way and it works great.
If you are doing motion control, "it depends". Ethernet can certainly be used. The problem with Ethernet lies in it's flexibility. You have lots of flexibility and control over your network architecture, much more so than Controlnet. The underlying architecture is also capable of much higher speeds. The flexibility is also the problem...you HAVE to do some planning and design up front if you are going to have a successful system. If the goal is to use a motion controller where you are sending commands over Ethernet, again, within reason, no problem.
However, if the drive/motion control path IS Ethernet, this is where it gets critical. Buy a copy of RSNetworx for Ethernet/IP just like with Controlnet because the big key here is planning. Make sure to install managed industrial grade switches (Cisco/AB is NOT an industrial grade switch, it arbitrarily locks up ports and requires administrative access if there is any electrical interference). Make sure to maintain an IGMP querier possibly with backup queriers. Use QoS, maximum packet rate controls, etc., to put gaurantees on your network availability. This is true even with a dedicated network. Use a switch capable of PTP (IEEE 1588). Do it all correctly and it will be faster and cheaper than Controlnet or Devicenet. Do it wrong, disaster.