FactoryTalk View Studio

Project Settings

Project window size and run-time screen resolution

Title bar

Start Up
Used to specify which application processes and components to start when the application starts at run time.

can specify once youve set up all the parts of the application, or as you create them.

Developing a hierarchy of displays

A hierarchy of displays is a series of graphic displays that provide progressively more detail as users move through them. Design your display hierarchy to meet the needs of the various users, including managers, supervisors, and operators. Well-organized graphic displays present information clearly and consistently and guide users through the system. Before designing individual graphic displays, plan an overall display hierarchy and plan how users will navigate through the hierarchy

Display Settings

Display Buttons

Message
Use local messages to give the operator ongoing information about the status of devices and processes. For example, you might use local messages to describe the status of a device whose condition cannot be shown graphically with complete accuracy

Follow these steps to set up local messages: 1. In the Local Messages editor, set up the messages and their trigger values. 2. In the Graphics editor, create local message display objects in the graphic displays in which you want the messages to appear at run time. For each local message display, assign a tag or expression to the Value connection and specify the file of messages to display.

Alarms

Follow these steps to set up alarms: 1. In the Alarm Setup editor, set up alarm triggers (the tags or expressions to monitor), define the alarm messages and their trigger values, and specify the graphic display to open when alarms occur (if any). Also use this editor to specify trigger types, Acknowledge all values, the maximum alarm log file size, the hold time, and optional connections. 2. In the Startup editor, ensure that the Alarms box is checked (it is checked by default). 3. If desired, in the Graphics editor modify the default [ALARM] display, or create your own graphic display to use for alarms. For example, if you wont be using audible alarm signals, edit the default display to remove the silence alarms button. For information about graphic displays, 4. Test alarms on the run-time system.

Data Logging
Follow these steps to set up data logging: 1. In the Data Log Models editor, set up a data log model that specifies how many log values to store, the conditions that trigger data logging, where to log data, and which tags to monitor.

2. In the Startup editor, turn on data logging by selecting the Data logging check box.Also use this editor to specify the data log model to use at run time.
3. In the Graphics editor, create a graphic display containing the trend graphic object, and set up how the object looks, which tag values to display, the start time, and the time span for the data. Also specify the name of the data log model to use.

Recipes

A recipe is a set of numeric and string data values (ingredients) that can be downloaded to their associated tags at the data source. Each ingredient has a pre-set data value assigned to it. The set of data values for all the ingredients in a recipe is called a data set. The set of numeric and string tags assigned to the ingredients in the recipe is called a tag set. The ingredients, data sets, and tag sets are stored together in a recipe file

Recipes

For example, a bakery making whole wheat bread could use the same ingredients and tag sets, but depending on the type of crust desired, could use different data sets to specify different baking temperatures. As another example, you might want to have multiple production lines baking the same bread. In this case, the data set for all the production lines would be the same, but the tags receiving the recipe information would be different for each production line. Units allow you to combine different tag sets and data sets for the same set of ingredients

Creating Runtime Application