Technote PanelView Plus Block Transfers

8/12/2019 Technote PanelView Plus Block Transfers

1/18

This technote assumes that the reader knows how to setup discrete remote IO

communications in a PanelView Plus per technote G53039759 - RIO configuration andaddressing.

This technote provides examples of Block Transfer communications to a PanelView Plus

700 station from a PLC scanner! a "LC00 processor usin# a $7%&'"( scanner module!and a $7&'L ControlLo#ix processor usin# a $7&')*+IO module,

-ou will have to setup .lock transfer communications for the PanelView Plus examples#iven here, Two PanelView example pro/ects are provided! PanelView pro/ect

TECHNOTE_RIOis meant to work with the ControlLo#ix RIO_TECHNOTE.ACD

ladder lo#ic example! and with the PLC5 RIO_TECH.rspPLC ladder lo#ic example,

PanelView pro/ect SLC_RIOis meant to work with the SLC500 RIO_TECH.RSS

ladder lo#ic example,

CONTENTS

1) RIO Block Transfrs ! Prl"#"nar$

%) Ho& 'o s'(p Panl"& Pl(s co##(n"ca'"ons "n or*r 'o accp' Block

Transfrs fro# '+ PLC5, or fro# '+ DHRIO #o*(l, "n '+ -a#pls

"/n.

) Ho& 'o s'(p Panl"& Pl(s co##(n"ca'"ons "n or*r 'o accp' Block

Transfrs fro# '+ SLC500, "n '+ -a#pls "/n

) Block Transfr prora##"n "n Con'rolLo"-.

5) Block Transfr prora##"n "n '+ PLC5

2) Block Transfr prora##"n "n '+ SLC500


2/18

1) 3 RIO Block Transfrs 3 Prl"#"nar$

+emote IO is a master ' slave1 network, The master is called the scanner1! and the

slaves are called adapters1, 2dapters can .e read from or written to .3 the scanner! .ut

the3 do not initiate communications! this is a PLC concept, 4hen properl3 confi#uredfor discrete communications! a scanner will expect to see a predetermined num.er of so

called racks1 in the network, 2 rack means 5 Input'Output #roups1! and an Input'

Output #roup means $& .its of input 6or a word of input plus a correspondin# set of $&.its of output 6or a word of output, In discrete communications the PLC accesses the IO

#roups throu#h its IO ima#e, 8or the purposes of this technote! a rack can .e visuali9ed

as a $&'slot remote virtual chassis! with sixteen'.it input and sixteen'.it output words

alternatin# throu#hout the chassis,

PanelViews are alwa3s confi#ured as adapters in the +IO network so that the scanner

thinks1 that it is lookin# at a remote PLC chassis, B3 readin# from the inputs and

outputs of this :virtual chassis;! the scanner can read from or write to ta#s that aremapped to the different input and output words 6or .its of these words in the IO #roups

of said virtual chassis, This is what we call discrete transfers1! or discretecommunications1,

Block transfer instructions allow the user to read or to write a maximum


3/18

.lock transfer instructions that can .e in the


4/18

2n example of the confi#uration for BT$ is shown .elowD 6This is accessed .3 ri#ht

clickin# on the .lock transfer and selectin# properties, 6Or durin# the addition of the.lock transfer

This means we can now .lock transfer read1 % words from PanelView throu#h rack %!

#roup 0! slot 0! at the scanner processor,

In order to illustrate the use of 2liases in PanelView A! ri#ht click on the first .locktransfer and add three aliases as followsD 6(otice that 3ou can use an3 name for an alias!

we are simpl3 usin# the default names here


5/18

The properties for alias (ew2lias'00001 are shown .elowD

"tart address 0 indicates that (ew2lias'00001 points to the first word! or B$ 0! of the

.lock transfer, Len#th F $ indicates that it onl3 points to one word, The len#th cannot .e

chan#ed,

The overlap .utton should list aliases that overlap this confi#uration, The overlap .utton

should 3ield no result if no alias or ta# has alread3 .een created that points to the same

.lock transfer word,

In order to illustrate the different wa3s in which a screen o./ect can o.tain .lock transfer

data! four ta#s were created in the +IOTAC*(OTA example #iven here, The firstthree ta#s point to the three aliases that were created! and the next two ta#s point to the

.lock transfer words directl3, 6)ou.le click on the *I ta#s of the pro/ect in order to

