PLC21000 Network Basics

PLC21000
Network Basics
509 -BOD
24vdc
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 1

What Is a Network?
A network provides a means of connecting multiple devices together for

the purposes of exchanging information.
EtherNet Network
Printer
email document
A common example of a network is an office where the computers are

connected together using an Ethernet network for the purpose of sending
emails or printing documents on a networked printer.

Why Use a Network?
• There are many reasons to use a network. Some examples are:

– Data Acquisition from the Control System
– Control devices in a remote location
– Data Sharing Between PLC Controllers
– The ability to program devices from a remote location
– The ability to troubleshoot problems from a remote location
– The ability to integrate all production areas of a plant
– The ability to integrate manufacturing systems with business systems

Why Are There So Many Networks?
• Many different networks exist for a variety of reasons:

– Different manufacturers
– Newer networks developed
– Designed for many devices transferring large data blocks
– Designed to be inexpensive
– Designed for maximum reliability
– Designed to support many communication protocols (languages)
• Many of these items are mutually exclusive. For example, if a network
was designed to support many communication protocols, it cannot also be
designed to be the least expensive. Therefore, one network can’t be
designed to do everything the best.

Examples of Networks
• Examples of networks used in industrial automation today:

– EtherNet/IP
– ControlNet
– DeviceNet
– DH+
– Remote I/O
– Foundation Fieldbus
– Profibus DP
– Modbus
– AS-i
– InterBus

Types of Networks
• Networks are often referred using the following categories:

– Fieldbus
– Information
– Control
– Device
– Sensor

Network Types
Fieldbus
• A generic term covering all industrial networks.
• Note that there is also a specific network known as Foundation
Fieldbus that is often referred to as just Fieldbus.
Information Network
• Typical devices are computers.
• In an industrial environment, typically PLCs are on the network with
computers.
• Common uses are data collection, data monitoring, file transfers, and
email.
Control Network
• Typical devices are PLCs, HMI terminals, and I/O chassis.
• Common use is for control of plant floor devices such as I/O chassis,
robots and other intelligent devices.

Network Types
Device Network
• Typical devices are field devices such as buttons, lights, valves,
and drives. Also small blocks of I/O.
• Common use is for direct connection to field devices.
Sensor
• Typical devices are very simple field devices such as sensors, and
lights.
• Common use is for direct connection to field devices

Network Topologies

Bus or Trunk/Drop Topology
All nodes are connected to a “bus” or “trunk” cable.

• The bus/trunk cable is run to each node.
• Nodes may connect directly to the trunk, but typically connect to
the trunk using a “tap” and “drop” cable.
• Both ends of the trunk cable are terminated.
Trunk cable
Drop cable
Terminator Tap

Taps and Drop Cables
A tap is a device that allows a node to be connected to the trunk.

• Drop cables connect a device to the tap.
• In some cases the tap and drop cable will be a single unit.
• Typically, drop cables have a relatively short maximum length
allowed compared to the trunk.
Drop cable
Tap

Terminators
Terminators are added to each end of a bus topology network. The

terminators prevent electrical signals from “bouncing back” off the end
of the cable and interfering with new signals that are being transmitted
on the cable. The “bouncing back” of signals off the end of the cable is
known as “reflections”. Terminators absorb the electrical energy of the
signal once it reaches the end of the cable to prevent reflections. The
electrical characteristics of the terminator used depends on the network.
For example, Ethernet uses a 50 ohm terminator and ControlNet uses a
75 ohm terminator.
Terminator

Daisy Chain Topology
A cable is run from one node to the next.

• The trunk cable must be run all the way into each device, and then
back out.
• A daisy chain is like a bus based network with no drop cables.
• Both ends of the cable are terminated.
Terminator

Star Topology
All nodes are directly connected to a central network device.

• There are only 2 nodes on any one cable segment, the node and
the network device.
• The ends are not terminated.
Node
Network device

Ring Topology
Each node is connected to two other nodes to form a ring.

• The ring configuration provides a means of redundancy by
providing two paths between each device.
Node

Combination Topologies
Many larger networks incorporate devices that allow combinations of these

basic topologies.
Hybrid Star Star / Bus

Comparing Bus and Daisy Chain to Star
Bus and Daisy Chain Topology Advantages

• Uses the least amount of cable. Just run from node to node. Star requires a cable
back to a central device. Even if 2 nodes are right next to each other they must be
cabled back to the central device.
• There are no active devices as part of the cable system. With a star, if the network
device fails or loses power it will bring down the whole network.

Comparing Bus and Daisy Chain to Star
Star Topology Advantages

• Adding and removing nodes is simple, just plug into a port on the network device.
With most daisy chain or bus networks, you have to break the network to add a
node.
• Easier to troubleshoot. Each node is on its own segment. The failure of a node
doesn’t affect all the other nodes. With a daisy chain or bus a shorted node or a
node that continuously transmits could bring the whole network down (network
devices in a star can shut off a port if the node transmits continuously).
• Most popular on computer networks.

