PaneelView 5000 / Logixx Integrration

For Cllassroom Use Onlyy!

Important User Inforrmation

This documentation, whetheer, illustrative, prrinted, online or
o electronic (herreinafter Docum
mentation) is inteended for use onnly as
a learning aid
a when using Rockwell
R
Automaation approved demonstration
d
haardware, softwarre and firmware.. The Documentation
should only be used as a learning tool by quualified professioonals.
The variety of uses for the hardware,
h
softwaare and firmwaree (hereinafter P roducts) described in this Docuumentation, manndates
that those reesponsible for thhe application annd use of those Products
P
must s atisfy themselvees that all necesssary steps have been
taken to enssure that each application and actual use meets all performancee and safety requuirements, includding any applicaable
laws, regulaations, codes andd standards in addition to any appplicable techniccal documents.
In no event will Rockwell Auutomation, Inc., or
o any of its affiliate or subsidiaryy companies (heereinafter Rockw
well Automation) be
responsible or liable for anyy indirect or conssequential damages resulting froom the use or appplication of the Products describbed in
this Documeentation. Rockw
well Automation does not assum
me responsibility or liability for daamages of any kkind based on thee
alleged use of, or reliance on,
o this Documenntation.
No patent liaability is assumeed by Rockwell Automation
A
with respect to use oof information, ciircuits, equipment, or software
described inn the Documentaation.
Except as specifically agreeed in writing as part
p of a maintennance or supportt contract, equipment users are responsible for:

prroperly using, caalibrating, operatting, monitoring and

a maintaining all Products connsistent with all Rockwell Autom
mation
orr third-party provvided instructionss, warnings, recoommendations aand documentattion;

ennsuring that onlyy properly trainedd personnel use, operate and m aintain the Prodducts at all times;

staying informed of
o all Product uppdates and alertss and implementting all updates aand fixes; and

all other factors afffecting the Prodducts that are ouutside of the dire ct control of Rocckwell Automatioon.
Reproductioon of the contentts of the Documeentation, in wholle or in part, withhout written perm
mission of Rockw
well Automation is
prohibited.
Throughout this manual we use the followinng notes to makee you aware of ssafety considerattions:
Identifies information aboout practices or circumstances
c
that can cause
c
an explosion in a hazardoous environmentt,
which maay lead to personnal injury or deatth, property dam
mage, or econom
mic loss.

t is critical forr successful appplication and undderstanding of thhe product.

Identiffies information that

a
practices or
o circumstancees that can lead tto personal injurry or death, propperty
Identiffies information about
damagge, or economic loss. Attentionss help you:
identtify a hazard
avoidd a hazard
recoggnize the conseqquence

Labels may be located onn or inside the drrive to alert peopple that dangeroous voltage may be present.

Labels may be located onn or inside the drive to alert peopple that surfacess may be dangerous temperaturres.

PanelView 5000 / Logix Integration

Contents
Before you begin ............................................................................................................................................................................... 4
About this lab .................................................................................................................................................................................... 4
Other RSTechED Labs with related content ..................................................................................................................................... 4
Tools & prerequisites ........................................................................................................................................................................ 5
Section 1: Comments, Descriptions and Extended Tag Properties .............................................................. 6
1.1Descriptions and Rung Comments ............................................................................................................................................. 6
1.2Enabling Tag Extended Properties ............................................................................................................................................. 6
1.3Referencing Min and Max Extended Tag Properties in Your Logic ............................................................................................ 7
1.4Engineering Unit, State1 and State0 properties as Pass-Through properties ............................................................................ 9
1.5Extended Tag Properties in an Array ........................................................................................................................................ 10
1.6Referencing Tag Extended Properties in your HMI (Informational section only) ...................................................................... 12
1.7Extended Tag Properties in Different Programming Languages (Information Section Only).................................................... 13
1.8Using Pass-Through for Optimized Download / Upload Times................................................................................................. 14
1.9Section 1 Summary................................................................................................................................................................... 20
Section 2: Alarms ........................................................................................................................................ 21
2.1Working with device-based Alarms and Events (Information Section Only) ............................................................................. 21
2.2Alarm Shelving Setup in Studio 5000 Logix Designer ........................................................................................................... 23
2.3Deploying an Application in Studio 5000 View Designer....................................................................................................... 25
2.4Shelving Alarms Detailed Steps............................................................................................................................................. 26
2.5Shelving Alarms Additional Steps .......................................................................................................................................... 30
2.6Adding Alarms........................................................................................................................................................................... 31
2.7Section 2 Summary................................................................................................................................................................... 34
Section 3: High-Speed HMI Button Control ................................................................................................ 35
3.1.Adding the PanelView 5000 to the I/O Configuration of Logix .................................................................................................. 36
3.2.Adding the HMIBC instruction in Ladder ................................................................................................................................... 37
3.3Configuring the button on the PanelView 5000......................................................................................................................... 37
3.4Deploy the modified project to the PanelView 5000 terminal.................................................................................................... 40
3.5Section 3 Summary................................................................................................................................................................... 41

3 of 44

Before you begin

From the desktop, open the P5K_Demo.ACD in Studio 5000 Logix Designer
Download the ACD project to the controller designated to your lab station. See your lab station computer monitor for
information on which controller is dedicated to your station.
Perform as much of the lab as possible while online with the controller.

