jj
  •  jj
  • 53.19361% (Neutral)
  • Newbie Topic Starter
2020-04-18T18:52:33Z
I am having some difficulty understanding a customers's network architecture. They have a PLC1 that communicates via Devicenet to MCC (Motor Control Center) and then the PLC1 communicates via Ethernet to PLC2 and PLC3.(PLC2 and PLC3 need the MCC pump info to operate). Why would they do that? Why can't it be devicenet from PLC1 to PLC2 and PLC3,or why can't it be Ethernet all the way round meaning PLC1 Communicates Ethernet to MCC and then communicates Ethernet to PLC1 and PLC2.
Guest
2020-04-18T18:56:52Z
I just answered your question on RIO. Device Net is another communication medium I am not real thrilled about. By Ethernet I am assuming that you are referring to Ethernet IP. That is pretty much the industrial protocol version of Ethernet. With that out of the way - on to your question. Device net was designed primarily for discrete components; however, it does work ok for a limited number of more complex components. It also can provide diagnostic information that may not be available in a hard wired situation. It does not work well for communications such as PLC to PLC where potentially large amounts of information may need to be passed back and forth. Ethernet IP is much better at this task. Ethernet IP is limited by the processor you are using as to how many drops it can connect. It therefore would not be a good medium to connect a large number of motor starters together in an MCC.
Guest
2020-06-25T22:42:20Z
Users browsing this topic