Scribd
Upload
769 views4 pages

PlantPAx Library Faceplate To Faceplate Navigation

The PlantPAx library faceplate navigation has two methods - using fixed tagnames or user configured tags. The fixed tagname method navigates to upstream/downstream objects using suffixes added to the parent object's tagname. The user configured method requires developers to enter tagnames for upstream/downstream objects in the parent object's faceplate. Both methods allow navigation between related faceplates to show process data.

Uploaded by

jaysonlkh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
769 views4 pages

PlantPAx Library Faceplate To Faceplate Navigation

The PlantPAx library faceplate navigation has two methods - using fixed tagnames or user configured tags. The fixed tagname method navigates to upstream/downstream objects using suffixes added to the parent object's tagname. The user configured method requires developers to enter tagnames for upstream/downstream objects in the parent object's faceplate. Both methods allow navigation between related faceplates to show process data.

Uploaded by

jaysonlkh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

PlantPAx Library Faceplate to Faceplate

Navigation
The 3.0 release of the PlantPAx library has two different methods for faceplate to faceplate navigation.
The first method uses fixed names to determine the object name of the destination faceplate. The
second method requires the developer configure an object by entering the tagnames the object can
navigate. Both of these methods are described in this document.

Navigate using Fixed Tagnames


Navigation using fixed tagnames is used when an object has upstream or downstream objects that are
used by that object and usually not shared with other objects. The following objects fall in this category:

Analog Input Channel Objects (e.g. P_AIChan)


Interlock Objects (e.g. P_Intlk)
Permissive Objects (e.g. P_Perm)
Restart Inhibit Objects (e.g. P_ResInh)
Motor Overload Objects
Runtime (e.g. P_RunTime)
Valve Stats (e.g. P_ValveStats)

The fixed tagnames are created by taking the parent object tagname and appending a suffix. The table
below lists each AOI that navigates using fixed tagnames along with the required suffix to create the
upstream or downstream objects tagname.
Upstream Objects
AOI
P_AIn
P_AInAdv
P_AInDual
P_AInMulti

Channel
Object

_Chan
_Chan
_ChanA
_ChanB
_ChanA
_ChanB
_ChanC
_ChanD
_ChanE
_ChanF
_ChanG
_ChanH

Interlock

Permissive

Downstream Objects
Restart
Inhibit

Overload

Run Time

Valve Stats

Upstream Objects
AOI
P_AOut
P_D4SD

Channel
Object

Interlock

_Intlk
_Intlk

P_DoseFM

_ChanRate
_ChanQty

P_DoseWS
P_DOut
P_Motor
P_Motor2Spd

_Chan
_Intlk
_Intlk
_Intlk

Permissive

Downstream Objects
Restart
Inhibit

Overload

Run Time

_ResInh
_ResInh

_Ovld
_Ovld

_RunTime
_RunTime

_ResInh

_Ovld
_Ovld

_RunTime
_RunTime

Valve Stats

_Perm0
_Perm1
_Perm2
_Perm3

_Perm
_Perm
_Perm
_FastPerm
_SlowPerm

P_MotorHO
P_MotorRev

_Intlk
_Intlk

P_nPos
P_Perm
P_PF753

_Intlk

_Perm

_Intlk

_FwdPerm
_RevPerm

_ResInh

_RunTime

P_PF755

_Intlk

_FwdPerm
_RevPerm

_ResInh

_RunTime

P_PIDAdv
P_PIDE
P_ValveC
P_ValveHO
P_ValveMO

_Intlk
_Intlk
_Intlk
_Intlk

P_ValveMP
P_ValveSO
P_VSD

_Intlk
_Intlk
_Intlk

_FwdPerm
_RevPerm

_ValveStats
_ValveStats

_OpenPerm
_ClosePerm
_Perm
_Perm
_FwdPerm
_RevPerm

_ValveStats
_ValveStats
_ResInh

_RunTime

Here are some examples of the fixed tagnames:


If a P_Motor2Spd object has the name"Motor123", then its Fast Permissive object must be named
"Motor123_FastPerm"
If a P_ValveSO object has the name"Valve123", then its Interlock object must be named "Valve123_Intlk"
If a P_AInDual object has the name"AIn123", then its Channel A object must be named "AIn123_ChanA"

If a P_ValveMO object has the name"Valve123", then its Valve Stats object must be named
"Valve123_ValveStats"
If a P_Motor object has the name"Motor123", then its Run Time object must be named
"Motor123_RunTime"
If there is a case where one of the upstream or downstream objects is shared by more than one parent
object, then Tag Aliases can be created in the controller for each parent object.

Note: When using FactoryTalk View SE, the object types are not strict. For example, a P_Din object may
be used in place of an interlock object and the navigation still works as long as the P_Din object is
named according to the rules above.
Note: When using FactoryTalk View ME, the object types are strict. For example, only a P_Intlk object
may be used for an interlock without modifying the library faceplates.

Navigate using User Configured Tags


Navigation using configured tags is used when an object has upstream or downstream objects that are
not directly related to the object and can be shared with other objects.
The table below lists the objects that have this type of navigation along with the upstream or
downstream object they can navigate.

AOI
P_AOut
P_Fanout
P_Intlk
P_Logic
P_Perm
P_PIDAdv
P_PIDE
P_ValveC

Upstream

Downstream

Description

Description

CV Source
Input CV
Inputs
Inputs
Inputs
PV, CascSP
PV, CascSP
CV Source

CV Outputs

CV Output
CV Output

For these objects the upstream or downstream tags are entered in the engineering tab of the objects
faceplate. To save controller memory, only the tag name needs to be entered. The path to the tag
name is configured in the Objects Global Object Parameter list.
Important: When configuring the Path in the global object parameters, the program name along with
the following period (.) should be included for program scoped tags. For example, if your tag is in the
program MyProgram, then the path in the global object parameters should look like this:
[MyCLX]Program:MyProgram..

Important: This type of navigation is not available in FactoryTalk View ME.

Navigation Methods in FactoryTalk View SE Library Faceplates


All objects now have the tags Inf_Type and Inf_Lib to allow for auto-discovery. When the display
element is clicked, the Inf_Type and Inf_Lib tag are read and used to build the name of the faceplate
display to call up.
All faceplates are identified by their type tag (Inf_Type) and library tag (Inf_Lib) in the object's AOI.
These tags are read and used to build the display name of the faceplate. Display names are built as
follows: ({value of Inf_Type}) {value of Inf_Lib}-faceplate
With this method, the HMI developer does not need to know the object's faceplate during design. Also,
by modifying these tags in the AOI, the developer can display a custom faceplate using a standard library
display element.
NOTE: When importing library 3.0 into an existing application, be sure the Inf_Type and Inf_Lib Local
Tag strings are set properly to the default value (same as the instruction name and RA-BAS
respectively). If not set properly, attempting to navigate to the particular analog input faceplate will
result in a display not found message.
To support the new navigation capabilities, one macro file (NavToObject.mcr) must be installed in
FactoryTalk View SE (along with the images, global objects and displays).

You might also like