Networks understanding

Alex Pel

Member
Join Date
Feb 2004
Location
Vancouver
Posts
145
Hello. I am trying to move from local PLC projects into industrial network. At fist I realized that I don’t really understand why there are so many kinds of networks. Even one company provides several networks. For example Allen-Bradley. Does anybody explain a fundamental difference between:

  • DH-485 network
  • DH+
  • Universal Remote I/O
  • DeviceNet™
  • ControlNet
  • EtherNet/IP
Please, don’t send me to AB site. I already read that and still nothing clear. For example for my potential project with 200 I/O I could use any of mentioned one, but why they are all still exist?

Thank you.



 
They all still exist because many people still use old 485 & DH+ & RIO so AB still support it like their other legacy products. For example if you were starting a brand new project you would install control logix & DN/CN/Ethernet networks but if you were adding your 200 IO to a substantial existing PLC5 DH+/RIO system you would use for example Flex I/O on RIO.
 
DH-485: One of the oldest ALLEN BRADLEY networks, it is typcally slow, and I believe supports up to 31 nodes (though I could be wrong). Typically, it runs at 19,200 baud. Useful for programming, and communications between PLC's and HMI's or other PLC's.

DH+: A newer, faster ALLEN BRADLEY designed network, though most of the structure is available in the public domain. It typically runs at 57,600 baud, but also can run at 115 and 230kbaud. Useful the same as DH-485, but supported by more devices. I believe it can support up to 77 nodes. This is a two-wire (blue-hose) network.

RIO: Another legacy AB network, designed primarily for controlling remote-I/O bases. The same speeds, and cabling as DH+, except for some odd reason, the blue and white wires are reversed.

DeviceNet: An AB Network based on the CANBus protocol, which was initially developed for point to point communications in automobiles (go figure). Very good for PLC to Device communications (including drives, limit switches, flow-meters, encoders), but not good for programming or HMI interfacing. Runs on a 4-Wire network that provides both power and communications to slave devices.

ControlNet: One of the newest AB protocols, widely supported, and deterministic. ControlNet runs over coax (basically, RG-6), at a speed of 5MBps. ControlNet can be completely redundant if desired. It is used mainly to replace RIO for remote I/O points, but can also be used for HMI's and programming.

EtherNet/IP: Is another of the newer AB Networks which is becoming a standard. It supports the same CIP protocol as ControlNet, but modified to run over standard Ethernet IP systems. Speeds are generally 10/100MBps on the hardware end, but can be switched to a higer speed backbone (it is, Ethernet after all). This is commonly used for I/O, HMI's, Data Collection, and programming.

Personally, for all new systems, I specify primarily ControlNet for I/O and drives, and Ethernet/IP for HMI and Enterprise communications.

Why are there so many? Technology evolves. Initially, the 'Proprietary' networks gave an edge to one 'brand', as they could sell more items on the premise that all of their devices could communicate well together.

Later on, the networks became more open source, or at least more freely licensed, mainly to increase the potential compatible target markets.

Today, things are moving more and more to universal networks, but there are still the 'biggies' out there that are not interoperable, Profibus/Profinet, Modbus/Modbus TCP, ControlNet, EthernetIP... who knows where the future will take us?
 
Last edited:
DH-485 network
DH+
Universal Remote I/O
ControlNet

These are AB specific. This is typical of the PLC industry. Each manufacturer has different type of proprietary networks available.

DeviceNet™
EtherNet/IP

These are open networks. Ethernet I/P is used for peer to peer mainly but also for remote I/O etc. Device Net is an I/O system from a scanner in the PLC to remote I/O, as are Profibus, ASI, Can Open, Modbus (ASCII, RTU, TCP/IP) etc.

Here is a link to a site where some details can be found on many networks and fielbusses

http://ourworld.cs.com/rahulsebos/

Here is s link to the Device Net website

http://www.odva.org

And the Modbus website

http://www.modbus.org

Hope this helps.
 

Similar Topics

Hi Guys, I want to connect my 1769-L36ERM to a different network domain, is it possible to do it using only the dual ports in the Controller? Or...
Replies
3
Views
221
Hello everyone. I have an PLC L35 (fmw 16) with address 192.168.1.1 and too many connected ethernet devices (3 hmi, a lot of ethernet port, asi...
Replies
11
Views
735
New to S7. Are the "Network 1/2/3/..." simply individual "rungs" of the ladder or is there more to it than that? Thanks
Replies
2
Views
551
So I was trying to shed some light on intermittent timeouts to a 1769-AENTR from CompactLogix L36ERM (basically timeouts are counting up in...
Replies
3
Views
1,293
Hello Gents, I have 3 devicenet Westlock Intellis Valve networks and considering the way DeviceNet is going, I'm wondering if anyone has seen...
Replies
4
Views
1,878
Back
Top Bottom