1. Studio 5000 Logix Designer V24
Dustin Sims
Studio 5000 Logix Designer V24
Features Presentation

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

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

4. Studio 5000
Overview/Direction

5. Studio 5000 Today and Future
System Organization
System Security
& IP Management
Modular
Automation
Device
Management
Library
Management
Collaborative
Engineering
Actionable
Information
Virtual Design
& Engineering
Common
Infrastructure
Scalable
Architecture
Multi-Discipline

6. Studio 5000 Phase 1 - Control Design Logix Designer
RSLogix 5000
Logix Designer the first Element of Studio 5000
V1…16,17,18,19,20
V21,…

7. Version 24 is offering new design workflows to enhance productivity
Before we begin…
Version 24 is offering new design workflows to enhance productivity
Existing workflows will continue to be supported
You do not need to change until you are ready…
But we think you’ll like these changes…

8. Studio 5000 Logix Designer V24
Automation Productivity Release

9. Program Parameters
Studio 5000 Logix Designer Newest Modular Component

10. Programs Before -Conceptual Block Diagram
Previously
Controller Tags
Supports modular automation practices an enables a higher level of encapsulation
AOI-style Input, Output, and In/Out parameters for Programs
Supports strings, arrays, and structures as parameters
Online editable and supports sub-element connections
Ability to interconnect Programs with these parameters
Ability to Copy / Paste Programs without disturbing parameter configuration
Data
Prog_01
Prog_02

11. Program Parameters -Conceptual Block Diagram
NEW
Controller Tags
Supports modular automation practices an enables a higher level of encapsulation
AOI-style Input, Output, and In/Out parameters for Programs
Supports strings, arrays, and structures as parameters
Online editable and supports sub-element connections
Ability to interconnect Programs with these parameters
Ability to Copy / Paste Programs without disturbing parameter configuration
Data
Prog_01
Prog_02

12. The Composition of a Program (Before and After)
Previous
NEW
Prog_01
Prog_01
Local Tags
Code
Routines
Program Tags
INPUT
OUTPUT
InOut
Parameter
Interface
Public
Code
Routines
Supports modular automation practices an enables a higher level of encapsulation
AOI-style Input, Output, and In/Out parameters for Programs
Supports strings, arrays, and structures as parameters
Online editable and supports sub-element connections
Ability to interconnect Programs with these parameters
Ability to Copy / Paste Programs without disturbing parameter configuration
Why add Parameter Interface to Programs?
For A Better Understanding Of Interaction Between Programs

13. Program Parameters -Conceptual Block Diagram
Supports modular automation practices an enables a higher level of encapsulation
AOI-style Input, Output, and In/Out parameters for Programs
Supports strings, arrays, and structures as parameters
Online editable and supports sub-element connections
Ability to interconnect Programs with these parameters
Ability to Copy / Paste Programs without disturbing parameter configuration
Connected Programs Can Form A Larger Object

14. Program Parameters Editor - How To Define A Program Parameter
Shared Editor for Program Parameters and Local Tags
Similar to the AOI Interface

15. Program Parameters Editor - How To Connect A Program Parameter
All In One Editing Environment Makes Connecting Programs Easy

16. Program Parameters Editor - Connecting Program Parameters
AX_Axis01
Prog_20

17. Program Parameters Safety to Standard Connections
Input
EStop
Safety Output parameters can connect to Std program parameter inputs.
However, going the opposite way is prohibited and in order to get Std data into the Safety Task requires that that data be mapped (i.e. Map Safety Tags)
Output
Safety Output and Public Parameters can connect to
Standard Input Parameters

18. Parameter Types Input InOut Output Public Data Flow:
Input / Output - Passed by value
InOut - Passed by Reference (like an Alias, Asynchronously)
Public – Passed by Value

19. Public Parameters - “Global” Tag at a Program Level
Controller Tags
Tag_01
Tag_02
Tag_03
Tag_04
Data Flow:
Public parameters represent a “public” memory space at program level.
They behave very similarly to Controller scope tags.
Can Be Connected to:
Input parameters
Output Parameters
InOut parameters
General FYI:
One Public parameter can be connected or bound to multiple Input, Output or InOut parameters to form a shared memory space.
Publics allow a concentration of data similar to that of a controller tag but at program level.
Shared memory space established at a program level
(Assists with modularity at program level)

