We have done a lot of projects using "recipes". We have done it (1) of (2) ways.

1) using the built-in Recipe functions in the C-more HMI, > Object > Recipe > Recipe and Call Recipe objects.

2) using standard Numeric Entry objects to load recipe setpoints and standard Pushbutton to load selected recipe setpoints into the control setpoint registers.

It depended on the size and number of recipes. It was manageable to use standard Numeric Entry objects for smaller number of recipes, and smaller number of recipe setpoints (setpoint Numeric Entry objects that can fit on (1) screen, for example). It was easier for the operators (or plant managers) to use the standard Numeric Entry objects than to navigate the Recipe Sheets. However for very large number of recipes and recipe setpoints, and plant managers that can manage Excel spreadsheets, and can import and export spreadsheet files, then the C-more Recipe functions are the way to go. This would apply to Productivity PLCs, as well as other PLCs.

Once this decision is made which way to go, then pointers can be given on how to get started.

I would guess 80% of our projects fell into the smaller category, and where the operators, and managers, wanted the Numeric Entry objects.

I would then suggest using standard Numeric Entry, Pushbutton, and Numeric Display objects, as this will be easier for the operators. Also, each setpoint Numeric Entry object can include a Label and/or static text box to further identify the setpoint. We would have a screen with a list of recipes, along with recipe numbers, and static text boxes to further identify the recipes. The recipe name and/or number would be Screen Change Pushbuttons taking you to the selected recipe setpoint screen, where you enter each setpoint for that recipe. Copy and paste makes this easy, just change tags.

When you select the desired recipe name/number, and press the "Load Recipe" push button, the setpoints of the selected recipe are loaded into the controlling setpoint registers. We include a screen showing the loaded controlling setpoint values, along with the selected recipe name/number.

Thought has to be given to who has access to adjust recipe setpoint values and/or to load recipes. Once a process had been started, the PLC logic disables changing the recipe, until the process has completed, or until the operator "aborts" the process, and the abort procedure has completed. There may be other PLC permissives, alarms, and HMI pass codes that are required. For example, valve feedback switches to prove proper valve schedule for a given recipe.