Comparing Ring Topologies
Ring Topology Advantages

• Provide a measure of network redundancy. The signal could travel around the ring
in either direction, so if the ring is broken in one place the nodes can still
communicate.
Ring Topology Disadvantages
• Not as popular as others. Typically requires more expensive network devices to
implement.

Types of Cable

Cables
The cables used in networking basically fall into two classes:

• Copper Conductor
• Fiber
Copper conductor cables are relatively inexpensive and easy to work
with. Examples of these are:
• Coax cable
• Twisted pair cable
Fiber cables are more expensive and harder to work with, but they
offer the ability to span much larger distances than copper cables and
are also immune to electrical noise since they use light to transmit
data instead of electricity. In order to transmit light signals, fiber cables
use glass or plastic as the signal conductor.

Fiber or Copper?
Fiber cables are used when:
• You need to span large distances beyond the distances

coax cables support for the given network.
• The cables have to pass through electrically noisy areas,
such as those with large inductive motors, welding, or
possible lightning strikes (outdoors between buildings).
Copper cables are used when:
• You don’t need fiber cables. Coax is less expensive and

easier to work with.

Common Network Devices

Repeater
• A device which amplifies a signal. A repeater boosts the incoming signal

to a level that allows devices further down the network to understand it.
There are two types
–Amplifying repeater: amplifies the signal, including noise, and retransmits it.
–Regenerating repeater: recreates the incoming signal and re-transmits it without noise
(most common).
• It is used when the length of the network needs to be expanded or
additional nodes added.
• Repeaters are commonly used on many networks

Hub
• Hub receives signals from devices on the network and re-broadcasts

the signal to all other nodes connected to it on the network.
–A hub is the center of a star topology
–Hubs are commonly used on Ethernet
Hubs do not selectively

route packets. Any packet
entering a port on the hub
will be retransmitted out all
other ports.

Switch
A switch is the most common device at the center of the star topology and
utilizes twisted pair or fiber cable to connect to devices. Switches may be
connected together using a variety of media as a backbone between
switches, including coax cable.
A switch is really a multiport bridge that selectively forwards packets to

their proper destination.
Incoming message is
transmitted only to the Switches
desired node. selectively route
packets of
information to
specific devices

Hub vs. Switch
Since switches selectively forward packets instead of broadcasting them like a hub,
switches are more efficient in that they reduce the number of collisions* on the network,
and the amount of bandwidth used. Switches are used in applications where better
performance than what a hub can provide is desired. Switches are an integral part of
industrial Ethernet networks.
Incoming message is
transmitted to the desired Switches
node only. selectively route
packets of
information to
specific devices
* the concept of collisions is covered in the technology section

Gateway
• A gateway is a device that allows devices on completely different

networks to communicate with each other without knowing anything
about the other network.
–A gateway may covert physical media and protocols
–Gateways are commonly used to convert between all types of networks
The gateway allows the

computer on Ethernet to
Ethernet
communicate with the PLC-5
on ControlNet, even though
Desktop PC the computer has no ability to
communicate on ControlNet
ControlLogix itself.
Gateway
ControlNet
PLC-5
Network Functions
Business
System
HMI HMI
PC Router/switch
server client
Ethernet
Control network
Controller
Ethernet
EOI PC
Control/Ethernet
Link coupler
Control network
Control network
Control network
Device network
Drive
I/O
Controller
Controller
Device
Instruments
Drive
Device
I/O
Drive

Network Functions
• The 3 functions automation networks must provide:

– I/O data CONTROL
– programming support CONFIGURE
– messaging data COLLECT
Control Collect and Configure are the new terms being used for these functions within Rockwell

Network Functions
• Control refers to communications that are directly related to controlling a

process or operation.
– Most often communication is between a controller such as a PLC and an I/O device
– Reading a temperature that is being held steady
– Turning on an output that tells a gate to open
• Configure refers to communication that tells a device how to operate
– Most often communication between a computer and a control device
– Setting the current limit in a drive
– Downloading a program to a PLC
• Collect refers to communication where data is collected about the process
or operation being controlled
– Most often communication between a computer and a control device
– Reading the temperature during a sterilization process for historical record
– Tracking the movement of a part through the manufacturing process

Network Functions
• Rockwell Automation connects to a number of networks to support control,

configure, and collect activities
-- ControlNet -- DeviceNet -- EtherNet/IP
-- Remote I/O (RIO) -- DH+ -- DH-485
-- Other competitive
• Also serial communications using DF1 protocol

• For Process applications to interface to instrumentation
– Foundation Fieldbus
– HART
All of these 6 networks (DH+; DH-485, RIO, D-Net, C-Net and E-Net/IP) exist to provide these functions.
There are six networks because of history; we certainly did not come up with all 6 at once. This was a
progression over 2 decades.
We could abandon DH+; DH-485 and RIO; since we have newer networks that provide this functionality; but we
never do those types of things to our customers (who is currently happy with existing 3 legacy networks)
The legacy networks (DH+, DH-485) are lacking in capability when compared to the newer ones. < Hey, the
first plane only sat one person so he had to fly it; the first car rode a little rough> ; networks have progressed
over time the same way; as technology changes and silicon gets smaller, the networks get more advanced.