20. Public Parameters - “Global” Tag at a Program Level
I have something to say that everyone needs to hear!
Public
Data Flow:
Public parameters represent a “public” memory space at program level.
They behave very similarly to Controller scope tags.
Can Be Connected to:
Input parameters
Output Parameters
InOut parameters
General FYI:
One Public parameter can be connected or bound to multiple Input, Output or InOut parameters to form a shared memory space.
Publics allow a concentration of data similar to that of a controller tag but at program level.
Shared memory space established at a program level
(Assists with modularity at program level)
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.

21. Data Flow How the Parameters Enter & Exit Against Code Execution.
Data Flow
How the Parameters Enter & Exit Against Code Execution.

22. 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

23. Parameter Data Flow - Passing by Value
Name
Value
Code
MY_Tag
7.00
9.00
9.00
Tag
9.00
Value changed
Value is passed into the code.
BUFFERED and code executes with that value
Note that even though the external tag value changes that the internal value used is buffered
(copied in at the beginning of execution and used throughout the scan)
Value Passed in is what was used for Code

24. Parameter Data Flow - Passing by Reference
Name
Value
Code
MY_Tag
8.00
7.75
7.50
7.00
7.25
Tag
7.25
8.00
7.00
7.75
7.50
Pointing to Memory
First difference is that you are actually pointing to a memory.
Second difference is that the internal tracks the outside value.
Value can change throughout code execution
(Real time data update)

25. Logix Designer Modularity – Shared Subroutines Data Flow
Call the Subroutine
The “Original” modular component
JSR - Jump to Subroutine
Passes and returns tags by value.
Pass In THE Values
In a shared subroutine, you are “Sharing Logic” (that you created ONCE) with other routines but PASSING Values to that routine with a Return of value based on that specific call’s
If you have multiple calls to this subroutine, you will most likely not be able to monitor the internals of this subroutine given the individual call.
Think about the scan rate at which this is called.
BUT the usage is as follows:
Their Call..
Their Values…
Their Results…
Return THE Results
Execute Subroutine Logic

26. Logix Designer Modularity – 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)

27. Logix Designer Modularity – Program - Parameter Data Flow
Task Calls the Program
Copy In The Values
Prog_01
Local Tags
Code Routines
Input
Copy
Copy
Copy Out Results
Output
Execute Routine Logic
InOut
Public
InOut Parameters can change within the scan of the Program. (Asynchronously)

28. Conceptual Diagram Direct Access to Program Parameters
Valve
TankCtrl
Parameters
Code
Routines
Parameters
Code
Routines
WaterLevel
Local Tags
Local Tags
Cannot Access Local Tags
from other programs
High_Lvl_Tmr
Format:
\<ProgramName>.Parameter
\Valve.WaterLevel

29. Direct Access to Program Parameters
In-line access to Program Parameters (\prog1.var)
Leading ‘\’ identifies the argument as a program and not as tag
Full Programming Language Support
Format
\<ProgramName>.Parameter
\Valve.WaterLevel
Allows for a more dynamic data values (real-time, un-buffered)

30. Logical Organizer
A new way to view your code

31. Physical Representation: Machine Or Process
VFFS
VFFS
Infeed
Filling
Infeed
Forming
Forming
Filling
Sealing
Sealing
Mixer
From this view, the user will define a multi-level, organizational hierarchy of folders, programs, & phases to represent their system.
View supports same functionality as execution view to create, edit, or delete code.
Organizational hierarchy is stored in the controller and therefore is recoverable on upload.
Drag & drop of structure (program + sub-programs) to and from a library or between projects
Addition
Addition
Mixer
Agitate
Agitate
Transfer
Transfer

32. 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
System Organizer provides a way to create a organizational model of the system from the user’s perspective.
This facilitates good modular automation design practices.
Paradigm shift from how the “controller executes code” to how the “user views the system”.
Programs Span
the Tasks

33. Application Example - Revisited
VFFS
Infeed
Form
Fill
Seal
Logic and Tags
VFFS
Infeed
Filling
Forming
Mixer_01
Addition
Agitate
Transfer
Logic and Tags
Sealing
From this view, the user will define a multi-level, organizational hierarchy of folders, programs, & phases to represent their system.
View supports same functionality as execution view to create, edit, or delete code.
Organizational hierarchy is stored in the controller and therefore is recoverable on upload.
Drag & drop of structure (program + sub-programs) to and from a library or between projects
Addition
Mixer
Agitate
Transfer

