Frame Grabbers in Machine Vision
A frame grabber is a PCIe expansion card that sits between a camera and a host PC, capturing image data from the camera interface and transferring it to system memory via direct memory access (DMA). For cameras connected over GigE Vision or USB3 Vision, the standard network stack or USB controller on the host PC handles this transfer without additional hardware. For higher-bandwidth interfaces such as Camera Link and CoaXPress, a dedicated frame grabber is required because these interfaces rely on specialized receiver hardware to acquire, buffer, and transfer the incoming image data to system memory while supporting their high data rates and deterministic triggering features.
Frame grabbers have been part of industrial machine vision since the analog camera era. Their role has evolved as digital interfaces replaced analog video signals, but the core function remains: manage the transfer of image data from the camera to system memory while providing predictable, low-latency acquisition and synchronization.
How a Frame Grabber Works
A frame grabber connects to the host PC via a PCIe slot, which provides the internal bandwidth needed to move large image buffers directly into system RAM without moving large image buffers directly into system RAM using DMA, minimizing CPU involvement in the data transfer. The card receives image data from the camera over the specified interface, whether Camera Link, CoaXPress, or in some configurations analog video, and writes each frame into a pre-allocated buffer in host memory. The application software then reads from that buffer for processing.
Beyond raw data transfer, most frame grabbers manage several functions that benefit from dedicated hardware implementation. Hardware-based triggering allows the card to respond to an external signal, such as a photoelectric sensor or encoder pulse, with deterministic latency. Strobe control synchronizes an external light source with each camera exposure. In multi-camera configurations, the frame grabber coordinates capture timing across all connected sensors so that frames from each camera align in time.
Some frame grabbers also include an FPGA that can perform on-card image pre-processing, such as tap geometry correction on Camera Link cameras or Bayer demosaicing, before the data reaches system memory. This offloads image processing from the host CPU and can reduce the latency between image acquisition and downstream processing.
When a Frame Grabber Is Required
The need for a frame grabber is determined primarily by the camera interface. For most mainstream machine vision interfaces, no frame grabber is needed: the host PC handles data transfer directly through the standard USB controller or network interface card.
|
Camera Interface |
Frame Grabber Required |
Notes |
|
GigE Vision (1G / 5G / 10G) |
No |
Standard NIC handles transfer; dedicated NICs are commonly used in demanding applications |
|
USB3 Vision |
No |
USB 3.0 controller on the host PC is sufficient for most cameras |
|
Camera Link (Base / Medium / Full / Extended) |
Yes |
Requires a compatible Camera Link frame grabber |
|
CoaXPress (CXP-6 / CXP-12) |
Yes |
Requires a CXP frame grabber; multiple acquisition ports are available for higher aggregate bandwidth |
|
Analog (composite, RS-170) |
Yes |
Frame grabber performs A/D conversion and digitisation |
The distinction matters for system budgeting. A CoaXPress frame grabber is a meaningful cost item, and adding one to a Camera Link system represents an additional PCIe card, occupied expansion slot, and software driver dependency. For applications where GigE Vision or USB3 Vision can meet the bandwidth and triggering requirements, omitting the frame grabber simplifies the system and reduces cost.
The practical threshold is bandwidth and determinism. GigE Vision at 1 Gbps suits many standard inspection applications. When an application's bandwidth, latency, synchronization, or deterministic triggering requirements exceed what standard GigE Vision or USB3 Vision systems can practically support, Camera Link or CoaXPress with a frame grabber becomes an appropriate choice.
Frame Grabbers in Machine Vision Applications
Frame grabbers are most commonly specified for high-speed and high-resolution applications where the image data rate exceeds what standard interfaces can sustain, or where the system requires deterministic hardware triggering that is difficult to achieve reliably in software alone.
|
Application |
Interface Typically Used |
Why a Frame Grabber Is Appropriate |
|
High-speed web inspection (printing, film, foil) |
Camera Link or CoaXPress |
Line scan cameras at high line rates generate sustained data rates that require dedicated PCIe bandwidth |
|
Semiconductor wafer inspection |
Camera Link Full / Extended |
Very high resolution sensors at moderate frame rates; precise synchronization with the motion stage encoder |
|
High-frame-rate area scan inspection |
CoaXPress multi-lane |
High sustained image bandwidth benefits from CXP link aggregation and PCIe-based acquisition. |
|
Legacy analog camera integration |
Analog frame grabber |
Digitises composite or RS-170 signals from installed base cameras |
|
Multi-camera synchronised capture |
CoaXPress or Camera Link |
Hardware synchronisation across multiple sensors within a single PCIe card |
For applications using GigE Vision or USB3 Vision cameras at standard frame rates and resolutions, a frame grabber is generally not required. The companion articles on GigE Vision and USB3 Vision cover interface selection in detail for those cases.
Frequently asked questions
No. Whether a frame grabber is needed depends on the camera interface, not the camera itself. GigE Vision and USB3 Vision cameras connect directly to the host PC without additional hardware, using the standard Ethernet NIC or USB controller. Camera Link and CoaXPress cameras require a compatible frame grabber. If you are selecting a camera interface for a new system, the decision about whether to include a frame grabber should be made at the same time as the interface decision, since the two are interdependent.
A network interface card (NIC) handles Ethernet traffic using the standard TCP/IP or UDP protocol stack managed by the operating system. A frame grabber is a dedicated capture card that bypasses the OS protocol stack entirely, writing image data directly into host memory via DMA. This gives the frame grabber deterministic transfer behaviour and lower latency than a general-purpose NIC. For GigE Vision cameras, a standard or dedicated NIC is sufficient; for Camera Link or CoaXPress, a frame grabber is required.
Yes, many frame grabbers provide multiple input ports, allowing several cameras to connect to a single card. CoaXPress frame grabbers commonly offer two or four input ports. The card manages synchronisation across all connected cameras and aggregates their data streams into a single DMA transfer pipeline. The maximum number of cameras is constrained by the total available PCIe bandwidth on the card relative to the aggregate data rate of the connected cameras.
Most frame grabbers for Camera Link and CoaXPress are GenICam-compliant, meaning they expose a standard interface for camera control and image acquisition that major machine vision software libraries support. Halcon, OpenCV, MATLAB, and The Imaging Source's own SDK and tiscamera library all provide acquisition pathways that work with GenICam-compliant devices. Confirm GenICam compliance and the availability of a driver for your target OS before specifying a frame grabber.