Configure the Safety Application

After you define the location, ownership, and configuration of safety controllers and safety I/O devices, you must configure the safety application for each controller. A safety application includes a safety task with safety programs and routines.
When you add a safety controller to a project,
FactoryTalk® Design Studio™
 automatically creates an application for that controller, which contains an empty safety task.
To configure the safety application:
  1. In the Execution explorer, open the safety application to access the safety task. For more information about tasks, see Tasks in the FactoryTalk Design Studio Online Help.
  2. Configure the safety task in the Properties pane (see Safety Tasks).
    Safety Task Properties pane
  3. To add a program, right-click the safety task and select New Program (see Safety Programs). The Class must be Safety and the Main Routine Type must be Ladder Diagram. Select Create. For more information on how to create programs, see Programs in the FactoryTalk Design Studio Online Help.
  4. In the Execution explorer, open the main routine under the program that you created. Use the Toolbox pane to add logic to the safety routine. See Ladder Diagram Safety Instructions.
  5. Edit controller, program, and routine tags and parameters. See Safety Tags and Parameters. For more information on how to create tags, also see Tags in the FactoryTalk Design Studio Online Help.

Programming Restrictions

FactoryTalk® Design Studio™
 limits the availability of some menu items and features, such as cut, paste, delete, and replace, to protect safety components from modification when the following are true:
  • The controller is safety-locked
  • A safety signature exists
  • Safety faults are present
  • User access is restricted (see Managing User Roles and Access)
  • Safety status is in any of these states when online:
    • Partner missing
    • Partner unavailable
    • Hardware incompatible
    • Firmware incompatible
IMPORTANT: The maximum and last scan times of the safety task and safety programs can be reset when online.
If even one of these conditions applies, you cannot do the following:
  • Create or modify safety objects, including safety programs, safety routines, safety tags, and safety I/O devices
  • Apply forces to safety tags
  • Modify or delete user-defined data types that are used by safety tags
  • Modify the controller name, description, chassis type, slot, and safety network number
  • Create, modify, or delete a safety connection
When the controller is safety-locked, you cannot modify or delete the safety signature.

Controller Capacity

Controllers have a finite programming capacity. You can monitor the controller memory usage by opening the Properties pane for the controller. The Controller Capacity pane shows Standard Controller Usage (memory that is used by standard programs) and Safety Controller Usage (memory that is used by safety programs).
Controller Capacity
If the size of the project approaches or exceeds the total capacity available in the controller, a message warns you about the limited or exceeded capacity. When the controller capacity is exceeded, you cannot download to the controller.
The Usage Information dropdown shows:
  • Usage - Shows the percentage of blocks used by the project.
  • Available - The number of unused blocks.
  • Used - The number of blocks used by the project.
  • Total - The total number of blocks available in the controller.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal