Version: 16.3.1.167ea6ecff

Frame Grabber & Camera Drivers

Introduction

In addition to the cameras and framegrabbers that it directly supports, 3DExpress is also able to use any fgd driver from SAL3D. In this case, the user can specify any driver options in the fgd config string.

Specified in each driver is the version of the manufacturer SDK used to build it. It should be possible to recompile the driver (as we provide the sources) for newer versions of the SDK, provided that the API has not changed.

Frame Grabber drivers list:

Camera drivers list:

Others:

Silicon Software microEnable III/IV (sisome4.fgd)

Note
The driver has been built using the SDK v5.2.1
Warning
This framegrabber only accepts multiples of seconds for timeouts, instead of milliseconds. See sal3d::FrameGrabber::wait .

This driver allows acquiring frames from a Silicon Software microEnable III/IV frame grabber card. It initializes the card from a MCF config file on first load of the driver. If the FrameGrabber::FrameGrabber constructor passes a null string parameter to the driver, on fgd loading it will pop up a Windows UI file open dialog to get the MCF file. Otherwise, the string parameter should be a pipe "|" separated list of the following parameters:

For example:

Following is a list of considerations regarding the driver and the way it works:

DALSA Sapera supported cards (sapera.fgd)

Note
The driver has been built using the SDK v7.00

This driver allows acquiring frames using the Sapera library backend. It has been tested and is known to work at least with the DALSA X64 XCelera-CL PX4. The configuration parameter fed to the constructor may be empty, in which case a dialog will appear to choose from a CCF configuration file. Otherwise, it must be a pipe "|" separated combination of the following parameters:

For example:

Remarks
It is possible to specify a configuration file and several of the other parameteres, like size. In this case, the ones prevailing are the ones specified through the parameter, not the ones in the configuration file.

Following is a list of some details concerning how the driver works:

Imperx supported cards (imperx.fgd)

Note
The driver has been built using the SDK v1.2.0.78

This driver allows capturing frames from an Imperx frame grabber. It has been tested with a FrameLink Express card but it should work with other models.

The driver expects a configuration parameter. If it is empty, a dialog will appear asking for a configuration file. Otherwise, a pipe "|" separated list of the following parameters may be given (the configuration file is mandatory):

Example:

Warning
The reconfig function is still not supported.

Matrox supported cards (matrox.fgd)

Note
The driver has been built using the SDK v9.00.1950(R2)

This driver allows acquiring frames from a Matrox frame grabber card, and has been tested with a Solios eV-CL.

The configuration parameter fed to the constructor may be empty, in which case a dialog will appear to choose from a DCF configuration file. Otherwise, it must be a pipe "|" separated combination of the following parameters:

For example:

Following is a list of considerations regarding the driver and the way it works:

Bitflow supported cards (bitflow.fgd)

Note
The driver has been built using the Bitflow SDK v5.40

This driver allows capturing frames from a BitFlow frame grabber.

The driver allows a configuration parameter. A pipe "|" separated list of the following parameters may be given:

Example:

Warning
The reconfig function is still not supported.

IDS Camera (ids.fgd)

Note
The driver has been built using the SDK v4.40

The IDS driver is tested and known to work with a USB microEye LE, but it should support any GigE or USB camera of the manufacturer.

Several configuration parameteres can be given to the driver through the configuration parameter, or the FrameGrabber reconfig method,all of them separated by a pipe "|", and value assigned with the equal "=" sign:

You can check your camera manual for valid values of those parameters.

Example:

Point Grey Cameras (flycapture.fgd)

Note
The driver has been built using the FlyCapture SDK v2.8.3.1

The FlyCapture driver is tested and known to work with a Firefly MV USB2, Chameleon USB2 and Flea3 GigE, but it should support any camera of the manufacturer.

Warning
In order for the driver's lost frames method to work, the frame counter embedded information is enabled when the driver is loaded. This means that the first 8 pixels of the first row of the image are overwritten with this information.
The camera may not accept any ROI values, only some. This can make the driver fail to load.

Several configuration parameteres can be given to the driver through the configuration parameter, all of them separated by a pipe "|":

You can check your camera manual for valid values of those parameters.

Example:

Ximea cameras (ximea.fgd)

Note
The driver has been built using the Ximea SDK v1.0

The Ximea driver is tested and known to work inside Currera cameras. but it should support any camera of the manufacturer.

Several configuration parameteres can be given to the driver through the configuration parameter, all of them separated by a pipe "|":

You can check your camera manual for valid values of those parameters.

Example:

Pleora cameras (pleora.fgd)

Note
The driver has been built using the Pleora eBUS SDK 3.1.3

This driver has been tested with Photonfocus and JAI GigE cameras.

Several configuration parameteres can be given to the driver through the configuration parameter, all of them separated by a pipe "|":

Example:

File Frame Grabber (file.fgd)

With this driver, Frames stored in files can be provided as Frames acquired through a FrameGrabber. This may help debugging the Frame processing part of a program. The supported Frame file types are related to the Frame::Frame constructor which reads the picture from a file.

When loading the driver, if the string parameter of the FrameGrabber::FrameGrabber constructor is null, it will pop up a dialog asking for a list of picture files to open. Otherwise it expects a parameter specifying either a picture file or a file containing a list of pictures to be opened, in the form:

Example:

All files are read at the initialization of the FrameGrabber driver, and they are stored in memory until destruction of the object (unless memory=0 is specified). This way, Frames can be delivered quickly to the program grabbing from the related FrameGrabber object, although being constrained by the virtual memory available to the program.

After delivering the last file on the list, the first file will be delivered on next FrameGrabber::frame(). The FrameGrabber::wait() function will never block.

On reconfiguration, the image files are re-read from the given parameter.

Kinect Driver (kinect.fgd) (not available for WinXP)

This driver is capable of getting live images, depth images, or COP reconstructions of the scene. To use it, there is a specific interface named KinectFrameGrabber.

There is a single parameter that affects the Kinect behaviour: