PLC21200

ControlNet Overview
and Media

(Confidential For Internal Use Only)

Copyright 2007 Rockwell Automation, Inc. All rights reserved.

1

PLC
21200

What is ControlNet?

ControlNet is a high speed, industrial control network designed for deterministic,

predictable and repeatable communication between industrial devices.
ControlNet is unique among industrial networks in that you can schedule data
communications between devices at various rates, and the data is guaranteed to be
delivered at the rate specified. This type of data communication is known as scheduled
data.
At the same time ControlNet allows devices to send data on an event basis during the
time periods where scheduled data is not being transmitted. There is no guarantee as to
the rate at which this data can be transmitted since it is of a lower priority than scheduled
data. This data is known as unscheduled data.

PLC
21200

ControlNet Features

5 Mb data rate
Supports deterministic and repeatable data delivery using scheduled communications.
Also supports unscheduled communications
Designed primarily for communications between PLCs, I/O devices, programming
terminals, and operator terminals
A single network that can be used for I/O control, messaging, programming and operator
interface
A producer/consumer network that supports multiple masters, multicast and peer-to-peer
Flexible installation options
Coax Media redundancy (option)
Coax (BNC and TNC connectors) and fiber cabling (ST ceramic or plastic
connectors except the Versalin V connector for the 1786-RPS)
Support for up to 99 nodes on the same physical link
Support of intrinsically safe products and media (1797)
An open network represented by the ControlNet International users organization
Supports ControlLogix Redundancy and PLC-5 ControlNet Hot Backup (redundant
processors for high availability systems)

PLC
21200

ControlNet International Ltd.

Users organization
Owns the ControlNet network specification
Owns the ControlNet trademark name
Chartered with making ControlNet successful

Open to all
SIGs activities (Special Interest Groups)
Internet Home Page

