讲义plc学习-rs5000l教程p

CCS-2

classanizerSection

1CCS-2IntroductionSection

2LogixOverviewSection

3PanelViewSection

7设备Section

8DiagnosticsSection

10ScrollistSection

12Station

LogicSection

9ActionsSection

11CellLogicSection

14Robot

LogicSection

13RobotConceptsSection

16Hard

AutoWeldingSection

15Robot

Logic2Section

6InterlocksSection

5ProgramsSection

4Naming22021/1Next学习目标通过本章学习，您将:掌握DeviceNet基础知识解释设备Input/Output

(I/O)存在的潜在问题描述解决设备I/O潜在问题的方法解释Copy指令的使用方法解释如何使用DeviceNet扫描器模块

I/O32021/1NextDeviceNet标准DeviceNet是一种开放的设备通讯标准Standards

are

maintained

by

theOpen

DeviceNet

Vendors

Association

(ODVA)ODVA

specifies

how

the

devices

interact

on

the

networkHow

the

device

logically

“attaches”

to

the

networkHow

the

device

responds

and

sends

data

on

the

networkHow

the

device

provides

its

data

-

Polled,

Strobed,

Change

of

State

(COS)What

tests

mustbe

performed

for

ODVA

certificationODVA

does

notspecifyWhat

type

or

how

much

data

a

device

producesHow

the

scanner

“maps”

the

devicedataEach

vendor

has

theflexibility

to

decidethisDeviceNet

ODVA

certificationCertification

is

performed

by

a

third

partyDevices

do

not

have

tobe

certified

(thisis

not

an

ODVA

requirement)CCH-1

requires

thatDeviceNet

devices

must

be

certified42021/1NextDeviceNet基础知识DeviceNet网络通讯速率（CCH-1中有相关要求）125Kbps

for

tooling

equipment

(default)250Kbps

notused500Kbps

for

robotprocess

and

end-of-arm

equipment(机器人DeviceNet网络)最多支持64个节点节点数为0-63CCH-1

每个网络的节点数量不超过20新设备的缺省节点地址为63所以不使用＃63节点地址支持多个扫描器在一个网络中CCH-1要求每个网络中只有1个扫描器，节点地址为052021/1NextDNBScannerIODeviceNet

基础知识DNB

设备数据到它的

区

(polled)输入映像数据发送到Logix控制器(通过框架背板进行

–与逻辑扫描周期不同步)输出映像数据发送给DNB

区DNB将输出数据发送给现场设备Node

#ONode

#INode

#IOControllerOI--][--()--Logix控制器将输出数据发送到输出映像表62021/1NextOIDeviceNet

I/O

映像表尺寸Node

#ONode

#INode

#IODevice

I/O

size

is

dependent

on

device

typeOutput

imageDINT[123]DNB

I/O

映像表尺寸由模块种类决定设备I/O

数据大小（尺寸）由设备类型和供应商决定ControllerInput

imageDINT[124]72021/1NextDNB模块数据类型All

devices

are

mapped

into

the

DNB

module

I/Oimage.This

makes

all

internal

I/O

data

of

datatypeDINT,

4

bytes

in

length.82021/1NextDeviceNet

I/O

mapDNBScannerIONode

#ONode

#INode

#IOControllerOI--][--()--User

performs

I/O

map with

RSNetWorx

forDeviceNetODVA

or

Rockwell

does

not

specify

where

data

is

mapped

to/from

the

I/O

imageUser

must

perform

I/O

map with

RSNetWorx

for

DeviceNet92021/1NextCCS-2

I/Omap

rulesDevice

I/O

mapped

to

scanner

I/O

image

at

DINT

[2

X

node

number]– Allocates

8

bytes

of

input

and

output

dat r

nodeNode

7

is

allocated

Local:#:I.Data[14]

and

[15]

and

Local:#:O.Data[14]

and

[15]for

8

available

input

and

output

bytesDNBScannerIONode

7ONode

6INode

#IONode

6

is

allocated

Local:#:I.Data[12]

and

[13]

and

Local:#:O.Data[12]

and

[13]for

8

available

input

and

output

