Control Net Presentación.ppt

8/10/2019 Control Net Presentacin.ppt

1/95

ControlNet Phase 1.5

Rockwell AutomationsAutomation and Control Network


2/95

Rockwell AutomationNetwork Positioning

Information

Device

Automation and Control

2 4 v d c

509-BOD

T


3/95

Information Network Requirements

Information

Link between the plant floor and the Manufacturing ExecutionSystems (MES)

Connectivity to multiple vendorshost computers

Large networks with capacity fortransfer of large data files

Standard network management andtroubleshooting tools

24vdc

509-BOD

T


4/95

Defacto-standard 10 Mega Bit network for data transfer

Standard media and software components

Connectivity to all computer manufacturers andsoftware - 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, programmingsoftware, programming cards, Ethernet Gateway,Control Co-processor, ControlView Software

Core Info rmation Netwo rk: Ethernet TCP/IP


5/95

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

24vdc

5

09-BOD

T


6/95

Easy to use low level device network

Optimized for collecting data and diagnostics fromlow 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 1746scanners, bar code scanners, configurationsoftware, sensors, drives, SMP-3TM, media, 1770-KFD,Redi-STATIONTM

Core Device Network: DeviceNet


7/95

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


24vdc

509-BOD

T


8/95

Rockwell AutomationCommunications Strategy

Information

Discrete Device


24vdc

509-BOD

24vdc

509-BOD

f f


9/95

To be the foundation of Rockwell Automations and

other Au tomation System Suppl iers con trol

archi tectures by pro viding reliable high-speed

transport o f appl icat ion info rmation.

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


10/95

High-speed (5 Mbits/sec) control and I/Onetwork

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 asdevices enter and leave the network

Producer/Consumer model: multimaster, multicastinputs, 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 providesthe features that arenot available by any

single network on themarket today.

ControlNet Features


11/95

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, ACdrives, motor protectors, programming and config s/w

ControlNet Features


12/95

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 preventreflections and provides for simple installations

Tap placements anywhere along the trunk are permitted

Node Node Node Node

75 75

Tap Separation

