Recipes
Recipe Definition
The Recipe Definition section is where you configure the structure of all available recipe variables. Each entry you define here represents a PLC-bound variable that can later be used in recipe instances (see Recipe List). This is the foundational step for enabling structured, parameterized configuration in the frontend.
Purpose
This view allows you to:
- Declare which variables should be part of recipes
- Set input limits for each variable (Min/Max)
- Bind each variable to its location in the PLC
- Assign optional display labels for frontend use
Field Descriptions
- Name: The full technical variable name (e.g.,
Recipe1.rTemp) that maps to the PLC. It must be unique across the list. - Label: An optional display name shown in the frontend. This can be used to provide a more readable or localized label.
- Min Value / Max Value: These define the allowable range for user input. Values outside this range cannot be entered in the frontend.
- Value: Initial or default value. This is not written to the PLC unless a recipe is applied.
- Path: The exact address of the variable in the PLC project, including scope and namespace. This is required to link UI variables to PLC memory.
Usage Notes
- Variables defined here are automatically made available when creating or editing recipe entries under "Recipe List".
- You must define at least one recipe variable before any recipe list items can be used in the frontend.
- Backend validation prevents input outside the Min/Max range. There is no need to add external logic for this.
Connection Assignment
When adding a new variable, you will be asked to select a connection. This ensures that each recipe variable knows which PLC or runtime it belongs to.
Recipe1.rTemp