Skip to content

Release notes for HALCON🔗

More Info

See also the release notes for HDevelopEVO.

The latest version HALCON 26.11.1.0 was released in November 2026.

Major new features of HALCON 26.11.1.0🔗

AI object detection enhancements and more efficient edge inference🔗

HALCON 26.11 expands its AI object detection with oriented bounding boxes, enabling more precise localization of rotated, elongated, or closely spaced objects. By representing an object’s orientation in addition to its position and size, oriented bounding boxes reduce irrelevant background and enable orientation-aware evaluation.

Per-class confidence thresholds provide further control by allowing users to adjust the balance between detection rates and false positives individually for each object class.

For edge deployment, the new ONNX Runtime AI² interface enables more efficient deep learning inference on Linux-based edge devices using the 64-bit Arm architecture.

Automatic contour optimization for slightly deformable objects🔗

HALCON 26.11 extends automatic contour optimization to slightly deformable objects. This makes it easier to create robust Shape Matching models for real-world parts that slightly differ in every image. For example, metal or plastic components may vary slightly because of production tolerances, perspective effects, or minor deformations.

Previously, such variations could limit automatic contour optimization and require users to disable it, manually edit model contours, or carefully select training images with minimal geometric differences. HALCON 26.11 can now account for expected local shape variations while identifying and removing genuinely unstable contours. Using multiple representative training images, users can create compact and robust models with less manual contour editing and apply automatic contour optimization to a broader range of real-world matching tasks.

More flexible and robust 3D processing🔗

HALCON 26.11 simplifies common 3D vision tasks and delivers more reliable results from real-world data. When fitting geometric shapes, users can now incorporate known object properties such as size or orientation. This helps reduce ambiguities, for example when objects are only partially visible or measurement data contains noise.

Additional improvements make everyday 3D processing workflows easier to handle. A new operator simplifies the calculation of intersections between lines and planes. HALCON 26.11 also preserves neighborhood information when sampling XYZ-mapped 3D data, provides more consistent handling of XYZ mappings when object models are merged, and gives users greater control over surface-normal calculation.

Supporting manufacturers with EU Cyber Resilience Act requirements🔗

Cybersecurity and regulatory compliance are increasingly important throughout the lifecycle of connected products. With HALCON 26.11, MVTec strengthens the processes supporting vulnerability handling and security updates.

Together with the Software Bills of Materials already provided for HALCON, these measures give customers transparent information about included software components and a clearer basis for addressing security issues. This helps manufacturers assess dependencies, maintain their products, and prepare relevant documentation with less effort.
HALCON thus supports manufacturers in addressing EU Cyber Resilience Act requirements, while responsibility for assessing the compliance of the complete final product remains with its manufacturer.


Changelog🔗

Compatibility🔗

Licenses🔗

All HALCON 26.05 Progress licenses or licenses of earlier versions must be replaced or upgraded. Please contact your local sales partner. HALCON 26.11.1.0 Progress-Steady licenses will be downwards compatible to HALCON 26.05 Progress.

Hlib🔗

Compared to HALCON 26.05 Progress, many extensions have been introduced. Thus, the HALCON 26.11.1.0 Progress-Steady libraries are not binary compatible with HALCON 26.05 Progress or earlier versions.
However, HALCON 26.11.1.0 Progress-Steady is mostly source-code compatible to HALCON 26.05 Progress except for the changes listed below:

  • Some OBJ files previously written by HALCON were not valid OBJ files. The meshes’ vertex normals are lost when reading OBJ files written by previous versions of HALCON.
    More information

  • The default memory allocator on Windows systems is no longer mimalloc, but the system allocator. This is the same behavior as on Linux systems. You can use set_system('memory_allocator', 'mimalloc'), to re-enable the mimalloc allocator.
    More information

  • The Postscript window type has been removed.

    The fallback mode that allowed HALCON to open windows with reduced functionality if the hcanvas library could not be loaded has been removed.
    More information

  • In very rare cases, a bug fix in an internal function can change the behavior of multiple operators, including but not limited to gen_region_polygon_filled and gray_inside.
    More information

  • Due to a code refactoring, extension packages using the functions HRLClip2, HRLRelClip, or HRLClip are no longer source-code compatible and must be adapted.
    More information

  • uncalibrated_photometric_stereo now raises an error if ResultType is not set to ‘all’.
    More information

  • sample_object_model_3d with Method set to ‘xyz_mapping’ or ‘xyz_mapping_compute_normals’ now stores a zoomed, dense output XYZ mapping and does not copy sparse values from the input XYZ mapping anymore.
    More information

  • union_object_model_3d for Method set to ‘points_surface’ does not return mappings anymore. If mappings are wanted for further processing, please set Method to ‘points_surface_single_viewpoint’.
    More information

  • In previous versions, tuple_rand(0) threw an error. Starting with HALCON 26.11, it returns an empty tuple instead.
    More information

Legacy notes🔗

