MVTEC MERLIC4.4.0标准智能图像处理软件下载 非破解版 多国语言完整版

石鑫华视觉

MVTEC MERLIC4.4.0标准智能图像处理软件下载 非破解版 多国语言完整版


MVTEC公司出品Halcon同门小师弟MERLIC4.4.0下载，本版本为非破解版，可以在MVTEC公司官网申请45天试用期（自MERLIC4.2版本起已经取消了网络激活功能，改用本地试用的方试，会更方便一点）。

本帖版本为4.4.0正式版。包含多国语言包。发布日期2020.3.12。

PS：2019.3.1，经验证，确实已经取消了网络激活方式，变成了本地验证45天。这个45天是写死的。也就是试用期最大不能大于45天，但是可以通过改系统时间的方式，只要在安装日期后的45天内，都可以试用。如2019年3月1号安装，那么只要将系统时间修改为2019.3.1~2019.4.14之间，都是可以试用的。如果使用日期已经超过45天试用期，则提示试用许可过期。如果改前旧日期距离安装日期大于45天的，则试用校验失败，提示加密错误，不能正常使用。

MERLIC为一款标准的智能软件，不需要太多编程知识，只需要拖动需要的功能模块，组成一定的工作流程，配置一下参数，完成配方配置，即可应用于机器视觉领域。同时MERLIC优化并行处理功能，可匹配多相机的工位应用。再加上其基于Halcon的底层，图像检测功能是非常优秀的。不过相对较贵的价格，2万+的人民币，一般个人可能承受不起。如有需要，可联系我方论坛购买大恒Pallas智星智能相机的批量许可证版本的MERLIC，该版本是大恒批发的MERLIC，绑定了大恒的PALLAS智星智能相机，即只能使用PALLAS智能相机（现阶段有两款带MERLIC软件的型号可选择，一个是全局的130万相机的PALLAS 6513M-M0（MERLIC全功能版），另一款为行曝光630万像素的PALLAS 6563M-M0（MERLIC全功能版），其它的相机如大恒水星MER、火星MARS、Basler、AVT等品牌的相机，都不支持。两款智能相机带MERLIC软件，2万以内可以拿下，详情可联系我方。如需要支持其它非PALLAS的工业相机的MERLIC，可购买独立版本的，价格2万以上。

MERLIC4.4.0版本下载：

链接: https://pan.baidu.com/s/1T4xYH6QVzahCr_g9rz4-Lg

提取码:

游客，如果您要查看本帖隐藏内容请回复

Release Notes for MERLIC 4.4

Here you can read the release notes for MVTec MERLIC 4.4, as released in March 2020. It contains information about new functionality and fixed bugs since MERLIC 4.1.

Contents

• Supported Operating Systems
• Major New Features
• Backend
• Designer
• Frontend
• Tools
• Process Integration
• Documentation
• Installation
• Miscellaneous
  

Supported Operating SystemsWindows

MERLIC 4.4.0 is available for Windows 7 and Windows 10 (64-bit operating system).

During the installation, the environment variable MERLICEXAMPLES is set to C:\Users\Public\Documents\MVTec\MERLIC 4 by default. It contains the path to the directory in which additional files such as example applications or images are installed.

Please refer to the "Readme" in the MERLIC manual for more information about the system requirements.

Linux

MERLIC 4.4.0 is available for selected Linux ARM 64-bit platforms. This edition requires a specific license that needs to be activated on the ARM device. After the license activation, the ARM device also functions as a license dongle for the PC version of MERLIC 4.4.0, however, with some limitations.

Please refer to the "Help → About" dialog in the MERLIC Backend for the respective limitations.

Major New FeaturesProcess Integration with Digital I/O Communication

MERLIC 4.4.0 is providing communication via digital I/O interfaces supporting Advantech, NIDAQmx, and Contec cards. In addition, the new version enables cameras to communicate via GenICam digital I/O control.

Greatly improved recipe management

The newly designed Recipe Manager helps to keep the overview of the used recipes and to organize them for the production line thanks to the easy-to-use graphical user interface.

Backend

• Enhancements
  • The scaling of the MERLIC Backend, Designer, and Frontend has been improved. Previously, GUI elements, e.g., fonts, icons, or arrows, were scaled differently when running MERLIC on high-DPI screens such as Microsoft Surface. Now, MERLIC scales correctly when running on screens with high resolutions.
  • The startup behavior of the MERLIC Backend has been improved. Previously, the MERLIC Backend did not start but raised an error message in case the underlying configuration for MERLIC process integration contained errors. Now, the MERLIC Backend starts without error messages. A possible misconfiguration of the MERLIC process integration can be seen and investigated inside the new "MVTec MERLIC Process Integration Setup" which can be opened via the MERLIC Backend or as stand-alone application.
  • The minimal window size of MERLIC has been revised. Previously, the MERLIC Backend, MERLIC Designer, and the user management dialog were available in different minimal window sizes. Especially, the minimal size of the MERLIC Designer was too small to be applicable. Now, the minimal window size has been unified for the Backend, Designer, and the user management dialog to 1024x786.
    
  
  
  

