AD07 Studio5000NewFeatures PDF

AD07
Studio 5000
New Features and Benefits
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.

Related Sessions
 AD06 Studio 5000 Best Practices

 AD08 ControlLogix, CompactLogix, and GuardLogix Family Overview
 AD09 Intro to Logix Hands-On-Lab
 AD10 Logix Integration Hands-On-Lab
 AD15 FactoryTalk AssetCentre Introduction
 MC05 PowerFlex 520 Series Logix Integration Lab
 PR01 PlantPax Object Overview
 PR03 High Availability
 VI07Panelview Plus 7 New Features & Functions plus Mobility

Topics & Features
Studio 5000 Overview
Program Parameters
Logical Organizer
Module Object

Topics & Features
Code Re-use and Library Concepts
Compare & Merge Tool
Motion Updates
Notable Mentions

Studio 5000 Logix Designer V24
Studio 5000
Overview/Direction

Studio 5000 Today and Future
System System Security

Organization & IP Management
Modular Device
Automation Management
Library Collaborative
Management Engineering
Actionable Virtual Design

Information & Engineering
Common Scalable
Multi-Discipline
Infrastructure Architecture

Studio 5000 Phase 1 - Control Design
Logix Designer
Logix Designer
RSLogix 5000
Logix Designer the first

Element of Studio 5000
V1…16,17,18,19,20 V21,…
Studio 5000 Logix Designer V24
Automation Productivity Release

Program Parameters
Studio 5000 Logix Designer Newest Modular Component

Programs Before
-Conceptual Block Diagram
Previously
Controller Tags
Data
Prog_01 Prog_02

Program Parameters
NEW
Controller Tags
Data
Prog_01 Prog_02

The Composition of a Program
(Before and After)
Prog_01 Previous Prog_01 NEW
Program Tags Local Tags
Code INPUT Code OUTPUT
Routines Routines
Parameter InOut
Interface Public
Why add Parameter Interface to Programs?

For A Better Understanding Of Interaction Between Programs
Program Parameters
Connected Programs Can Form A Larger Object

Program Parameters Editor -
How To Define A Program Parameter
Shared Editor for Program Parameters and Local Tags

Similar to the AOI Interface
How To Connect A Program Parameter
All In One Editing Environment Makes Connecting Programs

Easy
Connecting Program Parameters
AX_Axis01 Prog_04 Prog_20

Program Parameters
Safety to Standard Connections
Input
EStop
Output
Safety Output and Public Parameters can connect to

Standard Input Parameters
Parameter Types

Public Parameters -
“Global” Tag at a Program Level
Controller Tags
Tag_01
Tag_02
Tag_03
Tag_04

Public Parameters -
“Global” Tag at a Program Level
I have something to
say that everyone
needs to hear!
Tag_01
Tag_02
Tag_03
Tag_04
Allows the modularity to be increased at program level.

Creating a world within a world and assign ownership of data.
Data Flow
How the Parameters Enter & Exit Against Code Execution.

Parameter Data Flow -
Passing by Value vs. Reference
What are the differences between these types of data flow?

• Passing By Value:
– Passes the actual value of the tag for code execution
• i.e. the value of DM07_SSL_StateNo , DM07_SSL_In
• Value passed is the value that is used for code
– (Even if the value externally changes)
• Passing By Reference
– Passes the reference to a memory location
• Value can change throughout the execution
• Used for real-time data
– Like an Alias

Passing by Value
Passing By Value
Name Value Code

MY_Tag 9.00
7.00
9.00 Tag 9.00
Value changed
Value Passed in is what was used for Code

Passing by Reference
Passing By Reference
Name Value Code

MY_Tag 7.75
8.00
7.00
7.25
7.50 Tag 7.75
8.00
7.00
7.25
7.50
Pointing to Memory
Value can change throughout code execution

(Real time data update)
Logix Designer Modularity –
Shared Subroutines Data Flow
The “Original” modular component Call the Subroutine
• JSR - Jump to Subroutine

– Passes and returns tags by value.
Pass In THE Values
Execute Subroutine Logic
Return THE Results

AOI - Parameter Data Flow
Call the AOI
Copy In The Values
Execute AOI Logic
Copy Out Results
InOut Parameters can change within the scan of the AOI.

(Asynchronously)
Program - Parameter Data Flow
Task Calls the Program
Copy In The Values

Prog_01
Local Tags
Code Routines
Input Copy Copy Output
Execute Routine Logic

InOut Public
Copy Out Results
InOut Parameters can change within the scan of the Program.