bytesControllerOI--][--()--102021/1NextCCS-2

I/Omap

rulesNodes

requiring

more

I/O

map

to

the

next

consecutive

words– Node

numbers

thathave

had

their

data

area

already

allocated

cannot

beusedIf

node

6

requires

12

bytes

of

inputs

it

will

be

allocated

both

“node

6”

and

“node

7”

input

andoutput

words

Local:#:I.Data[12]

[13]

[14]

[15]

and

Local:#:O.Data[12]

[13]

[14]

[15]Therefore,

node

7

is

not

allowed

for

this

network

because

its

input

and

output

words

havealready

been

assignedDNBScannerIONode

7ONode

6INode

#IOControllerOI--][--()--Node

8112021/1NextCCS-2

I/Omap

rulesDevice

I/O

mapped

to

scanner

I/O

image

at

DINT

[2

X

node

number]Nodes

62-63

cannot

be

used

because

of

DNB

I/O

imagesizeInput

image

is

DINT[124]Output

image

is

DINT[123]Map allocates

8

bytes

(64

bits)

of

input

and

output

dat r

nodeNodes

requiring

more

than

8

bytes

map

to

the

next

consecutiveDINTsNode

numbers

thathave

had

their

data

area

already

allocated

cannot

beusedThe

device

data

sizes

should

be

known

when

allocating

nodes

numbers122021/1Next设备I/O存在的问题存在如下问题:LogixI/O的更新周期与逻辑程序扫描周期不同步在同一程序的扫描过程中，输入信息可能会变化（从on到off）类似的DeviceNet设备I/O地址的 不相同不同设备的I/O

不一样在不重新调整逻辑地址的情况下，不能快速更换设备DeviceNetI/O地址的 通常不直观Example:

Valve

stack

may

be

reversed–第一个阀门通常是最后一个Bit位单独为每个I/O分别创建别名 会增加出错机会虽然这样可以方便地为每个I/O命名，但是不能解决I/O数据更新与程序扫描不同步的问题。在设备与I/O映像之间不存在相互关系用户需要自己负责

I/O132021/1Next解决方案解决I/O扫描异步问题允许相似的设备采用相同的数据结构，看以来就像一样的！每次都能准确地找到 数据避免采用别名根据设备每个I/O点的实际情况，创建相应的数据类型采用相应的设备数据类型，创建原始Input数据到 ，或者 到Output142021/1Next设备为每一种DeviceNet设备创建数据类型用于输入的数据类型用于输出的数据类型主设备类型用于将输入、输出数据类型结合在一起主数据类型:ad_ArmorBlock_8BIO8E成员数据类型描述CommOkBOOLNode’s

comm

statusIzd_ArmorBlock_8BIO8E_InContains

the

device’s

input

mapOzd_ArmorBlock_8BIO8E_OutContains

the

device’s

output

mapNote:并不是所有的设备都有输入、输出。所以，可能不存在输入或者输出数据映像。152021/1Next设备

(cont’d)利用主数据类型，创建–

示例:ArmorBlock

MaXum

16点输入模块1792D-16BVT0DNote:Just

as

the

device

is

mounted

to

a

station,

the

tag

should

becontainedin

the

station’s

program.

In

other

words,

the

tag

is

a

program

scoped

tag(shown

above

in

program

S100FA)•名称需要与设计图纸中 名一致–

示例:BK01

(Block

1)162021/1NextDestLengthBK01.I1COPCopy

FileSource

Local:9:I.Data[6]Copy拷贝指令文件

(COP)

指令可以将源

到目标–

Byte数量=长度x

（目标数据类型中的Byte数量）BK01.I

的尺寸为4bytes并不在乎源数据的大小（尺寸）长度为(1)，目的度为4Bytes，所以总共长的字节数为4Bytes.Caution:

Copying

data

between

differentsized

tags

requires

an

understanding

of

thecontrollers

memory

layout.

If

the

bytecountis

greaterthan

the

length

of

thesource,unpredictable

data

is

copied

for

theremaining

elements.9关键概念172021/1NextExercise

1

-

How

the

length

effectsthe

copy

instructionTime:

15

minObjective:

Program

the

COP

instruction,

use

crossreference

to

find

overwritesDirections:Open

the

exercise

project

“Sec07Exercises.ACD”

in

RSLogix5000Create

the

following

datatype

ap_CopyTest

with

the

following

members:ABCDINT[4]DINTDINTCreate

the

following

tags

in

the

AA010

program

tagdatabase“Test1”

of

type

DINT[10]“Test2”

of

type

ap_CopyTestAdd

COP

instruction

in

the

B001_MapInputsroutineAdd

a

new

rung

in

the

B001_MapInputs

routineAdd

COP

Source:

Test1[0],

Dest:

Test2.B,

Length:2Generate

a

cross

reference

of

Test2.COpen

the

program

tag

database,

expand

the

Test2

tag

by

clicking+Select

the

Test2.C

tag,

right-click

and

select

Go

to

Cross

Reference182021/1NextExercise

1

(cont’d)Directions:Observe

the

references

to

Test2.CBy

checking

the

the

Destructive

column,

you

will

notice

a

destructive

reference

from

the

COPinstruction

above.

The

destructive

reference

is

a

result

of

the

copy

instruction

copying

8

bytes(2

x

size

of

Test2.B)

and

size

of

the

destination

(Test2.B)

being

4

bytes.

The

remaining

fourbytes

of

the

COP

is

copied

into

Test2.CChange

COP

instruction

length

to

1Generate

a

cross

reference

of

Test2.C

(Refresh

existing

cross

reference)Youshould

notice

no

references

fromthe

copy

instruction

aboveVerify

and

save

the

project192021/1Next设备(con’t)添加一个COP质量从DNB模块输出输入信息到相应的到DNB模块的输出映像表–

示例：BK01，只有输入对于输入数据，长度始终为1如果输入设备出现故障，清除已有的输入信息202021/1NextDeviceNet节点在设备的输入梯级之后，紧跟DeviceNet梯级212021/1Next设备示例：控制气动阀组PM1–

采用合适的数据类型，创建气动阀组根据实际的输出映像大小确定长度对于包含输入、输出映像的设备，CommOK位于输入映像梯级中222021/1Next如何让相似的DeviceNet设备，在程序中看一起来是一样的？数据位学会解决的问题?解决I/O扫描的同步问题每次都能准确地找到对应的对于每个I/O数据点，不使用别名标记232021/1Next让相似的DeviceNet设备，在程序中看一起来是一样的针对相似的设备，采用供应商中立的成员设备命名方式接近开关盒Prox

Blocks:

采用D00,D01,D02…方式表示输入阀门:采用V1S12

&

V1S14

表示电磁阀线圈12

&14采用供应商中立的成员名称来表示设备242021/1Next示例

–4

Port

Prox

Block数据类型成员数据类型D00BOOLD01BOOLD02BOOLD03BOOLD04BOOLD05BOOLD06BOOLD07BOOL4端口Allen-BradleyProx

Block在DNB输入映像表中的位置Datatype:zd_ProxBlockAB_InCreate

the

input

datatype

as

follows:Bit

0

corresponds

to

the

member,bit

1

to

the

second,

bit

2

to

thethird,etc...DNB输入字Bit输入数据描述0D001D012D023D034D045D056D067D07252021/1NextExample

–

4

Port

Prox

BlockDNB

Input

WordBitInput

Description0Status01Status12Status23Status34Status45Status56Status67Status78D009D0110D0211D0312D0413D0514D0615D07DatatypeMemberDatatypeStatus0BOOLStatus1BOOLStatus2BOOLStatus3BOOLStatus4BOOLStatus5BOOLStatus6BOOLStatus7BOOLD00BOOLD01BOOLD02BOOLD03BOOLD04BOOLD05BOOLD06BOOLD07BOOLThis

DNB

bit

pattern

is

for

an

4

PortLumbergProxBlock.Notice

that

8

bits

of

status

precede

theinputsDatatype:zd_ProxBlockLumberg_InAgain,

create

the

input

datatype

for

thisblock

is

asfollows:

As

before,

Bit

0corresponds

to

the member,

bit

1to

the

second,bit

2

to

the

third,etc...262021/1NextExampleCreate

a

tagDatatype:zd_ProxBlockAB_InThis

denotes

that

an

input

is

comingfrom:device

BK01Input

digital

2Notice

that

this

input

is

mapped

to

bit

2in

the

DNB

module

DINTDatatypeDNB

Input

Word272021/1NextBitInput

DescriptionMemberDatatypeTagDatatype0D00D00BOOLBK01ad_ProxBlockAB1D01D01BOOL2D02D02BOOLAdd

the

COP

instruction

3D03D03BOOLAdd

an

XICwith

theaddress

4D04D04BOOLBK01.I.D02

5D05D05BOOL6D06D06BOOL7D07D07BOOLExampleChange

the

datatype

of

the

tagDatatype:zd_ProxBlockLumberg_InThis

is

all

that

is

required

to

use

adifferent

manufacturer’s

device.没有任何改变！The

input

is

still

from

digital

input

2

butthemap is

to

bit

10,

not

bit

2.

Thedatatype

takes

care

of

the

conversionand

the

extra

status

bits

do

not

affect

thelogicDNB

Input

WordDatatypeBitInput

DescriptionMemberDatatype0Status0Status0BOOL1Status1Status1BOOL2Status2Status2BOOL3Status3Status3BOOL4Status4Status4BOOL5Status5Status5BOOL6Status6Status6BOOL7Status7Status7BOOL8D00D00BOOL9D01D01BOOL10D02D02BOOL11D03D03BOOL12D04D04BOOL13D05D05BOOL14D06D06BOOL15D07D07BOOLTagDatatypeBK01ad_ProxBlockLumberg10KeyConcept282021/1NextGM

Standard

Panels

with

DeviceNet

I/OViewed

the

same

as

off-the-shelf

DeviceNet

componentsCreate

up

to

three

datatypesMain

datatype

and

the

input

and

output

datatypesThe

datatypename

is

related

to

the

control

panelGatebox

ECS

1011

uses

datatypes

ad_ECS1011GateBox,

zd_ECS1011GateBoxIn,zd_ECS1011GateBoxOutUse

vendor

neutral

member

names

for

similar

devicesThe

gate

box:

ResetGatePB

is

used

to

identify

the

Reset

Gate

pushbutton

inputArrange

the

vendor

neutral

member

names

to

match

the

bit

pattern

of

the

deviceExample:

Gateboxwith

Allen

Bradley

Flex

I/Oversus

Square

D

Momentum

I/OThese

two

control

panels

would

have

different

ECS

numbers

and

different

UDTsThis

will

allow

the

use

of

the

same

gatebox

software

for

either

ECS292021/1NextGM

Template

Panels

with

DeviceNet

I/OViewed

the

same

as

off-the-shelf

DeviceNet

componentsTemplate

Panel

provides

base

functionality

that

user

may

addtoProvides

starting

point

for

designVariation

in

the

form

of

electrical

sizing,

number

of

robots,

number

of

stations,

numberof

conveyors,

number

of

light

screensetc.Create

up

to

three

datatypesMain

datatype

and

the

input

and

output

datatypesDevice

datatypes

are

prefixed

ud_User

adds

names

for

I/O

asrequiredNames

to

match

hardware

device

IDUse

vendor

neutral

member

names

for

similar

devicesArrange

the

vendor

neutral

member

names

to

match

the

bit

pattern

of

the

deviceExample:

WDTStaOperRobot

fixture

box

uses

the

same

logic

as

ECS1128

fixture

box302021/1NextCustom

Panels

with

DeviceNet

I/OViewed

the

same

as

off-the-shelf

DeviceNet

componentsCreated

when

no

standard

or

template

panels

existShall

be

approved

by

your

responsible

CRW

engineerStandard

or

template

panels

may

be

in

processCreate

up

to

three

datatypesMain

datatype

and

the

input

and

output

datatypesDevice

datatypes

are

prefixed

ud_User

adds

names

for

I/O

asrequiredNames

to

match

hardware

device

IDArrange

the

names

to

match

the

bit

pattern

of

thedevice312021/1NextExercise

2

–

Adding

PM2

DeviceNet

deviceTime:

15

min.Objective:

Create

device

tag,

add

map

input

rung,

add

map

output

rung,

adddiagnosticrungDirections:Open

the

exercise

project

“Sec07Exercises.ACD”

in

RSLogix5000Create

the

following

tags

in

the

AA010

program

tagdatabasePM2

of

type

ad_SMC_EX230Add

input

map

rung

and

diagnostic

rung

in

B001_MapInputs

routine

using

the

samplerung

forPM1

shown

in

the

exercise

project

(note:

this

p atic

manifold

also

hasinputs

in

addition

tooutputs)Add

rung

to

map

inputs

fo