The following functionality may be discontinued in a future major release or has been removed with this release. See the operator reference entries of legacy operators for details on how to replace them.

  • The following deprecated operators have been removed from HALCON:

    disp_lut, get_fixed_lut, get_lut_style, set_fixed_lut, set_lut_style, write_lut, open_textwindow, clear_rectangle, move_rectangle, slide_image, disp_distribution, get_tshape, query_tshape, set_tshape, get_comprise, set_comprise, get_fix, set_fix, set_line_approx, get_line_approx, get_pixel, set_pixel

  • The PostScript window type has been removed.

    The fallback mode that allowed HALCON to open windows with reduced functionality if the hcanvas library could not be loaded has been removed.
    This change affects the compatibility (read more).

  • The following legacy operators have been removed from HALCON (Legacy/Matching, Component-Based):
    clear_all_component_models, clear_all_training_components, clear_component_model, clear_training_components, cluster_model_components, create_component_model, create_trained_component_model, deserialize_component_model, deserialize_training_components, find_component_model, gen_initial_components, get_component_model_params, get_component_model_tree, get_component_relations, get_found_component_model, get_training_components, inspect_clustered_components, modify_component_relations, read_component_model, read_training_components, serialize_component_model, serialize_training_components, train_model_components, write_component_model, write_training_components

    The following classes have been removed from HALCON:
    HComponentModel, HComponentTraining

  • The support for the 32‑bit HALCON Variable Inspect Visual Studio Extension has been removed. Please switch to the 64‑bit versions of Microsoft Visual Studio 2022 or 2026.

  • Official support for Visual Studio 2013 has been discontinued. Please use Visual Studio 2017 or later for compiling HALCON applications.
    You will still need Visual Studio 2022 or later to use the HALCON Variable Inspect Visual Studio Extension as announced separately.


Cybersecurity🔗

The following issues are relevant in the context of cybersecurity. Note that not all of them are necessarily security vulnerabilities.

  • Internal security checks identified the security vulnerability CVE-2021-4048. The vulnerability concerns the CLARRV, DLARRV, SLARRV, and ZLARRV functions in lapack. HALCON does neither ship nor use these functions. Exploitation in the context of HALCON is therefore not possible and the CVE is not applicable for our product.

  • The third-party library libpng has been updated to 1.6.59. This fixes the security vulnerability CVE-2026-46675.

  • The third-party library Apache Thrift has been updated to version 0.25.0 to fix several security vulnerabilities.

  • The third-party library OpenSSL has been updated to version 3.5.9. This fixes numerous security vulnerabilities.

  • Internal security checks identified the security vulnerability CVE-2026-85091 (third-party library zlib). This vulnerability does not apply to HALCON, as the vulnerable APIs are not used in HALCON.

  • Internal security checks identified the security vulnerabilities CVE-2026-89157, CVE-2026-89161, CVE-2026-89158, CVE-2026-89160, and CVE-2026-89156. The vulnerabilities concern specific functions and settings of the pcre2 library. These functions and settings are not used and the CVEs are not applicable to our product and do not affect HALCON.

  • The third-party library libxml2 has been updated to version 2.15.4. This fixes the security vulnerabilities CVE-2026-86137, CVE-2026-86138, CVE-2026-86139, CVE-2026-86140, CVE-2026-86141, CVE-2026-86142, CVE-2026-86143, and CVE-2026-86144.

  • Internal security checks identified the security vulnerability CVE-2026-63632. While this CVE is not applicable to our product and has never affected HALCON, it has also been addressed by updating the ONNX third-party library to version 1.22.0, which is no longer affected by it.

  • HALCON now uses version 8.41a of the CodeMeter Runtime. This update fixes security vulnerabilities in CodeMeter Runtime.

  • The third-party library Apache Thrift has been updated to version 0.24.0 to provide a fix for CVE-2026-55971, CVE-2026-58662, CVE-2026-48145, CVE-2026-48586, CVE-2026-55969, and CVE-2026-55970. This library is used for the communication between HDevelop and HDevEngine during remote debugging. HALCON applications that do not use HDevEngine are unaffected.

    HDevEngine production applications that run without enabling the debug server are also unaffected. If the debug server was enabled, exploiting potential vulnerabilities required malicious third-party software to be able to open a socket connection to the host/port combination configured for remote debugging.

    Another path to exploiting potential vulnerabilities was to trick an HDevelop user into initiating a remote debugging connection to a malicious third-party server.

  • The third-party library GenApi has been updated to version 3.5.1. This fixes various security vulnerabilities by updating the third-party library Expat to version 2.8.1.

  • Internal security checks identified the security vulnerability CVE-2026-44512. This vulnerability could cause an unrecoverable denial of service when processing an untrusted model. While this CVE is not applicable to our product and has never affected HALCON, it has also been adressed by updating the ONNX third-party library to version 1.22.0, which is no longer affected by it.

  • The third-party library libxml2 has been updated to version 2.15.3. This fixes the security vulnerability CVE-2026-6732.

  • The third-party library thrift has been updated to version 0.23.0. This fixes the security vulnerabilities CVE-2026-41636, CVE-2026-41604, CVE-2025-48431, CVE-2026-41602, CVE-2026-41605, CVE-2026-41603, CVE-2026-41607, CVE-2026-41606, CVE-2026-43870, CVE-2026-43869, CVE-2026-43868.

  • The third-party library libtiff has been updated to version 4.7.2. This fixes the security vulnerability CVE-2026-4775.

  • Internal security checks identified the security vulnerabilities CVE-2026-27489, CVE-2026-34447, CVE-2026-34446. These vulnerabilities concern path traversal vulnerabilities in ONNX. These vulnerabilities have been addressed by updating the ONNX third-party library to version 1.22.0, which is no longer affected by them.

    Internal security checks identified the security vulnerability CVE-2026-34445. The vulnerability concerns the ONNX Python interface, which is not being used. While this CVE is not applicable to our product and has never affected HALCON, it has also been addressed by updating the ONNX third-party library to version 1.22.0, which is no longer affected by it.


