MVTec MERLIC 5.7.1 Runtime for x64-Linux

MVTec MERLIC 5.7.1 Runtime for x64-LinuxFile Name: merlic-5.7.1-x64-linux_merlic_rte-dl.tar.gzFile Size: 3880309467 bytes (3.61 GB)Modification Date: 2025-06-05 23:48MD5: a0f5c403956a79e9b191b7b976a6f85dSHA1: 112d9e12c4d4bdbfefea18a1188b589faf287dd3SHA256: e35431fee9a5db7119481ce94e8d8a10cfb4e109f468c43b571d459958b4b030CRC32: f05f5581Download from Baidu Cloud:

MVTec MERLIC 5.7.1 Runtime for x64-Linux

http://visionbbs.com/thread-33741-1-1.html

(Source: Shi Xinhua Vision Forum)

Latest Features of MERLIC 5.7

MVTec released the new version MERLIC 5.7 on April 3, 2025. The new version 5.7 enhances the usability of the MERLIC Runtime Environment (RTE) and optimizes the operation of communication interfaces. MVTec MERLIC integrates powerful traditional machine vision methods with state-of-the-art deep learning technologies. Additionally, its graphical user interface helps users intuitively create complete machine vision applications.

What’s New?

MERLIC 5.7 optimizes the integration with machine control systems by managing communication plugins directly within the MERLIC Runtime Environment (RTE). This reduces components, enhances usability, and simplifies deployment. Furthermore, the MERLIC frontend is now available for Linux and can be used as a remote frontend, enabling flexible system architecture. New example Docker files and scripts assist in containerized deployment and integration into existing workflows.

Further Simplification of Integration with Machine Control Systems

MVTec MERLIC 5.7.1 Runtime for x64-Linux

In MERLIC 5.7, the integration process with machine control systems has been further optimized. Now, configuring and running communication plugins only requires the MERLIC Runtime Environment (RTE), without the need to start and manage additional processes as in previous versions. By integrating plugin management into the RTE, the required components are reduced, usability is enhanced, and the deployment process is further simplified. For example, two MERLIC RTE instances can now run in parallel without manual port configuration. Additionally, plugin messages are now directly logged in the MERLIC RTE log file, greatly simplifying the debugging process.MERLIC Frontend Now Supports Linux

MVTec MERLIC 5.7.1 Runtime for x64-Linux

In addition to the MERLIC Runtime Environment (RTE), the MERLIC Frontend is now also supported on Linux. Starting from MERLIC 5.7, users can visualize image processing results directly on Linux systems.

The MERLIC Frontend can run locally or as a remote frontend on a separate Linux system. This flexible system architecture allows for the separation of image processing and visualization to optimize resource usage, such as running the frontend on a standalone terminal or enabling remote monitoring over the network.

Example Dockerfiles and Scripts for Containerized Deployment

MVTec MERLIC 5.7.1 Runtime for x64-Linux

Dockerfiles and related scripts are provided for easy deployment of MERLIC in a containerized environment. These examples can be used to quickly set up the MERLIC Runtime Environment (RTE) and MERLIC Frontend, enabling a more flexible and scalable deployment approach suitable for industrial automation and cloud applications.

Release Notes for MERLIC 5.7.1

Here you can read the release notes for MVTec MERLIC 5.7.1, as released in June 2025.

Contents

  • Supported Operating Systems

  • Image Source Manager

  • MERLIC RTE Setup

  • MERLIC Creator

  • MERLIC Designer

  • Examples

  • Documentation

  • Release Notes for Linux Systems Only

  • Known Issues

Supported Operating Systems

MERLIC is available for Windows and Linux systems. On Windows, all components of MERLIC can be used. For Linux systems, currently only the runtime environment of MERLIC, MERLIC RTE, and MERLIC Frontend are available.

Windows

MERLIC 5.7.1 is available for Windows 10 (64-bit, version 1903) or newer.

Linux

MERLIC RTE and MERLIC Frontend are available on PC-based and Arm-based Linux systems (kernel version 5.4 or newer).

Developing the MERLIC Vision App is still done on a Windows system with the MERLIC Creator. The application can then be used with MERLIC RTE and MERLIC Frontend on the Linux system. Cameras can be set up remotely with the help of MERLIC RTE Setup.

System Requirements

A detailed description of the system requirements for installing and using MERLIC on Windows and Linux systems is provided in the MERLIC manual on the page System Requirements.

