EGrabberBridge - Using Images from eGrabber Sources¶

EGrabberBridge and EGrabber¶

EGrabberBridge is a user-friendly namespace of conversion classes. These classes perform the direct conversion from a buffer originating from eGrabber, the API of eGrabber sources, to an eVision data container.

See EGrabber documentation for more information about the eGrabber library.

EGrabber Sources¶

The possible eGrabber sources are the following:

Euresys Coaxlink frame grabbers
Gigelink vision cameras

Prerequisites¶

Open eVision 2.9 (or newer)
A Coaxlink frame grabber: Coaxlink 11.0.3 (or newer) or eGrabber 12.8 (or newer)
A Gigelink vision camera: eGrabber 12.8 (or newer)

Libraries¶

To use EGrabberBridge in C++, include the main EGrabber headers before the eVision header.
```
#include "EGrabber.h"
#include "FormatConverter.h"
#include "eVision.h"
```
To use EGrabberBridge in C#, reference the assembly in addition to the eVision .NET assembly.

Data Containers¶

EGrabberBridge is part of the main eVision header.
The FormatConverter header is required only if you need to perform pixel format conversion. See the EGrabberBridge code snippets.

Each EGrabberBridge class derives from a specific data container.

The following classes are implemented:

Base class	EGrabberBridge class	Corresponding GenAPI pixel format
`EImageBW8` ^.NET ^Python	`EGrabberImageBW8` ^.NET	`Mono8, BayerGR8, BayerRG8, BayerGB8, BayerBG8`
`EDepthMap8` ^.NET ^Python	`EGrabberDepthMap8` ^.NET	`Coord3D_C8`
`EImageBW16` ^.NET ^Python	`EGrabberImageBW16` ^.NET	`Mono16, BayerGR16, BayerRG16, BayerGB16, BayerBG16`
`EDepthMap16` ^.NET ^Python	`EGrabberDepthMap16` ^.NET	`Coord3D_C16`
`EImageC24` ^.NET ^Python	`EGrabberImageC24` ^.NET	`BGR8`

These classes have 2 constructors:
- 1 that requires only an EGrabber buffer descriptor (see EGrabber reference).
- 1 that requires an EGrabber buffer descriptor and an additional FormatConverter parameter used to perform the conversion from the pixel format of the buffer to the pixel format of your EGrabberBridge class, if these are different (see Using EGrabberBridge with Format Conversion code snippet).
Scope and copy of the buffer:
- eVision does not perform any copy of the buffer unless you require a pixel format conversion.
- The availability of the EGrabberBridge data container buffer depends on the EGrabber buffer object or on the FormatConverter object if a copy is performed.

Examples and Code Snippets¶

A sample (UsingEGrabberBridge) illustrates the use of the EGrabberBridge classes using callbacks. The sample is available in C++ and in C# and is present in its corresponding samples solution under the EGrabberBridge name.
A code snippet (Using EGrabberBridge with Format Conversion) is available to show how to use EGrabberBridge to perform the inversion of an image acquired using EGrabber.
Camera and GenTL parameters can be handled through the EGrabber Object setters and getters (see EGrabber documentation).
You can also test out parameters using the GenTL application (see GenTL documentation).