HALCON系统中整合图像采集硬件编程手册

需积分: 9 131 浏览量更新于2024-07-22 收藏 917KB PDF 举报

"Image Acquisition Interface Programmer's Manual 是一份关于如何将第三方图像采集硬件（如帧抓取卡或数字相机）集成到HALCON系统的详细指南。手册涵盖了从版本12.0到版本12.0的HALCON Image Acquisition Interfaces的创建方法。这份文档由MVTec Software GmbH出版，版权自1997年至2014年，包含多个修订版，反映了HALCON系统随时间的更新和发展。手册强调了机器视觉的重要性，并提供了电子、机械、摄影复制、记录等任何形式的复制和传输都需要得到出版商事先书面许可的规定。" 在机器视觉领域，图像采集接口是核心组件之一，它允许系统与各种图像源进行通信，例如工业相机、帧捕获卡等。HALCON的Image Acquisition Interface 提供了一种标准化的方法来控制这些硬件设备，使得用户能够无缝地集成它们到自己的应用中。这份编程手册详细解释了如何创建和使用这些接口，帮助开发者理解和实现高效的图像数据获取。具体知识点包括： 1. **HALCON系统介绍**：HALCON是一个强大的机器视觉软件库，提供多种图像处理功能，如形状匹配、模板匹配、1D/2D码识别、光学字符识别(OCR)等。 2. **图像采集接口的概念**：图像采集接口是连接硬件设备和软件系统的关键部分，它负责设置参数、初始化设备、获取图像数据并将其转换为可处理的格式。 3. **接口创建过程**：手册详细描述了如何创建HALCON的图像采集接口，包括配置硬件参数、设置通信协议、处理图像流等步骤。 4. **版本历史**：手册的多个修订版反映了HALCON系统的不断升级和改进，每个新版本可能引入了新的特性、优化了性能或修复了已知问题。 5. **兼容性**：由于HALCON支持多种图像采集硬件，手册会讲解如何确保软件与不同硬件之间的兼容性。 6. **编程接口**：手册可能涵盖HALCON的API（应用程序编程接口），介绍如何在程序中调用接口函数进行图像采集操作。 7. **错误处理和调试**：对于可能出现的问题，手册可能提供了故障排查和调试的指导。 8. **示例代码和实践应用**：手册通常包含实际代码示例，帮助开发者快速理解和应用理论知识。通过深入学习这份"Image Acquisition Interface Programmer's Manual"，开发者能够掌握HALCON系统中图像采集的关键技术，从而在实际项目中实现高效、稳定的机器视觉解决方案。

16 Introduction

Parameter Name Typical Values

’continuous_grabbing’ ’enable’,’disable’

’do_abort_grab’ ’true’

’grab_timeout’ <int>

’image_available’ 0, 1

’num_buffers’ <int>

’revision’ ’4.0’,’4.1’,....

’start_async_after_grab_async’ ’enable’,’disable’

’volatile’ ’enable’,’disable’

Figure 1.2: Standard names and values for recommended image acquisition parameters.

ﬁgure 1.2 for a list of recommended parameters. ﬁgure 1.3 shows a list of typical names for device

speciﬁc parameters.

• All parameter names and also the valid string values of parameters should be denoted in lowercase

notation.

• All parameters which can be set via set_framegrabber_param should also be asked for their

current setting via get_framegrabber_param.

• Special parameters (so-called action parameters) which do not set a new parameter value but

initiate a certain action should use the preﬁx ’do_’. Obviously, there’s no need to access the

current setting of these parameters by get_framegrabber_param.

• All parameters should have a corresponding parameter with the sufﬁx ’_description’ contain-

ing a meaningful tooltip.

• If applicable, all parameters should have a corresponding parameter with the sufﬁx ’_range’ or

’_values’ containing the necessary information about possible ranges or values.

1.8 Optimal Interaction with the HDevelop Image Acquisi-

tion Assistant

If you want to use a HALCON image acquisition interface in combination with the HDevelop Image

Acquisition Assistant please note the following items:

• Auto Detection

– The user has the possibility to select an image acquisition interface either manually from

the list or restrict this list to all image acquisition interfaces which are actually available

on the computer (auto-detection). For all known interfaces which are present in the di-

rectory bin/%HALCONARCH% (or lib/$HALCONARCH, respectively) the auto-detection calls

1.8 Optimal Interaction with the HDevelop Image Acquisition Assistant 17

Parameter Name Typical Values

’brightness’ <int>

’do_ﬂush_buffers’ ’true’

’do_force_trigger’ ’true’

’contrast’ <int>

’exposure’ <int>

’frame_rate’ <float>

’gain’ <int> or <float>

’shaft_encoder’ ’enable’,’disable’

’shutter’ <int>

’strobe’ ’enable’,’disable’

’strobe_delay’ <int> or <float>

’strobe_duration’ <int> or <float>

’timestamp’ <string> or <int>

’trigger_mode’ ’free-run’,’async’,...