• Improved Usability
  • The search functionality of the Tool Library in the MERLIC Backend has been improved. Previously, the search bar became only visible via a click on the search icon. In addition, by clicking on the close icon the search bar was closed instead of clearing the search text. Now, the search bar is placed on top of the Tool Library panel and is always visible and the close icon now clears the search text.
  • The naming convention of input and output parameters that can be used for the communication during the MERLIC process integration has been revised and unified. Previously, they were named "interface parameters". Now, these parameters have been renamed to "MVApp parameters" and "MVApp results".
    
  
  
  

• Fixed Problems
  • In some cases, long tool error messages were not completely visible in the message box of MERLIC tools. This problem has been fixed.
  • When closing the MERLIC Backend, pending user actions, e.g., save on exit, were discarded under certain circumstances. This problem has been fixed.
  • In some cases, the MERLIC Frontend restored settings in the .ini file that have been changed by the MERLIC Backend and vice versa. This problem has been fixed.
  • If the .ini file contained erroneous entries or caused validation errors, the MERLIC Backend did not start anymore. This problem has been fixed.
  • MERLIC could not be started if the "Maximum size of log files" was set very high in the MERLIC preferences. This problem has been fixed. The "Maximum size of log files" is now limited to a maximum value of 1024 MB.
    
  
  
  

Designer

• Improved Usability
  • The menu icon for the MERLIC Designer has been revised. It has been redesigned to fit to the design of the new "MVTec MERLIC Process Integration Setup".
    
  
  
  

• Fixed Problems
  • If a Designer widget was connected to a tool parameter or tool result and the respective tool was then deleted in the Backend, the connection between the widget and the tool parameter or result was lost. A generic error message was shown that did not mention the actual problem and the respective combo boxes "Connected Tool" and "Connected Parameter" were empty instead of indicating that no tool or tool parameter is connected. This problem has been fixed. Now, a widget instantly shows the info that no tool or parameter is connected and no error message is displayed.
  • If a widget in the MERLIC Designer was connected to a tool parameter with tuple type "long", the respective parameter value was sometimes not displayed correctly and could not be edited in the Frontend. This problem has been fixed.
  • If the "Table" widget was configured in the MERLIC Designer by selecting multiple table cells at once and adjusting a widget property such as the colors, previously defined cell texts have been deleted. This problem has been fixed. In addition, the configuration of multiple table cells is now restricted to properties that do not represent the cell texts.
  • If MERLIC was set to a language other than English, the "Action" property of the "Dialog Button" widget showed an empty combo box in the Designer instead of the view selection. This problem has been fixed.
    
  
  
  

Frontend

• Enhancements
  • The usage of the MERLIC Frontend during MERLIC process integration has been improved. Now, the user can use the new Designer widget "Write Access" to activate the write mode in the Frontend for modifying parameters and saving the MERLIC Vision App. When write access is granted to the MERLIC Frontend, the internal state of MERLIC process integration changes to "Manual" and the currently connected communication device or control system is no longer allowed to trigger commands for the execution of the MVApp or to prepare a recipe.
    
  
  
  

• Fixed Problems
  • When displaying a multi-valued parameter in a table in the MERLIC Frontend, the first value was not shown but the last value of the parameter was shown twice instead. This problem has been fixed.
  • The menu entries and dialog texts within the MERLIC Frontend were always shown in English even if a different language was selected. This problem has been fixed.
  • If the Designer widget "Label" or a cell of the "Table" widget was connected to a tool result that might contain an empty tuple, e.g., the result "Decoded Data" of the tool "Read Bar Code", the respective text field still showed the result of the previous MVApp execution in the Frontend if the execution resulted in an empty tuple, e.g., if no bar code was visible in the image. This problem has been fixed. The text will now be set to an empty string if the connected tool result contains an empty tuple.
    
  
  
  

Tools

• Enhancements
  • The tool "Acquire Image from Camera" has been revised. It is now possible to achieve higher frame rates for cameras that support GenICam SFNC-conform software trigger. With this change, it is no longer possible to configure these cameras to be triggered by hardware.
    
  
  
  