(No Min.

Drop Cable1 meter

Trunk CableTerminationRequired

Trunk Cable

Node

Tap

Required

ControlNet Physical Layer


13/95

ControlNet Media Layer Details



14/95

A Tap is required for every permanent

node on the network

Four types available to meet aplicationneeds: Y or T, straight or right ended

Network Access Port (NAP) is built intoall products to allow temporary access tothe network and/or products attached.

A B

NAP

A

B

ControlNetLED's

NetworkAccessPort (RJ45)

Coax

MediaConnection

Module Face Plate(Typical)

Network Connection


15/95

No complex formulas are required to determine themaximum 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


16/95

Using repeaters, ControlNet supports alternate mediatopologies including Bus, Tree, Star, or any combination

Stand-alone coax versions available for high voltage AC or low voltageDCpower ( 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 RR


17/95

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


18/95

ControlNet Fiber Optic HubApplication 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 RPFMRPA

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


19/95

Phase 1.0/1.25 maximum of 5 repeaters in series

Phase 1.5

Software determines how many repeaters based on signalpropagation delay through the system.

Phase 1.5 rules of thumb for repeaters Maximum delay is lessof (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 NumberOf 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)


20/95

BONUS PROBLEMS - MEDIA


21/95

CABLE STRIP DEMO


22/95

ControlNet Products



23/95

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 interlockingdata mapped-in once

Immediate data input/output instructions

Cat. No. 1785-L20C15, -L40C15,-L8015C (Noseries 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 CoaxCable Connectors

NetworkAccess Port

A B

1

2

1

2

A

B

Battery

PLC-5/40CProgrammable

Controller

Prog

REM

Run

BATT

PROC

FOR

COMM

A

B

Programmable Controllers


24/95

Functionally patterned after 1771-ASB

Rotary switches for network address Remaining parameters configured in software

Four (4) dot matrix LEDs for node addressindication 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)


25/95

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


Network Access Port

ControlNet

Adapter

Flex I/O Adapter


26/95

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, dedicatedMMI, 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


27/95

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


Network Access Port

Serial channel (38.4 k baud RS232C)

Parallel channel

Applications

PCs (notebook, laptop, desktop)

Hosts, Modems, other automation devices

HEALTH

COMM1770-KFC

PARALLEL

SERIAL

A B


28/95

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


29/95

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


30/95

ControlNet Software



31/95

ControlNet Software

PLC I/O

RSLogix5

PLC-5 CCT

RSNetWorxRSLinxControlNet Card1784-KTCX, 1770-KFC/D, 1784-PCC

RSLinx

RSLogix5 RSNetWorxPLC-5 CCT


32/95

RSNetWorx

PLC I/O

Configuration of Network

Online/Offline configuration

Interfaces to RSLinx

ControlNet Card1784-KTCX, 1770-KFC/D, 1784-PCC

RSLinx



33/95

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 NTTM4.0, Windows 95TM


34/95

RSLogix5

PLC I/O

Simple Windows Interface Drag-and-drop; Right-mouse

Compatibility with LegacyProducts

Compatibility with AI projects

Easy import of 6200 projects

Context-sensitive Online Help ControlNet Card1784-KTCX, 1770-KFC/D, 1784-PCC

RSLinx



35/95

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


RSLinx



36/95

Provides a customer with a common driverset 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 95TM(KFC)

RSLinx


RSLinx



37/95

RSNetWorx & PLC-5 CCT

Need both RSNetWorx and PLC-5 CCT to configure a ControlNetnetwork 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 topeer data

Other controllers have their own programming software with CCTs


38/95

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.


39/95

ControlNet Software

Support forWindows NT 4.0

Support forWindows 95

RSLinx KTCX15, KFC15

RSNetWorx Yes Yes

RSLogix5 Yes Yes

KTCX15, KFC15

KFCD15KFCD15


40/95

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 2NODE 3

Processor Enclosure

1794-ACNR1794-

IE4XOE2

1794-OB16

NODE 4

NODE 20

I

B

D


41/95

PERFORM LABS 1 AND 2


42/95

ControlNet Technology Overview



43/95

ControlNet assures a nodes access to the network with a

patented media access method called Concurrent TimeDomain 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 latestnetworking technology - Producer/Consumer Model

Technology Overview

NetworkInterval#1

Time

Network

Update TimeNetwork

Interval#2Network

Interval#3Network

Interval#4Network

Interval#5

UnscheduledBandwidth

*ScheduledBandwidth


44/95

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)


45/95

ControlNet Definitions

Network Update Time (NUT)- base time at which thenetwork can transmit data

Network Update Interval (NUI) - one time slot on thenetwork 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 theunscheduled service

Slot Time - time to wait for a skipped network addressor missing node from the network

Based on the physical attributes of the network

Cable length

Number of repeaters


46/95

12

34

n

The Scheduled Service

12

34

n SMAXMaximum scheduled

network address

Max Schedule Nodeis user-selected...

1

34

n

This boundary movesdepending on the utilization

of reserved/configuredscheduled bandwidth

each node is allowed to transmitexactly once during each interval

(Implied token)

nodes wait one slot time for each missingnode (network address)

from 1 to SMAX

Example:node #3 waits one slot time

because device #2 wasturned off

Time


47/95

The Unscheduled Service

78

9

UMAXMaximum unscheduled

network address

Default=99

89

1011

1

2 3

910

1112

permission to transmit is passedon a round-robin basis

(Implied Token)

nodes wait one slot time for eachmissing node (network address)

from 1 to UMAX

each node maytransmit many times

........or not at all

network address from previousinterval plus one gets firstopportunity to transmit in

interval plus one

Time

T h l E l


48/95

Technology ExampleNetwork

Update Time

NetworkInterval#1 Time

NetworkInterval#2

NetworkInterval#3

NetworkInterval#4

NetworkInterval#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 UnscheduledNetwork Interval 2

Scheduled Unscheduled

Network Interval 3

The scheduled rotat ion allows each configured scheduled node one chance

to transmit in each interval.

The unscheduledrotation 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.


49/95

IMPORTANT: SMAX and UMAX Notes

Scheduled Maximum Node (SMAX) - Nodes with network

addresses above SMAX will NOT use ControlNets scheduledservice

Implied token during the scheduled service passes from 1 to the value of SMAX

Unscheduled Maximum Node (UMAX) - Nodes with networkaddresses 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 nextNUI

The configuration of the network (i.e. Scheduled Max Node)

can be changed by the user as his application requirementschange

This may or may not force a change of the NUT

Wh R t d P k t I t l ?


50/95

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 amaximum 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 onapplication requirements, ControlNet will meet or beat the

requested time (Acutal Packet Interval indicated) or providefeedback that the configuration can not be supported

Why Requested Packet Intervals?


51/95

ControlNet Packet Structure

PreambleStart

DelimiterSourceMAC ID

0 - 510 BytesMax CRCEnd

Delimiter

Lpacket Lpacket Lpacket.........

All communication transfers use this packet format

Each node can send one and only one MAC packet at eachopportunity to transmit

Each MAC packet will contain one or more Lpackets

Each Lpacket contains one piece of application information

MAC Packet


52/95

ControlNet Data Transfer

Based on the Producer / Consumer Model

A Producer is a senderof 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 receiverof 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


53/95

Example of Lpacket Filteringusing 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



CID #1 CID #2 CID #3

CID #1

CID #2

CID #3

ControlNet

How is Configuration done ?


54/95

How is Configuration done ?

Customer configures his control system using RSNetWorxand 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 scheduleddata (Expected Packet Interval - EPI)

RSNetWorx completes the following (transparent to the user):

Reserves enough unscheduled bandwidth to support one maximum lengthframe per NUI

Provides feedback on:

Is there enough scheduled bandwidth to support the user enteredconfiguration?

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


55/95

How does bandwidth getallocated on ControlNet ?

NetworkUpdateTime

2 ms

equals

approximately

1250

bytes ScheduledBandwidth

Unscheduled

Bandwidth

One MaximumLength

UnscheduledPacket

Maintenance

AvailableScheduledBandwidthFor Control

Maintenance

RequiredScheduled

BandwidthFor Devices

(Extra at usersdiscretion

AvailableUnscheduled

Bandwidth

Default Configurationincludes minimums

User / ToolDetermines Actual

ConfigurationUser Specifies

Maintenance 50

690

510

740

50

10050

50

50

50

900

350

51%

BandwidthUsage

NOTE: Numbers shown are for explanation only (not actuals!)


56/95

BONUS PROBLEMSMEDIA ACCESS


57/95

ControlNet Advanced Features


ControlNet Phase 1 5


58/95

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.5New Features

Multiple controllers controlling I/O


59/95

Multiple controllers controlling I/Oon the same link

PLC-5Cs at any valid node address will be able to listen toinputs 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


60/95

Scheduled peer-to-peerinterlocking 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 ScheduledSend message (multicast interlocks)

PLC-5C PLC-5C

PLC-5C

ControlNet Network

SPO

SPI

SPO

SPI SPIMulticast Interlocks

SPO

SPI

PLC-5C Enhancements


61/95

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) andData Output File (DOF)

In Phase 1.0...

limited to one DIF (1000 words) and one DOF (1000 words)


DIF files must be consecutive. DOF files must be consecutive.

DIF and DOF files specified are permitted to overlap

ProcessorType Number ofMappings Number ofDIF Files Number ofDIF Words Number ofDOF Files Number ofDOF 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


62/95

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


User can configure non-discrete connections to provide a bit toindicate new data has arrived. Similar to a done bit.

PLC-5C Enhancements


63/95

PLC-5C Enhancements

DIF and DOF files can be overlapped - in to out with no ladderprogramming

1794 map entry consistent with 1771- 1 entry for discrete and 1 foreach 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 onlyby 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


64/95

DEMO THE SOFTWAREONLINE AND THEN

PERFORM LABS 3-7


65/95

ControlNet Advanced Topics


Immediate Discrete and Block


66/95

Instructions

Support for IIN and IOT immediate instructions: singleword 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


67/95

Connection Types

Exclusive Owner: Device has exclusive rights to controlthe outputs for the map entry. Listens to inputs also. Willallow other devices to listen to the inputs using aMulticast 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 onedevice has control at a time. Listens to inputs also.

Multicast Connection Errors


68/95

Multicast Connection Errors

1771-ACN(R): If the exclusive owner connection is lostall multicast connections will be lost.

1794-ACN(R): If the exclusive owner connection is lost all

multicast connections will continue to function (receiveinputs).

ControlLogix(future): Configurable to work like 1771 or1794 implementation.

The Keeper


69/95

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


70/95

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 isalready configured.

The Keeper also stores (keeps) the master key for otherscanner class devices.

The master key is a CRC (cylic redundancy checksum)of that networks configuration data.

At powerup or loss of all connections, a scannerdevice will compare its stored key to the Keepersstored key. If it does not match, the device will not jointhe network and not transmit data.

The Keeper


71/95

p

Phase 1.5

If Node 1 is shut down or faults, the network will continue tofunction.

If Node 1 has I/O that it owns, that I/O will be effected (will go toconfigured 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


72/95

p

Phase 1.5

If Node 1 is not up on a running network and aPLC with a node address of anything greaterthan 1 goes down and comes back (cabledisconnected), 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


73/95

p

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 todayKeeper 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


74/95

gand the Edit Resource

When edits are accepted, the software (RSNetworx)gets not only the network edit resource, but also theedit resources for all of the PLC-5Cs on the network(the PLC-5Cs must be in program mode). This isknown as a full edit.

Currently, the only method of editing a ControlNetprocessor or ControlNet network parameters is in fulledit mode. Therefore, when making any changes tothe ControlNet configuration in any PLC-5, all PLC-5smust go to program mode.

Incremental Edits


75/95

(Future)

When editing the map table of a particular PLC-5C, thesoftware gets the edit resource for that node. The PLCmust be in program mode to edit the map table

If incremental edits are accepted, only the PLCsaffected by the change need to be in program mode

A map entry change can be accepted incrementally aslong as it doesnt increase scheduled bandwidth above100%

Any network parameter change will still require a fullaccept edits

If full edits are accepted, the software (RSNetworx)

gets not only the network edit resource, but also theedit resources for all of the PLC-5Cs on the nework(the PLC-5Cs must be in program mode).

Exceeding the Maximum


76/95

gTransmit Size for a PLC-5C

A single device can transmit up to 510 bytes during thescheduled 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 willprovide the following error message ExceededMaximum Transmit Size

Possible work around: Based on the configuration,one option would be to reduce the NUT in half and usea RPI of 2 times the NUT. Must also be aware of PLCbandwidth.

NetworkInterval#1

NetworkInterval#2

NUT = 20 msec. change to 10 msec.

RPI = 20 msec. (2 * 10(NUT))510 bytes 510 bytes


77/95

GO TO SCHEDULED PEERMESSAGING TALK CHALK AND

COMPLETE LABS 8-11


78/95

ControlNet Additional Information

Rockwell Automations

Automation and Control Network

ControlNet Enablers


79/95

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


80/95

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 ResourcesControlNet


81/95

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 SupportControlNet


82/95

ControlNetFax 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)

[email protected] = Rockwell Automation Tech Supportsite


83/95

START DAY 2TROUBLESHOOTING

DISCUSSION AND THEN

PERFORM LABS 12-13 ANDOSCILLOSCOPE DEMO


84/95

ADVANCED MODULEPLACEMENT CHALK TALK

C t lN t P d t Ph i d Mi ti


85/95

ControlNet Product Phasing and Migration


ControlNet Product Phasing


86/95

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

Phase 1 Architecture


87/95

DIN

DOUT

540C

AIN

AOUT

DIN

DOUT

ACN

1771 I/O

AIN

AOUT

DIN

DOUT

520C

AIN

AOUT

1770-KFC

Serial/Parallel

DEVICE

DH+

RIO

ACN

Flex I/O

DIN

DOUT

AIN

AOUT

DIN

DOUT

520C

AIN

AOUT

1784-KTX,KT

6200INTERCHANGEsoftware

PC

1784-KTCX

6200INTERCHANGEsoftware

PC Network Address 1Interchange

WinLinx6200

ControlView

ControlNet

High Speed I/O Network

Scheduled I/O Data

Scheduled Peer to Peer

Unscheduled Messaging

Phase 1 Architecture

Operator

Interface

PV1400E

6200/AI Software


88/95

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: networkbandwidth, 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 SoftwareProgramming and Network Tool

Migrating To Phase 1 5


89/95

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 willcoordinate 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


90/95

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, Theprocedure calls for the ability to go back if problems arise.Therefore, you will need old and new versionssimultaneously.

Software Issues


91/95

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


92/95

ControlNet Advanced Ownership


1771 Ownership Rules


93/95


The owner of the discrete connection owns the entirerack.

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).



94/95


Will support shared owner connections.

shared owner connections must match

Exclusive ownership can be set on a module bymodule basis

analog modules

discrete modules if they are mapped separately

discrete rack connections must start at first slot so cannot set upownership of 1/2 rack to PLC 1 and 1/2 rack to PLC 2.

Two different PLCs can control individual modulesin a chassis using CIO instructions (unscheduled).

END OF PRESENTATION


95/95

Control Net Presentación.ppt

Documents

Transcript of Control Net Presentación.ppt