#Recipe

Top  Previous  Next

The #Recipe object is used for managing recipes with the Recipe definition. The Recipe object is a global object.

 

The recipe object enables a defined variable set to be saved and loaded. This variable set consists of recipe variables. The actual values of the variable set are saved in the file ACTUAL.XMLA. The recipe variables are defined in the Recipe definition. Several recipe objects can be created. Each recipe object has its own definition file. The unique name of the recipe type is formed from the name of the definition file.

 

Parameters

Object

Column A, object

M/O

Default

Description

#Recipe

M


Recipe handling

 

Text/File

Column B, Text/File

M/O

Default

Description

<recipe.txt>

M


Recipe definition with the recipe variables.

 

Action

Two comma separated Actions may be defined: [[action1],action2]

The first action is executed  with the button action Recipe:[<type>].csave for confirmation if the recipe file already exists. A runtime error is displayed if this action is not configured
The second action is executed whenever a recipe has been saved successfully.

Column K

M/O

Default

Description

#Page=<name>

O


Change to screen page <name>

Close

O


Close the topmost page

 

ActionLimit1

Spalte K

M/O

Default

Description

#Page=<name>

O


Change to screen page <name> if on Button action

Recipe:[<type>].{csave¦save} the root directory of the target path ( /S/APP/Recipe:Path) doesn't exist.

 

This may happen, if the target directory is located in a memory stick, but the memory stick isn't connected.

 

Eg. : /StorageCard2

 

If action isn't defined a system runtime error pops up.

 

ActionLimit2

Spalte K

M/O

Default

Description

#Page=<name>

O


Change to screen page <name> if on Button action

Recipe:[<type>].Load the recipe file to load doesn't exists.

 

If action isn't defined a system runtime error pops up.

 

VarValue

Column P

M/O

Default

Description

Variable

M


Variable as Status/Control word

Control/Status word

Value

Direction

Description

1

PLC->EPAM

PLC requests a recipe download.

EPAM is required by the PLC to reload the current recipe or the recipe values modified by the user and to write it to the PLC.

2

EPAM->PLC

Epam indicates to the PLC that the request (Download/Upload) is completed.

3

PLC->EPAM

PLC requests an upload of recipe variables from the PLC.

The actual values are saved in the ACTUAL.XMLA file.

4

EPAM->PLC

Epam indicates to the PLC that the download is running.

5

EPAM->PLC

Epam indicates to the PLC that the upload is running.

6

PLC->EPAM

PLC requests that the recipe /S/APP/<recipetype>_file is saved or overwritten.

7

PLC->EPAM

PLC requests that the recipe /S/APP/<recipetype>_file is loaded and that a download is then carried out.

 

VarType

Column Q

M/O

Default

Description

WORD

UINT

INT

M


The integer data types are supported

 

Option

Column S

M/O

Default

Description

 

 

Download ACTUAL.XMLA

Recipe values from ACTUAL.XMLA are written to the PLC on EPAM start. ACTUAL.XMLA contains the actual state of the recipe variables, i.e. also values that were changed manually by the user for example.

NoDownload

O


When EPAM is started, no data is transferred to the PLC. ACTUAL.XMLA is not created.

NoActual

O


Recipe values of the last loaded recipe are written on EPAM startup to the PLC . If variable values were manually changed by the user and not saved in the recipe, these will be lost or overwritten again with the recipe values.

ACTUAL.XMLA is not created.

 

See also

Recipe action
RecipeList action

 

 

Difference to EPAM3

The options Filename=Auto and Filename=Auto10 are currently not supported