Components · Software

Vision Software

Software turns images into decisions. A good vision application combines the right tools — locating, measuring, reading, inspecting, deep learning — with robust communication, clear operator screens and traceable data.

Phần mềm biến hình ảnh thành quyết định: định vị, đo, đọc mã, kiểm tra lỗi, học sâu — kèm giao tiếp ổn định, giao diện vận hành rõ ràng và dữ liệu truy xuất được.

How it works

The vision pipeline

Almost every application follows the same steps: acquire the image, prepare it (filters, calibration), locate the part, run the inspection, measurement or reading tools, decide pass or fail, send the result to the line and log images and data.

Rule-based tools are precise, fast and explainable — ideal for measurement, code reading and well-defined features. Deep learning learns from labeled images and excels where defects vary in shape and appearance or backgrounds are complex.

In practice, the best systems are often hybrid: rule-based tools locate and measure; deep learning classifies the difficult, natural-looking defects.

1 · Acquire 2 · Pre-process 3 · Locate 4 · Inspect / measure 5 · Decide 6 · Output 7 · Log images, results, statistics → MES / data platform

Types

Software capabilities in detail

Open each type for how it works, where it fits, its limitations and the specifications to check.

01 Graphical (no-code) vision softwareBuild inspections with flowcharts and parameter panels.

How it works. Tools are connected visually; parameters are set with live images. Operators and engineers can adjust recipes without programming.

Best for

  • Fast deployment
  • Machine builders and plant engineers
  • Frequent product changes

Limitations

  • Very special algorithms may still need scripting or an SDK

Key specs to check

  • Tool library
  • Scripting option
  • Recipe management
  • User levels
02 SDK / vision librariesFull flexibility for custom applications.

How it works. Programming libraries for image acquisition, processing and communication, used inside custom software.

Best for

  • OEM machines
  • Unusual algorithms
  • Tight integration with machine software

Limitations

  • Requires software development and maintenance

Key specs to check

  • Supported languages
  • Platform support
  • Licensing model
03 Rule-based tool libraryPrecise, explainable tools for well-defined tasks.

How it works. Pattern and shape matching, blob analysis, edge and caliper tools, geometric fitting, gauging, color tools, code reading and OCR/OCV.

Best for

  • Measurement and gauging
  • Code reading
  • Presence and position
  • Alignment and robot guidance

Limitations

  • Struggles with highly variable defects and complex textures

Key specs to check

  • Sub-pixel accuracy
  • Speed per tool
  • Calibration support
04 Deep learningLearns from labeled examples instead of explicit rules.

How it works. Classification (what is it?), detection (where is it?), segmentation (which pixels?), anomaly detection (trained on good parts only) and deep-learning OCR.

Best for

  • Natural, variable defects (scratches, stains, cracks)
  • Complex backgrounds and textures
  • Difficult OCR

Limitations

  • Needs representative images and careful labeling
  • Less explainable; requires validation and change control

Key specs to check

  • Model types
  • Training workflow
  • Inference speed on CPU/GPU
05 3D processingTools for height maps and point clouds.

How it works. Plane fitting, height and volume measurement, 3D matching, profile tools and 3D calibration for robots.

Best for

  • Height, flatness, volume
  • Bin picking and robot guidance

Limitations

  • Requires good 3D data and calibration

Key specs to check

  • Supported sensors
  • Point-cloud tools
  • Robot calibration
06 HMI, data & integrationOperator screens, statistics and plant connectivity.

How it works. Custom operator screens, image archives, statistics and SPC, and communication with PLC, robots and MES or a manufacturing data platform.

Best for

  • Traceability and audits
  • Process improvement from inspection data
  • Plant-wide visibility

Limitations

  • Data volumes must be planned

Key specs to check

  • Protocols
  • Database/export options
  • User management and audit trail

Compare

Rule-based vs deep learning

