ControlNet Phase 1.

5









Rockwell Automations
Automation and Control Network
Rockwell Automation
Network Positioning
Information
Device
Automation and Control
2 4 v d c
509 -BOD
T
Information Network Requirements
Information
Link between the plant floor and
the Manufacturing Execution
Systems (MES)
Connectivity to multiple vendors
host computers
Large networks with capacity for
transfer of large data files
Standard network management and
troubleshooting tools
2 4 v d c
509 -BOD
T
Defacto-standard 10 Mega Bit network for data transfer
Standard media and software components
Connectivity to all computer manufacturers and
software - customers can choose the vendor they prefer
Full client-server built into PLC processors
Most media types supported: twisted pair, thin and
thick wire coax, fiber, radio, satellite
Standard network management software: SNMP
Allen-Bradley support in PLC5Es, programming
software, programming cards, Ethernet Gateway,
Control Co-processor, ControlView Software
Core Information Network: Ethernet TCP/IP
Wire replacement
Small physical device size
Low node cost relative to device
Deterministic and repeatable performance
Bandwidth for device configuration and diagnostics
Controller/System support
Multi-vendor device support
Device
2 4 v d c
509 -BOD
T
Device Network Requirements
2 4 v d c
509 -BOD
T
Easy to use low level device network
Optimized for collecting data and diagnostics from
low level devices
Reduced wiring and hardware costs
Reduced start-up and maintenance time
Increased device diagnostics and trouble shooting
CAN based - use of standard chips
Over 100 companies actively developing products
Allen-Bradley products include: 1771 and 1746
scanners, bar code scanners, configuration
software, sensors, drives, SMP-3
TM
, media, 1770-KFD,
Redi-STATION
TM

Core Device Network: DeviceNet
Real - time I/O data
Deterministic and repeatable
Controller-to-controller interlocking data
Deterministic and repeatable
Controller-to-controller messaging data
As time allows
Program upload/download data
As time allows
Diagnostics and MMI support
Control Network Requirements
Automation and Control
2 4 v d c
509 - BOD
T
Rockwell Automation
Communications Strategy
Information
Discrete Device
Automation and Control
24vdc
509 -BOD
24vdc
509 -BOD
To be the foundation of Rockwell Automations and
other Automation System Suppliers control
architectures by providing reliable high-speed
transport of application information.
Two types of information are supported on a single physical cable:

Time critical control and I/O data - I/O update and peer to peer interlocking
Given highest priority
Deterministic and Repeatable

Non-time critical information- messaging and program upload/download
Given lower priority
Not allowed to sacrifice performance of control and I/O data
ControlNets Mission
High-speed (5 Mbits/sec) control and I/O
network
Improved I/O performance
Improved peer to peer communications
Advanced network capabilities
Deterministic - know when data will be transmittted
Repeatable - transmit times are constant, even as
devices enter and leave the network
Producer/Consumer model: multimaster, multicast
inputs, and peer-to-peer
Flexible installation options
Placement of devices anywhere along trunkline
Media redundancy (option)
Support for up to 99 nodes on the same physical link
ControlNet provides
the features that are
not available by any
single network on the
market today.
ControlNet Features
Flexible control system architectures
Single network for programming and I/O
Network access from every node - even adapters
Simplified/Enhanced user programming
User-selectable control and I/O update rates
Update rates constant with addition and/or removal of nodes
Elimination of block transfer programming to remote racks
On-line feedback of bandwidth utilization
Open Network
Technology enablers available for other Automation Suppliers
Rockwell Automation Products
PLC-5Cs, 1771 and Flex I/O adapters, Panelview MMI, PC cards, AC
drives, motor protectors, programming and config s/w
ControlNet Features
Media is RG-6/U coax cable
Standard cable used by cable TV industry ( 75 ohm)
Inexpensive ( < .10 / ft)
Noise immune ( 2 foil plus 2 braided shields)
Available in several types (plenum, high flex, armor) from several vendors
Connectors are standard BNC type
Available from several sources
Custom designed Tap matches the device to the cable to prevent
reflections and provides for simple installations
Tap placements anywhere along the trunk are permitted