Image Source Manager

  • Enhancements

    • GigEVision2: Revision 24.11.21

    • GenICamGenTL: Revision 24.11.21

    • USB3Vision: Revision 24.11.25

    • File: Revision 18.11.5

    • The image acquisition interfaces that are used for the Image Source Manager (ISM) as well as for the tools “Acquire Image from Camera” and “Acquire Image from File”, respectively, have been updated to a new revision. MERLIC now contains the following versions of the interfaces:

MERLIC RTE Setup

  • Fixed Problems

    • MERLIC RTE did not shut down properly on Windows when closing the console window or using Ctrl+Break instead of Ctrl+C. As a consequence, a connected MERLIC RTE Setup did not update the tabs to reflect the lost connection. Instead, it was still offering to configure image sources and communication plug-ins, while not allowing to configure recipes and I/O devices. This problem has been fixed.

MERLIC Creator

  • Fixed Problems

    • If MERLIC Creator crashes, MERLIC shows a message dialog and tries to save the current MVApp as backup. After closing the dialog, the MERLIC Creator window remained open. However, the window was unresponsive and could only be closed by force-quitting the application. This problem has been fixed. In case MERLIC Creator crashes, it will now exit after closing the respective message dialog.

MERLIC Designer

  • Fixed Problems

    • The .ts translation files generated by the “Export Translation Files (.ts)” feature of the Frontend Designer were missing entries for error texts for languages other than English (en_US), German (de_DE), Japanese (ja_JP), and simplified Chinese (zh_CN). This problem has been fixed.

Examples

  • Enhancements

    • The MVApp example “evaluate_ecc_200_print_quality.mvapp” has been improved. The set of images used in the example MVApp has been changed to show effects of different disturbances to the print quality measurement. The new images each contain an additional text which indicates the expected change of the print quality measurement.

Documentation

  • Fixed Problems

    • In the MERLIC manual, the information on the system requirements was not complete. The required libraries to run MERLIC Frontend on Linux systems were missing. This problem has been fixed. The list of required libraries has been updated. The libraries are described as available in the Ubuntu package manager. Please be aware that other distributions use different names for these packages.

    • In the Communication Plug-in Development manual, an example command line invocation on page “Getting Started with Plug-in Development” used the –plugin argument misleadingly. This problem has been fixed. The example usage has been changed and its behavior is now clarified.

Release Notes for Linux Systems Only

In this section, you can find the release notes that apply only for Linux systems.

  • If the recipe path in the INI configuration file wrongly pointed to a directory instead of a file, MERLIC RTE on Linux crashed. This problem has been fixed. To simplify troubleshooting, MERLIC RTE will now exit with a more descriptive message if a recipe file cannot be opened, regardless of whether it points to a file or a directory.

Known Issues

The following issue is already known and in development process. It will be fixed for upcoming releases.

  • In frequent cases, when using TensorRT™ accelerated processing units in MERLIC tools with deep learning technology, MERLIC crashes if the required memory for the deep learning model exceeds the available memory on the GPU.

  • When an instance of MERLIC Creator or MERLIC RTE of version 5.0 is remotely configured using a MERLIC RTE Setup 5.1 or newer, removing an image source from a configuration will cause the Creator or RTE application to crash. We recommend upgrading Creator/RTE to the current version or, in lieu of that, to use RTE Setup 5.0 to configure Creator/RTE 5.0.

  • When an instance of MERLIC Creator or MERLIC RTE of version 5.2 (or newer) is remotely configured using a MERLIC RTE Setup 5.1, it is not possible to rename image sources or configurations, despite the fact that this feature has been added in MERLIC 5.1. We recommend upgrading the MERLIC RTE Setup to version 5.2.

Legal Notes:

Modicon® is a registered trademark of Schneider Electric USA, Inc.

Intel, the Intel logo, OpenVINO, the OpenVINO logo, and Movidius are trademarks of Intel Corporation or its subsidiaries.

Related posts

  1. Lessons Learned from Developing Distributed Systems with Rust
  2. Comprehensive Analysis of Market Access in Saudi Arabia: What Do SABER, GCC, SFDA, and Other Certifications Mean? Part Two
  3. Updated Version of Linux Graphical Batch Operation Inspection Tool
  4. Complete Guide to Installing Nginx on Rocky Linux 9
  5. Introduction to CMake: Essential for Building Modern C++ Projects
  6. Remote Real-Time Monitoring and Rapid Dispatch Response
  7. Allwinner V853 Development Board – Building and Compiling
  8. Energy-Saving Software Development Based on FreeRTOS for Automotive Applications

Leave a Comment