MVTEC MERLIC 5.4.0 Linux x64-linux/aarch64-linux完整版和运行版的扩展MERLIC 5.4.0 Tools for the runtime version
MVTEC MERLIC 5.4.0 Linux x64-linux/aarch64-linux完整版和运行版的扩展MERLIC 5.4.0 Tools for the runtime version文件名: merlic-5.4.0-tools_all.tar.gz
文件大小: 1526335 字节 (1.46 MB)
修改日期: 2023-10-24 17:21
MD5: 62d0b7cbde330dc4064a82cd2555d89f
SHA1: 7c8d158de920e3dcc5f83bda1618284967539c55
SHA256: 69e3d038cd03d3ea5bc418b516bbf316194aedc263f75e50500edbb2e8eaded8
CRC32: 0499193f
百度网盘下载：
链接：https://pan.baidu.com/s/1uprpUBKeVHFwGx6q8105dA
提取码：**** Hidden Message *****
--来自百度网盘超级会员V6的分享
MERLIC 5.4 的最新功能
MERLIC 5.4 坚定追求为不断增长的新机器视觉用户市场提供易于使用的软件，集成了最新技术。为此，软件必须能够轻松融入工作流程中。
最新改动？
在全新的5.4版本中，我们将重点放在了更加轻松的流程集成上。借助全新开发的插件，MERLIC现在可以通过流行的REST接口进行操作，并且可以由Schneider Electric Modicon PLC进行控制。
MERLIC 的 REST 插件
MERLIC 5.4 使用 REST 插件扩展了可用的 MERLIC Communicator 插件。此接口打开了通往 Web 服务世界的大门。MERLIC 用户可以通过这个重要的接口来控制软件，使用Web 浏览器上的前端。此外，机器视觉应用程序的结果也可以以独立于设备的方式显示，例如在移动设备上。
MERLIC的 Modicon 插件
MERLIC 5.4中的新插件允许用户访问施耐德电气 Modicon PLC。这扩大了可以轻松集成到MERLIC 中的应用范围。例如，这种集成将使机器人和 MERLIC能够直接通过运行 Modbus 协议的 Modicon PLC 进行协作。* Modicon ® 是施耐德电气美国公司的注册商标。
采集序列
MERLIC 用户经常有机会在早期阶段测试新的开发并为进一步的进展做出贡献。在 MERLIC 5.4中，"采集序列"就是这样一个例子。这一概念功能引入了图像采集的新可能性。例如，在处理光线不足的对象时，用户现在可以采集具有短曝光时间和长曝光时间的图像，然后将它们合并成一张图像。因此，具有挑战性的对象特性得以平衡，从而提高了细节的可见性。
在 MERLIC RTE 设置中增强的图像处理
在 MERLIC 5.4中，改进了在MERLIC RTE 设置中处理图像的方式。现在可以直接将采集的图像保存到文件中。例如，这使得生成用于训练深度学习模型的图像数据集变得非常简单。
Release Notes for MERLIC 5.4
Here you can read the release notes for MVTec MERLIC 5.4, as released in October 2023.
Contents
[*]Supported Operating Systems
[*]Major New Features
[*]Compatibility
[*]Image Source Manager
[*]Process Integration
[*]Communicator
[*]Interfaces for Process Integration
[*]MERLIC Creator
[*]MERLIC Designer
[*]MERLIC Frontend
[*]Tools
[*]Examples
[*]Documentation
[*]Installation
[*]Licensing
[*]Tool Development
[*]Miscellaneous
[*]Release Notes for Windows Systems Only
[*]Known Issues
Supported Operating SystemsWindows
MERLIC 5.4.0 is available for Windows 10 (64-bit) or newer.Please refer to the "Readme" in the MERLIC manual for more information about the system requirements.Linux
MERLIC provides a test version for evaluating MERLIC RTE (Runtime Environment) for Linux on PC (Linux x86_64) and for Arm-based platforms (AArch64). This means that both embedded devices based on the widely used Arm architecture and Linux alternatives to the typical Windows operating system can now be tested for image processing with MERLIC. This is a first step towards making MERLIC available on additional platforms in the future.Developing the MVApp is still done on a Windows system with the MERLIC Creator. The application can then be tested on the "new" systems using MERLIC RTE for Arm-based platforms and Linux. Cameras can be set up remotely with the help of MERLIC RTE Setup. The test version requires a specific license. Please contact MVTec to get more information about how to obtain this license.MVTec appreciates any feedback on the test version. The feedback can be submitted on the MERLIC feedback website which can be accessed from the MERLIC Creator either via the feedback icon on the top right or via the "Help" menu.
Major New FeaturesREST Plug-in for MERLIC
MERLIC 5.4 extends the available MERLIC Communicator plug-ins with a REST plug-in. This interface opens the door to the world of web services.MERLIC users benefit from being able to control the software through this important interface, using a Frontend on the web browser. Furthermore, the results of the machine vision application can also be displayed in a device-independent manner, for example on mobile devices.Modicon®* Plug-in for MERLIC
A new plug-in in MERLIC 5.4 allows users to access the Schneider Electric Modicon PLC ®. This broadens the range of applications that can be easily integrated with MERLIC. For instance, this integration would enable robots and MERLIC to collaborate directly using a Modicon PLC ® that operates on the Modbus protocol.* Modicon® is a registered trademark of Schneider Electric USA, Inc.Acquisition Sequences
MERLIC users regularly have the opportunity to test new developments at an early stage and to contribute to further advancements. In MERLIC 5.4 this is the case with "Acquisition Sequences". This concept feature introduces new possibilities for image acquisition. For instance, when dealing with a poorly lit object, users can now acquire images with both short and long exposure times, which are then merged into a single image. As a result, challenging object characteristics are balanced, resulting in improved visibility of details.Enhanced Image Handling in the MERLIC RTE Setup
In MERLIC 5.4 working with images in the MERLIC RTE Setup has been improved. It is now possible to save acquired images directly to a file. This makes generating image datasets for training deep learning models very easy, for example.Compatibility
Since the last MERLIC version we have been working hard to improve MERLIC in every way. This has, however, resulted in a few of incompatibilities. We apologize for the inconvenience.
[*]Communicator
[*]The Communicator API has been updated to version 2.2.1. Plug-ins build against a previous version of the Communicator API 2.x.y remain source- and binary-compatible to the present version of MERLIC Communicator. Plug-ins build against the present version of the Communicator API remain binary-compatible to MERLIC Communicator 5.2 and 5.3 (API version 2.2.0) but should expect that the new features in the API version 2.2.1 are not available in previous versions. More information.
[*]Miscellaneous
[*]Due to the new underlying HALCON version, the behavior of existing custom tools might have changed since the last MERLIC version. Therefore, it is recommended to check the functionality of existing custom tools in this MERLIC version. More information.
Image Source Manager
[*]New Features
[*]The list of camera parameters and EasyParams provided for the configuration of camera devices in the "Image Sources" tab of the MERLIC RTE Setup has been extended to allow the user to query the internal name of a camera parameter or EasyParam. Each camera parameter and EasyParam now provides a new context menu when right-clicking on the respective parameter. The context menu allows the user to copy the internal name of the respective camera parameter or EasyParm.
[*]The configuration of image sources via the Image Source Manager (ISM) has been improved. When configuring a camera device in the "Image Sources" tab of the MERLIC RTE Setup, it is now possible to save the snapshot of the acquired image that is displayed in the image preview. The snapshot can be saved via the new "Save image" button on the bottom right of the image preview. This allows the user to save a series of images from a camera device on the local system. These images can be used for the development of a MERLIC Vision App (MVApp) and many other purposes.
[*]Enhancements
[*]The image preview of the Image Source Manager (ISM) in the "Image Sources" tab of the MERLIC RTE Setup has been improved. Previously, zooming of the currently displayed image was only possible for image sources representing camera devices. In addition, when zooming the image, a new image was acquired from the camera device. Now, zooming does not trigger the acquisition of new images anymore and it is now also possible to zoom the images from file.
[*]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:
[*]GigEVision2: Revision 20.11.16
[*]GenICamGenTL: Revision 20.11.16
[*]USB3Vision: Revision 20.11.19
[*]File: Revision 18.11.5
In addition, the GigEVision2 streaming filter has been released in a new revision. MERLIC now contains the version 2.2.8.4-1 of the streaming filter.[*]The configuration of image sources via the Image Source Manager (ISM) has been improved. Previously, the user did not get any feedback if the active configuration could not be used for running jobs in MERLIC RTE. The "Image Sources" tab of the MERLIC RTE Setup now displays a warning if the active configuration contains image sources that could not be connected to warn the user that this configuration cannot be used for running jobs in MERLIC RTE.
[*]Fixed Problems
[*]When renaming an image source in the MERLIC RTE Setup and trying to set the mouse cursor at the beginning of the original name, the edit mode was terminated and the image source name was still unchanged. This problem has been fixed.
[*]When configuring camera devices on the "Image Sources" tab of the MERLIC RTE Setup and switching from the "EasyParams" tab to the "All Parameters" tab, the collapsing state of the list in the "All Parameters" tab was not preserved. In addition, the collapsing state was also not preserved when refreshing the parameter list in the "All Parameters" tab. These problems have been fixed.
[*]When using the live image mode in the "Image Source" tab of the MERLIC RTE Setup and pressing CTRL to activate the pan mode on a zoomed image, the mouse cursor did not change to reflect this mode. This problem has been fixed.
[*]If the name of an image source was changed in the "Image Sources" tab of the MERLIC RTE Setup, the live image of other image sources did not work anymore. This problem has been fixed.
Process Integration
[*]Enhancements
[*]In networks where DNS resolutions take more than 5 seconds, it was not possible to connect the MERLIC RTE Setup to a remote host. This problem has been fixed.
[*]Fixed Problems
[*]In the "Communication" tab of the MERLIC RTE Setup, the values of plug-in parameters were sometimes elided if the respective text field was not in focus. This problem has been fixed.
[*]If an image tool result was used as an MVApp result for MERLIC RTE but the associated image was empty, for example, because the name of the respective image source was invalid, MERLIC RTE did not emit a "ResultReady" event for the whole result record. Therefore, no results were available at all for Communicator plug-ins, including MVApp results of other data types. This problem has been fixed. Now, the "ResultReady" event is emitted but the data component descriptor corresponding to the empty image has dimensions of 0 by 0 pixels.
[*]When configuring user parameters of Communicator plug-ins in the MERLIC RTE Setup, information about unsaved changes was sometimes lost if parameters with dependencies to other parameters were adjusted. This problem has been fixed.
[*]When running MERLIC RTE with a recipe that contained at least one MVApp parameter, MERLIC RTE sometimes stopped responding after some time. This problem has been fixed.
Communicator
[*]Enhancements
[*]The Communicator API has been updated to version 2.2.1. It extends the information associated with the "JobStarted" event by the ID of the recipe that is being executed, the type of job (single vs. continuous job), and the start parameters used to execute the job. It also allows to query the name of the acquisition sequence associated with a recipe, provided an acquisition sequence has been set for the recipe. Both of these extensions are also reflected in the C++ support library.
To profit from these improvements, the Communicator plug-in "MQTT" has been updated to version 2.3.0. The JSON payload published on the "<prefix>/recipes" topic has been extended by the names of the acquisition sequences associated with each recipe. The documented JSON schema has been updated accordingly. In addition, the example plug-in "event-logger" has been updated to version 2.0.1. It will now print the additional information that are available as part of the "JobStarted" event. Note that this change affects the compatibility. Read more.
Interfaces for Process Integration
[*]New Features
[*]MERLIC has been extended by the new Communicator plug-in "MODICON". It enables the user to communicate directly with Schneider-Electric's programmable controllers of the MODICON® Series and allows the user to control and monitor the vision system in the process integration mode. For the communication between the "MODICON" plug-in and the Schneider-Electric Modicon® PLC, the Modbus communication protocol is used.
The plug-in offers a rich set of configuration options in the "Communication" tab of the MERLIC RTE Setup, for example, plug-in parameters to set the connection settings to the PLC, to select the number of MVApp results that shall be available to be queried by the PLC, as well as the number of iteration parameters that shall be available for the PLC to overwrite the parameter values defined in the recipe. After configuring the plug-in, the user may export the symbols of the selected MVApp parameters and results and import the exported file into the PLC program. The imported symbols can then be accessed by both the plug-in and the PLC to transmit commands, results, and further information.
[*]The MERLIC Communicator plug-in "MELSEC_Communicaton" now also supports the communication with Mitsubishi Electric PLCs of the MELSEC iQ-F and iQ-R series in addition to the MELSEC-L and MELSEC-Q series.
Furthermore, the plug-in now supports the label format for GxWorks3. For this, the plug-in has been extended by the new user parameters "Environment" and "Locale". They are provided in the category "Global Label CSV Export". The parameter "Environment" can be used to select the GxWorks version and the parameter "Locale" can be used to select between "English" and "Japanese". This enables the user to export the global label file in a compatible format for the respective PLC IDE.
[*]MERLIC now provides the new Communicator plug-in "REST". It exposes a subset of the Communicator's C API in the form of a RESTful API which is served on an embedded HTTP server. This allows the user to create an application-specific frontend and to control MERLIC RTE by using the available endpoints of the RESTful API.
The REST plug-in itself provides a built-in example web application that allows the user to explore the MERLIC RTE state machine and monitor recipe results directly from a web browser. It also enables an interactive documentation of the RESTful API. For this, only a MERLIC installation and a web browser are required.
[*]Fixed Problems
[*]The "MELSEC_Communication" plug-in received invalid responses when using a recipe that defined iteration parameters requiring more than 250 words of PLC memory for a given data type. This problem has been fixed.
[*]When using the "MELSEC_Communication" plug-in and the field "gMV_ReqCommandCode" was set to an invalid command code value in the plug-in, this code was mirrored on the field "gMV_AckCommandCode" without any other side effects. In particular, no indication was given to the PLC that the command code is invalid, likely pointing to a user error. This problem has been fixed. Now, an error occurs indicating that the requested action is unknown.
MERLIC Creator
[*]New Features
[*]The MERLIC Creator now allows adding new MERLIC tools directly from the "Tool Flow" panel. For this, the context menu of the "Tool Flow" panel has been extended by the menu entry "Insert tool" which allows the user to browse the available tools without switching to the Tool Library.
[*]Enhancements
[*]The graphical user interface of the preference dialog in the MERLIC Creator has been revised to fit the look and feel of other components of MERLIC and to allow more flexible user controls.
[*]MERLIC now provides the possibility to inspect the values of tool parameters and tool results directly at the Tool Board. When hovering the mouse pointer over the connector of the tool parameter or result, the respective values will be shown in a tooltip. For tuples, even the number of tuple elements as well as the minimum and maximum value are shown. This is especially useful if the parameter or result contains multiple values that are not visible in the respective connector.
[*]Improved Usability
[*]The usability of navigating through the Tool Library has been improved. Previously, tool categories and tools could only be selected via mouse clicks. Now, it is possible to use keyboard shortcuts to navigate through the Tool Library and to add the selected tool to the Tool Flow.
ACTIONKEYBOARD SHORTCUT
Moving up and down the Tool LibraryUp/down arrow keys
Expanding and collapsing tool categoriesRight/left arrow keys or Enter
Switching to the search field of the Tool LibraryEsc or Up arrow key
Adding the selected toolEnter or Space
[*]When using MERLIC Creator in Chinese or Japanese, texts that are displayed in vertical directions are now written from top to bottom instead of bottom-to-top rotated by 90 degrees.
[*]Fixed Problems
[*]While dragging a tab header in the MERLIC Creator, the text within the header was sometimes not positioned correctly. This problem has been fixed.
[*]If a custom tool was selected in the Tool Library, opening the context-sensitive help via "F1" did not work. In addition, when using "F1" in the "Custom Tools" tab of the preferences dialog in the MERLIC Creator, the context-sensitive help opened a wrong section in the MERLIC manual. These problems have been fixed. Pressing "F1" in the Tool Library when a custom tool is selected will now open the documentation of the Tool Library and pressing "F1" in the "Custom Tools" tab of the MERLIC preferences will open the description of the available settings for custom tools.
[*]In some cases, the tool flow visualized wrong connections that led to no tools. This could lead to unexpected connections in the Tool Flow panel. This problem has been fixed.
[*]In rare cases, MERLIC crashed when using the keyboard shortcut CTRL+U to ungroup a tool group in the Tool Flow panel of the MERLIC Creator. This problem has been fixed.
[*]When adding multiple training images to a training tool and immediately trying to group tools multiple times in the Tool Flow panel while the process of adding the training images has not finished yet, MERLIC Creator crashed. This problem has been fixed.
[*]In the Tool Library of the MERLIC Creator, the tool category "Communication (legacy)" was translated without the "legacy" add-on. This problem has been fixed.
[*]If a tool was moved and then immediately de-selected or moved again in the Tool Flow panel, MERLIC sometimes crashed. This problem has been fixed.
[*]When starting the MERLIC Creator using a trial license, the dialog informing about the modalities of the trial version could only be accepted after closing the start dialog. This problem has been fixed.
[*]The texts for "Acquisition Time" and "Total Acquisition Time" that are displayed in the status bar of the MERLIC Creator when using the "Image Source" tool were not translated. This problem has been fixed.
[*]The MERLIC Creator refused to start up if an invalid directory was configured in the "Tool paths" or "Additional procedure paths" settings for custom tools. This problem has been fixed. Now, MERLIC Creator displays an error message but continues starting up.
MERLIC Designer
[*]Fixed Problems
[*]In rare cases, MERLIC crashed when adding the "Image Display" widget very quickly via drag-and-drop.
MERLIC Frontend
[*]Fixed Problems
[*]If the "Image Display" widget in the MERLIC Frontend showed editable ROIs and the connected tool supported easyTouch, the ROIs were not displayed anymore as soon as the easyTouch functionality had been activated. This problem has been fixed. The ROIs will now be displayed in read-only mode when easyTouch is active.
[*]If the MERLIC Frontend provided multiple tabs with different views and one of these tabs contained a "Training" widget, the MERLIC Frontend crashed when switching between the tabs. This problem has been fixed.
Tools
[*]New Features
[*]The tools "Find Objects" and "Read Text and Numbers with Deep Learning" have been improved for the usage with AI2 interfaces for the NVIDIA® TensorRT™ SDK and the Intel® Distribution of OpenVINO™ toolkit.
Previously, the deep learning model of the "Find Objects" tool was created anew each time the following parameters for the model were changed after the optimization:
[*]Minimum Confidence
[*]Overlap of Different Classes
[*]Overlap of Same Classes
Now, these parameters can be changed without performing the model optimization anew which leads to faster processing of the parameter changes.
In addition, in the tool "Read Text and Numbers with Deep Learning", the following tool parameters were previously set to read-only after the optimization.
[*]Automatic Detection Of Orientation
[*]Detection Orientation
[*]Detection Tiling
[*]Minimum Character Detection Score
[*]Minimum Word Connection Score
[*]Minimum Word Score
Now, these parameters can also be changed after the optimization without changing the selected processing unit first.[*]The "Image Source" tool now allows the user to quickly access the configuration of the image sources directly from the Tool Board. For this, a new button has been added on the left of the Tool Board to open the "Image Sources" tab of the MERLIC RTE Setup.
In addition, the tool now also provides feedback if a warning occurs because no image could be received. A warning text will be displayed with specific information on the possible cause together with a button to open the image source configuration. This way, the user can quickly access the configuration to fix the problem.
[*]The tool "Read Text and Numbers with Deep Learning" has been extended by the new tool parameter "Detection Model File". It allows the user to select which of the provided detection models shall be used, that is, which Deep OCR model component shall be used for the word detection. Currently, two pre-trained detection models can be selected, "pretrained_deep_ocr_detection.hdl" and pretrained_deep_ocr_detection_compact.hdl". However, you can also use your own detection model.
[*]Fixed Problems
[*]If the tool "Find Objects" used a deep learning model that was trained with images of a smaller dimension than the one of the images that were used in the tool for the processing, the scaling of the X and Y coordinates, the regions, and the contours did not work as expected. This led to wrong result values and to a wrong visualization of the results. This problem has been fixed.
Examples
[*]Fixed Problems
[*]The example MVApp "check_bent_leads.mvapp" contained some wrong configuration. The expression defined in the "Evaluate Expression" tool is meant to change the format of the "Maximum Distance" value to show three digits after the comma. However, it was not set correctly and therefore changed the format to show only three digits overall. In addition, the "Label" Designer widget showing the value of the maximum distance was incorrectly connected to the unformatted result instead of the formatted value returned by the "Evaluate Expression" tool. This problem has been fixed. In addition, the "Evaluate Expression" has been renamed in the example MVApp to "Create Maximum Distance Parameter" to better reflect the purpose of the tool in the application.
[*]In the MVApp example "find_and_count_screw_types.mvapp", some screws were not correctly identified. This problem has been fixed. The deep learning model was trained anew and the classes representing nuts were removed from the example.
Documentation
[*]New Features
[*]The documentation of the user interfaces in the MERLIC manual has been improved. Previously, the user interfaces of the MERLIC RTE Setup and the MERLIC Frontend were not described in the MERLIC manual. Now, the description has been added to the overview of the user interfaces in the "Getting Started" chapter as well as in the "MERLIC Process Integration" chapter and "MERLIC Frontend" chapter, respectively.
[*]The information about the used third-party components provided in the "About" dialog of the MERLIC Creator now contains hyperlinks to the respective project websites to allow quick access to the used components.
[*]Enhancements
[*]The layout of several overview topics in the MERLIC manual has been improved. Previously, the overview topics of the chapters "MERLIC Creator", "MERLIC Designer", and "MERLIC Frontend" still had an outdated layout. Now, all overview topics use the same layout.
[*]The layout of the MERLIC manual, the MERLIC Communicator manual, and the Tool Development manual have been improved for responsive design. Previously, the settings of the table of contents and the toolbar icons on the top right were not optimized for smaller browser widths which led to overlapping content. In addition, the table of contents switched to the right side in tablet and mobile mode. Now, the width of the table of contents adjusts according to the browser width and it is always accessible on the left. Furthermore, the menu bar with the toolbar icons has been revised to avoid overlapping content and to ensure a correct alignment of the icons in all modes.
[*]The documentation of the "MELSEC_Communication" plug-in in the MERLIC Communicator manual has been improved. The description of the available commands now also provides a link to the description of the available MERLIC states and transition in the MERLIC manual.
[*]Fixed Problems
[*]The visualization of some graphics showing the MERLIC states and processes during the process integration mode has been improved. Previously, the font in the graphics was small and it could be hard to read the text in the image, especially when the graphics were scaled on a small browser width. Now, the graphics have been revised to use a bigger font and to allow the user to enlarge the image to better see the content.
[*]In the topic "Standard Plug-ins > OPC UA Server Plug-in > Operating the OPC UA Server > Available Methods" in the MERLIC Communicator manual, the table showing the available methods for the respective MERLIC states was cut off for browser widths below 1300px. This problem has been fixed. The table is now resized for browser widths between 800px to 1350px.
[*]In the German MERLIC manual, the tiles in the topic "Erste Schritte mit MERLIC > MERLIC Komponenten" were cut off if the width of the browser was lower than 1250px. This problem has been fixed.
[*]In some cases, images showing numbers as overlays were not displayed correctly in the MERLIC manuals when scrolling down the page. This problem has been fixed.
[*]In the MERLIC manual, the description of the tool state result "info" with code 99 was missing in the topic "MERLIC Creator > MERLIC Creator Concepts > Error Handling > Tool State Result". In addition, the description of the respective interface procedure "Me_set_toolstate_info" that can be used for the development of custom MERLIC tools was missing in the Tool Development manual. These problems have been fixed.
Installation
[*]New Features
[*]The options for the installation of MERLIC via the MVTec Software Manager (SOM) have been extended. To profit from these improvements, it is required to use the new SOM version 1.4 for the installation. With the new version, it is now possible to choose between multiple MERLIC "packages" for the installation. This allows the user to install only selected MERLIC components, for example, the MERLIC Frontend, instead of a full MERLIC installation.
In addition, MERLIC comes with some new options for multiple MERLIC installations. The new version of SOM allows to "activate" a MERLIC installation. If multiple MERLIC versions are installed, the user can activate the desired installation to associate the MERLIC files such as MVApps to the respective version. When double-clicking on an MVApp in the file browser, it will be automatically opened in the associated MERLIC version. However, it is still possible to open an MVApp in a different MERLIC version by using the context menu of the MVApp. It now provides clear menu entries to choose the desired MERLIC version.
Moreover, it is now possible to open all manuals directly from the SOM frontend.
Licensing
[*]New Features
[*]The behavior on how to check whether the license restrictions for image acquisition are met have been changed. Previously, the number of acquisition tools "Image Source" and "Acquire Image from Camera" that were allowed per MVApp was determined by the used MERLIC license. If multiple "Image Source" tools were used in an MVApp to retrieve images from the same image source, it was not possible to use a MERLIC license that allows the use of only one image source because the number of tools were decisive for the license and not the number of used image sources. Now, the license restricts only the number of used camera devices. In detail, the new license restrictions are as follows:
[*]When using the Image Source Manager (ISM), the MERLIC license restricts the number of camera devices in the active image source configuration. The number of camera devices in inactive image source configuration is not restricted. As a consequence, image source configurations which contains more camera devices that allowed by the license cannot be activated. However, the number of images sources from file is not restricted.
[*]When using the deprecated acquisition tools, the MERLIC license restricts the number of "Acquire Image from Camera" tools per MVApp. The number of "Acquire Image from File" tools is not restricted.
[*]It is not permitted to acquire images using both Image Source Manager (ISM) and the deprecated tool "Acquire Image from Camera" within one and the same MVApp.
Tool Development
[*]Fixed Problems
[*]When hovering the mouse pointer over an image result of a custom tool, MERLIC could crash if the result was not assigned to a valid image object in the main procedure of the tool. This problem has been fixed.
Miscellaneous
[*]To profit from the improvements of the new HALCON version, the HALCON libraries used by MERLIC have been upgraded to the HALCON 23.05 Progress version.Note that this change affects the compatibility. Read more.
[*]The recipe files as well as the configuration files for image source configurations and Communicator plug-ins created by MERLIC are defined in JSON format. However, the newline character at the end of the files were missing. This problem has been fixed.
[*]The "MERLIC Collect Support Information" program failed to create a .zip file if the configuration directory "%APPDATA%\MVTec" was missing. This problem has been fixed.
Release Notes for Windows Systems Only
In this section, you can find the release notes that apply only for Windows systems.
[*]On some machines with an Intel UHD Graphics 620 graphics card, the MERLIC Creator showed no content. Instead, the window was completely black. This problem has been fixed.
[*]If non-ASCII characters were used in the name of an image source configuration in the "Image Sources" tab of the MERLIC RTE Setup, MERLIC Creator and MERLIC RTE could crash on startup depending on the selected Windows system locale. This problem has been fixed.
[*]MERLIC Vision Apps could not be overwritten anymore if the path of the %TEMP% or %TMP% folders contained any non-ASCII characters. This problem has been fixed.
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 to upgrade 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.
页:
[1]