HALCON 6.1 Frame Grabber Interface for Datacube Boards using VLL Software

This page provides the documentation of the HALCON frame grabber interface HFGDqVll.dll for the Datacube frame grabber boards MaxRevolution and all future products that use VLL software. Registered customers can download the latest revision of this interface from the MVTec WWW server.

Revision: 2.1

• Intel compatible PC with Windows 2000 or Windows XP.
• Installed Datacube VLL software from release CD after you have successfully installed HALCON software.
• HALCON frame grabber interface HFGDqVll.dll or parHFGDqVll.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.

• Support of multiple frame grabber boards.
• Two cameras per board with Dual Base Mode MaxRevolution, running independently.
• Support of a large variety of cameras based on the VLL system configuration files (SCI file).
• Support of line scan cameras.

• External trigger not yet supported.
• No subsampling or cropping of image parts.
• No LUTs.
• grab_region and grab_region_async not supported.

Parameters for open_framegrabber():

	Name		'DqVll'		The name of the HALCON frame grabber interface.
	HorizontalResolution		1		Ignored. The desired image resolution is set via the system configuration file specified in the CameraType parameter. Default: 1.
	VerticalResolution		1		Ignored. The desired image resolution is set via the system configuration file specified in the CameraType parameter. Default: 1.
	ImageWidth		0		Ignored. The desired image part is set via the system configuration file specified in the CameraType parameter. Default: 0.
	ImageHeight		0		Ignored. The desired image part is set via the system configuration file specified in the CameraType parameter. Default: 0.
	StartRow		0		Ignored. The desired image part is set via the system configuration file specified in the CameraType parameter. Default: 0.
	StartColumn		0		Ignored. The desired image part is set via the system configuration file specified in the CameraType parameter. Default: 0.
	Field		---		Ignored.
	BitsPerChannel		---		Ignored. The desired number of bits per image channel is set via the system configuration file specified in the CameraType parameter. Default: -1.
	ColorSpace		---		Ignored.
	Gain		---		Ignored.
	ExternalTrigger		'default'		Not yet supported. Default: 'default'.
	CameraType		'file'		Specify the system configuration file in this parameter with full path and name (e.g., 'C:\\Datacube\\Halcon.sci'). Note, that if you use several frame grabber handles at the same time, all following instances should be set to 'default' or point to the same SCI file! To check to alter the system configuration file, use the VllToolbox program delivered with the VLL software.
	Device		'0', '1', ...		The ID (assigned in the SCI file) of the frame grabber board (passed as a string!), i.e., '0' is, say, RevolutionF_00. Default: '0'.
	Port		number		The ID (assigned in the SCI file) of the VLL AcqManager of the board, 0 is AcqManager_00. In Dual Base Mode MaxRevolution, each camera port has an AcqManager. Default: 0.
	LineIn		---		Ignored.

Parameters for set_framegrabber_param():

	'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'.

Parameters for get_framegrabber_param):

Additional parameters supported by get_framegrabber_param only. Note that all parameters supported by set_framegrabber_param can also be accessed by get_framegrabber_param.

	'revision'		revision (string)		The revision number of the HALCON DqVll interface.

Dual Base Mode MaxRevolution has two Base Mode CameraLink ports and can interface up to two cameras running independently. In the SCI file create two AcqManagers for the board using VllToolbox. Each AcqManager then can be an instance for HALCON image acquisition.

Not yet supported in this revision.

• Revision 2.1 (Apr 8, 2002):
  
  • First official release (included in HALCON 6.1 CD).