Vision processing unit (vision controller for multiple industrial cameras)
Vision processing units · camera ports and PoE, factory protocols, isolated I/O and encoder input, processor and software, per-port image bandwidth
A vision processing unit, or vision controller, is a fanless industrial computer dedicated to acquiring images from two or more machine vision cameras or 3D sensors, running inspection software on them and passing results to the PLC through factory protocols and discrete I/O. Ask three things first: how many cameras of which interface it acquires from at the frame rates you need, which factory protocols and I/O it provides for triggering and results, and which processor and vision software it ships with.
Vision controllers and vision processing units that acquire from multiple GigE Vision, USB3 Vision or 3D sensors and run machine vision software for the line. Microcontroller chips are covered on the Microcontrollers (CPU / MCU) page; smart cameras with built-in processing, lighting and general industrial PCs are outside this page.
CNFX editorial research · Sources checked October 12, 2026 · 3 sources
Count the camera ports and check bandwidth per port
Design World's report on Cognex's VC5 vision controller states that it connects directly to up to four DS1000 series 3D laser displacement sensors or Cognex GigE Vision area scan and line scan cameras, is powered by a dual-core CPU with a dedicated real-time subsystem for factory protocols and precision I/O, comes pre-installed with Cognex Designer software, and is built with OEM components for a minimum three-year availability. [1] Cognex's product listing on MarkLines adds four independent GigE channels with PoE for asynchronous image acquisition, a fanless enclosure with SSD, and VisionPro software preinstalled. [2]
Graftek's listing for the Matrox 4Sight EV7 (model EV7I5M16DA) describes a fanless unit with an Intel Core i5-1250PE, 16 GB DDR5 RAM, a 256 GB M.2 SSD and Windows 10 IoT Enterprise, PoE-enabled ports and support in its description for four GigE Vision and four USB3 Vision cameras; its technical details list six GigE Vision inputs, two USB3 inputs and 8 GB storage memory, which do not match the description, so confirm the port count and storage with the supplier. [3]
Editorial calculation: one Gigabit Ethernet channel carries at most 1,000 Mbit/s, or 125 Mbyte/s before protocol overhead, so a 5-megapixel 8-bit camera (about 5 Mbyte per frame) is limited to about 125 ÷ 5 = 25 frames per second per channel at most; four independent channels, as on the VC5, let four such cameras run in parallel rather than sharing one link.
Give the supplier the cameras and sensors (interface, resolution, frame rate, number), PoE needs, inspections and cycle time, software platform and licences, factory protocol and PLC, discrete I/O and encoder needs, operating environment and mounting, operating system and lifecycle requirements, and quantity.
02
Connect it to the line: protocols, discrete I/O and encoder
Cognex's MarkLines listing gives the VC5's factory protocols as Allen-Bradley/Rockwell EtherNet/IP, Siemens PROFINET, Mitsubishi SLMP and TCP/IP, its discrete I/O as 24 V optically isolated, 8 inputs and 16 outputs with a dedicated CPU, and a two-phase encoder input, and names automotive, electronics, code reading and sheet inspection among its uses. [2]
Graftek's EV7 listing gives 8 bidirectional TTL input channels with the same number of TTL outputs, 8 isolated inputs, 8 isolated outputs and one quadrature encoder input, and describes the unit as pre-loaded with Matrox MIL X and Matrox Design Assistant X run-time environments, with partial licences. [3]
Editorial note: an encoder input lets the controller time image capture to conveyor position, and isolated outputs carry pass/fail results to the PLC; count both against your stations before choosing a unit, and add an I/O module if they run short.
03
Processor, camera ports, real-time I/O and encoder input
The real-time I/O subsystem (24 V isolated, with its own CPU on one unit) and the encoder input link image capture to the moving line.
Cognex Designer/VisionPro; MIL X/Design Assistant X. [1][2][3]
Platform and licences.
04
Camera channels, PoE, isolated I/O and memory for a vision controller
Compare the camera channel and isolated I/O rows first: the published units range from four PoE GigE channels with 8 inputs and 16 outputs to GigE and USB3 ports with TTL lines.
Field
What it means and published values
Ask the supplier for
Processor clock speed (GHz)
Example: Intel Core i5-1250PE on one unit; dual-core CPU on another. [3][1]
Explore company information and manufacturing capabilities, then discuss the scope of your project with a relevant supplier.
Share this page
Compiled and source-reviewed by the CNFX editorial team.
Each manufacturer above links to the page on that company's own website where the product is listed, with the date we checked it. How we source and review
· Page last updated 13 October 2026
Buyer questions
How many cameras can a vision controller run?
Cognex describes its VC5 as connecting up to four GigE Vision cameras or 3D displacement sensors on four independent PoE GigE channels. [1][2]
Which factory protocols do vision controllers support?
The VC5 listing gives EtherNet/IP, PROFINET, Mitsubishi SLMP and TCP/IP. [2]
Why does a vision controller need an encoder input?
Both reviewed units list one; it lets capture be timed to conveyor position (editorial note). [2][3]
How fast can one GigE port deliver images?
At 125 Mbyte/s before overhead, about 25 frames per second of a 5-megapixel 8-bit image (editorial calculation). [2]
Sources and what still needs a direct check
Sources checked 2026-10-12. Design World and MarkLines publish Cognex's descriptions of its VC5 controller; Graftek is a distributor listing the Matrox 4Sight EV7. Figures are the makers' own.
