Using the Library of Process Objects Updated 2014-09-08

8/9/2019 Using the Library of Process Objects Updated 2014-09-08

1/28


2/28

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.

Reusable Library for Design Productivity

Suite of control and

HMI objects to

accelerate projectengineering

Role-based feature set

for Operation

Maintenance

Engineering

2

Process Library –“Out of the Box”


3/28


Library Philosophy

3

Standard Applications

Control Strategies(Contro l Modules)

Library Hierarchy

Devices (valves, motors/ drives, controlalgorithms, transmitters,etc.)

Logix5000 functionblocks, faceplates andgraphic objects

Level control,temperature control,etc.

Mixer/Reactor, etc.

ExampleIncludedin base

system

SystemAdd-On

CustomPurchase

Logix Programming andVisualization Tools

Devices(Process Objects)


4/28


Key Benefits

4

Improvements in:

System “out-of-the-box” experience

Engineering efficiency, plus tools, for Solution Providers

Focus on application engineering rather than building base blocks

Consistency of application solutions from multiple delivery partners

Predictability of system behavior

Library managed by Rockwell Automation

Consistent engineering library framework

In line with customer expectations

TechConnectSM support

Ask for “PlantPAx Support”


5/28


Installing the Library: Logix Components

5

For Add-On Instructions, import only the AOIs you need.


6/28


All Dependencies Are Imported

6

IMPORTANT: All dependencies are included in the AOI import file

Embedded AOIs and all required data types (UDTs, STRINGs)

Example: the P_Motor instruction uses P_Alarm and P_Mode


7/28


Installing the Library: HMI Components

7

First, add the library components to your HMI application (Site Edition or Machine Edition)

1. Import the Images –all the .BMP and/or .PNG files (.BMP and .PNG must be imported separately)

2. Import the Global Objects –all the .GGFX files

3. Import the Displays –only the GFX files you need

4. If using Site Edition, import the Macro – the .MCRfile

5. If using Machine Edition, import the Tags – the .CSV file

Theorder is important: each item depends on the previous items


8/28


Displays: Just the Ones You Need

Each Faceplate or Help Popup counts as only ONE Display

… even though the Faceplate has multiple tabbed views.

P_Motor uses P_Mode, P_Alarm ...so don’t forget to include their Help and Configuration Displays.

SE: Always include “Common Analog Edit” – used for number entry

8


9/28


Create an Instance: Logix

9

Add the instruction (Ladder (LD), Function Block Diagram (FBD), or StructuredText (ST))

Create its backing tag Controller or program scope

You can do this online


10/28


Connect Its I/O

10


11/28


Create an Instance: FactoryTalk® View

11

Open your Display

Drag and Drop the Graphic Symbol

From the appropriate “… Graphics Library” GGFX file

3.0: Note the updated graphics, with .PNG images, throughout the library


12/28


Create an Instance: Link It Up

12

Just ONE global object parameter


13/28


Default Configuration

IMPORTANT:

Every instruction defaults to the

simplest, basic device configuration. Motors: outputs only

with no run feedback

Valves: outputs onlywith no limit switch

feedback

Additional features are used

if you configure / enable them

Defaults are listed in the Reference

Manual for each instruction

13


14/28


Add Run Feedback

Open the faceplate and enable Run Feedback checking

Engineering tab: HAS Run Feedback; Maintenance tab: USE it

14


15/28


“HAS” and “USE”

15

Has: the function exists, is coded

Under control of Engineering

If an AOI does not HAVE afunction, it is not visible toOperators or Maintenance

Use: the function should be usedas intended

Under control of maintenance

Allows bypassing or disabling

a function temporarily

Maintenance Bypass Indicator

Appears when function is

bypassed (Has but not Used)


16/28


Designed Around User Roles

16

Operation, maintenance, engineering tabs

Pre-defined security model

User profiles for operator, operating supervisor, maintenance,maintenance supervisor, manager, engineer, administrator


17/28


Operation:

