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
RSLogix500 Introduction
RSLogix500 Inserting Instructions
RSLogix500 Opening a File
RSLogix500 Creating a Project
RSLogix500 Instruction Comments
RSLogix500 Rung Comments Page Titles
RSLogix500 Inserting Branches
RSLogix500 Program Organization, Part 1 - Overview
RSLogix500 Program Organization, Part 2 - Examples
RSLogix500 Using Symbols
RSLogix500 View Properties
RSLinx
RSLogix500 Online Offline
RSLogix500 Dowloading and Uploading
RSLogix500 Processor Modes
RSLogix500 Processor and Cards
RSLogix500 Introduction to Faults
RSLogix500 Indirect Addressing
RSLogix500 Indirect Addressing Faults
RSLogix500 Handling Faults
RSLogix500 Forcing I/O
RSLogix500  Custom Data Monitor
RSLogix500 I/O Configuration
RSLogix500 Advanced Diagnostics
RSLogix500 Instructions OTL OTU, Part 1
RSLogix500 Instructions OTL OTU, Part 2
RSLogix500 Instructions OTL OTU, Part 3
RSLogix500 Instructions, OTE
RSLogix500 Instructions, XIC XIO
RSLogix500 Instructions, ADD
RSLogix500 Instructions, COP
RSLogix500 Instructions, CPT - Part 2
RSLogix500 Instructions, CTU CTD - Part 1
RSLogix500 Instructions, CTU CTD - Part 2
RSLogix500 Instructions, CTU CTD - Part 3
RSLogix500 Instructions, CPT - Part 1
RSLogix500 - Comparison - Part1
RSLogix500 - Comparison - Part 2
RSLogix500 Instructions, DIV
RSLogix500 - FIFO - FFL and FFU - Part 1
RSLogix500 - FIFO - FFL and FFU - Part 2
RSLogix500 Instructions, FLL
RSLogix500 Instructions, JMP and LBL
RSLogix500 Instructions, Masking and MEQ
RSLogix500 Instructions, MUL
RSLogix500 Instructions, MOV
RSLogix500 Instructions, LIM
RSLogix500 Instructions, NEG
RSLogix500 Instructions, OSR
RSLogix500 Instructions, RTO
RSLogix500 Instructions, SQO sequencer - Part 1 of 3
RSLogix500 Instructions, SQO sequencer - Part 2 of 3
RSLogix500 Instructions, SQO sequencer - Part 3 of 3
RSLogix500 Instructions, SUB
RSLogix500 Instructions, TOF
RSLogix500 Instructions, JSR and RET
RSLogix500 Shift registers
RSLogix500 Instructions, SQR
RSLogix500 Instructions, TON - Part 1
RSLogix500 Instructions, TON - Part 2
RSLogix500 Instructions, TON - Part 3
Introduction to Ladder Logic