Escolar Documentos
Profissional Documentos
Cultura Documentos
Network Basics
509 -BOD
24vdc
EtherNet Network
Printer
email document
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.
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
Trunk cable
Drop cable
Terminator Tap
Drop cable
Tap
Terminator
Terminator
Node
Network device
Node
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.
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
PLC-5
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 28
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
Control Collect and Configure are the new terms being used for these functions within Rockwell
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.
• 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.
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.
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.
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 40
RIO
(Remote I/O)
• 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.
• 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.
ALLEN-BRADLEY
• 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.
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
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.
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 46
DH+
(Data Highway Plus)
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
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.
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 49
DH485
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.
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 51
How do the networks differ ?
Determinism
Packet
Max * Max * Worst
I/O Msg Prog/ Technology Size Nodes
config Length Speed Case
32 per
RIO 10,000ft 230k Master/Slave Polling Small
scanner
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.
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 52
NetLinx Networks
networks.
Additional
With NetLinx Programming 509 -BOD
24vdc Black
Boxes
• No additional programming
• No black boxes
Traditional Networks
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 55
* Explanation of previous slide *
• 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.
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 56
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)
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 57
ControlNet
1756-CNB PLC Prog s/w
ControlNet Bridge RSNetWorx
RSLinx
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
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 58
* 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.
• 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
How do the networks differ ?
Determinism
Packet
Max * Max * Worst
I/O Msg Prog/ Technology Size Nodes
config Length Speed Case
32 per
RIO 10,000ft 230k Master/Slave Polling Small
scanner
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
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 60
Netlinx Network: DeviceNet
• Market is transitioning from hard-wired to networked devices
Control Network
e.g. ControlNet
D D A A
Device Network
24vdc
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
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 61
* Explanation of previous slide
• 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.
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
Eth/IP
* Can’t always get max length at the max speed
** DeviceNet is configuration only, no programming of controllers
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 65
* Explanation of previous slide
• 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.
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 66
Netlinx Network: EtherNet/IP
Ethernet + CIP =
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 67
Netlinx Network: Ethernet/IP
ETHERNET/IP
1757-FFLD
ALLEN-BRADLEY Powermonitor I
1761-Net-ENI Power
Monitor 3000
PowerFlex Drive DF1 to Ethernet/IP
FlexLogix
DriveLogix
Flex Adapter
1756-EWEB
CompactLogix Point Adapter
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 69
How do the networks differ ?
Determinism
Packet
Max * Max * Worst
I/O Msg Prog/ Technology Size Nodes
config Length Speed Case
32 per
RIO 10,000ft 230k Master/Slave Polling Small
scanner
twisted pair
• 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)
Analog
Signal
• 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.
• 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.
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
Copyright © 2006 Rockwell Automation, Inc. All rights reserved. 76
Foundation Fieldbus H1
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).
PLC PC
PROFIBUS-DP
RS485