Add a new controller
Before programming or configuring a controller, create a project file in which to store it by adding a new controller.
To add a new controller:
- FromFile, selectNew.
- In theNew Projectdialog box, select a controller.
- InName, enter a name for the project and selectNext.The same name is used for the project file with the .acd extension.
- ForRevision, select the major revision of the firmware for which this project is configured.Choose from the list of major revisions that are installed that support the controller type.
- ForChassis, choose the appropriate chassis type for the controller.
- This field applies to 1756 ControlLogix and 1756 GuardLogix controller types.
- This field is unavailable for CompactLogix or GuardLogix controller types. These controllers do not have a physical chassis, and therefore do not need a chassis type.
- InSlot, enter the slot number for the controller.
- For 1769-L1x CompactLogix controllers,Expansion I/Ois used instead ofSlot.IMPORTANTWhen usingExpansion I/Owhile online with the controller, make sure theExpansion I/Osetting matches the actual number of modules in the chassis to prevent unexpected control.
- 1756 controllers occupy a numbered slot in the chassis. Place the controller in slot.
- GuardLogix controllers occupy two slots. Reserve the last slot in the chassis for the GuardLogix safety partner processor.
- For CompactLogix controllers, because the controller always resides in slot 0 of the virtual backplane, this field is unavailable, and slot number 0 displays in theController Propertiesdialog box,Generaltab,Slotfield.
- For GuardLogix L7x safety controllers, theSafety Partner Slotalso appears. This field is a read-only field whose value is always equal to the value entered in theSlotfield plus 1. For example, if a value of 1 is in theSlotfield, theSafety Partner Slotvalue is equal to 2.
- For GuardLogix L8x safety controllers, the project default is SIL2/PLd with no safety partner.
- To associate this project with a specificSecurity Authority, selectFactoryTalk Securityand then selectUse only the selected Security Authority for Authentication and Authorization. When selected, users interacting with this project must be authenticated and authorized by the sameSecurity Authoritythat was used to secure the project. To remove the association to the specifiedSecurity Authorityfor this project, go online with the controller and clear this check box.This check box is only enabled when using FactoryTalk Services Platform 2.50 or later.When associating a project with a specific Security Authority, the project is also associated with a specific FactoryTalk Network Directory that is identified by a security authority identifier. Projects that are secured and bound to a specific Security Authority cannot be recovered if the security authority identifier of the FactoryTalk Network Directory used to secure the project no longer exists.IMPORTANTBefore associating this project with a specific Security Authority, Rockwell Automation recommends backing up the FactoryTalk Directory, saving unsecured versions of this project file in (.ACD) or (.L5X or .L5K) formats, and saving them in a secure location.For details about backing up a FactoryTalk Directory, see FactoryTalk Help:Start > Programs > Rockwell Software > FactoryTalk Tools > FactoryTalk Help.
- Select aSecure Withoption:
- To associate the project with a Logical Name in FactoryTalk Services Platform, selectLogical Name <Controller Name>. If there is no existing Logical name that matches the controller name, a new Logical Name is created with the controller's name and it inherits permissions from its parent resource.
- To associate the project with a Permission Set configured in FactoryTalk Services Platform, selectPermission Setand select a permission set from the list.
- In theDescriptionfield, enter a description of the controller.
- If redundancy is available for this controller and used for this project, selectRedundancy Enabled.
- SelectFinishto create the project.Once the project file is created, theController Organizeropens, which shows everything in the controller.The default configuration contains a continuous task, calledMainTask. TheMainTaskcontains a program calledMainProgram. TheMainProgramcontains a routine calledMainRoutine, which is configured as the main routine.If using a Safety controller, the primary controller and safety partner are created under theI/O Configurationfolder. The safety partner is created with the same name as the primary controller, with the word Partner appended to it (for example, MYCONTROLLER:Partner).Modules created at the time that the controller was created cannot be deleted, copied, cut, pasted, dragged, or dropped. In addition, when working with a safety controller, the safety partner cannot be deleted, copied, cut, pasted, or dragged and dropped.Safety controllers create aSafetyTaskas well as a standardMainTask. For more information, refer to theGuardLogix Controllers User Manual(publication 1756-UM020) or theCompact GuardLogix Controllers User Manual, publication 1768-UM002.
Provide Feedback