To select a certain camera description to be used to prepare the capture device for the expected data the property mvIMPACT::acquire::CameraSettingsFrameGrabber::type can be modified. Note For devices that don't support camera descriptions at all, creating an instance of mvIMPACT::acquire::CameraDescriptionManager will raise an exception, that should be handled appropriately. One or more of this lists might be empty for a device, which indicates, that this device doesn't support this particular group of descriptions. These objects will contain different lists for each camera class. Which basic "camera description" classes are supported by an individual device can be seen directly after the device has been initialized by creating and instance of mvIMPACT::acquire::CameraDescriptionManager. See mvIMPACT::acquire::CameraDescriptionBase and derived classes to find out how the basic structure of these objects look. To reflect these device specific capabilities the "camera descriptions" have been grouped into different base classes. For example some capture devices will only be able to capture image data from standard video source such as a PAL or NTSC compliant camera, while others might only be capable to acquire data from digital image sources such as CameraLink compliant cameras. when dealing with interlaced cameras) that need to be reconstructed in a certain way to form the complete image.Įach capture device will support different sets of parameters. For instance this information may contain information whether the image is transmitted as a whole or if it's transmitted as individual blocks (e.g. A "camera description" is a certain set of parameters that should enable the capture device to cope with the incoming image data to reconstruct a correct image from the imaging device in the memory of the host system. The mvIMPACT Acquire interface addresses this necessity by the introduction of so called "camera descriptions". However in order to interpret the incoming data from an imaging device correctly, the capture device needs to be given a certain amount of information about the structure of the video signal. frame grabber) can process data from a wide range of imaging devices (e.g.
The iPORT CL-U3 External Frame Grabber family includes a range of solutions to meet specific system requirements, including products supporting extended operating temperature range, extensive GPIO functionality, and power over Camera Link (PoCL).Certain capture device (e.g. Integrated PLC and GPIO capabilities allow end-users to control, trigger and synchronize cameras and other vision system elements. With these external frame grabbers, video from Base and Medium mode Camera Link cameras is transmitted with low, predictable latency over a USB 3.0 link directly to existing ports on a broader selection of computing platforms, including laptops, embedded computers, and single-board computers.
Pleora’s iPORT™ CL-U3 External Frame Grabbers help designers leverage the performance attributes of USB 3.0 – including high-bandwidth output, power over cable, and computing platform choice – by converting Camera Link® cameras into native USB3 Vision™ cameras. Simple to integrate USB3 Vision video interface for Camera Link Cameras