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

communications in a PanelView Plus per technote G53039759 - RIO configuration and

addressing.
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_RIO is meant to work with the ControlLo#ix RIO_TECHNOTE.ACD
ladder lo#ic example! and with the PLC5 RIO_TECH.rsp PLC ladder lo#ic example,
PanelView pro/ect SLC_RIO is 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.
0) Ho& 'o s'(p Panl)"& Pl(s co##(n"ca'"ons "n or*r 'o accp' Block
Transfrs fro# '+ SLC500, "n '+ -a#pls ."/n
1) Block Transfr pro.ra##"n. "n Con'rolLo."-.
5) Block Transfr pro.ra##"n. "n '+ PLC5
2) Block Transfr pro.ra##"n. "n '+ SLC500
1) 3 RIO Block Transfrs 3 Prl"#"nar$
+emote IO is a 0master ' slave1 network, The master is called the 0scanner1! and the
slaves are called 0adapters1, 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#ured
for discrete communications! a scanner will expect to see a predetermined num.er of so
called 0racks1 in the network, 2 rack means 5 0Input'Output #roups1! and an Input'
Output #roup means $& .its of input 6or a word of input7 plus a correspondin# set of $&
.its of output 6or a word of output7, 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
0thinks1 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 are
mapped to the different input and output words 6or .its of these words7 in the IO #roups
of said virtual chassis, This is what we call 0discrete transfers1! or 0discrete
communications1,
Block transfer instructions allow the user to read or to write a maximum <uantit3 of &%
inte#er words 6&% x $&'.it words7 to a specific module located in either a :local chassis;
6or processor resident chassis7 or a 0remote chassis1 6adapter interface resident chassis7,
It will do so throu#h one of the IO #roups of the specific rack where the module resides,
In a t3pical .lock transfer! the 0slot1! or 0module num.er1! refers to a set of input=output
.3tes in the particular IO #roup .ein# tar#eted .3 the .lock transfer instruction, This set
of input=output .3tes is .ein# used .3 the .lock transfer instruction itself, 2 0 denotes
the lower .3tes 6or .its 0 thou#h 77 of the IO #roup input=output words! and a $ denotes
the hi#her .3tes 6or .its $0 thou#h $7 in octal7! therefore the user should refrain from
usin# discrete communications throu#h the IO #roup .ein# tar#eted .3 the .lock transfer
instruction,
+ack 0 can onl3 .e the local rack if usin# the PLC as a scanner! .ut it can .e a remote
rack in the "LC and ControlLo#ix architectures, PanelView Plus can present a maximum
of >? racks 6>7 octal7 in a +IO network! .ut it cannot .e confi#ured as rack 0, (otice
that the maximum num.er of racks in a remote IO network is also processor dependent!
for instance! >7 octal @ for a PLC L50B processor! and % racks onl3 for a $7%7'"(
scanner module in the "LC architecture,
Processors execute .lock transfer operations as3nchronousl3 with the pro#ram scan! this
means that the .lock transfer instruction is placed .3 the processor in the remote IO
<ueue of the particular port throu#h which the .lock transfer is to .e issued at the
moment the .lock transfer instruction is executed, The execution of ladder lo#ic proceeds
forward .efore the .lock transfer actuall3 takes place, Limitations on the num.er of
.lock transfer instructions that can .e in the <ueue at an3 one time var3 with processor
architecture, The #iven examples se<uence the .lock transfer lo#ic,
%) 3 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.
+estore pro/ect TAC*(OTAB+IO in +"View "tudio, Asta.lish discrete remote IO
communications per technote 0G530397591! .ut create two racks, 4e will work with
racks % and $0 for .oth! the PLC! and the ControlLo#ix architecture examples, Both
racks should .e setup as full racks 6that is! comprisin# the entire set of 5 IO #roups7 with
full read=write access, (otice that 3our communications shortcut! accessed from the
communications setup window of +"View CA should look similar to he #raphics .elow
for .oth! the local and tar#et ta.s of the communications setup,
4e should now ri#ht click on the +IO root of the a.ove tree! and add four .lock transfers
6BT$! BT>! BT?! and BT%7 with the followin# propertiesD

BT$ PropertiesD +ack %! Eroup 0! "lot 0! t3pe 0read1! si9e %,
BT> PropertiesD +ack %! Eroup 0! "lot $! t3pe 0read1! si9e &
BT? PropertiesD +ack $0! Eroup 0! "lot 0! t3pe 0write1! si9e %,
BT% PropertiesD +ack $0! Eroup 0! "lot $! t3pe 0write1! si9e &,
(otice that we could transfer up to &% words! .ut in this case we will .e readin# onl3 four
words throu#h rack %! #roup 0! slot0! and six words throu#h rack %! #roup 0! slot $, 4e
will also .e writin# four words throu#h rack $0! #roup 0! slot0! and six words throu#h
rack $0! #roup 0! slot $,
-our confi#urations should now look like thisD
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 transfer7
This means we can now 0.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 CA! ri#ht click on the first .lock
transfer and add three aliases as followsD 6(otice that 3ou can use an3 name for an alias!
we are simpl3 usin# the default names here7
The properties for alias 0(ew2lias'00001 are shown .elowD
"tart address 0 indicates that 0(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 +IOBTAC*(OTA example #iven here, The first
three 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 *CI ta#s of the pro/ect in order to
see the created ta#s7 The shortcut name is Gm3BshortcutG,
6Ta#s point to 2liases7
6Ta#s point to the .lock transfer word directl37
0) 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 +IOB"LC application, The communications
setup for the +IOB"LC PanelView CA application should look like thisD
The rack properties should .e as followsD
BT$ PropertiesD +ack $! Eroup 0! "lot 0! t3pe 0read1! si9e %,
BT> PropertiesD +ack $! Eroup 0! "lot $! t3pe 0read1! si9e &
BT? PropertiesD +ack >! Eroup 0! "lot 0! t3pe 0write1! si9e %,
BT% PropertiesD +ack >! Eroup 0! "lot $! t3pe 0write1! 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
Onl3 two ta#s were created for the +IOB"LC pro/ect, The3 point to the .lock transfer
words directl3D 6(ot to the aliases7
1) 3 Block Transfr pro.ra##"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<uence, Pro/ect TAC*(OTAB+IO
should .e loaded in the PanelView Plus station! and runnin#,
The confi#uration for the .lock transfer instructions should coincide with the PanelView
+IO confi#uration,
The followin# #raphics show the IO confi#uration tree in +"Lo#ix000D
(otice that the $7&')*+IO confi#uration switches should .e set per the ta.le #iven in
technote E?%0>& to 7,& HB for .oth channels! Channel 2 is )*I! Channel B is the
+IO scanner port, The module resides in slot $ for this example! and its firmware
revision ,?, Confi#uration for the $7&')*+IO is as followsD
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
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*(OTAB+IO, 6The ladder lo#ic is shown on the followin# pa#e7
The .lock transfer lo#ic is desi#ned to se<uence the .lock transfers, This is alread3
contained in the example! and should not have to .e chan#ed,
5) 3 Block Transfr pro.ra##"n. "n '+ PLC5.
The example PLC pro#ram +IOBTAC*,rsp was written +"Lo#ix version &, There
should .e four .lock transfer instructions executed in se<uence, Pro/ect
TAC*(OTAB+IO should .e loaded in the PanelView Plus station, Channel $B of a
PLC=%0 was used as the scanner port,
Once remote IO communication has .een confi#ured with PanelView Plus .ein# racks %
and $0! and the pro/ect has .een loaded in the PanelView 700 station, 2n 0auto confi#1
action! in the channel confi#uration for the PLC channel %B ou#ht to 3ield racks % and
$0 as followsD 6(oteD The 0auto confi#1 feature is onl3 availa.le on line and in pro#ram
mode7
The auto confi# feature shows rack % and $0 as confi#ured in the PanelView station,
-ou must create and assi#n an IO status file in the processor status dialo# in order to
execute an 0auto 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 the
instruction itself, The followin# #raphics show the .lock transfer confi#uration for the
four .lock transfers,
2) 3 Block Transfr pro.ra##"n. "n '+ SLC500.
The example "LC00 pro#ram +IOBTAC*,rss was written in +"Lo#ix00 version &,
There should .e four .lock transfer instructions executed in se<uence, Pro/ect +IOB"LC
should .e loaded in the PanelView Plus station! and runnin#, 2 $7%&'"( +emote IO
scanner module! series B! was used in slot $ of a four slot "LC00 chassis in con/unction
with a "LC=0 $7%7'L>B processor usin# firmware 8+(&,
This technote assumes that PanelView Plus is the onl3 adapter in the network, In order
for the scanner module to read racks $ and > 6the racks that were confi#ured in
PanelView Plus for this example7 3ou must access the IO confi#uration in the pro/ect tree
of +"Lo#ix00! select the $7%7'"( module! and click on the 2dvanced Confi#uration
.utton, 6-ou can also dou.le click the module7,
Once the advanced confi#uration dialo# opens! 3ou will see the num.er of discrete input
and output words that can .e read or written to .3 the processor from the module 6?> of
each in the case of the $7%7'"(7! as well as the num.er of words in the module memor3
6??00 for .oth inputs and outputs7,
The module memor3 is addressed .3 means of the C files, 6C$ for inputs! and C0 for
outputs7, Block transfers use these memor3 files to transfer information .etween the
"LC processor and the $7%7'"( scanner module, Aach .lock transfer instruction should
.e assi#ned an address such as C$D",J00 if the instruction is a .lock transfer read! or an
address such as C0D",J00 if the instruction is a .lock transfer write, The letter 0"1
denotes the slot num.er where the scanner module resides! and the letter J denotes a
num.er .etween $ and ?>, It is important to notice that 3ou cannot repeat the J00
portion of the address in an3 other .lock transfer! for instance! if 3ou assi#n C$D$,$00 to
a .lock transfer read instruction! 3ou cannot use C$D$,$00 or C0D$,$00 in an3 other
.lock transfer instruction! .ecause an3 t3pe of .lock transfer! read or write! will use .oth!
the C$ and its correspondin# C0,
4hile in the advanced confi#uration screen! 3ou should click on the 0Adit E 8ile1 .utton,
The E 8iles dialo# should coincide with the adapter confi#uration, +emem.erin# that we
confi#ured racks $ and racks > as full racks in PanelView! we should select racks $ and >
in the E files! and select full rack for each of them, If the E'8ile does not coincide with
the adapter confi#uration! communications will not take place, The followin# three
#raphics illustrate the processD
IO Confi#uration dialo#,
2dvanced IO confi#uration )ialo#,
E'8ile confi#uration dialo#,
The followin# #raphics illustrate the .lock transfer lo#ic for our "LCB+IO PanelView
pro/ectD
"LC00 Block transfers for rack $
"LC00 Block transfers for rack >,
KKK And of Technote KKK