Knowledge · Machine vision
The cameras deliver their images, but the inspection result must reach the machine in time. Choose your industrial vision PC around the data rate and the complete inspection. Use this guide to specify processing, memory and interfaces for a quotation and a practical acceptance test.

For each camera, record resolution, the transmitted pixel format and frames per second. Include simultaneous triggers, images required per part and the deadline for delivery to the PLC. Megapixel count alone tells you little about processing demand.
Describe the processing sequence: localisation, measurement, code reading or inference with a trained model. Benchmark the complete procedure on the intended configuration using representative images. Some steps execute sequentially; extra CPU cores shorten that chain only when the software can use them.
For uncompressed images, data rate equals width × height × bytes per pixel × frames per second. Add the streams and assess each shared link. A faster processor cannot fix an overloaded network interface. Sufficient network bandwidth also does not establish that processing will meet its deadline.
Measure from trigger to receipt of the result by the machine controller. Include exposure, readout, transfer, queues, processing and communication. Specify both the allowed delay for each part and the sustained part rate. Test the case where every camera delivers an image at once.
For conventional image processing, the CPU is often the starting point. Compare configurations using identical images, procedures and software versions. Record processing times, per-core utilisation and queue behaviour. An office-workload benchmark does not establish inspection capacity.
A GPU matters when the selected functions support it, for example with certain deep-learning models. Verify supported hardware, drivers, video memory and runtime for the software release. Integrated display graphics do not establish compatibility with a required acceleration path. For an expansion card, check the slot, power supply, cooling and physical clearance.
Allow RAM for the operating system, application, camera buffers and intermediate results. One Mono8 frame in the example contains 5,013,504 bytes. Buffering 100 frames per camera for two cameras requires about 1.00 GB for source images alone. Conversion to colour or a wider processing type can add memory demand.
Decide whether to save every image, rejects only or a sample. The two example streams would require about 721.94 GB per hour if stored continuously without compression, excluding file metadata. Calculate capacity from image size × saved frames/s × retention time, and measure actual file sizes when using compression.
Check sustained write speed, write endurance and behaviour when the disk fills up. Keep image saving enabled during acceptance testing. Define whether inspection continues, stops or raises an alarm if storage becomes unavailable.
Count camera interfaces, machine-network connections and expansion cards separately. Establish which ports share an internal controller or link. For USB, inspect the shared host controller; for GigE, check each interface and any common uplink.
Power over Ethernet, or PoE, supplies compatible cameras through the image-data cable. This can remove the need for a separate injector. Check camera compatibility, power per port and the combined budget. A compatible PoE switch or separate camera supply is also an option.
The Hikrobot datasheet specifies four GigE ports with a combined 20 W PoE load for MV-VC2143-128G40-NN and -1T. The listed MV-VC2140 variants do not support PoE. Four sockets therefore do not establish that four arbitrary cameras fit the power or processing budget.
Use the temperature around the PC inside the cabinet. Check mounting orientation, clearance, heat removal and contamination against the model manual. The cited VC2140/VC2143 datasheet specifies a 0–50 °C operating range and non-condensing humidity. Do not apply that range to other controllers without checking.
Run sustained-load tests after the cabinet reaches operating temperature. Check for heat-related slowdown and missed deadlines. Plan system-image restoration, storage replacement and recovery of recipes, drivers and licences. These procedures affect how long the machine remains unavailable after a failure.
Complete this worksheet before requesting a configuration. Agree limits with production and machine engineering, then have the complete application tested on the proposed PC.
| Requirement | Record and verify |
|---|---|
| Cameras and images | Model, count, resolution, pixel format, frame rate and simultaneous triggers. |
| Result deadline | Maximum trigger-to-result time, sustained part rate and response to a missed deadline. |
| Software and processing | Release, modules, licence, representative images and CPU/GPU compatibility. |
| Memory and storage | Buffer depth, saving policy, retention period and disk-full response. |
| Machine and environment | Interfaces, PoE budget, I/O, cabinet temperature, mounting and recovery procedure. |
| Sustained-load test | All cameras, saving, operator interface and communication active; no lost images and results within the agreed deadline. |
Include interfaces, camera power, operating system, licences, integration and acceptance testing in the investment. Compare recurring maintenance, storage and support costs. Any payback calculation needs measured changes in manual inspection effort, rework and downtime. A processor name or camera count cannot predict those returns.
Integrated PoE can remove separate camera supplies and injectors. These product families provide starting points for selection. Test the complete inspection and confirm the specification of the exact order code.

The cited VC2143 variants combine an Intel N97, 8 GB RAM and four GigE ports sharing a 20 W PoE budget. Verify that your procedure meets its deadline.
Explore models and discuss your configuration

Explore this family when you need different processor, storage or expansion options. PoE and expansion capabilities vary by model; check the complete order code.
Explore models and discuss your configuration
Model data comes from the Hikrobot MV-VC2140/VC2143 datasheet and documentation on the linked product pages, checked on 15 November 2026. Calculations use uncompressed Mono8 pixel data and decimal MB/GB. They are sizing examples, not measured performance.
Share sample images, camera settings and the time available per part. These provide a practical basis for discussing the trial and computer configuration.
Discuss a feasibility trial