34. Logical Organizer View
From this view, the user will define a multi-level, organizational hierarchy of folders, programs, & phases to represent their system.
View supports same functionality as execution view to create, edit, or delete code.
Organizational hierarchy is stored in the controller and therefore is recoverable on upload.
Drag & drop of structure (program + sub-programs) to and from a library or between projects

35. Logical Grouping Of Programs
Introducing a virtual concept of “sub-programs”
14 sub-programs under a single program
Drag & drop of the hierarchy
(program + sub-programs)
Increased number of programs per task to 1000.
Mixer 1
Code
Routines
Parameters
Local Tags
Addition
Agitate
Press Cntrl

36. Creating A Program – In Logical Organizer
Logical View
Execution View
Right Click
Add Program
This slide is used to show that if you create a program folder in the Logical organizer it shows up in the “Unscheduled Program / Phases”
Discuss that you can drag and drop between the two views (i.e. drag from the Logical to the Controller Organizer)
Also Shows Up in
Controller Organizer
Program Created in
Logical Organizer

37. New Ways To View Your Code
My Project .ACD
Logical View
Execution View
This slide is used to assure users that the original way of viewing their code is still there.
Added ability for a more logical view of your system while maintaining your execution view.

38. Accessing the Module Object
Ways to abstract HW centric Logic from your project.

39. What’s the Module Object?
The Module Object provides status information relevant to a module.
The Module
Attributes –
Entry Status
Fault Code
Fault Info
FW Supervisor Status
Force Status
INSTANCE
LED Status
Mode
Path
The Info
How to Access
FYI
That’s New

40. 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

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

42. 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
Possible way to multiplex a single message instruction to handle set up of modules
Coding required! Use a Solid state machine with Error handling.

43. Library Concepts and Enhancements
Creating and Storing Reusable Code

44. 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

45. $ Why Else? Geography Worldwide systems with a common approach
Decreases the differences between systems
Money
Margins on orders can be increased
Allow you to be more competitive $

46. Library Options with XML
Using XML Code
Import/Export
Library Management Tools
Right Click

47. 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

48. Library Concept Utilizing .ACD File
Library .ACD
My Project .ACD
This includes Dependencies
(UDT, AOI’s)
Add to Library
Demonstrate the Flow of using Library content in a project and then likewise populating the Library from a working ACD file.
The Hierarchy will prove to be a very valuable tool going fwd.
Create from Library

49. Partial Import Online/Offline (PIO) Enhancements
Manage references (Tag Aliases, Program Connections)
Manage dependencies (AOI’s UDT’s and Tags)
Manage conflicts (Overwrite or Use Existing)
Optionally include/exclude data values
Supports online and offline workflows
Easily copy content across projects or within project
This capability started in V17 and is continuing to grow today.
Enhancements to PIO
Hierarchy and Groups of Objects
Copy Paste and Drag Drop and Import Export
Optionally include data values

50. Partial Import Online/Offline (PIO) Enhancements
Improved Search and Replace
Anything you can change via PIO dialogs
Wildcards, Replace All
Asterisk = ignore
Find What
Replace With
Text Found
Result
Tk1_*_001
PRE_*_010
Tk1_me_001
PRE_me_010
Tk3_*
Tk4_*
Tk3_unit
Tk4_unit
*001
*002
Mi_2001
Mi_2002

51. Compare and Merge Tool

52. 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

53. Compare and Merge Tool Merging Selected Content

54. 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

55. Multiple Motion Update Rates
Greater Flexibility

56. 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

57. Previous Motion Group Coarse Update Rate
Only 1
Coarse Update Rate
Explain the application where multiple axes exists.
Highlight the fact the there are axes in the system that do not run continuous OR that do not demand a fast CUP.
Highlight the fact that prior to V24 we only have one coarse update rate.
Because we have seen more and more axes being added we saw the need to add some additional flexibility to this. – Then go to the next slide.
Support for three coarse update periods (CUP)
Available for CIP Motion drives and Virtual axes
Synchronized Gear, PCAM, MDSC motion (interpolated axes must all be in the base rate)
Optimize controller, network, and drive performance
Use base rate for high performance drives and alternate rates for lower performance drives
Example: L7x with 15 CIP Motion drives

