Prerequisites and Restrictions
Prerequisites
MERLIC 5.6.2 Installation
To use the MERLIC Communicator, you have to install the current MERLIC version. It contains the required files for the Communicator and the plug-in implementation such as header files, libraries, or example plug-ins.
The following sections give an overview of the files for the Communicator that are contained in the MERLIC installation. To get information on further prerequisites for the implementation of a plug-in, see the reference documentation of the Communicator API.
Header Files
The header files are installed in the "include" directory within the MERLIC installation path.
Libraries
|
Operating system |
File |
|---|---|
|
Windows |
lib/x64-win64/communicator.lib |
Example Plug-ins
We provide various example plug-ins. They are installed in the same directory in which the MVApp examples are stored. Thus, if you started the MVTec Software Manager (SOM) for the installation with administrator rights, the example plug-ins are installed in the directory "%PROGRAMFILES%\MVTec\MERLIC-5.6\examples" by default. If you started SOM in user mode, i.e., without administrator rights, the example plug-ins are installed in the directory "%LOCALAPPDATA%\Programs\MVTec\MERLIC-5.6\examples" by default.
The provided example plug-ins are implemented in C++ 17. You have to make sure to use a compiler that supports this revision of C++. For more information about the example plug-ins, see the topic Example Plug-ins.
Restrictions
Use of Multiple Communicator or MERLIC Instances
While it is in principle possible to use more than one instance The term instance is used to describe a new or additional context based on a model, e.g., an executeble, plug-in, etc. Therefore limitations, parameters, and values can differ from one instance to another, e.g., based on command line parameters and .ini settings. It is possible to start multiple instances of Communicator plug-ins. of the Communicator to connect to the same instance of MERLIC, we currently strongly discourage this scenario because it can not be ensured that unique IDs are given to the plug-ins.
Required Adjustments for MVApps of Previous MERLIC Versions
In some cases it might be required to make some adjustments to the MVApp if it was created in a previous MERLIC version, e.g., MERLIC 4.4.2.
Especially if you are using camera devices with GenICam compliant digital I/O channels and also want to perform a recipe change via the process integration mode, you have to edit the MVApp to use the new Image Source Manager (ISM) for the image acquisition instead of the tool "Acquire Image from Camera" or "Acquire Image from File".
For a detailed description of the Image Source Manager, see the topic Image Acquisition in MERLIC in the MERLIC manual.
