Skip to content

Limitations🔗

General limitations🔗

See the following for limitations that are relevant for typical application development with HALCON:

String processing
The HALCON library does not handle multibyte characters internally. File names containing multibyte characters are supported after calling set_system('filename_encoding','utf8').
Processing of NaNs
Due to performance reasons, the HALCON library does not check for NaNs in input data. Using such input can lead to undefined behavior.
Maximum image size
HALCON: 32 768 × 32 768
HALCON XL: 1 073 741 824 × 1 073 741 824 (230 × 230)
Maximum number of channels per image
65 535
Range for coordinates
HALCON: from −32 767 to 32 767
HALCON XL: from −1 073 741 824 to 1 073 741 823 (−230 to 230 − 1)
Maximum number of windows
600

Limitations for dongle-based licenses🔗

After starting applications based on HALCON 20.05 (or later), the dongle must be removed and inserted again before starting applications based on HALCON 19.11 (or earlier). This problem can be avoided by installing the CodeMeter Runtime from WIBU SYSTEMS AG. The CodeMeter Runtime is not shipped with HALCON, but can be downloaded from wibu.com in the download area.

On Arm platforms (aarch64 architecture) with GLIBC ≥ 2.21, it is no longer possible to run both 64-bit and 32-bit HALCON processes in parallel as they might block each other.

Limitations related to compute devices🔗

Operators that are based on texture are limited to the maximum size of the graphics card. Currently, this limit is 8192\(\times\)8192. This is relevant for the following operators:

Further limitations include:

  • All other operators are restricted to the maximum allocated block size, for example, 200 MB on the Tesla C2050.
  • edges_sub_pix and lines_gauss are not Open CL accelerated for HALCON XL.
  • edges_sub_pix and lines_gauss need a lot of memory on the compute device.

Limitations related to image acquisition🔗

  • Maximum number of acquisition interfaces: 128
  • Maximum number of open handles per acquisition interface: 256
  • Maximum number of interface-specific parameters: 2048

Limitations related to OpenGL🔗

Operators using OpenGL for visualization (for example, disp_object_model_3d) require OpenGL 2.1, GLSL 1.2, and the OpenGL extensions GL_EXT_framebuffer_object and GL_EXT_framebuffer_blit. Therefore, those operators cannot be used via Windows Remote Desktop or SSH forwarding. Other operators, like find_shape_model_3d, have an optimized implementation when OpenGL is available. Which operators benefit from OpenGL can be found in the reference documentation of the corresponding operators.

To figure out which OpenGL features are available and offered by the driver, HALCON opens a hidden OpenGL window during initialization when the first HALCON operator is called. Thus, if the system has defective OpenGL drivers installed, HALCON may crash during initialization. To work around this issue, HALCON can be told to ignore OpenGL entirely by defining and setting the system environment variable HALCON_NO_OPENGL to 1.

Limitations on Arm-based platforms🔗

The following limitations apply compared to other platforms:

  • no HALCON XL version
  • no MAC-based licensing, no standard evaluation licenses
  • no HDevelop
  • no hcomp, thus extension packages have to be cross-compiled on the development computer

Limitations related to extension packages🔗

Maximum number of parameters:

  • Iconic input parameters: 9
  • Iconic output parameters: 9
  • Control input parameters: 20
  • Control output parameters: 2