HDevelop🔗

New functionality🔗

IDE🔗
  • HDevelop now sends the cross-product UUID, fetched from somctl, when checking for updates and the like.
Language🔗
  • In HDevelop, accessing a dictionary key after a tuple index operation (such as MyDicts[2].my_key) for either reading or writing did not work. This problem has been fixed. Expressions of such a form are now valid.

Bug fixes🔗

Miscellaneous🔗
  • In some cases, HDevelop crashed when selecting “Discard” in the “New Program” dialog. This problem has been fixed.

  • The third-party library Apache Thrift has been updated to version 0.24.0 to provide a fix for CVE-2026-55971, CVE-2026-58662, CVE-2026-48145, CVE-2026-48586, CVE-2026-55969, and CVE-2026-55970. This library is used for the communication between HDevelop and HDevEngine during remote debugging. HALCON applications that do not use HDevEngine are unaffected.

    HDevEngine production applications that run without enabling the debug server are also unaffected. If the debug server was enabled, exploiting potential vulnerabilities required malicious third-party software to be able to open a socket connection to the host/port combination configured for remote debugging.

    Another path to exploiting potential vulnerabilities was to trick an HDevelop user into initiating a remote debugging connection to a malicious third-party server.

  • Dragging files like 3D models into HDevelop could create a line of code that led to parser errors. This problem has been fixed.

  • HDevelop did not detect an update. This problem has been fixed.

Example programs🔗

New example programs🔗
  • hdevelop/3D-Matching/Deep-3D-Matching/deep_3d_matching_data_generation.hdev

  • hdevelop/3D-Matching/Deep-3D-Matching/deep_3d_matching_training_workflow.hdev

  • hdevelop/3D-Matching/Deep-3D-Matching/find_symmetries_object_model_3d.hdev

  • hdevelop/3D-Object-Model/Transformations/intersect_line_plane_object_model_3d.hdev

  • hdevelop/Deep-Learning/Augmentation/dl_transform_pipeline.hdev

  • hdevelop/Deep-Learning/Classification/continual_learning_for_classification.hdev

  • hdevelop/Deep-Learning/Classification/continual_learning_for_classification_on_edge_device.hdev

  • hdevelop/Deep-Learning/Detection/dl_advanced_detection_with_orientation_workflow.hdev

  • hdevelop/Deep-Learning/Detection/dl_advanced_detection_workflow.hdev

  • hdevelop/Deep-Learning/Detection/dl_detection_inference_yolo.hdev

  • hdevelop/Filters/Color/analyze_pills_hyperspectral_canonical_variates.hdev

  • hdevelop/Filters/Color/smooth_hyperspectral_images.hdev

  • hdevelop/Identification/Data-Code/ecc200_deep_learning_detection.hdev

  • hdevelop/ImageSource/image_source_chunks.hdev

  • hdevelop/ImageSource/image_source_configuration_file.hdev

  • hdevelop/ImageSource/image_source_create.hdev

  • hdevelop/ImageSource/image_source_frame_rate.hdev

  • hdevelop/ImageSource/image_source_information.hdev

  • hdevelop/ImageSource/image_source_modules.hdev

  • hdevelop/ImageSource/image_source_parameters.hdev

  • hdevelop/ImageSource/image_source_parameters_persistence.hdev

  • hdevelop/ImageSource/image_source_pixel_format.hdev

  • hdevelop/ImageSource/image_source_plugin_path.hdev

  • hdevelop/ImageSource/image_source_query_devices.hdev

  • hdevelop/ImageSource/image_source_query_plugins.hdev

  • hdevelop/ImageSource/image_source_simple.hdev

  • hdevelop/ImageSource/image_source_trigger_hardware.hdev

  • hdevelop/ImageSource/image_source_trigger_software.hdev

  • hdevelop/ImageSource/image_source_trigger_software_multithread.hdev

  • hdevelop/Matching/Shape-Based/get_generic_shape_model_result_score_visualization_contours.hdev

  • hdevelop/Matching/Shape-Based/train_generic_shape_model_contour_pruning_workflow.hdev

  • hdevelop/Transformations/2D-Transformations/gen_image_warp_map.hdev

Bug Fixes🔗
  • When multiple TensorRT AI² devices were available, the example hdevelop/Deep-Learning/AnomalyDetection/dl_anomaly_detection_global_context_inference.hdev ran into an error. This problem has been fixed, the example now consistently selects the first device for inference.

  • The visualization in the HDevelop example program hdevelop/3D-Matching/Deep-3D-Matching/deep_3d_matching_workflow.hdev did not work correctly for cameras of different sizes, or when only one camera was used. This problem has been fixed.


HLib🔗

New functionality🔗

