MVTEC MERLIC 4.8.0标准智能图像处理软件下载 非破解版 多国语言完整版
MVTEC MERLIC 4.8.0标准智能图像处理软件下载 非破解版 多国语言完整版MVTEC公司出品Halcon同门小师弟MERLIC 4.7.0下载，本版本为非破解版，可以45天试用期。
本帖版本为4.8.0正式版。包含多国语言包。发布日期2021年6月。
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万以上。
文件名: merlic-4.8.0-windows.exe
文件大小: 701341008 字节 (668.85 MB)
修改日期: 2021-07-01 15:54
版本: 4.8.0.0
MD5: 4e1ea18098926d60d964b0689ab48be7
SHA1: cd613e9a354e6d70fd21555461b27decd5262a73
SHA256: a739012f060bddffed0b4fcffb98386d6490edce01bd07d7e83e2a5770bf2b92
CRC32: de79909e
MERLIC 4.8.0版本下载：
百度网盘下载地址：
RELEASE NOTES FOR MERLIC 4.8Here you can read the release notes for MVTec MERLIC 4.8, as released in June 2021.
CONTENTS
[*]Supported Operating Systems
[*]Major New Features
[*]Compatibility
[*]Image Source Manager
[*]Process Integration
[*]Communicator
[*]Interfaces for Process Integration
[*]Backend
[*]Designer
[*]Frontend
[*]Tools
[*]Documentation
[*]Licensing
SUPPORTED OPERATING SYSTEMSWINDOWSMERLIC 4.8.0 is still available for Windows 7 and Windows 10 (64-bit operating system). However, in future MERLIC versions only Windows 10 will be supported.During the installation, the environment variable MERLIC4EXAMPLES 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.LINUXMERLIC 4.8.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. Please contact MVTec to get more information about how to obtain this license. After the license activation, the ARM device also functions as a license dongle for the PC version of MERLIC 4.8.0, however, with some limitations.Please refer to the "Help → About" dialog in the MERLIC Backend for the respective limitations.
MAJOR NEW FEATURESNEW GUI FOR EASY CONFIGURATION OF COMMUNICATOR PLUG-INSWith MERLIC 4.8, both provided and self-developed Communicator plug-ins can be configured clearly and easily via a GUI. In the MERLIC PI Setup there is a new graphical user interface for this purpose, in which plug-in instances can be added, removed, started and stopped, and the parameters can be adjusted. In the context of easy-to-use, this simplifies and speeds up the configuration, as the editing is done directly in MERLIC. Additionally, the configuration of Communicator plug-ins can be done locally and remotely. The remote configuration greatly improves the user experience in situations where MERLIC is used on an embedded device or across physically distant computers (remote systems).EXPANDED INTEGRABILITY WITH MQTT PLUG-INWith MQTT, a new standard plug-in for IoT communication is available in MERLIC 4.8. The MQTT plug-in significantly increases the number of systems with which MERLIC can communicate out-of-the-box, whether directly via MQTT-enabled controllers or indirectly via the gateways between MQTT and various other languages and protocols. This can significantly reduce integration time and complexity. For mobile applications, free mobile clients for iOS and Android are available.COMPATIBILITYSince 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.
[*]Process Integration
[*]The command "merlic.exe --pi" is now deprecated and will no longer be available in the next major version of MERLIC. More information.
[*]Communicator
[*]The behavior of the "--plugin" flag has been slightly altered. It will no longer read plug-in configurations from the default configuration directory but implicitly create a new (default) configuration in a temporary location. To force reading an existing configuration, specify the configuration directory explicitly.
The "--plugin" option is only supported for compatibility reasons. It is recommended to use the new "Communication" tab of the MERLIC PI Setup program to manage plug-in configurations and choose which plug-ins to run. More information.
IMAGE SOURCE MANAGER
[*]Enhancements
[*]The Image Source Manager has been improved for the use of a multi-camera setup. Now, the images from all configured "Image Sources" are grabbed simultaneously.
[*]The behavior of loading ISM sources in the MERLIC Backend has been improved. Previously, when starting the MERLIC Backend, an image from all configured image sources in ISM was acquired. In case of hardware triggered cameras, loading the MERLIC Backend was blocked until a trigger was sent or a timeout occurred. Now, MERLIC does not acquire an image from hardware triggered cameras when starting the MERLIC Backend.
[*]The behavior when stopping an MVApp via the MERLIC Backend or MERLIC Frontend has been improved. Previously, MERLIC waited until the Image Source Manager finished the image acquisition before the MVApp was stopped. Thus, in the case of hardware triggered cameras, the MVApp was not stopped before either the acquisition timed out or the cameras were triggered. Now, MERLIC aborts a currently running image acquisition and stops after the current execution of the tool flow has finished.
PROCESS INTEGRATION
[*]New Features
[*]The MERLIC Process Integration Setup (MERLIC PI Setup) has been extended. It now provides a new tab "Communication" for the configuration of Communicator plug-ins. The "Communication" tab enables the user to add instances of Communicator plug-ins. These can then be configured individually in the GUI. Changes at the plug-in parameters are validated automatically as implemented for the respective Communicator plug-in. In addition, the plug-in instances can also be started and stopped in the new "Communication" tab.
The MERLIC PI Setup has also been extended by the ability to connect to a remote system. This enables the user to configure available configuration services on those systems, i.e., to configure Communicator plug-ins on the system. When starting the MERLIC PI Setup the user can choose between the local system and a remote system. If the MERLIC PI Setup is opened from the MERLIC Backend, it is automatically connected to the local system. It is also possible to switch to a different system from the MERLIC PI Setup. In case of the local system, all tabs of the MERLIC PI Setup ("Recipe Manager", "Hardware Setup", and "Communication") are available for configuration. In case of a connection to a remote system, only the "Communication" tab can be accessed, provided that a Communicator is already running on the remote system.
[*]The executable of the MERLIC PI Setup "merlic_pi_setup.exe" has been extended by the command line argument "--host". It can be used to specify the system which is ought to be configured already when starting the program.
[*]MERLIC now provides a new startup option for the MERLIC process integration. It can now be started via the executable "merlic_rte" which substitutes the command "merlic.exe --pi". In addition, the MERLIC process integration can still be started via the Windows start menu but with the new start menu entry "MERLIC RTE". Note that this change affects the compatibility. Read more.
[*]Enhancements
[*]The behavior on calling "Stop", "Reset", or "Halt" while running a "SingleJob" or "ContinuousJob" in MERLIC process integration has been improved. Previously, MERLIC waited until the Image Source Manager finished the image acquisition before the running job was finished. Thus, in case of hardware triggered cameras, the current job was not finished before either the acquisition timed out or the cameras were triggered. Now, MERLIC aborts a currently running image acquisition and then leaves the state "SingleExecution" or "ContinuousExecution", respectively, as fast as possible after performing the necessary cleanup. If MERLIC already started to process the acquired images when "Stop", "Reset", or "Halt" is requested, MERLIC still awaits until the execution of the tool flow has finished before leaving the job state.
[*]The configuration of the ports for the Communicator and the MERLIC process integration has been improved. Previously, the ports could only be set via the command line options "--command_port" and "--event_port". Now, it is possible to also set the ports in the .ini file. They can be defined in the section with the parameters "CommandPort" and "EventPort".
[*]MERLIC now provides dedicated log files for the process integration mode and the MERLIC PI Setup. They can be found in the directory "%localappdata%\MVTec\MERLIC" with the prefix "merlic_rte_" and "merlic_pi_setup_", respectively.
[*]Fixed Problems
[*]If "Reset" or "Halt" was triggered while a "SingleJob" or "ContinuousJob" was running, MERLIC first changed to the "Initialized" state while the currently prepared recipe was being unprepared and then changed to the "Preoperational" or "Halted" state, respectively. Thus, the behavior was not compliant with the "OPC UA Companion Specification Vision - Part 1" on which the framework of the internal MERLIC states is based. This problem has been fixed. MERLIC now unprepares the recipe while residing in the "SingleExecution" or "ContinuousExecution" state, respectively, and then directly changes to the "Preoperational" or "Halted" state, respectively.
[*]MERLIC leaked memory in the process integration mode if a recipe change was triggered while a Frontend with an "Image Display" widget was being connected. This problem has been fixed.
[*]If the help for the executable "merlic_pi_setup.exe" was requested via the command line option "--help", no help text was displayed. This problem has been fixed.
[*]MERLIC process integration crashed if the configuration for the process integration mode contained a MERLIC recipe path with certain non-native multibyte characters such as Chinese characters on English systems. This problem has been fixed.
COMMUNICATOR
[*]New Features
[*]The Communicator now provides dedicated log files. They can be found in the directory "%localappdata%\MVTec\MERLIC" with the prefix "communicator_". In addition, the Communicator now supports the usage of its own default .ini file called "Communicator.ini". This .ini file must be created manually in a predefined directory to ensure that it is used by default. You can define logging options for the Communicator and some additional options such as the ports, plug-in and configuration directory, and a timeout for commands.
[*]The Communicator now automatically reloads plug-in instances and their associated configurations from the specified (or implied) configuration directory. It also restarts those plug-ins which were running when the Communicator was last executed on the configuration directory. In this new mode of operation, it is no longer necessary to specify any plug-ins on the command line using the "--plugin" flag, and it is recommended to use the new "Communication" tab of the MERLIC PI Setup program instead. Note that this change affects the compatibility. Read more.
[*]Enhancements
[*]The start-up options for the MERLIC Communicator have been improved. Previously, the Communicator could only be started with a plug-in. Now, it is possible to start the Communicator without a plug-in. In the course of this, the Windows start menu entry "MERLIC Communicator OPC UA" has been replaced with "MERLIC Communicator" which now starts the Communicator without a plug-in. In addition, it is also possible to start the Communicator together with MERLIC process integration in one step from the command line using the new executable for the process integration with a command line option "--communicator", i.e., with the command "merlic_rte --communicator".
The Communicator plug-ins can now be started in the new "Communication" tab of the MERLIC PI Setup which enables the user to add new instances of a plug-in, to start and stop these instances, and to change the configuration of the plug-in instances.
[*]Fixed Problems
[*]The Communicator failed to start up altogether if any of the specified plug-ins failed to start. This problem has been fixed. If the Communicator is now started from the command line with one or multiple plug-ins and one of these plug-ins fails to start, the Communicator will continue to run and to load the other specified plug-ins. In addition, the failing plug-in will return an error that it could not be started.
INTERFACES FOR PROCESS INTEGRATION
[*]New Features
[*]MERLIC now provides a new Communicator plug-in for the communication over MQTT. It can be used to retrieve various information of MERLIC and the current application by publishing this information on the corresponding MQTT topics. This way, information about the current status of MERLIC process integration can be retrieved, e.g., its current state, the currently prepared recipe, and the currently running job. In addition, also detailed information on the available recipes, including their input and output parameters, as well as the results from completed MVApp executions can be retrieved. The "MQTT" plug-in can also be used to control MERLIC process integration as it subscribes to a dedicated MQTT topic in order to be able to publish on that topic to trigger actions. The plug-in offers a variety of configuration options via the new GUI for the plug-in configuration, i.e., the new "Communication" tab in the MERLIC PI Setup, to customize its behavior, including options to switch between preferred message formats (JSON or Plaintext), and to control the Quality of Service (QoS) settings.
[*]The simulated PLC has been extended by a new program "ContinuousJobs". During this program, the simulated PLC repeatedly runs continuous jobs for a certain amount of time. It can also be configured to alternate the recipe after a certain number of executed jobs. In addition to the new program, all parameters for the configuration of the simulated PLC in the MERLIC PI Setup have been revised.
[*]The protocols for the data exchange when using a Hilscher PCI card for the MERLIC process integration have been extended by new command codes for "SelectModeAutomatic", "StartContinuous", "Stop", "Abort", "Reset", and "Halt". The new command codes can be used to trigger the associated actions when MERLIC runs in process integration mode.
[*]The OPC UA server plug-in now supports recipes as objects in the address space. They can be accessed via the "Recipes" folder in the "RecipeManagement" object. In addition, the transition from the "Preoperational" state to "Initialized" has been fixed to be set correctly on the "StateChanged" event.
[*]Enhancements
[*]The configuration of the simulated PLC has been improved. Previously, it was required to set a default recipe to use the simulated PLC with MERLIC process integration. Now, the simulated PLC can also be used without a default recipe. In this case, the first recipe that has been selected for the parameter "RecipeList" is used. If "RecipeList" is empty, the recipe with ID=0 is used.
[*]The OPC UA server plug-in now takes advantage of the configuration validation feature. When configuring the parameters in the new "Communication" tab of the MERLIC PI Setup, the changes will be validated after saving. It will be checked if certain parameters need to be conditionally disabled depending on other parameter values. In addition, validation messages will be displayed in case of errors or warnings concerning the currently configured state.
[*]Fixed Problems
[*]If the OPC UA server plug-in was used for the process integration, the server reported error messages when entering and leaving the "FrontendAccessMode". This problem has been fixed. The "FrontendAccessMode" is now handled by a new sub-state machine that was added to the "VisionStateMachine".
[*]The OPC UA server plug-in could previously be started with the control-only access level even though the plug-in cannot be operated in a sensible manner without access to events from MERLIC. This problem has been fixed. The OPC UA server plug-in cannot be started anymore with the control-only access level, neither via the new "Communication" tab in the MERLIC PI Setup nor via the command line. If the user tries to start the plug-in from the command line with an additional flag for the access level set to "control", an error message is returned.
[*]The example Communicator plug-in "action-sender" did not accept TCP connections if the plug-in was started for a second time after being stopped. This problem has been fixed. The code of the example and the deployed plug-in binary have been adjusted. Note that this problem could not be observed in the previous version because of the startup behavior of the Communicator and the plug-ins. However, it occurs when using the "action-sender" plug-in of MERLIC 4.7.0 in combination with the new Communicator of version 4.8.0.
BACKEND
[*]New Features
[*]The MERLIC Backend now provides a new option that enables the user to visualize the tools in the Tool Flow panel and in the workspace depending on their executed state. With this option, it is easier to recognize which tools have been executed when using a "Branch on Condition" tool. It can be enabled and disabled in the MERLIC Preferences dialog at the option "Display Option > Visualize skipped tools".
[*]Improved Usability
[*]The MERLIC Backend now provides a new zooming feature in the Tool Flow panel that enables the user to zoom in and out in the Tool Flow to get a better overview, especially in large MVApps.
[*]The MERLIC Backend now provides a new menu bar button that enables the user to easily give feedback on MERLIC at the MVTec website.
[*]Fixed Problems
[*]If an additional installation of MERLIC was used and the MVApp example directory was opened via the MERLIC Backend menu "File > Open Examples", the example directory of the main installation was opened instead of the directory of the additional installation. This problem has been fixed.
[*]If the MERLIC language was set to Japanese, the font of the headings in the quick info help texts was too large. This problem has been fixed.
[*]In rare cases, MERLIC crashed if a new tool was added to an empty Tool Flow. This problem has been fxed.
[*]If more Frontends were connected to the MERLIC server than allowed, either due to license restrictions or due to the configuration in the .ini file, the MERLIC Backend did not unlock anymore after all Frontend have been closed again. In addition, the Backend still showed the message that the Frontend is connected. This problem has been fixed.
[*]The tooltips for the MERLIC tools in the Tool Library were not displayed anymore. This problem has been fixed.
DESIGNER
[*]Fixed Problems
[*]If a new MVApp was saved in the MERLIC Designer first instead of the MERLIC Backend, the MVApp was not added to the list of recently used files. This problem has been fixed.
[*]If a property of a Designer widget was misconfigured, e.g. if no tool and no parameter was selected for the "Image Display" widget, the respective property value was no longer highlighted in the property panel of the Designer. This problem has been fixed.
FRONTEND
[*]Fixed Problems
[*]In rare cases, the MERLIC Frontend crashed when loading the Frontend of a new MVApp due to a recipe change in MERLIC process integration. This problem has been fixed.
TOOLS
[*]Enhancements
[*]The tool "Image Source" has been improved. Previously, images have been displayed only after MERLIC was executed. Now, images are instantly displayed when an image source has been selected.
DOCUMENTATION
[*]New Features
[*]MERLIC now supports context-sensitive help for the following basic GUI components:
[*]MERLIC Backend
[*]Preferences Dialog in the MERLIC Backend
[*]MERLIC Designer
[*]MERLIC Frontend
[*]MERLIC Process Integration Setup (MERLIC PI Setup)
Pressing "F1" directly opens the corresponding topic in the MERLIC manual.
[*]Enhancements
[*]In the MERLIC manual, the recommendation to use only up to two cameras with MERLIC was added to some further topics to improve visibility.
[*]The documentation of the different trigger and grabbing modes for the image acquisition in MERLIC was improved. The MERLIC manual now contains a new topic "Image Acquisition Basics" that provides general information on the image acquisition in MERLIC with triggers. In addition, the topic "Image Source Manager" has been extended to provide more specific information on how to configure a camera for hardware trigger.
[*]The Communicator manual has been extended by a new topic "Getting Started to Develop Communicator Plug-ins". It provides information about the first steps to develop plug-ins and how to proceed to customize the plug-in.
[*]The Communicator API is now available in the new version 2.0.1. It has been extended by three return codes and associated error codes in the header "mv_error_def.h":
[*]MV_CODE_PLUGIN_RUNNING_STATE / MV_ERR_COMM_PLUGIN_RUNNING_STATE: A plug-in API function could not be called because it is only applicable when the plug-in is either currently running or not yet running.
[*]MV_CODE_INV_PLUGIN_ID / MV_ERR_COMM_INV_PLUGIN_ID: A plug-in could either not be registered or accessed by the plug-in manager because its ID is invalid.
[*]MV_CODE_PLUGIN_INSTANTIATION / MV_ERR_PLUGIN_INSTANTIATION: A plug-in could not be instantiated.
Additionally, the reference documentation for the existing API has been improved. In particular, it now lists the expected return codes for all functions returning MVCode_t.[*]The MERLIC manual has been extended by the new topic "Introduction" which gives an overview of all components of MERLIC and their use.
[*]The tool reference of the tools "Acquire Image from File" and "Image Source" has been improved. They now also provide information on the accepted file formats.
[*]Improved Usability
[*]The quick info of the tools "Evaluate Expression" and "Branch on Condition" has been improved. They now provide examples of various expressions for easier usability of the tools.
[*]Fixed Problems
[*]The tool references of the tools "Acquire Image from Camera" and "Image Source" contained outdated information about the system requirements for the image acquisition interfaces. It stated for all interfaces that the GenICam version 3.0.2 is required. In addition, the requirements for GigEVision2 interfaces stated that at least the version v2.1.8.0 of the GigEVision filter driver is required. However, starting with MERLIC 4.7.0 all interfaces require the GenICam version 3.3 and for GigEVision2 interfaces, at least the version v2.2.8.4 of the GigEVision filter driver is required. This problem has been fixed.
LICENSING
[*]Fixed Problems
[*]The CodeMeter runtime bundled with MERLIC had a potential denial-of-service vulnerability. This problem has been fixed with an update to version 7.21a of the CodeMeter runtime.
页:
[1]