About this lab

Learn about the premier integration between the Logix Family of programmable automation controllers (PAC) and the new
PanelView 5000 industrial automation panels.
This lab is intended to walk you thru the synergy created between these traditionally independent development environments.
Working in tandem, the PanelView 5000 terminal and the Logix controller family provide differentiation that cannot be realized by
other vendors building independent products. This allows the Logix controller to focus on control and the PanelView 5000 to
focus on operator interface to data.
This lab will be focused on Extended tag Properties and the High-speed HMI Button Control. We will also touch on the Alarms
and Events introduced with firmware 16.03 as it is part of the PanelView 5000 HMI Premier Integration to Logix. We will use the
new Studio 5000 Logix Designer (formally RSLogix 5000) and the Studio 5000 View Designer software packages.
This lab is made up of three sections; each concentrating on one major feature. A presentation or a demo is provided prior to
every section. All three sections combined take approximately 60 minutes to complete (not including presentations).

Other RSTechED Labs with related content

DE01 Rockwell Software Studio 5000 V22 Productivity Features Preview
VZ06 FactoryTalk View Site Edition: Implementing FactoryTalk Alarms and Events
VZ07 Allen-Bradley PanelView 5000: Exploration of the Latest Features

4 of 44

Tools & prerequisites

Software programs required
The following software is required to complete this lab.
VMware Workstation
Studio 5000 Logix Designer (formally RSLogix 5000)
RSLinx Classic
Studio 5000 View Designer
Hardware devices required
The following hardware is required to complete this lab.
1756 ControlLogix Chassis
1756-L75 ControlLogix PAC
1756-EN2TR ControlLogix Ethernet Bridge
Desktop Computer with Studio 5000 View Designer and Studio 5000 Logix Designer
Files required
The following files are required to complete this lab.
VMWare image files for the RSTechED 2013 DE04 virtual machines
ACD project file (PV5K_Demo.ACD) for Studio 5000 Logix Designer
VPD project file (SuperJuice_Complete.VPD) for Studio 5000 View Designer
Tag import CSV file (DE04_Passthrough.CSV) containing Pass-through tag examples
Tag import CSV file (DE04_NoPassthrough.CSV) containing Non Pass-through tag examples

5 of 44

Section 1: Comments, Descriptions

D
and
a Extended Tag Propertiees
This sectionn of the lab provides an overview
w of whats new with
w version 21 oof Studio 5000 rrelated to Comm
ments, Descriptioons and
tag propertiees.

1.1 Descrriptions and Rung

R
Commen
nts
All comments and descriptioons (including taag description annd program desccriptions) now reeside in the contrroller and do nott use
the Data, Loogic and I/O mem
mory. Logix conttrollers come witth extended inte rnal memory to support this featture. They also pprovide
a level of coonvenience whenn multiple engineeers need accesss to the logic orr in case the ACD
D project file is lost. Workflow off
multiple devvelopers adding code to a singlee project online iss greatly improveed as commentss are maintainedd between conneected
workstationss.

1.2 Enabling Tag Exten

nded Propertiees
1. Navigate to the Program Tagss in the DE04__Program.
2. Highlight the tagg myDINT and press the Exteended Propertties button in thhe tag properties window.

wn.
3. Select Engineerring Units, Maax, and Min from the dropdow

6 of 44

4. Once
O
Extended Properties aree enabled, Expaand the Data pproperties and sset Enginnerinng Unit to SEC
C,
Min
M to 0 and Max
M to 1000.

1.3 Refereencing Min an

nd Max Extend
ded Tag Propeerties in Your Logic
Lets say yoou have to prograam your logic in a way to prevennt a critical outpuut from being energized when thhe input value is
outside a sppecified range. This
T can easily be done using thee Limit instructioon with the Min aand Max Extendeed Properties.

1. Add the following rung to the DE04_MainRou

D
utine under thee DE04 Prograam.
Today, you cant browsse for the Exteended Propertiies of a tag, pplease manuallly type it in ass shown below
w.

2. Fiinalize all editss in the program

