MVTec Software GmbH
  Building Vision For Business
Halcon

HALCON 7.0 Frame Grabber Interface for GINGA++ Boards

This page provides the documentation about the HALCON frame grabber interface HFGGinga++.dll for the LinX GINGA++ frame grabber boards. Registered customers can download the latest revision of this interface from the MVTec WWW server or from the Support Area of the LinX WWW server. In case of installation problems please send e-mail (techimage@linx.jp) or fax (81-45-979-0732) to LinX technical support center.

Revision: 2.3

System Requirements

  • Intel compatible PC with either Windows NT 4.0 (Service Pack 5 or later) or Windows 2000.
  • Successfully installed GINGA++ Initial Software Kit (ISK):
    <GINGA++M4>
      Windows NT 4.0: GINGA++ device driver version 1.5.5.9 or later
      Windows 2000: GINGA++ device driver version 1.3.5.9 or later
    <GINGA++M2>
      Windows NT 4.0: GINGA++ device driver version 1.1.2.4 or later
      Windows 2000: GINGA++ device driver version 1.1.3.4 or later
  • Successfully installed GINGA++ driver GingaPP.sys (GINGA++M4) or GingaM2.sys (GINGA++M2) in %SystemDrive\Winnt\system32\drivers.
  • HALCON frame grabber interface HFGGinga++.dll or parHFGGinga++.dll, respectively. If you have properly installed the interface, both DLLs should reside in bin\i586-nt4 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.

Limitations

  • grab_region and grab_region_async not supported.
  • No LUTs.

Description

Parameters for open_framegrabber() :

Name 'Ginga++' The name of the HALCON frame grabber interface.
HorizontalResolution 1, 2, 4 The desired horizontal image resolution. Use '1' for full resolution, '2' for subsampling by factor 2, and '4' for subsampling by factor 4. Default: 1.
VerticalResolution 1, 2, 4 The desired vertical image resolution. Use '1' for full resolution, '2' for subsampling by factor 2, and '4' for subsampling by factor 4. Default: 1.
ImageWidth 0, width The width of the desired image part (use '0' for the maximum image width). Default: 0.
ImageHeight 0, height The height of the desired image part (use '0' for the maximum image height). Default: 0.
StartRow 0, row The row coordinate of the upper left pixel within the desired image part (use '0' for the complete image). Default: 0.
StartColumn 0, column The column coordinate of the upper left pixel within the desired image part. Default: 0.
Field --- Ignored.
BitsPerChannel --- Ignored.
ColorSpace --- Ignored.
Gain --- Ignored.
ExternalTrigger --- Ignored.
Note that the external trigger mode depends on the settings of the camera file described below!
CameraType cam_name 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.

<GINGA++M4> You have to use the same camera name for pair port, which consists of even and odd channel number. Channel 0 and 1 compose pair port.
<GINGA++M2> You have to use the same camera name for the same board.
Device 'GINGA++M4', 'GINGA++M2' Board type of the GINGA++ board.
Port 0, 1, 2, ... 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():

'continuous_grabbing' 'enable', 'disable' Activate/deactivate continuous grabbing mode. Default: 'disable'.
'external_drive' 'enable', 'disable' 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. Default: 'enable'.
'external_trigger' 'true', 'false' 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' msec Timeout value for image acquisition in milliseconds. Default: 5000.
'long_exposure_time' 1 ... 256 Specify long exposure time.
'sequence_grabbing' 'enable', 'disable' Activate/deactivate sequence grabbing mode. Default: 'disable'.
'shutter_speed' > 0 Specify shutter speed (exposure time) in seconds if camera is used in reset shutter mode.
'signal_range_max' -0.285 ... 0.990 Specify 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 Specify 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' 'enable', 'disable' 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. Default: 'disable'.
'start_async_after_grab_async' 'enable', 'disable' By default, at the end of grab_image_async a new asynchronous grab command is automatically given to the frame grabber board. If the parameter 'start_async_after_grab_async' is set to 'disable' this new grab command is omitted. Default: 'enable'.
'volatile' 'enable', 'disable' In the volatile mode the two frame grabber 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! Default: 'disable'.
'wait_frame_exposure_timeout' > 0 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.
Default: 1000.
'do_abort_capture' --- Abort the current image acquisition.
'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.

Parameters for get_framegrabber_param():

Additional parameters supported by get_framegrabber_param only. Note that all parameters supported by set_framegrabber_param except the ones with prefix 'do_' can also be accessed by get_framegrabber_param.

'revision' revision The revision number of the HALCON Ginga++ frame grabber interface.
'wait_frame_exposure' 0, 1, 2 Wait for the completion of camera exposure for the period specified by 'wait_frame_exposure_timeout'. The possible return values are
  • 0 (failed): Failure of the waiting process for the completion of camera exposure.
  • 1 (timeout): Inform that the time specified by the parameter 'wait_frame_exposure_timeout' has passed.
  • 2 (success): Success of the waiting process for the completion of camera exposure.

Release Notes

  • Revision 2.3 (Dec 17, 2004):
    • 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).

© Copyright 2012, MVTec Software GmbH, corporate/legal/privacy information






Last modified: Wed Aug 3 19:13:56 CEST 2005