Recipe Definition

Top  Previous  Next

All recipe variables in the <recipe> worksheet are defined with type and an initial value if necessary. The <recipe> worksheet has the following structure:

 

Variable

VarType

Value

#Recipe=Default


 Path=

/<DRV>/<Host>/MyRecipeVar1

WORD

123

/<DRV>/<Host>/MyRecipeVar2

WORD

345






 

Icon-Hinweis        System variables in recipes

System variables can be defined in the recipe as recipe variables and also as values. In this case the actual value of the system variables is saved in the recipe and written to the PLC if necessary.

 

Icon-Hinweis        Consistency of recipe files

Recipe files are saved in XML format to ensure data consistency. The recipe files are assigned an ID for project name, version (from Project Settings), recipe type and number of variables

Only recipes with a corresponding project name can be loaded
If the recipe files are different (xml does not correspond to the recipe definition), an error message is output (Runtime Error). The version of the recipe file is displayed.

 Cancel: The recipe is not loaded

 Ignore: Recipe variables with the same name and data type are loaded. Non-existent variables are ignored and skipped.

 New variables that are not present in the recipe file remain unchanged. For variables with different data types, a type conversion of the value is executed from the old type to the new type.

 For string variables with different string lengths, only what is possible is accepted (with smaller string lengths, only as many characters as the new one has space)

The process with different versions is written in the EPAM log (version of the recipe file, variable with type conflict or non-existent variable)
Recipe files can be deleted with the Delete button (Delete=Cancel and delete file); Cancel and Ignore does not delete the file

 

warnung_allg        Consistency of recipe values

The saving and loading of recipe data is NOT synchronous with the PLC cycle! The data consistency over all recipe values must be examined via the recipe status in the PLC. A recipe is fully loaded if the recipe status is 2.

 

Difference to EPAM3

Multi-level recipes are not yet supported