3D🔗
  • The example hdevelop/3D-Matching/Deep-3D-Matching/deep_3d_matching_training_workflow.hdev now uses advanced object detection. The model match_bitholder.dm3 used by deep_3d_matching_workflow.hdev has been adapted accordingly. The automatic augmentation of (typically synthetically generated) training samples for detector models retrieved from a Deep 3D Matching model has been adapted.

  • surface_normals_object_model_3d has been extended with a GenParamName ‘xyz_mapping_mask_size’ to adjust the width and height of the used neighborhood for speed.
    smooth_object_model_3d has accordingly been extended with a GenParamName ‘xyz_mapping_compute_normals_mask_size’.

  • The content of the result handles of deformable surface matching, i.e., of semantic type ‘deformable_surface_matching_result’, was not visible in the handle inspect windows. This has been improved. The content of such handles can now be inspected in handle inspect windows.

  • HALCON has been extended with an operator intersect_line_plane_object_model_3d that calculates the intersection point of a line and a plane.
    The new HDevelop example program hdevelop/3D-Object-Model/Transformations/intersect_line_plane_object_model_3d.hdev shows how to use this operator.

  • HALCON has been extended with an operator find_symmetries_object_model_3d that can analyze a 3D object model and determine its symmetric properties.
    The new HDevelop example program hdevelop/3D-Matching/Deep-3D-Matching/find_symmetries_object_model_3d.hdev shows how to use the operator to find symmetries and visualize them.

  • sample_object_model_3d with Method set to ‘xyz_mapping’ or ‘xyz_mapping_compute_normals’ has been improved so that a dense XYZ mapping is available in output for further processing.
    This change affects the compatibility (read more).

  • union_object_model_3d has been extended with a new Method ‘points_surface_single_viewpoint’, which checks mappings for consistency before returning their combination.
    This change affects the compatibility (read more).

  • fit_primitives_object_model_3d has been extended with new GenParamNames to specify parameters that are assumed to be known and are not changed during the fitting process, namely ‘cylinder_axis_dir’, ‘cylinder_axis_point’, ‘cylinder_radius’, ‘plane_normal’, ‘plane_point’, ‘sphere_center’, ‘sphere_radius’.

    fit_primitives_object_model_3d is now faster by up to 20% in case that several types of primitives are fitted.

Deep learning🔗
  • HALCON has been extended with a new AI Accelerator Interface (AI²) featuring the ONNX Runtime.
    In this release, the plugin enables optimized CPU inference through the ONNX Runtime CPU Execution Provider.
    The AI² can be installed using the MVTec Software Manager and is supported on the following platforms:
    x64-win64, x64-linux, aarch64-linux

    The plugin is documented online at https://docs.mvtec.com. The documentation features a description of the new plugin, including installation, configuration, and usage instructions.

    A new HDevelop example, hdevelop/Deep-Learning/AI2Interfaces/run_deep_ocr_on_onnxruntime_cpu_ep.hdev, demonstrates how to perform deep learning inference, such as Deep OCR, using the ONNX Runtime AI² CPU Execution Provider.

    These operators have been extended to support the new AI² interface:
    query_available_dl_devices, optimize_dl_model_for_inference, get_dl_device_param, set_dl_device_param

  • transform_dl_sample_batch is now parallelized on batch item level.

  • The cross entropy loss layer now supports soft targets in the form of class probability vectors.

  • HALCON’s deep-learning-based advanced object detection has been extended with oriented object-detection to locate instances of oriented objects in an image.

    Advanced object detection for oriented instances comes with three pretrained models:

    • pretrained_dl_detection_rectangle2_small.hdl
    • pretrained_dl_detection_rectangle2_medium.hdl
    • pretrained_dl_detection_rectangle2_large.hdl

    This new approach is significantly faster than the previous one on both GPU and CPU runtimes as well as on AI² interfaces. The new anchor-free network architecture is easier to use because no anchor parameters have to be tuned.
    Further, the new models shows superior precision and recall on testing datasets due to an improved network architecture and a pretraining on a large-scale dataset.

    This update replaces the previous object detection for oriented bounding box prediction. Now, creating object detection models with create_dl_model_detection is no longer needed for rectangle2 instances.

    The HDevelop example hdevelop/Deep-Learning/Detection/dl_advanced_object_detection_with_orientation_workflow.hdev has been added to demonstrate how to use advanced object detection for oriented instances in HALCON.

  • When optimizing deep learning models for TensorRT devices, now the hardware_compatibility_level parameter is available.

  • query_available_dl_devices reported unsupported TensorRT GPU devices with compute capability lower than 7.5 for the AI² TensorRT plugins 25.11.1 and 25.11.2. This problem has been fixed with the AI² TensorRT plugin 25.11.3 and newer.

  • HALCON’s advanced object detection has been extended to support class specific minimum confidence thresholds at inference.
    For advanced object detection during inference, proposals with confidence scores below min_confidence are discarded. Models now support class-specific values of min_confidence, allowing the confidence threshold to be configured independently for each class.

    Suggestions for minimum confidence thresholds can be calculated from the validation split of the dataset with the new procedure determine_dl_model_detection_confidence_thresholds.

    The HDevelop examples for advanced object detection now demonstrate the necessary configuration to use class-specific min_confidence values. The HDevelop examples for advanced object detection also offer the possibility to visualize precision and recall values for different minimum confidence values.

  • The Deep OCR detection component now has an improved orientation estimation, resulting in more accurate bounding boxes.