Rule-based vs deep learning
CriterionRule-based toolsDeep learning
Best forMeasurement, codes, defined featuresVariable, natural defects, complex textures
SetupConfigure tools and thresholdsCollect, label and train images
ExplainabilityHigh — every rule is visibleLower — validated by test sets
Precision of measurementSub-pixel, metrologicalNot intended for precise measurement
Handling variationLimited to programmed casesGeneralizes from examples
HardwareCPU usually sufficientGPU often recommended

Specifications

What to look for in vision software

What to look for in vision software
SpecificationWhat it meansHow to choose
Camera supportStandard camera interfaces and GenICam compliance.Freedom to choose cameras and replace them later.
Tool coverage2D, 3D, codes, OCR, deep learning.One platform for current and future tasks.
PerformanceProcessing time per tool and parallelism.Must fit the cycle time with margin.
Recipe managementProduct-specific settings.Fast changeovers without engineering support.
User managementRoles, passwords, audit trail.Protects settings; needed in regulated industries.
LoggingImages, results, statistics.Traceability and continuous improvement.
CommunicationPLC, robot, TCP/IP, file and database export.Clean handshakes with the line and MES.
MaintainabilityDocumentation, backup, versioning.Your team can support it after handover.

Engineering tools

Calculate before you choose

Quick estimates based on standard formulas. Always confirm with a test on real parts.

Rule-Based, Deep Learning or Hybrid?

Answer four questions about your inspection to get a recommended software approach.

All calculators in the Knowledge hub

Selection guide

Which approach for which task?

Which approach for which task?
RequirementRecommendedWhy / note
Precise dimensionsRule-based measurement toolsSub-pixel edge and fit tools.
Codes and printed textCode reading and OCR/OCV toolsDeep-learning OCR for difficult fonts.
Scratches, stains, cracks on textured surfacesDeep learning (detection/segmentation)Collect representative defects.
Unknown or rare defectsAnomaly detectionTrain mainly on good parts.
Presence and positionPattern matching and blob toolsFast and simple.
Mixed requirementsHybrid pipelineRules locate/measure, deep learning classifies.

Selection steps

  1. Write down what must be found, measured or read — and the acceptance criteria.
  2. Collect images of good parts and all known defect types.
  3. Choose rule-based, deep learning or hybrid for each task.
  4. Build and tune the program; define recipes and user levels.
  5. Validate with a separate test set and document results.
  6. Integrate communication, HMI and data logging.
  7. Hand over with training, documentation and backups.

Examples

Typical application examples

Illustrative setups showing how the components are combined in practice.

Application example

Cosmetic defects on molded parts

Challenge
Defects varied widely and rule thresholds caused false rejects.
Setup
Deep-learning segmentation on a GPU edge computer.
Result
Variable defects detected with far fewer false rejects after validation.

Application example

Mixed inspection on a gearbox cover

Challenge
Needed dimensions, presence of inserts and surface defects.
Setup
Hybrid: pattern matching and gauging tools plus deep-learning classification.
Result
Each task uses the best-suited method in one program.

Application example

Lot and date code verification

Challenge
Printed text with varying quality.
Setup
OCR/OCV with font training and quality limits.
Result
Wrong or unreadable codes are rejected automatically.

Common mistakes to avoid

  • Starting software before lighting and optics are right.
  • Training deep learning with too few or unrepresentative images.
  • Using deep learning for precise measurement.
  • No validation set — results look good only on training images.
  • No recipe management or user rights — settings change without control.
  • Not logging images, making it impossible to investigate escapes.

FAQ

Frequently asked questions

How many images are needed for deep learning?

It depends on the task and defect variability. Anomaly detection can start mainly with good parts; supervised detection typically needs many labeled examples per defect class. We plan the data collection with you.

Can operators change settings?

Yes, within defined limits. Recipes and user levels let operators switch products while protecting critical parameters.

Can the software send data to MES?

Yes. Results, measurements and image references can be sent to MES or a manufacturing data platform for traceability and analysis.

What happens when the product changes?

New products are added as recipes. For deep learning, models may need additional images and retraining, followed by validation.

🌐 Tiếng Việt