see the created ta#s The shortcut name is Gm3shortcutG,


6/18

6Ta#s point to 2liases

6Ta#s point to the .lock transfer word directl3


7/18

) 3 Ho& 'o s'(p Panl"& Pl(s co##(n"ca'"ons "n or*r 'o accp' Block

Transfrs fro# '+ SLC500, "n '+ -a#pls "/n.

The "LC00 use the $7%&'"( module as a scanner! and can onl3 access racks 0 throu#h

? in non'complementar3 mode,

4e will use +acks $ and > in the PanelView +IO"LC application, The communications

setup for the +IO"LC PanelView A application should look like thisD

The rack properties should .e as followsD

BT$ PropertiesD +ack $! Eroup 0! "lot 0! t3pe read1! si9e %,

BT> PropertiesD +ack $! Eroup 0! "lot $! t3pe read1! si9e &

BT? PropertiesD +ack >! Eroup 0! "lot 0! t3pe write1! si9e %,BT% PropertiesD +ack >! Eroup 0! "lot $! t3pe write1! si9e &

2#ain! aliases should .e created that point to the first three words of the first .lock

transfer, The followin# #raphics shows the properties for the first aliasD


8/18

Onl3 two ta#s were created for the +IO"LC pro/ect, The3 point to the .lock transfer

words directl3D 6(ot to the aliases


9/18

) 3 Block Transfr prora##"n "n Con'rolLo"-.

The example ControlLo#ix pro#ram was written +"Lo#ix000 version $>, There should.e four .lock transfer instructions executed in se


10/18

In order to add each of the PanelView racks shown in the IO confi#uration tree! 3ou

should ri#ht click on the )*+IO module and select Eeneric +emote IO adapter as

followsD

-ou should then ri#ht click on the #eneric adapter and insure that the confi#uration for.oth! rack % and +ack $0 adapters coincide with the confi#uration discussed a.ove for

PanelView Plus, The followin# #raphics shows the confi#uration properties for rack % in

the +"Lo#ix000 IO confi#uration treeD


11/18

The followin# #raphics show the confi#uration for one of the .lock transfer instructions

in the ControlLo#ix ladder pro#ram! .lock transfer one! which we setup as +ack %! Eroup

0! slot 0! si9e % in TAC*(OTA+IO, 6The ladder lo#ic is shown on the followin# pa#e


12/18

The .lock transfer lo#ic is desi#ned to se


13/18

5) 3 Block Transfr prora##"n "n '+ PLC5.

The example PLC pro#ram +IOTAC*,rsp was written +"Lo#ix version &, Thereshould .e four .lock transfer instructions executed in se


14/18

-ou must create and assi#n an IO status file in the processor status dialo# in order to

execute an auto confi#1, )ata 8ile $0 was used as an IO status file in this case, )ata

8ile $$ is assi#ned as the channel dia#nostics file,

2lthou#h there are different wa3s to confi#ure Block Transfers in +"Lo#ix ! it is

relativel3 simpler! in this case! to confi#ure .lock transfers manuall3 on the face of theinstruction itself, The followin# #raphics show the .lock transfer confi#uration for the

four .lock transfers,


15/18

2) 3 Block Transfr prora##"n "n '+ SLC500.

The example "LC00 pro#ram +IOTAC*,rss was written in +"Lo#ix00 version &,

There should .e four .lock transfer instructions executed in se


16/18

IO Confi#uration dialo#,

2dvanced IO confi#uration )ialo#,


17/18

E'8ile confi#uration dialo#,

The followin# #raphics illustrate the .lock transfer lo#ic for our "LC+IO PanelView

pro/ectD


18/18

"LC00 Block transfers for rack $

"LC00 Block transfers for rack >,

KKK And of Technote KKK

Technote PanelView Plus Block Transfers

Documents

Transcript of Technote PanelView Plus Block Transfers