58. New Functionality Multiple Coarse Update Rates
AX_SetUp_DS
AX_SetUp_Cntr
AX_SetUp_OS
Multiple
Rate Selections
AX_Unw
AX_GR01
AX_GR02
AX_GR03
AX_SetUp_DS
AX_SetUp_Cntr
AX_SetUp_OS
AX_ExConv
AX_Unw
AX_GR01
AX_GR02
AX_GR03
AX_ExConv
Match the Update Rate With The Machine Functionality

59. New Functionality Multiple Coarse Update Rates
Estimated & Actual
Utilization
AX_Unw
AX_SetUp_DS
AX_ExConv
AX_GR01
AX_SetUp_Cntr
AX_GR02
AX_SetUp_OS
AX_GR03
Estimated and actual utilization metrics
Information on important system performance metrics – calculated and runtime actual
FYI: Same metrics are available in Integrated Architecture Builder (IAB)
Manage/predict system performance during design, programming, and commissioning

60. Editor Enhancements
Improved user experience

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

62. Function Block Editor - Keyboard Shortcuts for Quick Navigation
Ctrl
Home
On a per sheet basis. So if you have multiple sheets it will be in reference to the active sheet.
Ctrl
End

63. Sequential Function Chart - Embedded ST Editor Enhancement
Previously
Updated
Horizontal Scroll Bar for the Embedded Structured Text Editor.

64. Multi-Select and Export / Transport Programs, AOI’s, UDT’s and Strings
Left Click
Ctrl
Left Click
Left Click
Shift
Programs (Within the Ctrl Organizer you are confined to the Task for Multi-Select)
AOI’s
UDT’s
Strings
Tags (always been there)
Left Click
Programs, AOI’s, UDT’s and Strings Can be multi-selected and Exported into a Single XML format or Drag and Dropped

65. Controller and Logical Organizer- Program and Phase Delete
Previously
Updated
Right Click
Programs no longer have to be unscheduled and purged of tags to be deleted.

66. Alarming
Improved user experience

67. “Suppressed by Design”*
Alarming
Full ISA 18.2 Alarm State Model Support
“Suppressed by Design”*
“Shelved”
“Out of Service”*
 A&E Device Based alarms will be supported again in V24.  Use with View SE 8.0 with CPR 9 SR 7.1 of FTSP/FTAE.
Managing your Alarming System Health…

68. Logix Designer Notable Mentions
Improved user experience

69. Safe & Standard Connections
FANUC R-30iA Controller
FANUC M-1iA Robot
Provides Flexibility In Designing Safety Systems

70. Operating Systems

71. 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.

72. Logix Designer Supporting Software
Integrating Workflows

73. Protect Your Automation Investment
Manage changes effectively - AssetCentre

74. Common Challenges Lost comments to another program!
Temp changes
cause issues
later
How do I
recover system
quickly?
Lost comments to another program!
Some maintenance practices may be unnecessary
I need to
minimize
downtime
I need to
manage
versions
effectively
When we talk to a customer’s operations team (engineers, maintenance engineers) these are common topics of conversation about their day-to-day activities.
A FactoryTalk AssetCentre system can help with each of these expressed problems.
Who made
changes to
this program?
Dead Battery!
This machine is down again!
Oops! Downloaded wrong program

75. FactoryTalk® AssetCentre Platform
Set of asset-centric focused tools to securely and centrally manage your automated production environment
Centrally archive electronic files/folders
Provide backup and compare of operating asset configurations
Track users’ actions
Secure access
Configure process instruments
Manage process instruments calibrations
Scalable design allows expansion of functionality and device counts
Practical application for small-line applications and site-wide installations
Low entry cost easily supports testing and proof of concept work
FactoryTalk AssetCentre is a tool to manage automation assets

76. Logix Designer Integration with AssetCentre
Possible to add ACD file to Source Control (AssetCentre Archive) directly from Logix Designer
ACD files not opened from Logix Designer source control will detect membership in AssetCentre archive.

77. Working with Logix Designer & Source Control
If file is Checked-In, Logix Designer users can . . .
Check-Out File by . . .
File > Open > Source Control
Navigate and select file, perform Checkout
Logix Designer Indicates Checkout status

78. Working with Logix Designer & Source Control
If file is Checked-Out, Logix Designer users can . . .
Check In with options
Delete (local copy)
Keep Checked Out
Leave Intact (marks as read only)
Undo Check Out with options
Delete
Replace with copy from source control
Show Difference
Between Local project and source control

79. Dustin Sims
Questions??