• Fixed Problems
  • When trying to select a calibration plate descriptor file in the tool "Calibrate Camera", the file selection dialog automatically filtered for image files instead of files with file ending ".cpd". This problem has been fixed.
  • The tool "Measure Opposite Edges" did not respect connected calibration data when calculating the angle between opposite edges. This problem has been fixed.
  • In case of communication issues when using the tools "Read from Serial Interface", "Write to Serial Interface", "Read from Socket", or "Write to Socket", the respective tool state was set only for some of the tools. This problem has been fixed. The tool state is now set consistently for all of these tools.
  • To open a socket connection the maximum timeout was used. This increased the loading time for MERLIC Vision Apps that contains the tools "Read from Socket" or "Write from Socket". This problem has been fixed. Now, the read/write timeout that is specified in these tools is also used for opening the socket connection. In addition, the default timeout has been adjusted to 0.5 seconds and the maximum value has been changed to 10 seconds.
    
  
  
  

Process Integration

• New Features
  • MERLIC has been extended by the new application "MVTec MERLIC Process Integration Setup" (MERLIC PI Setup) that provides a graphical user interface for the configuration of the MERLIC process integration mode. It is provided as a stand-alone software that can be opened from the MERLIC Backend or with the respective executable file without starting the MERLIC Backend.
    The MERLIC PI Setup is divided in two configuration areas: the "Recipe Manager" and the "Hardware Setup". The "Recipe Manager" enables the user to import and check existing MERLIC recipe files whereas the "Hardware Setup" enables the user to select and configure the communication device that is used for the process integration of MERLIC.
    
  
  
  

• Fixed Problems
  • When MERLIC was started via command line with the option --ini and a file with the wrong file type was defined for the --ini option, e.g., an MVApp file instead of a .ini file, the content of the specified file has been changed. This problem has been fixed. Now, the file is not overwritten anymore if a wrong file type is specified. Instead, MERLIC is started with the default settings.
  • The "Interface Parameters" panel in the MERLIC Backend displayed the position ID of the respective interface parameters two times instead of only once. In addition, the position was counted beginning from 1. This problem has been fixed. The numbering has been unified with the numbering in the new "MVTec MERLIC Process Integration Setup" and now starts with the ID 0. The visualization of the position ID has been fixed in the course of renaming the panel to "MVApp Parameters and Results".
  • In rare cases, MERLIC hanged if it was running in process integration mode with the simulated PLC, i.e., no further executions were triggered. This problem has been fixed.
  • In some cases, the preamble byte sent by the PLC was ignored by MERLIC in process integration mode. If the preamble byte was set to a wrong value, the command was still executed. This problem has been fixed. Now, messages with a wrong preamble byte are ignored and commands will not be executed.
    
  
  
  

Documentation

• Enhancements
  • The documentation of several tools has been improved. The quick info and tool references of the tools of the category "Combined Measuring" have been extended to be more clear. In addition, also the quick info of further tools has been extended to describe more clearly how to use the tools.
  • The documentation of the tools in the category "Reading" has been improved. The respective tool references have been extended by a description how the training is performed.
  • The documentation of the tools "Read from File" and "Write from File" has been improved. It has been extended by a description on how to finish the writing mode and close a file.
  • The MERLIC manual has been improved. Images and videos have been revised and are now displayed with a simplified user interface to provide a clear look and focus the user's attention on the features to be shown in the images and videos.
    
  
  
  

• Fixed Problems
  • The documentation of the logging mechanism of MERLIC contained an example in which the log file size was set to 100 bytes. However, this was misleading because MERLIC ignores values less than 1 MB. This problem has been fixed. The example now uses an appropriate log file size.
  • The tool reference of the tool "Write to File" contained wrong information about how the file is opened for writing. This problem has been fixed.
    
  
  
  

Installation

• New Features
  • MERLIC has been extended to provide a new entry for the MERLIC Frontend in the Windows start menu in addition to the new "MVTec MERLIC Process Integration Setup".
    
  
  
  

• Fixed Problems
  • After installing MERLIC, the language of the MERLIC Backend was set to English even if a different language was selected during the installation process. This problem has been fixed.
    
  
  
  

Miscellaneous

• If comments were added in the MERLIC configuration file (.ini file), these comments were deleted as soon as the settings have been overwritten due to adjustments from the MERLIC GUI. This problem has been fixed. Now, the comment lines starting with "#" or ";" are not removed anymore from the configuration file.
• The loading time for MERLIC Vision Apps has been improved. Especially, large MVApps and those without complex tool connections and trainings are loaded significantly faster.
• The configuration of MERLIC via the .ini file has been improved. MERLIC now uses the new .ini file "MERLIC4.ini" to enable separate settings for different major versions. Previously, the settings in the .ini file were applied for all MERLIC instances of all major version. Now, the new .ini file is applied only for the respective major version. When MERLIC is installed on a system that contains only a "MERLIC.ini" and no "MELRIC4.ini" yet, the settings in the "MERLIC.ini" will be automatically converted to the new "MERLIC4.ini".
  

