Wiki¶

1) Soft Hyperproto¶

2) API VIALUX¶

2.1) ALP-4.1 basic (Accessory Light modulator Package)¶

ALP-4 basic supports DLP® Discovery™ 4100 based hardware: ALP-4.1 is the software for ViALUX V-9500/V-9600 Modules (VX4100 Boards) and for the DLP® Discovery™ 4100 Developer Kit.
The ALP basic suite comes with all components required for the use of the DLP® Discovery™ Boards including a software DLL. The following notes describe general software organization rules applicable to the whole library.
The image display on a DMD is divided into two different operations. Data operations load image data in on-chip SRAM memory cells. In a subsequent reset operation the mirrors are flipped to 12° or -12° positions, respectively, according to the SRAM data.
There are two types of data operations. Loading data (AlpbDevLoadRows) transfers image data row by row to the DMD. The clear operation (AlpbDevClear) sets the memory content of whole reset blocks to logic ’0’.
A Reset operation (AlpbDevReset) addresses the micro mirrors in terms of reset blocks. Single blocks, groups of two or four blocks, or even all mirrors (global reset) can be reset at the same time.
The reset operation itself takes the same time to finish, independent of how many mirrors are affected.
ALP-4.1 basic APIs reside in different DLL files: alp41basic.dll.
There are two configurations of the ALP basic DLL having different names. Alp*basic.dll uses the “cdecl” calling convention. The library alp*basicS.dll exports functions using the “stdcall” calling convention
and redirects them to the cdecl DLL. This might be required for development environments that do not support the C calling convention. Function names and argument lists are equal in both configurations.
For C and C++ users a header (alpbasic.h) and a static library ( alp41basic.lib) file is provided together with the DLL.
ALP basic devices are identified in function calls by handles of type ALPB_HDEVICE. This handle is generated by AlpbDevAlloc.

Dongle protection
ALP-4.1 basic is protected by a hard-lock USB key

bug api windows7 ?

2.2) ALP-4.1 high-speed¶

Dongle protection
ALP-4.1 high-speed is not protected by a hard-lock USB key any more. The return code
ALP_ERROR_DONGLE has been removed.

3) NI IMAQdx¶

fig : General Steps for Designing a Vision Application

fig : Inspection Steps for Building a Vision Application
IMAQdxEnumerateCameras (IMAQdxCameraInformation cameraInformationArray[], uInt32* count, bool32 connectedOnly);

This is the information that was mentioned in the LabVIEW Documentation:

Camera Information Array is an array of interface files that are on the host computer. This includes cameras that are currently connected or that were previously connected.

- Type has a value of 3. This designates an NI-IMAQdx interface file.

- Version is the version of the interface file. This number may increment with different versions of the driver as the format of the interface file changes.

- Flags is a bitwise mask of the current interface status. If bit 0 is on (value = 1), the interface represents a camera that is currently connected. If bit 0 is off (value = 0) , the interface represents a disconnected camera.

- SerialNumberHigh is the upper 32-bits of the interface serial number. Every camera has a unique value for SerialNumberHigh.

- SerialNumberLow is the lower 32-bits of the interface serial number. Every camera has a unique value for SerialNumberLow.

- BusType specifies the bus type for the camera.

- InterfaceName is the name of the interface. Use this name when opening the interface.

- VendorName is the vendor name of the camera designated for this interface. VendorName varies from camera to camera.

- ModelName is the model name of the camera designated for this interface. ModelName varies from camera to camera.

- CameraFileName is the name of the camera file that this interface uses. The camera file contains all the settings for a given camera. You can configure and save these settings from Measurement & Automation Explorer (MAX).

- CameraAttributeURL is the URL of the XML file that describes the camera attributes.

3.2 The camera can be opened in MAX, but it does not acquire images¶

Case 1: The High Performance Driver for Intel Pro/1000 NIC is not installed.
http://www.ni.com/product-documentation/5846/en/

....

....

Allied Vision Vimba GigE Driver 2.1.3

https://cloud.laas.fr/index.php/apps/files/?dir=%2FShared%2Fhyperproto%2Fcamera%2Fsofts

Jumbo Frames enabled in Network Adapters (size of 9014 bytes)

4) Common Vision Blox CVB (by STEMMER IMAGING)¶

At the heart of Common Vision Blox is the Image Manager.
Probably the most essential feature of the Image Manager is the implementation of a hardware abstraction layer that allows programmers to access a variety of entirely different image sources (ranging from simple file-based image sources to high performance frame grabbers and covering all relevant interface and acquisition technologies available for machine vision) through the same simple API while still enabling access to a fair amount of hardware specific functionality.

That way, with Common Vision Blox a programmer does have the choice to either write completely hardware independent machine vision applications (that allow for simple drop-in replacement of the acquisition hardware) or take best advantage of the details and features his hardware offers.

For a list of supported acquisition devices you can either have a look at the Drivers folder of your Common Vision Blox DVD, or visit www.commonvisionblox.com.

In addition to the hardware abstraction layer, the Image Manager provides functionality for handling image data like

·access to image data and properties

·display images in a fast and interactive display with non-destructive overlay capabilities

·modify image data by copying them, creating new views on them or using basic transformation functions

·read and replay AVI, MPG or MP4 streams from disk

·read/write image files from/to disk in various formats

The Image Manager is the most basic module of Common Vision Blox that may be purchased separately.

The Common Vision Blox CameraSuite in terms of functionality is almost identical to the Common Vision Blox Image Manager, however it is limited to those cameras that are compatible with it and does not come with a dongle to which Common Vision Blox tools may be license (see Licensing Concept).

The CameraSuite can not be purchased individually - it comes for free bundled with those cameras that are supported by the Camera Suite like e.g. the the CVC camera series from STEMMER IMAGING or the AreaScan 3D cameras from VRmagic, as well as all GigE Vision and USB3 Vision cameras sold by STEMMER IMAGING.

If more functionality than what the Image Manager and the CameraSuite offer is required, then we recommended looking at the Common Vision Blox Foundation Package .

This package includes the Image Manager and extends it by adding state-of-the-art image processing functionality which many machine vision applications will need, like

·arithmetic and logic operations on image data

·blob analysis

·color space conversions

·correlation

·Fourier transform

·various filter functions for de-noising, edge detection and morphology operations

·statistical evaluation of image data

·advanced transformation functions for image data

Both basic packages, the Image Manger or the Foundation Package, may be combined with a number of more sophisticated Tools for specialized tasks like bar code reading, OCR or print inspection.

These tools are sold independently, offering customers a flexible and cost-effective choice of modules to build their machine vision systems from.

On the Windows™ platform, Common Vision Blox may be used with C/C++, the .Net programming languages, or Delphi.

On the Linux platform it may be used with the C/C++ compilers of the GNU Compiler Collection.

For an explicit list of supported programming environments and versions please refer to the Common Vision Blox Release Notes (located in your start menu and in the doc sub-directory of your Common Vision Blox installation, but also available on www.commonvisionblox.com).