Create a Project

A project organizes all the different components of a control program. Before using any of
Logix Designer
 features, create a project.
Creating a project uses these items:
Project Component
Definition
Task
Provides scheduling and priority information for a set of one or more programs.
Program
Each task requires at least one program that defines the operations.
Routine
Provides the executable code for the project in a controller. Each routine uses a specific programming language (ladder logic, function block diagram, sequential function chart, or structured text).
MainRoutine
The first routine executed in a program. Use the main routine to call other routines (subroutines), using the Jump to Subroutine (JSR) instruction.
Subroutine
Any routine other than the main routine or fault routine.
To create a project
  1. From
    File
    , choose
    New
    .
    The
    New Project
     dialog opens.
  2. In
    Project Type
    , select
    Logix
    , then choose the controller type to use for this project.
  3. Enter the name to use for the controller.
    TIP:
    An .acd extension is added to controller name to name the project file. Example:
    MyControllerName.acd
  4. In
    Location
    , type or browse to a location to store the project file. By default, projects are saved to <user>\My Documents\Studio 5000\Projects
  5. Select
    Next
    .
  6. In
    Revision list
    , select a firmware revision for the controller. The latest revision of firmware is the default.
  7. In
    Security Authority
    , select a security option:
    • No Protection
       - All users can view and edit the project.
    • FactoryTalk Security
       - Only users authenticated through FactoryTalk Security can view and edit the project.
      (optional) Select
      Use only the selected Security Authority for authentication and authorization
       to associate this project with a specific Security Authority. When this check box is selected, users interacting with this project must be authenticated and authorized by the same Security Authority that was used to secure the project.
  8. Select
    Logical Name
    <
    Controller Name
    > or
    Permission Set
     to apply specific permissions to the controller.
    • Select
      Logical Name
       <
      Controller Name
      > to apply a Logical Name in FactoryTalk Services Platform that has the same name as the controller. If there is no existing Logical Name that matches the controller name, a new Logical Name is created with the controller's name. The new Logical Name inherits permissions from its parent resource.
    • Select
      Permission Set
       to apply a specific set of permissions to the controller. The permission sets in the list are maintained in FactoryTalk Services Platform and identify a set of actions that are allowed or denied for a particular user and computer combination.
  9. (optional) In
    Description
    , enter a description for the controller.
  10. Select
    Finish
    .
    Once the project file is created, the
    Controller Organizer
    opens.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.