Identification > General🔗
  • For the print quality assessment of direct part marked Data Matrix ECC 200 symbols (ISO/IEC 29158 standard), the new set_data_code_2d_param parameter 'quality_isoiec29158_decode_algorithm' has been introduced. This parameter offers the possibility to switch between a 'robust' and a 'reference' implementation. While the 'robust' mode represents the previous HALCON implementation, the new 'reference' mode is strictly following the reference decode algorithm described in ISO/IEC 16022, including the adaptations of ISO/IEC 29158. The latter is intended for grading with a standard-compliant camera and lighting setup.

    The new mode uses the so-called dot connecting algorithm described in Annex C of  ISO/IEC 29158 to ensure continuous edges even for dot peen symbols, where the reference decode algorithm would fail otherwise. If the dot connecting algorithm led to the best grades, the user will be notified by a value ‘true', available via get_data_code_2d_results and the parameter 'quality_isoiec29158' or 'quality_isoiec29158_values'. The corresponding name of the new entry is called 'Dot connecting algorithm used' and can be queried via 'quality_isoiec29158_labels' as usual.

    The following examples have been adapted to use the new 'reference' mode:

    • hdevelop/Identification/Data-Code/calibration_isoiec29158.hdev
    • hdevelop/Identification/Data-Code/print_quality_isoiec29158.hdev

    Minor additional changes: The “Solution Guide II-C 2D Codes” mentions the new parameter 'Dot connecting algorithm used'. Furthermore, the reference decode algorithm as a whole has been partly reworked. These changes can lead to slight differences in the grading not only for ISO/IEC 29158 but also for ISO/IEC 15415 following the reference decode algorithm (see the parameter 'quality_isoiec15415_decode_algorithm'). The overall runtime of the reference decode algorithm has been improved as well.

Identification > Bar code🔗
  • find_bar_code in conjunction with the parameter ‘composite_code’ set to ‘CC-A/B’ allowed to decode composite symbols of the GS1 DataBar family. Now, the barcode types EAN-8, EAN-13, UPC-A, UPC-E, and GS1-128 support composite structures of type A and B as well.

  • The bar code reader has been improved for GS1 DataBar Omnidir, GS1 DataBar Truncated, GS1 DataBar Limited, and GS1 DataBar Expanded codes with composite component. The composite part can now be detected more robustly.

Identification > 2D code🔗
  • The training mode of the operator find_data_code_2d has been improved. Now, training calls require less memory. This improvement does not change the results of the training.

  • HALCON’s DataMatrix reader is now more robust on codes with perspective distortion. The parameter ‘alternating_pattern_tolerance’ toggles this improved functionality. If this parameter is set to ‘high’, the improved functionality is used. For the settings ‘low’ and ‘medium’, the behaviour is not changed.

  • HALCON’s Data Matrix reader is now more robust on deformed codes, especially on codes with multiple data regions and dot printed codes.

  • The ‘robust’ decoding algorithm used in ISO/IEC 15415 and ISO/IEC 29158 print quality inspection of Data Matrix codes has been improved. Especially the boundary of the symbol is now detected more robustly to achieve more accurate grades.
    This might lead to slightly different grades compared to earlier versions. However, the overall grading is more robust with these improvements.

    Further, the determination of the position of the non-data module centers of Data Matrix codes in ISO/IEC 15415 and ISO/IEC 29158 print quality inspection has been adapted to be in line with the new 2024 revision of ISO/IEC 16022.

  • The QR code reader is now more robust with branded codes.

  • HALCON’s DataMatrix reader is now more robust when multiple codes are positioned very close to each other in an image.

  • The Data Matrix, QR Code, and DotCode reader now require less memory. The reduction depends on the parameter setting and is highest with standard_recognition and without parallelization. The memory requirements for symbol_search=rudimental have not been changed.
    The performance of these readers slightly improves in these situations as well. In best cases, the QR Code reader is 10 percent faster.

  • The Data Matrix reader has been extended with AI-based candidate detection. This enables a more robust detection of codes in challenging environments, such as low contrast or nearby clutter.
    To activate this feature, the 'detection_method' parameter must be set to 'deep_learning' when creating the Data Matrix reader handle using create_data_code_2d_model. Otherwise, the default 'classic' rule-based method will be used.

    The pretrained model pretrained_data_matrix_detection.hdl included with HALCON uses tiling by default and can be further optimized using AI² interfaces.

    The minimum confidence for Data Matrix code candidates can be set with the new parameter ‘detection_min_confidence’ or trained with the existing training mechanism in find_data_code_2d.

    A new example has been added showing the workflow with AI-based Data Matrix detection:
    hdevelop/Identification/Data-Code/ecc200_deep_learning_detection.hdev
    For this example, the new images images/datacode/ecc200/ecc200_dongle_01.png to images/datacode/ecc200/ecc200_dongle_08.png have been added.

  • The reference decode algorithm of the Data Matrix ECC 200 usable by setting the set_data_code_2d_param parameters 'quality_isoiec15415_decode_algorithm' or 'quality_isoiec29158_decode_algorithm' to 'reference' has been updated to follow the newest revision (see ISO/IEC 16022:2024). The changes made can lead to different grading results.

Graphics🔗
  • HALCON has been extended with the operator open_runtime_window. It opens a new graphics window and makes open_window more extensible by using a dictionary as input. HDevelopEVO extends the functionality of the operator to arrange graphic windows in the IDE. Hence, open_runtime_window serves as the common ground for managing graphics windows in HALCON applications, which facilitates re-use and export of HALCON scripts written with HDevelopEVO.

  • The Postscript window type is no longer supported and has been removed.
    This change affects the compatibility (read more).

