curlyandshemp
Lifetime Supporting Member
We are currently in the design phase of a fairly large project involving Controlnet, Ethernet and Devicenet. This projcet will have 4 Contrologix PACs in one central rack. There are 4 large Devicenet MCCs , each so large that there are 3 Devicenet segements in each MCC. The MCCs are where I am getting stuck. I have used various scenerious using Integrated Architecture Builder, and hit road blocks such as exceeded bandwidth , connections and rack power supply capacity.
Due to the nature of this project i will have to message to the PAC that is controlling the MCCs via devicenet using produced consumed tags there are about 150 motors, mainly PF70s. Would I be better off using Ethernet or Controlnet?. My gut tells me to use Controlnet as I am still do not have the warm and fuzzy regarding ethernet controlling a pump in a remote PAC , where that pump is filling a tank with $10/gallon product.
Due to the nature of this project i will have to message to the PAC that is controlling the MCCs via devicenet using produced consumed tags there are about 150 motors, mainly PF70s. Would I be better off using Ethernet or Controlnet?. My gut tells me to use Controlnet as I am still do not have the warm and fuzzy regarding ethernet controlling a pump in a remote PAC , where that pump is filling a tank with $10/gallon product.