’trigger_signal’ ’rising’,’falling’,...

’trigger_source’ ’line1’,’line2’,...

Figure 1.3: Typical names and values for additional image acquisition parameters representing parameters

provided by the manufacturer’s API .

info_framegrabber(...,’info_boards’,...). If a device is found and the return pa-

rameter contains a valid (i.e., non-empty) string, the interface will be added to the list of

detected image acquisition interfaces.

– The implementation of info_framegrabber(...,’info_boards’,...) has to check for

actually available devices. If multiple devices are present, this operator should return a tu-

ple with all found devices. Each device string should contain the name ’device:’ followed

by the interface-speciﬁc device name. Multiple devices should use different names, e.g.,

[’device:0 camera_type:Camera-X’, ’device:1 camera_type:Camera-Y’]. Fur-

ther information like port will also be parsed and may be useful inside this string.

– In some cases there is no API function available to call the required informa-

tion without opening the device. In this case it is important that the call of

info_framegrabber(...,’info_boards’,...) returns an error if no underlying

driver/API is actually present, especially if there are no dependencies of the image acqui-

sition interface to vendor-speciﬁc dynamic libraries!

• Opening a Device

– For opening a device the user has to insert the necessary parameters. To provide this param-

eters, the necessary information is queried with calls of info_framegrabber. All calls of

info_framegrabber must be also possible without opening the device before.

– The following query types are actually called via info_framegrabber: ’de-

faults’, ’info_boards’, ’port’, ’camera_type’, ’horizontal_resolution’, ’vertical_resolution’,

Introduction

18 Introduction

’color_space’, ’bits_per_channel’,’ﬁeld’, ’external_trigger’, ’generic’, and ’revision’. In case

of ’camera_type’, the returning string can also indicate that a ﬁle selection box should be used

in the GUI, see the template code for an example.

• Parameterization

– During the connection process all parameters are queried via

info_framegrabber(...,’parameters’,...). These parameters are displayed in the

parameter window, unless there exists a read-only parameter ’available_param_names’

that queries the actual available parameters in case of generic parameters, e.g., in the

GigEVision interface.

– If calling get_framegrabber_param for a single parameter returns an error code like

H_ERR_FGPARAM, the parameter is discarded.

– For each available parameter also the following parameters are checked automatically:

’*_range’ (if implemented, a slider will be visible), ’*_values’ (if implemented, a combo

box with the returned values will be displayed), and ’*_description’ (if implemented, a tooltip

will appear).

– Read-only parameters should also be returned by the call of

info_framegrabber(...,’parameters_readonly’,...).

– Write-only parameters should also be returned by the call of

info_framegrabber(...,’parameters_writeonly’,...). To display a button

for a write-only parameter, you have to implement also the corresponding ’_values’

parameter with exactly one value.

– If you want to exclude some parameters from the GUI, then these parameters should be re-

turned by the call of info_framegrabber(...,’parameters_hidden’,...). Also tuple

parameters, which are not read-only, should be added to this list.

– Besides ’*_range’, ’*_values’, and ’*_description’, there exist three more speciﬁc parameter

extensions: ’*_access’ (if implemented, the parameters will be handled as read-only, write-

only, or read- and writable), ’*_category’ (if implemented, groups of parameters based on

categories are shown), and ’*_visibility’ (if implemented, groups of parameters based on the

possible user skill levels ’Beginner’, ’Expert’, and ’Guru’ are displayed).

1.9 HALCON Image Acquisition Integration Interface vs.

HALCON Image Acquisition Interface

The term “HALCON image acquisition interface” typically refers to an external module encapsulating

the code that is speciﬁc for the image acquisition device; this is the one you have to provide. In contrast,

the “HALCON image acquisition integration interface” is the module inside the HALCON library which

is responsible for managing and accessing (external) image acquisition interface modules.

Whenever an image acquisition device is accessed for the very ﬁrst time using open_framegrabber or

info_framegrabber the corresponding (external) image acquisition interface, a dynamically loadable

module,

is loaded. For example, a call like

A DLL for Windows or a shared library for Linux systems, respectively.

剩余95页未读，继续阅读

qq_26803287

粉丝: 0
资源: 1

HALCON系统中整合图像采集硬件编程手册

Senz3D Acquisition interface：Creative Senz3D、Intel Interactive Gesture Camera (Time of Flight)、Acquisition interface。-matlab开发

Image Acquisition Gateway

Image Acquisition Toolbox 支持 FLIR Spinnaker：使用 Image Acquisition Toolbox 的 Spinnaker 支持相机的 Spinnaker 适配器-matlab开发

Image Acquisition Toolbox user's guide (R2014a)

image acquisition.m

Image Acquisition and Processing with LabView

FireWire Image Acquisition Toolbox-开源

Image Acquisition and Processing with Labview

Image Acquisition and Processing with LabVIEW代码

wxIA - wxWindows Image Acquisition-开源

最新资源