Dokumentation
Image Acquisition Interface for Ginga++ Boards
Interface: | Ginga++ |
Revision: | 13.0.1 |
Date: | 2016-10-28 |
HALCON Version: | 13.0 |
- General
- System Requirements
- Features
- Camera File Naming Convention
- Sequence Grabbing Mode
- Continuous Grabbing Mode
- Parameters for info_framegrabber
- Parameters for open_framegrabber
- Parameters for set_framegrabber_param
- Parameters for get_framegrabber_param
- Operator set_framegrabber_lut
- Operator get_framegrabber_lut
- Operator set_framegrabber_callback
- Operator get_framegrabber_callback
- Operator grab_image_start
- Operator grab_image
- Operator grab_image_async
- Operator grab_data
- Operator grab_data_async
- Operator close_framegrabber
- HDevelop Examples
- Release Notes
General
System Requirements
- Intel compatible PC with Windows 7 (32-bit or 64-bit) or newer that is also supported by the vendor-specific SDK.
- Successfully installed Ginga++ Initial Software Kit (ISK):
<GINGA++M4>
Ginga++ device driver version 1.3.5.9 or later
<GINGA++M2>
Ginga++ device driver version 1.1.3.4 or later - Successfully installed Ginga++ driver GingaPP.sys (GINGA++M4) or GingaM2.sys (GINGA++M2).
- HALCON image acquisition interface hAcqGinga++.dll or hAcqGinga++xl.dll, respectively. If you have properly installed the interface, both DLLs should reside in bin\%HALCONARCH% within the HALCON base directory %HALCONROOT% you have chosen during the installation of HALCON.
Features
- Multiple cameras on multiple frame grabber boards.
- Serial and parallel (simultaneously from several cameras) grabbing.
- Synchronous and asynchronous grabbing.
- Using arbitrary cameras by setting the camera file name.
- Different grabbing modes: external trigger, sequence grabbing, continuous grabbing.
- Subsampling.
- Software cropping of image parts.
Camera File Naming Convention
[Camera Name] Name of camera. Symbols like "-" are removed.
[Scan Format] Video signal format of the camera and the number of signals (single or dual tap) as shown below:
- IL: Interlace
- FLD: Non-interlace (field grabbing)
- NI: Non-interlace (progressive frame grabbing)
The number of signals in case of a dual video tap camera:
- SINGLE: Single tap
- DUAL: Dual tap
[Shuttering]
Shutter mode of the camera:
- NORM: The images, which are continuously outputted from the camera, can be grabbed by the software timing. Each grab starts just after a grab command like grab_image is called.
- TRIG_FREERUN: The video signal, which is the continuous output from the camera, can be grabbed by the shot (trigger) signal from the external device or shot operation by software trigger. The camera runs in free running mode. Each grab starts by the vertical sync signal of the video just after external shot signal input or software shot operation using grab_image or grab_image_async.
- TRIG_DEMAND: Reset shutter is made by a trigger signal given to the camera from the GINGA++ board. The camera trigger signal is given at the timing of shot signal from external device (external trigger) or shot operation (software trigger, see above). The camera can be reset by the shutter operation and outputs the video signal at the shot signal timing. In case that several cameras connected to a GINGA++ board are reset by the same shot signal timing, these cameras can grab simultaneously.
Example:
- Sony XC-55, interlace scan, free running without reset
shutter:
XC55_IL_NORM - Teli CS-3720, progressive scan, single video, grabbing by shot signal under
free running mode:
CS3720_NI_SINGLE_TRIG_FREERUN - Teli CS-3720, interlace scan, dual video, grabbing with reset shutter by
external shot signal (external trigger) or software shot operation (software
trigger):
CS3720_IL_DUAL_TRIG_DEMAND
Sequence Grabbing Mode
Note that the frame rate for grabbing can be adjusted either automatically or dynamically according to the PCI load by setting the grabbing frequency.
Note: The sequence grabbing mode can not be combined with the software trigger (shot grabbing) mode!
Example:
- num_buffers: 5
- capture_frequency: 'Capture=2 Drop=1'
Continuous Grabbing Mode
This mode is usually applied with external trigger and cannot be used with software trigger (shot operation). However, this method can be used in normal mode also without trigger.
Note that the frame rate for grabbing can be adjusted either automatically or dynamically according to the PCI load by setting the grabbing frequency.
Note: The continuous grabbing mode can not be combined with the software trigger (shot grabbing) mode!
Example:
- num_buffers: 5
- capture_frequency: 'Capture=2 Drop=1'
Reference of Ring Buffer: This paragraph describes how to transfer the remaining images in the ring buffer to HALCON when the image acquisition stops in continuous grabbing mode. The figure below shows the status of the ring buffer when the image acquisition is terminated in the condition of 'abort' for the parameter 'overwrite_method'. The gray area shows the remaining images which have not been transferred to HALCON. The condition of the continuous grabbing mode is
- num_buffers = 6
- overwrite_method = 'abort'
- ring_buffer_stop_margin = 1
The image acquisition is terminated because it has reached the last frame number specified by 'ring_buffer_stop_margin' although the acquisition is made to Frame2. You can transfer the images to HALCON according to the sequence of Frame5->Frame0->Frame1->Frame2 by setting the parameter 'walk_ring_buffer' to 'enable' and calling grab_image or grab_image_async.
Parameters for info_framegrabber
Parameter | Value List | Type | Kind | Description |
---|---|---|---|---|
'bits_per_channel' | [] | Unused. | ||
'camera_type' | ['CAMFILE:', '', <camera_path>] | string | pre-defined | Syntax for camera configuration file. |
'color_space' | [] | Unused. | ||
'defaults' | [1, 1, 0, 0, 0, 0, 'interlaced', 8, 'gray', -1.0, 'false', 'default', '0', 0, 0] | mixed | pre-defined | Default values for open_framegrabber. |
'device' | ['GINGA++M4', 'GINGA++M2'] | string | pre-defined | Pre-defined list of possible board types. |
'external_trigger' | [] | Unused. | ||
'field' | [] | Unused. | ||
'general' | [] | string | pre-defined | Information about the HALCON Ginga++ interface. |
'generic' | [] | Unsupported query. | ||
'horizontal_resolution' | [1, 2, 4] | integer | pre-defined | Value list for horizontal resolution. |
'image_height' | [] | Unsupported query. | ||
'image_width' | [] | Unsupported query. | ||
'info_boards' | ['device:Ginga++M4', 'device:Ginga++M2'] | string | dynamic | Returns a list of the available Ginga++ boards. |
'parameters' | ['<parameters>'] | string | pre-defined | Pre-defined parameters of the HALCON interface. |
'parameters_readonly' | ['<parameters>'] | string | pre-defined | Pre-defined read-only parameters of the HALCON interface. |
'parameters_writeonly' | ['<parameters>'] | string | pre-defined | Pre-defined write-only parameters of the HALCON interface. |
'port' | [0, 1, 2, ... 15] | integer | pre-defined | Pre-defined list of possible values for port. |
'revision' | '<revision>' | string | pre-defined | Revision number of the Ginga++ interface. |
'start_column' | [] | Unsupported query. | ||
'start_row' | [] | Unsupported query. | ||
'vertical_resolution' | [1, 2, 4] | integer | pre-defined | Value list for vertical resolution. |
Parameters for open_framegrabber
Parameter | Values | Default | Type | Description |
---|---|---|---|---|
Name | 'Ginga++' | string | Name of the HALCON interface. | |
HorizontalResolution | 1, 2, 4 | 1 | integer | The desired horizontal image resolution. Use '1' for full resolution, '2' for subsampling by factor 2, and '4' for subsampling by factor 4. |
VerticalResolution | 1, 2, 4 | 1 | integer | The desired vertical image resolution. Use '1' for full resolution, '2' for subsampling by factor 2, and '4' for subsampling by factor 4. |
ImageWidth | 0, <width> | 0 | integer | Width of the desired image part ('0' stands for the complete image). |
ImageHeight | 0, <height> | 0 | integer | Height of the desired image part ('0' stands for the complete image). |
StartRow | 0, <row> | 0 | integer | Row coordinate of the upper left pixel within the desired image part. |
StartColumn | 0, <column> | 0 | integer | Column coordinate of the upper left pixel within the desired image part. |
Field | --- | Ignored. | ||
BitsPerChannel | --- | 8 | Ignored. | |
ColorSpace | --- | 'gray' | Ignored. | |
Generic | --- | -1 | Ignored. | |
ExternalTrigger | --- | 'false' | Ignored. | |
CameraType | <cam_name> | 'default' | string | The CameraType parameter is used to specify the file name of the desired camera configuration. Note that the file name has to be relative to the
environment variable %GingaPPConfigPath%. Example: jai/CVM40_NI_NORM For details please refer to the rule for camera file naming.
|
Device | 'GINGA++M4', 'GINGA++M2' | '0' | string | Board type of the Ginga++ board. |
Port | 0, 1, 2, ... | 0 | integer | The port parameter specifies the channel number the camera(s) is/are connected to. The channel number must be set from 0 for the first channel
of the smallest PCI bus and slot number when multiple cameras on multiple
frame grabber boards are installed in the same system. For example, in
case of [Board 1] bus number = 0, slot number = 0 [Board 2] bus number = 0, slot number = 1 [Board 3] bus number = 1, slot number = 0 then: Port number of [Board 1] must be set to [0-3] Port number of [Board 2] must be set to [4-7] Port number of [Board 3] must be set to [8-11] |
LineIn | --- | Ignored. |
Parameters for set_framegrabber_param
Parameter | Values | Default | Type | Description |
---|---|---|---|---|
'abort_wait' | <milliseconds> | 0 | integer | Time to wait in milliseconds after aborting a grab. Default: 0. |
'capture_frequency' | 'Capture=<frames_x> Drop=<frames_y>' | value specified in the camera file | string | Specify the grabbing frequency to adjust the desired frame rate automatically and dynamically according to the PCI load. The frames specified by frames_x
are grabbed sequentially. After that, the grabbing is suspended for the next
frames_y frames. This parameter is effective only in
sequence or
continuous
grabbing mode.
|
'continuous_grabbing' | 'disable', 'enable' | 'disable' | string | Activate/deactivate continuous grabbing mode. |
'do_abort_capture' | --- | Abort the current image acquisition. | ||
'do_clear_ring_buffer' | -1 | integer | If 'continuous_grabbing' is enabled, the parameter clears the internal used buffers. | |
'do_force_trigger' | --- | This parameter is prepared for shot operation similar to the 'software_trigger' parameter. When set_framegrabber_param operator with 'do_force_trigger' is called, a shot operation is invoked and a trigger signal is sent to the camera. This mode is useful to abort a pending grab_image_async when using a reset shutter mode camera file. | ||
'external_drive' | 'disable', 'enable' | 'enable' | string | When this mode is enabled, the Ginga++ board sends the HD (horizontal drive) signal to the camera(s). In this case the horizontal synchronization of the camera is driven by the Ginga++ board. This mode is especially useful for simultaneous grabbing with multiple cameras. If this mode is disabled, switching of synchronization signal source of the cameras, which are connected to a pair port, is made automatically. This disabled mode is used for grabbing by switching between multiple cameras. |
'external_trigger' | 'false', 'true' | string | Activate/deactivate external triggering. If enabled, the grabbing starts with the shot (external trigger) signal input to the Ginga++ board. Note that you cannot disable the external trigger mode when using a reset shutter mode camera file. | |
'grab_timeout' | <milliseconds> | 5000 | integer | Desired timeout (milliseconds) for aborting a pending grab. If -1 is specified, the timeout is set to INFINITE. |
'long_exposure_time' | 1 ... 256 | integer | Long exposure time. | |
'overwrite_method' | 'abort', 'ignore' | 'abort' | string | In this continuous grabbing mode you might encounter situations where the images are acquired at a faster rate than they
are read by your application. Thus, the buffers will fill up and finally you
will encounter a buffer that was not read so far, but should be overwritten by
the next frame. You can decide what to do in this situation via the parameter
'overwrite_method':
|
'ring_buffer_stop_margin' | 0 ... (num_buffers-1) | 1 | integer | When 'overwrite_method' is set to 'abort', empty frame number is specified for the condition of completion of image acquisition. You may have the problem that you cannot stop acquisition at the expected frame number when the load of application is big or high-speed camera is used. The image may by overwritten before converting it into HALCON object. Please specify enough number of frames to avoid this situation. See continuous grabbing mode for more details. |
'sequence_grabbing' | 'disable', 'enable' | 'disable' | string | Activate/deactivate sequence grabbing mode. |
'shutter_speed' | <seconds> | integer | Shutter speed (exposure time) in seconds if camera is used in reset shutter mode. | |
'signal_range_max' | -0.285 ... 0.990 | float | Maximum value for the intensity range of the grabbed images. If the grabbed video signal intensity is greater or equal than this value the corresponding pixels become white (255). | |
'signal_range_min' | -0.285 ... 0.990 | float | Minimum value for the intensity range of the grabbed images. If the grabbed video signal intensity is lower or equal than this value the corresponding pixels become black (0). | |
'software_trigger' | 'disable', 'enable' | 'disable' | string | Enable or disable the software trigger mode (shot grabbing). In case you specify a camera file for reset shutter mode in the CameraType parameter
during open_framegrabber, the Ginga++ board sends the trigger
signal to the camera for shuttering. This trigger signal is synchronized
with the shot (external trigger) signal input to Ginga++ from
an external device if the parameter 'software_trigger' is set to 'disable'
(default). However, if you enable the software trigger mode, the Ginga++ baord sends the trigger signal to the camera synchronized with the software operation instead of the external device signal. When calling grab_image or grab_image_async in this software trigger mode (also called shot grabbing mode) the trigger signal is sent immediately to the camera for shuttering and grabbing the desired image. |
'start_async_after_grab_async' | 'disable', 'enable' | 'enable' | string | By default a new asynchronous grab command is automatically given to the acquisition device at the end of grab_image_async. If the parameter 'start_async_after_grab_async' is set to 'disable', this new grab command is omitted. |
'volatile' | 'disable', 'enable' | 'disable' | string | Grayscale only. In the volatile mode the two image acquisition interface buffers are used directly to store HALCON images. This is the fastest mode avoiding to copy raw images in memory. However, be aware that older images are overwritten again and again as a side-effect. Thus, you can only process one image while you grab another image. Older images are invalid! |
'wait_frame_exposure' | <milliseconds> | integer | Time to wait for the camera exposure. | |
'wait_frame_exposure_timeout' | <milliseconds> | 1000 | integer | Specify timeout value in milliseconds for waiting process for the completion of camera exposure by 'wait_frame_exposure' of get_framegrabber_param, when image acquisition is made by random trigger shutter of camera. |
'walk_ring_buffer' | 'disable', 'enable' | 'disable' | string | If you specify 'enable' to this parameter, you can convert the remained images in the ring buffer into HALCON objects sequentially using grab_image or grab_image_async after completion of continuous grabbing. The total number of remaining images in the ring buffer can be calculated by the parameters 'ring_buffer_last_index', 'ring_buffer_current_index', and 'num_buffers' using get_framegrabber_param. HALCON error H_ERR_FGF is returned if you invoke grab_image or grab_image_async after all images stored in the ring buffer are read. See continuous grabbing mode for more details. |
Parameters for get_framegrabber_param
- '_description': These parameters provide the tool-tip of the corresponding parameter as a string.
- '_range': These parameters provide the minimum, maximum, step width, and default values for the corresponding integer or float parameter as a tuple with 4 elements, e.g., get_framegrabber_param(.., 'Shutter_range', ..) will return the output tuple [min, max, step, default].
- '_values': These parameters provide the valid value list for the corresponding parameter as a tuple, e.g., get_framegrabber_param(.., 'volatile_values', ..) will return the output tuple ['enable', 'disable'].
All these postfixed parameter names are not returned when calling info_framegrabber(.., 'parameters', ..) and are used to enable the easy parameterization via a generic graphical user interface, particularly the HDevelop Image Acquisition Assistant.
Parameter | Values | Default | Type | Kind | Description |
---|---|---|---|---|---|
'abort_wait' | <milliseconds> | 0 | integer | dynamic | Time to wait in milliseconds after aborting a grab. Default: 0. |
'abs_counter' | <number> | integer | dynamic | Number of grabbed images. | |
'bits_per_channel' | <default> | 8 | integer | pre-defined | The value is not used, so a default value is returned. |
'camera_type' | <cam_name> | 'default' | string | pre-defined | Returns the values for the camera type. |
'capture_frequency' | 'Capture=<frames_x> Drop=<frames_y>' | value specified in the camera file | string | dynamic | Grabbing frequency to adjust the desired frame rate automatically and dynamically according to the PCI load. |
'color_space' | '<default>' | 'gray' | string | pre-defined | The value is not used, so a default value is returned. |
'continuous_grabbing' | 'disable', 'enable' | 'disable' | string | pre-defined | Activate/deactivate continuous grabbing mode. |
'device' | 'GINGA++M4', 'GINGA++M2' | '0' | string | pre-defined | Board type of the Ginga++ board. |
'external_drive' | 'disable', 'enable' | 'enable' | string | pre-defined | External drive mode. |
'external_trigger' | <default> | 'false' | string | pre-defined | The value is not used, so a default value is returned. |
'field' | '<default>' | 'interlaced' | string | pre-defined | The value is not used, so a default value is returned. |
'generic' | <default> | -1 | mixed | pre-defined | The value is not used, so a default value is returned. |
'grab_timeout' | <milliseconds> | 5000 | integer | pre-defined | Current grab timeout in milliseconds. |
'horizontal_resolution' | 1, 2, 4 | 1 | integer | pre-defined | Current value of horizontal resolution. |
'image_height' | <height> | 0 | integer | pre-defined | Height of the desired image part ('0' stands for the complete image). |
'image_width' | <width> | 0 | integer | pre-defined | Width of the desired image part ('0' stands for the complete image). |
'line_in' | <default> | 0 | integer | pre-defined | The value is not used, so a default value is returned. |
'long_exposure_time' | 1 ... 256 | integer | dynamic | Long exposure time. | |
'name' | 'Ginga++' | string | pre-defined | Name of the HALCON interface. | |
'next_buffer_acquired' | <index> | integer | dynamic | Index of the next buffer which could be acquired. | |
'next_buffer_returned' | <index> | integer | dynamic | Index of the next buffer which is returned. | |
'num_buffers' | <number> | 2 | integer | pre-defined | The number of allocated frame buffers is specified in case of sequence grabbing or continuous grabbing mode. The maximum number of frame buffers is limited by system memory size. Note that 'num_buffers' must be set before enabling the sequence grabbing mode! |
'overwrite_method' | 'abort', 'ignore' | 'abort' | string | pre-defined | Overwrite method of the buffers. |
'port' | 0, 1, 2, ... | 0 | integer | pre-defined | Current port number. |
'revision' | '<revision>' | string | pre-defined | Revision number of the Ginga++ interface. | |
'ring_buffer_current_index' | 0...(num_buffers-1) | integer | dynamic | Index number of the last ring buffer which is converted into HALCON object when image acquisition is completed. The index number is between 0 and (num_buffers-1). See continuous grabbing mode for more details. | |
'ring_buffer_last_index' | 0...(num_buffers-1) | integer | dynamic | Last index number of the ring buffer when image acquisition is completed. The index number is between 0 and (num_buffers-1). See continuous grabbing mode for more details. | |
'ring_buffer_stop_margin' | <number> | 1 | integer | pre-defined | Number of buffers to stop the ring buffer. |
'sequence_grabbing' | 'disable', 'enable' | 'disable' | string | pre-defined | Activate/deactivate sequence grabbing mode. |
'shutter_speed' | <seconds> | integer | dynamic | Shutter speed (exposure time) in seconds if camera is used in reset shutter mode. | |
'signal_range_max' | -0.285 ... 0.990 | float | dynamic | Maximum value for the intensity range of the grabbed images. If the grabbed video signal intensity is greater or equal than this value the corresponding pixels become white (255). | |
'signal_range_min' | -0.285 ... 0.990 | float | dynamic | Minimum value for the intensity range of the grabbed images. If the grabbed video signal intensity is lower or equal than this value the corresponding pixels become black (0). | |
'software_trigger' | 'disable', 'enable' | 'disable' | string | pre-defined | Software trigger mode (shot grabbing). |
'start_async_after_grab_async' | 'disable', 'enable' | 'enable' | string | pre-defined | Status of 'start_async_after_grab_async'. |
'start_column' | <column> | 0 | integer | pre-defined | Returns the current start column of the HALCON image. |
'start_row' | <row> | 0 | integer | pre-defined | Returns the current start row of the HALCON image. |
'vertical_resolution' | 1, 2, 4 | 1 | integer | pre-defined | Current value of vertical resolution. |
'volatile' | 'disable', 'enable' | 'disable' | string | pre-defined | Grayscale only. In the volatile mode the two image acquisition interface buffers are used directly to store HALCON images. This is the fastest mode avoiding to copy raw images in memory. However, be aware that older images are overwritten again and again as a side-effect. Thus, you can only process one image while you grab another image. Older images are invalid! |
'wait_frame_exposure' | 0, 1, 2 | integer | dynamic | Wait for the completion of camera exposure for the period specified by 'wait_frame_exposure_timeout'. The possible return values are
|
|
'wait_frame_exposure_timeout' | <milliseconds> | 1000 | integer | dynamic | Specify timeout value in milliseconds for waiting process for the completion of camera exposure by 'wait_frame_exposure' of get_framegrabber_param, when image acquisition is made by random trigger shutter of camera. |
'walk_ring_buffer' | 'disable', 'enable' | 'disable' | string | pre-defined | Walk ring buffer. |
Operator set_framegrabber_lut
Operator get_framegrabber_lut
Operator set_framegrabber_callback
Operator get_framegrabber_callback
Operator grab_image_start
Operator grab_image
Operator grab_image_async
Operator grab_data
Operator grab_data_async
Operator close_framegrabber
HDevelop Examples
- ginga++_2cameras.hdev - Usage of a LinX Ginga++ frame grabber board with two cameras
- ginga++_capture_freq.hdev - Capture frequency control of a LinX Ginga++ frame grabber board
- ginga++_continuous.hdev - Simple example for the usage of the continuous grabbing mode.
- ginga++_crop.hdev - Shows image cropping.
- ginga++_external_drive.hdev - Simultaneous grabbing with multiple cameras.
- ginga++_frame_exposure.hdev - Example for the usage of frame exposure.
- ginga++.hdev - Benchmark
- ginga++_parameters.hdev - Lists all parameters of a device.
- ginga++_sequence.hdev - Example for the usage of the sequence grabbing mode.
- ginga++_simple.hdev - A simple example to show the usage of the interface.
- ginga++_trigger.hdev - Example for the usage of a LinX Ginga++ frame grabber board with triggering.
- ginga++_walking.hdev - Example for the usage of the continuous grabbing mode.
Release Notes
- Revision 13.0.1 (Oct 28, 2016):
- HALCON 13 version of the interface.
- Revision 6.0 (Oct 31, 2014):
- HALCON 12 version of the interface.
- Added support of Windows 64-bit.
- Revision 5.1 (Oct 24, 2014):
- Fixed error when using 'do_abort_capture' or 'do_force_trigger' with the HDevelop Image Acquisition Assistant.
- Added missing code for parameter 'do_clear_ring_buffer'.
- Revision 5.0 (May 15, 2012):
- HALCON 11 version of the interface (included in HALCON 11 DVD).
- Revision 4.1 (Sep 8, 2010):
- Added parameters 'do_clear_ring_buffer', 'next_buffer_acquired' and 'next_buffer_returned'.
- Fixed bug in grab_image and grab_image_async.
- Removed internally used debug functions.
- HALCON 10 version of the interface (included in HALCON 10 DVD).
- Revision 4.0 (Dec 1, 2008):
- Added read-only parameters 'do_force_trigger_values' and 'do_abort_capture_values' to enable this functionality also in the HDevelop Image Acquisition Assistant.
- Special thread handling in continuous grabbing mode.
- HALCON 9.0 version of the interface (included in HALCON 9.0 DVD).
- Revision 3.1 (Apr 22, 2008):
- Added read-only parameters with postfix '_description', '_range', and '_values' to enable the easy parameterization via a generic graphical user interface.
- Revision 3.0 (May 15, 2007):
- HALCON 8.0 version of the interface (included in HALCON 8.0 DVD).
- New parameters 'abort_wait' and 'abs_counter'.
- Support of absorb frame buffer mode.
- Revision 2.3 (Dec 17, 2004):
- HALCON 7.1 version of the interface (included in HALCON 7.1 CD).
- New parameters 'long_exposure_time' and 'do_abort_capture'.
- The query types 'bits_per_channel', 'camera_type', 'color_space', 'device', 'external_trigger', 'field', and 'port' for info_framegrabber provide now specific value lists for the corresponding parameters in open_framegrabber.
- Revision 2.2 (Jun 24, 2003):
- HALCON 7.0 version of the interface (included in HALCON 7.0 CD).
- info_framegrabber(...'info_boards'...) returns now an error in case that no Ginga++ boards are actually installed.
- Revision 2.1 (Dec 19, 2002):
- Support of GINGA++M2 boards.
- Waiting process for the completion of camera exposure (new parameters 'wait_frame_exposure' and 'wait_frame_exposure_timeout').
- Additional parameters for continuous grabbing mode.
- Revision 2.0 (Apr 28, 2002):
- First official release (included in HALCON 6.1 CD).