When to review smart cameras.
The Smart Cameras route fits compact inspection cell, presence detection, simple pass/fail automation projects. Use smart cameras when the inspection logic is contained.
Product route
Smart Cameras
Integrated imaging, onboard processing and I/O for compact inspection cells, retrofit projects and line-side decisions.
One station needs a compact pass/fail decision without a separate industrial PCConfirm cycle time, I/O, protocol, lighting, lens/FOV and algorithm complexitySmart camera for contained logic
Confirm these before model selection.
Onboard processing, I/O ready, Compact inspection are only the starting point. Also confirm field of view, working distance, line speed, interface, trigger timing and mounting limits.
Send evidence before asking for a part number.
Share sample images, good and bad parts, current reference model, target defect, tolerance, production speed and available fixture space.
Use these limits before locking a model.
- Do not lock a model before sample images, line speed and target tolerance are available.
- Do not treat the component as a standalone purchase when lighting, optics, fixture or trigger constraints are still unknown.
- Do not assume a reference brand or catalog model proves production-line acceptance.
Send route evidence before asking for a final part number.
- Part photos or short line video
- Good and bad sample examples
- Target feature size or tolerance
- Field of view and working distance
- Line speed, trigger and interface needs
When this route is a good fit
Smart cameras fit compact pass/fail cells; Deyi reviews onboard processing, I/O, lighting, lens, trigger and communication before quote.
Use this route when the project matches these constraints.
- Use when
- One station needs a compact pass/fail decision without a separate industrial PC.
- Core numbers
- Confirm cycle time, I/O, protocol, lighting, lens/FOV and algorithm complexity.
- Route split
- Smart camera for contained logic; PC-based vision for multi-camera or heavy processing.
Do not quote this route before these checks are clear.
- Do not force smart cameras into complex multi-camera algorithms that need centralized processing.
- Do not quote without I/O, protocol and reject-action details.
- Do not rely on onboard tools before sample images prove contrast stability.
Swipe horizontally to compare buyer situation, inspection constraint, recommended route and what to send.
| Buyer situation | Inspection constraint | Recommended route | What to send |
|---|---|---|---|
| Integrated camera, processor and I/O review for compact inspection stations | Smart-camera RFQ | Integrated camera, processor and I/O route for compact inspection stations. | Send defect target, station photos, I/O needs and speed. |
| Smart camera review when inspection logic can run at the edge | Edge-vision route review | Smart camera route when inspection logic can run at the edge. | Confirm tool complexity, trigger, protocol and operator interface needs. |
| Simple decision review for presence, orientation, code or label checks | Pass/fail station review | Simple decision route for presence, orientation, code or label checks. | Provide good/bad examples, reject logic and required output signal. |
| Architecture comparison between all-in-one smart camera and PC-based multi-camera system | Architecture decision review | Architecture comparison between all-in-one smart camera and PC-based multi-camera system. | List camera count, algorithm complexity, data logging and maintenance expectations. |
How buyers should compare this route
Build the product route around the inspection target, not the catalog model.
Use smart cameras when the inspection evidence matches the route.
Smart Cameras should be evaluated when the project is tied to compact inspection cell, presence detection, simple pass/fail automation. A useful review starts from the part behavior, target feature, motion condition and current failure mode, then maps those limits to the right component family instead of forcing one catalog model.
- Compact inspection cell
- Presence detection
- Simple pass/fail automation
Compare constraints, not only specifications.
Use smart cameras selection as a system decision: lens, lighting, fixture, trigger, interface and software all affect repeatability. The safest shortlist is created only after sample images, line speed and output constraints are reviewed together.
- Use smart cameras when the inspection logic is contained.
- Confirm I/O and protocol requirements.
- Avoid overloading smart cameras with complex multi-camera logic.
What engineering should confirm first
Four checks before locking the smart cameras route.
This workflow keeps the RFQ focused on the real inspection constraint and reduces the risk of buying a component that works on paper but fails under production lighting, motion or fixture variation.
- Define the inspection target State the defect, code, edge, height, presence check or measurement result that must be accepted or rejected.
- Lock optical and mechanical constraints Confirm field of view, working distance, mounting space, part motion, fixture stability and available light geometry.
- Match the component route Review smart cameras with related lenses, lighting, controllers, I/O and software rather than selecting one part number in isolation.
- Validate with samples Use good parts, bad parts and edge-case samples to confirm contrast, repeatability, read rate or measurement stability before purchase.
Reviewed selection basis
Review model data, buyer constraints and acceptance risk before RFQ lock.
Manufacturer seriesSmart camera series Selection basisXS-Code smart camera route Model routeDeyi-supported model route Buyer reference modelKeyence / Hikrobot
Model parameter matrix
Model-level parameters reviewed against manufacturer specs before RFQ lock.
AI smart camera
DY-NV5
Reference model reviewed: NV5
Feature route mapped Official family page Request this route- Architecture
- MV + AI hybrid smart-camera route
- AI functions
- Presence/absence, defect detection, classification, OCR and counting
- Deployment
- One-learning deployment workflow
- Processing
- Millisecond-level processing route
- Acquisition
- Up to 60fps image acquisition stated in official feature copy
- Route use
- Compact pass/fail and line-side AI inspection
- XS-Code public site exposes feature-level smart-camera data; exact sensor and I/O table must be locked in RFQ.
Smart camera
DY-NV4
Reference model reviewed: NV4
Feature route mapped Official family page Request this route- Series
- NV smart-camera route
- Route use
- Presence, position and compact inspection tasks
- Integration
- Onboard processing and line-side decision route
- RFQ lock
- Confirm sensor, lens, light, I/O and communication protocol
- Use as the lower-complexity smart-camera route when the exact NV5 AI package is not required.
Swipe horizontally to compare reviewed model parameters. Use the mobile cards above on small screens.
| Parameter | AI smart camera DY-NV5 Reference model reviewed: NV5 Feature route mapped Official family page | Smart camera DY-NV4 Reference model reviewed: NV4 Feature route mapped Official family page |
|---|---|---|
| Architecture | MV + AI hybrid smart-camera route | Confirm during RFQ |
| AI functions | Presence/absence, defect detection, classification, OCR and counting | Confirm during RFQ |
| Deployment | One-learning deployment workflow | Confirm during RFQ |
| Processing | Millisecond-level processing route | Confirm during RFQ |
| Acquisition | Up to 60fps image acquisition stated in official feature copy | Confirm during RFQ |
| Route use | Compact pass/fail and line-side AI inspection | Presence, position and compact inspection tasks |
| Series | Confirm during RFQ | NV smart-camera route |
| Integration | Confirm during RFQ | Onboard processing and line-side decision route |
| RFQ lock | Confirm during RFQ | Confirm sensor, lens, light, I/O and communication protocol |
| RFQ notes |
|
|
What changes the route, cost and delivery review.
- Application route
- Compact inspection cell, Presence detection, Simple pass/fail automation
- Hardware scope
- Onboard processing, I/O ready, Compact inspection
- Buyer reference model
- Keyence / Hikrobot
Common use cases
Common reasons product selection goes wrong.
- Choosing by resolution, catalog size or brand reference before defining the inspection target.
- Ignoring lighting, lens, fixture or trigger limits that decide whether the component can repeat on the production line.
- Requesting a quote without good/bad sample images, line speed, target tolerance or the current failure mode.
Evidence that helps engineering reply faster.
Part photos or short line videoGood and bad sample examplesTarget feature size or toleranceField of view and working distanceLine speed, trigger and interface needsCurrent model, competitor reference or failure mode
Related solution routes
Connect this product family to an inspection problem.
Solution
Automated Visual Inspection
Build automated visual inspection systems for defect detection, presence checks, surface inspection, orientation, measurement and repeatable pass/fail output.
SolutionBarcode & Traceability
Select readers and lighting for label codes, DPM marks, carton sorting and part tracking.
SolutionFlexible Feeding & Robot Loading
Build flexible small-part loading cells with F/FL/FS feeder trays, optional storage bins, vision positioning and DTA robot pickup routes.
Application case briefs
See how this product family appears in real inspection scenarios.
Packaging inspection
Packaging Label and Barcode Traceability
Application brief for label presence, barcode read rate and packaging traceability on moving conveyor lines.
Metal and surface inspectionDirect Part Mark Code Reading on Metal Parts
Application route for DPM barcode reading on machined or laser-marked metal parts with difficult surface contrast.
Electronics inspectionPCB Connector Pin Presence Inspection
Application brief for checking connector pin presence, orientation and bent-pin risk with camera, lens and controlled lighting.
Related buying guides
Use these guides to validate the product route before RFQ.
Resource
What Is a Smart Camera?
Decide when a smart camera is enough for a compact cell and when PC-based vision is safer for algorithms, data or multi-camera scope.
ResourceSmart Camera vs PC-Based Vision System
Compare smart cameras and PC-based machine vision systems by inspection complexity, I/O, multi-camera logic, data handling, maintenance and expansion risk.
ResourceIndustrial Barcode Reader Selection Guide
Select fixed industrial barcode readers by code type, module size, read distance, line speed, lighting route, trigger timing and no-read handling.
ResourceFixed Barcode Reader vs Handheld Scanner
Compare fixed-mount barcode readers and handheld scanners for production lines, warehouses and traceability cells.
Reference alternatives
Compare this product family against reference-model requirements.
Compare
Banner Vision Sensor Alternative
Compare Banner-style vision sensors with smart cameras, lighting and compact pass/fail inspection routes.
CompareSICK Vision Sensor Alternative
Map SICK-style sensor and reader requirements to fixed barcode reading, smart camera and inspection cell needs.
CompareOmron Vision System Alternative
Compare Omron-style inspection system requirements with modular cameras, optics, lighting and smart camera routes.
CompareCognex Camera Alternative
Compare Cognex-style machine vision camera requirements with inspection goals, lighting constraints and integration budget.
Product RFQ
Need help selecting smart cameras?
Send working distance, target size, speed, defect type, competitor model or sample images before locking a part number.
Request engineering RFQProduct FAQ
Common questions before selecting smart cameras.
How do I confirm whether smart cameras fit my project?
Start with the inspection goal, field of view, working distance, line speed and target tolerance. Then match smart cameras with lens, lighting, mounting and I/O requirements instead of choosing by part number alone.
What information improves smart cameras selection accuracy?
Send good and bad sample images, target feature size, field of view, working distance, speed, trigger method, interface requirement and any current reference model. That lets engineering confirm whether smart camera is the right route or whether another product family is safer.
When should I avoid selecting smart cameras by catalog specs only?
Avoid catalog-only selection when the part is reflective, moving quickly, tolerance-sensitive, space-limited or already failing under manual inspection. In those cases, lighting, lens, fixture and software behavior often matter as much as the component specification.
What information should I send before requesting a machine vision quote?
Send part photos or drawings, target defect or measurement goal, field of view, working distance, line speed, accuracy target, lighting limits and any current camera, lens, light, barcode reader or competitor model.
Do I need a 2D or 3D machine vision system?
Use 2D when contrast, edges, labels or position are enough to judge the part. Use 3D when height, profile, gap, volume, weld shape or surface geometry decides pass or fail.
How should I choose machine vision lighting?
Start from the defect and material surface instead of the camera model. Backlight helps edge measurement, coaxial and dome lighting help reflective surfaces, and bar or ring lighting often works for general presence and defect checks.