(http://www.controlnet.org)
(http://www.controlnet.org)

PLC
21200

Media Detail-most modules have BNC connectors, a

few modules have TNC or fiber connectors
PLC

PLC

PLC

Coax Segment

Coax Segment

Coax Segment

RPA RPFS

To other
ControlNet
products

RPA RPFS RPFM

To other
ControlNet
products

Fiber Segment
(Point-to-point)

RPA RPFM

Fiber Segment
(Point-to-point)
Fiber Segment
(Point-to-point)
RPA RPFS RPFM

1336T
Drive
1336T
Drive

PLC
21200

ControlNet Physical Layer

(Coax, BNC & TNC connectors)

ControlNet is a Trunk/Drop (or bus) network. Each node is

connected to the trunk cable with a tap. The taps are fixed
at 1 meter in length, so each node must be located within 1
meter of the trunk cable. Since ControlNet is a bus based
network, each end of a segment must be terminated.
Note: Tree and star topologies are
supported with repeaters. Ring topology
is supported via fiber ring repeaters.

BNC Tap
Coax trunk cable

Trunk Cable

Tap Separation
(No Min)

Trunk Cable
Termination
Required

Trunk Cable
Termination
Required
75

75
Drop Cable
1 meter

Node

Node

Tap
Required

Node

Node

Node

PLC
21200

ControlNet Physical Layer

(Coax, BNC & TNC connectors)

The trunk of the network is RG-6 quad shield coax*, which is

inexpensive and available from many vendors. The drops,
or taps, can be placed anywhere along the trunk. The tap
cable connects to the device with a BNC connector**. The
terminators use BNC** connectors and are 75 ohm.
0

ControlNet tap
with fixed 1 meter
cable

Last tap has a 75

ohm terminator
Standard BNC
connectors

RG6 quad shield

coax

*Available in several types (plenum, high flex, armor) from several vendors
**ControlNet Armor products use TNC connectors. There are also TNC
terminators.

PLC
21200

Network Connections

All permanent nodes on the network should

be connected using a tap. You can connect
to the network temporarily through the
Network Access Port, or NAP, found near the
BNC connector on the device for the tap.

NAP port for

temporary cable

The NAP is a phone jack style connector that

allows you to connect to the network through
an existing device. The NAP provides full
access to the network, not just to the device
Tap connects
you are connected to, just as if you were
here
connected using a tap.
The NAP eliminates the need to install spare
taps on the network for temporary nodes
used in troubleshooting, commissioning, etc.

BATT
Prog
PROC

R
E
M

FOR

Run

COMM

A
B
AB

1
2
1
2

Battery
PLC-5/40C
Programmable
Controller

PLC
21200

Spare Taps

In some cases users will want to install spare taps along the
network so that they do not have to break the cable later to
install a new node. A loose tap is a source of noise to the
network, so it is a good idea to install the dummy load
terminator (1786-TCAP) on any loose taps. The dummy
load terminator matches the impedance of an actual device
and prevents noise from entering the system through the
unconnected tap. The dummy load can easily be removed
when it is time to install the actual node. Note that this
device is not the same as the trunk cable terminators.

Spare tap

Dummy load
terminator
(1786-TCAP)

You can install a straight through BNC

connector instead of a tap. While this will
reduce the noise entering the system, you
will have to break the network to install the
tap later when you wish to add the device.

PLC
21200

Coax Trunk Segment Specification

The distance that a coax cable segment can be run is based

on the number of devices that are attached to the segment.
The more devices attached to the segment, the less the
allowable distance. The chart below shows the maximum
allowable cable length for 1786-RG6 cable based on the
number of devices. For example, with 16 devices the
maximum allowable cable length would be 750 meters.
Coax
Trunk
Cable
Length

M
E
T
E
R
S

Repeater required
if your system falls
in this area

1000
750
500

Single
Segment
Chart

No repeater
required if your system
falls in this area

250

16

32

Number of devices

48

PLC
21200

Coax Trunk Segment Specification

Note that the chart stops at 48 devices. You cannot have

more than 48 devices on a single coax segment. But what if
you needed more than 48 devices on your network
(ControlNet allows up to 99 nodes on a network)? Or you
needed to run the cable a longer distance than the chart
allows? The answer is to add a repeater.

Coax
Trunk
Cable
Length

M
E
T
E
R
S

Repeater required
if your system falls
in this area

1000
750
500

Single
Segment
Chart

No repeater
required if your system
falls in this area

250

16

32

Number of devices

48

PLC
21200

Coax Trunk Segment Specification

The previous graphic shows the limitations for 1786-RG6 coaxial cable with
a 5.99 dB @ 10 MHz per 304m cable attenuation. Note: If a cables
attenuation factor is not 5.99 dB like 1786-RG6FA (high flex), then you must
use the dB formula which is
Max distance per segment in m = (20.29 dB ( number of taps * 0.32 dB))/
cable attenuation@10 MHz per 304 m.
Coax
Trunk
Cable
Length

M
E
T
E
R
S

Repeater required
if your system falls
in this area

1000
750

1786-RG6 only

500

Single
Segment
Chart

No repeater
required if your system
falls in this area

250

16

32

Number of devices

48

PLC
21200

ControlNet Repeaters

Repeater modules are available to extend the allowable cable

distance or add additional nodes to a ControlNet network.
There are both coax and fiber optic repeaters available for
ControlNet. For the most part, you cannot attach nodes
directly to fiber optic cables, so fiber repeaters generally
connect coax segments together.
Coax cable

Coax cable
Fiber cable
Fiber
Repeater

Fiber
Repeater

Coax with BNC & TNC connectors

1786-RPFS 200/300 micron plastic fiber with Versalin V connectors
1786-RPFM,-RPFRL, -RPFRXL 62.5/125 micron multi-mode fiber with ST ceramic
or plastic connectors
1786-RPFRXL 9/125 micron single mode fiber with ST ceramic or plastic

PLC
21200

ControlNet Repeater Modules

ControlNet repeaters use a modular system where the

repeater units are connected to a base unit, or the previous
repeater unit. Each repeater unit has 2 channels on it,
allowing you to go off in two different directions. Up to 4
modules* can be attached to the base, effectively creating a
repeater hub.
Base unit always
connects to coax
segment through
a tap

Repeater module. This could be

a coax or fiber repeater. You can
mix types.

RG6 quad shield

coax
* Only 2 modules if using one of the fiber optic ring repeaters

Fiber cable to similar

fiber repeater on next
hub

PLC
21200

ControlNet Coax Repeaters

A coax repeater connects coax cable segments together

and boosts the signal as it passes from one segment to the
other. If you connect 2 segments together with a repeater
you could have up to 96 devices on a ControlNet network,
since each segment can contain up to 48 devices. Since
ControlNet supports 99 nodes, you will have to have a
minimum of 2 repeaters to get all 99 nodes.
This segment has 3 devices. The repeater will count
as a device on each segment. Each segment is
compared to the charts on the previous pages
individually to verify it is within specification.

Coax
Repeater

Repeaters connect through a

tap just like any other device

PLC
21200

ControlNet Coax Repeaters

To create a coax repeater unit you simply add a coax

repeater module to the repeater base. Since each repeater
module has 2 ports on it, you could go off in two different
directions. You can connect the tap from the coax repeater
directly to a network segment. You do not have to go to
another repeater unit (although you can).

RPA

Coax repeaters can

be used to connect
directly to another
segment, or to
connect to another
repeater unit.

RPCD

RPA

RPCD

Unused ports on a
coax repeater should
have a standard 75
ohm coax trunk cable
terminator (1786-XT)
attached to maintain
network integrity

PLC
21200

ControlNet Fiber Repeaters

Fiber optic cabling tends to be more expensive than coax.

However, fiber does provide the following advantages:
Provides access to environments that contain explosive gases
(areas requiring intrinsic safety)
Cable can be run outdoors
Can be run in high electrical noise environments without
interference to the signal
Extends distances far beyond coax
Example - Fiber run
outdoors over long
distances

Building A
Coax cable
Fiber
Repeater

Fiber cable

Building B
Coax cable
Fiber
Repeater

PLC
21200

ControlNet Fiber Repeaters

To create a fiber repeater unit you simply add a fiber

repeater module to the repeater base. Since each repeater
module has 2 ports on it, you could go off in two different
directions. Fiber repeater units are generally connected to
other fiber repeater units. The end nodes are typically
connected to the coax segments, which are connected to
the repeater base.
RPA

RPFS

Drive

RPA

RPFS

There are some drives

that connect directly to
the fiber module. See
the products section
for more details.

PLC
21200

ControlNet Repeater Hub Application Example

PLC

PLC

PLC

PLC

Coax Segment

Coax Segment

Coax Segment
Coax Segment
RPA
To other
ControlNet
products

RPFS RPCD

To other
ControlNet
products

RPA

RPFS RPFM

To other
ControlNet
products

Fiber Segment
(Point-to-point)

Note that fiber and coax

repeaters can be added
to the same base.

RPA Starter Block required at each

location. However the coax is not
required to be used

Repeater devices used in this example:

RPA - Fiber Hub Starter Block
RPFS - Fiber Hub Short Distance Module (up to 300m)
RPFM - Fiber Hub Medium Distance Module (up to 3km)
RPCD - Coax repeater

RPA

RPFM

Fiber Segment
(Point-to-point)

RPA

RPFS RPFM

1336T
Drive
1336T
Drive

Fiber Segment
(Point-to-point)

PLC
21200

ControlNet Repeaters

A repeater counts as a device on a segment, but does not

require a node address. Therefore, repeaters will not
detract from the 99 available node addresses on a
ControlNet network.
You can have up to 20 repeaters in series*. This means if
you go from any point on the network to any other point you
cannot cross through more than 20 repeaters.
Repeater

Repeater

Repeater

Repeater

This network uses 4 repeaters

but the worst case is 2 in series.
*Series A of the 1786-RPA only supported 5 repeaters in series.
Also you cannot exceed the max. propagation delay of 121 usec.

Repeaters can also

be used to create
different cabling
topologies other
than a straight bus.
This can make
cabling easier and
less expensive.

PLC
21200

ControlNet Maximum Distance

You can never exceed the 121 usec of propagation delay in media between any two
ControlNet nodes. Use the table in the ControlNet Fiber Media Planning & Installation
Guide.
The maximum distance two ControlNet nodes can be apart is ~20 Km. This would use
2 1786-RPA, 2 1786-RPFRXL and 20 Km of fiber cable (max. distance of the 1786RPFRXL) and short coax runs to the ControlNet nodes. The propagation delay for this
system is 2.9 usec for repeaters and 100 usec for fiber cable which is under the 121
usec propagation delay limit.

PLC
21200

ControlNet Fiber Ring Repeaters

Fiber optic ring repeaters can be connected in a ring such

that there are two paths between any two repeaters. The
signal travels in both directions on the ring. This allows the
network to remain functional with a single break in the
cabling.
RPA

RPFRL

You can have up to 20

repeaters in the ring.
RPA

RPA

RPFRL

RPA

This repeater is used only to

extend the distance.

RPFRL

RPFRL

Each port has both a

transmit and receive.
Two channels are
used so the device
can communicate in
either direction

PLC
21200

ControlNet Fiber Ring Repeaters

It is not recommended to mix ring repeaters with other

repeaters in the same architecture.
If an architecture would require mixing fiber ring repeaters
and other repeaters, factory application assistance is
required.

This architecture mixes ring

repeaters in a ring topology
with coax repeaters..

A fiber ring can not be used with coax

media redundancy.
RPA
RPA

RPCD

RPA

RPFRL

RPCD
RPA

RPA

RPFRL

RPA

RPFRL

RPFRL

PLC
21200

Coax Media Redundancy

ControlNet supports coax media redundancy. Coax media

redundancy is where two taps are run to a device. Each of
the taps connects to a different physical cable segment.
Media redundancy provides protection against a single
break in the cable system taking down the network.

Cable A
RPA

RPCD

RPA

RPCD

RPA

RPCD

RPA

RPCD

Cable B

PLC
21200

Coax Media Redundancy

Note that coax media redundancy does not protect against

breaks in on both channels, even if it appears that there
would be a path for the signal to get through. The devices
use the rates of errors on each channel to determine which
channel to transmit on. If both channels have breaks, then
devices will detect high error rates on both channels and
switch back and forth between channels looking for a good
channel to transmit on.

Cable A

Cable B
The network does not
function correctly with breaks
in 2 places.

RPA

RPCD

RPA

RPCD

RPA

RPCD

RPA

RPCD

PLC
21200

Coax Media Redundancy Notes

Requires that all products on the network be connected in a redundant

fashion so the system can operate redundantly
temporary devices connected through NAP port do not have to be
redundant
Products which support redundant media may be connected to a nonredundant media system and configured to use one channel only.
Dont cross channels. It will cause incorrect LED indications and create
lots of confusion.

Products that support media redundancy will

have 2 BNC connectors on them. The channel
As on all devices should be connected to the
same segment, and the channel Bs of all
devices should be connected to the same
segment.

ControlNet

PCICS

PLC
21200

Fiber Ring Repeaters and Coax Media

Redundancy

The fiber optic ring repeaters cannot be used in a redundant

coax media system when they are connected in a ring.
However, the fiber optic ring repeaters can be used linearly,
like the other fiber repeaters. When used linearly, as shown
below, they can be used in a redundant coax media system.

Cable A
RPA

RPFRL

RPA

RPFRL

Cable B
You could not create a ring of
repeaters here because the
repeaters are used in a
redundant media system.

RPA

RPFRL

RPA

RPFRL

PLC
21200

TNC Media Products-for high vibration and

water

ControlNet - Premier Industrial Network for Control of I/O

Due to the harsh industrial environment which ControlNet is targeted,
ruggedized IP67 media using a TNC design has been developed to
ease installation and prevent downtime.
Typical ControlNet BNC and Ethernet RJ45 connectors are not
designed to withstand high vibration, water, etc.
Availability of Ruggedized IP67 Media further positions ControlNet
as the standard Industrial Network Backbone
Instead of the BNC twist and lock you have TNC screw treads and
o-rings

PLC
21200

TNC Media Products-and/or for moving

enclosures

There are 3 TNC taps for 3 different drop

cable configurations; straight BNC end,
right angle TNC end and straight BNC end.
Most ControlNet devices use a BNC
Connector. Armor Point devices use
a TNC connector.
What are the differences between the
regular taps and the TNC Tap?
- Water Tight up to IP67
- Shock/Vibration specs up to 10g (as
opposed to 2.5g for BNC)
- Drop cable is removable no need to
remove tap body from main trunk line when
enclosure is being moved or replaced.

PLC
21200

Intrinsically Safe ControlNet Ex (1797) Media

designed to operate in a hazardous area

Intrinsically Safe (IS) is an attribute applied to electrical equipment that is

designated for use in explosion-prone areas. IS devices are designed to
not contain any components that produce sparks or contain components
which can hold enough energy that could produce a spark.
With RA IS products there are two ways to get to the Hazardous Area:

PLC
21200

See CNET-IN003A-EN-P ControlNet Ex Media

Planning & Installation Manual for Details

ControlNet Ex Media is a bright blue color.

Second way to get to the Hazardous Area:

PLC21200
ControlNet Products

(Confidential For Internal Use Only)

Copyright 2007 Rockwell Automation, Inc. All rights reserved.

32

PLC
21200

ControlNet Products Hardware and Software

This section is meant to be used as overview of ControlNet products available from Rockwell
Automation. While this section will give you a good idea of the suite of ControlNet products
available, it is not intended to give you a complete understanding of each of the individual
products.
For a comprehensive listing please visit the ControlNet International web site at
www.ControlNet.org.

PLC
21200

ControlNet Hardware Product Classes

Media
Then in Descending order of complexity
Scanner - can control I/O and initiate transactions (also keeper functionality)
SCHEDULED and unscheduled
PLC-5C, 1747-SCNR, 1756-CNB(R), 1756-CN2(R), 1769-L35CR, 1769-L32C, 1784-KTCS,
1788-CNC(R), 1788-CNF(R), 1784-PCICS
Adapter - can respond and send I/O data back to Scanner
SCHEDULED and unscheduled
1771-ACN(R), 1747-ACN(R), 1794-ACN(R), 1797-ACN(R),1734-ACNR, 1738-ACNR
1788-CN2DN
PanelView Plus, PanelView and PanelView E
1203-CN1, 20-COMM-C, 22-COMM-C
Messaging - can initiate unscheduled transactions
unscheduled only, upload/download/online monitor
1784-KTCX15, PCC, PCIC; 1770-KFC, 1747-KFC15

PLC
21200

ControlNet Media Products

ControlNet Media Products are broken down into two categories;

Standard
Coax cable with BNC connectors (1786)
Coax repeater (1786)
Fiber Short Distance cable and Repeater (1786)
Fiber Medium, Long and Extra Long Distance Repeaters (1786)
Specialty
Coax cable with TNC connectors (1786)
Intrinsically Safe Coax cable with BNC connectors (1797)
Intrinsically Safe Fiber Repeater (1797)

PLC
21200

ControlNet Coax Cable

Rockwell Automation has two types of ControlNet

coax cable;
1786-RG6, quad shield coax cable
1786-RG6FA, high flex quad shield coax cable
The 1786-CTK (ControlNet Toolkit) is used to place BNC
and TNC connectors on the ends of the cables.
In addition to the coax cable and connectors, you will
need terminators,taps, and barrel connectors. Bulkhead
and bullet connectors as well as dummy loads are
available. See the ControlNet Cable Planning and
Installation Manuals for more details.

PLC
21200

ControlNet Repeater Family

1786-RPA & 1786-RPCD

PLC
21200

Short Distance Fiber Media for the 1786-RPFS

Pre-made fiber cables with V-pin connectors for use with the 1786-RPFS
in lengths of
10, 20, 60, 100, 200, and 300 meters
1786-FSB500 500 m Bulk short distance fiber cable to be used with the
1786-FSKITV-pin connectors for the short distance fiber cable

PLC
21200

Medium, Long and Extra Long Fiber Media

Rockwell Automation does not sell fiber for the medium, long and extra
long fiber repeater products.
You need to purchase the fiber and the ST plastic or ceramic connectors
from a third party.
1786-RPFM,-RPFRL, -RPFRXL use 62.5/125 micron multi-mode fiber
1786-RPFRXL can also use 9/125 micron single mode fiber

PLC
21200

ControlNet Scanners-I/O Family Limitations

Make sure you are aware of the following remote I/O limitations;
The Logix ControlNet Scanner cannot control 1746 I/O remotely over
ControlNet.
PLC-5C cannot control 1756 I/O remotely over ControlNet.
The SLC ControlNet Scanner cannot control 1756 I/O remotely over
ControlNet.

PLC
21200

ControlNet Scanners-Logix can have

multiple ControlNet Scanners

PLC-5 has a built in ControlNet scanner. You select either a

-L20C15, -L40C15, or -L80C15 based on the number of scheduled
(ControlNet remote I/O) connections you need or if you need ControlNet
hot backup functionality.
Logix allows for multiple ControlNet scanners. You can add another
ControlNet scanner if you need to add more ControlNet remote I/O. Or
you can choose to segregate your ControlNet HMI traffic from your
ControlNet remote I/O traffic. Or you can choose to segregate your
ControlNet traffic by different areas of the plant to more easily schedule
partial plant shut downs.

PLC
21200

ControlNet Adapters-Special Notes

Logix cannot talk to 1771 analog I/O with a scheduled connection.

Rather you must write a MSG instruction (unscheduled) and select the
Message Type of either Block Transfer Read or Block Transfer Write.

PLC
21200

ControlNet Software

There are 3 major software components used when working with a ControlNet
network.
RSNetWorx for ControlNet - This is a network commissioning tool. It is required on
any network that will use scheduled communications. RSNetWorx is the only
software tool that can create the schedule for a ControlNet network. RSNetWorx is
also used to configure individual connections when using a PLC-5 or SLC scanner.
RSLinx - This is the software package that contains all the drivers for the
communication cards in a computer. RSLinx is the actual gateway to the network
for all other software packages residing on the computer. RSNetWorx for
ControlNet communicates through RSLinx.
RSLogix 5000 - This is the logic programming software for Logix controllers. It is
also where individual ControlNet connections must be configured for Logix
controllers before they can be scheduled by RSNetWorx.

PLC
21200

ControlNet Software

A user would use the software in the following manner.

1 RSLinx would be used to configure the drivers for the communication card(s). This
would allow other software packages the ability to communicate on the network.
2 If using a Logix controller, RSLogix 5000 would be used to configure the connections
(who should talk to who) to each device.

- or 2 If using a PLC-5 or SLC, RSNetWorx would be used to configure the connections (who
should talk to who) to each device.
3 RSNetWorx is used to configure network parameters (such as SMAX) and schedule
the network. Without actually scheduling the network, none of the connections
configured will work.

PLC
21200

ControlNet Software
RSLogix5

RSLogix500

RSLogix5000

RSNetWorx

RSLinx
ControlNet Card
1784-KTCX,1770-KFC,1784-PCC,1784-PCIC, 1784-PCICS

Ethernet
Card

DH+
card

ControlNet

Device

Device

RSLinx
Gateway

ControlLogix

ControlNet

Device

Device

PLC
21200

RSNetWorx for ControlNet

Graphical
Network
Configuration
Tool

Configures Network-wide parameters

Network Update Time
Scheduled Maximum Nodes
Unscheduled Maximum Nodes
Physical Media Configuration (must be entered for proper slot time calculation)

PLC
21200

RSNetWorx for ControlNet

Builds the schedule for the entire network

Includes PLC-5 and SLC Scanner configuration tool (SCT)
All Logix controllers SCT in RSLogix 5000
KTCS SCT in IOLinx

Offline configuration for PLC-5, SLC and Logix controllers (V12)

PLC
21200

RSLogix 5, RSLogix 500, RSLogix 5000

Program monitoring and editing

Simple Windows Interface
Drag-and-drop; Right-mouse
All packages present similar interface

Context-sensitive Online Help

Project Reports
Supports PLC-5, SLC, and Logix platforms
RSLogix 5 for PLC-5
RSLogix 500 for SLC
RSLogix 5000 for Logix
Contains the Logix Scanner Configuration Tool (SCT)
Exchanges ControlNet information with RSNetWorx

PLC
21200

RSLinx

Communication interface to networked devices for Windows

applications
Provides a customer with a common driver set for multiple applications
Contains ControlNet drivers:

1784-KTCX15
1784-KTCS
1784-PCC
1784-PCIC
1784-PCICS
1770-KFC15
1770-KFCD15

RSLinx has a C API for custom applications

RSLinx is a DDE/OPC Server for HMI applications
Graphical RSWho and Diagnostics