Introduction to Rockwell Automation Networks

Which function do they provide ?
I/O Programming Messaging

(Control) (Configure) (Collect)
RIO
DF1 DF1
DH+ DH+
DH-485 DH-485
DeviceNet DeviceNet DeviceNet
ControlNet ControlNet ControlNet
Ethernet/IP Ethernet/IP Ethernet/IP

* Explanation of previous slide *
• This is an attempt to state what basic function these networks provide.

• RIO is, and always has been, an I/O network
• DF1 is the Rockwell standard for point to point RS-232 communications to/from PLCs.
Important because it is an easy way to program a PLC if there is no other network
connection available.
• DH+ is the legacy peer to peer messaging/programming network for PLCs.
• DH-485 is a peer to peer messaging/programming network for SLCs.
• DeviceNet is an I/O network designed to let you add I/O devices as drops on the network,
which negates the need for I/O wiring to I/O modules; saving lots of money. It is also an
open network which makes it possible for products from multiple vendors to sit on a single
network with ease. It can do messaging; but messaging affects I/O speed. (it does not on
ControlNet)
• ControlNet was the next generation network which combined I/O and messaging and
programming onto a single network wire. Kind of RIO and DH+ rolled into one. It provided
a high data rate (5MB) which was critical at the time due to specmanship games with
competitors. We were getting locked out of jobs due to the 230k limit of DH+ and RIO.
• Ethernet/IP is simply Rockwell’s ‘Control & Information Protocol’ (CIP) running on Ethernet;
the “de facto” information network. Ethernet/IP for I/O is available as well.

What is DF1 ?
• A serial protocol for RS-232

• Typically point-to-point, two nodes (full duplex)
• Designed for A-B PLCs to communicate over modems.

• PCCC packets can be transmitted over the other messaging networks as well, just
within different protocols. DF1 is simply the serial protocol.
• The picture shows that a third party can develop a DF1 driver to interface any
product with a serial port (in this case a computer) to a network such as DH+.
Note that DH+ basically sends PCCC packets as well. The need for such drivers
has obviously been reduced by packages such as RSLinx / Windows; since both
utilize windows standards such as OPC/DDE.
• Full Duplex means that both devices can talk at once, so this can only be used in
point to point apps; only two devices.
• If multi-drop is used, the nodes have to set up half-duplex as there is typically only
one (balanced / differential) wire that is switched between Tx and Rx.

DF1
RS-232 port on 5550 processor
COM port Point to Point
Programming
PLC Prog s/w Channel 0 / RS-232 port

RSLinx
COM port Point to Point
Programming
PLC
modem modem
ALLEN-BRADLEY
232 port
PLC
RS-232 232 port
COM port port 1770-KF2 or DH+
Foreign Device
DF1 protocol Interface Third Party Interface
to Data Highway Family

• “ RSLinx ? ” RSLinx provides all of the connectivity drivers between the PLCs and
Windows based software packages (programming, HMI, or third party).
• This would be a good time to run RSLinx and show all the drivers available: such
as: DF1, Ethernet/IP, KTC (ControlNet), KTx(DH+&DH-485), PIC, AIC (DH-485),
DeviceNet, PCMK, SL5, Gateway
• Note that RSLinxLite ships with the various programming software packages. It
has all the comm drivers in it; it just does not support the DDE/OPC (Windows)
stuff required to use RSLinx as a server between windows packages and ROKA
software products. A good way of stating this is that Lite supports ROKA network
comms but not windows based comms.
• There are more ways to use DF1. This is just a sample of the most common.
Programming, SCADA, and third party interfaces are the most common uses.

How do the networks differ ?
Determinism
Packet
Max * Max * Worst
I/O Msg Prog/ Technology Size Nodes
config Length Speed Case
RIO
DF1 50 ft 38.4K Serial / RS-232 Medium 2
DH+
DH-485
CNet
DNet
Eth/IP
•Can’t always get max length at the max speed,
-- Given that a medium amount of data is moved and that the data rates are low, that is not the best network if speed is a concern.
-- Also, RS-232 is only point to point, so if it is required to talk to multiple devices on a single network, a different network is required.
RIO
(Remote I/O)
• An I/O control network, used by PLCs.

• Optimized for scanning a known amount of I/O in a very
predictable fashion – “Deterministic”
• Media: PVC Twinaxial cable (w/shield)
– “Blue hose”
• Daisy-chain between nodes
• Data Rates: 57.6k, 115.2k, 230.4k baud
• Max Distance: 10,000 ft. (30 miles via fiber optic repeaters)
• Topology: Master/Slave
• Max Nodes: 32