Image🔗
Matching🔗
  • HALCON shape-based matching now supports the use of ‘max_deformation’ during contour pruning.

    This enhancement extends the Automatic Contour Optimization workflow to applications where objects show moderate geometric deviations between the template and the training samples. As a result, contour pruning can create robust matching models even when sample images contain manufacturing tolerances, perspective effects, or small object deformations.

    To use this feature, set the ‘max_deformation’ parameter with set_generic_shape_model_param before training. No additional training parameters are required and the existing contour pruning workflow remains unchanged. The contour pruning algorithm now takes the specified deformation tolerance into account when finding the model on the provided samples. This allows stable contour information to be identified more reliably while still removing unstable contour parts.

    The result is a contour-pruned model even for slightly deformed objects, reducing manual contour editing effort and extending the applicability of Automatic Contour Optimization to a wider range of applications.

  • find_shape_model, find_shape_models, find_scaled_shape_model, find_scaled_shape_models, find_aniso_shape_model, find_aniso_shape_models, and find_generic_shape_model differed in the evaluation of match candidates during tracking for different simd implementations. Now their results deviate less.

Transformation🔗
  • affine_trans_image, affine_trans_image_size, zoom_image_factor (if ScaleWidth and ScaleHeight are not exactly 0.5), zoom_image_size (if the output image size is not half the input image size), rotate_image (for angles not multiples of 90 degrees), and crop_rectangle2 with AlignToAxis set to ‘true’ with system parameter ‘int_zooming’ set to ‘true’ for interpolation ‘bilinear’, ‘constant’, ‘weighted’ for images of type ‘uint2’ and ‘real’ and ‘bicubic’ for images of type ‘real’ have been accelerated on Arm 64-bit processors that support the NEON instruction set. A speedup of up to 40% can be expected for images of type ‘uint2’ and up to 55% for images of type ‘real’.

    The same holds for gen_gauss_pyramid using interpolation ‘constant’ and ‘weighted’ for images of type ‘uint2’ and ‘real’, when the Scale is not exactly 0.5.

Tuple🔗
  • tuple_rand(0) will now return an empty tuple instead of throwing an error.
    This change affects the compatibility (read more).
Miscellaneous🔗
  • The default memory allocator on Windows systems is no longer mimalloc, but the system allocator. This is the same behavior as on Linux systems.
    This change affects the compatibility (read more).

Speedups🔗

  • The mean_image filter is now faster by up to 5% for int2 and int4 images on Linux and up to 8% on Windows platforms.

  • affine_trans_image, affine_trans_image_size, zoom_image_factor (if ScaleWidth and ScaleHeight are not exactly 0.5), zoom_image_size (if the output image size is not half the input image size), rotate_image (for angles not multiples of 90 degrees), and crop_rectangle2 with AlignToAxis set to ‘true’ with system parameter ‘int_zooming’ set to ‘true’ for interpolation ‘bilinear’, ‘constant’, ‘weighted’ for images of type ‘uint2’ and ‘real’ and ‘bicubic’ for images of type ‘real’ have been accelerated on Arm 64-bit processors that support the NEON instruction set. A speedup of up to 40% can be expected for images of type ‘uint2’ and up to 55% for images of type ‘real’.

    The same holds for gen_gauss_pyramid using interpolation ‘constant’ and ‘weighted’ for images of type ‘uint2’ and ‘real’, when the Scale is not exactly 0.5.

  • abs_diff_image was slower when NEON optimizations have been enabled using set_system (‘neon_enable’, ‘true’) which is the default.

    Now, the faster code is used, resulting in a speedup compared to the default by up to 20%.

Bug fixes🔗

3D🔗
  • find_surface_model, find_surface_model_image, refine_surface_model_pose, and refine_surface_model_pose_image with ‘pose_ref_use_scene_normals’=’true’ did not differentiate enough between normals pointing in opposite directions in pose refinement. This problem has been fixed.

  • preprocess_dl_samples and preprocess_dl_model_3d_data returned faulty normals when XYZ maps contained NaN values. This problem has been fixed. Now, pixels with NaN values are excluded from the normals calculation.

  • distance_object_model_3d with ‘store_closest_index’=’true’ and ‘distance_to’=’triangles’ returned an incorrect closest index if ObjectModel3DTo contained triangles and the attribute ‘&original_indices’, but no polygons. This occurred when ObjectModel3DTo was processed with triangulate_object_model_3d ‘polygon_triangulation’ or created by read_object_model_3d from an .obj file with ‘convert_to_triangles’=’true’. This problem has been fixed. Now, triangle indices are returned.

  • When reading and writing OBJ files with read_object_model_3d and write_object_model_3d, point normals were not correctly handled when the file contained triangles or polygons. This problem has been fixed. Triangles and polygons now have the correct per-point attributes. The ability to import pure point cloud data (no lines or faces) with normals is unaffected.
    Additionally, read_object_model_3d and write_object_model_3d for OBJ files have been extended to support reading and writing of line data as well as per-vertex texture coordinates.
    This change affects the compatibility (read more).

  • The accuracy of poses detected and refined with Deep 3D Matching, i.e., with the operator apply_deep_matching_3d, has been improved.

  • connection_object_model_3d sometimes did not raise errors or did not unlock models in error cases and might have crashed in rare cases. This problem has been fixed.

  • fit_primitives_object_model_3d and segment_object_model_3d in rare cases may have crashed or returned no result. This problem has been fixed.

  • project_object_model_3d in rare cases created artifacts and did not return all expected contours for telecentric camera parameters and ‘hidden_surface_removal’ set to ‘true’. This problem has been fixed.

  • dev_display_dl_data did not display the text ‘gripping_map’. dev_display_dl_3d_data did not display ‘gripping_point_cloud’. These problems have been fixed.

  • read_object_model_3d may have crashed for large PCD files. This problem has been fixed.

  • When rerunning deep_3d_matching_training_workflow.hdev or resuming an existing training, preprocess_dl_dataset unnecessarily reprocessed the complete dataset instead of reusing existing preprocessed data. This problem has been fixed. Existing preprocessed data is now reused if the dataset and preprocessing configuration have not changed.

  • triangulate_object_model_3d with ‘Method’ set to ‘greedy’ crashed in very rare cases. This problem has been fixed.

  • uncalibrated_photometric_stereo did not check the input parameter ResultType. This problem has been fixed. Now, only ResultType ‘all’ is supported.
    This change affects the compatibility (read more).

