Recipe management

In a typical automation system, we execute certain types of processes to achieve some services or to create some products. If we don’t have any variation then in our manufactured products or service then we don’t need any recipe. The automation system can do the work repeatedly without any problem.

The simplest example, is if we want to create many pieces of a single type of pizza then the automation system can repeatedly create the same type of pizza. But if we want to create a different type of pizza by varying the amount of content and type of content then we need a recipe. The recipe will determine what kind of produce the automation system will produce.  There are two important terms we use in TwinCAT HMI Engineering, those are:

Download the sample (kind of Beckhoff made!)

Recipe type:

A recipe type is a general description of a set of symbols, based on these we can create different types of recipes. These are comparable to class (recipe type) in object-oriented programming from where we can make instances of the class (recipes) with different attributes.

Recipe :

A recipe is a combination of different recipe types. This is more like an instance of a class and which can have different attributes for different variables.




Download the sample from the link given above.

Next, let’s try to understand how to integrate OPC UA at


Ask questions related to Hemelix sample code and design at Google group