// Key takeaways
- Define the fault and acceptance test before choosing a brand.
- Choose the device class first: vision sensor, smart camera, code reader, or cameras with a PC or controller.
- HIKROBOT, KEYENCE and Cognex cover several device classes; Basler’s documentation centres on cameras and pylon software.
- Use the same unseen sample set and production conditions for each candidate; a clean test bounds the miss rate, it does not prove zero.
- Score complete offers with fixed weights agreed before the results are in.
- Our HIKROBOT focus is a delivery choice, not proof that it wins every application.
What are you asking the station to decide?
Separate reading a code, matching it to an order, checking a missing component and measuring a dimension. A reader may decode a barcode without checking the order data. A presence sensor may find a missing cap without measuring its sealing surface. Define the required output and the consequence of a no-read or an uncertain result.
| If the task needs … | Start with | Because |
|---|---|---|
| One visible difference at one position | A vision sensor | Least engineering; OK/NG to the PLC |
| Several checks or OCR in one view | A smart camera | Tools and processing in the camera, no separate PC |
| Reading and matching codes | A fixed code reader | Built for decoding, with lighting and tuning for codes |
| Several cameras, line scan, 3D or heavy AI | Cameras with a vision controller or industrial PC | Processing, I/O and storage scale with the station |
| Integration into a machine you build | Board-level or compact cameras with an SDK | You own the application and its maintenance |
Which product families are comparable?
The matrix lines up the four vendors by device class, from their own pages: HIKROBOT’s product menu and catalogue (HIKROBOT product menu)(HIKROBOT catalogue 2025 Q4), Cognex’s In-Sight and logistics pages (Cognex In-Sight 3800)(Cognex logistics), KEYENCE’s vision sensor, vision system and code reader pages (KEYENCE vision sensors)(KEYENCE vision systems)(KEYENCE code readers), and Basler’s product documentation (Basler cameras). “Not in the pages we checked” means exactly that; ranges change, so confirm the current model in each quotation.
| Device class | HIKROBOT | Cognex | KEYENCE | Basler |
|---|---|---|---|---|
| Vision sensor (one simple check) | SC1000, SC2000, SC3000 | Not in the pages we checked | IV4, IV3, IV2, IV | Not in its camera documentation |
| Smart camera / vision system | SC5000X, SC6000 with VisionMaster tools | In-Sight 3800, 3900, 1750 | VS; controller systems CV-X, XG-X, VS-G | Not in its camera documentation |
| Fixed code reader | ID2000, ID3000, ID5000; logistics ID6000, ID7000 | DataMan, for example 380 and 390 | SR-X, SR-1000, SR-700, SR-L; logistics SR-5000, SR-2000, ST | Not in its camera documentation |
| Industrial cameras for a PC system | Area-scan CS, CE, CA, CH, CU and others; CL line scan | Not compared here | VJ series for PC environments | ace 2, ace, boost, dart, pulse; racer 2 line scan |
| 3D | DP laser profilers; RoboScan | In-Sight L38 | XG-X supports 3D cameras | blaze time-of-flight |
| Inspection software | VisionMaster | In-Sight Vision Suite | Built into each system | pylon with licensable vTools |
Software is part of the platform. VisionMaster offers graphical, SDK and operator-design development with deep-learning modules (HIKROBOT VisionMaster); Basler states that most pylon vTools need a licence after demo or evaluation periods (Basler vTool licensing). Ask every supplier for the licence list and how a licence is recovered after a PC or device is replaced.
How should you run a fair comparison?
- Give each candidate the same good and defective products, including borderline examples and normal packaging variation.
- Keep a separate evaluation set that was not used for setup or training. Record misses, false rejects and no-reads separately.
- Test actual exposure, speed changes, product spacing, glare, changeovers and stop/restart behaviour.
- Challenge the complete chain: trigger, image, decision, PLC tracking, reject confirmation and alarm.
- Agree who may adjust recipes and how a software update or replacement camera is revalidated.
How big should the challenge set be? A run with no misses bounds the miss rate; it does not prove zero. Using the Wilson method in NIST’s handbook (NIST e-Handbook, 7.2.4.1), the bounds are:
| Challenge units with no misses | 95 % one-sided upper bound on the miss rate |
|---|---|
| 30 | about 8.3 % |
| 100 | about 2.6 % |
| 300 | about 0.9 % |
| 1,000 | about 0.27 % |
How do you score the offers?
Agree the weights before the results are in, score each offer on evidence, and keep the scores with the test records. The example uses invented offers to show the arithmetic: B wins on the sample result and price, A wins overall because it demonstrated failure handling and named local support. Your weights may differ; the discipline of fixing them first is what matters.
| Criterion | Weight | Offer A (score 1–5) | Offer B (score 1–5) | A weighted | B weighted |
|---|---|---|---|---|---|
| Result on your sample set | 35 % | 4 | 5 | 1.40 | 1.75 |
| PLC, data and failure handling demonstrated | 20 % | 5 | 3 | 1.00 | 0.60 |
| Lifecycle: licences, backups, versions | 15 % | 4 | 3 | 0.60 | 0.45 |
| Named local support and spares | 15 % | 4 | 2 | 0.60 | 0.30 |
| Total cost on the same itemised scope | 15 % | 3 | 4 | 0.45 | 0.60 |
| Total | 100 % | 4.05 | 3.70 |
Which selection mistakes cost the most?
| Mistake | What happens on the line | How to avoid it |
|---|---|---|
| Comparing a sensor offer with a system offer | The cheaper offer cannot do half the checks once SKUs multiply | Fix the device class from the task before inviting quotes |
| Testing on easy samples only | Borderline products fail after go-live; false rejects pile up | Include worn, borderline and wrong-but-valid samples, and keep a separate test set |
| Judging by the setup demo | The recipe works on the demo parts and nothing else | Score only on the independent test set |
| Ignoring the reject chain | Failed products still leave the line | Demonstrate tracking, reject and reject confirmation |
| Leaving licences and backups out of scope | A dead PC or lost dongle stops production | Itemise licences and the recovery procedure |
| Assuming local support from a brand name | Repairs and spares take weeks | Get a named company and response terms in writing |
Most of these are not about the camera at all. They are about scope, evidence and responsibility, which is why the scorecard above weights demonstrated behaviour and support alongside the sample result.
What belongs in the South African quotation?
Request an itemised scope for camera, lens, light, mounting, enclosure, controller or PC, runtime and development licences, PLC work, reject mechanism, FAT, SAT, training and backup files. Ask for VAT treatment, freight, exchange-rate assumptions, travel, spare-part availability and the support responsibility in writing. We did not find published, verifiable information on any of the four vendors’ South African service channels, so ask each supplier to name the company that repairs and holds spares. We have not obtained equivalent current quotations from all four suppliers, so this guide gives no brand price ranking.
Our cost guide explains station budgets; PLC and reject integration explains the controls scope.
When should HIKROBOT be on the shortlist?
Our standard proposals centre on HIKROBOT cameras, readers and VisionMaster where the sample test supports them. That can suit a new station whose optics, controls and software are designed together. If your plant mandates another platform, has trained maintenance staff or a validated software estate, include that lifecycle constraint in the decision. We scope new stations; this comparison is not an offer to take over an existing third-party installation.
HIKROBOT vs Cognex · HIKROBOT vs KEYENCE · HIKROBOT vs Basler · HIKROBOT and Hikvision
Test portability and recovery before choosing a platform
Include a recovery exercise in the platform trial. Restore the approved recipe, camera configuration and calibration onto the agreed spare or recovery environment, then run the reference challenge set. The demonstration should include the actual PLC protocol and result acknowledgement. An exported project file is not sufficient if licences, firmware or external dependencies prevent it from running when production needs it.
Separate data portability from recipe portability. Images and result records may be exportable in common formats while proprietary inspection tools, trained models or operator screens still require the original runtime. Define which files the plant will receive and which changes require the integrator. A documented camera interface does not make every algorithm or controller interchangeable.
For a South African plant with a small maintenance team, the practical comparison includes access to backups, fault diagnostics, spare configuration and the agreed support response. Request written evidence from the organisation providing those services. Evaluate these obligations alongside the technical trial rather than assuming that a globally familiar brand automatically supplies local stock, application support or an identical service contract.
Compare platforms on a defined industry task
Start with the inspection contract, sample variation and presentation. Compare systems using the same visible features, operating conditions and acceptance method; device labels and processor specifications alone do not establish a successful station.
| Decision or event | Check or action | Acceptance boundary |
|---|---|---|
| Machined dimensions | Evaluate optics, calibration and reference agreement | Processor choice does not replace a measurement study. |
| Burrs | Demonstrate visibility on the specified edge and finish | A vendor defect tool is not a proven burr threshold. |
| Food trays | Test film, flange, moisture and physical reject | A camera pass is not a leak result. |
| Returnable bottles | Map mouth/base/wall checks to accessible views | A camera scope does not imply every specialised EBI function. |
Record the selected device class, optics, lighting, licensing and data interfaces in the proposal. Test the hardest normal variation as well as obvious faulty samples.
Frequently asked questions
Which machine vision brand is best?
Is this an independent laboratory benchmark?
Does a camera price include a working inspection station?
Can a platform selection replace a sample test?
How many samples does a fair comparison need?
Frank Guo is addaScan’s technical lead and writes the technical articles on this site. More about the team → LinkedIn
Sources
- HIKROBOT machine vision product menu (Official source; checked 2026-10)
- HIKROBOT VisionMaster: inspection tools and development modes (Official source; checked 2026-09-25)
- HIKROBOT Machine Vision Smart Product Catalogue 2025 Q4 (Official catalogue; checked 2026-10)
- Cognex In-Sight 3800 datasheet page (Official source; read 2026-10-03)
- Cognex logistics: DataMan barcode readers (Official source; read 2026-10-03)
- KEYENCE vision sensors (Official source; read 2026-10-27)
- KEYENCE vision systems (Official source; read 2026-10-27)
- KEYENCE fixed-mount code readers (Official source; read 2026-10-27)
- Basler product documentation: cameras (Official documentation; read 2026-10-27)
- Basler: vTool licensing (Official documentation; read 2026-10-27)
- NIST/SEMATECH e-Handbook, 7.2.4.1 Confidence intervals for a proportion (NIST; read 2026-10-27)