Deep learning🔗
  • Reading ONNX models with read_dl_model failed if the ONNX model contained operations where the axis specification was negative and the input node of the operation had rank < 4. This problem has been fixed.

  • The procedure calculate_dl_segmentation_class_weights incorrectly returned an error if the parameter IgnoreClassIDs contained IDs that did not belong to DLDataset.class_ids. This problem has been fixed.

  • For Deep OCR models, the postprocessing parameters detection_``min_word_area and detection_``tiling_overlap could neither be set via set_deep_ocr_param nor via set_dl_model_param after optimize_dl_model_for_inference had been called. However, these parameters do not affect the underlying model structure and, hence, should be settable. This problem has been fixed.

  • Training a deep learning model with a zoom layer in ‘nearest_neighbor’ mode on the ‘gpu’ runtime was unexpectedly slow due to a bug in the backward pass. This problem has been fixed.

  • The generic parameters class_weights and max_weight were ignored in the procedure preprocess_dl_dataset for overwrite_files set to auto. This problem has been fixed.

  • The generic parameters class_weights and max_weight were ignored in the procedure preprocess_dl_dataset for 3d_gripping_point_detection models. This problem has been fixed.

  • Internal security checks identified the security vulnerability CVE-2026-44512. This vulnerability could cause an unrecoverable denial of service when processing an untrusted model. While this CVE is not applicable to our product and has never affected HALCON, it has also been adressed by updating the ONNX third-party library to version 1.22.0, which is no longer affected by it.

  • After classification models had been optimized for AI² inference with optimize_dl_model_for_inference, re-fitting Out-of-Distribution (OOD) Detection was not possible. This problem has been fixed.
    Users can now recalibrate OOD detection on AI²-optimized models to compensate for accuracy changes introduced by the optimization process.

  • apply_dl_model and train_dl_model_batch led to a crash in ‘cpu’ devices for image_width=32 on Advanced Object Detection (AOD) models. This problem has been fixed.

  • transform_dl_sample_batch for large RangePerspective specified in create_dl_transform_random_geometric sometimes did not transform labels or raised internal errors. This problem has been fixed.

  • Passing object detection training results to the dev_display_dl_model_train_info procedure led to an error. This problem has been fixed.

  • The cross entropy loss layer could crash when using invalid target class indices. This problem has been fixed.

Identification > Bar code🔗
  • find_bar_code may have failed to decode certain readable barcodes in very rare cases. This problem has been fixed.

  • Some GS1 DataBar composites could not be decoded due to incorrect segmentation of the lower outline of the composite. This problem has been fixed.

  • For set_bar_code_param and set_bar_code_param_specific, the parameter ‘quiet_zone’ could not be set to 0. This problem has been fixed.

  • The training of the Barcode reader did not work with some codes that could be decoded with fixed parameters. This problem has been fixed.

Identification > 2D code🔗
  • When setting an AI² device with set_dl_model_param('device') for an advanced object detection model, the new error 7918 (“DL: The model supports this device only with optimize_dl_model_for_inference”) is now returned instead of 7903 (“Error occured while writing an ONNX model”).

  • In rare cases, get_data_code_2d_results could crash during print quality inspection for low quality Data Matrix codes when using ‘quality_isoiec15415’, ‘quality_isoiec29158’, ‘quality_semi_t10_values’, or their variants. This problem has been fixed.

  • The print quality inspection for Aztec Codes sometimes returned a temporary memory error if the code to grade was very close to the image border. This problem has been fixed.

  • The grid center determination used in the print quality inspection of the Data Matrix ECC 200 code reader had an issue caused by false edges close to the ends of the alternating pattern. This could affect both the robust and the reference decode algorithms. This problem has been fixed.

File🔗
  • Writing a lossless JPEG-XR image was not completely lossless. This problem has been fixed.

  • When reading reduced domain JPEG 2000 images with four or more channels, HALCON always read the image as if it was saved with the full domain. This problem has been fixed.

    When writing multi-channel images with more than three channels in JPEG 2000 format, HALCON saved the image as using the sRGB color space. Now, HALCON saves such images as having an unspecified color space.

Filter🔗
  • unwarp_image_vector_field did not handle multiple references to the same image correctly, for example, in the case of multi-object images, producing equal results for different vector fields. This problem has been fixed.

  • In rare cases, when using large byte or uint2 images, many channels, and many threads, convol_channels could run out of memory, throw an out-of-memory exception, or crash. This problem has been fixed.

Image🔗
  • fit_surface_first_order returned wrong results if the input contained empty regions. This problem has been fixed.

  • gray_projections returned projections with inconsistent length and order in ‘rectangle’ mode when the smallest enclosing rectangle was axis-aligned. This problem has been fixed.