m.
3. Make
M
sure the processor
p
is in Run mode. Maanually changee the value of m
myDINT. Veriffy that only valuues
beetween @Min (0)
( and @Max (1000) will exeecute true and energize the O
OTE (myBOOLL).

Why
W use the Min and Max Properrties instead of a constant or justt another tag? U
Using Extended pproperties
gives you the option to make a chhange in one place and have thaat take affect eveery place it is useed in your
logic, whether it iss used in a Limit, greater than orr any other inputt type of an instruuction. Furtherm
more,
Exxtended Propertties can be refereenced from the PanelView
P
50000 Terminals. Thiis functionality ooptimizes
coontroller / HMI coommunication annd is especially useful when cre ating device facceplates.

Exxtended propertiies must be usedd as an input opperand that is no t of type BOOL aand you can chaange the
taag's extended prooperties only in the
t Tag Propertiies Pane. You caannot remove exxtended properties that are
acccessed in logic when the projecct is online with the
t controller. Yoou would have too go offline. It iss also
im
mportant to point out that when extended
e
tag prooperties are usedd or referenced iin logic, they willl consume
daata and logic meemory.

7 of 44

During a download, the user will have

h
the option to
t select whetheer or not to downnload all project
doocumentation annd extended tag properties. If anny extended tag property is usedd in logic, all exttended tag
prroperties must be downloaded, otherwise
o
the doownload will not ccomplete. The ssame concept applies when
exxtended tag propperties for a giveen tag are used within
w
an HMI appplication. If thee project documeentation and
Exxtended Tag Prooperties are not included in the download,
d
the exxtended tag propperty referencess on the HMI
will show an errorr. We will take a closer look at thhis concept laterr in this section.

8 of 44

1.4 Engin
neering Unit, State1
S
and Staate0 propertiess as Pass-Throough propertiies
1. Navigate to the program tags in the DE04_Prrogram.
2. Highlight the taag myBOOLalias and note that extended taag properties arre NOT enableed.

3. Enable all Exten

nded Propertiees for the program scope tagg called myBOO
OL and set thee Enginnering Unit
too Position, Sttate0 to Openeed and State11 to Closed.

4. Select the myBO

OOLalias tag. The tag myBO
OOLalias has already been cconfigured as aan alias for
MyBOOL.
M
Whatt are the default values used for Enginnerinng Unit, State00, and State1??

Sttate0, State1, annd Engineering Unit

U are considered pass-through properties. Thhis means that w
whenever you
doo not explicitly prrovide State0, State1, and Enginneering Unit propperties for an aliias tag, the basee tag
prroperties values are displayed.

5. Thhe user is allow

wed to overwritte a pass-throuugh property if ddesired. Lets try this by changing the
Engineering
E
Un
nits of myBOO
OLalias to Aliaas-Position.

Thhe pass-throughh properties will be

b grayed out. As
A stated above , you can overw
write the pass throough
prroperties by mannually entering thhe desired valuee into the applicaable field. Additional considerations on
paass-through propperties will be disscussed later in this section.

9 of 44

1.5 Extended Tag Prop

perties in an Array
T array tag calleed myDINTArrray in the Proggram Tags of D
DE04_Program
m and enable
1. Loocate the DINT
Extended
Ex
Properties for the base
b
tag ONLY
Y and set the M
Min to 0 and M
Max to 1000.

2. Navigate to DE004_MainRoutin
ne.
3. Change the Limit instruction onn the rung addeed previously sso that it uses m
myDINTArray[
y[2].@Min and
myDINTArray[2
m
2].@Max as thee Low Limit annd High Limit..

4. Fiinalize all proggram edits. Notte what values are used in thee limit instructioon Low Limit aand High Limiit.
5. Navigate back too myDINTArraay in the DE04__Program tagss, enable Extennded Propertiees for the arrayy
Min
element myDINTArray[2] and explicitly proviide different Miin and Max prooperty values (ee.g. 1000 for M
annd 5000 for Maax).

6. Navigate to DE004_MainRoutin
ne.

10 of 44

7. What
W is the limit instruction now
w using for Low
w Limit and Hiigh Limit?

8. Change the Limit instruction onn the rung addeed previously sso that it uses m
myDINTArray[
y[3].@Min and
myDINTArray[3
m
3].@Max as thee Low Limit annd High Limit..
9. Fiinalize all proggram edits. Notte what values are used in thee limit instructioon Low Limit aand High Limiit.

Exxtended Propertties on an array apply

a
to all arrayy elements exceept when specifieed on an individuual array
element. In this case,
c
the array extended
e
propertties are overridd en by the extendded properties sspecified on
the element.

11 of 44

1.6 Refereencing Tag Exxtended Propeerties in your HMI (Informattional section only)
When the PanelView
P
50000 HMI terminaals are releasedd, we will be abble to referencee all propertiess, including; Minn,
Max, Enginneering Unit, Tag Description and Tag Name.
Beeing able to refeerence Extendedd Tag Properties in the PanelView
w 5000 has manny benefits. To sstart with, a
UDT structure is not
n required for the
t basic Min, Max,
M Description, Tag Name, andd Engineering Units. All
Exxtended Tag Prooperties configurred for a tag will be read by the H
HMI if the base ttag is read by thhe HMI.
Fuurthermore, becaause Extended Tag
T Properties do
d not change offten, they are NO
OT polled basedd on an
uppdate rate by thee PanelView 50000. They are onlyy read when a pproperty change is noted by the controller!
Ass stated previously in the lab, thee extended tag properties
p
will noot consume dataa and logic mem
mory in the
coontroller, unless they are referennced in logic. With these factorss in mind, using eextended tag prooperties for
HMI faceplates wiill result in reducced communication load on the ccontroller as welll as less consum
med
memory.
NOTE: If any tag extended property is referencedd in the HMI, the Download Prooject Documenttation and
Exxtended Tag Prroperties checkkbox must be selected in the Proojects tab of the Controller Propeerties.

12 of 44

1.7 Extended Tag Prop

perties in Diffeerent Programming Languagges (Informatiion Section O
Only)
1. Exxtended Propeerties also workk within a Function Block Diaggram. Here is aan example of a Function Bloock
rooutine.

W can also usee the extended properties in Structured

S
Texxt. We are usingg the Extendedd Properties of a
2. We
UDT member in the example below.
b

13 of 44

1.8 Using
g Pass-Throug
gh for Optimizeed Download / Upload Timees
This sectioon will cover hoow using pass-tthrough for proj
oject documentaation and extennded tag propeerties can optim
mize
upload andd download tim
mes.
When Passs-Through Display is utilized

1. Save the ACD file.

2. Go
G offline with thhe controller.
3. Open
O
the controoller properties window and naavigate to the P
Project tab. Make sure both Pass-Through
Display checkbooxes are checkked. They shouuld be checkedd by default.

4. Click on Tools =>

= Import => Taags and Logic Comments
C

14 of 44

5. Navigate to the C:\Lab Files\L

Logix folder and select the D
DE04_Passthroough.csv file. Select Imporrt.

m Tags.
6. Navigate to the DE04_Program
h tags. Each oof the 10 structtures is of the ssame data typee,
7. Exxamine the myyStructureXX__Passthrough
m
my100DINTs.
Notice
e how the desscription text is
grayed
d. This indica
ates that no
descriiption has bee
en defined an
nd
the de
escription from
m the UDT
definittion will be passed-throug
gh.

8. Exxpand the myStructure1_Paassthrough taag.

15 of 44

9. Inn the Controlleer Organizer, navigate

n
to the Data Types User-Defineed folder and oopen the UDT
sttructure my1000DINTs. Minimize the UDT window and m
move it so you ccan view the booth the program
m tags
annd the UDT definition.

10. Loook at the desccription for myyStructure1_Passthrough.D

Dint001. Expaand the descripption column if
neecessary. Thee tag descriptions in the UDT definition are ppassed throughh to the program
m tags. The gray
teext indicates paass-through is used.
u

The description should be:

11. We
W are now goinng to downloadd the current prrogram with paass-through enabled. Begin a download andd
keeep track of thee amount of tim
me it takes for the program to finish the download process.. Record the time.
12. Go
G offline with thhe controller.

16 of 44

Paass-Through Display:
Thhis shows a good example of hoow the pass-through feature worrks with UDTs within the Logix environment.
When
W
a user doess not explicitly deefine a tag desccription when creeating a tag, it wiill inherit the desscription that
exxists in the UDT definition.
Thhe pass-throughh configuration caan be found in thhe controller prooperties on the P
Project tab. Therre are two
main settings:

Thhe Show Pass-Through Properties check boox will ensure thhat the tag and aall members will inherit the
deescriptions defined in the UDT definition.

Thhe Append To Base Tag Desccription check box will appendd the UDT descriiption to the begginning of the
Member descriptioon.

17 of 44

When Passs-Through Display is NOT utilized

13. Navigate to the DE04_Program

m Tags.
14. Ensure the Editt Tags tab is seelected and dellete all 10 of thhe myStructurreXX_Passthrrough tags.
15. Click on Tools =>
= Import => Taags and Logic Comments
C
16. Navigate to the C:\Lab Files\L
Logix folder and select the D
DE04_NoPasstthrough.csv ffile. Select Impport.

17. Exxamine the myyStructureXX__NoPassthrou

ugh tags. Eacch of these 10 structures is off the same dataa
tyype, my100DIN
NTs.

18. Exxpand the myStructure1_No

oPassthrough
h tag.

19. Loook at the desccription for myyStructure1_NoPassthroughh.Dint001. Exxpand the desccription columnn if
neecessary by clicking inside the tag descriptioon. Each struccture member hhas a distinct tag description.. You
shhould notice thaat it is identical to the descripption from the ppass-through taags. The text iss BLACK and nnot
GRAY.
G
This inddicates that the description haas been hard-ccoded

The description should be:

18 of 44

20. We are now going to download the current program with pass-through disabled. Begin a download and
keep track of the amount of time it takes for the program to finish the download process. Record the time.

You should notice a 20% 30% increase in download time when pass-through is not utilized.

Designing your application to use pass-through will enhance upload / download times.

21. Delete all 10 of the myStructureXX_NoPassthrough tags.

What happens to Project Documentation during a download?
During a download, all project documentation and extended tag property lists are packed into a database that
lives on extended memory in the controller. Each comment, description, and extended tag property list for all
AOIs, UDTs, rungs, programs, and tags will be entered into in the project documentation database as each
element is downloaded to the controller. As the number of project documentation items increase, the size of
the project documentation database will increase as well as the total number of database entries.
Pass-Through
This is probably the single most important optimization technique that can be utilized to minimize download
and upload times when project documentation is included. Since Pass-Through Display can only be used
with arrays and UDTs, it is important to organize as many tags as possible into these two groups. The
Pass-Through Display setting allows project documentation pertaining to arrays and UDTs to be defined in
the base tag or definition.
When using arrays, the base tag description and extended tag properties list will be propagated to all
members of the array. If certain tags in the array must have a unique description or extended tag properties
list, it can be changed in the tag editor. Any manual changes in project documentation to members of an
array will take priority over the Pass-Through Display information.
When using UDTs, the data type definition description and extended tag properties list will be propagated to
all tags of that data type. Similarly to arrays, if certain members (tags) of a UDT must have a unique
description or extended tag properties list, it can be changed in the tag editor. Any manual changes in
project documentation to members in a user defined tag will take priority over the Pass-Through Display
information.
Pass-Through Display allows the description and extended tag properties list to be entered into the project
documentation database one time, regardless of how many members are in the array or how many user
defined tag instances exist. If Pass-Through Display was not implemented, every tag and member would
have a separate entry in the project documentation database. Using Pass-Through Display whenever
possible will greatly improve upload and download time performance.
Rung Comments:
Rung comments can have an impact on upload and download times. As the total number of rung comments
increase, so will the number of project documentation database entries. Studio 5000 Logix Designer does
an excellent job compressing rung comments. With that in mind, it is better to have a smaller number of
large rung comments as opposed to a large number of small rung comments. Since each comment will
require an entry in the project documentation database, better performance can be achieved by consolidating
as many rung comments as possible into one or several large rung comment(s).

19 of 44

1.9 Section 1 Summary

You learned

How to configure Extended Tag Properties

How to use Extended Tag Properties in Logic

How Extended Tag Properties will optimize HMI faceplate development

How project documentation is downloaded and stored in the controller.

How to use Pass-Through Display to optimize Project Documentation

You have finished Section 1 of the lab. Please do not continue unto Section 2 until after the instructor demonstration.

20 of 44

Section 2: Alarms
The PanelView 5000 terminal allows you to subscribe to Logix-based Device Alarms configured in Studio 5000 Logix
Designer. This feature is referred to as FactoryTalk Alarms and Events. It has been available since ControlLogix firmware
version 16 and was limited to the FactoryTalk View Site Edition HMI software package. The PanelView 5000 terminals will
support FactoryTalk Alarms and Events. The Logix-based alarm instructions are used to monitor and control alarm conditions.
These instructions will integrate alarming between PanelView 5000 applications and Logix controllers. Studio 5000 View
Designer has two alarm tables to view the alarms, Alarm Summary and Alarm Manager. In this lab, we will primarily be focused
on exploring the Logix based alarm instructions and the Alarm Manager screen.

2.1 Working with device-based Alarms and Events (Information Section Only)
Digital (ALMD)
A digital alarm (ALMD instruction) is configured to monitor its input for one of the following alarm conditions:

the input value equal to one

the input value equal to zero

When the alarm condition is true, the alarm enters the In Alarm state. When the alarm condition is false, the alarm enters the
Normal or Out of Alarm state.
Analog (ALMA)
An analog alarm (ALMA instruction) can be configured to monitor for two types of alarm conditions:

Level

Rate of Change

Level Alarms monitor an input for alarm conditions that go In Alarm when the input value goes above or below predefined
limits. When defining a level alarm, you can configure up to four alarm level conditions each with limits (sometimes called
thresholds), a severity and alarm message. The supported alarm conditions are:

High High (HIHI)

High (HI)

Low (LO)

Low Low (LOLO)

Rate of Change alarms monitor an input for alarm conditions that go In Alarm when the input value changes faster or slower
than predefined limits. When defining a rate of change alarm, you can configure up to two rate of change conditions each with
limits, a severity, and an alarm message. The supported alarm conditions are:

Rate of Change Positive (ROC_POS)

Rate of Change Negative (ROC_NEG)

21 of 44

Advantages of alarming instructions in the controller

Alarm instructions are programmed only once, reducing programming effort and errors.
Alarm conditions are detected more quickly.
HMI tags are not required, reducing overhead and device tag mapping errors.
Alarms are managed, processed, and preserved by controllers, even if the HMI goes down.
Data polling is eliminated, which reduces network overhead and controller processing and improves overall system
performance.
Timestamps on alarm conditions are much more accurate, because they are applied in the controller, and not delayed until
they reach the HMI software.
Follows ISA 18 Alarm recommendations.

What is Shelving?
You can shelve an alarm for a piece of equipment in your system that is currently under maintenance.
Shelving an alarm prevents notification of new state changes. Alarms are shelved for the shelve duration as
defined in the controller. Un-shelving an alarm resumes the notification of new state changes.
A shelved alarm:
-

Can still become In Alarm (but the event that makes the alarm In Alarm does not appear in the Alarm
Summary).

Remains unacknowledged until you acknowledge it. Therefore, even if an alarm configured to require
acknowledgment becomes active while shelved, it does not transition to the Active state.

Appears in the Alarm Summary, only if the shelved alarm is unacknowledged.

Appears in the Alarm Manager.

Why is shelving important?

Shelving is essential for helping plant operators address higher priority alarms efficiently and effectively by
allowing the user to temporarily hide lower priority alarms.

22 of 44

2.2 Alarm
m Shelving Settup in Studio 5000
5
Logix Designer
D
1. Thhe default shelving time definned in an alarm
ming instruction in the controlleer is zero. Letss access the
prroperties for thee ALMD instrucction to changee its shelving ti me. In Studio 55000 Logix D
Designer, openn the
DE04_Alarms routine
r
under thhe DE04_Prog
gram and click on the button hhighlighted below to access tthe
prroperties of thee ALMD instrucctions.

2. Change the Sheelving Duration to 5 min and the Maximum S

Shelve Durationn to 10 min andd click OK.

Sh
helve Duration
Shhelve duration iss the length of tim
me in minutes too shelve an alarm
m. The minimum
m is 1 minute. Shhelving an
alarm postpones alarm
a
processing. It is like supprressing an alarm
m, except that shhelving is time lim
mited. If an
alarm is acknowleedged while it is shelved, it remaains acknowledg ed even if it beccomes active agaain. It
beecomes unacknoowledged when the shelve durattion ends, providded the alarm is still active.
Noormally this is ann operator defineed duration. Thee operator will h ave the option too set the shelve time from
the PanelView 5000 terminal in a future release. The operators aability to set the shelve duration is available
onn FactoryTalk View SE 7.0.
Maximum
M
Shelvee Duration
Maximum shelve duration is the maximum
m
time duration in minutees for which an aalarm can be shelved. This
typically is configuured by the systeem designer andd is not operatorr adjustable.

3. Click on the buttton highlighted below to access the propertiies of the ALMA instructions.

23 of 44

M
Shelvve Duration to 10 min, and click OK.
4. Change the Sheelving Duration to 2 min, the Maximum

5. Save your Studio 5000 Logixx Designer prooject and minim

mize the softwaare.

24 of 44

2.3 Deplo
oying an Application in Stud
dio 5000 Vieew Designer
1. Frrom the desktoop, double-clickk on the Lab Fiiles folder
2. Navigate to: Exp
plore Comp
plete and doubble-click the filee SuperJuice__Complete.vpdd.

3. Thhe project is already configurred with the corrrect terminal IP

P address. Froom the main meenu of Studio
50000 View Deesigner, go to Communicatio
C
ons Deployy application.
4. Inn the Deploy Ruuntime Applicaation window, click on the Depploy button highhlighted below to deploy the vview
prroject. Again, thhe project shouuld already be configured withh the correct IP
P address.

5. Once
O
the wizardd is complete (115 20 secondds) with all greeen checkmarkss, click Close.
6. Minimize
M
Studioo 5000 View Designer usingg the control buuttons in the uppper right of the window

25 of 44

7. Double-Click thee PV5000Clien

ntToolUser.exee icon on the ddesktop

8. Inn the window thhat appears, veerify the IP address is 192.1688.1.20, and clicck Reboot.
Note: The
T reboot will taake roughly one minute to compplete.

Note: The final prroduct will run the project automaatically after depployment and coontain a full set oof terminal
coonfiguration screeens.

2.4 Shelving Alarms Detailed

D
Stepss
1. Loocate and presss the Navigatiion button on the bottom of thhe terminal.

2. Navigate to the DE04_Main sccreen. It is locaated in the DE004 folder on thee root of the Naavigation menuu.

26 of 44

3. Once
O
the DE04__Main screen is open, click on the Alarm S ummary Screeen Button.

What
W is an Alarm
m Summary Tab
ble?
Thhe Alarm Summary Table is a lisst of alarms in yoour projects refeerenced controlleer that require attention (i.e.
Allarms that are Inn Alarm and Unaacknowledged).

4. Thhere may be seeveral alarms in the summaryy screen. Acknnowledge all allarms by selectting them and
prressing the Acknowledge Bu
utton.

5. Once
O
the currennt alarms are accknowledged, press the Backk Arrow buttonn to navigate back to the
DE04_Main screeen.

27 of 44

6. Thhe DE04_Main
n screen allowss you to manuaally control an aanalog and diggital alarm in the controller. Lets
sttart by enablingg a digital alarm
m by pressing the
t Enable Alaarm button. Thhe stack light should switch frrom
grreen to red.

7. Navigate to the Alarm Summaary screen.

O the terminal, in the Alarm Summary

S
screeen, scroll up annd press on thee Severity coluumn header (
8. On
tw
wice to sort alarrms by the highhest severity annd locate the foollowing alarm: DE04 Digital Alarm Activee.

Acknow
wledged alarms will have the following icon:
Unacknnowledged alarm
ms will have the following icon:

9. Select the DE044 Digital Alarm

m Active alarm. Press the Accknowledge button.

A
Summaary, select the aalarm first, andd then select the shelve button. The
10. Too shelve an alaarm using the Alarm
Alarm should bee removed from
m the Alarm Summary. Go ahhead and shelvve the DE04 Diigital Alarm Active
alarm.

28 of 44

11. Use the Navigattion button agaain to navigate to

t the Alarm M
Manager screen under the Syystem folder.

What
W is an Alarm
m Manager Tablle?
Thhe Alarm Managger Table is a pree-configured list of all alarms fouund in your projeect's referenced controllers,
reegardless of statee. Alarms listed in the Alarm Maanager include alll of the conditionns for a given alarm.

12. Inn the Alarm Manager screen, it should be eaasy to locate thhe shelved alarm. It will have the shelved icoon in
in the inhibit statte. Select and highlight the DE04
D
Digital A
Alarm Active alarm.

13. Scroll down in thhe details window and locate the shelving deetails. You cann see when thee alarm was
shhelved, who shhelved the alarm
m, and when thhe alarm will bee unshelved.

14. Thhe digital alarm

m will be unsheelved automaticcally after 5 minnutes as we coonfigured them in the Studio
50000 Logix Designer.
D

29 of 44

2.5 Shelving Alarms Additional

A
Steeps
1. Navigate back too the DE04_Maain screen.
2. Disable the Digittal Alarm by prressing the Dissable Alarm buutton.
3. Note the 4 level alarms for the Analog Alarm.. Press the Grreen button to start a simulation. The simullation
will
w slowly increaase the value being
b
monitoredd from 0 to 50000.

4. Navigate to the Alarm Summaary Screen. Accknowledge thhe two low leveel alarms when they appear.
Acknowledge
A
and
a Shelve thee two high alarm
ms as they apppear in the table. The entire ssimulation will ttake
abbout 90 secondds to complete.
5. Affter the two higgh level alarms have been ackknowledged annd shelved, navvigate to the A
Alarm Managerr
Screen.

6. Highlight the DE
E04_Program.m
mySimALMA alarm.
7. Thhe details winddow allows the user to see thee settings for aany digital or annalog alarm connfigured in the Logix
coontroller. The left
l hand side of
o the window allows
a
you to sselect which alaarm to investigaate for a given alarm
instruction. Thee example below
w shows the deetails for the H I level alarm foor DE04_Progrram.mySimALLMA.

These butttons will shelve

or unshelve
e ALL alarms for
a given ala
arm instructio
on.
These
e buttons will shelve or
unshel ve individual alarms for
a givven alarm insttruction.

8. Unshelve the HI alarm by presssing the unsheelve button in tthe top left cornner of the detaails window.

30 of 44

9. Navigate back to
t the Alarm Summary screeen. Verify that the HI alarm foor DE04_Program.mySimALLMA
is present, unshelved and unaccknowledged.

NOTE:
Eaach alarm can be acknowledgedd, shelved or unsshelved from Stuudio 5000 Loggix Designer whiile online
with the controllerr. The Status tabb on the alarm innstruction prope rties window shoows a detailed ssummary of
the state of the alaarm.

2.6 Addin
ng Alarms
1. Maximize
M
Studioo 5000 Logixx Designer.
2. Navigate to the DE04_Alarms routine in the DE04_Progra m program.
W online, add a new rung after
a Rung 5.
3. While
4. Add an ALMA innstruction.

31 of 44

5. Create an ALMA
A backing tag by
b entering the desired tag naame in the instruction.

O
you enter a tag name, click off of the innstruction.
6. Once
7. Right
R
click on the tag name and press New Tag

Name. P
Press Create w
when promptedd.

8. Make
M
sure your instruction looks like the folloowing screen shhot. The backing tag does noot have to be named
thhe same.

9. Click the ALMA properties button.

32 of 44

10. Make
M
changes so
s your configuuration window looks like the oone below.

11. Add custom messsages to eachh level alarm inn the Messagess tab.

12. Press OK.

13. Fiinalize all editss in the controlleer. (

14. On
O the PanelVieew 5000 displaay, navigate to the Alarm Sum
mmary Screenn.
15. Acknowledge all alarms.
16. Navigate to the DE04_Main sccreen.
n simulation staart button for thhe analog alarm
m control.
17. Press the green
A
Summaary Screen.
18. Navigate to the Alarm

33 of 44

19. You should see the level alarms for the analog alarm you just created.
Its that easy to add alarms to a running system!

2.7 Section 2 Summary

You learned

PanelView 5000 displays incorporate Logix based alarming!

Many of the benefits of Alarms and Events can now be realized in the PanelView 5000 displays.

Differences between the Alarm Summary and the Alarm Manager.

The benefits of alarm shelving.

The ease of adding or changing alarms in a runtime environment.

You have finished Section 2 of the lab. Please do not continue unto Section 3 until after the instructor demonstration.

34 of 44

Section 3: High-Speed HMI Button Control

Manual operator actions that were used for positioning mechanical devices (for things such as axis jogs, or linear actuator
movements) require better performance than was available on the traditional HMI. This required most machine builders to add a
physical hard wired button for these operations below/next to the operator interface panels adding cost and reducing flexibility.
Because of the tight integration between Logix controllers and the PanelView 5000 product, this system delivers operator actions
with a fast, highly consistent round trip time.
The HMIBC instruction is a high-speed output control that behaves like the Examine On (XIC) instruction. This instruction
provides the ability for an operator that is interacting with a PanelView 5000 Human Machine Interface (HMI) to initiate machine
control operations, such as jogging a motor or enabling a valve. This is done while maintaining a fast, accurate, and
deterministic response. The HMIBC instruction provides built-in communications diagnostics that permit the instruction to
automatically reset itself should the communications from the controlling HMI become unavailable. Furthermore, multiple
PanelView 5000 panels can control the same HMIBC instruction.
The HMI Button Control (HMIBC) instruction is available in Ladder Logic, Function Block and Structured Text.

Each HMI device that is interacting with an HMIBC instruction can be in one of three states:
Idle - A button that is associated with the HMIBC tag on this HMI device is not currently being pressed. The HMI device has a
valid connection to the controller.
Triggered A button that is associated with the HMIBC tag on this HMI device is being pressed. The HMI device has a valid
connection to the controller.
Connection Faulted - The HMI device does not have a valid connection to the controller. (The button state is unknown.)

You are ready to start with this section of the lab.

35 of 44

3.1. Addin
ng the PanelView 5000 to the I/O Configurration of Logixx
To function, the Logix controoller's I/O configuration must incclude all of the P
PanelView 5000 Human Machinee Interfaces (HM
MIs)
that need too interact with thee HMIBC instrucction.

1. Maximize
M
Studioo 5000 Logixx Designer.
2. You should alreaady be online with
w the controlller. If not, do sso now.
O
so you
y can see thee I/O Configuraation.
3. Scroll down in thhe Controller Organizer
R
on the
t 1756 Backplane
4. Right-Click
5. Select Discoverr Modules

t the Ethernett module that iss assigned to yyour lab stationn.

6. Press the Creatte button next to
a press OK.
7. Enter a name foor the module and
c
the module online.
8. Click YES when prompted to create
ule Discovery window.
w
9. Close the Modu
R
on the Ethernet neetwork under thhe module you just created annd select Discoover Moduless.
10. Right-click

11. Press the Creatte button next to

t the PanelVieew 5500 12 TTouch display.
K.
12. Enter a name foor the PanelVieew 5500 displayy and press OK
c
the module online.
13. Click YES when prompted to create
ule Discovery window.
14. Close the Modu

36 of 44

3.2. Addin
ng the HMIBC instruction in Ladder
D
routine
r
under thhe DE04_Proggram.
1. Add the following rung to the DE04_HMIBC

2. Fiinalize all of thhe edits in the program.

p
3. Save the applicaation.

3.3 Config
guring the buttton on the PaanelView 50000
Additionally, the application created for each PanelView 50000 HMI must incclude button actions configured tto reference the tags
associated with
w the HMIBC instructions thatt are to be controolled.

1. Maximize
M
the Studio
S
5000 View Designer software.
2. Navigate to the Project Explorer tab in the bottom
b
left cornner of you winddow.

37 of 44

3. Frrom the Projecct Explorer, exxpand DE04 folder and doubl e click on DE004_HMIBC to oopen the HMIBC
C
sccreen for editing.

4. Right-click
R
on the green push button and select Button Beehavior Logix HMIBC seet to 1 on press, 0
on
n release. You may need to scroll down onn the screen to locate the greeen button.

5. Loocate the Prop

perties window
w on the right.

38 of 44

6. Click on the Browse button [

] as shown below to open thee Tag Browserr.

7. Note that the tagg browser autoo-filtered all tags with HMIBC as a data type. Double-click oon myHSJ.

8. Thhe Events tab under Propertiees should now be configured as shown beloow

9. Save the changees.

39 of 44

3.4 Deplo
oy the modified
d project to th
he PanelView 5000
5
terminal
1. Frrom the main menu
m
in the Stu
udio 5000 View
V
Designer,, go to Commuunications Deploy
ap
pplication.
2. Inn the Deploy Ruuntime Applicaation window, click on the Depploy button higghlighted below
w.

3. Once
O
the wizardd is complete with
w all green chheckmarks, clicck Close.
4. Minimize
M
Studioo 5000 View Designer usingg the control buuttons in the uppper right of the window

5. Double-Click thee PV5000Clien

ntToolUser.exee icon on the ddesktop

6. Inn the window thhat appears, veerify the IP address is 192.1688.1.20, and clicck Reboot.

Noote: The final prooduct will run thee project automaatically after depployment and contain a full set of terminal
coonfiguration screeens.

40 of 44

7. Maximize
M
Studioo 5000 Logixx Designer.
8. If you are not onnline with the coontroller, do soo now.
9. On
O the PanelVieew 5000 terminnal, navigate too the DE04_HM
MIBC screen.
10. Teest the high sppeed jog button on the terminaal and watch thhe rung in logicc getting energiized in the
DE04_HMIBC rooutine.
W the green button
b
pressed, you should seee the needless on the gauge on the PanelV
View 5000 Term
minal
11. With
coounting.
CHAL
LLENGE: Try too stop the needdles so they aree both in the m
middle and the vvalues are as cclose to 5000 aas
possibble. This wouldd be even moree difficult using traditional po lled communiccation betweenn the controllerr and
the HM
MI for the pushbutton.

NOTE:: This example

e does not show
w the true highh-speed responnsiveness of the HMIBC buttoon since the annalog

value displayed on thhe gauge is updated per the screen

s
refresh rate.

Reeview:
Thhe HMIBC instruuction is a high-sspeed output conntrol that providees the ability for an operator to innitiate
machine control, such
s
as jogging a motor or enabbling a valve, witth a high degreee of accuracy aand
deeterminism. Furrthermore, built--in communications diagnostiics permit the innstruction to autoomatically
reeset itself should the communicaations from the coontrolling HMI b ecome unavailaable.

3.5 Sectio
on 3 Summaryy
You leaarned

How to add thhe PanelView 50000 terminal to the

t I/O Configuraation

How to add thhe HMIBC instruuction in Ladder Logic

How to configgure a button in Studio 5000 View

V Designer too use the HMIBC
C instruction

The benefits to using the HMIBC button as opposed to traditiional polled Coontroller / HMI coommunication.

41 of 44

42 of 44

Sttructured Text exxample;

Fuunction Block exxample;

In Function Block Diagram routinee only, Executionn Order Numberr displays a num
mber that identifiees the
exxecution order off the instruction.

You haave finished Section 3 of the lab.. The lab is now

w complete. Thaank you for attennding!

43 of 44

Puublication XXXX-X
XX###X-EN-P Month
M
Year

Suupersedes Publicatioon XXXX-XX###X-E

EN-P Month Year

44 of 44

Copyright 2013 Rockwell Automation, Inc. All rights reserved.