• Important to note that no EXTRA software is required to do RIO. In other words, it is native to the PLC as
firmware. Built in stuff. It is Implicit. There is nothing you can really do to stop it from running.
• Built to do nothing but poll I/O. That is why it is great for I/O.
• RIO has a very low overhead; very few commands/functions supported; so it is very efficient at what it
does.
• As the data rate increases, the distance decreases.
• Because we know how long it will take to scan each RIO adapter, we can ‘determine’ ahead of time the ‘worst
case’ time it will take to scan an RIO network. If block transfers are added, and they always are, the ability to
calculate the ‘worst case’ RIO scan time becomes much more difficult. For example, if block transfers are used in
remote racks, the system will do one block transfer per adapter per scan. So if two BT modules are in the same
remote rack; we cannot be sure in which scan the BT will occur for each module. Also the time for BTs changes
as the length increases.
• So it would be a mistake to say that RIO is deterministic. Lets just say that it is possible to calculate a worst case
update time. The actual scan time almost always is less than that worst case time. Some argue that this means
RIO is not deterministic. I say it simply means the network is not repeatable. But I will defer and simply say that
RIO allows one to generate a worst case update time.
• Determinism is the ability to determine ahead of time the response of the network; even before it is even
assembled.

Remote I/O
Since RIO is a master/slave network, every RIO network requires
a SCANNER and an ADAPTER
1747-SN Scanner 1756-DHRIO Scanner
ALLEN-BRADLEY
Blue 1771-ASB Adapter

Hose

• The RIO scanner is native to the PLC5
• A modular 1747-SN Scanner is required for the SLC
• A modular 1756-DHRIO is required for ControlLogix. The 1756-DHRIO supports 2 channels of RIO,
2 channels of DH+, or 1 channel of each.
• Note the local I/O in the same chassis as the PLC. This I/O is updated every I/O scan. The I/O in
the RIO chassis are updated asynchronously to the PLC program scan. In other words, you could do
multiple RIO scans for every program scan.
• Worst case RIO throughput is 2 RIO input scans (because we may have just missed the input) plus
two (2) program scans plus 2 RIO output scans (because we may have just missed the output when
we updated the RIO data)
• For a PLC5 system at 230.4k, it takes 3ms to update each RIO adapter node; if no BTs are
occurring.
• RIO can only have a single master / scanner on the network. Unlike DeviceNet and ControlNet that
can have multiple scanners on the network. Each RIO network has one scanner and can have
multiple adapters.

Remote I/O Devices
Scanners
ALLEN-BRADLEY
1784-KTx / ISA 1784-PCMKS

Native 1747-SN 1756-DHRIO
1784-PKTx / PCI
Adapters
1771-ASB 1794-ASB
1747-ASB
Third
ALLEN-BRADLEY
Motion Party
Control Devices
- Drives
- CNC - Robots
- PanelView - Weld Controls
- 1771 I/O - 1746 I/O - RediPanel
- Block I/O Flex I/O - etc.
- Dataliner

Determinism
Packet
Max * Max * Worst
32 per
RIO 10,000ft 230k Master/Slave Polling Small
scanner
DF1 50 ft 38.4k Serial / RS-232 Medium 2
DH+
DH-485
CNet
DNet
Eth/IP
DH+
(Data Highway Plus)
• A messaging network for PLCs.

– Allows access to PLC data table info via read or write messages (PCCC)
• Protocol: a token passing Peer to Peer bus network.
• Number of Stations: 64 stations maximum
– 15 or less recommended.
• Cable System: Twinaxial Baseband (Blue Hose)
• Provides online programming capability
57.6 Kbaud ----> 10,000 ft

115.2 Kbaud ----> 5,000 ft
230.4 Kbaud ----> 2,500 ft
* DH+ was primarily designed to send messages between PLCs

Data Highway +
PLC Prog s/w
RSLinx
1784-KTx / ISA
1784-PKTx / PCI COM port
PLC5
Native
1770-KF2
or 1785-KE
1756-DHRIO
Module
DH+
Messaging &
Programming
1785-KA5
ALLEN-BRADLEY
Bridge
SLC-5/04
Native 1784-PCMK
DH-485

Determinism
Packet
Max * Max * Worst
32 per
scanner

64, 15 or less
DH+ 10,000ft 230k

Floating Master /
Token Passing
Medium recom-
mended
DH-485
CNet
DNet
Eth/IP
DH485
• An information network primarily designed for SLC500, 5/02,

5/03
• A token passing Peer to Peer bus network
• up to 19.2 Kbaud
• Number of stations: 32 maximum / 15 or less recommended
• Often requires more hardware to support network connections
(ie. AIC Link Coupler) vs. DH+
• Message passing network only, not deterministic.
• Supports a respond only mode for low level devices
• Remote programming support
• Based on RS-485 electrical signal specification

