MERLIC Recipe Files

MERLIC recipe files are a crucial part for MERLIC RTE MERLIC RTE (Runtime Environment) is the name of the application that is used to start MERLIC in process integration mode. It can be started either via the Windows start menu or via the command line with the executable "merlic_rte.exe"., the process integration MERLIC can be used in machine vision systems that are integrated in a manufacturing machine. The machine controller, e.g., a programmable logic controller (PLC), must be able to control an integrated vision system, to monitor the execution, and to query the results. Therefore, MERLIC provides a process integration mode to enable the communication with a machine controller. The process integration mode can be started with the application "MERLIC RTE" that is provided with the MERLIC installation. mode of MERLIC because they are required to load MERLIC Vision Apps (MVApps) in MERLIC RTE mode.

A MERLIC recipe contains various information about a specific MVApp:

• Name and location of the MVApp
• Pre-defined set of input values and data types for selected tool parameters of the MVApp (MVApp parameters)
• Optional description of the recipe file
• Optional reference of the acquisition sequence to be activated

Recipes can be created via the MERLIC Creator and are stored in separate files with file ending .mrcp.

By loading a MERLIC recipe in MERLIC RTE mode, the respective MVApp will be loaded with the parameter settings defined in the recipe. If the recipe references an acquisition sequence, it will be automatically activated.

You have to create a MERLIC recipe for each MVApp you want to use in MERLIC RTE. However, you can also create multiple recipe files with individual sets of input values for one and the same MVApp. This enables you to reuse an MVApp with different parameter settings and different image acquisition settings for various scenarios of your application.

In MERLIC RTE, you can switch between the MVApps with their individual parameter settings by changing the recipe, that is, by loading the MERLIC recipe that references the desired MVApp and settings. The respective MVApp will then be loaded. However, if you change to a recipe that references the same MVApp but with different parameter settings, the MVApp is not loaded anew. Instead, only the parameter settings defined in the newly loaded recipe are applied. As the MVApp is not loaded anew in this case, the state of the respective MERLIC tools or connected Frontends will not be reset. For example, this might affect tool results such as "Counter" of the Get Execution Info tool or the buffered data in Determine Data History. If you want to ensure that the MVApp is loaded anew when changing the recipe, you can first unload the current recipe via "UnprepareRecipe" before loading the new recipe.

Get More Information