---

Release Notes for MERLIC 4.3.0
MERLIC 4.3版未下载到本地，网络上没有相应的软件可供下载。如真的需要这个版本，则只能买正版，但是就算是购买正版，仍然建议使用4.4版，功能更强、性能更稳定、问题更少。

This document provides the release notes for MVTec MERLIC 4.3.0, as released in August 2019.

Contents

• Backend
• Tools
• Documentation
• Installation
• Licensing
• Miscellaneous
  

Backend

• Fixed Problems
  • Error dialogs that were shown during the startup of MERLIC were not visible because they were hidden by the splash screen. This problem has been fixed.
  • The menu of the MERLIC Backend was disabled when pressing the keyboard shortcut ALT+Tab while the mouse cursor hovered over the image of the tool board. This problem has been fixed.
  • When moving the mouse cursor over the image in the tool board while pressing the keyboard shortcut ALT, the image coordinates and gray values of the respective pixel are shown. However, if the mouse cursor was moved, the displayed values were truncated and not readable anymore. This problem has been fixed.
  • When changing the value of image specific training parameters, such as "Sample Type" in the tool "Check Presence with Gray Features", the respective value was highlighted in the wrong font size. This problem has been fixed.
  • If a tool parameter name has been renamed to an HTML code instead of a text, the HTML code was accepted as parameter name, parsed, and rendered. This problem has been fixed.
  • If a tool with multiple connections to subsequent tools was displayed in the tool workspace, the text of the drop area for new tool connections was hidden by the labels of the connected tools. This problem has been fixed.
  • If a tool parameter with a predefined list of values was adjusted, the combo box with the value list was only opened after a second click on the respective connector instead on the first click. This problem has been fixed.
    
  
  
  

Tools

• New Features
  • The path settings for the tools of the category "File Access" have been improved. Previously, the tools used paths that were relative to the working directory. Now, relative paths refer to the directory "%USERPROFILE%/Documents". Furthermore, the "File Name" parameter of these tools are now set to an absolute path by default and it is now possible to use "/" as well as "\" as path separators.
    
  
  
  

• Fixed Problems
  • In some cases, the tool "Detect Scratches" threw an error message that too many scratches were found right after inserting the tool. This problem has been fixed. Now, the tool shows a warning which gives more detailed information about the number of found scratches and the allowed maximum number of scratches for the respective image size.
  • If the ALT key was pressed while moving the mouse cursor over the image in the tool "Invert Gray Values", the respective information about the gray value and the coordinates of the original image were displayed instead of the pixel information of the inverted image that is displayed in the tool. This problem has been fixed.
  • Each time the tool "Level Surface" was added to an MVApp, an error message was written to the log file. This problem has been fixed.
    
  
  
  

Documentation

• Enhancements
  • The information about the system requirements of MERLIC have been improved. They are now more clear on which operating systems are supported. In addition, they have been extended by a link to the system requirements of the supported image acquisition interfaces to provide an easy access to the respective information.
    
  
  
  

• Fixed Problems
  • Some screenshots in the MERLIC manual were not up to date. This problem has been fixed.
    
  
  
  

Installation

• Fixed Problems
  • In some cases, the display of the installer option to install the MVTec GigEVision streaming filter was broken. This problem has been fixed. This option is now displayed on two separate pages instead of one single page.
  • If the MERLIC setup was executed on a system with an installed MVTec GigEVision streaming filter, the respective files of the streaming filter were deleted when deselecting the option to install the streaming filter during the MERLIC setup. This problem has been fixed.
    
  
  
  

Licensing

• New Features
  • MERLIC 4.3.0 is now available as a new edition for selected Linux ARM 64-bit platforms. This edition requires a specific license that needs to be activated on the ARM device. After the license activation, the ARM device also functions as a license dongle for the PC version of MERLIC 4.3.0, however, with some limitations. Please refer to the "Help → About" dialog in the MERLIC Backend for the respective limitations.
    
  
  
  

Miscellaneous

• The MERLIC configuration settings in the .ini file have been improved. Previously, paths needed to be given with double backslashes "\" as path separator. Now, it is possible to also use to regular slashes "/" and backslashes "\" as path separators in the .ini file. In addition, the [ProcessIntegration] setting "RecipeCount" has been removed.
• In some cases, settings with language-specific characters in the .ini configuration file could not be read correctly. This problem has been fixed. Note that the .ini file requires an UTF8 character encoding on all platforms.
  

woshigaowei5146

学习一下

lcz

下来看看，研究研究。。。。