Node Node
Node Node
75
75
Tap Separation
(No Min.
Drop Cable
1 meter
Trunk Cable
Termination
Required
Trunk Cable
Node
Tap
Required
ControlNet Physical Layer
ControlNet Media Layer Details









Rockwell Automations
Automation and Control Network
A Tap is required for every permanent
node on the network








Four types available to meet aplication
needs: Y or T, straight or right ended
Network Access Port (NAP) is built into
all products to allow temporary access to
the network and/or products attached.
A B
NAP
A
B
ControlNet
LED's
Network
Access
Port (RJ45)
Coax
Media
Connection
Module Face Plate
(Typical)
Network Connection
No complex formulas are required to determine the
maximum segment length allowed
A single segment can have between
2 nodes at 1000 m, and
48 nodes at 250 m
A subnet can consist of...
a maximum of 99 addressable nodes
Number of devices
2 16 32 48
250
500
750
1000
Coax
Trunk
Cable
Length
M
E
T
E
R
S
Coax Trunk Segment Specification
Single
Segment
Chart
No repeater
required if your system
falls in this area
Repeater required
if your system falls
in this area
Using repeaters, ControlNet supports alternate media
topologies including Bus, Tree, Star, or any combination
Stand-alone coax versions available for high voltage AC or low voltage
DCpower ( 1786-RPT or 1786-RPTD)
Connects using a standard Tap at any location on the coax segment
Does not need to be at the end of a segment
Fault relay for diagnostic feedback to your control system
Applications for Coax Repeater:
Extend the physical length, Increase the number of nodes
Star
Tree
Coax Repeater
R R
R R
R
R R
R R R
Modular Repeater Architecture
New modular repeater design :
Supports from 2 to 8 ports of many
different media types:
Mix and match different media types on
the same repeater!
Initial offering: 3 Fiber Optic Modules:
covers three distance ranges:
300m, 3km and 12km (future)
24VDC power connected to the adapter
(1786-RPA) supplies power to modules
DIN rail mountable
Rebuilds signal (does not pass noise)
Diagnostic status LED on every port
Fault relay for diagnostic feedback to
control system
Applications
Extend the physical length, Intrinsically
Safe, outdoor cable routing, high-noise
environments
Available NOW
1786-RPFS Short
Distance Fiber Module
1786-RPA Modular
Repeater Adapter
1786-RPFM Medium
Distance Fiber Module
ControlNet Fiber Optic Hub
Application Example
PLC
RPA RPFS
Coax Segment
PLC
RPA RPFS
Coax Segment
PLC
RPA RPFM
Coax Segment
Fiber Segment
(Point-to-point)
Fiber Segment
(Point-to-point)
To other
ControlNet
products
To other
ControlNet
products
To other
ControlNet
products
RPFS RPFM RPA
1336T
Drive
RPA - Fiber Hub Starter Block
RPFS - Fiber Hub Short Distance Module (up to 300m)
RPFM - Fiber Hub Medium Distance Module (up to 3km)

Starter Block required at each location , however
the Coax is not required to be used
Up to four (4) modules connected to each Starter Block
Coax segments are standard segments (distance, drops, etc.)
Total nodes in this system remain at 99 (this is not a bridge)
RPFM
Fiber Segment
(Point-to-point)
1336T
Drive
Phase 1.0/1.25
maximum of 5 repeaters in series
Phase 1.5
Software determines how many repeaters based on signal
propagation delay through the system.
Phase 1.5 rules of thumb for repeaters
Maximum delay is less of (NUT-1ms/SMAX, 120 us)
coax cable km counts for 4.1us
fiber cable km counts for 5.1 us
coax repeater counts for 1 us
fiber repeater counts for 1.2 us
New Rules For Number
Of Repeaters
EXAMPLE: NUT=10 ms SMAX=20 5km coax 10km fiber
max delay=(10-1/20) ms=9/20 ms=450 us. 450>120, so max=120 us
repeater delay=120-(5*4.1)-(10*5.1)=120-20.5-51=48.5 us
you could have 48 coax repeaters or 40 fiber repeaters (or a mix)
BONUS PROBLEMS - MEDIA

CABLE STRIP DEMO

ControlNet Products









Rockwell Automations
Automation and Control Network
Functionally patterned after NP5
I/O, memory, and instruction set
Rotary switches for network address
I/O Processing Enhancements:
No rack addressing limitations (i.e. 1/4 rack)
I/O updates < 1ms/rack
Block Transfers executed remotely by adapters
I/O and controller-to-controller interlocking
data mapped-in once
Immediate data input/output instructions
Cat. No. 1785-L20C15, -L40C15,-L8015C (No
series E -L60C15. Can flash existing L60C)
Communication Channels
ControlNet Ports
Redundant media BNCs
Network Access Port
Serial channel (RS232C)
DH+/RIO
5/20C - 1 fixed DH+, 1 Configurable DH+/RIO
5/40C - 2 Configurable DH+/RIO
Network Address
Rotary Switches
Redundant Coax
Cable Connectors
Network
Access Port
A B
1
2
1
2
A
B
Battery
PLC-5/40C

Programmable
Controller


Prog

R
E
M

Run
BATT
PROC
FOR
COMM
A
B
Programmable Controllers
Functionally patterned after 1771-ASB
Rotary switches for network address
Remaining parameters configured in software
Four (4) dot matrix LEDs for node address
indication and advanced diagnostics
Mode indication
Fault indication (i.e. RUN, CBLE FALT)
Cat. No. 1771-ACN15
ControlNet Ports
Non-redundant media BNC


Network Access Port
Cat. No. 1771-ACNR15
ControlNet Ports
Redundant media BNCs
Network Access Port
A
B
A # 1 2
1771-I/O Adapters
A B
ControlNet
Active

Rack

I/O

(Important - Entire network
will be non-redundant)
Pen push switches for setting network address
Remaining parameters configured in software
Cat. No. 1794-ACN15
ControlNet Ports
Non-redundant media BNC
Network Access Port
Cat. No. 1794-ACNR15
ControlNet Ports
Redundant media BNCs
Network Access Port

ControlNet
Adapter
Flex I/O Adapter
KTC KTCX
ControlNet ControlNet
A
B
Functionally patterned after KT
Multiple modes to support various functions
KT Emulation
ControlNet-native messaging
Cat. No. 1784-KTCX15
ControlNet Ports
Redundant Media BNCs
Network Access Port
Applications: Programming, troubleshooting, dedicated
MMI, and general purpose
Cat. No. 1784-KTC - discontinued for phase 1.5
Can flash upgrade a phase 1.25
Network Access Port only
Applications: Programming and/or troubleshooting
Programming Interface - KTCX
Programming Interface - KFC
Functionally patterned after 1770-KF2
Approximately half the size of the 1770-KF3 (6.5 X 4.5 X 2)
Multiple modes to support various functions
KF2 Emulation
ControlNet-native messaging
Cat. No. 1770-KFC15, 1770-KFCD15 (24VDC)
Communication channels
ControlNet Ports
Redundant media BNCs
Network Access Port
Serial channel (38.4 k baud RS232C)
Parallel channel
Applications
PCs (notebook, laptop, desktop)
Hosts, Modems, other automation devices
HEALTH
COMM
1770-KFC
PARALLEL
SERIAL
A
B
Products Under Development
1784-PCC (PC card) for ControlNet With RSLinx Rel 2.0
messaging only
WIN 95 driver in RSLinx (2.0)
1785-L46C - secure processor Available Now
1747-ACNR - 1746 I/O adapter 1QCY98 (target)
1747-SCN/R - 1747 Scanner 3QCY98 (target)
1747-KFC15 - Serial to SLC 1QCY98 (target)
I/O Linx for ControlNet 1QCY98 (target)
1784-KTCS - ISA/EISA 1QCY98 (target)
1784-PCICS -PCI 2QCY98 (target)
ControlLogix
Gateway (1756-CNB) 1QCY98
Control System 2QCY98 (target)
1788-CN2FF - ControlNet to H1 Linking Device TBD
1788-CN2DN - ControlNet to DeviceNet Linking Device TBD
Products Under Development
Dummy load terminator Available Now
Drives
1336T Force - direct connect (fiber) 12/97
1395 DC Drive - direct connect (fiber) 12/97
1203-CN1 - scan port interface 1QCY98
EOI
1000e, 1400e
Unscheduled now
550, 600, 900
Unscheduled 12/97
Intrinsically safe devices
1797-ACNR 2QCY98
Fiber repeater 2QCY98
ControlNet Software









Rockwell Automations
Automation and Control Network
ControlNet Software
PLC I/O
RSLogix5
PLC-5 CCT
RSNetWorx
RSLinx
ControlNet Card
1784-KTCX, 1770-KFC/D, 1784-PCC
RSLinx

RSLogix5

RSNetWorx PLC-5 CCT
RSNetWorx
PLC I/O
Configuration of Network
Online/Offline configuration
Interfaces to RSLinx
ControlNet Card
1784-KTCX, 1770-KFC/D, 1784-PCC
RSLinx

RSLogix5

RSNetWorx PLC-5 CCT
RSNetWorx
Graphical network configuration tool
Configures Network-wide parameters
Network Update Time
Scheduled Maximum Nodes
Unscheduled Maximum Nodes
Physical Media Configuration
Builds the schedule for the entire network
Supports ControlNet 1.5
Uses RSLinx for network communication
Interfaces to PLC-5 ControlNet configuration tool
(PLC-5 CCT)
32-bit, Windows NT
TM
4.0, Windows 95
TM
RSLogix5
PLC I/O
Simple Windows Interface
Drag-and-drop; Right-mouse
Compatibility with Legacy
Products
Compatibility with AI projects
Easy import of 6200 projects
Context-sensitive Online Help ControlNet Card
1784-KTCX, 1770-KFC/D, 1784-PCC
RSLinx

RSLogix5

RSNetWorx PLC-5 CCT
PLC-5 CCT
PLC I/O
Simple Windows Interface
Right-mouse
Map Editing Tool
Maps I/O and scheduled peer to peer
Context-sensitive Online Help
ControlNet Card
1784-KTCX, 1770-KFC/D, 1784-PCC
RSLinx

RSLogix5

RSNetWorx PLC-5 CCT
Provides a customer with a common driver
set for multiple applications
Eliminates driver collisions on the customers
computer
RSLinx has ControlNet drivers for the
1784-KTCX15, 1770-KFC15, 1770-KFCD15
RSLinx has a C API for custom applications
RSLinx is a DDE Server for MMI applications
Graphical SuperWho and Diagnostics
32-bit Windows NT
TM
4.0 (KTCX)
Windows 95
TM
(KFC)
RSLinx
ControlNet Card
1784-KTCX, 1770-KFC/D, 1784-PCC
RSLinx

RSLogix5

RSNetWorx PLC-5 CCT
RSNetWorx & PLC-5 CCT

Need both RSNetWorx and PLC-5 CCT to configure a ControlNet
network with PLC-5Cs
RSNetWorx and PLC-5CCT are integrated for ease of use
Why two tools?
RSNetWorx is for network-wide configuration
PLC-5 CCT is for setting up that particular PLC-5Cs I/O and peer to
peer data
Other controllers have their own programming software with CCTs
Software Products


RSLogix 5/RSNetWorx bundle (9324-RWCNTENE). Includes:
RSNetWorx
RSLogix5
RSLinx lite
PLC-5 CCT
RSNetworx (9357-CNETL3):
RSNetWorx
RSLinx lite
PLC-5 CCT
Future - PLC-5 CCT to be embedded with RSLogix 5
Current RSLogix 5 customers will receive updates while under warranty so if they
purchase RSNetWorx later they will have the PLC-5 CCT.
ControlNet Software
Support for
Windows NT 4.0
Support for
Windows 95
RSLinx
KTCX15, KFC15
RSNetWorx
Yes Yes
RSLogix5
Yes Yes
KTCX15, KFC15
KFCD15 KFCD15
ControlNet Hands-On Lab Set-up
P
L
C
-
5C
S
I
M
P
/
S
1
7
7
1
-
ACN
S
I
M
P
/
S
RSNetworx
RSLogix5
RSLinx
KTCX
ControlNet
NODE 1
I/O Enclosure
P
L
C
-
5C
S
I
M
P
/
S
NODE 2 NODE 3
Processor Enclosure
1794-ACNR
1794-
IE4XOE2
1794-OB16
NODE 4
NODE 20
I
B
D
PERFORM LABS 1 AND 2

ControlNet Technology Overview









Rockwell Automations
Automation and Control Network
ControlNet assures a nodes access to the network with a
patented media access method called Concurrent Time
Domain Multiple Access (CTDMA)
Time slice algorithm where all nodes are kept in synch






Scheduled Data Transfers
Data sent at a deterministic and repeatable rate
Time-Critical I/O and Controller-to-Controller Interlocking
Unscheduled Data Transfers
Data sent as time permits
Non Time-Critical Peer-to-Peer Messaging and Programming Data
ControlNet is a connection-based system using the latest
networking technology - Producer/Consumer Model
Technology Overview
Network
Interval#1
Time
Network
Update Time
Network
Interval#2
Network
Interval#3
Network
Interval#4
Network
Interval#5
Unscheduled
Bandwidth
*
Scheduled
Bandwidth
The Media Access Method
Network Update Interval (NUI)
Scheduled Service
Concurrent
Time
Domain
Multiple
Access
LINK LAYER SERVICES
Unscheduled Service
Network Maintenance Service
the Guardband
Time
Network
Update
Time
(NUT)
ControlNet Definitions
Network Update Time (NUT)- base time at which the
network can transmit data
Network Update Interval (NUI) - one time slot on the
network equal to one NUT
Scheduled Maximum Node Address - Highest network
address of a node that can use the scheduled service
Unscheduled Maximum Node Address - Highest
network address of a node that can use the
unscheduled service
Slot Time - time to wait for a skipped network address
or missing node from the network
Based on the physical attributes of the network
Cable length
Number of repeaters
1
2
3
4


n
The Scheduled Service
1
2
3
4


n
SMAX
Maximum scheduled
network address

Max Schedule Node
is user-selected...

1

3
4


n
This boundary moves
depending on the utilization
of reserved/configured
scheduled bandwidth
each node is allowed to transmit
exactly once during each interval
(Implied token)

nodes wait one slot time for each missing
node (network address)
from 1 to SMAX
Example:
node #3 waits one slot time
because device #2 was
turned off
Time
The Unscheduled Service
7
8
9
UMAX
Maximum unscheduled
network address

Default=99
8
9
10
11


1
2
3

9
10
11
12
permission to transmit is passed
on a round-robin basis
(Implied Token)

nodes wait one slot time for each
missing node (network address)
from 1 to UMAX
each node may
transmit many times
........or not at all
network address from previous
interval plus one gets first
opportunity to transmit in
interval plus one
Time
Technology Example
Network
Update Time
Network
Interval#1
Time
Network
Interval#2
Network
Interval#3
Network
Interval#4
Network
Interval#5
1
2
3
4
3
4
5
1
2

1
2
3
4
5
1




1
2
3
4
4
5
1



Scheduled Unscheduled
Network Interval 1
Scheduled Unscheduled
Network Interval 2
Scheduled Unscheduled
Network Interval 3
The scheduled rotation allows each configured scheduled node one chance
to transmit in each interval.
The unscheduled rotation starts at a different node each interval. During
any one interval each node may have one, many, or no chances
to transmit based on network loading.
IMPORTANT: SMAX and UMAX Notes
Scheduled Maximum Node (SMAX) - Nodes with network
addresses above SMAX will NOT use ControlNets scheduled
service
Implied token during the scheduled service passes from 1 to the value of SMAX
Unscheduled Maximum Node (UMAX) - Nodes with network
addresses above UMAX will NOT communicate at all on
ControlNet
Implied Token during the unscheduled service passes from network address n
to the value of UMAX and then starts over at network address 1
Network address n+1 will be given the opportunity to transmit first in the next
NUI
The configuration of the network (i.e. Scheduled Max Node)
can be changed by the user as his application requirements
change
This may or may not force a change of the NUT
Scheduled application data may have different timing
requirements
Inefficient to send all data at the same rate
Example - Discrete I/O data versus Analog I/O data
ControlNet nodes may support more than one rate up to a
maximum of eight
Most will support a minimum of 2 rates - Fast and Slow
Rates supported will be binary multiples of the NUT
Binary multiples - 1, 2, 4, 8, 16, 32, 64, 128
Each node on ControlNet can be sending at a different rate
User provides a Requested Packet Interval based on
application requirements, ControlNet will meet or beat the
requested time (Acutal Packet Interval indicated) or provide
feedback that the configuration can not be supported
Why Requested Packet Intervals?
ControlNet Packet Structure
Preamble
Start
Delimiter
Source
MAC ID
0 - 510 BytesMax CRC
End
Delimiter
Lpacket Lpacket Lpacket .........
All communication transfers use this packet format
Each node can send one and only one MAC packet at each
opportunity to transmit
Each MAC packet will contain one or more Lpackets
Each Lpacket contains one piece of application information
MAC Packet
ControlNet Data Transfer
Based on the Producer / Consumer Model
A Producer is a sender of data
Producers transmit data packets (Lpackets) on the wire
Lpackets do not contain a destination address or name of the node to receive
the data only a shorthand name called the connection identifier or CID


A Consumer is a receiver of data
Any and all interested consumers can pick Lpackets off the wire by filtering on
the shorthand name (CID)
Many consumers could receive and make use of the data
CID Data (up to 508 bytes)
Example of Lpacket Filtering
using CIDs
PLC-5
Adapter #1 Adapter #2 Adapter #3
Lpacket Lpacket Lpacket
MAC Packet
Lpacket
Lpacket
Lpacket
PLC-5 Transmits 1 MAC packet containing 3 Lpackets
Adapter #1 filters CID #1 and discards CID #2 and #3
Adapter #2 filters CID #2 and discards CID #1 and #3
Adapter #3 filters CID #3 and discards CID #1 and #2
CID #1 CID #2 CID #3
CID #1
CID #2
CID #3
ControlNet
How is Configuration done ?
Customer configures his control system using RSNetWorx
and RSLogix5 either online or offline by selecting the
following:
Network Update Time and Maximum Scheduled Node
How much data the applications (nodes) would like to exchange
How often each application (nodes) would like to send or receive scheduled
data (Expected Packet Interval - EPI)
RSNetWorx completes the following (transparent to the user):
Reserves enough unscheduled bandwidth to support one maximum length
frame per NUI
Provides feedback on:
Is there enough scheduled bandwidth to support the user entered
configuration?
Percent of available scheduled bandwidth that has been reserved
Actual rate the data will be sent (Actual Packet Interval - API)
API will be a binary multiple of the NUT
How does bandwidth get
allocated on ControlNet ?
Network
Update
Time

2 ms

equals
approximately

1250
bytes
Scheduled
Bandwidth
Unscheduled
Bandwidth
One Maximum
Length
Unscheduled
Packet
Maintenance
Available
Scheduled
Bandwidth
For Control
Maintenance
Required
Scheduled
Bandwidth
For Devices

(Extra at users
discretion
Available
Unscheduled
Bandwidth
Default Configuration
includes minimums
User / Tool
Determines Actual
Configuration User Specifies
Maintenance 50
690
510
740
50
100
50
50
50
50
900
350

51%
Bandwidth
Usage
NOTE: Numbers shown are for explanation only (not actuals!)
BONUS PROBLEMS
MEDIA ACCESS

ControlNet Advanced Features









Rockwell Automations
Automation and Control Network
Enhanced system/product features
Multiple controllers controlling I/O on the same link
Multiple controllers sharing input data (multicast)
Scheduled peer-to-peer interlocking between all controllers
Increase the number of mappings on PLC-5
Increased DIF/DOF files and/or sizes on PLC-5
Map discrete data to DIF/DOF files
Process Control Sample Complete (PCSC)
And more!
RSNetWorx for ControlNet Configuration
Improved scheduling of bandwidth usage
Graphical view of network
offline and online capability
ControlNet Phase 1.5
New Features
Multiple controllers controlling I/O
on the same link
PLC-5Cs at any valid node address will be able to listen to
inputs from any rack of I/O
Inputs can be shared between multiple PLC-5Cs (multicast inputs)
PLC-5Cs at any valid node address will be able to control all
of the outputs of a particular rack of I/O at one time
Outputs from any single rack can only be controlled by a single PLC-5C
PLC-5C PLC-5C
1771-ACN
or
1794-ACN
I
I
I
O
O
O
Multicast Inputs
1771-ACN
or
1794-ACN
1771-ACN
or
1794-ACN
ControlNet Network
Only one PLC-5C can
control the outputs in
an I/O rack at a time.
Scheduled peer-to-peer
interlocking between all PLCs
a PLC-5C at any valid node address can be the source
(i.e. producer) initiating a Scheduled Send message
Any other PLC-5C on the network can receive (i.e.
consume) the message using a Scheduled Receive
Multiple PLC-5Cs can listen to or consume the produced Scheduled
Send message (multicast interlocks)
PLC-5C PLC-5C
PLC-5C
ControlNet Network
SPO
SPI
SPO
SPI
SPI
Multicast Interlocks
SPO
SPI
PLC-5C Enhancements
Increased number of mappings
In Phase 1.0...
PLC-5/20C, 5/40C, 5/60C and 5/80C is limited to 64 mappings
In Phase 1.5...see table below.
Increase the number (and size) of the Data Input File (DIF) and
Data Output File (DOF)
In Phase 1.0...
limited to one DIF (1000 words) and one DOF (1000 words)
In Phase 1.5...see table below.
DIF files must be consecutive. DOF files must be consecutive.
DIF and DOF files specified are permitted to overlap
Processor
Type
Number of
Mappings
Number of
DIF Files
Number of
DIF Words
Number of
DOF Files
Number of
DOF Words
PLC-5/20C 64 2 2000 2 2000
PLC-5/40C 96 3 3000 3 3000
PLC-5/60C 128 4 4000 4 4000
PLC-5/80C 128 4 4000 4 4000
PLC-5C Enhancements
Map discrete to DIF and DOF files
In Phase 1.0...
Discrete could only be mapped to I/O image table
In Phase 1.5...discrete can be mapped to I/O, DIF or DOF.
Process Control Sample Complete (PCSC) bit
In Phase 1.0...
no explicit indication of new data for non discrete connections
In Phase 1.5...see table below.
User can configure non-discrete connections to provide a bit to
indicate new data has arrived. Similar to a done bit.
PLC-5C Enhancements
DIF and DOF files can be overlapped - in to out with no ladder
programming
1794 map entry consistent with 1771- 1 entry for discrete and 1 for
each analog
I/O immediate inhibit bit (via ladder)
Maximum data size for scheduled peer increased to 240 words -in
phase 1.0 maximum is 64 words
Maximum number of scheduled messages per device limited only
by total map entries allowed - was 16 in phase 1.0
Added number of listeners in send data status entry
Added multihop messaging via MSG instruction (1756-CNB)
Added CIO support for 1794 (flex) I/O
. . . And more
DEMO THE SOFTWARE
ONLINE AND THEN
PERFORM LABS 3-7

ControlNet Advanced Topics









Rockwell Automations
Automation and Control Network
Immediate Discrete and Block
Instructions

Support for IIN and IOT immediate instructions: single
word updates to/from buffer (cant go across wire).
IDI and IDO block instructions: Up to 64 word block can
be updated to/from the buffer.
Connection Types

Exclusive Owner: Device has exclusive rights to control
the outputs for the map entry. Listens to inputs also. Will
allow other devices to listen to the inputs using a
Multicast connection.
Multicast: Device listens to inputs. Has no ability to
control outputs.
Shared Owner (future - flex only): Device shares control
of the outputs with another shared owner. Only one
device has control at a time. Listens to inputs also.
Multicast Connection Errors

1771-ACN(R): If the exclusive owner connection is lost
all multicast connections will be lost.
1794-ACN(R): If the exclusive owner connection is lost all
multicast connections will continue to function (receive
inputs).
ControlLogix(future): Configurable to work like 1771 or
1794 implementation.
The Keeper
Phase 1.5
Keeper
2
FLEX I/O
PLC-5C
1
PLC-5C
3
4
1771 I/O
5
Scanners
- A scanner can open connections to a target
device such as flex or 1771 adapter.
- A Keeper is the node at address 1. It is also a scanner.
PLC-5C
The Keeper
Phase 1.5
The Keeper is the PLC-5C at node address 1.
Need a Keeper to store (keep) the network parameters.
Dont need RSNetworx on-line to attach a device that is
already configured.
The Keeper also stores (keeps) the master key for other
scanner class devices.
The master key is a CRC (cylic redundancy checksum)
of that networks configuration data.
At powerup or loss of all connections, a scanner
device will compare its stored key to the Keepers
stored key. If it does not match, the device will not join
the network and not transmit data.
The Keeper
Phase 1.5
If Node 1 is shut down or faults, the network will continue to
function.
If Node 1 has I/O that it owns, that I/O will be effected (will go to
configured safe state).
If another node is added to the scheduled bandwidth or the network
parameters are changed, Node 1 must be present on the network.
Keeper shut down
PLC-5C
2
FLEX I/O
PLC-5C
1
PLC-5C
3
4
1771 I/O
5
Node 2 still controls its I/O
The Keeper
Phase 1.5
If Node 1 is not up on a running network and a
PLC with a node address of anything greater
than 1 goes down and comes back (cable
disconnected), that PLC will not be able to re-
establish the connections to its target
devices.
Keeper shut down
PLC-5C
2
FLEX I/O
PLC-5C
1
PLC-5C
3
4
1771 I/O
5
Distributed Keeper- future
Phase 1.5
If Node 1 is shut down or faults the next highest numbered scanner
node will assume keeper function.
Target for products
Next major ControlNet phase of PLC-5 (NOT next release of PLC-5).
Scanner cards at release (1784-KTCS/PCICS)
1747-SCN/R at release
Next major ControlNet phase of ControlLogix (NOT at release)
NOTE - software changes (RSNetworx) must be made - no
schedule today
Keeper shut down
PLC-5C
2
FLEX I/O
PLC-5C
1
PLC-5C
3
4
1771 I/O
5
Node 2 becomes keeper
Network Configuration
and the Edit Resource
When edits are accepted, the software (RSNetworx)
gets not only the network edit resource, but also the
edit resources for all of the PLC-5Cs on the network
(the PLC-5Cs must be in program mode). This is
known as a full edit.
Currently, the only method of editing a ControlNet
processor or ControlNet network parameters is in full
edit mode. Therefore, when making any changes to
the ControlNet configuration in any PLC-5, all PLC-5s
must go to program mode.
Incremental Edits
(Future)
When editing the map table of a particular PLC-5C, the
software gets the edit resource for that node. The PLC
must be in program mode to edit the map table
If incremental edits are accepted, only the PLCs
affected by the change need to be in program mode
A map entry change can be accepted incrementally as
long as it doesnt increase scheduled bandwidth above
100%
Any network parameter change will still require a full
accept edits
If full edits are accepted, the software (RSNetworx)
gets not only the network edit resource, but also the
edit resources for all of the PLC-5Cs on the nework
(the PLC-5Cs must be in program mode).
Exceeding the Maximum
Transmit Size for a PLC-5C
A single device can transmit up to 510 bytes during the
scheduled interval
If you attempt to configure too many mappings
(exceeds 510 bytes) to a single PLC in any one
network update interval, the configuration software will
provide the following error message Exceeded
Maximum Transmit Size
Possible work around: Based on the configuration,
one option would be to reduce the NUT in half and use
a RPI of 2 times the NUT. Must also be aware of PLC
bandwidth.
Network
Interval#1
Network
Interval#2
NUT = 20 msec. change to 10 msec.
RPI = 20 msec. (2 * 10(NUT))
510 bytes 510 bytes
GO TO SCHEDULED PEER
MESSAGING TALK CHALK AND
COMPLETE LABS 8-11



ControlNet Additional Information










Rockwell Automations
Automation and Control Network
ControlNet Enablers
Applications based on open ControlNet interface products
PC Buses supported:
ISA/EISA
PCI
PC Card
Software APIs/Drivers
RSLinx (messaging)
IOLinx (I/O and peer to peer interlocking)
Specifications

Applications with ControlNet Embedded
Documentation
Training
Hardware components
Transceiver, Transformer, Crystal, ASICs
Example software
Messaging
Adapter
Scanner
Development Tools (Traffic Analyzer / Generator)
Development Kits
Open to all!
From product developers to end-users
Manage ControlNet Technology
Publish Specifications
Publish Test Software, Run Test Centers
Provide forum for directing the future of ControlNet technology and products
Pursue International Standardization
Reduce Vendor Time-to-Market
Promote ControlNet
Manage common marketing efforts of group members
For further information: www.controlnet.org
Information Resources
ControlNet

Intranet sites
Networks web site - www.cle.ab.com:80/networks
ControlNet release 1.5 launchpak
Phase 1.0/1.25 to phase 1.5 migration instructions
contact list
and much more!
Price guide - www.cle.ab.com/cigprice
appendix E is consolidated ControlNet information
Internet sites
ControlNet International - www.controlnet.org
NEW- Networks commercial web site - www.ab.com/networks
Hot link off the main ab web page
Technical Support
ControlNet
Fax Back Application Notes
Fax Back Number: 216.646.5436
Revision History/Firmware (9073)
Operation and Usage/Cabling (9074)
Troubleshooting Tips (9075)
Random & Intermittent Communication Errors (9254)
Exceeded Maximum Transmit Size Error (7826)
Blockages & Out of Step Events (7885)
www@ab.com = Rockwell Automation Tech Support
site
START DAY 2
TROUBLESHOOTING
DISCUSSION AND THEN
PERFORM LABS 12-13 AND
OSCILLOSCOPE DEMO

ADVANCED MODULE
PLACEMENT CHALK TALK

ControlNet Product Phasing and Migration









Rockwell Automations
Automation and Control Network
ControlNet Product Phasing
Phase 1.0/1.25- High-speed RIO/DH+
Centralized control
Single controller controlling I/O
DOS based software tools
Phase 1.5
Decentralized control
Multiple controllers controlling I/O on the same link
Shared inputs and peer-to-peer data
Additional products
Windows based software tools
D
I
N
D
O
U
T
5
4
0
C
A
I
N
A
O
U
T
D
I
N
D
O
U
T
A
C
N
1771 I/O
A
I
N
A
O
U
T
D
I
N
D
O
U
T
5
2
0
C
A
I
N
A
O
U
T
1770-KFC
Serial/
Parallel
DEVICE
DH+
RIO
A
C
N
Flex I/O
D
I
N
D
O
U
T
A
I
N
A
O
U
T
D
I
N
D
O
U
T
5
2
0
C
A
I
N
A
O
U
T
1784-KTX,KT
6200
INTERCHANGE
software
PC
1784-KTCX
6200
INTERCHANGE
software
PC
Network Address 1
Interchange
WinLinx
6200
ControlView
ControlNet
High Speed I/O Network
Scheduled I/O Data
Scheduled Peer to Peer
Unscheduled Messaging
Phase 1 Architecture
Operator
Interface
PV1400E
On-line and off-line configuration
Channel 2 (ControlNet) Configuration
User selectable Network Update Time
I/O mapping of Control and I/O data
Discrete I/O, Non-discrete I/O, Controller-to-Controller Interlocking
User selectable update time per entry
AutoNet - provides automatic identification of remote nodes
AutoMap - provides automatic addressing of mapped devices
Status provided for network and controller resources used: network
bandwidth, number Map Entries, Data I/O files (DIF / DOF)
Ability to launch I/O Config software directly from map table
Diagnostic Functions
WHO function to identify nodes on the network
Network and node counters
Product-specific (i.e. Flex I/O advanced diagnostics)
6200/AI Software
Programming and Network Tool
Migrating To Phase 1.5
Process detailed in launch pack, Networkshomepage (intranet)
and on MKESLAFS file server
Launch Pack: SP-2765
Networks page: http://www.cle.ab.com/networks
MKESLAFS: MKESLAFS\vol1\netfiles\networks\cnet\cnet1_5\upgradekit
GTS representative and AM/Sales rep required to be involved
Marketing contact (currently Doug Wylie) at headquarters will
coordinate with AM/Sales rep/GTS
30 GTS champions were trained in May 1997 in a special class.
We would like 1 of these individuals to be involved.
Step by step instructions and labs available to assist
Hardware Issues
Flash Upgradeable
PLC-5, 1771-ACN(R) series B, and 1784-KTC(X)
Must be replaced
1771-ACN(R) series A, 1794-ACN(R), 1770-KFC
NOTE - While some products are flash upgradeable, The
procedure calls for the ability to go back if problems arise.
Therefore, you will need old and new versions
simultaneously.
Software Issues
All new ControlNet software.
Phase 1.0/1.25 requires 6200 or AI software
Phase 1.5 requires RSNetWorx/PLC-5 CCT
Operating system change.
DOS to WIN 95 or NT
ControlNet Configuration cannot be converted.
ControlNet Advanced Ownership









Rockwell Automations
Automation and Control Network
1771 Ownership Rules
The owner of the discrete connection owns the entire
rack.
Does not support shared owner connections.
A multicast input connection can only listen to inputs
the owner is configured to listen to.
Two different PLCs can control individual modules
in a chassis using CIO instructions (unscheduled).
1794 Ownership Rules
Will support shared owner connections.
shared owner connections must match
Exclusive ownership can be set on a module by
module basis
analog modules
discrete modules if they are mapped separately
discrete rack connections must start at first slot so cannot set up
ownership of 1/2 rack to PLC 1 and 1/2 rack to PLC 2.
Two different PLCs can control individual modules
in a chassis using CIO instructions (unscheduled).
END OF PRESENTATION