Matching🔗
Region🔗
  • channels_to_image and other operators performing region intersections internally could have failed for very small regions of 1x1 or 2x2 pixels. This problem has been fixed.

  • Even when the region had enough capacity, HALCON could incorrectly signal H_ERR_NOT_ENOUGH_CHORDS, leading to incorrect region generation in affected cases. This problem has been fixed. The reliability of operators such as gen_region_polygon_filled and gray_inside has been improved.
    This change affects the compatibility (read more).

  • Code analysis detected uninitialized values. This problem has been fixed.
    Due to the refactoring of the code, extension packages using the functions HRLClip2, HRLRelClip, or HRLClip are no longer source-code compatible and must be adapted.
    This change affects the compatibility (read more).

Segmentation🔗
  • watersheds_threshold and watersheds_threshold crashed in very rare cases. This problem has been fixed.

  • segment_image_mser could incorrectly suppress a valid region when ‘may_touch_border’ was set to ‘false’. The problem occurred for regions that do not touch the border, but were an interior region of a larger, enclosing region that touches the border. This problem has been fixed.

Tools🔗
  • intersection_contours_xld used to throw a dispensable low-level error message. This error message has been removed.

  • intersection_contours_xld did not return any intersection point if one of the passed contours was a single, unique point lying on the other passed contour. This problem has been fixed.

Tuple🔗
  • tuple_sum and tuple_cumul could return incorrect results for very large integer input values. This problem has been fixed.

    tuple_cumul did not return all values as floating-point values if the input contained at least one floating-point value, as described in the reference documentation. This problem has been fixed.

  • tuple_number treated floating point numbers starting with a plus sign as strings, not numbers. This problem has been fixed.

XLD🔗
  • union_adjacent_contours_xld produced in incorrect unions of adjacent contours when closed contours were involved. This problem has been fixed.

  • Code analysis detected uninitialized values. This problem has been fixed.
    Due to the refactoring of the code, extension packages using the functions HRLClip2, HRLRelClip, or HRLClip are no longer source-code compatible and must be adapted.
    This change affects the compatibility (read more).

Miscellaneous🔗
  • hinfoxl attempted to load the standard HALCON library, not the XL version. This problem has been fixed.

HDevEngine🔗

Bug fixes🔗

  • The SBOMs for HDevEngine for the aarch64 and armv7 architectures were missing. This problem has been fixed.

  • The third-party library Apache Thrift has been updated to version 0.24.0 to provide a fix for CVE-2026-55971, CVE-2026-58662, CVE-2026-48145, CVE-2026-48586, CVE-2026-55969, and CVE-2026-55970. This library is used for the communication between HDevelop and HDevEngine during remote debugging. HALCON applications that do not use HDevEngine are unaffected.

    HDevEngine production applications that run without enabling the debug server are also unaffected. If the debug server was enabled, exploiting potential vulnerabilities required malicious third-party software to be able to open a socket connection to the host/port combination configured for remote debugging.

    Another path to exploiting potential vulnerabilities was to trick an HDevelop user into initiating a remote debugging connection to a malicious third-party server.


HBench🔗

Bug fixes🔗

  • hbench did not run the complete set of benchmarks but produced an error when the -operator option was used and no individual operator was specified. This problem has been fixed.

HALCON Variable Inspect🔗

Bug fixes🔗

  • Debugging C++ tuples in older HALCON versions with a new HALCON Variable Inspect version was not possible anymore. This problem has been fixed.

Image acquisition🔗

The latest information about new interface revisions and newly supported image acquisition devices can be found on MVTec’s website. For information about improvements, bugfixes, or whether a new revision of the corresponding device driver is required, see the release notes within the documentation of the individual image acquisition interfaces.

Image Source🔗

New functionality🔗
  • A new Image Source plugin, mvtec_file, has been added. It allows simulating a real application with image files when a real camera is not desired or available. The first version only supports the JPEG and PNG formats.

  • The third-party library GenApi has been updated to version 3.5.1. This fixes various security vulnerabilities by updating the third-party library Expat to version 2.8.1.

  • Some GenTL Producers refused to open a module without a previous call to TLUpdateInterfaceList or IFUpdateDeviceList. If this case is detected, these functions are now called, and opening the module is retried.


Digital I/O🔗

The latest information about new interface revisions and newly supported digital I/O interfaces can be found on MVTec’s website. For information about improvements, bugfixes, or whether a new revision of the corresponding device driver is required, see the release notes within the documentation of the individual digital I/O interfaces.


Documentation🔗

Operator reference🔗

  • The documentation of create_caltab has been expanded to include information about the example calibration plate description files provided with HALCON, as well as the calibration plate portfolio available on the MVTec website.

  • The reference manual entry of find_data_code_2d did not clearly state that the parameter ‘stop_after_result’ needs to be set to a value greater than 0. This problem has been fixed.

  • The reference manual entries of all operators whose results are affected by the set_system parameter ‘clip_region’ were updated with a note indicating the clipping behavior.

  • The documentation of register_object_model_3d_pair did not clearly describe the interaction between default_parameters and additional parameter settings. This problem has been fixed.

  • For some operators, the output of get_operator_info contained invalid UTF-8 characters and incorrect output of quotation marks. This problem has been fixed. The following operators were affected by invalid UTF-8 output:
    triangulate_object_model_3d, reconstruct_surface_stereo, set_stereo_model_param, get_dl_model_param, get_deep_ocr_param

Programmer’s guide🔗

  • The information about supported .NET versions was outdated and has been clarified.

User’s guide🔗

  • The Installation Guide now warns about changing the system time when using temporary licenses.

  • The system requirements now state how using Windows IoT systems can affect HALCON functionality.


Third-party libraries🔗