DH-485
SLC Prog s/w
RSLinx
1784-KTx / ISA
1784-PKTx / PCI COM port
1770-KF3
or 1747-PIC
1761-NET-AIC
1761-NET-AIC
1747-AIC
Messaging &
1747-AIC
Programming Serial Port
1747-AIC 1785-KA5
Bridge
ALLEN-BRADLEY
DH+
SLC-5/03
Native
1784-PCMK
Note that PLC5s and ControlLogix can only connect via a bridge (DHRIO). They cannot be placed directly on DH-485.
Determinism
Packet
Max * Max * Worst
32 per
scanner

64, 15 or less
DH+ 10,000ft 230k

Floating Master /
Token Passing
Medium recom-
mended
32, 15 or less
Floating Master / Medium recom-
4,000ft 19.2k
DH-485 Token Passing mended
CNet
DNet
Eth/IP
NetLinx Networks
The NetLinx Open Architecture is the Rockwell Automation solution that

uses open networking technology for seamless shop-floor to top-floor
integration. NetLinx uses three networks to make up the NetLinx
architecture, DeviceNet, ControlNet, and EtherNet/IP. Each share the
same protocol, CIP, which enables you to Control, Configure, and Collect
information and data efficiently.
By using the same application level protocol, NetLinx networks allows
seamless communication between the networks.

What is Seamless Communication?
Seamless communication means you don’t have to do programming of the

devices between the networks in order to communicate through them.
Some networks support bridging to other networks, but in most cases they
require programming at each bridge device. Seamless communication,
often referred to as seamless bridging and routing, has many benefits
including:
– Access to all parts of the architecture from a central
location EtherNet/IP,
– Ability to segment networks to reduce traffic or ControlNet
implement security, yet still communicate across

networks when needed
– Integrate the architecture - allow information flow from
the plant floor to the business enterprise system. DeviceNet

NetLinx And Seamless Communications
• NetLinx Uses a Common

Application Layer called the CIP Protocol “spoken” on all 3 networks
Common Industrial Protocol
(CIP) EtherNet/IP ControlNet DeviceNet
• Using a common application

layer protocol eliminates the
need to “translate” information
as it passes between 509 -BOD
24vdc
networks.
Additional
With NetLinx Programming 509 -BOD
24vdc Black
Boxes
• No additional programming
• No black boxes
Traditional Networks
• *This table is a generalization. Obviously there are exceptions to every Requirement.

• Field Devices – Small, intelligent field devices such as photoeyes, proximity sensors are
generally only found on DeviceNet.
• Interlocking (Peer-Peer) – With Logix controllers, DeviceNet only supports unidirectional

