Professional Documents
Culture Documents
Chapter 1
Chapter 2
Chapter 3
Chapter 4
Chapter 5
Chapter 6
Chapter 7
Chapter 8
Chapter 9
Chapter 10
Chapter 11
Chapter 12
Chapter 13
Appendix A
Log on, log off, and set About Studio 5000 Architect software and FactoryTalk Security Single Sign-On
.............................................................................................................................................. 133
security policies
Log on to FactoryTalk..................................................................................................... 134
Change the logged on user account .............................................................................. 134
Change a password ........................................................................................................... 135
Log off Studio 5000 Architect software ...................................................................... 135
Set FactoryTalk Directory permissions ....................................................................... 136
Set Studio 5000 Architect permissions ........................................................................ 137
Set Logix Designer permissions ..................................................................................... 137
Set FactoryTalk View SE permissions .......................................................................... 138
Set FactoryTalk View Machine Edition permissions................................................ 139
Studio 5000 Architect Feature Security policies........................................................ 139
Required Studio 5000 Architect permissions............................................................. 140
Required Logix Designer policies and permissions for Studio 5000 Architect
software .............................................................................................................................. 140
Required FactoryTalk View SE permissions for Studio 5000 Architect software
.............................................................................................................................................. 141
Required FactoryTalk View Machine Edition permissions for Studio 5000
Architect software ............................................................................................................ 142
Log on to FactoryTalk..................................................................................................... 142
Studio 5000 Architect software is a tool for creating the basic I/O and
communication configurations for automation systems. Using the visual editing
system in Studio 5000 Architect software, you can rapidly assemble and connect
control hardware, I/O modules, and visualization devices.
You can also create and import FactoryTalk View Site Edition and FactoryTalk
View Machine Edition visualization projects, including PanelView Plus graphic
terminals, MobileView graphic terminals, RSLinx Enterprise and FactoryTalk
Alarms and Events servers. Edit screen resolution, areas, shortcuts, and network
configuration in Studio 5000 Architect. Edit application screens and program
logic by launching FactoryTalk View Studio.
See also
Use Hardware Diagram to view and organize components that are added to a
Studio 5000 Architect project. If multiple hardware diagrams are open
simultaneously, switch between them using the tabs at the top of Hardware
Diagram.
A large hardware diagram can exceed the display area in Hardware Diagram. Use
the scroll bars or Diagram Overview to navigate to a section of a hardware
diagram.
See also
Use Project Explorer to view or edit the contents of a Studio 5000 Architect
project.
Components An alphabetical list of hardware components added to a hardware diagram, such as chassis, controllers, modules,
computers, PanelView Plus and MobileView terminals.
See also
Use Toolbox to view default hardware components or add, remove, and manage
custom libraries. Drag components from the Toolbox to a Hardware Diagram to
add components to a project.
Product Catalog A list of Logix Designer and FactoryTalk View Studio components that can be added to a hardware diagram.
Libraries A list of libraries containing components that can be added to a hardware diagram or a Logix Designer or FactoryTalk
View Studio project.
See also
Add components to your project from a library, import them from a file or online
controller, or remove them from the project. Once added, connect components to
networks and configure relationships to share tags and control an automation
system.
See also
Install and activate Studio 5000 Architect software on a computer that meets the
system requirements to begin designing automation systems.
See also
To run Studio 5000 Architect software version 2.00.00, the host computer must
System requirements
meet the hardware, software, and firmware requirements. For the latest
compatibility information, refer to the Product Compatibility and Download
Center.
Hardware requirements
Software requirements
* See Studio 5000 Architect Release Notes for anomalies regarding Windows 10
support.
Firmware requirements
Studio 5000 Architect software does not have any firmware requirements.
Hardware and software products used in Studio 5000 Architect projects might
place limits on firmware versions. Read the release notes for each product in the
FactoryTalk system to determine firmware limitations.
See also
Install Studio 5000 Architect software on a computer that meets the system
Install Studio 5000
requirements to begin designing automation systems.
Architect software
To install Studio 5000 Architect software:
4. In End User License Agreements, read the license agreements, then select
an option:
See also
Activate Studio 5000 Studio 5000 Architect software is copy protected and must be activated using
FactoryTalk Activation Manager software. When you start Studio 5000 Architect
Architect software software, FactoryTalk Activation Manager software verifies its activation is valid.
If Studio 5000 Architect software has not yet been activated, you can use the
software for a seven-day grace period with full functionality. If the grace period
ends and Studio 5000 Architect software has not been successfully activated,
Studio 5000 Architect software will not start and an error will be logged to
FactoryTalk Diagnostics.
If you are unable to complete the activation process from the computer on which
you installed Studio 5000 Architect software, you can obtain an activation from
the Rockwell Automation Activation web site.
See also
Use the Studio 5000 Launcher to create or open a Studio 5000 Architect
project. After you design your automation system, save and close the project.
See also
Studio 5000 Architect projects are saved as a project file (.ADL) and a project
About projects
folder containing related files. Studio 5000 Architect projects are composed of
Hardware Diagrams and Components.
Hardware Diagrams
Hardware diagrams are displayed in Hardware Diagram and under the Projects
and Devices folders in Project Explorer. As hardware diagrams are added,
removed, and renamed, the corresponding folders in Project Explorer are added,
removed, and renamed.
Components
shown in the Project Explorer tree under the Projects folder. Software
components are stored as Logix Designer (.ACD) files and FactoryTalk View
Studio project folders under the Studio 5000 Architect project folder. Edit the
project files and folders using Logix Designer and FactoryTalk View Studio.
Graphics, files, text boxes, shapes, and links are reference components that
describe other components. Reference components are only shown in Hardware
Diagram. Reference components are stored as part of the Studio 5000 Architect
project file.
See also
Create a project To design a new automation system, create a Studio 5000 Architect project.
Studio 5000 Architect projects are stored in the logged in user's directory at
Documents\Studio 5000\Projects by default.
7. Click Finish.
See also
Open a project To edit an existing Studio 5000 Architect project, open it using the Studio 5000.
Studio 5000 Architect projects are stored in the logged in user's directory at
Documents\Studio 5000\Projects by default. Each instance of Studio 5000
Architect software can have a single open project.
If the Studio 5000 Architect project contains Logix Designer or FactoryTalk View
applications and those projects have changed, Studio 5000 Architect software
displays Project Update to update the hardware diagram.
To open a project:
4. Navigate to the folder that contains your Studio 5000 Architect project file.
6. Click Open.
See also
Save a project Saving a project records the locations, properties, relationships, and tags of all
components in the Studio 5000 Architect project file. By default, Studio 5000
Architect projects are stored in the directory of the logged in user at
Documents\Studio 5000\Projects.
To save a project:
2. (optional) In Save Project As, enter a name for the new project.
3. (optional) In Save Project As, select a location to store the project file.
4. Click Save.
See also
Close a project Each instance of Studio 5000 Architect software can have a single open project.
To open a project in the same Studio 5000 Architect instance, first close the
current project.
To close a project
See also
Project Update only appears when you open a Studio 5000 Architect
project that contains Logix Designer or FactoryTalk View projects. If the
Logix Designer or FactoryTalk View project has changed since the last time
the Studio 5000 Architect project was opened, Studio 5000 Architect
displays Project Update.
Use Project Update to select which controllers and project files overwrite
components in the Studio 5000 Architect project. The Selected controller
validation results table lists all the changes to be made to the Studio 5000
Architect project.
See also
If you add or move components past the right or bottom edge of a hardware
diagram, Studio 5000 Architect automatically expands the hardware diagram to a
new page. Page breaks show as dashed gray lines and do not print. When you close
and reopen a hardware diagram, Studio 5000 Architect automatically shrinks the
hardware diagram to the number of pages necessary to show the components in
the hardware diagram.
Hardware diagrams are displayed in Hardware Diagram and under the Projects
and Devices folders in Project Explorer.
See also
Add a hardware diagram Add a hardware diagram to group a new set of components within the same
Studio 5000 Architect project.
2. (optional) In Enter New Hardware Diagram Name, type a name for the
new hardware diagram.
3. Click OK. The new hardware diagram appears in the Hardware Diagram
and under the Project and Devices folders in Project Explorer.
See also
Open a hardware diagram Open a hardware diagram to view or edit its components.
In Project Explorer, expand the Project or Devices folders, then click the
hardware diagram to open.
See also
Navigate a hardware A large hardware diagram can exceed the display area in Hardware Diagram. Use
Diagram Overview to quickly navigate to a section of a hardware diagram.
diagram
To navigate a hardware diagram
See also
Show or hide the grid Show the grid to align components vertically or horizontally on a hardware
diagram. Hide the grid to only view components.
Components placed on the hardware diagram use the Snap to Grid setting even if
the grid is hidden.
See also
Enable or disable snap to When Snap to Grid is enabled, components dropped on the Hardware Diagram
pane automatically align horizontally and vertically to the grid lines, even if the
grid grid lines are hidden. When Snap to Grid is disabled, components are placed on
the Hardware Diagram pane where they are dropped.
Below Hardware Diagram, click Snap to grid or Turn off snap to grid.
See also
Close a hardware diagram Close a hardware diagram to hide a hardware diagram from view without closing
the Studio 5000 Architect project.
See also
Remove a hardware Remove a hardware diagram to delete it and all associated hardware components
and software projects from a Studio 5000 Architect project. The remove
diagram operation cannot be undone.
See also
The red rectangle in Diagram Overview represents the current view in Hardware
Diagram. Clicking in Diagram Overview centers both the red rectangle and
Hardware Diagram at the clicked location.
See also
Use Hardware Diagram to view and organize components that are added to a
Studio 5000 Architect project. If multiple hardware diagrams are open
simultaneously, switch between them using the tabs at the top of Hardware
Diagram.
A large hardware diagram can exceed the display area in Hardware Diagram. Use
the scroll bars or Diagram Overview to navigate to a section of a hardware
diagram.
See also
Add components to your project from the Toolbox, using the predefined
components or an imported library. Once added, connect components to
networks and configure relationships to share tags and control an automation
system.
For a list of supported Logix Designer controllers, see Studio 5000 Architect Help.
See also
See also
Add a 1756 ControlLogix chassis Automation systems driven by 1756 ControlLogix controllers require one or
more chassis to connect controllers and I/O modules.
3. (optional) In New Chassis Graphic, enter a unique name for the chassis.
See also
Add a 1756-L6x or L7x Automation systems driven by 1756-L6x or L7x ControlLogix controllers require
one or more controllers to manage inputs, outputs, and run applications.
ControlLogix controller
Before you begin:
5. Click OK. In Hardware Diagram, the controller snaps into its slot in the
chassis. Project Explorer shows the controller in Devices.
See also
Add a 1756-L8x ControlLogix Automation systems driven by 1756-L8x ControlLogix controllers require one or
more controllers to manage inputs, outputs, and run applications.
controller
Before you begin:
5. Click OK. In Hardware Diagram, the controller snaps into its slot in the
chassis. Project Explorer shows the controller in Devices.
See also
3. (optional) In Enter Name, type a unique name for the controller, then click
OK.
Use New Controller Graphic to set firmware, project, and hardware settings for a
new controller. You can edit these settings after the controller is added to the
project.
Bank 2 Contains the information of the expansion bank, for example, slot number, power L3x and L4x
supply, and cable type.
Bank 3 Contains the information of the expansion bank, for example, slot number, and power L3x and L4x
supply.
Slots Left Specifies the number of 1769 slots to the left of the power supply in the bank. L3x and L4x
Slots Right 1
Specifies the number of 1769 slots to the right of the power supply in the bank. L3x and L4x
Power Supply Specifies the power supply catalog number. L3x and L4x
Cable Type Specifies the cable type between banks. After selecting a cable type, the banks are L3x and L4x
connected automatically.
There are three cable types, 1769-CRLx, 1769-CRRx, and 1769-CLLx, where x means the
length of the cable (1 or 3):
1769-CRLx: connection from the right side of one bank to the left side of the next
bank.
1769-CRRx: connection from the right side of one bank to the right side of the next
bank.
1769-CLLx: connection from the left side of one bank to the left side of the next bank.
This cable can be used only to connect banks 2 and 3.
See also
Add 176x/5069 You can add a variety of 1768, 1769, and 5069 CompactLogix controllers, banks,
expansion slots, and modules to a Studio 5000 Architect project. Controllers,
CompactLogix hardware banks, slots, and modules appear in Hardware Diagram and Project Explorer.
See also
Add a 1768-L4x CompactLogix Automation systems driven by 1768-L4x CompactLogix controllers require one
or more controllers to manage inputs, outputs, and run applications.
controller
To add a 1768-L4 CompactLogix controller:
Slot Left: Enter the number of left slots for each bank.
Power Supply: Select the power supply for each bank.
Slot Right: Enter the number of right slots for each bank.
Cable Type: Select a type of cable to connect banks 1 and 2 or banks 2
and 3.
6. Click OK. The CompactLogix controller, banks, slots, power supplies, and
cables appear in Hardware Diagram. Project Explorer shows the
CompactLogix controller, banks, slots, and power supplies in Hardware
Diagrams.
See also
Add a 1769-L1x CompactLogix Automation systems driven by 1769-L1x CompactLogix controllers require one
or more controllers to manage inputs, outputs, and run applications.
controller
To add a 1769-L1x CompactLogix controller:
4. Click OK. The CompactLogix controller, banks, and expansion slots appear
in Hardware Diagram. Project Explorer shows the CompactLogix
controller, banks, and expansion slots in Devices.
See also
Add a 1769-L23x CompactLogix Automation systems driven by 1769-L23x CompactLogix controllers require one
or more controllers to manage inputs, outputs, and run applications.
controller
To add a 1769-L23x CompactLogix controller:
4. Click OK. The CompactLogix controller, banks, and expansion slots appear
in Hardware Diagram. Project Explorer shows the CompactLogix
controller, banks, and expansion slots in Devices.
See also
Add a 1769-L24x or L27x Automation systems driven by 1769-L24x or L27x CompactLogix controllers
require one or more controllers to manage inputs, outputs, and run applications.
CompactLogix controller
To add a 1769-L24x or L27x CompactLogix controller:
4. Click OK. The CompactLogix controller, banks, and expansion slots appear
in Hardware Diagram. Project Explorer shows the CompactLogix
controller, banks, and expansion slots in Devices.
See also
Add a 1769-L3x CompactLogix Automation systems driven by 1769-L3x CompactLogix controllers require one
or more controllers to manage inputs, outputs, and run applications.
controller
To add a 1769-L3x CompactLogix controller:
Slot Left: Enter the number of left slots for each bank.
Power Supply: Select the power supply for each bank.
Slot Right: Enter the number of right slots for each bank.
Cable Type: Select a type of cable to connect banks 1 and 2 or banks 2
and 3.
5. Click OK. The CompactLogix controller, banks, slots, power supplies, and
cables appear in Hardware Diagram. Project Explorer shows the
CompactLogix controller, banks, slots, and power supplies in Devices.
See also
Add a 5069-L3x CompactLogix Automation systems driven by 5069-L3x CompactLogix controllers require one
or more controllers to manage inputs, outputs, and run applications.
controller
To add a 5069-L3x CompactLogix bank:
See also
4. Click OK. The 5069-AEN2TR, 5069 CompactLogix bank and slots appear
in Hardware Diagram. Project Explorer shows the CompactLogix
controller, banks, and slots in Devices.
See also
Add an expansion slot Before you can add a module to a 1769/68 CompactLogix bank or POINT I/O
communication module, the controller must have an available expansion slot. You
can add expansion slots until the controller has reached its limit.
See also
3. (optional) In Enter Name, type a unique name for the controller, then click
OK.
Use New Controller Graphic to set firmware, project, and hardware settings for a
new controller. You can edit these settings after the controller is added to the
project.
See also
Use New 5069-AEN2TR Graphic to set a name and number of expansion slots
for a new 5069-AEN2TR communication module.
See also
Add modules Add or remove modules for 1756 ControlLogix, 1769/68 CompactLogix,
1794/97 FLEX I/O, and 1734 POINT I/O hardware. You can add modules to a
project without a related chassis or controller, but most modules require a
See also
Add a module Automation systems require one or more modules to drive inputs, outputs, or
handle communications.
To add a module:
Tip: The unused slot turns green if it is compatible or red if it is not compatible.
3. (optional) In New Module Graphic, enter a unique name for the module,
then click OK. In Hardware Diagram, the module snaps into its slot in the
chassis. Project Explorer shows the module in Projects and Devices.
See also
About unsupported modules Modules updated or imported from a controller or Logix Designer project may
not be supported in Studio 5000 Architect. When a module is not supported,
Studio 5000 Architect displays an unsupported module image in the appropriate
chassis, DIN rail, or expansion slot.
For this family of devices: Studio 5000 Architect displays this image:
1756 ControlLogix
1768/69 CompactLogix
See also
Add Kinetix servo drives Add Kinetix servo drives to operate multi-axis motion controls using a Logix
Designer project. Servo drives appear in Hardware Diagram and Project
Explorer.
Important: Using Kinetix drives in Studio 5000 Architect software requires Logix
Designer 24.x through 30.x.
See also
Add a Kinetix servo drive Add a Kinetix servo drive to run multi-axis motion controls from a Logix
Designer project.
Important: Using Kinetix drives in Studio 5000 Architect software requires Logix
Designer 24.x through 30.x.
See also
New Servo Drive Graphic How do I open New Servo Drive Graphic?
Use New Servo Drive Graphic to set description, and network settings for a new
servo drive.
Important: Using Kinetix drives in Studio 5000 Architect software requires Logix
Designer 24.x through 30.x.
Setting Description
Type Sets the type of the servo drive.
Vendor Shows the vendor information of the servo drive.
Name Sets the name of the servo drive.
Description Sets the description of the servo drive. Cannot be longer than 128 characters.
Change DC BUS Supply/Line Filter Sets the number and type of power supply/line filters for the servo drive. Only shown for Kinetix
5700 devices.
Setting Description
Address/Host Name Sets the network configuration of the servo drive.
Private Network: Select the value from the list, from 1 to 254.
IP Address: Enter a unique IP address to identify the servo drive on the IP network.
Host Name: Enter a fully qualified domain name, such as servodrive.yourcompany.com.
See also
Add PowerFlex drives Add a PowerFlex drive to connect and control it in a FactoryTalk system.
Important: Using PowerFlex drives in Studio 5000 Architect software requires Logix
Designer 24.x through 30.x.
See also
Add a PowerFlex drive Add a PowerFlex drive to control it from a Logix Designer project.
Important: Using PowerFlex drives in Studio 5000 Architect software requires Logix
Designer 24.x through 30.x.
5. Click OK. The drive appears in the Hardware Diagram pane. Project
Explorer shows the drive in Devices.
See also
Important: Using PowerFlex drives in Studio 5000 Architect software requires Logix
Designer 24.x through 30.x.
Field Description
Name Sets a unique name for the drive.
Description Sets the description for the drive. Cannot be longer than 128 characters.
Address / Host Name Sets the IP address or host name for the drive.
Always show this dialog If unchecked, New PowerFlex Graphic does not open the next time a drive is added to the Hardware Diagram. New drives use the
default settings.
See also
Add PanelView Plus and You can add or remove PanelView Plus and MobileView graphic terminals to your
project. Adding a PanelView Plus or MobileView terminal creates a new
MobileView graphic FactoryTalk View Machine Edition application.
terminals
See also
Add a PanelView Plus graphic Add a variety of PanelView Plus graphic terminals to a Studio 5000 Architect
project. Adding a PanelView Plus terminal creates a new FactoryTalk View
terminal
Machine Edition application.
5. Click OK.
Name: Enter a unique name for the application. Studio 5000 Architect
creates a new FactoryTalk View Machine Edition application.
(optional) Description: Enter a description of the application. Cannot
be longer than 128 characters.
(optional) Scale Replace Displays: Select to scale objects in Replace
displays to the resolution of the panel.
(optional) Scale OnTop Displays: Select to scale objects in OnTop
displays to the resolution of the panel.
(optional) Language: Select a language for the application.
See also
Add a MobileView graphic Add a variety of MobileView graphic terminals to your Studio 5000 Architect
project. Adding a MobileView terminal creates a new FactoryTalk View Machine
terminal
Edition application.
5. Click OK.
Name: Enter a unique name for the application. Studio 5000 Architect
creates a new FactoryTalk View Machine Edition application.
(optional) Description: Enter a description of the application. Cannot
be longer than 128 characters.
(optional) Scale Replace Displays: Select to scale objects in Replace
displays to the resolution of the panel.
(optional) Scale OnTop Displays: Select to scale objects in OnTop
displays to the resolution of the panel.
(optional) Language: Select a language for the application.
See also
New PanelView Plus Graphic How do I open New PanelView Plus Graphic?
Use New PanelView Plus Graphic to set name, description, and IP address
settings for a new PanelView Plus graphic terminal. These settings are editable
after the project contains the PanelView Plus terminal.
See also
New PanelView Plus Project How do I open New PanelView Plus Project?
4. Configure the settings in New PanelView Plus Graphic, then click OK.
Use New PanelView Plus Project to set the name and description for a new
PanelView Plus project. The name and description are editable after the project is
part of the Studio 5000 Architect project.
See also
Use New MobileView Graphic to set name, description, and IP address settings
for a new MobileView graphic terminal. These settings are editable after the
MobileView terminal is in the project.
See also
Use New MobileView Project to set the name and description for a new
MobileView project. The name and description are editable after the project is
part of the Studio 5000 Architect project.
See also
PanelView Plus Properties The PanelView Plus Properties settings define name, description, and network
settings for PanelView Plus graphic terminals. Set these settings from New
settings
PanelView Plus Graphic when adding a PanelView Plus terminal or from the
Properties General tab when editing a PanelView Plus terminal.
Setting Description
Name Sets the name for the PanelView Plus terminal.
Description Sets the description for the PanelView Plus terminal. Cannot be longer than 255
characters.
IP Address Sets the unique address that identifies the PanelView Plus terminal on the IP
network.
Catalog Number Sets a catalog number for the PanelView Plus terminal.
See also
MobileView Properties settings The MobileView Properties settings define name, description, and network
settings for MobileView components. Set these settings in New MobileView
Graphic when adding a MobileView terminal or from the Properties General tab
when editing a MobileView terminal.
Setting Description
Name Sets the name for the MobileView.
Description Sets the description for the MobileView. Cannot be longer than 128 characters.
IP Address Sets the unique address that identifies the MobileView on the IP network.
Catalog Number Sets a catalog number for the MobileView.
See also
Add computers You can add or remove computers from your project. Computers represent the
hardware that serve FactoryTalk View SE and FactoryTalk View Machine Edition
applications to visualization devices. Computers appear in Hardware Diagram
and Project Explorer.
See also
Add a computer Add a computer to a Studio 5000 Architect project to represent a host machine
for FactoryTalk View SE and FactoryTalk View Machine Edition servers.
To add a computer:
See also
Use New Computer Graphic to set the name, description, and host name for a
new computer. Edit these settings after the computer has been added to the
project.
Field Description
Name Sets the name for the computer.
Description Sets the description for the computer. Cannot be longer than 128 characters.
Computer Name Sets the unique name that identifies the computer on the network.
See also
See also
Add a FactoryTalk View Site If your automation system integrates with FactoryTalk View Site Edition
visualization devices, add a FactoryTalk View Site Edition station to your Studio
Edition Station
5000 Architect project.
Name: Enter a unique name for the application. If you enter a unique
name, the Studio 5000 Architect software creates a new FactoryTalk
View Site Edition application.
(optional) Description: Enter a description of the application. Cannot
be longer than 255 characters.
(optional) Language: Select a language for the application.
4. In New View SE Station Project, configure settings for the HMI server:
(optional) Area: Enter a View SE area to assign the HMI server to the
area.
Name: Enter a unique name for the HMI server.
(optional) Description: Enter a description of the HMI server.
Cannot be longer than 255 characters.
6. Click OK. Project Explorer shows the View SE Station project in Projects.
See also
Add a FactoryTalk View Machine If your automation system integrates with View Machine Edition (ME)
Visualization devices, add a View ME Station to your Studio 5000 Architect
Edition Station
project.
See also
Add a FactoryTalk View Site If your automation system integrates with FactoryTalk View Site Edition
Visualization devices, add a View SE Server project to your Studio 5000 Architect
Edition Server Project
project.
(optional) Area: Enter a View SE area to assign the HMI server to the
area.
Name: Enter a unique name for the HMI server.
(optional) Description: Enter a description of the HMI server.
Cannot be longer than 255 characters.
6. Click OK. Project Explorer shows the View SE Server project in Projects.
See also
Add an RSLinx Enterprise Server If your automation system has a dedicated RSLinx Enterprise server, you need to
add a RSLinx Enterprise server project to your Studio 5000 Architect project.
Project
Before you begin:
Enable alarm and event support: Select if this server monitors alarm
and event tags.
Enable server-assigned priorities: Select and assign severity ranges if
this server has custom warning levels for alarms and events.
6. Click OK. Project Explorer shows the RSLinx Enterprise server project in
Projects.
See also
Add a Tag Alarm and Event If your automation system has a dedicated FactoryTalk Alarms and Events server,
you need to add a Tag Alarm and Event server project to your Studio 5000
Server project
Architect project.
3. In New Tag Alarm and Event Server Project, enter the Application
settings:
4. In New Tag Alarm and Event Server Project, enter the Tag Alarm and
Event Server settings:
(optional) Area: Enter a View SE area to assign the tag server to the
area. If you enter a unique area, the Studio 5000 Architect software
creates a new area.
Name: Enter a unique name for the server.
(optional) Description: Enter a description of the server. Cannot be
longer than 255 characters.
(optional) Create HMI Server: Select to create an associated HMI
server.
5. (optional) In the Priorities tab of New Tag Alarm and Event Server
Project, enter the Priority settings.
6. Click OK. Project Explorer shows the Tag Alarm and Event server project
in Projects.
See also
New Site Edition Project How do I open New Site Edition Project?
Use New Site Edition Project to set application and HMI server settings for a
new local or network distributed Site Edition project. You can edit these settings
after the Site Edition project is added to the Studio 5000 Architect project.
See also
New Machine Edition Station How do I open New Machine Edition Station Project?
Project 1. In Toolbox, expand the Visualization and Stations folders.
Use New Machine Edition Station Project to set name, description, resolution,
scaling options, and language for a new FactoryTalk View Machine Edition
project. You can edit these settings after the FactoryTalk View Machine Edition
project is added to the Studio 5000 Architect project.
See also
New Tag Alarm and Event How do I open New Tag Alarm and Event Server Project?
Server Project 1. In Toolbox, expand the Visualization and Servers folders.
2. Drag the Tag Alarm and Event Server from Toolbox to a computer in the
Hardware Diagram.
Use New Tag Alarm and Event Server Project to set server and alarm properties
for a new Tag Alarm and Event Server.
See also
New RSLinx Enterprise Data How do I open New RSLinx Enterprise Data Server Project?
Server Project 1. In Toolbox, expand the Visualization and Servers folders.
Use New RSLinx Enterprise Data Server Projectto set application, server, and
alarm and event settings for a new RSLinx Enterprise data server
See also
FactoryTalk View Site Edition The FactoryTalk View Site Edition Project settings define application and
HMI server settings for a Site Edition project. Set these settings from New Site
Project settings
Edition Project when adding a local or network server or from the Properties
General tab when editing a Site Edition project.
The FactoryTalk View Site Edition Project application and HMI server settings
are:
The FactoryTalk View Site Edition Project HMI server settings are:
See also
FactoryTalk View Machine The FactoryTalk View Machine Edition Project settings define name,
description, language, resolution, and scaling options for a FactoryTalk View
Edition Project settings
Machine Edition application. Set these settings from New ME Station Project
when adding a FactoryTalk View Machine Edition application or from the
Properties General tab when editing a FactoryTalk View Machine Edition
application.
Setting Description
Name Sets the name for the FactoryTalk View Machine Edition application. The project
name must not be empty.
Description Sets the description for the FactoryTalk View Machine Edition application. Cannot
be longer than 255 characters.
Language Sets the display language for the FactoryTalk View Machine Edition application.
Resolution Sets the target resolution for the FactoryTalk View Machine Edition application.
Scale Replace Displays Sets if objects in Replace displays should be scaled to the resolution of the panel.
Scale OnTop Displays Sets if objects in OnTop displays should be scaled to the resolution of the panel.
Ensure runtime application can execute on PanelView Plus 7 Standard Sets if a application should be compatible with both PanelView Plus 7
Performance and PanelView Plus 7 Standard graphic terminals.
See also
FactoryTalk Alarms and Event The FactoryTalk Alarms and Event Server General settings define server
settings for a FactoryTalk Alarms and Events server. Set these settings from the
Server General settings
General tab of New FactoryTalk Alarms and Event Server when adding a new
FactoryTalk Alarms and Events server or from the Properties General tab when
editing an FactoryTalk Alarms and Events server.
See also
FactoryTalk Alarms and Event The FactoryTalk Alarms and Event Server Priorities settings define settings for
a FactoryTalk Alarms and Events server. Set these settings from the Priorities tab
Server Priorities settings
of New FactoryTalk Alarms and Event Server Project when adding a new
FactoryTalk Alarms and Events server or from the Priorities tab when editing a
FactoryTalk Alarms and Events server.
Field Description
Enable server-assigned priorities If selected, allows you to set custom priority values for Urgent, High, and
Medium priority events.
Urgent Specifies the priority at which an Urgent priority alarm or event will be created.
High Specifies the priority at which a High priority alarm or event will be created.
Medium Specifies the priority at which a Medium priority alarm or event will be created.
See also
RSLinx Enterprise Data Server The RSLinx Enterprise Data Server General settings define options for an
RSLinx Enterprise data server. Configure these settings from the General tab of
General settings
New RSLinx Enterprise Server when adding an RSLinx Enterprise server or
from the Properties General tab when editing an RSLinx Enterprise server.
See also
RSLinx Enterprise Data Server The RSLinx Enterprise Data Server Alarms and Events settings define alarm
and event settings for an RSLinx Enterprise data server. Set these settings from the
Alarms and Events settings
Alarms and Events tab of New RSLinx Enterprise Data Server when adding a
new RSLinx Enterprise data server or from the Properties Alarms and Events tab
when editing an RSLinx Enterprise data server.
The RSLinx Enterprise Data Server Alarms and Events settings are:
Setting Description
Enable alarm and event support If selected, sets the RSLinx Enterprise Data Server to act as an Alarm and Event
server.
Enable server-assigned priorities If selected, enables custom priority values for Urgent, High, and Medium priority
events.
Urgent Sets the priority at which an Urgent priority alarm or event will be created.
High Sets the priority at which a High priority alarm or event will be created.
Medium Sets the priority at which a Medium priority alarm or event will be created.
See also
Import existing components from a project file or online controller to add them to
a Studio 5000 Architect project. Once added, connect components to networks
and configure relationships to share tags and control an automation system.
See also
Import a controller project Logix Designer project files (.acd) can be imported to to a Studio 5000 Architect
project. Studio 5000 Architect software adds the controller, chassis or DIN rail,
from a file and all associated modules, tags, and aliases to the project.
If the imported project contains produced or consumed tags using user defined
data types, the user defined data type must be defined in the producer controller
before you can commit the hardware diagram.
2. In Open, locate and select the project file to add, then click Open.
See also
Import a controller project You can import a controller project to your Studio 5000 Architect project from
an online controller using RSLinx Classic. Studio 5000 Architect software adds
from an online controller the controller, chassis or DIN rail, and all associated modules, tags, and aliases to
your project.
If the imported project contains produced or consumed tags using user defined
data types, the user defined data type must be defined in the producer controller
before you can commit the hardware diagram.
See also
Import a FactoryTalk View You can import a FactoryTalk View application to your Studio 5000 Architect
project. Studio 5000 Architect software adds the associated PanelView Plus or
application from a file MobileView terminal, tags, displays, global objects, images, macros, and servers to
the project.
3. Click OK.
See also
Import From the Hardware Diagrams menu, click Import from Online
Controller...
See also
Choose Matching Controller How do I open Choose Matching Controller Configuration File?
Choose Matching Controller Configuration lists existing project files that are
compatible with the controller you are importing. The selected controller project
and its documentation are added to the Studio 5000 Architect project.
See also
2. In Open, locate and select the project file you wish to add, then click Open.
2. In Select Online Controller to Import, browse the network and click the
controller you want to import into your project, then click Select.
See also
Add Existing FactoryTalk How do I open Add Existing FactoryTalk View Project?
View Project In Hardware Diagram, right-click on a blank area of the hardware diagram,
then click Add Existing FactoryTalk View Project.
See also
Add networks
Networks in Studio 5000 Architect represent the hardware and cables that allow
components to communicate. After components are connected to the same
network, you can create ownership relationships, tags, and I/O aliases.
See also
Add a managed Ethernet Add a managed Ethernet switch to build or expand an Ethernet network using
Stratix devices. Studio 5000 Architect software supports managed Stratix switches
switch ranging from 3 to 20 ports in their default configuration. Some switches support
expansions up to a total of 26 ports.
2. Expand Managed Switches, then expand the list by switch port size.
c. Address / Host Name: Set the IP address or host name for the switch.
5. Click OK. The Stratix switch appears in the Hardware Diagram and in
Project Explorer under Devices.
See also
Add an unmanaged Add an unmanaged Ethernet switch to build or expand an Ethernet network
using Stratix devices. Studio 5000 Architect software supports unmanaged Stratix
Ethernet switch switches ranging from 4 to 8 ports.
2. Expand Unmanaged Switches, then expand the list by switch port size.
4. In New Switch Graphic, enter a unique name for the switch, then click
OK. The switch appears in Hardware Diagram and in Project Explorer
under Devices.
See also
You can add a generic switch to your Studio 5000 Architect project. Use generic
Add a Generic switch
switches to connect mainstream Ethernet hardware to your automation system.
4. Click OK. The generic switch appears appears in Hardware Diagram and
in Project Explorer under Devices.
See also
Add a network trunk ControlNet and other network trunks represent the cabling that
connectnon-Ethernet components. Using multiple controllers or modules to
communicate across a ControlNet or other non-Ethernet network requires a
network trunk.
1. From the Network Trunk list, select a network trunk type, then select
Network Trunk Tool.
See also
Connect Ethernet For Ethernet components to communicate with each other, connect them to the
same Ethernet network. In most cases, components connect to an Ethernet
components switch. Components with multiple Ethernet ports support Device Level Ring
(DLR) connections and can connect components without a switch.
See also
Connect components to a In order for ControlNet and other non-Ethernet components to communicate
with each other, connect the components to the same network trunk.
network trunk Components can only connect to one network trunk at a time.
See also
Add an Ethernet Tap Add an Ethernet tap to monitor messages on an Ethernet network.
3. In New Switch Graphic, configure the switch properties, then click OK:
74 Rockwell Automation Publication ARCH-GR001G-EN-E
Add networks Chapter 7
4. Click OK. The Ethernet tap appears in Hardware Diagram and in Project
Explorer under Devices.
See also
New Generic Switch Graphic How do I open New Generic Switch Graphic?
Use New Generic Switch Graphic to set switch settings for a new Ethernet
switch. You can edit these settings after the switch has been added to the project.
Settings Description
Name Specifies the name of the generic switch.
Description Specifies the description of the generic switch. Cannot be longer than 255
characters.
Type Specifies the type of switch:
Unmanaged: Unmanaged switches provide a basic network connection. No
additional network configuration is required with this option.
Managed: Managed switches allow you to take control of communication
over an Ethernet network. You need to configure the address or host name if
choosing this option.
Number of Ports Specifies the number of ports to create connections between communication
modules. The value range is 2 to 26.
Address/Host Name Specifies the IP configuration for a managed switch. There are three options:
Private Network: Select the value from the list, from 1 to 254.
IP Address: Enter a unique IP address to identify each node on the IP
network.
Host Name: Enter a fully qualified domain name, such as
switch.yourcompany.com.
See also
Use Switch Configuration to set the name, description, and network settings for
a new Stratix switch or Ethernet tap. You can edit these settings after the switch or
tap has been added to the project.
Setting Description
Type Specifies the type of the switch.
Vendor Shows the vendor information of the switch.
Name Shows the switch name specified in New Switch Graphic.
Description Specifies the description for the switch. Cannot be longer than 128 characters.
Expansions Specifies the port expansion information. There are three available options, (0) -
None, (1) - 8 port expansion, and (2) - 8 port expansion(16 ports total).
Address / Host Name Specifies the configuration for the switch. The setting is available if the switch
type is Managed. There are three options:
Private Network: Select the value from the list, from 1 to 254.
The Private Network setting is not available for Stratix 6000 switches.
IP Address: Enter a unique IP address to identify each node on the IP
network.
Host Name: Enter a fully qualified domain name, such as
switch.yourcompany.com.
See also
For components to communicate with each other in production, they must have
one of three relationships:
Relationship Description
Ownership relationship Connects one module to one controller or RSLinx Enterprise server.
Producer/consumer relationship Connects one controller to another controller.
Shortcut Connects one controller to an RSLinx Enterprise server for use in a FactoryTalk View application.
Once two components have a relationship, they can communicate with each other
using one or more tags. Add tags for producer/consumer relationships, point tags,
and axis tags using Studio 5000 Architect or Logix Designer.
See also
About ownership An ownership relationship connects one module to one controller or RSLinx
Enterprise server. Once the relationship has been added, the controller or server
relationships "owns" the module and can read from or write to its tags. A controller or server
can own multiple modules. Modules can have multiple owners. In large
automation systems, ownership relationships can be very complex with many
modules owned by many controllers across multiple chassis.
Studio 5000 Architect software displays the owned modules for each controller in
Project Explorer under the controller project's I/O Configuration folder. Studio
5000 Architect displays owned modules for each RSLinx Enterprise server in
Communications.
Either the controller and the target module must be on the same chassis
Or the controller or RSLinx Enterprise server must own all communication
modules along the path to the target module's chassis
Example
A controller in Chassis A needs to read tags from an input module across the
factory floor in Chassis B. The two chassis are physically connected using an
Ethernet network. Adding an ownership relationship between the controller and
the input module is a four step process:
1. In Studio 5000 Architect software, connect the two chassis together using
communication modules and an Ethernet switch.
Project Explorer shows the path of owned modules in the controller project's
I/O Configuration folder.
See also
Studio 5000 Architect software displays the producer controllers for each
consumer controller in Project Explorer under the controller project's I/O
Configuration folder.
Example
1. In Studio 5000 Architect software, connect the two chassis together using
communication modules and an Ethernet switch.
Project Explorer shows the path of owned modules and producer controllers in
the consumer controller project's I/O Configuration folder.
See also
About shortcuts A shortcut connects one controller to an RSLinx Enterprise server for use in a
FactoryTalk View project. Once the relationship has been added, the RSLinx
Enterprise server can read from or write to the controller's tags. This allows a
FactoryTalk View application to communicate with a controller.
Studio 5000 Architect software displays the shortcuts for each RSLinx Enterprise
server in Communications.
To add a shortcut, the RSLinx Enterprise server must own all communication
modules along the path to the target module's chassis.
Example
Communications shows the path of each shortcut from the RSLinx Enterprise
server to the controller.
See also
Communications on page 94
Add an ownership An ownership relationship connects one module to one controller or RSLinx
Enterprise server. Once the relationship has been added, the controller or server
relationship owns the module and can read from or write to its tags.
Either place the controller and the target module on the same chassis, or
make the RSLinx Enterprise server the owner of all communication
modules along the path to the target module.
3. In Configure Module, set the keying, and network settings, then click OK.
Project Explorer displays the owned modules for each controller and
Communications displays owned modules for each RSLinx Enterprise server.
See also
Either place the consumer controller and producer controller on the same
chassis, or make the consumer controller the owner of all communication
modules along the path to the producer controller
Project Explorer shows the path of owned modules and producer controllers in
the I/O Configuration folder of the consumer controller project.
See also
The RSLinx Enterprise server must own all communication modules along
the path to the target controller.
To add a shortcut:
2. Drag the controller on top of the computer that hosts the RSLinx
Enterprise server.
3. In Add New or Modify Existing Shortcut, set the shortcut settings, then
click OK:
See also
Communications on page 94
Add a produced and Add produced and consumed tags to allow a consumer controller to read and
write values in a producer controller.
consumed tag
Before you begin:
2. In Consumer Tag, select a consumer controller and a name for the tag.
3. Click Connection.
6. Click OK.
8. Click OK.
9. Commit the hardware diagram to save the tags to the Logix Designer
projects.
See also
Add a point tag A point tag, also known as an I/O alias, allows you to reference the point tag
instead of the I/O point in your controller programs. This can be a useful
shorthand for controllers with many inputs and outputs.
If the Create alias tags automatically when Point Tag is defined setting in
Studio 5000 Architect options is enabled, adding a point tag automatically adds
controller scope alias tags in each owning controller's project. If the setting is
disabled, corresponding alias tags are not added.
2. In I/O Aliases, click in the Point Tag column for an I/O point.
4. Commit the hardware diagram to save the tags to the Logix Designer
projects.
See also
6. Click OK.
7. Commit the hardware diagram to save the tag to the Logix Designer project.
Studio 5000 Architect displays the new axis tag and motion group in
Project Explorer under the controller project's Motion Groups folder.
See also
Edit a produced and Edit a produced and consumed tag to change its name, description, data type,
access options, or RPI.
consumed tag
To edit a produced and consumed tag
1. In Produce/Consume Tags, locate and click on the tag you wish to edit.
2. Click Edit.
3. In Consumer Tag, edit the name, description, data type, or access options.
4. (optional) Click Connection to open Producer Tag to edit the RPI, then
click OK.
5. Click OK.
See also
Edit a shortcut Edit a shortcut to change its name or offline tag file.
To edit a shortcut
7. Click OK.
See also
Common module When adding an ownership relationship between an Add-On Profile (AOP)
module and a controller, Studio 5000 Architect software checks the validity of the
configuration errors relationship against Logix Designer relationship rules. If the relationship is invalid,
Studio 5000 Architect software displays an error message.
See also
Ethernet node limitations Any Ethernet/IP device that is owned by or added to the I/O configuration of a
controller is counted towards the node limits of the controller. ControlLogix and
CompactLogix controllers count all devices connected to local and remote
Ethernet ports.
The maximum number of connected Ethernet nodes varies by controller. Use the
Capacity tab in the Logix Designer software to determine limits for a controller.
The local Ethernet modules and embedded Ethernet ports are not included in the
count.
See also
2. Drag the module on top of the controller or RSLinx server that will own it.
1. In Hardware Diagram, locate the controller that will produce tags for the
consumer controller.
Use Configure Module to set keying and connection settings for a module or
producer controller. Use these settings to create an ownership relationship or a
producer/consumer relationship. Edit these settings using the Edit Device
Properties Module Configuration tab.
Setting Description
Type Specifies the type of the module.
Vendor Shows the vendor information of the module.
Parent Shows the name of the parent module. If the module is in the local chassis, displays Local.
Name Shows the name of the module.
Description Specifies the description for the module.
Comm Format Specifies the format of the module (input or output).
Slot Shows the slot in the chassis where the module exists.
Specifies the electronic keying protection mode to prevent a module from being inserted in the wrong slot.
Exact Match. Requires all attributes of the physical module and the module created in the software to match.
Compatible Module Keying. Accepts or rejects the connection based on firmware compatibility.
Electronic Keying
Disable Keying. Requires no attributes of the physical module and the module configured in the software to match.
Modifying the Electronic Keying option may cause the module connection to break or result in a loss of data, or both. If used
incorrectly, this option can lead to personal injury or death, property damage or economic loss.
Revision Specifies the major (primary) and minor (secondary) firmware version of the module.
Specifies the node on the module trunk where the module exists.
Node
This option is only available for ControlNet modules that you are associating with a controller.
Specifies the configuration for the switch. These settings are available for managed Ethernet switches. There are three options:
Private Network: Select the value from the list, from 1 to 254.
Address / Host Name
IP Address: Enter a unique IP address to identify each node on the IP network.
Host Name: Enter a fully qualified domain name, such as switch.yourcompany.com.
See also
Use Produce/Consume Tags to add, edit, and remove produced and consumed
tags from controller projects.
Column Description
Consumer Controller The name of the consumer controller.
Consumer Tag The name of the consumed tag in the consumer controller project.
Data Type The data type of the tag, such as BOOL or DINT.
Producer Controller The name of the producer controller.
Producer Tag The name of the produced tag in the producer controller project.
RPI The requested packet interval (RPI) of the tag. The producing controller updates
the tag once per interval. The default interval is 20ms.
Class The class of the tag, either Standard or Safety. Only available for safety
controllers, such as a 1756-L61S.
See also
Setting Description
Controller The controller that consumes the tag.
Setting Description
Tag Name The tag name used in both the producer and consumer controller.
Description The description of the tag. Cannot be longer than 120 characters.
Data Type The data type of the tag, such as BOOL or DINT.
For safety class producer/consumer tags, the user defined data type must be
defined in Logix Designer and the data type of the first element must be
CONNECTION STATUS.
Class The class of the tag, either Safety or Standard. Only available for safety
controllers, such as a 1756-L61S.
External Access The level of access that external applications and devices have to the tag.
Read/Write: External applications and devices can both read and change the
tag's value.
Read Only: External applications and devices can only read the value of the
tag.
None: External applications and devices cannot read or change the tag's
value.
Array Dimensions Sets the number of dimensions for the tag. The default is 0
Use Unicast Connection over EtherNet/IP Sets whether or not the tag is consumed using a unicast connection. This setting
is only available if the connection between the producer and the consumer is
over EtherNet/IP.
See also
Setting Description
Controller The controller that produces the tag.
Tag Name The tag name used in both the producer and consumer controller.
Description The description of the tag. Cannot be longer than 120 characters.
Class The class of the tag, either Safety or Standard. Only available for safety
controllers, such as a 1756-L61S.
Setting Description
External Access The level of access that external applications and devices have to the tag.
Read/Write: External applications and devices can both read and change the
tag's value.
Read Only: External applications and devices can only read the value of the
tag.
None: External applications and devices cannot read or change the tag's
value.
RPI The requested packet interval (RPI) of the tag. The producing controller
updates the tag once per interval. The default interval is 20ms.
Allow Unicast Consumer Connections Sets whether or not the tag is provided using a unicast connection to the
consumer controller. This setting is only available if the connection between the
producer and the consumer is over EtherNet/IP.
See also
Use I/O Aliases to add, edit, and remove point tags. I/O Aliases shows each I/O
module owned by a selected controller and lists the I/O points, direction, and
created point tags of the module. You cannot create or edit tags for an I/O module
unless the module is owned by at least one controller.
Column Description
Name The name of the module.
Catalog Number The catalog number of the module.
Description The description of the module.
Point The number of the physical input or output point on the module.
Column Description
Type/Direction The type of input or output, as defined by the module.
Point Tag The point tag as defined for the module.
InputController Shows the alias tag as defined in each owner controller's project. If multiple
controllers own the module, multiple columns are shown.
See also
Use Communications to view and edit shortcut paths for FactoryTalk View
applications that have RSLinx Enterprise servers.
See also
2. Drag the controller on top of the computer that hosts the RSLinx server.
Use Add New or Modify Existing Shortcut to set a name and offline tag file for a
new or existing shortcut. Change these settings after the shortcut is created using
the Properties Shortcuts tab when editing an RSLinx Enterprise server.
See also
Add graphics, files, text boxes, shapes, and links to display additional information
or reference material about the project. Graphics, files, text boxes, shapes and links
appear in Hardware Diagram.
See also
Add a graphic You can add a graphic in Hardware Diagram to display information related to
your network design. Studio 5000 Architect software comes with a set of sample
device images, located at C:\Users\Public\Documents\Studio
5000\Samples\Architect\Graphics.
To add a graphic:
2. In Add Graphic, type the path to the file or click Browse to select an image
file, then click OK.
See also
Add a file You can add any file to Hardware Diagram to accompany your project. You can
add any file type but the most common uses are configuration and documentation
files. Added files are copied into the project folder. Files appear in Hardware
Diagram as images.
To add a file:
Image file name: Enter the path to the file or click Browse to select an
image file.
File name: Enter the path to the file or click browse to select the file.
3. Click OK. Studio 5000 Architect software adds the file to the project and
shows it in Hardware Diagram as the selected image.
See also
Add a text box You can add text boxes in Hardware Diagram to label components.
To add text:
2. Click in Hardware Diagram to set the position or click and drag to set
both the position and size.
See also
Add a shape You can add shapes in Hardware Diagram to label and group components.
To add shapes:
Line Tool
Rectangle Tool
Circle Tool
See also
Add a link You can add a web link in Hardware Diagram to refer to a web page or document
containing more information about your network design. Web links are
represented in Hardware Diagram using text and an optional image.
To add a link:
3. Click OK. Studio 5000 Architect software displays the link in Hardware
Diagram.
See also
If you are adding a text box, click the Text Tool, then click in
Hardware Diagram to set the position or drag across the hardware diagram
to set both the position and size.
If you are editing a text box, right-click the text box and select Properties.
Use Text Box Properties to add or edit a text box in a Studio 5000 Architect
project. You can change the text, font, size, color, effects, and borders of a text box.
See also
Supported graphic formats Studio 5000 Architect software supports these graphic formats:
Bitmap (BMP)
Device-independent bitmap (DIB)
Graphics interchange format (GIF)
Joint Photographic Experts Group (JPEG)
Portable Network Graphics (PNG)
Icon (ICO)
See also
Use Element Properties to set border and fill options for a rectangle, circle, or
line.
See also
Updating a hardware diagram pulls all changes made in associated Logix Designer
or FactoryTalk View project files into Studio 5000 Architect software
components. Updating with an online controller applies changes in the controller
project to Studio 5000 Architect software components. Any differences in the
Studio 5000 Architect components, including Add-On Instructions (AOIs) and
User Defined Types (UDTs), are overwritten.
See also
Commit a hardware Committing a hardware diagram pushes all changes made to software components
in Studio 5000 Architect software into the associated Logix Designer and
diagram FactoryTalk View application files. Any differences in the project files are
overwritten. Studio 5000 Architect software creates new project files if they do
not exist. You must commit each hardware diagram separately.
Important: If a FactoryTalk View application has a shortcut that is not in the Studio
5000 Architect project, the commit does not remove the shortcut from the
FactoryTalk View application.
3. In Commit Summary, review the changes that will be made to the Logix
Designer or FactoryTalk View applications, then click OK.
See also
Update a hardware Updating a hardware diagram applies all changes made in associated Logix
Designer or FactoryTalk View application files to Studio 5000 Architect software
diagram components. Any differences in the Studio 5000 Architect components are
overwritten. You must update each hardware diagram separately.
See also
Update a hardware Updating with an online controller applies changes from the controller project
into Studio 5000 Architect software components. Any differences in the Studio
diagram with an online 5000 Architect components are overwritten. You must update each hardware
controller diagram separately.
If the controller project contains a module that is not supported, Studio 5000
Architect software adds an unsupported module image in the appropriate chassis,
DIN rail, or slot. If a module is unnamed, Studio 5000 Architect software
automatically generates a module name based on the module's catalog number.
2. From the Sync menu, click Update Changes from Online Controller.
3. In Select Online Controller to Update, browse the network and click the
controller to import into your hardware diagram.
4. (optional) To update the online controller to a project other than the one
associated with the existing controller component, select Use external
controller configuration file.
5. Click Select.
See also
Commit a single project to apply all changes made in the Studio 5000 Architect
Commit a single project
project to the associated Logix Designer project or FactoryTalk View application
file. Any differences in the project file are overwritten. Studio 5000 Architect
creates a new project file if one does not exist.
Important: If a FactoryTalk View application has a shortcut that is not in the Studio
5000 Architect project, the commit does not remove the shortcut from the
FactoryTalk View application.
See also
Update a single project Update a project to apply all changes made in its associated Logix Designer project
or FactoryTalk View application file to the Studio 5000 Architect project. Any
differences in the Studio 5000 Architect project are overwritten.
See also
Use Output to view error, warning, and informational messages about a Studio
5000 Architect project. By default, messages are sorted by time, with the newest
message at the bottom of the list. Messages are cleared when the project is closed.
Column Description
Severity The type of message, including:
Error: An operation was canceled or could not continue. Resolve the error condition and repeat the operation to continue.
Warning: An operation completed, but may have significantly changed one or more components in the project. Review these components to ensure
they function as expected.
Info: An operation completed successfully.
Time The time the message occurred. Hidden by default.
Hardware Diagram The hardware diagram associated with the message. Hidden by default.
Project The Logix Designer project or FactoryTalk View application associated with the message.
Type The model number of the hardware component associated with the message.
Message The message description, explaining the operation status and severity.
See also
See also
See also
Choose Matching Controller How do I open Choose Matching Controller Configuration File?
Choose Matching Controller Configuration lists existing project files that are
compatible with the controller you are importing. The selected controller project
and its documentation are added to the Studio 5000 Architect project.
See also
Errors during commit and Duplication, permission, communication, and license errors may occur when
committing or updating a Studio 5000 Architect project. These errors either
update cancel the action or continue with limited functionality. They are not displayed in
Commit Summary or Update Summary.
HMI <name> is unable to be created for it already exists. Remove the duplicated HMI server from the target project.
User does not have permissions <permission> for <scope>. Verify the permissions of the user are set correctly in FactoryTalk Security.
User does not have permission to read or list children for <scope>. Verify the permissions of the user are set correctly in FactoryTalk Security.
See also
FactoryTalk View commit Studio 5000 Architect software validates each component of FactoryTalk View
applications before committing to ensure compatibility with FactoryTalk View.
validation rules
Scenario FactoryTalk View Compatibility Result
Display or global object has a higher version than the FactoryTalk Incompatible Commit cancels. Error appears in Commit Summary.
View application.
Display or global object has a lower version than the FactoryTalk Compatible Commit succeeds. FactoryTalk View upgrades the display or
View application. global object when opened in FactoryTalk View Studio
software.
FactoryTalk View Machine Edition display or global object added to Compatible Commit succeeds. FactoryTalk View converts the display or
FactoryTalk View SE application. global object when opened in FactoryTalk View Studio
software.
See also
Shortcut commit validation Studio 5000 Architect software validates shortcuts before committing to ensure
compatibility with the RSLinx Enterprise server.
rules
Scenario RSLinx Enterprise Compatibility Result
Shortcut in Studio 5000 Architect software points to communication Compatible Commit succeeds.
module and controller that match RSLinx Enterprise server device
tree.
Shortcut in Studio 5000 Architect software points to IP address not Compatible Commit succeeds. Communication module and controller
used by any device in RSLinx Enterprise server device tree. added to RSLinx Enterprise server device tree.
Shortcut in Studio 5000 Architect software points to a controller Incompatible Commit succeeds. The path is removed from the shortcut.
with a different catalog number than the controller in the RSLinx Studio 5000 Architect software displays a warning in Commit
Enterprise server device tree. Summary.
See also
Library components are add-on instruction (AOI), user defined tag (UDT),
FactoryTalk View components, or hardware definitions exported from Logix
Designer as .l5x XML files. Libraries have a .lal file extension and are an archive of
the individual .l5x files, each containing the definitions of each component and
any referenced AOIs and UDTs. The .lal file name matches the name defined for
the library.
See also
Create a new library Libraries contain the components used in designing an automation system. Create
custom libraries for organizing groups of components. Libraries are not specific to
Studio 5000 Architect projects.
1. From the Studio 5000 Architect menu, select Library Management > New
Library.
6. Click OK to create new Studio 5000 Architect Library (.lal) file in the
libraries directory (by default C:\Users\Public\Documents\Studio
5000\Libraries\Architect).
See also
Toolbox on page 11
Rename a library Libraries contain the components used to design an automation system.
Components refer to other components by component name and type only, not
library location. Renaming a library does not require any changes to the
components in that library.
To rename a library
See also
Toolbox on page 11
Import a library Libraries contain the components used to design an automation system. Libraries
are not specific to Studio 5000 Architect projects and can be imported from Logix
Designer, FactoryTalk View, PlantPAx, and other Rockwell Automation
products.
To import a library
1. From the Studio 5000 Architect menu select Library Management >
Import Library.
2. In Import Library, navigate to and select one or more library files, then
click Open.
See also
Toolbox on page 11
To delete a library
See also
Toolbox on page 11
Export a library Libraries contain the components used to design an automation system. Libraries
are not specific to Studio 5000 Architect software and can be exported from
Studio 5000 Architect for use in Logix Designer software, FactoryTalk View
software, and other Rockwell Automation software products.
To export a library
1. From the Studio 5000 Architect menu select Library Management >
Export Library.
2. In Export Library, navigate to and select the location to export the library
file.
If a library file of the same name already exists in the directory, Studio 5000
Architect software prompts to replace it.
See also
1. From the Studio 5000 Architect menu select Library Management > New
Library.
4. (optional) In Revision, use the arrows to establish major and minor revision
for the library to support manual tracking of libraries over time.
6. Click OK to create the new Studio 5000 Architect Library filein the
libraries directory (by default C:\Users\Public\Documents\Studio
5000\Libraries\Architect).
9. Click OK. Studio 5000 Architect displays the component (or components)
in the target library or folder. Repeat the copy and paste process until you
have copied over the entire subset of components.
10. From the Studio 5000 Architect menu select Library Management >
Export Library.
11. In Export Library, navigate to and select the location to export the library
file.
12. In File Name, type the name for the library file.
If a library file of the same name already exists in that alternate directory,
Studio 5000 Architect prompts to replace it.
See also
Toolbox on page 11
Create a new folder Folders are used to organize the components in a custom library. Folder names
must not include \ / ? : * " > < or |.
Once created, folders can be copied, pasted, and moved. Components can be
imported directly into a folder.
See also
Toolbox on page 11
Rename a folder Folders are used to organize the components in a custom library.
To rename a folder
See also
Toolbox on page 11
Delete a folder Folders are used to organize the components in a custom library. If a folder is no
longer useful, it can be deleted.
To delete a folder that contains components, delete each of the components from
the folder first. After all components are deleted from the folder, proceed with
deleting the folder from the library.
To delete a folder
See also
Toolbox on page 11
Add a component to a A library component is a Logix Designer add-on instruction (AOI) or user
defined tag (UDT), or a FactoryTalk View Studio display, graphic object, or
library image. When a component is added to the library, the export file is added to the
archive file in the libraries directory.
Components with the same name but different types (for example, AOI or UDT)
can exist in the same library or folder in the library. Components with the same
name and type (for example, AOI) cannot exist in the same library.
3. From the main menu, select Library Management > Add Component to
Library.
See also
Import a component to a Import previously exported components from Logix Designer into a selected
library or folder. Multiple components can be imported in a single operation.
library
To import a component from a file
2. In Import Component, select one or more .l5x files to import, then click
Open.
See also
Toolbox on page 11
Copy library components Add-on instruction (AOI) and user defined tag (UDT) objects in Studio 5000
Architect libraries are items that can be copied into Logix Designer projects. Any
from Studio 5000 Architect references within the AOI and UDT objects are automatically copied into the
software to Logix Designer Logix Designer project.
See also
Toolbox on page 11
Displays, global objects, and images in Studio 5000 Architect libraries can be
Copy library components
copied into FactoryTalk View SE or FactoryTalk View Machine Edition
from Studio 5000 Architect applications.
software to FactoryTalk
To copy library components from Studio 5000 Architect software to
View Studio software FactoryTalk View Studio software
See also
Toolbox on page 11
Rename a component A library component consists of a single Logix Designer export file. This export
file may contain multiple AOIs or UDTs - if the export includes all referenced
components. When a component is added to the library, the export file is added to
the archive file in the libraries directory.
Components with the same name but different types (for example, AOI or UDT)
can exist in the same library or folder in the library. Components with the same
name and type (for example, AOI) cannot exist in the same library.
To rename a component
See also
Toolbox on page 11
Delete a component Components added to custom libraries can be deleted if no longer useful. Deleting
a component may break the reference relationship with another component in a
different folder of the same library.
To delete a component
Important: If a library component has been placed in a Logix Designer project and the Studio 5000
Architect project has been committed, even though the component has been deleted from
the library the component cannot be deleted from the controller project.
See also
Toolbox on page 11
View component properties Components added to custom libraries have associated properties that provide
additional information about the component. Properties are read-only.
See also
Toolbox on page 11
Replace an AOI in the One or more instances of an add on instruction (AOI) in a project can be replaced
with an AOI from a library.
current project
To replace an AOI in the current project:
4. Confirm all of the AOIs that are selected for replacement. Make any
changes, if necessary.
5. Click Replace. All of the selected instances are replaced; a message is shown
in Results for each instance that is replaced. The AOI changes will not be
shown in the controller project until you commit the hardware diagram.
See also
Show references to AOIs References identify the other instructions that depend on the selected add-on
instruction (AOI) or user-defined tag (UDT).
and UDTs
To show references to AOIs or UDTs
See also
Use Toolbox to view default hardware components or add, remove, and manage
custom libraries. Drag components from the Toolbox to a Hardware Diagram to
add components to a project.
Product Catalog A list of Logix Designer and FactoryTalk View Studio components that can be added to a hardware diagram.
Libraries A list of libraries containing components that can be added to a hardware diagram or a Logix Designer or FactoryTalk
View Studio project.
See also
From the Studio 5000 Architect menu, click Library Management, then
click New Library.
Use Create New Library to set the name, description, and revision information
for a custom library. These settings are edited from Library Properties.
See also
Use the search tool to quickly find tags, data types, tasks, programs, instructions,
and folders within custom libraries and Logix Designer projects. Print hardware
diagrams to a printer to save or reference.
See also
View relationships Use Show Owner Mode to view ownership, producer/consumer, and shortcut
relationships in a hardware diagram.
To view relationships:
See also
Print a hardware diagram Print a hardware diagram to review or archive it outside of Studio 5000 Architect
software. Large hardware diagrams are automatically split across multiple pages.
By default, print margins are set at approximately 0.25 inches per side.
1. In Project Explorer, expand the Project or Devices folder, then click the
hardware diagram.
See also
Search a project Search a Studio 5000 Architect project to find instances of tags, data types, tasks,
programs, instructions, and folders within custom libraries and Logix Designer
projects.
To search a project
2. In Find, enter search terms, select locations to search, then click Start
Search. The results are displayed in Find Results.
See also
Print search results Print search results to review or archive found tags, data types, tasks, programs,
instructions, and folders outside of Studio 5000 Architect software.
3. (optional) To set print options such as page size and orientation, in Print
Preview, click File > Page Setup.
4. In Print Preview, click File > Print. The results are printed using your
system default printer.
See also
Filter the Toolbox Use Filter to limit which products or library components appear in the Toolbox.
See also
Toolbox on page 11
Use Find to search for terms in custom libraries and Logix Designer projects
included in a Studio 5000 Architect project. Find does not search FactoryTalk
View applications.
Setting Description
Find The search term.
Match case Determines if the search term is case sensitive.
Whole word Determines if the search must find an exact match, including spaces.
Controller Projects Determines the controller projects to search.
Libraries Determines the custom libraries to search.
Look for Determines object types to search.
Close on Search Complete Determines if the Find closes once the search has completed.
See also
Use Find Results to view the results of a search. Double-click an item in Find
Results to open the item in Logix Designer. By default, items are sorted
alphabetically by name. Results are cleared when the project closes.
Item Description
Name The name of the search result, such as AB:1756_AO6_Struct:C:0.
Kind The kind of the search result, such as DataTypes.
Type The data type of the search result, such as DINT or IO.
Container The component in the project or library that contains the search result, such as Controller.
Location The name of the project or library that contains the search result, such as Hardware Diagram 01:L75.
Description The description of the search result, if available.
See also
Use Print Preview to review and print search results and hardware diagrams.
Icon Description
Print. Print the project search results or hardware diagram.
Hand Tool. Click and scroll through the contents of the search results or hardware diagram.
Snapshot Tool. Click or drag the search results or hardware diagram to copy the page or selection to the clipboard.
Dynamic Zoom Tool. Drag up to increase the zoom level and drag down to decrease the zoom level.
Zoom Out Tool. Drag a rectangle to decrease the zoom level or click to incrementally decrease zoom level.
Zoom In Tool. Drag a rectangle to increase the zoom level or click to incrementally increase zoom level.
Page Width. Display the search results or hardware diagram, including page margins, in the display area.
Margin Width. Display only the search results or hardware diagram that appears within the margins in the display area.
Whole Page. Display the search results or hardware diagram page in the display area.
Zoom Out. Decrease the zoom level.
Zoom. Change the zoom level.
Zoom In. Increase the zoom level.
Continuous. Successively scroll between multiple pages, displaying a continuous flow of project search results or hardware diagrams
without any page breaks.
Layout. Configure the display area to show multiple pages simultaneously.
Close. Close Print Preview.
First Page. Display the first page in Print Preview.
Previous Page. Display the previous page in Print Preview.
Current Page. Display the desired page in Print Preview.
Next Page. Go to the next page in Print Preview.
Icon Description
Last Page. Go to the last page in Print Preview.
Previous View. Display the last selected view in Print Preview.
Next View. Display the next selected view in Print Preview.
See also
There are a variety of options that can be set to customize how Studio 5000
Architect software operates. In most cases, changes to the project settings take
effect immediately. However, if the changed behavior does not occur, close and
restart Studio 5000 Architect software.
See also
Option Description
Workspace Directory Specifies the directory used for project backups and projects imported from
online controllers.
Create project subdirectory under the main project directory By default, a subdirectory named for the project under the default project
directory is created. Clearing this checkbox will store all of your project files in the
default project directory.
Launch new instance of Studio 5000 Architect if a project is already open Specifies how Studio 5000 Architect software opens projects.
When selected, Studio 5000 Architect software automatically starts a new
Studio 5000 Architect instance when a project is open and you choose to open
or create a new project.
When cleared, Studio 5000 Architect software closes the currently open
project and prompts you to save changes before opening or creating a new
project
Option Description
Create alias tags automatically when Point Tag is defined Specifies whether alias tags are created automatically when the point tag is
defined.
When selected, Studio 5000 Architect software automatically unifies alias tag
names across Studio 5000 Architect, Logix Designer, and third party software
packages (for example, EPLAN Electric P8 software).
When cleared, Studio 5000 Architect software permits unique alias tag names
across Studio 5000 Architect, Logix Designer, and third party software
packages.
Update alias tags automatically when Point Tag is updated Specifies whether existing alias tags are replaced upon import.
When selected, Studio 5000 Architect software automatically updates alias
tags when importing an XML file from a third party software package (for
example, EPLAN Electric P8 software).
When cleared, Studio 5000 Architect software maintains existing alias tags
when importing an XML file from a third party software package.
Arrange projects in the Project Explorer by the hardware diagram they support Specifies whether Project Explorer sorts projects and applications:
When Arrange Projects by Hardware Diagram is enabled, Project Explorer
lists Logix Designer projects and FactoryTalk View applications by the
hardware diagram that contains the project or application hardware.
When Arrange Projects by Hardware Diagram is disabled, Project Explorer
lists all Logix Designer projects and FactoryTalk View applications in a single
list.
Restore Defaults Restore to the default settings.
See also
From the Tools menu, select Options, then select Hardware Diagram.
Use Hardware Diagram to set the size, orientation, and language options for
hardware diagrams.
Option Description
Size Specifies the desired page size for hardware diagrams.
To ensure that hardware diagrams print correctly, set the hardware diagram size
to match the page size for the printer.
Orientation Specifies how hardware diagrams display and print, either Portrait for a vertical
alignment or Landscape for a horizontal alignment.
Using Logix Designer Specifies language the Logix Designer application should use when started from
within Studio 5000 Architect software. This setting has no impact on the
language display of Studio 5000 Architect software.
See also
From the Tools menu, select Options, then select User Prompts.
Use User Prompts to set the options for when prompts should occur. Items
selected on this tab will result in a prompt. Clearing the check box will stop the
prompt from occurring and Studio 5000 Architect software will perform the
default action.
Option Description
Prompt for configuration changes When attempting to close a project, prompt to save and commit in order to
implement the configuration changes.
Prompt for ACD filename change When the .acd file name for a controller is changed, prompt to commit the
hardware diagram.
Prompt for module names When a module is created, prompt with a default module name and the
opportunity to rename the module.
Prompt for overwrite configuration Before importing or updating with an online controller, prompt that the process
will overwrite your current controller configuration.
Prompt for commit pending changes Before updating with an online controller, prompt to commit any pending
changes to a hardware diagram.
Prompt for change to recommended Flex terminal base When an alternate Flex wiring base is specified, prompt to change back to the
recommended Flex wiring base.
Show docking indicators when dragging views When a view is rearranged in the hardware diagram, display indicators (top,
bottom, left, right, or as a tab of another view group) to show where it can be
docked.
Auto scroll upon selection When a device is selected either in Project Explorer or Hardware Diagram,
automatically locate the device in the Project Explorer or Hardware
Diagram.
Prompt for confirmation before updating from a project Be prompted to confirm changes and update the Studio 5000 Architect project
prior to updating changes from a controller project.
Prompt for confirmation before committing changes to a project Be prompted to confirm changes and update the Studio 5000 Architect project
prior to a commit operation.
Prompt for update when opening a project file Be prompted to update changes to the associated .acd file made in the Logix
Designer application since the last time the Studio 5000 Architect project was
opened.
Prompt for confirmation when deleting a controller (and associated controller project file) Be prompted to delete the controller from the hardware diagram, as well as the
controller project file (*.acd) associated with that controller.
Show duplicate library name dialog box Be prompted when specifying a library name that already exists.
Prompt for deletion of referenced component in the Toolbox pane Be prompted to delete components exclusively referenced by a component
currently selected for deletion in Toolbox.
Show duplicate component name dialog box Be prompted when specifying a library component name that already exists.
Option Description
Set replace (no backup) as the default when duplicate component names are found Be prompted to replace a component (without backing up the original with a
'_bk' extension) when duplicate component names are found (default).
Prompt for Ethernet configuration after updating from a project Be prompted to change Ethernet switches and connection settings after
updating a project
See also
Use Libraries to set the default location for libraries. If you change the directory
location, you must also manually move any existing libraries to this new directory
location.
Option Description
Default Library Directory The default location is C:\Users\Public\Documents\Studio
5000\Libraries\Architect. Library paths can include mapped network drives
and UNC paths. All libraries are stored in the same directory.
Libraries are not moved or copied when the directory is changed. To use existing
libraries after the directory has been changed, copy the .lal files to the new
directory location.
Browse button Use to browse a directory structure to provide the path to the library directory.
See also
If single sign-on is disabled, users must log on and log off of the FactoryTalk
Directory Network and Local Directory before using Studio 5000 Architect.
FactoryTalk Security policies set permissions that determine if a user or group can
perform an action in Studio 5000 Architect or other FactoryTalk products. If the
user or group does not have the required permissions, Studio 5000 Architect
actions will either display an error message or have limited functionality.
See also
About Studio 5000 Architect FactoryTalk Security policy setting "Use single sign-on" (SSO) is enabled by
default. When enabled, SSO allows you to log on just once per directory, on a
software and FactoryTalk given computer. After you are logged on, all participating FactoryTalk products
Security Single Sign-On that run in that directory on that computer automatically use the security
credentials of the logged-on user. This allows you to work with multiple Rockwell
Automation products simultaneously, without having to log on to each software
product separately.
When SSO is enabled, you are not required to perform any additional operations
unless an alternate FactoryTalk user wants to use Studio 5000 Architect software.
Use Log On to Factory Talk to log on that user account.
Keep the following in mind concerning how SSO policy settings are used with
Studio 5000 Architect software:
See also
Log on to FactoryTalk When single sign on is disabled, logging on to FactoryTalk Security from the Start
menu does not automatically log into Studio 5000 Architect software. Instead,
when you start Studio 5000 Architect software you will be prompted to log on to
FactoryTalk before you can edit a project.
To log on to FactoryTalk
In Log On to FactoryTalk, type the User name and password, and then
click OK.
The Change Password prompt displays if the password to the account has
expired or if the administrator requires a password change at log on.
See also
Change the logged on user If a different user account needs to open or edit a Studio 5000 Architect project,
use Log On to Factory Talk to change to that user account. The logon can be
account changed for the network directory, the local directory, or both.
1. From the Studio 5000 Architect menu click Tools > Security > Log On to
FactoryTalk
3. Type the User name and Password, and then click OK.
The Change Password prompt displays if the password to the account has
expired or if the administrator requires a password change at log on.
See also
To change a password
1. From the Studio 5000 Architect menu click Tools > Security > Log On to
FactoryTalk
4. In Change Password, in User name, type your domain and alias, for
example DOMAIN-NA\alias1
6. In New Password, type the new password that you want to use. This
password must meet any password complexity requirements enforced in
your organization.
7. In Confirm New Password, type the new password again to confirm it and
then click OK to apply the change.
See also
Log off Studio 5000 When logging off, choose whether to log off the local user account or the network
user account.
Architect software
If the FactoryTalk Security policy setting "Use single sign-on (SSO)" is enabled,
your local user and network user accounts are automatically logged on after you
attempt to log off Studio 5000 Architect software. In this environment,
permitting a different user to work with Studio 5000 Architect software is
accomplished by changing the logged on user account.
If SSO is not enabled, logging on and logging off are done through the Studio
5000 Architect Tools menu.
From the Studio 5000 Architect menu point to Tools > Security > Log
Off and then click the account to log off.
If SSO is enabled, a message will be shown informing you of the automatic
logon behavior and asking you to confirm the log off.
If SSO is disabled, you will be prompted to log on to FactoryTalk.
See also
Use FactoryTalk Directory permissions to set the actions a user can perform in a
Set FactoryTalk Directory
Studio 5000 Architect, FactoryTalk View, or Logix Designer project. Unless
permissions overridden by individual product policies, these permissions apply to all
FactoryTalk products.
5. Locate the action, set whether the user is allowed to perform the action,
then click OK.
See also
Set Studio 5000 Architect Use Studio 5000 Architect permissions to set the actions a user can perform in a
Studio 5000 Architect project.
permissions
To set Studio 5000 Architect permissions
3. In the Explorer tree, expand the System > Policies > Product Policy >
Studio 5000 Architect folders, then double-click the Feature Security
policy.
5. In Configure Securable Action, add or remove users and groups, then set
whether they are allowed to perform the action, then click OK.
6. Click OK.
See also
Set Logix Designer Use Logix Designer permissions to limit the actions a user or group can perform
in a Logix Designer project. These settings also affect what actions Studio 5000
permissions Architect software can perform on Logix Designer projects, such as adding, saving,
committing, and updating Logix Designer projects.
3. In the Explorer tree, expand the System > Policies > Product Policies >
RSLogix 5000 folders, then double-click the Feature Security policy.
6. Click OK.
See also
Set FactoryTalk View SE Use FactoryTalk View SE application or area permissions to limit the actions a
user or group can perform in a FactoryTalk View SE application. These settings
permissions also affect what actions Studio 5000 Architect software can perform on
FactoryTalk View SE applications, such as adding, saving, committing, and
updating the application.
5. Locate the action, set whether the user is allowed to perform the action,
then click OK.
See also
Set FactoryTalk View Use FactoryTalk View Machine Edition permissions to limit the actions a user or
group can perform in a FactoryTalk View Machine Edition application. These
Machine Edition permissions are applied on a per-application basis and affect what actions Studio
permissions 5000 Architect software can perform on FactoryTalk View Machine Edition
applications, including adding, saving, committing, and updating the application.
4. Locate the action, set whether the user is allowed to perform the action,
then click OK.
See also
Studio 5000 Architect Studio 5000 Architect Feature Security policies control user permissions, which
determine whether a user or group can perform a specific action in Studio 5000
Feature Security policies Architect software.
See also
Required Studio 5000 Permissions set in FactoryTalk Security policies determine if a user or group can
perform actions in Studio 5000 Architect projects. If the user or group does not
Architect permissions have the required permissions, Studio 5000 Architect actions will either display an
error message or have limited functionality.
See also
Action Required RSLogix 5000 Feature Security policies Required FactoryTalk Directory > RSLogix
5000 permissions
Commit a Logix Designer project Controller: Secure Controller: Modify Properties
Project: New (first commit only) Controller: Unsecure
Module: Modify Properties
Project: Open
Project: Save
Tag: Modify Properties
Update a Logix Designer project Controller: Secure Project: Open
Update a Logix Designer project with an online controller Controller Secure: Project: Go Online
Project: New (first update only) Project: Open
Project: Save
Project: Upload
Browse tags in the controller Controller: Secure Project: Open
Create aliases for I/O tags Controller: Secure Tag: Modify Properties
Use current tags in a controller to create a produce/consume tag Controller: Secure Tag: Create
relationship Tag: Delete
Add a new tag, and then create a produce/consume tag relationship Controller: Secure Tag: Create
Add a new AOI Controller: Secure Add-On Instruction: Create
Overwrite an AOI that already exists (properties are modified) Controller: Secure Add-On Instruction: Modify
Delete an AOI Controller: Secure Add-On Instruction: Delete
Add a new UDT Controller: Secure User Defined Type: Create
Overwrite an UDT that already exists (properties are modified) Controller: Secure User Defined Type: Modify
Delete an UDT Controller: Secure User Defined Type: Delete
Search a Logix Designer project Controller: Secure Project: Open
See also
Required FactoryTalk View FactoryTalk View SE permissions set in FactoryTalk Security determine if a user
or group can perform actions on Studio 5000 Architect projects that contain
SE permissions for Studio FactoryTalk View SE applications. If the user or group does not have the required
5000 Architect software permissions, Studio 5000 Architect actions either display an error message or have
limited functionality.
See also
Required FactoryTalk View FactoryTalk View Machine Edition permissions set in FactoryTalk Security
determine if a user or group can perform actions on Studio 5000 Architect
Machine Edition projects that contain FactoryTalk View Machine Edition applications. If the user
permissions for Studio 5000 or group does not have the required permissions, Studio 5000 Architect actions
either display an error message or have limited functionality.
Architect software
Action Required FactoryTalk Directory Required Application
permissions permissions
Add existing FactoryTalk View Machine Editionapplication List Children: Allow List Children: Allow
Read: Allow Read: Allow
Open FactoryTalk View Machine Edition application in FactoryTalk View Studio List Children: Allow List Children: Allow
Read: Allow Read: Allow
Commit existing FactoryTalk View Machine Edition application Create Children: Allow Create Children: Allow
Delete: Allow Delete: Allow
List Children: Allow List Children: Allow
Read: Allow Read: Allow
Write: Allow Write: Allow
Update existing FactoryTalk View Machine Edition application List Children: Allow List Children: Allow
Read: Allow Read: Allow
See also
See also
You can view the Rockwell Automation End-User License Agreement ("EULA")
by opening the License.rtf file located in your product's install folder on your hard
drive.
Trademark notices
Other trademarks
All other trademarks are the property of their respective holders and are hereby
acknowledged.
Warranty
This product is warranted in accordance with the product license. The products
performance may be affected by system configuration, the application being
performed, operator control, maintenance, and other related factors. Rockwell
Automation is not responsible for these intervening factors. The instructions in
this document do not cover all the details or variations in the equipment,
procedure, or process described, nor do they provide directions for meeting every
possible contingency during installation, operation, or maintenance. This
products implementation may vary among users.
This document is current as of the time of release of the product; however, the
accompanying software may have changed since the release. Rockwell Automation,
Inc. reserves the right to change any information contained in this document or
the software at any time without prior notice. It is your responsibility to obtain the
most current information available from Rockwell when installing or using this
product.
Environmental compliance
F K
FactoryTalk View ME station Kinetix servo drive
add 52, 53 add 43
FactoryTalk View SE server
add 54
FactoryTalk View SE station
L
add 52 library
file create 109
add 95 delete 111
find export 111
library components 122 export part of 111
matching controller 105 import 110
rename 110
library component
G add 114
generic switch copy to other software 115, 116
add 72 delete 117
connect to 73 import 115
graphic rename 116
add 95 view properties 117
supported formats 98 link
add 97
log off 135
H Legal Notices 145
hardware diagram log on 134
add 25
close 27
open 26
M
remove 27 managed switch
Hardware Diagram 10 add 72
connect to 73
MobileView graphic terminal
I add 47
I/O Aliases 93 module
image add 42
add 95
supported formats 98
import
N
controller project from file 65 network trunk
controller project from online controller 66 add 73
FactoryTalk View application from file 67 connect component to 74
library 110
library component 115
install 16
O
ownership relationship
add 82
148 Rockwell Automation Publication ARCH-GR001G-EN-E
Index
S
set
FactoryTalk Directory permissions 136
FactoryTalk View Machine Edition permissions 139
FactoryTalk View SE permissions 138
Logix Designer permissions 137
Studio 5000 Architect permissions 137
settings
libraries 130
page 128
project 127
Rockwell Automation Publication ARCH-GR001G-EN-E 149
Rockwell Automation support
Rockwell Automation provides technical information on the web to assist you in using its products. At
http://www.rockwellautomation.com/support you can find technical and application notes, sample code, and links to software service packs. You
can also visit our Support Center at https://rockwellautomation.custhelp.com for software updates, support chats and forums, technical
information, FAQs, and to sign up for product notification updates.
In addition, we offer multiple support programs for installation, configuration, and troubleshooting. For more information, contact your local
distributor or Rockwell Automation representative, or visit http://www.rockwellautomation.com/services/online-phone.
Installation assistance
If you experience a problem within the first 24 hours of installation, review the information that is contained in this manual. You can contact
Customer Support for initial help in getting your product up and running.
United States Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to
your distributor to complete the return process.
Outside United States Please contact your local Rockwell Automation representative for the return procedure.
Documentation feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete the
feedback form, publication RA-DU002.
Supersedes Publication ARCH-GR001F-EN-E Copyright 2017 Rockwell Automation Technologies, Inc. All rights reserved. Printed in the U.S.A.