(Asynchronously)
Conceptual Diagram
Direct Access to Program Parameters
Valve TankCtrl
Parameters Parameters
WaterLevel
Code Code
Routines Routines
Local Tags Local Tags
High_Lvl_Tmr
Cannot Access Local Tags

from other programs
Format:
\<ProgramName>.Parameter
\Valve.WaterLevel

Direct Access to Program Parameters
• In-line access to Program Parameters (\prog1.var)

– Leading ‘\’ identifies the argument as a program and not as tag
Format
\<ProgramName>.Parameter
\Valve.WaterLevel
• Full Programming Language Support
Allows for a more dynamic data values (real-time, un-buffered)

Logical Organizer
A new way to view your code

Physical Representation:
Machine Or Process
VFFS
VFFS Infeed Filling
Infeed
Forming
Filling Forming
Sealing
Sealing
Mixer
Addition Addition
Agitate Mixer
Agitate
Transfer
Transfer

Why Add A Logical Organizer?
• To create an organizational model of the system from the

user’s perspective.
• Helps facilitate good modular automation design practices.
• Paradigm shift from how the “controller executes code” to how
the “user views the system”.
Logically
Organized
Programs Span
the Tasks

Application Example - Revisited
VFFS
Infeed Filling
Forming
Sealing
Addition
Mixer
Agitate
Transfer

Logical Organizer View

Logical Grouping Of Programs
Mixer 1
 Introducing a virtual concept of “sub-programs”
Parameters
 14 sub-programs under a single program
Code
Routines
Drag & drop of the hierarchy

Local Tags
Addition 
Parameters
Code
 (program + sub-programs)
Routines
Local Tags
Agitate
 Increased number of programs per task
Parameters
Code
to 1000.
Routines
Local Tags
Press Cntrl
Parameters
Code
Routines
Local Tags

Creating A Program –
In Logical Organizer
Logical View Execution View
Right Click
Add Program
Also Shows Up in
Program Created in Controller Organizer
Logical Organizer

New Ways To View Your Code
My Project .ACD
Logical View Execution View
Added ability for a more logical view of your system while

maintaining your execution view.
Accessing the
Module Module Object
Ways to abstract HW centric Logic from your project.

What’s the Module Object?
• The Module Object provides status information relevant to a module.

The Module • Attributes – The Info
– Entry Status
– Fault Code
– Fault Info
– FW Supervisor Status
How to Access – Force Status
– INSTANCE
– LED Status
– Mode
– Path FYI
That’s New
Access to Module Object within AOIs
• Full Access to the Module Object inside the AOI.

– “ Module Data type as InOut Parameter (AOI and Programs)
– Allows you to point to the module from within an AOI Definition.
AOI Definition
Full Access

Using Program Parameters
Connecting to AOI
Routine
I/O Name InOut Parameter
RIO_01 ModRef_Slot00
Can Reference
Value support………..
Parameters or Physical I/O

New Attribute to the Module Object:
Path
• Use GSV to retrieve the Module Communication

Path
– SINT Array
• Use an SSV to Set the Msg Path

– Abstracted Approach
• Possible Re-use of Message for Multiple modules

– Coding required

Library Concepts
and Enhancements
Creating and Storing Reusable Code

Why Write Reusable Code?
• Why have to start from scratch each project?

– Once you solve and test something why repeat that effort?
• Reusable Code Allows Us
– Align resources to solve new problems
– Avoid making mistakes resolving the same problem over again
• Different people will approach and solve problems
differently
– Allow a collaboration and agreed upon way to tackle the
problems

Library Options
with XML
• Using XML Code

– Import/Export
– Library Management Tools
Right Click

Library Concept with .ACD File
Deployment
 Library File (.ACD File)

 Stored Repository for Code
 Supported content
 Programs, Phases, UDT’s, AOI’s,
& Routines
 Basically anything that can be
imported/exported or
copy/pasted in Logix
 Capability
 Dependencies & Collisions are
managed
 Edit entire library content
 Organizational hierarchies
supported
Library Concept
Utilizing .ACD File
Library .ACD My Project .ACD
This includes
Dependencies
(UDT, AOI’s)
Add to Library
Create from Library

Compare and
Merge Tool

Why Compare and Merge Code?
 Why Compare is necessary:

 Verification of changes made for end user.
 Quickly diagnose what has changed
 Catch simple errors
 Why Merging is necessary:

 Engineering Collaboration
 Merge updates
 Manage Library Content

Compare and Merge Tool
Merging Selected Content