messaging so cannot be used for interlocking. Both CNet and ENet/IP can perform interlocking
using Produce/Consume or Messaging but the highly deterministic behavior of CNet and its
hardened media attributes give it an edge.
• Distributed I/O (Control) – CNet is best because of its determinism, wide product support,
hardened media, media redundancy. ENet/IP has little established base but has emerging
product support and the features to become a distributed I/O network. DNet supports a wide
variety of smaller I/O blocks but is limited by distance and bandwidth.
• View (Operator Interface) – Due to the cost advantages of built-in Ethernet (PC, PanelView
Plus) and availability of Ethernet at the IT level, ENet/IP has the advantage over CNet, even
though CNet can perform the same function. DNet is widely used for low cost, simpler
PanelViews.
• Data Collection – Similar to View, the availability and cost structure of Ethernet in the “office
environment” gives it the advantage over CNet. DNet is widely used for Data Collection (drives,
sensors) but typically requires a supporting ENet/IP or CNet Linking Device or gateway.
ControlNet User Benefits
• High-speed (5 Mbits/sec) control and I/O network
– Improved I/O and improved peer-to-peer performance
– Ability to accommodate I/O (time critical) and programming (non-time critical on
the same network
• Time Critical: Scheduled Data
• Non-Time Critical: Unscheduled Data
• Industrial Hardened Physical Media
– High noise immunity (coaxial and fiber optic cabling)
– Intrinsically safe media and products (Flex Ex, fiber optic repeaters)
– Sealed (IP67) media
– Media redundancy
• Advanced network capabilities
– Deterministic - know when data will be transmitted
– Repeatable - transmit times are constant, even as devices enter and leave the
network
– Producer/Consumer model: Multimaster, multicast inputs, and peer-to-peer
• Open network supported by ControlNet International
(www.controlnet.org)
ControlNet
1756-CNB PLC Prog s/w
ControlNet Bridge RSNetWorx
RSLinx
PLC5C 1784-KTCS / ISA COM port

Native 1784-PCICS / PCI /serial
1770-KFC15
Processor 1756-CNB
Scanner 5550 ControlNet Bridge 1784-PCC
Messaging only
Repeater Scanner
Adapter Adapter
ALLEN-BRADLEY
Flex I/O
1794-ACNR15
Panelview 1746 I/O
1784-KTCS / ISA w/1747-ACNR
Adapter
1771 I/O Scanning for soft
w/1771-ACN15 control engines w/1747-SCNR
Adapter
Scanner
* Explanation of previous slide
• It is important to note that the ControlNet Module for the Controllogix chassis is
referred to as a bridge. Connections are made between the Logix processor and
nodes on Controlnet directly. In other words; those nodes appear to be essentially
sitting on the ControlBus. The CNB just gets info from the nodes over ControlNet and
blasts it onto the ControlBus.
• The backplane on ControlLogix is called ControlBus and it the backbone of the

ControlLogix producer/consumer model. Any slot on the Controlbus can pull down the
transmit line and produce data on the backplane; for anyone else to hear. There is no
schedule at all to control these comms; no round robin or time slice like on
ControlNET.
• A ControlLogix processor can control 1756 I/O not only in the local chassis but also in
distributed chassis that have a CNB. The CNBs are bridges that allow scheduled I/O
commands to occur; as well as explicit and implicit messaging.
• Not shown: ControlNet to DeviceNet Linking Device, ControlNet to Fieldbus linking
device Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 59
Determinism
Packet
Max * Max * Worst
32 per
scanner

64, 15 or less
DH+ 10,000ft 230k

Floating Master /
Token Passing
Medium recom-
mended
32, 15 or less
4,000ft 19.2k
250- Multiple Access /

CNet 1000m 5M
Time Slicing Medium
99, 40 or less
recom-
mended
DNet
Eth/IP
* Can’t always get max length at the max speed.
-- ControlNet is OPEN technology.
* ControlNet : 1000 meters with 2 devices on network, 250 meters with 48 devices, max of 6000 meters with repeaters
Netlinx Network: DeviceNet
• Market is transitioning from hard-wired to networked devices
Control Network
e.g. ControlNet
D D A A
Device Network
I/O Network 1-5 vDC T

4-20 ma T
e.g. RIO
509 -BOD
24vdc
120 vAC 509 -BOD
Remote
24 vDC
24vdc
I/O
Rack
D D A A
PAST PRESENT
1-5 vDC T
4-20 ma
120 vAC
509 -BOD
24vdc
24 vDC
• Running a single wire (granted, a more expensive wire) saves a

tremendous amount of money for your customer.
• Perhaps, it costs $10 for every foot a single wire is run. This includes the
labor, parts, and troubleshooting because the cable may have been wired
incorrectly.
• We cannot wire DeviceNet incorrectly. It is just a single wire that we route

to our devices on the network.

Netlinx Network: DeviceNet
• Lower Acquisition and Installation Cost
– Reduction in plant wiring (eliminates hardwiring of I/O)
– Lower installation, start-up, and maintenance times
• Network Attributes
– Data flow is governed by the Producer/Consumer model
– Ability to link smart factory floor devices together and bridge to higher level
networks
– Superior device level diagnostics
– Device Plug and Play capabilities - add or remove nodes on the fly
– Optimized to handle small-sized amounts of data (8 bytes per message, supports
message fragmentation for larger data sizes)
– 64 devices per network and data rates of 125, 250, and 500KB
• Media Options
– Passive bus media: nodes can enter and leave without affecting the network
– Sealed (IP67) and unsealed (IP65) media
– Low cost flat media
• Open network with over 250 companies
actively supporting ODVA
DeviceNet
RSNetWorx
RSLinx
COM port
serial
PLC5 1784-PCD
PCID
1770-KFD
Scanner 1756-DNB
Scanner DeviceNet Bridge
1771-SDN
1761-NET-DNI
Scanner
ALLEN-BRADLEY
1794-ADN
Hundreds of types of devices
SLC 1784-PCIDS / PCI
Compact 1747-SDN Scanning for soft Adapter
I/O Scanner Adapter
control engines Adapter
ALLEN-BRADLEY

Determinism
Packet
Max * Max * Worst
32 per
scanner

64, 15 or less
DH+ 10,000ft 230k

Floating Master /
Token Passing
Medium recom-
mended
32, 15 or less
4,000ft 19.2k

CNet 1000m 5M
Time Slicing Medium
99, 40 or less
recom-
mended
Multiple Access /
DNet ** 500 m 500 k bitwise arbitration Small 64
Eth/IP
* Can’t always get max length at the max speed
** DeviceNet is configuration only, no programming of controllers
• By definition, DeviceNet is NOT a deterministic network. This is because each node

does not have a specified time to talk on the wire like in ControlNet. Each node must
listen for the wire to be quiet before sending data on the wire. This is what ‘multiple
access’ means. Any node can talk at any time as long as the wire is quiet.
• The packet size is very small, in many cases a device will only send one bit to the
controller. Note that small packet size seems to be consistent with I/O networks.
• 64 nodes does not necessarily mean 64 devices. Flex I/O is a DeviceNet node that
provides up to 128 I/O points (per a single Dnet node)
• DeviceNet does support explicit messaging, as well as I/O. I/O is by far the more
important of the two; especially since the explicit messages can delay the I/O updates
on the wire. Recall that because DNet has ‘multiple access’ and no time slice stuff,
I/O has NO built in priority over messaging. I/O will, however, win out over messaging
if a collision occurs.
Netlinx Network: EtherNet/IP
• Ethernet has long been a defacto standard for business networks. It

was a natural progression to tie the plant floor into the business system
(MES) using Ethernet.
• Since Ethernet is ideal as an information network, it began to become
more popular on the plant floor as information needs increased
– Connectivity to multiple vendors’ host computers
– Large networks with capacity for transfer of large data files
– Standard network management and troubleshooting tools
– Processor, MMI, and software products are growing in complexity and capability
resulting in a need for higher performance networks
• As customers have pushed for further openness and fewer networks,
Ethernet is now being adopted as a control network also
– Requires some enhancements to existing Ethernet with TCP/IP
Ethernet + CIP =
Netlinx Network: Ethernet/IP
• Connectivity to all computer manufacturers and software

– customers can choose the vendor(s) they prefer
• Standard network management software: SNMP
• Highly efficient data transfer
– Increased baud rates (10Mb, 100Mb), use of switches (instead of hubs), full duplex data
transmission to minimize effect of message collisions, and isolation from the office
Ethernet network
• Use of commercial off the shelf products and technology
– Common set of installation and support tools
– Well established network standard, Can take advantage of web browsing services in the
products
• Media Options
– Active bus media: supports star network topologies
– High noise immunity (fiber optic cabling)
– Extend bus length with multiple switches (copper and fiber)
– Sealed (IP67) media - emerging technology (Consortia lead by RA)
• Open - Technology Is Owned and Managed by ODVA and ControlNet
International

Ethernet/IP
RSViewME 1756-ENBT 10/100Mb

with controller or PanelView
RSLinx
1756 I/O RSLogix 5000
SL5800
RSLinx
PV +
ETHERNET/IP
1757-FFLD
ALLEN-BRADLEY Powermonitor I
V 473 465 471

A 865 852 859
1761-Net-ENI Power
Monitor 3000
PowerFlex Drive DF1 to Ethernet/IP
FlexLogix
DriveLogix
Flex Adapter
1756-EWEB
CompactLogix Point Adapter
Determinism
Packet
Max * Max * Worst
32 per
scanner

15 or less
DH+ 10,000ft 230k

Floating Master /
Token Passing
Medium recom-
mended
15 or less
4,000ft 19.2k

CNet 1000m 5M
Time Slicing Medium
99, 40 or less
recom-
mended
Multiple Access / 64
DNet ** 500 m 500 k bitwise arbitration Small
Nodes
Multiple Access /
100m 10M Large 1024
Eth/IP 2 device
segments
100M
collision detect twisted pair
twisted pair
* Can’t always get max length at the max speed

** DeviceNet is configuration only,
Copyright © 2006 Rockwell no Inc.
Automation, programming
All rights reserved. of controllers 70
• There is a note regarding Manchester Phase Encoding / Decoding to answer the question
about why we simply don’t speed up DH+ or RIO to 5MB. The technology for the 5MB
ControlNet and 10MB Ethernet wires allows the network to run at these speeds. It does
NOT simply look at voltage levels at the receiver like DF1/RIO/DH+/DH485/Dnet; rather
they look at the signal phase. Basically, the transmitter matches the current clock cycle for
a data 0; and inverts (180 deg out of phase) the current clock cycle for a data 1. The
receiver simply has to determine whether the rcvd signal is IN phase or OUT of phase to its
current clock cycle to determine whether the signal is a 1 or a 0. Obviously, the clock
cycles of the transmitter and receiver must match up precisely.
• DNet , CNet and Ethernet/IP use the CIP model. The CIP supports multimaster, tag based
memory, producer / consumer, routing, bridging.
– Note that Floating Master and PCCC match up. This is because PCCC is a source/destination
protocol. We send a message to a destination and that station sends a reply back to the
source. Token passing works OK for these types of networks.
– Note that Multiple access and CIP are always matched up. This highlights that the
producer/consumer model works best with networks that allow immediate access to the network
if it is not being used (no token)

Process Instrumentation Communication
The most common interface to process instrumentation today is still a direct

interface from a device that provides a 4-20 mA signal to an analog I/O
module that communicates to a control processor.
Newer installations and system upgrades are taking advantage of digital
communications methods to exchange more data with a process device
than the process variable (such as the temperature or pressure). Using
digital communications allows devices to exchange multiple variables (such
as pressure and temperature) and also diagnostics (such as the health and
state of the device). In addition, configuration can be done remotely.
HART
• Digital signals encoded on the analog signal providing additional
diagnostic data from the transmitter
• Can be used in traditional 4-20mA applications and is backward
compatible with existing installations.
Analog
Signal
HART - Highway Addressable Remote Transducer

• HART originated in the late 1980s and became an open protocol in 1990.
• The basis for HART communication is a digital signal that rides on the existing analog 4-
20mA wiring. This two-way digit communication solution does not interrupt analog process
values.
• All HART-smart field devices contain valuable information to improve process operations
and better manage plant assets. Integrating HART with plant systems for real-time access
to this information unleashes the power in these devices for use during normal plant
operations.
• 3 levels of interfacing HART in existing systems:

– Replace only the device and use a handheld to get HART
– Replace the device and insert a HART multiplexer between devices and Input card to strip off the
HART and send to computer
– Replace the input card with a HART module

HART
• HART was the first open protocol to connect analog devices together
• Millions of devices installed worldwide
• 80% of all Instruments sold today have HART connectivity
– Many customers don’t use it, but device manufacturers build it in to almost all devices
rather than making HART and non-HART devices.
• Readily adopted by customers since they could use their existing 4-20mA
wiring.
Process people refer to HART as a protocol – not a network

Some customers have found HART difficult to maintain when there are a
number of different vendors instruments in the plant because there is no
standard software or tools to do calibration/maintenance

Foundation Fieldbus H1
• Digital network designed specifically to support the demands of devices

used in a process application.
– Device communication is scheduled at specific intervals
– Control, such as loop functions, can be distributed among the devices. Devices have
embedded function blocks.
– Devices are capable of transferring large amounts of analog data, in addition to digital
data.
Controller with
FFB interface
FFB Loop
H1
Foundation Fieldbus H1 is an open protocol developed in the
1990’s. It was designed specifically to support the demands of
devices used in a process application.
Devices can exchange data and perform loop control
independent of the controller
Foundation Fieldbus H1
• Foundation Fieldbus H1 is an open protocol developed in the 1990’s.

• Is a paradigm shift on how you do control.
– Instruments become a core part of the control strategy
– Customers need to learn it before they apply it
• Industries most accepting are those with remote monitoring requirements
such as oil & gas pipelines and platforms
• Very small but rapidly growing installed base.
• Customers can use their existing 4-20mA wiring.
– Requires reconnection, many rewire
Many talk of using the existing wiring, which is possible. In that case the wiring is
brought into FF terminal blocks and the network cable is also connected to carry the
signals from the devices. Others simply rewire because they are replacing old wiring
and just wire take the FF wiring directly to the device. In most cases the instruments are
replaced so a new instrument has to be wired anyway (with the old or new wire).

PROFIBUS-PA
• Digital network designed to extend PROFIBUS-DP in order to support

process automation
• PROFIBUS-PA was introduced in 1997 to extend PROFIBUS-DP in order
to support process automation.
• Relatively small installed base (primarily non U.S.).
• Operates on the same physical layer as Foundation Fieldbus H1.
PLC PC
PROFIBUS-DP
RS485
Devices are intrinsically safe (IS). Most

applications in Europe require IS devices.
Link coupler
PROFIBUS-PA PA devices do not execute function blocks or
IEC 61158-2 communicate with other devices like Fieldbus H1
Works like RIO block transfer. Use read and write
instructions to pass blobs of data.
More customers are purchasing because of lower
price vs. FF and they don’t need control in the device

PLC21000 Network Basics

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PLC21000 Network Basics

Încărcat de

Drepturi de autor:

Formate disponibile

PLC21000

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 1

A network provides a means of connecting multiple devices together for

A common example of a network is an office where the computers are

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 2

• There are many reasons to use a network. Some examples are:

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 3

• Many different networks exist for a variety of reasons:

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 4

• Examples of networks used in industrial automation today:

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 5

• Networks are often referred using the following categories:

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 6

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 7

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 8

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 9

All nodes are connected to a “bus” or “trunk” cable.

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 10

A tap is a device that allows a node to be connected to the trunk.

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 11

Terminators are added to each end of a bus topology network. The

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 12

A cable is run from one node to the next.

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 13

All nodes are directly connected to a central network device.

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 14

Each node is connected to two other nodes to form a ring.

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 15

Many larger networks incorporate devices that allow combinations of these

Hybrid Star Star / Bus

Bus and Daisy Chain Topology Advantages

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 17

Star Topology Advantages

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 18

Ring Topology Advantages

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 19

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 20

The cables used in networking basically fall into two classes:

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 21

Fiber cables are used when:

• You need to span large distances beyond the distances

Copper cables are used when:

• You don’t need fiber cables. Coax is less expensive and

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 22

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 23

• A device which amplifies a signal. A repeater boosts the incoming signal

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 24

• Hub receives signals from devices on the network and re-broadcasts

Hubs do not selectively

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 25

A switch is really a multiport bridge that selectively forwards packets to

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 26

* the concept of collisions is covered in the technology section

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 27

• A gateway is a device that allows devices on completely different

The gateway allows the

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 29

• The 3 functions automation networks must provide:

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 30

• Control refers to communications that are directly related to controlling a

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 31

• Rockwell Automation connects to a number of networks to support control,

• Also serial communications using DF1 protocol

Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 32