What Shut Us Down?

17

Interlocks with first-out and individual bypass

Access to logic for complex interlocks

Snapshot when logic triggers shutdown


18/28


Operation:

Where Am I Right Now?

18

Quick access to

detail displays

Highlight of currentstate

Available

commands and data

entries are obvious

Tooltips

Help displays


19/28


Maintenance:

Find and Work Around Problems

19

Goal: no need to force I/O or change code to bypass typical issues

Bypass run feedback, position feedbacks

Substitute PV (discrete or analog input)

Maintenance bypass indicators: follow the breadcrumbs


20/28


21/28


Engineering:

Tools to Manage Configuration

21

Instantiation tools to speed development and roll-out

Demonstrations later

Restricted HMI configuration access for changes


22/28


Library Tools


23/28


Color Change Tool Export displays and global objects from FactoryTalk View Studio

Modify using the color change tool

One color palette Save yours

By function

e.g., “Running”,

“Energized”,

“Fault”

Apply to all

exported displays

and global

objects at once

Import modified displays and global objects into FactoryTalk View Studio

23


24/28


Instance Configuration Tool Microsoft Excel workbook

Uses RSLinx® Classic to configure controller online

Requires RSLinx activation (Gateway, OEM); cannot use RSLinx Lite

Preconfigured sheets (tabs) for Process Library AOIs

All configuration parameters, including local tags

Read configuration from controller Store as archive for disaster recovery

Modify configuration using Excel

Tab for each AOI (class) Copy / paste within or from other tools

Write configuration to controller

NOTE: Tool Requires 32bitMS Excel24


25/28


Alarms Builder and

Tag Data Editing Tool Alarms builder

Creates alarm XML import files:

for FactoryTalk Alarms and Events polling-based tags for FactoryTalk View ME

Preconfigured definitions for Process Library V3.1 AOIs

Alarm tag parameters use underlying Logix tag parameter values Tag data editing tool:

Edit multiple tag data values

Including AOI Local Tags (strings)

In spreadsheet-like table

Copy / paste / import / export / filter functions

Use with any Logix data types: UDTs, AOIs, etc.

Alarms builder and tag data editing tool can be used independently25


26/28


Alarms Builder: QuickBuild QuickBuild creates an XML alarm import file using these settings:

Creates FactoryTalk Alarms and Events discrete alarms

Creates alarm only if P_Alarm “Cfg_Exists” = 1

AckRequired is set to true (AckRequiredhandled by P_Alarm AOI)

Latched is set to false (ResetRequiredhandled by P_Alarm AOI)

P_Alarm priority (1, 2, 3, 4) is mapped to FactoryTalk Alarms and Events severity (1,251, 501, 751)

P_Alarm Cfg_Desc (description) text added to FactoryTalk Alarms and Events alarmmessage

FactoryTalk Alarms and Events alarm name set to object’s tag name + alarm name(‘TI101_Alm_HiHi’)

FactoryTalk Alarms and Events alarm view command set to call up object’s faceplate

FactoryTalk Alarms and Events alarm class set to controller name, program name, tagname, tag type

FactoryTalk Alarms and Events alarm status and control handshake tags automaticallypopulated to link to P_Alarm for acknowledge, suppress/unsuppress, disable/enable,shelve/unshelve

TIP Set up alarms using configuration spreadsheet, then QuickBuildFactoryTalk Alarmsand Events database

26


27/28


Where to find more information?

Process Library Product Profile on

literature library (proces-pp008)

27

Process Library of ProcessObjects Reference Manual on

literature library (proces-rm002)

Process Library of Logix Diagnostic

Objects Reference Manual on

literature library (proces-rm003)


28/28


www.rockwellautomation.com

Follow ROKAutomationon Facebook& Twitter.Connect with us on LinkedIn.

Rev 5058-CO900D

Thank you!

Using the Library of Process Objects Updated 2014-09-08

Documents

Transcript of Using the Library of Process Objects Updated 2014-09-08