Collaborative Engineering
Compare and Merge Tool
V17-20 RSLogix5000
(V21+) Logix Designer
Selectable
Side by Side
Comparison and Merge
Programs
Tags & I/O
Routines
Motion Groups
AOI
UDT

Multiple Motion
Update Rates
Greater Flexibility

Machine Design Evolution
Only Operate At
Machine Set Up
Machine designs are

evolving to include more
axes for different needs
and rate requirements
Run when
needed
Run Continuous

Previous
Motion Group Coarse Update Rate
Only 1
Coarse Update Rate

New Functionality
Multiple Coarse Update Rates
AX_SetUp_DS
AX_SetUp_Cntr
AX_SetUp_OS
Multiple
Rate Selections
AX_Unw AX_SetUp_DS AX_ExConv

AX_GR01 AX_SetUp_Cntr
AX_GR02 AX_SetUp_OS
AX_GR03
AX_Unw
AX_GR01
AX_GR02
AX_ExConv
AX_GR03
Match the Update Rate With The Machine Functionality

New Functionality
Multiple Coarse Update Rates
Estimated & Actual

AX_Unw
AX_GR01
AX_SetUp_DS
AX_SetUp_Cntr
Utilization
AX_ExConv
AX_GR02 AX_SetUp_OS
AX_GR03

Editor Enhancements
Improved user experience

Function Block Editor -
Rename Connector Group
Right Click
Ability to Rename ICON/OCON as a connector group.

Function Block Editor -
Keyboard Shortcuts for Quick Navigation
Ctrl Home
Ctrl End

Logix Designer
Notable Mentions
Improved user experience

Safe & Standard Connections
Provides Flexibility In Designing Safety Systems

Operating Systems

Operating System Support
Microsoft Windows 7
Microsoft Windows Server 2008 R2
Microsoft Windows 8/8.1
Microsoft Windows Server 2012
Microsoft Windows Server 2012 R2
Important: Logix Designer V24 is expected to operate correctly on all editions and service packs of the
above operating systems but has not been tested on all permutations. For the specific list of tested
operating systems, please see V24 release notes.
Important: While the Windows 8.0 and Windows 8.1 operating systems run on many touch-enabled
devices, various features of the Logix Designer application may not be touch-enabled. Most
functions are expected to work with touch, but the software has only been tested with a keyboard
and mouse.

Related Sessions and Location
 AD06 Studio 5000 Best Practices

 AD08 ControlLogix, CompactLogix, and GuardLogix Family Overview
 AD09 Intro to Logix Hands-On-Lab
 AD10 Logix Integration Hands-On-Lab
 AD15 FactoryTalk AssetCentre Introduction
 MC05 PowerFlex 520 Series Logix Integration Lab
 PR01 PlantPax Object Overview
 PR03 High Availability
 VI07Panelview Plus 7 New Features & Functions plus Mobility
You can Find the Logix Controllers

throughout the Solution Areas

Questions ?
Thank You for Attending

AD07 Studio5000NewFeatures PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

AD07 Studio5000NewFeatures PDF

Încărcat de

Drepturi de autor:

Formate disponibile

AD07

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

 AD06 Studio 5000 Best Practices

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

Studio 5000 Overview

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

Code Re-use and Library Concepts

Compare & Merge Tool

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

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

System System Security

Actionable Virtual Design

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

Logix Designer the first

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

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

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

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

Prog_01 Previous Prog_01 NEW

Program Tags Local Tags

Code INPUT Code OUTPUT

Why add Parameter Interface to Programs?

Connected Programs Can Form A Larger Object

Shared Editor for Program Parameters and Local Tags

All In One Editing Environment Makes Connecting Programs

AX_Axis01 Prog_04 Prog_20

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

Safety Output and Public Parameters can connect to

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

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

Allows the modularity to be increased at program level.

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

What are the differences between these types of data flow?

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

Name Value Code

Value Passed in is what was used for Code

Name Value Code

Value can change throughout code execution

The “Original” modular component Call the Subroutine

• JSR - Jump to Subroutine

Execute Subroutine Logic

Return THE Results

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

Call the AOI

Copy In The Values

Execute AOI Logic

Copy Out Results

InOut Parameters can change within the scan of the AOI.

Task Calls the Program

Copy In The Values

Execute Routine Logic

Copy Out Results

InOut Parameters can change within the scan of the Program.

Cannot Access Local Tags

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

• In-line access to Program Parameters (\prog1.var)

• Full Programming Language Support

Allows for a more dynamic data values (real-time, un-buffered)

A new way to view your code

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

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

• To create an organizational model of the system from the

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