|
<< Click to Display Table of Contents >> Recipes |
  
|
|
<< Click to Display Table of Contents >> Recipes |
|
A Recipe is when SpecView saves the values of selected variables so that the values can be later uploaded to the connected instruments.
Recipes are useful for the following:
| • | Eliminating operator error in setting machine parameters |
| • | Taking a snapshot of the current process values when a good product is being made |
| • | Exactly reproducing previous machine setup |
| • | Displaying the loaded Recipe on-screen |
| • | Saving and reloading instrument setup parameters |
| • | Reviewing and editing complex programmer profiles |
There are four steps to creating a recipe:
1. In Edit Mode: Create a screen (GDW) and put all the variables on it that are intended to be set using Recipe. This screen can be thought of as a Recipe screen.
Note: The variables need to be writeable so that they can be changed.
2. Select these variables for Recipe using the Recipe tool 
which looks like a 'knife and fork'. Once all the variables are selected click the Recipe tool again.
3. In Runtime mode: Create the sets of values and save each set, giving each a different name.
4. To use the Recipe(s) in Runtime Mode go to the Recipe menu and choose Recipe Manager. Alternatively, to make it easier to use in Runtime Mode, go into Edit mode and either:
| • | Setup a button to do a button action for Recipe, such as: Recipe: Download Specific Recipe |
or
| • | Setup an automatic Recipe action via the Strategy Controller |
5. It is possible to limit which Recipe names are shown in the Recipe Manager box.
Each screen (GDW) in SpecView can have one Recipe associated with it. When 'Recipe mode' is selected a highlight (box) appears around all the variables selected for Recipe.
The Recipe defines the set of variables, and there can only be one of these per GDW, but there can be up to 1,295 different sets of values for these variables which are saved as files to disk.
However, each set of values may not need to set all the variables in the Recipe, therefore in order to set only some of the variables at a time the value N/C (No Change) can be used.
NOTE: A Recipe is therefore made up of two parts:
• The full list of variables which can be included in a Recipe (and there can only be one of these per GDW).
• The named sets of values for these variables (and there can be 1,295 different sets of values).
As of SpecView version 3.1.253, the number of Recipes per GDW was increased to 32,767.
Therefore, from 3.1.253 onwards there can be 32,767 named sets of values.
Recipe names may be any length and can include spaces and special characters.
A description, which for example, may include special instructions to the operator, can be associated with each set of Recipe values.
Either Button actions or the Strategy Controller can make use of Recipes.
The order that values are downloaded into variables can be defined using Recipe Levels
SpecView will automatically retry Recipe value downloads if there is a failure.
Selecting Variables to be Included in Recipe
Recipe Variables in the Variables List
Setting the Recipe download order
Recipe Limit - to limit which Recipe names are shown in the Recipe Manager box.